Comments on: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName http://www.ikode.net/2010/04/28/could-not-reliably-determine-the-server%e2%80%99s-fully-qualified-domain-name-using-127-0-1-1-for-servername/ More then just geek talk Tue, 14 Dec 2010 19:53:48 +0000 hourly 1 http://wordpress.org/?v= By: Alexey http://www.ikode.net/2010/04/28/could-not-reliably-determine-the-server%e2%80%99s-fully-qualified-domain-name-using-127-0-1-1-for-servername/comment-page-1/#comment-22 Alexey Mon, 30 Aug 2010 20:18:04 +0000 http://www.ikode.net/?p=155#comment-22 Thanks Thanks

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: to domain name http://www.ikode.net/2010/04/28/could-not-reliably-determine-the-server%e2%80%99s-fully-qualified-domain-name-using-127-0-1-1-for-servername/comment-page-1/#comment-6 to domain name Mon, 03 May 2010 08:23:55 +0000 http://www.ikode.net/?p=155#comment-6 <strong>hi guys...</strong> hi guysI would like to thank you for the efforts you have made in writing this article. I am hoping the same best work from you in the future as well and i have start my own blog now, , thanks for your effort... hi guys…

hi guysI would like to thank you for the efforts you have made in writing this article. I am hoping the same best work from you in the future as well and i have start my own blog now, , thanks for your effort…

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: Daniel Tisza-Nitsch http://www.ikode.net/2010/04/28/could-not-reliably-determine-the-server%e2%80%99s-fully-qualified-domain-name-using-127-0-1-1-for-servername/comment-page-1/#comment-5 Daniel Tisza-Nitsch Thu, 29 Apr 2010 14:39:20 +0000 http://www.ikode.net/?p=155#comment-5 Actually, it's got nothing to do with a Virtual Server. The problem lies with the fact that *nix servers expect a correct "domain name" or hostname. On a fresh install of *nix systems, often the default name will be set to localhost or 127.0.0.1. This is not a "correct" NAME (localhost is not a "real address" to a server, but something know as a loop-back address). Since many people set up their *nix environments for testing or development purposes, there is usually no need to ever change that. The problem lies with the fact that Apache is expecting the server to be set up as if it was a fully / properly configured hosting server, and is just being picky about getting the information on the server set up correctly so that there are no loopholes or errors later on. For that reason, force setting the "ServerName" to something in the httpd.conf (or apache2.conf if you are using ubuntu) will bypass the step of checking the server for the domain name, since you manually set it up in the config file! Actually, it’s got nothing to do with a Virtual Server.

The problem lies with the fact that *nix servers expect a correct “domain name” or hostname.

On a fresh install of *nix systems, often the default name will be set to localhost or 127.0.0.1. This is not a “correct” NAME (localhost is not a “real address” to a server, but something know as a loop-back address). Since many people set up their *nix environments for testing or development purposes, there is usually no need to ever change that.

The problem lies with the fact that Apache is expecting the server to be set up as if it was a fully / properly configured hosting server, and is just being picky about getting the information on the server set up correctly so that there are no loopholes or errors later on. For that reason, force setting the “ServerName” to something in the httpd.conf (or apache2.conf if you are using ubuntu) will bypass the step of checking the server for the domain name, since you manually set it up in the config file!

Like or Dislike: Thumb up 1 Thumb down 0

]]> By: Brian Reich http://www.ikode.net/2010/04/28/could-not-reliably-determine-the-server%e2%80%99s-fully-qualified-domain-name-using-127-0-1-1-for-servername/comment-page-1/#comment-4 Brian Reich Thu, 29 Apr 2010 13:20:12 +0000 http://www.ikode.net/?p=155#comment-4 Unless I'm missing something with your virtual server configuration, could the fact that your loopback address was configured to 127.0.1.1 instead of 127.0.0.1 be problematic? .-= Brian Reich´s last blog ..<a href="http://www.reich-consulting.net/2010/04/08/use-a-different-password-for-insecure-websites/" rel="nofollow">Use a Different Password for Insecure Websites</a> =-. Unless I’m missing something with your virtual server configuration, could the fact that your loopback address was configured to 127.0.1.1 instead of 127.0.0.1 be problematic?
.-= Brian Reich´s last blog ..Use a Different Password for Insecure Websites =-.

Like or Dislike: Thumb up 0 Thumb down 0

]]>