![]() ![]() One common web server issue is directory listing. With this feature visitors to your website can still access your website at and you do not need to worry about port 80 being blocked.Misconfigured or default configuration on web servers may lead to a number of issues that could aid malicious hackers in their attacks. I would recommend that you sign up for a free dynamic DNS service with Dynu( ) and use their port forwarding function to host your website on a port other than port 80. Posted: Thu 18 Jun '15 1:33 Post subject: host your website on an alternative port Then go to Manage Host -> Modify and edit it with DNS Host (A) and insert the WAN IP (very similar to GoDaddy). Sign up with an email, go to Manage Hosts -> Add a Host and select a host name. This eliminates configuration issues with GoDaddy. The idea with this is to eliminate the possibility of a XAMPP config issue stopping the server from responding.ī) Try a free dynamic DNS service such as. Just make sure to select "manual" start up during install (so there aren't any conflicts later with XAMPP - and remember to disable XAMPP during testing so there are no port 80 conflicts). It takes no configuration other than selecting a language after install and runs by default on port 80. ![]() This takes about 1 minute to set up on Windows (it also supports Linux and Mac). * Double check your XAMPP configuration (make sure it's listening on 80 and not 8080).Īs two additional steps for troubleshooting, you may want to:Ī) Try a different server for quick testing such as the free version of Abyss. * I would double check firewall settings, including turning it completely off forth the duration of testing. (This happened to me with a Netgear router - it reassigned the webserver a different IP than it initially had and broke port forwarding, despite the IP being "assigned" to that server). * Make sure the Netgear router didn't change the webserver internal IP while you weren't looking. Assuming things are configured correctly, a smartphone with a browser and any home computer (using the external IP address or domain name in the browser) should be able to reach the site. * I would try testing from locations other than work. That is, type the IP directly into the browser address bar (e.x. * I would try to access the page directly by your outside (WAN) IP. This does not necessarily mean Comcast is blocking it. The external port checker states the port is closed most likely because no service is answering. I currently run a set up very close to yours at my home office (Comcast residential, Netgear routers) and it works fine. Unfortunately, its more likely that it is a configuration error or a firewall issue. It is unlikely that this is due to Comcast. Posted: Mon 03 Mar '14 8:03 Post subject: Port 80 still appears to be closed If you have the possibility to connect to the "internet" side of the router, then you could test from there. We had this issue in Colorado Springs and it only worked once we switched to a business connection.Īs there is no easy way to connect directly at the outside of the cable modem (without the Comcast network), you can only test the total solution. I would indeed suspect Comcast to be the problem. Posted: Sun 02 Mar '14 18:59 Post subject: I am pulling(what little I have left) hair out. Then I go to use an external port checker tool on my router and it states that port 80 is closed when contacting my WAN IP. They swear up and down that they don't block incoming traffic from port 80. I thought that maybe Comcast ISP was blocking port 80. However when I try and bring open the webpage from work it receives a connection time out and no web page is displayed. I can ping either the WAN address or the Domain name from work and it receives a reply no problem. I have taken my domain name from Godaddy and assigned the A-record to my WAN address. I have port forwarded port 80 to the static IP of my webserver machine in my netgear router configuration page. I have xampp 1.8.1 and can access the "It works" page from anywhere within my LAN. I have assigned a static IP address of 192.168.1.3 to the webserver. Port 80 and apache have been made exceptions in the firewall tab of the webserver. It is wired directly to my netgear router(WNR2000V3). I will try to be as thorough as possible explaining my setup. I can see my apache webserver within my LAN but not outside on the internet. Posted: Wed 19 Feb '14 18:46 Post subject: Port 80 still appears to be closed Topic: Port 80 still appears to be closed
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |