Unable to connect clients to server after migration

Plex Media Server
1

I just moved my media server from Windows to Unraid. I did a fresh installation of Plex instead of copying the server. I can access the server web app with the IP address, but I can’t connect to the server from any Plex clients on the local network (Windows 10, Android phone, Nvidia Shield).

When I click on the server on the sidebar on Windows, it has this error:

“SERVER_NAME is currently unavailable.
Verify you have a network connection and that the server is online, or see our troubleshooting tips for further assistance.”

When I first attempted to use the Plex client after setting up the Plex docker, it listed both my old server and the new one. The names of the Plex servers are the same and the computer still has the same static IP address in the router.

Server Version#: 1.41.3.9314

2

If you used the same server friendly name then you’re getting a collision of old vs new

go to https://app.plex.tv/desktop/#!/settings/devices/pms

There you will see the old server entry and the new

REMOVE (delete) the old server entry.
Next, Force restart (stop/terminate then open fresh) as they will only pull the updated server info from Plex.tv at startup

3

I’ve already removed the old entry from that page. It was a few days ago, and since then I’ve re-installed the client, restarted the Plex docker, and rebooted the server.

I also removed the new server when I removed the old server, and then it reappeared on the list.

What are you saying I should force restart, the client or the server?

4

I just found that I’m getting a different error if I use app.plex.tv instead of the desktop client.

Screenshot 2025-01-28 234956
Screenshot 2025-01-28 234956743×454 39.1 KB

5

Force restart the client apps (the app in the TV, phone, tablet, etc).
but that won’t apply in this case.

Every time you open Plex/web, it’s a fresh start

Looking at your Plex.tv account, the server is not Published.
The clients can’t see an unpublished server.

Created     11 days ago 
Last Seen   15 minutes ago 
Published   No

The easy way to Publish is to enable Remote Access for a minute.
If you don’t want to do that, the is a Preferences.xml setting to tell PMS to publish.

What’s your preference?

6

I can try enable remote access in settings, but it doesn’t work, I believe the problem is that I’m on a CGNAT. Does that mean I have to use the xml?

7

Can you get to Preferences.xml from the command line?

If so,

  1. stop Plex

  2. using your favorite/most comfortable editor

  3. Edit Preferences.xml

  4. Confirm this new Preference doesn’t already exist. (it shouldn’t)

  5. Go down to the last line, far right, before the closing />

  6. Add this preference (insert a space before and after)
    PublishServerOnPlexOnlineKey="1"

  7. Save Preferences.xnl

  8. Start PMS

  9. Give it a moment to publish

  10. Now restart one of the client apps (or use app.plex.tv)

8

That setting is already in Preferences.xml. PublishServerOnPlexOnlineKey="1"

9

Whatever you just did, It now shows as published to a 4.x.x.x address. Is that correct?

10

That’s the correct address. I enabled the remote access setting, and it says “Not available outside your network.” But the client is still unable to connect.

11

Do you know anything else I could try to fix this?

12

Is this the LAN address of your server?

Local Addresses 172.17.0.8

I so, what is the LAN address for your WiFi / home devices ?

13

I don’t what a “LAN address” is, but that’s the “private” address in Remote Access settings. How can I find that on Windows?

14

@ChuckPa are you official Plex support? I need help.

15

@D3r3k23

I am the resident “old fart” and troll. lol

First:
There are multiple terms floating around which mean the same thing:

  1. WAN address / Public address – the IP address your ISP gives you
  2. LAN address / Private address – the IP address you assign to your equipment on your home network.
  3. Bridge / container addresses – Addresses created by software , such as Docker / containers so they have their own private network within your private (LAN) network

I look at plex.tv. I see your server is at 172.17.0.29 (This is a docker-created IP address)

In the container’s Network setting, are you using the ‘Host’ or ‘Bridge’ setting value ?

16

Thanks for the explanation. The terminology can be very confusing!

172.17.0.29 is the address for the docker container and it’s using bridge.

I so, what is the LAN address for your WiFi / home devices ?

I used my router to assign 192.168.50.82 to the machine running the Plex docker, is that what you were asking?

17

I offer a suggestion for you which will make life much easier.

  1. Change the network configuration of the container to HOST

  2. This will remove the network address double layer you have.

  3. After doing this, your server will be accessible at the host’s IP address
    http://192.168.50.82:32400/web

  4. Remote access will now be able to talk to your router directly.

  5. LAN (home network clients) will see the server as “local” (same network)

  6. PMS will see only one address translation ( ISP → 192.168.50.82 ) which is how it’s supposed to work.

18

I got it working by simply adding the IP to the Custom Server Access URLs setting! I went back and checked the container documentation and it does mention this.

I’m currently running Tailscale in the container, which only works with a bridge network. Would you still recommend using a host network for any reason?

I had assumed that the problem was a conflict with the old and new server, but now it seems like that wasn’t an issue at all. Thanks for the help!

19

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.