Use netstat -anp to find out what, then stop it. Some other program is already listening on port 80. ![]() Address already in use: make_sock: could not bind to address 0.0.0.0:80 As above, this can occur in the debian nf file, especially after an upgrade. This seems to happen when one is using multiple virtual host configuration files and doesn't understand that you only need to define a particular NameVirtualHost line once. Apache will ignore the second directive and use the first defined NameVirtualHost line, though. Multiple NameVirtualHost lines will yield a "NameVirtualHost *:80 has no VirtualHosts" warning. Follow up warnings and errors reported by Apache NameVirtualHost *:80 has no VirtualHosts If there is no entry there, it is a good indicator that Apache isn't receiving any request. If the request reached Apache you should see an entry in the error log. The latter is more likely to result in a HTTP response of 404 or 500. "Could not connect" suggests a basic IP connectivity problem rather than an Apache vhost configuration problem. Update: Check the Apache error logs (all of them) As Malfist pointed out in a comment: if the router supports NAT-reflection, this is not be necessary. etc/hosts or C:\WINDOWS\system32\drivers\etc\hosts). Lastly, remember that if you are testing this from within your LAN you need a different IP-address for you can add 192.168.10.151 to your hosts file (e.g. Some ISPs block inbound HTTP connections. Then check that your ISP's Terms and Conditions allow for you to run a HTTP service. Then check that your router has port forwarding configured so that requests arriving on port 80 at the external interface are forwarded to port 80 at your server's private IP address. The Apache error log may have more information.įirst use nslookup or dig or host to check that points at the static external IP-address of your router. No listening sockets available, shutting down (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 NameVirtualHost *:80 has no VirtualHostsĪpache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName NameVirtualHost 192.168.10.151:80 has no VirtualHosts * Restarting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName Restarting Apache results in this: sudo /etc/init.d/apache2 restart ![]() ![]() My conf.d/nf is: NameVirtualHost 192.168.10.151:80ĮrrorLog /media/BigDisk/CustomLog /media/BigDisk/combinedĪnd the site was enabled using a2ensite and apache reloaded without any warnings or errors, but when I go to I don't get anything ("Opps! Google Chrome could not connect."). I can't get Virtual Hosts to work though. However, I want to use the same server/ip to show more than one website. I have a domain name that is linked to my ip address at home.
0 Comments
Leave a Reply. |