Local network unable to connect securely when using browser

Plex Media Server
1

Server Version#: Version 1.32.1.6999
Player Version#: Version 4.100.1

I’ve got a bit of an interesting issue here.

What doesn’t work

Trying to connect to my local Plex server via app.plex.tv through a browser or the desktop apps for Win/MacOS fail 95% of the time with the “Unable to connect to x securely” error. In the 5% chance it does go through, the success is intermittent, and Plex will show that it’s streaming to my router’s WAN (not LAN!!)

This WAN IP is the same regardless of which device I use.

What works

Connecting and streaming over iOS and AppleTV work great. Connecting from a different network (remote streaming) is also perfect. And connecting over the IP address of the server (ip-address:32400) works as well. All of these will show that it’s streaming to LAN.

I also set up a reverse proxy and routed to a subdomain - that works too.

My Setup

I have the server linked to my eero via Ethernet. All other devices are connected via wifi to the eero. The modem has wifi disabled for good measure.

I’ve done a ton of troubleshooting for the basics (UPnP on, port forwarding 32400 on router + modem, no VPN, no DNS software, etc.)

I’ve toggled on/off remote access, and encountered the same bug.

Secure connections is set to: Preferred

Has anyone else experienced this issue before, or has any ideas on where to begin debugging?

2

It is Linux or Docker on linux box? If docker have you told it to use the host networking?

1 Like
3

Thanks for the quick response.

I did some investigation, the tl;dr is:

  • While on local, plex in browser pings two IPs: docker subnet, which fails obviously, and public ip, which only resolves 5% of the time. The issue is exclusive to the plex app as other appsare connectable.
  • Outside of local, public ip resolves 100% of the time.

Upon further investigation, it appears that I am indeed using default networking (bridged). Switching it out to host networking resolved the issue.

Thanks!

1 Like
4

Following up on this again - is there any way to purge Plex of cached addresses (or at least, I think it’s cached)? It looks like it is still occasionally pinging an internal docker subnet (172.x) and internal (10.x), which would of course fail to resolve.

5

I am trying to see if one of our backend guys purge any old IP addresses associated with your server record

6

This done. can you try again. Might need to restart server.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.