Error Could Not Determine Server
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the could not reliably determine the server workings and policies of this site About Us Learn more about Stack httpd could not reliably determine the server's fully qualified domain name Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users
Could Not Reliably Determine The Server's Fully Qualified Domain Name Centos
Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it
(98)address Already In Use: Ah00072: Make_sock: Could Not Bind To Address [::]:80
works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Problem with restarting Apache2 [duplicate] up vote 62 down vote favorite 22 This question already has an answer here: Could not reliably determine the server's fully qualified domain name? 8 answers I'm trying to restart apache2 : sudo service apache2 restart (13)permission denied: ah00072: make_sock: could not bind to address [::]:80 But get below error : Restarting web server apache2 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message I've tried to change sudo gedit /etc/apache2/httpd.conf Blank file appears, and i'd added this : ServerName localhost But that error doesn't disappear ! Any ideas would be appreciated. apache2 share|improve this question asked Aug 6 '13 at 13:42 Hamed Kamrava 80661740 marked as duplicate by Florian Diesch, Richard, Aditya, Maythux, Warren Hill Mar 12 '14 at 13:33 This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question. 1 well have you checked the link I posted? The error is clearly the same. try "my" Answer below. –Meintjes Aug 6 '13 at 13:58 add a comment| 4 Answers 4 active oldest votes up vote 92 down vote accepted So i found this: How do I restart/reload Apache when it can't determine the domain name? Good news! Apache is restarting successfully. Apache just isn't sure wher
httpd serive when doing restart ! General support questions Post Reply Print view Search Advanced search 8
Starting Httpd: Httpd: Apr_sockaddr_info_get() Failed For
posts • Page 1 of 1 squidcentos Posts: 78 Joined: servername localhost 2013/01/19 13:04:07 Contact: Contact squidcentos Website [SOLVED] problem in httpd serive when doing restart ! Quote apache servername directive Postby squidcentos » 2013/02/28 09:38:28 hi ,ive installed Apache server on centos 6.3 usingyum install httpd now i have an application called video cache that work http://askubuntu.com/questions/329323/problem-with-restarting-apache2 integrated with squid .i put the listen port ot Apache to be 4335 because 80 is reserved for another application >im trying to restart the httpd i have two errors :[root@squid ~]# apachectl -k restarthttpd: apr_sockaddr_info_get() failed for squidhttpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerNamenow http://www.centos.org/forums/viewtopic.php?t=3647 i modified the file :/etc/hosts to become as below :127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4::1 localhost localhost.localdomain localhost6 localhost6.localdomain6127.0.0.1 squidafter that ,there still an error exitst !In case of any bugs or problems, visit http://cachevideos.com/ and contact us.[root@squid videocache]# apachectl -k restarthttpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerNameABOUT THE ERROR above ,is it important ???does it affecting the httpd service ??how to solve it ?regards Top gerald_clark Posts: 10594 Joined: 2005/08/05 15:19:54 Location: Northern Illinois, USA [SOLVED] problem in httpd serive when doing restart ! Quote Postby gerald_clark » 2013/02/28 17:35:01 You need to put your actual IP and hostname in /etc/hosts, not add another 127.0.0.1 line. Top squidcentos Posts: 78 Joined: 2013/01/19 13:04:07 Contact: Contact squidcentos Website Re: problem in httpd serive when doing restart ! Quote Postby squidcentos » 2013/02/28 18:06:52 gerald_clark wrote:You need to put your actual IP and hostname in /etc/hosts, not add another 127.0.0.1 line.
here for a quick overview of the site Help Center Detailed answers to any questions you http://stackoverflow.com/questions/9541460/httpd-could-not-reliably-determine-the-servers-fully-qualified-domain-name-us might have Meta Discuss the workings and policies of this site https://thomas.vanhoutte.be/miniblog/fix-apache-error-ah00558/ About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of could not 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName up vote 131 down vote favorite 33 CentOS 5.0 I tried to restart my apache server and got this messeage httpd: could not reliably Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName here is /etc/host file 127.0.0.1 server4-245 server4-245.com localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 here is /etc/sysconfig/network file NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=server4-245 I also have this in apache httpd.conf file ServerName localhost However, I still get the first error messeage when I restart the apache. linux apache centos share|improve this question asked Mar 2 '12 at 22:49 user1220351 660266 Ensure you edited the right httpd.conf. Usually ServerName xy is just fine. –KingCrunch Mar 2 '12 at 22:53 add a comment| 8 Answers 8 active oldest votes up vote 62 down vote accepted Your hosts file does not include a valid FQDN, nor is localhost an FQDN. An FQDN must include a hostname part, as well as a domain name part. For example, the following is a valid FQDN: host.server4-245.com Choose an FQDN and include it both in your /etc/hosts file on both the IPv4 and IPv6 addresses
a VPS with DigitalOcean to test out some PHP scripts and to increase my overall Apache and Linux skills.However, upon restarting my Apache webserver running Ubuntu 64-bit, I was greeted with this error message:[emailprotected]:~# sudo /etc/init.d/apache2 restart * Restarting web server apache2 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this messageFixing this problem is, however, quite easy. Apache wants you to define a ServerName. So let's add it by first opening terminal and editing the httpd.conf file: sudo nano /etc/apache2/apache2.confGo to the very bottom of that file and add this line:ServerName localhostThe error code AH00558 should now be gone. Try restarting the Apache daemon to see if the error message is indeed no longer displayed:sudo /etc/init.d/apache2 restartThe output will look like this:[emailprotected]:~# sudo /etc/init.d/apache2 restart * Restarting web server apache2 [ OK ]Fix Apache Error: Could not reliably determine the server's fully qualified domain name was last modified: July 27th, 2015 by Thomas
Share the KnowledgeTwitterRedditWhatsappFacebook Author BioThank you for your interest in my blog! On this miniblog, I write mostly short (technical) blog posts that might interest other people. Read more about me or feel free to contact me. Google Ads Policy: Important information regarding the user consent policy →•← Fix: php mail() slow to sent on Ubuntu 3 thoughts on “Fix Apache Error: Could not reliably determine the server's fully qualified domain name” Programming Help says: December 20, 2015 at 19:11 It solved my issue. I had the same issue. But the problem is that "Problem has gone". But https: is not looking green. It become green when we are loading the content of website. But Once website is loaded https green color go away. Kindly help me to fix it.Reply to Programming Thomas says: December 21, 2015 at 21:00 Hi This could mean some resources are not loaded over HTTPS, but over an unsecured HTTP connection. Or, you could be using the deprecated SHA-1 algorithm for your certificate. Read here why you shouldn't be using SHA-1 any longer.Reply to Thomas sdfds says: July 29, 2016 at 11:29 TRY YOUR BESTReply to sdfds Leave a Reply Cancel replyYour email address will