Remote access broken, yet again!

[sa2000]

Does the Port Forwarding screen give different options from the one you used? Port Range Forwarding

[wazer]

@sa2000

Does the Port Forwarding screen give different options from the one you used? Port Range Forwarding

yes https://image.prntscr.com/image/4MxYoodsQIaMQFRpwEXK9Q.png

[zanich]

I rolled back to Version 1.13.9.5456 and it works again, something wrong with 1.14.0.5465

[wazer]

@sa2000

Your port forward appears wrong
It is forwarding 32401:32401 to 32401

Need another field for local / lan port and set it to 32400

What do you mean?

Its setup correctly?

[azdusty]

I rolled back to the most recent public release. It works again. Agree, something is wrong with 1.14.0.5465.

[sa2000]

@wazer

What do you mean?

Its setup correctly?

Why do you say that? For Plex Media Server the port forward must go to local port 32400. You have selected a public port of 32401 but your DD-WRT is not giving you an option on the screen to have a different WAN/Public Port range from the Local Port

Most routers give that option, you would have for your example

Port 32401
Forward to local 32400
to 192.168.1.3
and manually specify port ticked and 32401 entered

If your router does not allow you to have different port for WAN/public and for LAN/Private - then only option is to use 32400 for public
So would be
Port 32400
Forward to 32400
to 192.168.1.3 and manually specify port and enter 32400

[sa2000]

Plex Media Server 1.14.0.5468 has just been released as Beta. It has the two fixes for the bugs that impacted Remote Access

See Release Notice

Plex Media Server

Plex Media Server 1.14.0.5468 is now available to Plex Pass users in the Beta update channel. Additional changes after above release notes: FIXES: (Transcoder) Resolved a rare deadlock (#9332) Automatic port mapping could fail with some older routers (#9335) Fix for Server Unreachable and Remote Access issues (#9228)

• Automatic port mapping could fail with some older routers (#9335)
• Fix for Server Unreachable and Remote Access issues (#9228)

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

[sa2000]

@zanich

I rolled back to Version 1.13.9.5456 and it works again, something wrong with 1.14.0.5465

@azdusty

I rolled back to the most recent public release. It works again. Agree, something is wrong with 1.14.0.5465.

Please update to the beta release issued today - 1.14.0.5468

[sa2000]

@VBB

1.15 did not solve the issue, unfortunately.

Just posting to confirm that this issue has now been resolved with the 1.14.0.5466 pre release hot fix (now superseded by 1.14.0.5468)

[VBB]

.5466 did fix my issue, yes. Been running for two days, Will upgrade to .5468 in a bit. Thanks again!

[zanich]

Confirmed 1.14.0.5468 remote access working

[sa2000]

@wazer

What do you mean?

Its setup correctly?

Please in future avoid multiple forum threads posts for same issue as we end up with incoherent fragmented information.

For anyone who wants to know the outcome and conclusion of this issue - you can see posts in this other forum thread from here onwards

No Remote Acess beyond Indirect

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

[ssmith44]

My remote access is broken as well. I have the latest beta update

[sa2000]

@ssmith44

My remote access is broken as well. I have the latest beta update

If it is not working and you have already gone through Troubleshooting Remote Access . please see my post earlier on here for diagnostics Remote access broken, yet again! - #14 by sa2000

[SmoothMarx]

Issue resolved for me with version 1.14.0.5468

[beerhunt]

I resolved this by deleting BOTH the cache and data of the PM Server in my 2017 Shield TV’s (settings>apps>system apps). Then, rebooting the Shield TV and resetting the Server and then, reopened the Plex.tv web app. This was after installing the beta v1.14.0.5468 which had no effect beforehand!