Server Version#:v1.42.2.10156-f737b826c
Player Version#:
For at least a couple of days now, I’ve been having trouble accessing my Plex library from outside my network. The problem is simply that I can’t access it. I’ve restarted the server, logged out of the mobile and tablet apps, but it doesn’t work. Even when I enable remote access, it deactivates itself after a few seconds or when I reload the page.
New data: From the intranet, I can’t access the library with the Edge browser, neither using the server’s IP address nor through plex.tv. I can access it from Safari. The app works on the intranet, but not outside of it.
Looking through your logs I see that your Synology NAS has two Ethernet connections.
That does not work for Plex a lot of the time because Plex can send on one adapter, but receive on the other adapter, which means Plex does not receive the reply on the adapter that sent the message.
To correct that, open DSM Control Panel > Network > Network Interface > Create > Create Bond and then select the two adapters and bond them together into a single adapter/IP Address.
Also, go to Plex Settings > Server > Network > Preferred network interface and set it to the Bonded connection you just created. Click on Save Changes.
With a little luck, you should not have any more issues connecting to the server.
Although you may need to review the Privacy & Security settings in Microsoft Edge if you are still unable to connect using Edge.
I followed the steps, but it’s still not working. I restarted Plex just in case, but it still doesn’t work outside the intranet.
I’ve attached the new logs, in case they’re helpful.
@sw9f9qh64p@privaterelay.appleid.com
I looked at your Plex.tv account
Your server is trying to publish itself (make remote access available) but the port forwarding from your modem/router → the Syno is not working.
I attempted to open the connection manually as a test. I unfortunately confirm your PMS is not “reachable” on the published port (32400)
Here you can see PMS asking to be tested (reachable) and getting a FALSE (:0) response from Plex.tv
Nov 27, 2025 22:25:21.972 [140058720918328] DEBUG - Completed: [192.168.2.237:63288] 200 PUT /myplex/refreshReachability (6 live) #388 TLS GZIP 383ms 327 bytes (pipelined: 2)
Nov 27, 2025 22:25:22.088 [140058723027768] DEBUG - [EventSourceClient/pubsub/192.46.236.7:443] EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="d847325b-1ed9-4808-a00a-c9ec569e351b" connectivity="0" command="notifyConnectivity"/>'
Nov 27, 2025 22:25:22.088 [140058723027768] DEBUG - [EventSourceClient/pubsub/192.46.236.7:443] PubSub: Got notified of reachability for async identifier d847325b-1ed9-4808-a00a-c9ec569e351b: 0 for :0 (responded in 116 ms)
Nov 27, 2025 22:25:22.088 [140058723027768] DEBUG - [EventSourceClient/pubsub/192.46.236.7:443] MyPlex: reachability check - current mapping state: 'Mapped - Publishing'.
Nov 27, 2025 22:25:22.088 [140058723027768] DEBUG - [EventSourceClient/pubsub/192.46.236.7:443] MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.
Check the port forwarding in your modem/router and confirm you’re forwarding port 32400/tcp to your Syno’s port 32400/tcp
Just to follow up on what @ChuckPa stated above, after you bonded the connection your Port Forwarding rules would have changed and that may explain why your server is now unreachable.
You do need to correct the port forwarding using the bonded connection now.
You keep mentioning an intranet, is this part of a company network and if so, have all of the appropriate ports for Plex been opened through the firewall?
Problem solved! Today I was able to access the router and forward the port. It seems to have worked. What I don’t understand is why it failed a few days ago when it’s been working fine for a long time, and I hadn’t touched anything. Thank you so much for everything.
Your router may have suffered from DNS cache corruption which can throw a spanner in the works in the strangest ways sometimes.
It is unknown why this occurs, not even the experts in the field know why it happens, but it does.
Some folks can be affected almost daily, while others may not see it for years at a time.
The easiest solution is to reboot the modem/router and everything connected to it, that will clear the cache in most cases.
Also, most routers will do a refresh after you make a settings change and that can also clear the DNS cache.
In any case, I’m glad you were able to solve the issue.
Happy Plexing! 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
