Remote Access Not Available

Plex Media Server Desktops & Laptops
1

I’ve used Plex for quite some time and usually when this happens I toggle UPnP on and off and it solves the problem only this time I didn’t. I’ve tried the whole port forwarding thing but no dice. I am not great with all this so I may have screwed up somewhere.
I have a Netgear router R6300
Thanks for your help!
http://127.0.0.1:32400/web/index.html#!/logsPlex Log.txt (114.8 KB)

2 Likes
2

I’m having the same issue here, it does connect remotely though but still shows red in Plex Media Server. Started after the last update. Also when I close the app on my Windows 10 PC and try to connect, it will take a second and then it will turn green and say its connected, then quickly disconnects and turns red again. It usually got fixed with the UPnP but now it doesn’t fix it.
I’m connected to a Frontier Cable ARRIS modem/router model #NVG468MQ.
Thanks!

3

Leave upnp off

1 Like
4

Thanks! this fixed my issue. Same as above happened after last update. Also have a netgear router.

Thanks

Must be an issue with upnp.

5

Had the same issue on my Mac and Google fiber. Worked for me.

6

I turned it off and tried it and still didn’t stay green, just a quick toggle then goes Red. Funny enough although it shows Red I am still able to connect remotely and others can connect to my server remotely as well. Maybe its just an issue with the Server interface, that it shows Red but really isn’t.

7

<- Another one with remote access broken after the last update. canyouseeme.org shows the service as available using both UPNP and manually specifying a port in Plex and forwarding that port on the router. However remote access shows as “Not available outside your network” and sometimes when retrying the remote access function, Plex then shows the service as disabled. I’ve restarted the router, Plex server, reinstalled the server software and toggled the UPNP function on my router. Plex doesn’t seem to be requesting a port using UPNP.

8

A problem has been identified in 1.14.0.5465 that resulted in failure to map port through uPnP on some routers. A fix is being tested by a couple of users.It is an issue with some routers

This, however, does not affect manual port selection and port forward/

So would need logs to see what the issue is
Restart the server. wait 5 minutes. If remote access is not working, get the logs

See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/

9

The issue isn’t with the routers, it’s with Plex.

Manual port selection didn’t work either.

1 Like
10

The problem i was referring to has no relevance for manual port selection

Logs?
Please See my post

11

I am having the same problem ever since the update this week on plexplass beta attached are my logs. thanks! Plex Media Server Logs_2018-11-15_18-00-43.zip (4.2 MB)

12

Still having the issue, attached is my Log: Plex Media Server Logs_2018-11-16_12-41-15.zip (3.6 MB)

13

I’m seeing something similar where the remote access doesn’t work if Secure Connections are Required. This is due to Plex failing to issue certs:

Nov 16, 2018 00:54:07.954 [0x7f8014fff700] DEBUG - CERT: Certificate or intermediate did not exist, fetching a new one.
Nov 16, 2018 00:54:07.954 [0x7f8014fff700] DEBUG - HTTP requesting POST https://plex.tv/devices/xxxxxx/certificate?version=2&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Nov 16, 2018 00:54:08.612 [0x7f8014fff700] DEBUG - HTTP 429 response from POST https://plex.tv/devices/xxxxxx/certificate?version=2&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Nov 16, 2018 00:54:08.613 [0x7f8014fff700] ERROR - CERT: Could not fetch certificate from the cloud: 429

I’ve been seeing this since last night, and accessing Plex through the web interface only works by temporarily allowing insecure connections through the query param ?secure=0

14

The certificate issue is being looked into at this moment

15

Thanks for the logs. Your issue is the regression i mentioned which arises for some routers - (ones behind with the uPnP WAN IP Connection spec - routers that have not implemented a version of the spec that was released in 2010)

A beta hot fix release for 1.14.0 is expected soon
In the meantime i have given you access to a development build with the fix

Nov 16, 2018 12:07:28.064 [6388] WARN - NAT: UPnP, error mapping port 28683, error: Unknown Error, controlURL: http://192.168.254.254:5000/wipc_cont.
Nov 16, 2018 12:07:28.345 [6388] WARN - NAT: UPnP, error mapping port 24566, error: Unknown Error, controlURL: http://192.168.254.254:5000/wipc_cont.
Nov 16, 2018 12:39:13.243 [7904] WARN - NAT: UPnP, error mapping port 23774, error: Unknown Error, controlURL: http://192.168.254.254:5000/wipc_cont.
Nov 16, 2018 12:39:13.525 [7904] WARN - NAT: UPnP, error mapping port 29129, error: Unknown Error, controlURL: http://192.168.254.254:5000/wipc_cont.
16

Your issue has been addressed and resolved,

were green again, thanks

17

I seem to be having the same issue even with a Manual port.

Logs:

Plex Media Server Logs_2018-11-16_17-50-05.zip (2.8 MB)

18

I have the Manual port forwarding working so I assume the UPNP is the router issue.

19

When will this hotfix be available to Plex Pass members? I’m also experiencing this issue.

20

I cannot see any evidence in the log of enabling a manual port selection. What the log shows is failure of uPnP mapping (due to the regression issue I mentioned earlier for some routers)

Nov 16, 2018 17:47:56.609 [2636] DEBUG - NAT: PMP, attempting mapping.
Nov 16, 2018 17:47:56.609 [2636] DEBUG - NAT: UPnP, attempting port mapping.
Nov 16, 2018 17:47:56.629 [2636] WARN - NAT: UPnP, error mapping port 14663, error: Unknown Error, controlURL: http://192.168.1.1:2555/upnp/2e729dc1-231c-3add-afa8-c74e5a168741/WANIPConn1.ctl.
Nov 16, 2018 17:47:58.229 [2636] DEBUG - PublicAddressManager: Mapping failed.

When having a port forward in the router, the manually specify port tickbox must be ticked and the public port forwarded to 32400 for the server must be entered in the box