Remote Access shuts off

General Discussions
41

@sa2000 @ChuckPa

I have given up on plex automatic features like this a long time ago…

I always set a static reservation for each plex server
I always port forward manually
I always turn off DNLA on the server

On the routers

I always disable uPNP or whatever its called on your flavor of router its a security issue… any upnp device on the network can punch holes in the firewall whenever they want and dial home to russia and china

I always reboot my router after plex changes

Now even after turning off upnp and manually setting ports in plex the logs show it STILL tying to use NAT PNP…

I have pretty good remote connectivity this way but the logs definitely show that even though I get everything set up manually correctly … plex is fighting to screw it up…

Most importantly … after you set all this up. Log out of your server and all clients

Go to plex.tv and start the web client there… delete all your servers and clients under devices… DO IT… this will clear out all the old certfiicate info

Now sign back on your server, clear the DNS cache and / or reboot. Then log back into your server

Then go and log back into your clients … all new certificates should be downloaded…

42

ok, i’m fit to be tied. as much as i enjoy the help, having to go through all this effort for what should be automatic, as it used to be… its frustrating for someone like me.Saying that, I did as you asked.

610×559 92.1 KB

as you can see? router settings set up as you requested.

again, everything as it should be, but im not connecting to the net… what am i missing??? i know im missing someting in the process… and why i hate that i have to do this all manually, when 2 updates ago, it was clean.

I really would like the remote access to work. I’m extremely happy with my LAN based network on Plex, its great for home. But my wife uses Plex at work… and as i can tell you, Happy Wife, Happy Life. shes not that happy right now. chuckles

added the newest logs… sigh

43

@Wh4tthehell said:
ok, i’m fit to be tied. as much as i enjoy the help, having to go through all this effort for what should be automatic, as it used to be… its frustrating for someone like me.Saying that, I did as you asked.

610×559 92.1 KB

as you can see? router settings set up as you requested.

again, everything as it should be, but im not connecting to the net… what am i missing??? i know im missing someting in the process… and why i hate that i have to do this all manually, when 2 updates ago, it was clean.

I really would like the remote access to work. I’m extremely happy with my LAN based network on Plex, its great for home. But my wife uses Plex at work… and as i can tell you, Happy Wife, Happy Life. shes not that happy right now. chuckles

added the newest logs… sigh

Your server IP Address changed. It is not 192.168.0.13 anymore.
It is showing as 192.168.0.14

So first thing is get the DHCP Reservation working for the server IP Address and when you know it is fixed and won’t change then setup the port forward to that IP

44

I’ve had the same issue for a while now, posted about it in another thread. The server also occasionnally tells me it is unclaimed (because it can’t talk to plex.tv, I suppose).

Definitely not a double NAT issue, not using jumbo frames either.

Unreachable error :

zpqjd0lc195m.png1001×217 11 KB

Unclaimed error :

pgd680aaz122.png972×210 12.3 KB

45

Update : here are the logs.
Plex version 1.2.2.2857 on Synology DSM6.

46

ok I contacted my isp and got a IP and everything was working. I download the latest version and now it is not working again. I have checked and I do not have double NAT this time. What else ?

47

I forgot to attach the logs. Here they are.

48

ok I went into my router and found the forward section and the public port for Plex server and put that in the manual box on the setting page and now it is working. I see two Plex server entries in my router and each has a different port number. Should there be two ? I don’t think so. How do I remove one of them ?

49

Screenshots

50

Ok, all set up as you suggested, looks like its working again now. Thank you. however, I do notice that if i go back periodically to check on the server, i open the web based screen it shows red, then switches back to green. is this a real issue? or just they way the GUI is acting up.

51

@Wh4tthehell said:
Ok, all set up as you suggested, looks like its working again now. Thank you. however, I do notice that if i go back periodically to check on the server, i open the web based screen it shows red, then switches back to green. is this a real issue? or just they way the GUI is acting up.

The logs show successful connectivity tests at 15:19 and 15:22

There was an issue raised on this already where the green status is not set until after the asynchronous connectivity test completes. It was being fixed so that it does not go red when there are no actual errors.

I will find out the status of the fix

52

@Wh4tthehell said:
Ok, all set up as you suggested, looks like its working again now. Thank you. however, I do notice that if i go back periodically to check on the server, i open the web based screen it shows red, then switches back to green. is this a real issue? or just they way the GUI is acting up.

I have re-opened the issue for this as it does not appear to have been fixed.
There is no actual problem with remote access - it is just that the green status is delayed

53

I have a Netgear Nighhawk X4 which is a pretty new router that supports UPnP and I also am having the same issues with remote access since the last update.It will click to green for a few seconds only to go to red and not work.I hate when an upgrade is actually like a downgrade :frowning: And NO!!! I will not do a work around, that is not what I pay money for.Get this fixed already!

54

@GW215 said:
I have a Netgear Nighhawk X4 which is a pretty new router that supports UPnP and I also am having the same issues with remote access since the last update.It will click to green for a few seconds only to go to red and not work.I hate when an upgrade is actually like a downgrade :frowning: And NO!!! I will not do a work around, that is not what I pay money for.Get this fixed already!

Did @sa2000 say a work around was needed? I don’t see any. I believe his specific words are “There is no actual problem with remote access - it is just that the green status is delayed”

55

My comments were relating specifically to the last issue reported by @Wh4tthehell where the remote access status shows momentarily as red then the actual true status of green comes on

If it is going Red and staying red then that is a different problem which would need to be looked into with logs and screenshots.

With regards to uPNP ports, there have been many instances where it was seen that a port forward and manually specifying the port is a far more reliable option

56

I am having issues with this too. Remote Access appears to be working correctly for a period of time, then for some reason shows disconnected, however the appropriate ports are still forwarded in my router. If I disable and then reenable it all works again, until a day or two later then it happens again.

57

@interconnect said:
I am having issues with this too. Remote Access appears to be working correctly for a period of time, then for some reason shows disconnected, however the appropriate ports are still forwarded in my router. If I disable and then reenable it all works again, until a day or two later then it happens again.

Please provide zip of server logs when you find that remote access is disconnected
See https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files

58

@dpolombo said:
I’ve had the same issue for a while now, posted about it in another thread. The server also occasionnally tells me it is unclaimed (because it can’t talk to plex.tv, I suppose).

Definitely not a double NAT issue, not using jumbo frames either.

Unreachable error :

1001×217 11 KB

Unclaimed error :

972×210 12.3 KB

@dpolombo said:
Update : here are the logs.
Plex version 1.2.2.2857 on Synology DSM6.

Just looked at your logs.
You have network issues on the server
As example

Nov 13, 2016 20:28:06.826 [0xee111b40] ERROR - Error issuing curl_easy_perform(handle): 6
Nov 13, 2016 20:28:06.826 [0xee111b40] WARN - HTTP error requesting PUT https://plex.tv/api/servers/45cd7bae81937297d2bc815e6b82d0862acd04b7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=1954474d-8bb9-41fb-95c8-56ffebca0932 (0, No error) (Couldn't resolve host 'plex.tv')

Server was not able to communicate with plex.tv to get periodic connectivity tests for remote access
DNS not working

and earlier - a timeout

Nov 13, 2016 20:27:09.498 [0xe87c5b40] DEBUG - MyPlex: Requesting reachability check.
Nov 13, 2016 20:27:09.500 [0xe87c5b40] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/45cd7bae81937297d2bc815e6b82d0862acd04b7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=0da51e44-3757-4357-b14c-685c95e4c603

Nov 13, 2016 20:27:26.788 [0xe87c5b40] ERROR - Error issuing curl_easy_perform(handle): 28
Nov 13, 2016 20:27:26.788 [0xe87c5b40] DEBUG - HTTP simulating 408 after curl timeout

The logs have loads of these types of errors

As to the server becoming unclaimed - see release notice for version 1.2.3 here
http://forums.plex.tv/discussion/comment/1286422/#Comment_1286422
which has this fix

  • (Network) Clients might incorrectly report a server as unclaimed or remote access as unavailable after network timeouts. (#4994)

Suggest you get the current version of Plex Media Server - 1.2.7

Unrelated - you have some permissions issues

Nov 11, 2016 20:33:40.715 [0xf1223b40] ERROR - [Notify] Failed to add watch for /volume1/media/Videos/Series/Dark Matter/Season 01 (13: Permission denied)
Nov 11, 2016 20:33:40.725 [0xf1223b40] ERROR - [Notify] Failed to add watch for /volume1/media/Videos/Series/Star Wars - Rebels/Season 01 (13: Permission denied)
Nov 11, 2016 20:33:40.729 [0xf1223b40] ERROR - [Notify] Failed to add watch for /volume1/media/Videos/Series/Boardwalk Empire/Season 01 (13: Permission denied)
Nov 11, 2016 20:33:40.731 [0xf1223b40] ERROR - [Notify] Failed to add watch for /volume1/media/Videos/Series/Misfits/Season 04 (13: Permission denied)
Nov 11, 2016 20:33:40.731 [0xf1223b40] ERROR - [Notify] Failed to add watch for /volume1/media/Videos/Series/Misfits/Season 05 (13: Permission denied)
 Nov 11, 2016 20:33:40.777 [0xf1223b40] ERROR - [Notify] Failed to add watch for /volume1/media/Videos/Series/Blindspot/Season 01 (13: Permission denied)
59

@firefox99 said:
ok I contacted my isp and got a IP and everything was working. I download the latest version and now it is not working again. I have checked and I do not have double NAT this time. What else ?

@firefox99 said:
I forgot to attach the logs. Here they are.

@firefox99 said:
ok I went into my router and found the forward section and the public port for Plex server and put that in the manual box on the setting page and now it is working. I see two Plex server entries in my router and each has a different port number. Should there be two ? I don’t think so. How do I remove one of them ?

As I said need screenshot to know exactly what you are referring to.

What you need to have

  1. Make sure that IP Address 192.168.0.117 for the PC running Plex Media Server is fixed and does not change. So look into the router DHCP Reservations and make sure the IP is DHCP Reserved

  2. As you are using public port 32400, make sure your router has a tcp port forward for WAN/Public Port 32400 to forward to Local/Private Port 32400 for IP Address 192.168.0.117

  3. As there is some evidence of some firewall action in the logs with some udp actions being blocked, there may well be a block on the tcp port - so in the firewall have the following rule:

Inbound Port Rule
Protocol: TCP
Local Port 32400
Remote Port: any
Programs: Any
Scope: All network profiles
Action: Allow

  1. Separately for GDM and SSDP server discovery within the local network, allow the following udp ports in the firewall

Inbound Port Rule
Protocol: UDP
Local Port 32410-32412 and 32414
Remote Port: any
Programs: Any
Scope: All network profiles
Action: Allow

  1. To prove that DHCP Reservation is working for the IP Address, restart both router and PC
    and check with command ipconfig on the PC to see that the local IP Address is still 192.168.0.117 after the restarts

  2. On server settings for remote access, with show advanced, ensure Manually Specify Port is ticked and 32400 entered in the box and a retry done

60

@sa2000 said:
Server was not able to communicate with plex.tv to get periodic connectivity tests for remote access
DNS not working

Duh. Switched to OpenDNS, I’ll see if it’s better than my ISP.

As to the server becoming unclaimed - see release notice for version 1.2.3 here
http://forums.plex.tv/discussion/comment/1286422/#Comment_1286422
which has this fix

  • (Network) Clients might incorrectly report a server as unclaimed or remote access as unavailable after network timeouts. (#4994)

Suggest you get the current version of Plex Media Server - 1.2.7

Doing that right now, thanks!

Unrelated - you have some permissions issues

Well, thanks for everything :slight_smile: