Server Version#: v.1.41.1.9057-af5eaea7a on DSM 7.2.2-72806
Player Version#: App
Good evening,
For the last 4 days I have not been able to access my PMS remotely via app (Android, LG webOS), but the web version is reachable without problems.
I have not changed anything in the settings of my router or plex server for a few months now.
Are there problems with the API of the app?
You turned off DEBUG logging. I can’t see anything that it’s trying to do but can clearly see the errors.
Your network configuration is not correct somewhere.
Oct 28, 2024 17:35:17.125 [139709596412728] INFO - [NSB] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:17.125 [139709596412728] ERROR - [NSB] Error in browser handle read: 125 (Operation canceled) socket=-1
Oct 28, 2024 17:35:17.225 [139709596412728] INFO - [NSB] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:17.225 [139709596412728] ERROR - [NSB] Error in browser handle read: 125 (Operation canceled) socket=-1
Oct 28, 2024 17:35:17.325 [139709653056312] WARN - NetworkServiceBrowser: Error sending out discover packet from 0.0.0.0 to 239.255.255.250: Network unreachable
Oct 28, 2024 17:35:17.325 [139709596412728] INFO - [NSB] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:17.325 [139709596412728] ERROR - [NSB] Error in browser handle read: 125 (Operation canceled) socket=-1
Oct 28, 2024 17:35:17.416 [139709629852472] WARN - NetworkServiceBrowser: Error sending out discover packet from 0.0.0.0 to 192.168.0.255: Network unreachable
Oct 28, 2024 17:35:17.416 [139709655165752] WARN - NetworkServiceBrowser: Error sending out discover packet from 0.0.0.0 to 192.168.0.255: Network unreachable
Oct 28, 2024 17:35:17.426 [139709596412728] INFO - [NSB] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:17.426 [139709596412728] ERROR - [NSB/SSDP] Error in browser handle read: 125 (Operation canceled) socket=-1
Oct 28, 2024 17:35:17.526 [139709596412728] INFO - [NSB/SSDP] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:17.526 [139709596412728] ERROR - [NSB/SSDP] Error in browser handle read: 125 (Operation canceled) socket=-1
Oct 28, 2024 17:35:17.627 [139709596412728] INFO - [NSB/SSDP] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:17.627 [139709596412728] ERROR - [NSB/SSDP] Error in browser handle read: 125 (Operation canceled) socket=-1
Oct 28, 2024 17:35:17.727 [139709596412728] INFO - [NSB/SSDP] Abandoning browse socket, it was closed.
Oct 28, 2024 17:35:21.729 [139709596412728] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/actions-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']
Oct 28, 2024 17:35:21.729 [139709596412728] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/actions-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']
Oct 28, 2024 17:35:21.729 [139709596412728] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-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:174:33 in funct
My bad, i turned on Plex web debug…
I could see my collection with 4g on smartphone, but i can’t play the 2 movies.
Then i connected the smartphone with Wifi and all was instantly.
Then i disconnected my smartphone and with 4g again i could see nothing.
While remote access went red PMS in settings
Plex Media Server Logs_2024-10-28_20-19-47.zip (388.5 KB)
It should NOT be red in settings.
Your PMS logs clearly show PMS knows the server is reachable by Plex.tv
and has published the server as “Mapped”
(Reachability = 1 is Yes, 0 = No)
Oct 28, 2024 20:04:06.847 [139830223473464] DEBUG - [EventSourceClient/pubsub/172.104.133.220:443] PubSub: Got notified of reachability for async identifier e877097f-6b4e-4205-aaf1-0555b4f1ccdc: 1 for XXX.XXX.XXX.XXX:xxxxx (responded in 198 ms)
Oct 28, 2024 20:04:06.847 [139830223473464] DEBUG - [EventSourceClient/pubsub/172.104.133.220:443] MyPlex: reachability check - current mapping state: 'Mapped - Publishing'.
Oct 28, 2024 20:04:06.847 [139830223473464] DEBUG - [EventSourceClient/pubsub/172.104.133.220:443] MyPlex: mapping state set to 'Mapped'.
Can you refresh the display, capture a screenshot, and show me?
PS: Looking at Plex.tv, I can see your IPv4 and IPv6 addresses as I should.
Yes, my public static IPv4 address is visible, I shot a video with my smartphone to show how fast my PMS disconnects.
Looking at your logs:
Oct 28, 2024 20:11:43.881 [139830191553336] DEBUG - [HttpClient/HCl#4a] HTTP/1.1 (6.7s) 200 response from PUT https://plex.tv/api/servers/324600bb48bd6bf05e29b531aca3e7c6682e06cc/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=6a20d78d-7603-4549-bbaf-ecae367e8547
Oct 28, 2024 20:11:43.881 [139830178720568] DEBUG - [Req#17b] MyPlex: async reachability check - current mapped state: 'Mapped'.
Oct 28, 2024 20:11:43.881 [139830178720568] DEBUG - [Req#17b] MyPlex: we already have requested a connectivity refresh for async identifier 6a20d78d-7603-4549-bbaf-ecae367e8547 which has not yet expired.
Oct 28, 2024 20:11:43.881 [139830172392248] DEBUG - [Req#182] MyPlex: async reachability check - current mapped state: 'Mapped'.
Oct 28, 2024 20:11:43.881 [139830172392248] DEBUG - [Req#182] MyPlex: we already have requested a connectivity refresh for async identifier 6a20d78d-7603-4549-bbaf-ecae367e8547 which has not yet expired.
Oct 28, 2024 20:11:43.881 [139830221364024] DEBUG - Completed: [192.168.0.2:55618] 200 PUT /myplex/refreshReachability (12 live) #170 TLS GZIP 6683ms 320 bytes (pipelined: 2)
Oct 28, 2024 20:11:43.881 [139830168152888] DEBUG - [Req#187] MyPlex: async reachability check - current mapped state: 'Mapped'.
Oct 28, 2024 20:11:43.881 [139830168152888] DEBUG - [Req#187] MyPlex: we already have requested a connectivity refresh for async identifier 6a20d78d-7603-4549-bbaf-ecae367e8547 which has not yet expired.
Oct 28, 2024 20:11:43.881 [139830221364024] DEBUG - Completed: [192.168.0.2:55608] 200 PUT /myplex/refreshReachability (12 live) #17b TLS GZIP 4959ms 320 bytes (pipelined: 7)
Oct 28, 2024 20:11:43.881 [139830149520184] DEBUG - [Req#18f] MyPlex: async reachability check - current mapped state: 'Mapped'.
Oct 28, 2024 20:11:43.881 [139830149520184] DEBUG - [Req#18f] MyPlex: we already have requested a connectivity refresh for async identifier 6a20d78d-7603-4549-bbaf-ecae367e8547 which has not yet expired.
Oct 28, 2024 20:11:43.881 [139830157404984] DEBUG - [Req#196] MyPlex: async reachability check - current mapped state: 'Mapped'.
Oct 28, 2024 20:11:43.881 [139830157404984] DEBUG - [Req#196] MyPlex: we already have requested a connectivity refresh for async identifier 6a20d78d-7603-4549-bbaf-ecae367e8547 which has not yet expired.
Oct 28, 2024 20:11:43.881 [139830223473464] DEBUG - Completed: [192.168.0.2:55623] 200 PUT /myplex/refreshReachability (12 live) #18f TLS GZIP 1649ms 320 bytes (pipelined: 4)
Oct 28, 2024 20:11:43.882 [139830223473464] DEBUG - Completed: [192.168.0.2:55617] 200 PUT /myplex/refreshReachability (12 live) #196 TLS GZIP 962ms 320 bytes (pipelined: 13)
Oct 28, 2024 20:11:43.882 [139830221364024] DEBUG - Completed: [192.168.0.2:55620] 200 PUT /myplex/refreshReachability (12 live) #182 TLS GZIP 2717ms 320 bytes (pipelined: 3)
Oct 28, 2024 20:11:43.882 [139830223473464] DEBUG - Completed: [192.168.0.2:55621] 200 PUT /myplex/refreshReachability (12 live) #187 TLS GZIP 2132ms 320 bytes (pipelined: 3)
Here you can see where it has reached the status of “Non-reachable”
yet the remote playback is running.
I can’t tell if this playback request is coming in as the brokered (plex.tv) request or the IP:Port-direct request.
When Remote Access turns red, When you let it sit for a few minutes, doing something else, then return, Does it go back to green?
This might be a bug in PMS in how it handles being request-overloaded.
I don’t know without more info and testing on my Synos.
Without doing nothing, it will return green after few minutes, then it will turn red again like a loop
PMS periodically checks remote access by itself.
When it does this, it’s also checking to see if your WAN IP changed.
If it’s changed, it records that in Plex.tv so Remote Access brokering works correctly with the new IP.
If it’s turning red then green again, I wonder about your port forwarding
My wan IP isn’t changing, it’s static.
I’m using DHCP for giving 192.168.0.101 to my Syno.
Initially I used a manually port forwarding from external port 50740 to internal 192.168.0.101:32400 but when the problem begins I changed external port to 32400 trying to see if could work better
I’m not worried about your WAN.
What I am concerned about is:
Given you’ve stated DHCP… Reservation or just where it happens to be set to?
What is the DHCP lease time?
I am asking this and pushing this way because only a LAN IP change or Port change will cause that Remote Access indicator toggle in a normally functioning system.
The exotic stuff which can cause it to fail is: DNS faults, Gateway/Router fault, or something like a Pi-hole.
About your supposition, i tryed with another router and the remote access is never red.
I tryed a lot with my smartphone with 4g and all the times the preview download and the playback it’s like i’m in wifi (my connection https://www.speedtest.net/result/16944631216.png)
The problem so far is surely the router (a rog rapture gt-ax6000), that have some problems with port forwarding ipv4.
I’m trying to do a factory reset and start with new configuration from 0.
I’m sorry for all the time that you spent for listening my problem.
Im having the same issue with remote access on the latest version as well. It says im connected but none of the libraries appear outside of the network. It just failed to connect, nothing on the network has changed I factory reset the router as well
My problem was port forwarding, I could test with this site that with my problematic router the ports are closed.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
