Please advise, I know I went ahead and rolled back to previous version but if a larger data set is needed for testing please let me know, and I will go ahead and push forward and get wireshark info.
Sure, this is whatās configuredā¦ Iāve been trying various things, disabling upnp, fixing the port etc etc so the logs might show some odd stuff. But this is how its usually configured, upnp with port chosen by plex. Itās worked for years, occasionally it shows as ānot availableā but either a router reboot or clearing the upnp ports on the router and a reboot usually has it sorted.
Thank you very much for this and the logs. The same errors as seen from logs from user @Beefsnack. The wireshark provided by @Beefsnack with the corresponding logs has helped us find the regression in 1.14.0.
I would be interested to know if affected users are users with dd-wrt running and if the issue is for specific version
That sounds promising! I am using a TP-LINK TD-W9980 with firmware 0.6.0 1.13 v0021.0 Build 160125 Rel.52064n. No DD-WRT here.
Ya I am running a Netgear R7000 w/ firmware V1.0.9.42_10.2.44. If this helps.
Found a problem with automatic mapping from evidence from other users.
The snippet of log file you provided which only covered 27 minutes of time did not show any uPnP port mapping and only covered the time when you used manual port selection. So based on the evidence you supplied - the only issue i could see is the one i mentioned already
It is very possible that you have the issue with auto port upnp mapping that the 2 other users who provided logs have - but without logs i cannot say
I believe I do as well. I will perform an update tonight and logs if possible when I get a moment. Other than that could you advise on what the status of this is with the development team?
Same here. Rolled back to 1.13.x and it fixed.
2 Likes
Same here, rolled back to 1.13x and now it is working again
Any update from the development team?
Yes, same issue with DD-WRT / had to switch to manual and disable upnp. works now.
The regression for port mapping failing through uPnP for some routers has been identified and hoping that sometime this week I will have a development build available to give out to try and confirm the fix.
I will only be making it available to users who provided logs that showed this specific issue.
1 Like
I had to roll back to 5456 and all is good.
Itās a good thing I started downloading and saving every build for crap like this.
Iām another user that had remote access broken by updating to 1.14. Downgrading to 1.13.9 fixed it for me.
I have temporarily gone back to the public version of 1.13.9.5456. No other changes, just installed, rebooted my PMS and itās all working again.
Happy to switch back once there is a version we think will fix remote access.
Sent you and also to @beefsnack links to download development build 1.15.0.415
Let me know if this fixes the issue
Can I get this development build as well?
Please see my earlier posts
Did the development build work for the other users?
If it did not I will roll forward again to provide more logs for you.
Sorry been away with work, and been unable to reply.
Iām glad Iām not the only one and that something seems to be being done about it, makes a change!
I have rolled back to 1.13.9.5456 and that is where I will be staying. On the Public versions. No more Beta/Plex Pass (whatever they cant seem to make up their mind its called) version for me.
I hope it gets resolved soon and is fixed for the people who are sticking with 1.14.0.5465
