Could not reliably determine the server s fully qualified domain name

Question

I have just installed Apache 2 2 17  and I am using it first time    Now when I try to start the server using the command service httpd start it gives me the message      httpd  Could not reliably determine the server s fully qualified domain name  using   1 for ServerName   Now I think I have to set ServerName and the IP address as I search through Google  But I don t know in which file I have to set   How can I fix this problem

User · Answer

sudo vim  etc apache2 httpd conf Insert the following line at the httpd conf  ServerName localhost Just restart the Apache   sudo  etc init d apache2 restart

User · Answer

If you are using windows there is something different sort of situation  First open c  apache24 conf httpd conf  The Apache folder is enough not specifically above path  After that you have to configure httpd conf file    Just after few lines there is pattern like    Listen               80 Listen 80   Here You have to change for the localhost    You have to enter ipv4 address for that you can open localhost   Refer this video link and after that just bit more    Change your environment variables      In which you have to enter path   c apache24 bin   and same in the SYSTEM variables     If any query feel free to ask

User · Answer

FQDN means the resolved name over DNS  It should be like  server-name search-domain    The warning you get just provides a notice that httpd can not find a FQDN  so it might not work right to handle a name-based virtual host  So make sure the expected FQDN is registered in your DNS server  or manually add the entry in  etc hosts which is prior to hitting DNS

User · Answer

who are still couldnt resolve the problem and using mac then follow this  1 goto the root folder     cd usr local etc apache2 2 4   3 sudo nano httpd conf  4 change  servername to ServerName 127 0 0 1 8080 press ctrl o  return ctrl x  5 then restart the server apachectl restart

User · Answer

Here s my two cents  Maybe it s useful for future readers   I ran into this problem when using Apache within a Docker container  When I started a container from an image of the Apache webserver  this message appeared when I started it with docker run -it -p 80 80 my-apache-container   However  after starting the container in detached mode  using docker run -d -p 80 80 my-apache-container  I was able to connect through the browser

User · Answer

Under Debian Squeeze    Edit Apache2 conf file   vim  etc apache2 apache2 conf Insert the following line at the apache2 conf  ServerName localhost Restart Apache2  apache2ctl restart or  etc init d apache2 restart   Should work fine  it did solve the problem in my case   tks noodl for the link on the different layouts

User · Answer

sudo nano  etc apache2 httpd conf search for a text ServerName in nano editor  lt Ctrl   W gt  Insert the following line at the httpd conf  ServerName localhost Just restart the Apache   sudo  usr sbin apachectl restart

User · Answer

Yes  you should set ServerName   http   wiki apache org httpd CouldNotDetermineServerName  http   httpd apache org docs current mod core html servername  You can find information on the layouts used by the various httpd distributions here   http   wiki apache org httpd DistrosDefaultLayout  In your case the file to edit is  etc httpd conf httpd conf

User · Answer

If you are using windows  remove comment on these lines and set them as   Line 227   ServerName 127 0 0 1 80  Line 235   AllowOverride all  Line 236   Require all granted   Worked for me

User · Answer

I was NOT getting the ServerName wrong  Inside your VirtualHost configuration that is causing this warning message  it is the generic one near the top of your httpd conf which is by default commented out   Change   ServerName www example com 80   to     ServerName 127 0 0 1 80

User · Answer

To solve this problem You need set ServerName   1    vim  etc apache2 conf d name For example set add ServerName localhost or any other name   2  ServerName localhost Restart Apache 2  3    service apache restart For this example I use Ubuntu 11 10 1 125

User · Answer

Two things seemed to do it for me    Put all aliases for 127 0 0 1 in  etc hosts in a single line  e g  127 0 0 1 localhost mysite local myothersite local Set ServerName in my httpd conf to 0 0 0 0  localhost or 127 0 0 1 didn t work for me    Editing  etc hosts got rid of long response times and setting the ServerName got rid of OP s warning for me

User · Answer

Another option is to ensure that the full qualified host name  FQDN  is listed in  etc hosts  This worked for me on Ubuntu v11 10 without having to change the default Apache configuration

[apache2] Could not reliably determine the server's fully qualified domain name

Examples related to apache2

Examples related to fedora