Keep losing Remote Access

Plex Media Server Remote Access
,
1

Server Version#: 1.43.0.10492

Plex Media Server Logs_2026-02-19_17-32-42.zip (6.3 MB)

Player Version#: Don’t know, tend to play through Sonos or Symfonium
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

My Plex servers have been running without problem for many years. Teo weeks ago they lost remote access and the message “Not available outside your network” appearing.

I did not change anything about my Plex, Network or router set up. I have followed all of the guidance to no avail.

Yesterday and today I completely rebooted my entire set up. On both occasions remote access was stable for about 5 hours. I tested and was able to play music without problem. Remote access has now dropped. When I try to retry to connect, connection appears to work for a very short time and then drops again.

I wrote down all the details from the Plex remote access. Nothing has changed. I double checked that the manual port forwarding rules matched. They did and still do.

I checked on canyouseeme.org that my ports were visible. They were and still remain so.

I hope I have attached the logs correctly, my first time of doing so.

I can’t see what it preventing this from working.

2

Your server log has a bunch of warning that say (Could not resolve host: plex.tv)

I know you mentioned that you had not changed anything but possibly your ISP did.

First thing I would try using a different DNS like Google DNS or Cloudflare Public DNS

3

Thanks for that. I’ve gone with GoogleDNS. Rebooted and seems to be working at present but will keep an eye on it for now. Any problems I’ll report back with logs!!!

Thanks for your help.

4

Ok, that didn’t last. Remote access stayed up for about 90 minutes. Then back to previous state- not available outside your network

Log attached.

Plex Media Server Logs_2026-02-19_20-41-00.zip (5.7 MB)

5

From your logs:

Feb 19, 2026 18:36:22.589 [140361978215056] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
Feb 19, 2026 18:36:29.822 [140361970871096] WARN - MyPlex: attempted a reachability check but we're not yet online.
Feb 19, 2026 18:53:54.326 [140361851419448] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.1.226 to 192.168.1.255: Network unreachable
Feb 19, 2026 18:54:56.630 [140361881381688] WARN - [HttpClient/HCl#71] HTTP error requesting GET https://v4.plex.tv/pms/:/ip (6, Couldn't resolve host name) (Could not resolve host: v4.plex.tv)
Feb 19, 2026 18:54:56.630 [140361883491128] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6):

The error messages seem to indicate a local network issue, but that could also be an issue with your ISP.

It might be worth checking the service status with your ISP, perhaps they are experiencing some sort of issue.

It is also worth checking your own network equipment, you may be seeing issues that you are not aware of.

1 Like
6

Hi,

Thanks for that. I restored my router to factory settings. I also removed Symonium, which is a really great music player but doesn’t seem to integrate well with Plex.

Now I’ve got “Fully accessible outside your network”.

Attaching logs so you can check if things are looking any better!!!

Thanks for your help.

Plex Media Server Logs_2026-02-20_09-50-16.zip (3.9 MB)

7

I am still seeing the same set of errors in your logs. I suspect you may still have issues with Remote Access failing again.

This error:

Feb 19, 2026 18:53:54.326 [140361851419448] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.1.226 to 192.168.1.255: Network unreachable

makes me think you may have an issue with your router. That may be firmware related or it may be hardware related or I could be off base without a lot more information.

If you happen to have another router handy, I would recommend swapping it for your current router and see if the issue persists.

I am also seeing some badly named TV Show episodes for Doctor Who, which you should address.

I highly recommend using FileBot to automatically rename and organise your files with.

Cost is $6.00 USD for one year or $48.00 USD for a lifetime license.

Well worth the money IMHO.

You should follow the Plex naming guidelines in any case.
Your Media | Plex Support

8

Thanks for that.

The issue you point out is dated 19tth February- the items I listed were actioned this morning, 20th February. Four hours later I still have remote access which I have tested away from home- I will keep monitoring to see if it stays stable.

Thanks for the recommendation for FileBot. I do not use Plex for remote access of films or television programmes, they are for personal use at home. I suspect the items badly named are exclusive items which are not part of the main series, so as long as I know what they are, I’m happy for them to remain as they are.

9

The errors I see in your second set of logs start at 8:39 to around 8:42 and they are similar to the errors found in your earlier set of logs.

Feb 20, 2026 08:39:52.083 [140497938795320] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.1.226 to 192.168.1.255: Network unreachable
Feb 20, 2026 08:40:48.058 [140497968589624] WARN - [HttpClient/HCl#51] HTTP error requesting GET https://v4.plex.tv/pms/:/ip (6, Couldn't resolve host name) (Could not resolve host: v4.plex.tv)
Feb 20, 2026 08:40:48.058 [140497913613112] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6): 
Feb 20, 2026 08:41:33.074 [140497959922488] WARN - MyPlex: Updating device connections failed, retrying in 40 seconds.
Feb 20, 2026 08:42:17.523 [140497947265848] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-x86_64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:261:33 in function 'send_to']

Note: httpCode=-6 indicates a DNS error, usually a corrupted cache.

Keep an eye on things and if it fails again, at least you have some direction to follow up on.

10

It was up and running for about 23 hours. Played a 40 track playlist without interruption.

Then goes down and won’t connect again.

Not sure I even have the knowledge or experience to even know what to do now!!!

Plex Media Server Logs_2026-02-22_00-37-13.zip (120.9 KB)

11

Thanks for the Western Digital Logs.

The logs seem to indicate that you have just installed Plex on it recently (Feb 19) and there is only a single server log that does not show a whole lot.

Feb 19, 2026 23:13:47.024 [548032205024] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
Feb 19, 2026 23:13:48.989 [548032205024] WARN - [CERT] TLS connection from 192.168.1.226:54688 came in with unrecognized plex.direct SNI name '192-168-1-155.c568d9618e8240d5bf55e2ffa62e6d4b.plex.direct'; using installed plex.direct cert
Feb 19, 2026 23:52:20.548 [547630116920] ERROR - [Time] Date looks invalid: 2002--1--1

It seems that Plex was unable to update the certificate, which is most likely caused by the time/date not being set correctly on the WD.

The rest of the log is filled with database warnings about slow transactions which is not that surprising, given the quad core ARM processor and the new installation.

If you can, provide your Synology logs, they may contain more information for us to go on.

Grab your Synology server logs by opening File Station on the NAS and then navigate to: /PlexMediaServer/AppData/Plex Media Server.

Right click on the logs folder and select Compress to logs.zip

Attach the logs.zip file to your post, thanks.

If you are unable to connect to the Synology NAS at all, then I would suggest that you look at replacing the modem/router.

If you have any friends that have a spare modem/router handy or have good networking skills, maybe you could borrow a modem/router for some testing or their networking knowledge at least.

Failing that, contact your ISP and ask them to do a full diagnosis on your line and the modem/router in particular and if needed, ask for assistance in setting up your network properly.

They should have the tools needed to determine any faults that may exist and I am confident that they would at least be able to get your network configured to a working state.

Keep in mind, that the above is pure guess work at this point, I simply do not have enough information to determine the true cause of your issue/s at all.

12

Sorry, that was my naivety. I didn’t realise that the logs were separate- the Synology log should be attached now.

Yes, I did reinstall the WD setup yesterday.

Plex Media Server Logs_2026-02-22_09-33-52.zip (7.4 MB)

13

The IP of the Synology changed breaking the port forward rule. This indicates that you have not properly setup DHCP reservation for the Synology to always receive the same IP when the router reboots/resets/updates. You will need to update your port forward rule to point to the new ip.

Current Feb 22, 2026 00:12:09.604
Detected primary interface: 192.168.1.195
 Network interfaces:
  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
  * 3 eth0 (192.168.1.195) (00-11-32-F5-82-E3) (loopback: 0)

Previously Feb 20, 2026 08:37:42.063
Detected primary interface: 192.168.1.226
Network interfaces:
 * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
 * 3 eth0 (192.168.1.226) (00-11-32-F5-82-E3) (loopback: 0)
14

Thank you!

Think I’ve set the DHCP reservation properly now. But at least I know what to check next time.

15

Ok, so I’ve made sure the IP address for the Synology NAS is static, and I’ve just double checked. The port forwarding rules are correct.

I’ve confirmed the same for the WD NAS.

And the remote connection has been lost again.

Plex Media Server Logs_2026-02-22_16-09-48.zip (7.0 MB)

16

Network went unreachable (internet). It was still trying to reconnect when you dumped the logs. Did it recover?

17

Sorry, is this any better.

Plex Media Server Logs_2026-02-22_20-12-34.zip (4.9 MB)

18

@pl_5309
Well spotted, I think you are on to something there.

@Keith-Andrews
From your logs:

Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Got notification of changed network (first change: 1)
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Quick dispatch of network change.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Creating new service.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Got notification of changed network (first change: 1)
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Quick dispatch of network change.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Creating new service.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Got notification of changed network (first change: 1)
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Quick dispatch of network change.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Creating new service.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Got notification of changed network (first change: 1)
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Quick dispatch of network change.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Creating new service.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Got notification of changed network (first change: 1)
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Quick dispatch of network change.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Creating new service.
Feb 22, 2026 20:10:45.612 [140044148198032] DEBUG - NetworkService: Got notification of changed network (first change: 1)

We see a whole bunch of changed network warnings. Something definitely does not add up here.

Check your Ethernet cable and make sure there are no intermittent breaks in the cable anywhere and it has good clean connections at both ends.

If in doubt, change the cable for a known good cable and then monitor the connection to your NAS.

Try resetting the network settings on the Synology NAS and make sure your Ethernet cable is plugged into port 1 on the back of the NAS (it should be).

Note: You only want to perform a Mode 1 reset and NOT a Mode 2 reset.

Follow the instructions carefully.