I have just updated my plex server to 1.11.3.4803, but since that update, remote access displays that it’s not available.
Yesterday on the previous version it was still working fine. I’ve verified that the port setup is correct via canyouseeme, but I can’t seem to figure out why the server is suddenly not working.
I have attached the logs from after retrying the access, setting the port manually, restarting both plex and my pc.
I’m having the exact same issue.
I am having the same issue. Worst part for me? I had just gotten Plex to reach to the outside world. Sad. Anyone at Plex know when a fix action is going to happen?
I’m seeing the same thing. I updated to 1.11.3.4803 and the remote access status changed. When browsing to “Settings/Server/Remote Access” it shows that the Plex server is “Not available outside your network”. I’ve verified that Plex DOES work from outside the network. Must be a bug in the release.
@wizarduss said:
I have just updated my plex server to 1.11.3.4803, but since that update, remote access displays that it’s not available.
Yesterday on the previous version it was still working fine. I’ve verified that the port setup is correct via canyouseeme, but I can’t seem to figure out why the server is suddenly not working.I have attached the logs from after retrying the access, setting the port manually, restarting both plex and my pc.
Thanks for attaching logs
The logs show failure to automatically map a port
Feb 20, 2018 17:53:14.021 [3296] DEBUG - Request: [127.0.0.1:50177 (Loopback)] PUT /:/prefs?PublishServerOnPlexOnlineKey=true (11 live) GZIP Signed-in Token (wizarduss)
Feb 20, 2018 17:53:14.022 [10228] DEBUG - NAT: UPnP, attempting port mapping.
Feb 20, 2018 17:53:14.022 [8720] DEBUG - Completed: [127.0.0.1:50177] 200 PUT /:/prefs?PublishServerOnPlexOnlineKey=true (11 live) GZIP 1ms 268 bytes (pipelined: 17)
Feb 20, 2018 17:53:17.028 [10228] DEBUG - NAT: UPnP, didn't find usable IGD.
Sometimes router reboots resolve issues like failure to find the Internet Gateway Device interface to the router to setup the mapping
You could try the more reliable manual port mapping
So in the router setup a port forward as follows
WAN/Public Port 32400
Port forward to LAN/Private Port 32400
Protocol TCP
Forward to 192.168.1.88
and then in server / remote access / show advanced, tick manually specify port and enter the WAN/Public Port 32400
You could if your router allows it (most do) to have different WAN/Public Port forwarded to local/private port 32400.
You must ensue that the 192.168.1.88 address is fixed and setup as a DHCP Reservation in the router or outside DHCP Range if it is static
For others on this forum thread, please reboot router and then reboot server computer and if problem persists, disable and re-enable remote access (keep a 30 second gap between clicks) and if issue persists, get server 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/
I’m having the exact same issue on this release. Has Plex acknowledged as defect yet?
@slynch095 said:
I’m having the exact same issue on this release. Has Plex acknowledged as defect yet?
There is no evidence of a defect.
If your server is running on windows, check that the network connection has not switched to a Public Network or Unidentified Network
Somehow, it seems the issue has resolved itself now. I simply did a retry again on the remote access, and it seems to work now.
I have had remote access working for more than a year behind a professional grade firewall and have applied all patches to Plex with no issues to remote access, then suddenly it stops working with UPnP and you say it’s not a defect?
I have disabled the windows firewall, which has no effect on the outcome. This must be a new kind of feature, stop people from using it feature. I bet that will turn into a fad with engineers. Way to innovate 
Add one more with the same problem. UPnP cannot open a port and the port shows as ‘0’ in the Plex Remote Access status page.
Logged error
Feb 22, 2018 17:10:07.943 [6608] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (7474e4f5-b09c-44d5-adfe-dede931659c1, expected 6dd0db02-ee48-434c-b039-9ba90a018bc2)
Feb 22, 2018 17:10:16.583 [8244] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Feb 22, 2018 17:10:16.623 [7520] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Hello
I have the same problem with last version (1.11.3.4803). Even worse, because I can’t access the server from inside my net, for example, the Plex app on my Apple TV can’t connect to plex server and the android app on my phone only works with indirect conection.
I’ve tried to reboot router, the plex server, and disabling and re-enabling remote access with no success.
I was already using port 32400 and all stuff in my router seems ok.
I attach the logs.
Thanks.
I am also having the same issue, I have manual port forwarding setup but continue to get the message “Not available outside your network.” I have also restarted my router and server pc, disabled remote access and re-enabled, but no success. It does show for a split second, "Fully accessible outside your network when I do that, or click the “Retry” button, but then goes immediately back into “Not available outside your network.” My logs are attached.
Exact same issue
@Key_notes88 said:
… I have also restarted my router and server pc, disabled remote access and re-enabled, but no success. It does show for a split second, “Fully accessible outside your network when I do that, or click the “Retry” button, but then goes immediately back into "Not available outside your network.”
That’s exactly the issue I’m finding.
@sa2000 said:
@slynch095 said:
I’m having the exact same issue on this release. Has Plex acknowledged as defect yet?There is no evidence of a defect.
Is there evidence yet?
Same issue here.
Same issue. Making mom life harder.
Same problem here. Happened straight after the update.
Logs and screenshots are the same as everyone else.
@Key_notes88 said:
I am also having the same issue, I have manual port forwarding setup but continue to get the message “Not available outside your network.” I have also restarted my router and server pc, disabled remote access and re-enabled, but no success. It does show for a split second, "Fully accessible outside your network when I do that, or click the “Retry” button, but then goes immediately back into “Not available outside your network.” My logs are attached.
Could I please see the port forward setup in the router - a screenshot of the screen for editing the port forward to the server local IP 192.168.0.101 and confirmation that you have ticked the manually specify port in the server remote access advanced settings
I also want to see confirmation that you have a DHCP Reservation in the router for 192.168.0.101 - so screenshot of the DHCP Reservation Table please and the ipconfig /all output on the PC
I can see that the IP Address was 192.168.0.18 at some point so may be your port forward is to the wrong IP Address
@xasvi said:
@sa2000 said:
@slynch095 said:
I’m having the exact same issue on this release. Has Plex acknowledged as defect yet?There is no evidence of a defect.
Is there evidence yet?
No
There is a timing issue affecting the visible status of remote access - but that timing issue where the status may not be true should not affect the actual availability of remote access.
@xasvi said:
Hello
I have the same problem with last version (1.11.3.4803). Even worse, because I can’t access the server from inside my net, for example, the Plex app on my Apple TV can’t connect to plex server and the android app on my phone only works with indirect conection.
I’ve tried to reboot router, the plex server, and disabling and re-enabling remote access with no success.
I was already using port 32400 and all stuff in my router seems ok.
I attach the logs.
Thanks.
Thanks for the logs and screenshot
These log events indicate that a test to connect to your server via the public IP and public / wan port 32400 was not successful
Feb 22, 2018 21:34:17.696 [5656] DEBUG - EventSource: Got event [data] '<Message address="81.184.xxx.xxx" port="32400" asyncIdentifier="de7f2805-ee2c-46e7-a973-c39cb07268b6" connectivity="0" command="notifyConnectivity"/>'
Feb 22, 2018 21:34:21.318 [5656] DEBUG - EventSource: Got event [data] '<Message address="81.184.xxx.xxx" port="32400" asyncIdentifier="743c637b-ce6c-4089-a2e7-8e9492250055" connectivity="0" command="notifyConnectivity"/>'
I would like to see the following
Screenshot of the router Port Forward entry to show that external / wan / public tcp port 32400 is forwarded to local / lan / private port 32400 to 192.168.1.11 and the port forward is active
Screenshot of the router DHCP Reservation Table to confirm that 192.168.1.11 is setup as a DHCP Reservation
ipconfig /all on the server PC to show the network info - you can copy to a text file and attach
And confirmation that you are not unticking the Manually Specify Port and it is always left as ticked with the wan/public/external port in the box matching the WAN/Public/External Port in the port forward - which according to the logs should be 32400 - same as local port
Please also let me know what internet security / anti virus software is installed on the server
Check that the network connection on the windows machine is showing as Private Connection and not Unidentified Network or Public
You could try to add the following inbound rule in the firewall advanced settings - this is a port rule and does not specify any programs and is separate from the normal plex media server firewall rules that whitelist the exe files
Rule Type: Inbound Port Rule
Protocol: TCP
Remote Port: Any
Remote IP: Any
Local Port: 32400
Programs: Any
Scope: all network profiles
Action: Allow
and restarting the PC or firewall after setting it
With regards to the timing issue I mentioned earlier, avoid multiple clicks of retry on the server remote access settings page and have a delay of 30-60 seconds between clicks. Similarly if enabling / disabling remote access
When providing further info requested above, please include fresh server logs zip
Thank you
