Reply

Issue connecting to web server

ashwinnair2011
Aspirant

Issue connecting to web server

Hi all,

   I'm having trouble connecting to my webserver externally. Here is everything I've done so far:

- I enabled remote management on a port 12900 via Advanced->Adv. Setup-> Remote Mgmt

- I've enabled dynamic dns using Advanced->Adv. Setup->Dynamic DNS. After this, browsing to the 'dyn. DNS host name' (on port 80) would take me to the router portal. So would https://{'dyn DNS host name'}:12900.

- I set up a webserver on my home network and configured 3 sites to be accessible on port 80, 9100 and 9101. I set up the firewall so that other machines on the network can access these sites.

- I then (tried to) enabled external access by going to Advanced->Adv. Setup->Port Forwarding & setting up 2 rules,

    - One rule to direct incoming traffic on port 9100-9101 to {local web server IP} port 9100-9110.

    - A second rule to direct traffic on port 80 to {local web server IP} port 80. I had to select 'HTTP service' since it doesn't let me set custom rules for 80 and 443.

 

Here is what is happening:

- pinging dynamic DNS host name resolves correctly.

- Inside my network, browsing to http://{dyn DNS host name} on port 80, 9100 or 9101 works correctly from local machine/phone.

- externaly, browsing to https://{dyn DNS host name}:12900 works and takes me to router administration page

- externally, browsing to http://{dyn DNS host name}:9100 or http://{dyn DNS host name}:9101 works.

- externally browsing to http://{dyn DNS host name} or http://{dyn DNS host name}:80 does not work

 

If I make another port binding (say 9102) to the port 80 site, it works externally. Only port 80 keeps failing!!

I've tried many many things but it refuses to work. Please help. 

Model: R8000|Nighthawk X6 AC3200 Smart WIFI Router
Message 1 of 7
antinode
Guru

Re: Issue connecting to web server

> - Inside my network, browsing to http://{dyn DNS host name} on port
> 80, 9100 or 9101 works correctly from local machine/phone.

   NAT loopback seems to be working.

> - externally browsing to http://{dyn DNS host name} or http://{dyn DNS
> host name}:80 does not work

> [...] Only port 80 keeps failing!!

   Does your ISP block port 80?  Some ISPs don't allow any servers.

Message 2 of 7
ashwinnair2011
Aspirant

Re: Issue connecting to web server

Yeah, that would do it, I suppose. Is there some way to work around this using some sort of router configuration?

Model: R8000|Nighthawk X6 AC3200 Smart WIFI Router
Message 3 of 7
antinode
Guru

Re: Issue connecting to web server

> Yeah, that would do it, I suppose. [...]

   Ask your ISP?  If they have such a policy, then it should be public
information (and may be in your (never-read-by-anyone) terms of
service).

> [...] Is there some way to work around this using some sort of router
> configuration?

   If your ISP blocks port 80, then the work-around is to use a
different port.  (Which seems to work.)  The disadvantage is that
clients need to specify the non-standard port number in their URLs.

Message 4 of 7
ashwinnair2011
Aspirant

Re: Issue connecting to web server

I had a loooong chat with them and made their 'backend team' all but swear on their mothers that they weren't blocking any ports. Turns out they only block outbound requests on port 25 and don't block inbound requests at all even though I've found cases of others who face the same problem with this provider. The ISP keep insisting it's a fault with the router even though I'm using my own.

 

ISP telling someone else what they told me: https://yescrowd.optus.com.au/t5/Broadband-Telephony/Ports-80-25-and-110-on-Cable/td-p/55920

Non-affiliated but reputable site stating that they do block 80: https://whirlpool.net.au/wiki/on_blockport

 

Don't know what to believe. Is there any way to confirm this? My router logs, which aren't particularly verbose, don't have any entries when I try to connect via port 80 externally. Internally, port 80 works and I see it in the logs. Externally, the other configured ports work and I see related entries in the logs.

 

I'm currently working around this issue by getting my domain to point to a fixed port and it works but I'm not a fan of this method since it displays the redirected IP & port in the address bar. They've got an option to 'mask' this but they do this by putting the underlying site in a frame.

Model: R8000|Nighthawk X6 AC3200 Smart WIFI Router
Message 5 of 7
antinode
Guru

Re: Issue connecting to web server

> [...] Don't know what to believe. Is there any way to confirm this?
> [...]

   Obtain (beg/borrow/buy/steal) a different router, and run some
experiments?

   If you cascade two routers (a LAN port of router-A feeds the
WAN/Internet port of router-B) then you should be able to try a web
browser (or equivalent) on the LAN side of router-A (the WAN/Internet
side of router-B), with the web server on the LAN side of router-B.  If
that works, but it fails when the ISP is connected to the WAN/Internet
side of router-B, then that would suggest that router-B works, and the
ISP is a lying sack of some material or other.  (Or misinformed.)

Message 6 of 7
ashwinnair2011
Aspirant

Re: Issue connecting to web server

Okay. I suppose there's no other way really. Thanks for all your help.

Message 7 of 7
Top Contributors
Discussion stats
  • 6 replies
  • 777 views
  • 1 kudo
  • 2 in conversation
Announcements

Orbi WiFi 6E