You might probably faced the same following error while you were restarting the Apache server on Ubuntu.
$ sudo /etc/init.d/apache2 restart
* Restarting web server apache2 apache2: 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
* Restarting web server apache2 apache2: 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
To fix that problem, you need to edit the httpd.conf file. Open the terminal and type,
$ sudo gedit /etc/apache2/httpd.conf
By default httpd.conf file will be blank. Now, simply add the following line to the file.
ServerName localhost
Save the file and exit from gEdit.
Finally restart the server.
$ sudo /etc/init.d/apache2 restart
Source: How to fix Apache – “Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName” Error on Ubuntu.
Please don't copy and duplicate my original blog post.
ReplyDeleteWithout asking any permission doing this is illegal.
Please remove the post.
You don't need any traffic? You don't need better Google PageRank?
ReplyDeletethanks a lot. more power...
ReplyDeleteit works boy..ty
ReplyDeleteWorked for me - thanks!
ReplyDeleteWorked for me thank u so much !
ReplyDeletecheers, works.
ReplyDeleteworks for me too
ReplyDeleteThank, that's right!
ReplyDeleteawesome help..
ReplyDeleteturns out the problem very easy
It worked for me.Thanks a lot
ReplyDeleteWorks like a charm, thanks!
ReplyDeleteI'd suggest these 3 lines:
$ sudo su
# echo "ServerName localhost" >> /etc/apache2/httpd.conf
# /etc/init.d/apache2 restart
How easy was that :0
ReplyDeleteThanks!!! It's works!!!
ReplyDeleteworking like a charm, thank you!
ReplyDeleteCheers for that. I had been ignoring that error for ages!!
ReplyDeletethanks, worked for me as well.
ReplyDeleteMy http.conf file is not blank. where to add the line?
ReplyDeleteThanks (again!!)....
ReplyDeletethis is work thanks
ReplyDeletei add "ServerName " line
Me too - simple yet effective! :-)
ReplyDeletewah~!
ReplyDeleteI for one am grateful for the post.
Thank you for spreading the good advice (supposedly the only man on the planet came up with the idea....Aslam)....everyone bow down.
Doesn't work if you have 2 virtual server's running in the htttp.conf thru port 80. If all you have in the http.conf is ServerName then it will work, otherwise if you are set up like this.........
ReplyDeleteServerAdmin webmaster@localhost
DocumentRoot /var/www/somesite1
ServerName localhost
DirectoryIndex index.htm
AllowOverride None
Order allow,deny
Allow from all
ErrorLog /var/log/apache2/error.log
LogLevel warn
CustomLog /var/log/apache2/access.log combined
ServerAdmin webmaster@localhost
DocumentRoot /var/www/somesite2
ServerName localhost
DirectoryIndex index.htm
AllowOverride None
Order allow,deny
Allow from all
ErrorLog /var/log/apache2/error.log
LogLevel warn
CustomLog /var/log/apache2/access.log combined
(IT WON'T WORK!)
Please help! :(
[...] [SOLVED] “Could not reliably determine the server’s fully qualified domain name, using … for S.... Share this:ShareFacebookTwitterEmailLike this:LikeBe the first to like this post. Programming [...]
ReplyDeleteAwesome, worked like a charm!
ReplyDeletethank you
ReplyDelete[...] You may get an error from Apache: “apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName”. To fix this problem, do the following (as described here): [...]
ReplyDeleteThanks !
ReplyDelete[...] to russenreaktor and aslamnajeebdeen for the fix. This entry was posted in Ubuntu. Bookmark the [...]
ReplyDeleteThanks a lot!
ReplyDeletespread the knowledge how ever you can. this is a virtue.
ReplyDeleteyou should remove this post. its a blatant copy/paste.
ReplyDeleteIt didn't work for me. I have Ubuntu 11.10 recently installed.
ReplyDeletewonderful it works for me...
ReplyDeletethank you..
ReplyDeleteits works...gr8 job
ReplyDelete[...] konfigurasi dapat dilihat di sini. Share this:TwitterFacebookLike this:LikeBe the first to like this [...]
ReplyDeletethank's for solution :D
ReplyDeletethanks a lot for your support to all of us ...
ReplyDeleteway to go !!
regards
thanks...............................
ReplyDeleteIf running Ubuntu DO NOT edit httpd.conf!
ReplyDeleteecho "ServerName localhost" | sudo tee /etc/apache2/conf.d/fqdn
Thank you for copying this info. Mohamed Aslam's website has expired, and the info would have been lost otherwise. I for one am grateful.
ReplyDeleteYou sure you went to /etc/apache2/httpd.conf not /opt/lampp/etc/httpd.conf?
ReplyDeleteit works.thanks
ReplyDeletethank you man for your support
ReplyDeleteIf he had not duplicated your post, maybe some people wouldn't have found a solution so fast, which is in no way a gain for society...
ReplyDeleteSo please leave your "copyright infringement" claims at home, the internet is a free place...
thanks!
ReplyDeletecheers ^_^
It is working.. Thanks a ton!!
ReplyDeleteNo Such file in my syste :(
ReplyDelete/etc/apache2/httpd.conf
#if you dont find httpd.conf edit the hosts
ReplyDelete# restart apache services All Good for me .
/etc$ sudo vim hosts
127.0.0.1 localhost
192.168.168.122 WebServer-Linux.webpalm.ie WebServer-Linux
Really, a bit narcissistic are we? Do you really think that editing httpd.conf was so brilliant that only you would possible have come up with it and you should therefore be acknowledged every time that it is done?
ReplyDeleteThe original for this is no longer present, I'm glad it was duplicated here
ReplyDelete[...] (sumber: sini dan sini) [...]
ReplyDeleteThanks for my first apache answer that wasnt over complicated (by the answer) and actually worked first time.
ReplyDeleteit did not work for me - it keeps saying the same
ReplyDeleteThis makes a bug --- DO NOT ATTEMPT THIS
ReplyDeletein order for this to work, then edit the file fqdn and remove the " characters
ReplyDeletethen it works
[...] http://russenreaktor.wordpress.com/2010/04/17/solved-%E2%80%9Ccould-not-reliably-determine-the-serve... [...]
ReplyDeleteHI, tried it but it did not work for me.
ReplyDeleteso i checked my hosts and i have something like this:
127.0.0.1 localhost
127.0.1.1 voice
what do i do?
don't remove this post.
ReplyDeletestop being a jerk you numbskull :P
ReplyDeleteRestarting web server apache2 /usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted)
ReplyDeleteapache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
when restart apache server..
ReplyDelete/usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted)
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down Unable to open logs Action 'start' failed.
The Apache error log may have more information.
how to solve it could you please help..
ReplyDeletehow uninstall lamp server completly
ReplyDelete