Server reinstall is messy and Remote Access disconnected is broken

Over the years I have had problems where the Plex metadata got corrupt and the service wouldn’t start unless I reinstalled the service.

A quick reinstall of the service or delete of the metadata resolves the issue but every device shows the server unavailable and have to expand to find the new server.

Seems that user settings are cached so even clearing cache or reinstalling the app does not fix the problem. I have to reset customizations for each user on every device.

This coupled with Remote Access problems renders Plex a pain in the butt and unusuable.

Seems like there is an issue with remote Access every time I leave the house getting disconnected. I go back home and open the remote access tab and connect and fixes the issue. When I am on Plex on the local network there is no alert that there is a remote access issue, but as soon as I walk out the door. Plex is broken until I go back home and fix it.

I understand that Russell Automation bought out this product and wants to make it a cash revenue pushing to streamed w ads, but I have bought 2 lifetime memberships AND pay for a third plex pass account to support this project.

Can we get fix these customizable user settings to get a clearing option on the server settings and get LAN app notifications when remote connection is disabled?

I recommmend we all just cancel our plans and switch to Emby.

If you’re having a problem like crashing, it’s generally due to a database corruption, which in most cases is repairable without the loss of any metadata. Rolling back to an earlier version or updating to a new one is also common

Instead of having some kind of alert when your remote access goes down, the best option is to figure out why it’s going down

My remote access has been active for several years without a single failure

Remote access is generally not a Plex issue as much as a network/computer issue which you have to investigate and troubleshoot. Plex is just the last factor in the equation that is trying to tell you your setup is flawed

You can either troubleshoot those issues by yourself using the support articles Plex has provided or ask for specific help here for specific problems like you’re having

People here will help, but you have to ask, and provide input

I use the have the same problem of my remote access randomly turning off. It always seemed to turn off when I was away. Figured out (with Plex Help) that I needed to enable my UPnP for port forwarding. Since then, I have not had any issues.

Hi Jolly thanks for the suggestion, you are suggesting I enable my Comcast router for uPnP port forwarding (not uPNP on my Plex server) ?

I do have dedicated port forwarding on the manually specified port 32400 for NAT on the Comcast router to my server which has its IP static.

Xfinity Advanced Security disabled.
Xfinity xFi Port Forwarding assigned 32400 → server (IPv4)
[will check if behind CGNAT (double-NAT)]

When I attempt to connect remote access thru the web portal it always greens up after manually trying, then after a few days it stops working.

I wouldn’t think UPnP (security risk) would be required if the port is open and mapped.

I will try this suggestion next time I am back home granting that enable UPnP on my router should not be required if mapped and this introduces security risk on my home network.

My Plex server is on a dedicated Centos linux build so the service is always up and listening.

The comcast router goes out routinely and requires reboot often. I imagine this severs all connections to the Plex pass remote access servers.

I would think my Plex media server would try and reconnect automatically.
I suppose I should look at log files or maybe their is some reconnection command I can schedule to run.

https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
"Whenever you open your server settings or visit your Remote Access settings page, your server makes a HTTP request to our plex.tv service. "

  • I wonder if there is a way to cron this http get request out to keep alive my remote access.

[update]

Looks like I can run a cron a python script to authenticate to the API and republish server. Will try this cludgey idea.

cron > python script > API call > rePublish
plex.settings.get(‘PublishServerOnPlexOnlineKey’).set(True)
plex.settings.save()

Seems like the team could just make a change to the PlexMediaServer service to check the status and reconnect automatically.

Maybe it is time for a Comcast service call?

@FordGuy61 / @JaysPlex I believe it is more of an issue with the plex media server itself not checking and refreshing remote access connections.

It may be affecting many users and could possibly be contibuting to cancellations in numerous Plex Pass memberships.

How can I create a product bug w the DevOps team for review or a “feature” request?

The root cause of your problem is an unreliable Internet connection.

It is unrealistic to expect Plex, or any other such application, to provide reliable service when the Internet connection on which it depends is unreliable.

You should focus on resolving your Internet connection issues first, before looking at any issues with Plex.

Note that Plex Media Server checks remote access status on a regular basis. You can see the activity by searching for your public IP address and/or port number in the Plex Media Server.log file.

The forums are the only support mechanism for Plex.

You can create a feature request by posting in the Feature Suggestion section.

Connections drop all the time. A service should check the status and re-connect.
I don’t think you understand the nature of my issue. Once every few days my internet router requires rebooting.

This breaks my Remote Access as the PlexMediaServer service on my linux server never re-attempts to connect the remote access.

Every other service in my network re-establishes connection: onedrive, emby, syncthing, vpn services, etc.

This may not be an issue on the service running on a windows server.

Where can I submit a bug report?