Server Version#: 1.14.0.5465
Player Version#: 3.73.2
Plex Media Server Logs_2018-11-12_10-59-52.zip (1.9 MB)
I just updated to the new Beta Version because I was having DVR search issues and was hoping it would fix it, unfortunetly it also broke remote acess. Please Help! Attached are my logs.
Actually, on mine it is just showing 'no remote access ’ but it works. I tried to watch something on my phone with remote access to the server (via 4G so different network and IP) and it worked. Strange.
I can as well but only indirectly, limiting my Plex’s abilities (artificial limit because it connects via Plex’s servers). Have you checked if it is a direct or indirect connection?
Thanks for providing logs - (please in future ensure you have debug logging enabled - see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
For this issue, the problem has already been investigated and identified and can easily be spotted in logs
Nov 12, 2018 10:55:41.897 [0x700000bd6000] WARN - NAT: UPnP, error mapping port 22372, error: Unknown Error, controlURL: http://192.168.0.1:1900/ipc.
Nov 12, 2018 10:55:42.160 [0x700000bd6000] WARN - NAT: UPnP, error mapping port 11683, error: Unknown Error, controlURL: http://192.168.0.1:1900/ipc.
There was a change in 1.14.0.5465 and it appears that not all routers are up to date with implementation of the protocol.
A fix is being tested by a couple of users and will make its way through the release process
This bug does not affect manual selection of port and a port forward
So what you are saying that my DD-WRT linux (latest version) from this month is not up to date with this protocol? I make it hard to believe that
It is not DD-WRT - but could be related to version of DD-WRT
There were issues with routers not running DD-WRT as well
The issue is arising for any router that has not implemented version 2 of the uPnP WANIPConnection spec released in 2010
http://upnp.org/specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf
Plex Media Server 1.14.0.5468 has just been released as Beta. It has two fixes for bugs that impacted Remote Access
See Release Notice
Anyone running an early beta or a development build with early release of these fixes should now update to the official beta, Thank you for helping confirm the fixes
Like i wrote to you in private this is not fixed yet, When setting manually port in plex “IT SHOULD” try to upnp it self but it does not, and IT does not responds to routers on that port it is still broken, I have tested with 3 different routers now 1 asus, 2 netgears its NOT working.
Manual set port, delete any port forwards for plex, look it fail at automatic port mapping for manually selected port setup
When Selecting Manually Specify Port, this does not use uPnP port assignment and expects you to have setup the Port Forward manually in the router yourself - forwarding the public tcp port you specify in the box to tcp port 32400 of the server local IP
The only evidence i have seen of a screenshot from a router Port Forward Range screen which looked wrong to me as it appeared to be forwarding to 32401 and not to 32400
If you are expecting manually specify port to automatically do a uPnP port forward for you then you have misunderstood the functionality - automatic port forward using uPnP is only done when Manually Specify Port is not selected
Why would I want to open up 34200 which is for lan, and would the default target for attackers to find open security issues by plex. I want to manually assign port, The manually mapping must be broken or else I need some guidance, because all other services I run and port forward just works?, like teamspeak,csgo servers, when I remove them from the port range the ports are closed ?
When I add default port 32400 to manually assign in plex and the router it works, but when I replace 32400 to 32401 in any router I tested it does not work, I’m telling plex manually port service page is broken, its like it never reaches the router, and says hey im open, but plex does not transmit the info to the routers, is there a delay from adding manually port that is NOT 32400 to plex dns/services before it gets accepted?
Normally you do not have to and you configure your router port forward rule to forward a different public port to local port 32400. eg forwarding 32401 to 32400
But … the screenshot you provided me indicates to me that the router has no such capability for the firmware that you have running on it - allowing you only to specify the port range and not giving you the option to have a different range for WAN/Public and LAN/Private
May be there is an advanced port forwarding rule setup page that would allow you to do what you need
What is important that the port forward ends up on 32400 when it reaches 192.168.1.3
SORRY its me being a ignorant stupid d!ck
I totally missed the wan port to lan port internally even tho it was mentioned several times.
I have fixed it and its shown in DD-WRT here
what can i say - i did ask you to switch to Port Forwarding page instead of Port Range Forwarding
and as you i repeatedly referred to wan/public and lan/private ports
I’m having the issue with remote access and installing the latest version did not resolved it.
Still Not available outside your network
The only way to investigate issues is to have diagnostics that can be looked into
For remote access issues, run the server with debug logging enabled
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
Restart the server to get fresh set of logs
If using automatic port configuration, ensure router has uPnP enabled
If using manually specified port, make sure the port forward is setup in the router to forward the selected public port to local port 32400
If it is not working, provide details of what the setup is and open the remote access settings page, do a browser refresh and if still not working, get the logs and screenshots of router settings eg port forward
see
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
