remote access is not working for me but before I updated the plex media server is was working good

remote access is not working for me but before I updated the plex media server remote access was working good

here is a screenshot of what is happening

remote access seems to work on the public plex media server but not on the beta plex media server

i have the same issue here :frowning:

did you solve the problem?

I am using the Public update channel on the plex media server and remote access is working for me but when I tried to use the beta update channel on the plex media server remote access is not working for me

oh really. then I have to downgrade my plex server version to public channel version. Thank you for the update. cheers

What I did was uninstall the plex media server and then download the plex media server with plex pass downloads off option on the plex website to the 1.11.3 plex media server version and that worked for me

I had the same problem with plexmediaserver_1.12.0.4829-6de959918_amd64.deb. I downgraded to plexmediaserver_1.7.5.4035-313f93718_amd64.deb and remote works fine now. This is not the first time Plex has blown up remote access… I now am saving distributions until I have a newer one that works. I have not found an archive of older versions of Plex to get a more recent, working version.

I have this issue with the public update like “RowdyDog” where do I find a previous deb? This is on a windows 10 machine.

https://downloads.plex.tv/plex-media-server/1.7.5.4035-313f93718/plexmediaserver_1.7.5.4035-313f93718_amd64.deb

But this is for Linux. I’m note sure of the Windows location.

I’m running Plex Server on a NAS and I’m having this problem. Public channel for updates, followed directions for port forwarding. Before a few days ago It WAS working, then it stopped. Version 1.12.0.4829

I just upgraded to 1.12.0.4829 and can no longer get remote access to work. I have been using a specified port of 32400 which I setup for acceptance by my router months ago. It had been working on the previous release. Here’s the log output (attached).

Note regarding my previous comment - after retrying about 25 times - my PLEX server finally connected the PLEX remote gateway. Something is clearly “amiss”…

Yeah, I went through Plex’s troubleshooting tips for remote access and I didn’t get any closer to connecting. Nuts!

I have been experiencing the same dilemma for the past year or so. For the first couple of years my remote access was on 24/7, always ready on the server running the latest Windows 10 Home. Without any changes to Windows, my server or the router modem, I started to experience the remote access seemingly going to sleep. Sometimes by just clicking on that page in the Server setup the access returned. Other times I would need to click on the Retry button (even though the box was not ticked to use a manual port) and access would return. When not accessible some apps will offer to go to the plex.tv site. For those that are not able to access my Plex server directly or via the website they do receive immediate access when I go to the remote access setup page to wake it up. The appearance is that the remote access is taking a nap, randomly. I have checked all known sleeping options on my computer, but nothing seems to make a difference. Randomly the remote access will take a nap and randomly it might wake it self, I may need to just go to the server setup page or I have to click on the Retry button. Is there something in Plex that would put it to sleep for remote access or could there be something in the router or Win 10 that is putting it to sleep? When awake access is perfect, multiple users can use with no problems.

Huh. I tried connecting remotely using Plex in a browser and it worked. I have selected the preference to never “allow fallback to insecure connections.” I’ll comb through the other preferences in Plex Media Player to see if anything might be different between them. Same Plex server, connecting remotely, different Plex clients give opposite results. Curious!

@“lyle.bickley” said:
I just upgraded to 1.12.0.4829 and can no longer get remote access to work. I have been using a specified port of 32400 which I setup for acceptance by my router months ago. It had been working on the previous release. Here’s the log output (attached).

The extracts from the log are just the warnings and there is no debug logged info. To investigate issues full logs are needed with debug logging enabled

The warnings you extracted are due to a timing issue where notifications of results of connectivity tests may get received out of sequence -

The likelihood of this is reduced if clicks on retry / enable / disable remote access are not made in quick succession and a time gap between retries.

This timing issue would correct itself after browser refresh (F5) or restart of the server without any clicks

For most reliable remote access configuration, adopt a manually specified port (public port) and a port forward in the router to forward this tcp port to local port 32400 for the server and the server IP address setup as a DHCP Reservation in the router or static outside DHCP Range. Also should ensure any additional network interfaces are disabled and only have one active, the one that has the IP Address used for the port forward.

If there are multiple servers, each would needs its port forward forwarded to local port 32400. The public ports, however, must be different for each server

We have a troubleshooting support article https://support.plex.tv/articles/200931138-troubleshooting-remote-access/

I see that you have resolved the issue,

For anyone else, please have a look at the troubleshooting article and if issues remain even with a port forward and ticking the manually specify port and entering the public port, then please provide diagnostics

Attach the diagnostics in post here

I figured out my own Plex connection issue. Turns out I had IPv6 enabled on my Netgear router. I don’t remember which IPv6 setting I had it set as, but clearly it was not making Plex happy. I first changed it to “Disabled,” then to the recommended “6to4 tunnel;” both solved this problem.