NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

pipechess's avatar
pipechess
Star
Apr 25, 2021

[RBR40] Port Forwarding not working for Port 80

Good Evening,

 

I have a Orbi Mesh Router with 2 satellites in my house.

In my network I have multiple servers, one of them being  a webserver.
To enable public access I enabled port 80 in PORTFOWARDING to the servers IP address.

When trying to connect internally to the server I get the expected website displayed. However when trying 
externally it will not connect. 

 

Couole of things I made sure:

  1. The domain name points to the correct IP address (my Modem). 
  2. Portforwarding points to the right internal IP address
  3. Server is listening to the correct PORT 80
  4. UPNP is switched off

THings I tried:

  1. I let my webserver listen to port 81
  2. put a port forwarding rule in for port 81

This works. So port 81 is reachable externally. But not when trying port 80.

Any ideas whats going on or what I could try?

8 Replies

Sort By
  • CrimpOn's avatar
    CrimpOn
    Guru
    Apr 25, 2021
    pipechess wrote:

    This works. So port 81 is reachable externally. But not when trying port 80.

    I am unable to reproduce the problem.  I forwarded port 80 to my Pi-hole web portal. Disconnected from Orbi to use mobile LTE connection. Opened http://<my public IP address>/admin/ and up came the Pi-hole interface.

     

    I did not select from the drop down menu of services (starting with FTP at the top. HTTP is the second one.) and instead created a custom rule using port 80.  I doubt Netgear would have included HTTP on the list of services and not allow forwarding port 80.

     

    Since port 81 forwarded correctly for you, it is pretty clear that there is not a router in front of the Orbi.

     

    I have no clue why it didn't work for you. Certainly does for me.

    • pipechess's avatar
      pipechess
      Star
      Apr 25, 2021

      Yeah,

      the odd thing is that this worked a couple months ago.

      I don't know if this is a firmware bug after the latest update and/or if the router now reserves port 80 for internal puposes?

      This is driving me nuts. My entire server infrstructure is down because of this.....

      • CrimpOn's avatar
        CrimpOn
        Guru
        Apr 25, 2021
        pipechess wrote:

        the odd thing is that this worked a couple months ago.
        I don't know if this is a firmware bug after the latest update and/or if the router now reserves port 80 for internal puposes?
        This is driving me nuts. My entire server infrstructure is down because of this.....

        My Orbi firmware is v2.7.2.104.  Port 80 on the LAN side is used for the Orbi web interface, but that is entirely separate from forwarding port 80 from the WAN side to a specific device. The LAN side can any any number of devices listening on port 80. (I have 2 Pi-holes which are listening on a total of 4 interfaces.)

         

        Did you try forwarding using both the pre-defined (drop down menu) HTTP port and defining a custom rule for port 80 TCP?