Remote Access won't stay connected after update to 1.18.2.2058

Server Version#: 1.18.2.2058
Player Version#: 1.4.1.940-574c2fa7
After the update to 1.18.2.2058 Remote Access won’t stay on. It connects and then a few seconds later it closes. I am using Manual Port Forwarding. (32400) I shut down the Firewall for a few minutes to check that as an issue but it didn’t help. I checked all the ports and the correct ports are in the system.

  • UDP: 1900 (for access to the Plex DLNA Server)
  • TCP: 3005 (for controlling Plex Home Theater via Plex Companion)
  • UDP: 5353 (for older Bonjour/Avahi network discovery)
  • TCP: 8324 (for controlling Plex for Roku via Plex Companion)
  • UDP: 32410, 32412, 32413, 32414 (for current GDM network discovery)
  • TCP: 32469 (for access to the Plex DLNA Server)
    I don’t’ think its anything on my end. Something changed with the update.
    Thanks,
    Tom
2 Likes

Same. Meh. Shows me for upgrading.

3 Likes

Check canyouseeme.org for success on your port.
I used that version with no problem.

@sureok please create your own forum post to track your issue.

Is it a remote access issue or is it because the server is dying? I’ve just started having an issue where hardware transcoding kills the server (Hardware transcoding (QuickSync) causing server crash).

a ni tambien me falla ,he abierto puertos y se desconecta en unos segundos ,en red local tambien se para cada poco.

Yep same here disconnects after about 4 seconds, keep your software updated they say it stops hackers and adds fixes they say, forget to tell you that it nearly always breaks something else could Plex please add a ROLL BACK option as that would be super!!!

7 Likes

I am seeing a similar issue on the same version.

canyouseeme reports “Connection timed out” if I test my port.

Remotely clients are generally working though, but receiving the message about having an indirect connection.

If I retry the connection from my Remote Access tab it will go green, but switches to red anywhere between 5s and a minute later.

Nothing I’m aware of has changed recently elsewhere in my setup (checked router and port forwarding settings, they all look correct).

I did see this issue a little while back, and thought I’d traced it to IPv6 being enabled on Ubuntu, but that seemed to be fixed by the next update that came down. I thought that might have been 1.18.0.1846, but the IPv6 fix in there seems to be Android specific, so I must be wrong.

Mentioned this in another thread, but worth mentioning here too. Been messing around with my router and PMS settings to try and diagnose the issue.

Disabling and enabling my remote access generated an error and warning:

“ERROR - Error issuing curl_easy_perform(handle): 7”
“plex.direct port xxxxxx: Connection refused”

Port number reported was the port I was port forwarding on my router. That setting was still the same from when remote access was working perfectly a few weeks ago.

canyouseeme.org reported that my port timed out.

Ultimately I did the following:

  • remove the port forwarding in my router
  • disable remote access on PMS
  • enable remote access on PMS

This automatically created a port forwarding rule in my router on a different port, which canyouseeme reported as a success.

Remote access has remained green for about 30 minutes, which is 29 minutes more than it has done for the past couple of weeks!

Not sure why my previously working port forward suddenly stopped, but hopefully this has solved my issues.

Seeing the exact same flaky remote connection issue when I updated to 1.18.2.2058. Rolled back to my previous server version and all is working again. No changes made to any port settings whatsoever.

1 Like

Same here, 1.18.2.2058 seems to have killed my remote connection. On the server itself, It says “fully accessible out your network”, but since I foolishly updated, devices on the network can’t now direct connect (so stuck at 328p playback) or sometimes give the “error loading home screen”.

I’m manually specifying a port I have forwarded to the static IP (also reserved IP on the router) of the host PC. My router hasn’t changed and no other windows or software changes happened before I updated working Plex to 2058. Port checkers all confirm port is open and ip address is still static/same. Router has not had firmware upgraded.

I’m not ruling out what forum posters have claimed, that it categorically cannot be Plex and MUST be a change or error on my devices or network setup but the common element in the 7 or 8 times this has happened has been installing a Plex update and the eventual fix is always re-installing an older version of PMS after days of delving into obscure network and router settings.

This time is the end of me updating plex, I’ll go through the headache of getting backing up my library and re-installing an old version of plex one more time, and then not updating again.

Appreciate what Plex are doing and that they aren’t a giant corporate with cash behind them, but updates are like Russian roulette. Keep up the good work, but would prefer longer between updates but more tested/stable ones please.

But stop stonewalling the idea that the update itself may have caused a problem and add easy version rollback just incase it was the update that broke (some) people’s media servers…

2 Likes

I also have this problem and I’m not tech-savvy enough to fix it, though I did try installing a static IP address (didn’t work) and then removing it (didn’t work). I’ve also tried reinstalling Plex (ddn’t work).

I’m now at a loss.

Please if you reply make any explanation very simple!

I also have the problem that if I don’t update - every time - Plex stops working completely.

I have issue to, I even tried to do a rollback to a version from October, but that did not work either…

I have this one and even more serious issues.

It sounds like your problem is similar to mine. I can see the folders when I look at the Plex Media Server on my TV, but when I click on them, they don’t work.

Same on my PS4. The list of films and TV programs can be seen, but they won’t run.

On the Plex Server on my PC I can play the programs, but that’s not the point of having a media server. I want to watch them when I’m on the sofa, not sat up at the computer.

The error seems to be the public server which is not accessible. And nothing I do, no matter how technical, seems to put this right.

Oh, the help page says,

Blockquote> If your computer has a firewall, proxy, ad-blocking software, anti-virus software, or similar installed, try temporarily disabling them and then attempt to connect the server again

But it doesn’t say what to do if disabling your firewall solves the problem. Which it does, or seems to.

So I’m experiencing the same issues when I click on start sever it shows it’s visible for only a few seconds before it goes red and shuts off.
I have tried to check if port is showing open on ‘canyouseeme.org’ and it times out.

my server was working okay until I updated to version 1.8.3.2156

I’m running on windows with a fixed ip and port open thru router

Please help

Yep. Here too, I haven’t changed a thing, now I cannot keep my remote connection up.

Update………so after much checking I finally found that when plex updated it created a new permission for the Plex software. So it needed to have access granted thru my firewall/ network connections under ‘allow app thru firewall’ setting. Once I found the newly created plex server exe. and grated it permission port could be seen open from canyouseeme.org and server was working properly.

I hope this helps anybody else that might be experiencing the same issues.

I found that there was a setting in my firewall which was ticked when it shouldn’t have been. Unticking it resolved the situation.