Remote access port issue - only 32400 is working?

[snarble33]

Server Version#: 1.32.5.7516 (x64)
Player Version#: 4.108.0

I have Plex Server installed on a Windows 11 PC. When I provide 32400 as the remote access port in “Manually specify public port” everything is working fine. However when I change that port to other I’ve set rules for in my firewall and router, I continually receive the " Not available outside your network" after several seconds.

The port on my AT&T HUMAX BGW320-500 router for forwarding shows:

Using an online port checker to see if any of those ports are open, only 32400 returns as open.

Testing in command prompt using “netsh firewall show state” I see:

Firewall status:
-------------------------------------------------------------------
Profile                           = Standard
Operational mode                  = Enable
Exception mode                    = Enable
Multicast/broadcast response mode = Enable
Notification mode                 = Enable
Group policy version              = Windows Defender Firewall
Remote admin mode                 = Disable

Ports currently open on all network interfaces:
Port   Protocol  Version  Program
-------------------------------------------------------------------
28076  TCP       Any      (null)
36927  TCP       Any      (null)
32400  TCP       Any      (null)

The port is definitely open on my local PC as shown above, and forwarded on my router. I have been wrestling with this issue for several days and not understanding what is preventing me from using one of the other two ports there (either 28076 or 36927 - or really any other port between 20k and 50k)

Would appreciate any additional input on this issue, thank you for any help.

[Krazeh]

Plex always works internally on port 32400. If you want to use a different port for external connections you need to have your router forward packets from that port externally to 32400 internally.

[snarble33]

When you mention forwarding packets in the router, can you provide more information on this? Just curious are you referring to changing the forwarding similar to this in the screenshot below?

If so I did try this and it still shows as closed on port checkers, and also not working in Plex. If there is a different screen or configuration I would be interested in knowing, thank you.

[Krazeh]

@snarble33

When you mention forwarding packets in the router, can you provide more information on this?

You should take a look through Troubleshooting Remote Access | Plex Support.

[snarble33]

Hi Krazeh, I neglected to mention that I did already walk through that document several times. Running a search on that page using the word ‘packet’, it is not referenced there.

Checking is there a specific portion of that you are referring to? Specifically about the forwarding packets.

[Krazeh]

It’s the bit about port forwarding.

[snarble33]

Thank you. Yes I did review that, I believe I attached screenshots of my port forwarding setup previously. If there is anything specific that you are commenting about that I missed I can help provide more screenshots or clarification. Thank you.

[Krazeh]

@snarble33

If there is anything specific that you are commenting about that I missed I can help provide more screenshots or clarification.

I don’t know the specifics of your router so can’t tell you what might be right or wrong. But clearly you’ve missed something otherwise it would be working. I can only suggest you look at any manuals or help guides you have for your router or contact your ISP for assistance.

[snarble33]

I am working with my ISP to ask more questions on this. In the meantime if anyone else has more input for me, who may also be an AT&T customer using fiber and/or this modem, would appreciate additional input.

[phoneguyinpgh]

Why are you using those other ports when 32400 is working fine?? Are you operating more than one Plex server??

[JaysPlex]

The internal port for every server needs to be 32400. You cannot change this

It’s only the external port that needs to be different for each

As a basic example

TCP is all you need. UDP is not necessary

[FordGuy61]

@snarble33

I am working with my ISP to ask more questions on this. In the meantime if anyone else has more input for me, who may also be an AT&T customer using fiber and/or this modem, would appreciate additional input.

Port forwarding on AT&T with a BGW 320.

The post below uses 32400 for the external port. If you want to use a different port, change the Global Port Range.

As @JaysPlex mentions, Host Port is always 32400.

Only TCP is required. Forwarding UDP neither hurts nor helps.

Changed ISP - No Remote Access with AT&T BGW 320-500

Server Version#:WD Mycloud Home Player Version#:? I switched to AT&T from Verizon. I never had to do anything with Verizon. All worked fine. Now that I switched to AT&T I took a trip and could not access any of my content remotely as I could with Verizon. I am truly overwhelmed and everything I try to do send me to another page with more information and nothing is straight forward. One thing tells me about static ip, put wants me to do it in the router, and then there is something about p…

[snarble33]

I did some more testing on my local PC.

If I run Port Listener on my PC ( RJL Software - Software - Utility - Port Listener - Download ) and enter the port I am looking to configure, in this case 36927 - and then check if the port is open using an online port checker such as Open Port Check Tool - Test Port Forwarding on Your Router – it shows open.

I stopped the port listener, then launched Plex again and navigated to Settings > Remote Access and enter the same port 36927. It returns " Not available outside your network".

The Public IP in the Plex screen for the Remote Access setup shows the exact same public IP in the online port checker. It’s the same port.

I am not understanding why Plex continues to throw the error considering the check above - what portion is missing that would cause this?

As mentioned I do have a forwarding rule in my router:

I’ve tried it both with the internal port at 32400 and as 36927 but neither change the behavior.

[tom80H]

You’re still pointing your port forward to an internal port that’s different from 32400. The internal port MUST BE 32400 – you cannot change that.

[snarble33]

Yes, I edited my post and the screenshot and re-added it like 6 seconds before you responded. It’s updated above.

It is still the same outcome however.

[tom80H]

Can you take a look at this troubleshooting guide?
There might be some other hint you haven’t tried yet – if it’s still not working we’ll need the individual findings from those checks (e.g. do you get a publicly routable IPv4 address from your ISP, is your router’s public IP address accessible on the specific public/external port from outside your home network…).

The Basics of Remote Access Troubleshooting

When it comes to remote access, there’s a lot of different factors which can impact your setup. Some are under your own control, others not so much. First off… there’s a dedicated support article on troubleshooting your remote access. I strongly recommend you have a look at that. Find below some additional remarks on how to troubleshoot your remote access setup. Review your internet access / remote access configuration It’s good practice to review if Plex gets the correct public IP address…

[FordGuy61]

@snarble33

Did you change routers or do you have multiple routers?

The Port Forwarding screenshot you posted earlier today is different than in your original post. It does not look like an AT&T device. Also, the new screenshot shows the 192.168.0.x subnet. AT&T Fiber (at least on my BGW 320) uses the 192.168.1.x subnet.

[snarble33]

@FordGuy61 - yes, I neglected to add the most recent update on this so apologies for missing this.

Through troubleshooting further with AT&T tech support on multiple calls, they forwarded me to a 3rd party team that supports AT&T customers when apparently they can’t resolve an issue. That team informed me I would need to get a 3rd party router to handle my WiFi and routing which has worked for other customers running into port forwarding issues.

I bought a TP-Link AX11000 and have it configured in IP passthrough mode per the link here (steps in second post): https://community.ui.com/questions/BGW320-500-Bridge-Mode-and-or-IP-Passthrough-Question/99786f13-1f76-46dd-9801-7102fd1d44d7

Everything is working, all my wired devices and WiFi are connected to the new router and working without issue. I added the ports in the forwarding rules on my TP-Link AX11000, however they’re still showing as closed.

Per the article linked: https://support.plex.tv/articles/200931138-troubleshooting-remote-access/

I enabled UPnP on the TP-Link AX11000 (since the AT&T BGW router does not allow this) - I see that my Deluge torrent client shows up in the UPnP client list in TP-Link (they have a panel that shows what’s using it at the moment and a refresh button, refreshing it endlessly shows no change) - Plex Server is running on my PC (same that Deluge is running on) and has the custom port entered in the Remote Access field. I’ve triggered it multiple times but it’s not going through UPnP.

I configured inbound and outbound TCP rules for the port in Windows Advanced Firewall. I also completely disabled my Windows Firewall (all three types) and tested and there was no change in behavior. As mentioned before running a netsh on the PC shows the two custom ports I am testing are open:

Ports currently open on all network interfaces:
Port Protocol Version Program

28076 TCP Any (null)
36927 TCP Any (null)

The ports are forwarded in the TP-Link router per the following:

The local IP on my machine does not change and is always 192.168.0.248. The machine also is added to the DHCP address reservation page, with the MAC ID and IP address linked (not attaching the screen of my MAC ID)

Port is applied in Plex:

I see the section about double NAT and recognize that my AT&T is publishing 192.168.1.xx and my TP-Link is 192.168.0.xx. However even with this configuration I am able to see that either of my custom ports can be shown as open when using Port Listener on my PC ( RJL Software - Software - Utility - Port Listener - Download ) - the port is accessible when checking online using an open port checker.

Sort of banging my head against the wall with this issue and about ready to give up but soldiering on and hoping to get some input from others on this community, since this is somehow isolated to Plex app and how it uses the port. Something must be missed here somewhere but it’s not clear, since I’m able to see that port open using other methods.

[FordGuy61]

@snarble33

That team informed me I would need to get a 3rd party router to handle my WiFi and routing which has worked for other customers running into port forwarding issues.

FWIW, I’m on AT&T Fiber in Texas. I have port forwarding working with a BGW 320-500. I did not need to add a second router, use passthrough/bridge mode, etc.

See this thread (also linked above): Changed ISP - No Remote Access with AT&T BGW 320-500

Those screenshots are from my BGW 320-500 and Plex Media Server running on my Windows 10 PC.

The post uses 32400 for the external port. If you want to use a different port, change the Global Port Range.

The Host Port is always 32400.

I loaded Plex on my PC to grab those screenshots. My real Plex server runs on a different external port.

[snarble33]

Thanks for that input @FordGuy61

On my side 32400 is open and working without issue. Plex is properly listening on that port and it shows as open.

However Plex is not properly routing any custom port entry to ‘listen’ on my PC for it to show as open.

Can anyone from Plex Support add more technical input on the flow when a custom port is entered into Plex ‘Manually Specify Public Port’ in Remote Access? What is supposed to happen and what else needs to be open or configured for this manual port?

I run a program such as Port Listener from RJL software on this same PC, that port is shown as open and accessible on the PC. There is some block with the Plex process here that isn’t clear. I’ve fully uninstalled and reinstalled Plex on my PC, I removed all Firewall rules and re-added them without any improvement.