topic Re: Open another port for HTTP in additon to port 80 in Broadband

Open another port for HTTP in additon to port 80

Martin3780 — Mon, 08 Jun 2026 10:58:09 GMT

This is one for the specialists! I have recently received a new FAST F5364-3 T8 TalkTalk router and I'm trying to connect my Synology NAS so I can access the NAS externally. The NAS uses default port 5000 and 5001 for HTTPS, so I need to open ports 5000 and 5001 in the router for an HTTP and HTTPS service, respectively. But the router forces all HTTP service connections to be port 80, and for HTTPS it has to be port 443. I am unable to open an additional port for HTTP or HTTPS.

I have been using an old TP-Link router which allows me to do exactly what I want to do. So why can't I do it with the latest TT router? Any suggestions?

Re: Open another port for HTTP in additon to port 80

fr8ys — Mon, 08 Jun 2026 11:11:49 GMT

Does this article help?

https://help-centre.talktalk.co.uk/Broadband/More_broadband_support/Set_up_port_forwarding

Re: Open another port for HTTP in additon to port 80

Martin3780 — Mon, 08 Jun 2026 11:56:11 GMT

Thanks. The instructions are exactly what I was doing, but when I get to opening a new HTTP port I can't use port 5000. It defaults to 80 and doesn't allow me to change it. I'm hoping there's a workaround or the new TT router is useless for me.

Re: Open another port for HTTP in additon to port 80

fr8ys — Mon, 08 Jun 2026 12:16:24 GMT

Unfortunately, support staff are no longer available here and this will require you contact TalkTalk directly as the forum is now peer to peer and this is something I am, on this occasion, unable to help you with.

Not sure if @KeithFrench can help, but if you are following the instructions, including the static IP then TalkTalk may well be your best way forward
Please see the link in my signature for ways to contact TalkTalk.

Re: Open another port for HTTP in additon to port 80

KeithFrench — Mon, 08 Jun 2026 12:26:37 GMT

Hi @Martin3780

Yes, I can help with that.

In the router, go to:-

Dashboard > Manage my devices > Manage Advanced Settings > Access Control > Port Forwarding. Then click Add Rule > Add Rules Manually

In the resulting screen, set a Custom Service Name to perhaps "5000HTTP" and the external & internal ports to 5000 and the Internal Host to the IP address of your NAS (This needs to be a DHCP Reserved IP address).

The repeat setting the Custom Service Name to perhaps "5001HTTPS" and the external & internal ports to 5001 and the Internal Host to the IP address of your NAS (This needs to be a DHCP Reserved IP address).

Re: Open another port for HTTP in additon to port 80

fr8ys — Mon, 08 Jun 2026 13:43:04 GMT

@KeithFrench thank you.

Re: Open another port for HTTP in additon to port 80

Martin3780 — Mon, 08 Jun 2026 14:50:54 GMT

Thanks everyone for your help. I've tried what you suggest Keith, but it doesn't work and I don't understand why. I'm not an expert at port forwarding but I am trying to replicate the exact settings I have in my old TP-Link router. In the old router I can specify an HTTP service for port 5000 and it all works OK with my NAS on a static IP. If I use the same in the TT router I cannot specify a service type because if I request an HTTP service, then the port defaults to 80 and cannot be changed. If I leave the service type blank and have internal and external ports set to 5000 and have the internal host set to my NAS IP address (as you recommended), then I cannot connect.

It feels like the TT router is not expecting an incoming HTTP request on port 5000 because there is no service type set.

It's possible to change the default port on my Synology NAS to 80 (HTTP) or 443 (HTTPS) and then but I am reluctant to do this because it may clash with something else that I don't know about.

I'll keep trying various combinations and see if I can find a way round it. It's frustrating!

Re: Open another port for HTTP in additon to port 80

KeithFrench — Mon, 08 Jun 2026 15:03:31 GMT

Exactly how are you testing this @Martin3780? If this is from a PC or other device connected locally to your router, using your router's Public (WAN) IP address, it will fail. This is because you are trying to use NAT Loopback, which TT routers block as a potential security risk. What you need to do is to use a smartphone, disconnect it from your router & use mobile data.

Re: Open another port for HTTP in additon to port 80

Martin3780 — Mon, 08 Jun 2026 15:25:48 GMT

Keith, Brilliant idea! I'll try this when I get a chance. My TP-link router doesn't have this problem, but I have been caught out by this security feature with TT routers in years gone by. I'm now kicking myself for not thinking of it!

Thanks,

Martin

Re: Open another port for HTTP in additon to port 80

KeithFrench — Mon, 08 Jun 2026 15:26:56 GMT

If it still does not work, I will test my rules tomorrow for you.

Re: Open another port for HTTP in additon to port 80

Martin3780 — Wed, 10 Jun 2026 07:14:46 GMT

Keith,

It works! It was indeed a brilliant spot! Thanks. I can now see the NAS on my phone using mobile data. I've also set up my IP security cameras using port forwarding and they work too. The only problem now is that I cannot get to the router's log-in page remotely. I usually use my DDNS domain without a port number and the router admin log-in page appears....but with my TT router it just times out. Is this another TT security feature? Other routers I have had gave me a "Remote management" page in the advanced settings, but no such thing in the F5364. Any ideas? Do I need to open/forward another port?

Martin

Re: Open another port for HTTP in additon to port 80

KeithFrench — Wed, 10 Jun 2026 07:35:37 GMT

For security reasons it is impossible to mange TT routers remotely. They block all attempts to do so via incoming connections from their WAN link. The only acception to this is via TT's remote management suite.

The only way around this is to RDP into a PC on your local network and establish a browser connection from there to the router

Re: Open another port for HTTP in additon to port 80

Martin3780 — Wed, 10 Jun 2026 08:53:48 GMT

Thanks. I feared that TT have prevented remote router management. I wish they wouldn't do this. At the least TT should publish the rules to stop users wasting their time trying to get features to work that they have disabled. If it becomes a nuisance then the TT router will have to go and I'll buy my own. Thanks for all your help.

Martin