I am having difficulty connecting both locally and remotely to my PMS. I am running an updated version of PMS on Ubuntu and have set up port forwarding. In the sidebar menu it shows a green check next to remote access enabled. However, whenever I try to connect remotely I cannot and my player on my iphone has a red “offline” label next to all of my content. I have found that sometimes after several minutes the indicator of remote access will go away after being active for a little while on PMS but I have tested this while its green and still no luck. It also seems my device is having difficulty connecting even when on the same network. My PMS is up and running right in front of me, but when I try to access it from my phone on the same network error comes up. Any suggestions would be greatly appreciated.
Can you provide more info?
First, let’s address local access.
- Which error(s) are coming up?
- Can you obtain the logs (Settings - Server - Troubleshooting - Download Logs) and attach that ZIP file here for me to read?
- Is the firewall active? Are Plex’s ports open?
- Usually it says “cannot continue playback, server not available” or “cannot connect to server, retry”
- Done
- I do not believe the firewall is active. How can I confirm Plex’s ports are open? I believe they are as it works intermittently.Plex Media Server Logs_2020-01-23_23-09-33.zip (4.4 MB)
Thank you!
Is the server on WiFi ?
From your logs, it looks like it’s isolated from your LAN.
When clients play, they have to attempt to connect via the public IP.
Do you see “Nearby” or “Remote” ?
Yes, its on WiFi.
Nearby.
Is the WiFi configured for Guest Isolation (or any type of isolation) mode?
It will be an option in the SSID configuration.
I am interested too. My WiFI is split into the usual 2G and 5G modes. Is this relevant?
There is a difference between 2.4 Ghz + 5Ghz concurrently on the same SSID versus 2.4 Ghz SSID & independent 5 Ghz SSID. It all depends on how the firmware allows configuration.
Guest network is disabled.
“Isolate Client” is disabled
Actually, since last evening i seem to be connecting fairly consistently (at least last evening and this evening). Connecting remotely is definitely still not working though.
Mind if we get one piece at a time stable?
Once local is stable, remote is easier.
Remote involves either a well behaved modem/router with properly functioning UPNP (universal plug & pray) or a clean network topography to manually create the path from the modem to the server computer.
For me:
- Modem gateway = 192.168.0.1
- Server = 192.168.0.23
- In Modem I write the forwarding rule to forward: Port 55555-55555 (start-end range) TCP -> 192.168.0.23 Port 32400.
- I then tell Plex “Manually Specify port” and give it 55555
Apologies for the analogy but it’s the same as setting up call forwarding from one phone to another. You tell everyone to call the number of the first phone. Nobody knows the number of the 2nd phone.
Got it. I agree let’s fix one at a time. Now I can’t connect locally again. SAys my server isn’t available and whenever I retry it continues to not work. I’m sorry my info is so vague. I honestly don’t think anything changed.
And I didn’t make any of the forwarding changes. It stopped working before I got your most recent update.
Please go to the server, stop plex, and make a tar.gz of the Logs directory under /var/lib/plexmediaserver.
Attach that tar.gz here.
I will look.
thank you very muchLogs.7z (2.5 MB)
I am finding a ton of these in your logs.
It means, for whatever reason, the ethernet adapter is reporting changes.
In most cases it’s going OFFLINE then ONLINE again.
Something in the OS config or the physical connection , in this case WiFI is dropping.
it’s in your best interest to wire it. WiFi can’t handle it (almost none can)
Jan 24, 2020 13:33:33.204 [0x7f9d5d5e7700] DEBUG - NetworkInterface: received Netlink message len=64, type=RTM_NEWLINK, flags=0x0
Jan 24, 2020 13:33:33.204 [0x7f9d5d5e7700] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=3, flags=0x11043, change=0x0
Jan 24, 2020 13:33:33.204 [0x7f9d5d5e7700] DEBUG - Network change.
Jan 24, 2020 13:33:33.204 [0x7f9d5d5e7700] DEBUG - NetworkInterface: Notified of network changed (force=0)
Ok, I’m now hardwired. Response times and buffering were much better after doing so. Big improvement. I went out for the day, returned home and everything is listed as offline on my iPhone player and getting the error that server is not responding when attempting access from my iPad. Is the expected behavior for plex to wake the server or do I need to wake it each and every time I want to use it?
As an update when I wake the computer running PMS manually I’m able to get on instantly. Perhaps this is more of a modem or hardware issue. Is there a way to trigger the server to wake up when I try to access it?
Grab the logs please. There is something fundamentally wrong with the base network.
see attachedPlex Media Server Logs_2020-01-25_21-54-47.zip (4.2 MB)
| Thu Jan 16 12:22:43 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:45:e4:54;CMTS-MAC=00:01:5c:83:a4:49;CM-QOS=1.1;CM-VER=3.0; |
|---|---|---|
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:45:e4:54;CMTS-MAC=00:01:5c:83:a4:49;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
| Fri Jan 24 12:28:06 2020 | Warning (5) | MDD message timeout;CM-MAC=00:40:36:45:e4:54;CMTS-MAC=00:01:5c:83:a4:49;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jan 24 12:28:08 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:45:e4:54;CMTS-MAC=00:01:5c:83:a4:49;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jan 24 12:53:32 2020 | Warning (5) | MDD message timeout;CM-MAC=00:40:36:45:e4:54;CMTS-MAC=00:01:5c:83:a4:49;CM-QOS=1.1;CM-VER=3.0; |
| Sat Jan 25 16:42:38 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:45:e4:54;CMTS-MAC=00:01:5c:83:a4:49;CM-QOS=1.1;CM-VER=3.0; |
