18-08-2026 06:28 PM
I have a Synology NAS which I access from outside the home over HTTPS. The SSL certificate is provided by Let's Encrypt, and to renew the certificate, port 80 must be open and forwarded to the NAS. All was well until today, when the certificate expired and the NAS attempted to renew it.
It all worked fine with my Plusnet router, but forwarding port 80 does not work with the EE Hub Manager. The NAS uses UPnP to set port forwarding rules on the router. This works for all my other required ports, but it fails to set up and verify forwarding of port 80. If I go to the router's UI and forward port 80 manually, it is then listed along with all the other ports as a forwarded port, but it doesn't actually get forwarded. For example, if I go to an open port check tool, it says port 80 is closed.
There are some other threads on this forum complaining about this, but not all have the same router, and I couldn't find a solution.
I'm not going to do a factory reset, since I've only recently set up the router from factory condition, and I know from experience that a factory reset never solves anything, and it just wastes a couple of hours while you have to set everything up all over again.
Unbelievably, I telephoned EE support and was told that they do not provide technical support for port forwarding! This is EE, which is part of BT. I expected first class technical support, not this.
Does anyone know how to get port forwarding of port 80 working on a EE Hub Manager? Product code SH31B.
Thanks in advance.
21-08-2026 09:20 AM
Yep, it certainly does, and squarely points the finger of blame at the port forwarding. Thanks for testing 🙂
I notice your subnet is non-default. Have you changed the IP of the hub out of interest?
21-08-2026 09:30 AM
Yes, I changed the IP address of the router. It is at a second home, but it's part of a single Tailscale network with my main home. In order to use Tailscale subnet routers, the two networks routers have to have different IP address ranges.