Losing my mind with port forwarding not working.
 

I configured my hub 5 to forward ports for my Plex and for my web server, and 'yougetsignal' and other internet port checkers confirm that the port is open on my virgin IP address, but any attempt to actually use the port fails.

I created a basic hello world nodejs app to display a simple web page on port 16565, and I set port forwarding in the router. Yougetsignal says the port is open, but trying to connect to it with a browser returns nothing.

In my local network, if I browse from my laptop to <server local IP>:16565 I see my hello world website.

I've installed ufw on my web server (where nodejs app is) and it allows traffic on 16565.

Looking at the logs on the server, I don't see the external connection attempt hitting the application layer, something must be blocking this traffic.

My local IP is defined as static in the hub 5. My virgin 82. IP address does not change and is the same on 'whatismyip' as shown in the router info page.

Re: Losing my mind with port forwarding not working.
 

What does canyouseeme.org tell you ?

Re: Losing my mind with port forwarding not working.
 

It says:

Success: I can see your service on 82.xx.xx.xxx on port (16565)
Your ISP is not blocking port 16565

If I browse to http://82.xx.xx.xxx:16565 (it's a basic no ssl test website), I get nothing back, no response, just spins.

In my home network, from another computer http://82.xx.xx.xxx:16565 actually works. From my guest network (virgin hub 5 guest network), I get the same problem as from externally.

Also, "sudo ufw status" shows on my server:

16565/tcp ALLOW Anywhere
16565/udp ALLOW Anywhere

Re: Losing my mind with port forwarding not working.
 

This is a failure of Hairpin NAT (NAT Loopback). Hairpinning means when a router receives a packet from LAN addressed to its own WAN IP, it should loop the packet back into the LAN and forward it to the correct internal host - but the hub does not properly support hairpinning. The solution is to put the hub into modem mode, use a router which supports Hairpin NAT and set up your port forward on the new router.

Re: Losing my mind with port forwarding not working.
 

Thanks, so the solution is buy another router, when I just need my virgin to do one thing that is advertised as being able to do. I was afraid this would be the answer :-(.

Though I'm not really bothered if a device on my guest network goes out onto the internet only to return via the external virgin IP to access a device on the main network. Speed is not an issue here. What I want is external devices to be able to access the site I'm hosting.

Re: Losing my mind with port forwarding not working.
 

No, the solution is not to try and do things in a weird way.
Your service is available externally to any other users, you verified that.
If you want to connect to it internally just use the internal IP, it makes no sense trying to route packets out to a router and back in again.

Re: Losing my mind with port forwarding not working.
 

No hang on, it’s not completely clear what the situation is here.

Tell me if I have this right.

You have a device running a service which responds on port 16565. Internally it is on an IP address of, say, 192.168.0.100, and if from within your internal network, if you browse to that address and port it works, yes?

Now you have set up port forwarding to it from your public address of, say, a.b.c.d, and from somewhere outside your house, if you browse to a.b.c.d:16565 it also works?

Have I got it right up to now?

But, if you browse to a.b.c.d:16565 from within your house it doesn’t work? Again is that right?

If all the answers to the above are yes; then it is exactly as ‘gunner45’ says; it’s due to the lack of support for NAT loopback in the Hub 5 and there is absolutely nothing you can do about it.

If so, as Paul says, stop complicating the situation.