A while back I was getting the error message
Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
… waiting apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
every time I restarted Apache. Apparently to fix this issue you have to edit the /etc/apache2/httpd.conf. To resolve this issue, open up the httpd.conf (this will be empty by default) and add ServerName localhost. After you’ve added that entry, restart the Apache server and everything should work.
apt-get install curl libcurl3 libcurl3-dev php5-curl
Got a bit of the runaround when I was trying to setup my wordpress permalinks. Even though all was setup properly, I was not able to get the rewrite going. After some time I found that mod_rewrite was not automatically enabled. Running a quick a2enmod rewrite fixed it up really quick and now my links are looking spectacular!
For some reason, when I was using Ubuntu 10.04, I was unable to get my virtual hosts working. I am not too sure if it is because I am using 10, and I come from a previous 9 version, but in any event, I found it odd that I had to edit the httpd.conf to get my virtual hosts running.
The settings on my virtual host files were correct, because I’ve done it a thousand
1
2
3
4
5
6
7
8
| <VirtualHost 97.107.128.155:80>
ServerAdmin admin@malfunkshen.ca
ServerName johnathankong.ca
ServerAlias www.johnathankong.ca
DocumentRoot /srv/www/johnathankong.ca/public_html/
ErrorLog /srv/www/johnathankong.ca/logs/error.log
CustomLog /srv/www/johnathankong.ca/logs/access.log combined
</VirtualHost> |
But for some reason I kept getting the following warning messages
[warn] VirtualHost 97.107.128.155:80 overlaps with VirtualHost 97.107.128.155:80, the first has precedence, perhaps you need a NameVirtualHost directive
I know a lot of people say that those warning messages don’t matter, but it did in my case because I was hosting multiple sites from my server. After a bit of digging I found that I had to add NameVirtualHost 97.107.128.155:80 to the httpd.conf file. Some of the solutions was to put a “*” instead of an IP, but that did not resolve my issues, so you might want to try that out first, but in my case, it did not do anything.
What I found really odd about this experience, and I’ve compared this, is that on my other corporate servers I did not have to edit my httpd.config file. In any event, once I added that line everything worked well.