Plex server unreachable

Server Version#: Plex Media Server for Linux v.1.43.0.10389-8be686aa6

Player Version#: 4.156.0

Plex has been running fine on my Ubuntu for about a year now. However, within the last couple of weeks I keep getting errors stating the following:

“The server “PLEX” is unreachable. Make sure it’s running, double check your network, and try again.”

Usually this is resolved by stopping/starting plexmediaserver via SSH, but today that didn’t work. Nor did rebooting the Ubuntu box.

I can see that the Media folders ar properly mounted in Ubuntu and access the files within. PMS service is running in Ubuntu.

Accessing http://ServerIP:32400/web does not let me edit the server settings.

I haven’t touched preferences.xml since I got the server running a year ago.

The server was last running fine at 11pm last night, but down by 9:00am this morning.

Any help or insight would be appreciated.

Please make a tar.gz of the Logs directory the next time it stops
then attach that tar.gz here

It will help us figure out what happened.

Hi Chuck,

It’s stopped at the moment (and throwing 503 errors in the web client).

logs.tar.gz (2.4 MB)

Here are the logs.

Thanks for your help

Please re-enable debug, not verbose, logging. Without debug level entries it is difficult to tell what is happening with the server.

There is a typo in Allowed Networks. Use 192.168.1.0/24 or 192.168.1.0/255.255.255.0.
Jan 15, 2026 09:50:16.206 [132311686572856] ERROR - Error parsing allowedNetworks entry '192.168.1.x 255.255.255.0': Invalid argument [system:22]

If you cannot reach server settings via Plex Web and are comfortable with the Linux CLI & text editors (Nano, Vim, etc.), then you can directly edit preferences.xml. See Advanced, Hidden Server Settings, logDebug and allowedNetworks.

  1. Stop Plex Media Server.

  2. Make a backup copy of preferences.xml.
    sudo cp -p Preferences.xml Preferences.backup

  3. Edit Perferences.xml to correct the entries.
    logDebug="1"
    allowedNetworks="192.168.1.0/24"

  4. Verify correct ownership & permissions after saving the changes.
    plex:plex is default. Adjust as needed if running with a different username/group.
    ls -l Preferences.xml
    sudo chown plex:plex Preferences.xml <-- if needed

  5. Start Plex Media Server.

1 Like

Thanks for spotting that error. I’ve fixed it now. It must’ve been there for the last 6 years.

Plex did come back online after the edit. I’ll let you know if this was a permanent fix.

I saw this post Plex - Unraid - Docker, server going offline. Reason unknown as it seemed to discuss similar behavior.

The comment by @FordGuy61 regarding a bug in PMS 1.41.7 had me looking at the size of my plugins.library.db files. Several of my these files are 47GB in size each.

Could this be causing the error in my case? Are any of these safe to delete?

I’ll try running @ChuckPa ‘s DBRepair tool when I next get a chance.

Thank you for your help.

@ExHongKonger

You’ll want the Deflate function.

Not knowing your CPU and storage, it might take from a few minutes to several hours.

It won’t hang.

Be patient with it.

1 Like

DBrepair deflate worked great! It took less than 2 hours to reduce the database to 1% of its pre-deflate size.

Are the 3X47GB files with dates prior to today safe to manually delete now? It would be nice to reclaim that disk space if possible.

Plex isn’t constantly scanning the library anymore, but the pages are flashing approximately every 10-11 seconds (and it looks like it’s doing a mini-scan). This is more noticeable on the Mac app than the Web version.

I’ll follow up with new logs if the server goes missing again.

Thanks again!

You can delete -

  1. the -tmp- databases
  2. the 47 GB backups

Now that the DB is normal again, another DBRepair Auto might be in order

Thanks.

The DBrepair tool said the same thing about running again in auto, so I did.

Funny how it and I think alike

:rofl:

lol

1 Like

It was working for afew hours, but just went offline again. Logs attached:

logs.tar.gz (5.5 MB)

Go to Settings - server - Network - Show Advanced

Disable IPv6 and SAVE

you have an IPv4 LAN.

Also, the device at 192.168.1.88 needs the app restarted (terminate and restart)

It’s trying to use the old certificate

Lastly, Hardware transcoding does not appear to be enabled.
The N150 has the capability.

If it’s not showing up (to be enabled) in Transcoder settings,
then stop Plex, reinstall the package using DPKG and have it make certain everything is correctly configured

Jan 16, 2026 14:08:02.953 [126504215034680] DEBUG - [VoiceActivityDetectionManager] [Universal] Using local file path instead of URL: /mnt/Video/Movies/Pirates of the Caribbean - Dead Men Tell No Tales (2017)/Pirates of the Caribbean Dead Men Tell No Tales (2017) {tmdb-166426} [Bluray-1080p Proper][EAC3 Atmos 7.1][x265].mkv
Jan 16, 2026 14:08:02.953 [126504215034680] DEBUG - [VoiceActivityDetectionManager] TPU: hardware transcoding: final decoder: , final encoder: 
Jan 16, 2026 14:08:02.953 [126504215034680] DEBUG - [VoiceActivityDetectionManager/JobRunner] Job running: EAE_ROOT=/tmp/pms-8f66a461-4c8d-42fe-af51-05d2439a3d85/EasyAudioEncoder FFMPEG_EXTERNAL_LIBS='/var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Codecs/ca90ef9-9a65c18385d96de09023e106-linux-x86_64/' X_PLEX_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "/usr/lib/plexmediaserver/Plex Transcoder" -codec:1 eac3_eae -eae_prefix:1 20bd17c2-56da-4116-8879-1bd91af448e6_ -analyzeduration 20000000 -probesize 20000000 -i "/mnt/Video/Movies/Pirates of the Caribbean - Dead Men Tell No Tales (2017)/Pirates of the Caribbean Dead Men Tell No Tales (2017) {tmdb-166426} [Bluray-1080p Proper][EAC3 Atmos 7.1][x265].mkv" -y -nostats -loglevel quiet -loglevel_plex error -progressurl http://127.0.0.1:32400/video/:/transcode/session/20bd17c2-56da-4116-8879-1bd91af448e6/07b2018d-8a85-45c0-99df-0d19d16c1a48/progress -filter_complex "[0:1] aresample=async=1:ochl='mono':rematrix_maxval=0.000000dB:first_pts=0:min_hard_comp=0.01:osr=8000[0]" -map "[0]" -metadata:s:0 language=eng -codec:0 flac -b:0 4096k -f flac -map_metadata -1 -map_chapters -1 "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache/Transcode/Detection/ee51c278-5530-42dd-8b8a-a61eca68dea8"

Thanks for knowledge. I thought I’d disabled IPv6 when I switched ISPs to one that doesn’t support v6. I guess I forgot to hit save :man_facepalming: .

192.168.1.88 is the server itself. It doesn’t have the player app installed. Is there a way for me to get it to refresh the certificate? I remember that Tautulli was complaining about a stale certificate. Could it be a similar application hosted on the server that is causing this rather than Plex itself?

Hardware transcoding is already turned on & functional (at least on video playback). I wasn’t aware that the n150 was also capable of HW audio transcode, but I’d be happy if I’m wrong about that.

Restarting plexmediaserver did work to get the server back up again this time.

Part of my troubleshooting earlier this week was to stop & reinstall Plex using a fresh download and dpkg. Do you think it’s worth doing again?

I was noticing a lot of errors/warnings regarding the agents. Unable to find metadata agent provider for identifier ‘com.plexapp.agents.none’ It was while I was trying to save the setting in one of the libraries that the Plex crashed. Trying to make the same changes just now caused it to freeze for several minutes, but then it resumed on its own.

I don’t know if that’s important, or related, but I thought I’d add that information.

Your certificate was refreshed Jan 8th.

To refresh things, you only need to terminate and then cold-start the apps

As for the N150 HW transcoding – Yes, it’s supported. I have the N100 (alderlake) and it works beautifully.

Your logs weren’t indicating HW transcoding but I might have misread what it was doing at that point too. Sorry

I think I see what you’re referring to: [VoiceActivityDetectionManager] MDE: unable to find a working transcode profile for video stream

From what I remember, deleting the codecs folder and having Plex download a new one was a fix for this in the past. Is that still best practice?

terminate and then cold-start the apps

Would a reboot o fthe server cover that?

No, reset / reboot the player.

They are what need to pull the new cert ID info from Plex.tv

Shield / AFTKA / etc – reboot
ATV - Restart
TV’s - Full power off (not standby – there’s a setting for that)
Browsers – Control + F5 is a force reboot/reload of the browser

OK, I’ll try rebooting the various devices.

The IP address that’s giving all the warnings (ending in 88) is the server itself, no player app is installed on it.