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.
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 and as a result passenger could not get to work.
After deleting those default files it worked fine again.
PS: it worked all fine before but either froxlor or webmin have messed it up.
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.
-----------------------------------------------------------
- passenger was running fine
- apache2 was set up ok, same with my virtual hosts
- and rvm was running wonderfully
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 and as a result passenger could not get to work.
After deleting those default files it worked fine again.
PS: it worked all fine before but either froxlor or webmin have messed it up.
Kommentare
Kommentar veröffentlichen