|
I have set up a web server on port 80 and tested that it works locally. Several weeks ago I signed up for a dyndns hostname (the free service) and about a week ago I used the dyndns hostname to access the site and it was working (it was also successfully accessed by several other people). However, today I tried it again and it simply doesn't load the page (literally I see a blank page, it says "loading" for a while and then "done" but it's still a blank page). I tried telneting to the hostname (as well as straight to the IP) on port 80 and it disconnects after it times out i.e. it doesn't load anything. I have checked the following: - my server is up and running on port 80, - my IP address is indeed the one shown in the dyndns service page, - I have not made any changes to any firewalls/routers since last week (when it was working), - the dyndns service has not expired. Does anyone have any suggestions for what could be going wrong? Thanks.
(comments are locked)
|
|
What does the open port tool show? Did you remember to give your web server a fixed IP address on the LAN (as covered here)? Have you tried forwarding a different port, just in case your ISP has started blocking port 80/TCP? The open port tool result says that the attempted connection timed out, which "typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP". I know there's no firewall blocking it. Also, I have specifically configured the router to enable TCP/UDP on port 80. Checking the address of the web server on the LAN - it did indeed change! Previously it had been always been the same so I didn't realize that I have to explicitly fix it. Thank you for the help! To summarize: the solution is to give a fixed internal IP address to the web server.
(comments are locked)
|
