Dontyoudarenottobeaware

This could be a huge post, but I am cutting it short: configure pg_hba.conf right, e.g. set host stuff to password md5 try to connect to your database locally to test it, e.g. psql -U user "psql -U user dbname -W" and type in the password install phppgadmin, e.g. on debian I could not find a /etc/phppgadmin/apache.conf but a /etc/apache2/conf.d/phppgadmin your apache2 should be able to serve SSL, otherwise look a my post from yesterday: SSL virtualhost after you setup a SSH connection through rsa keys and always redirect to it in order to serve multiple site using SSL you should change to *:443 instead of _default_ also you have to tell /etc/apache2/ports.conf to use NameVirtualhost when listening on 443; otherwise apache will tell you about conflicting virtualhosts. apache2: now its time to copy the content of conf.d/phppgadmin into a sites-available file and dont forget to delete the alias line and adjust names and folders. From now on I followed these steps: Step...

First of all, I like these little problems because they make me so much better with dealing with linux. And since its a hobby of mine, I cant really complain. Anyway, it took me a while to figure out that postgresql could not connect via the console because of some settings regarding authorization. Go to your pg_hba.conf and change from peer to md5 and you can login your database with your user and password. ----------------------------------------------------------- The second thing also troubled me a while and I was checking everything, because the log files did tell what was going wrong. passenger was running fine apache2 was set up ok, same with my virtual hosts and rvm was running wonderfully But I could not connect to my virtual hosts. And after a decent research on the internet and after quite a lot of message boards and posts I found the answer: check for the apache2/sites-enabled/default And there it was, these default files overwrote my virtualhosts an...