If it is running, make sure it's listening for network connections with sudo lsof -a -c httpd -i -sTCP:LISTEN $ sudo lsof -a -c httpd -i -sTCP:LISTENĬOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME If there are no "httpd" processes listed, Apache is not running, and you'll need to troubleshoot further to find out whether it's not starting at all, or starting and getting a fatal error. If bypassing the name lookup doesn't work, check to see whether Apache ("httpd") is running with the command ps -ax | grep 'ttpd' $ ps -ax | grep 'ttpd'Ĥ8917 ? 0:00.62 /usr/sbin/httpd -D FOREGROUNDĤ8924 ? 0:00.02 /usr/sbin/httpd -D FOREGROUNDĤ8927 ? 0:00.01 /usr/sbin/httpd -D FOREGROUND Do not change this entry.Īlso, try bypassing the name lookup by trying to reach " " and " If those work, Apache is running and "localhost" lookup is the reason you're getting errors. # localhost is used to configure the loopback interface
If this is the problem, check your /etc/hosts file it should contain at least this: # (It's ok if it lists additional addresses like "fe80:1::1".) This has nothing to do with Apache. If the response doesn't list at least the addresses "::1" and "127.0.0.1", something is terribly wrong. So, first verify that "localhost" is being properly resolved with the command dscacheutil -q host -a name localhost - it should look like this: $ dscacheutil -q host -a name localhost
We’re having trouble finding the site.") sounds like Firefox having trouble looking up the address for the name "localhost", which is really weird because "localhost" is pretty much built into the operating system. You need to do some troubleshooting to find out what's wrong.
0 kommentar(er)
