Media and Server Not Visible From Most LAN Devices

Plex Media Server
,
1

Server Version#:1.43.0.10467
Player Version#:4.157.0

I have been having an issue over about the last two months where I am unable to see my server dashboard or media on most local connections. In every event that this has occurred cellular data via WAN connection has shown my media without issue.

Devices (desktop, laptop, appleTV app, and phone) on the same subnet as the plex server when the issue arise are unable to see the server dashboard or media via http://IP:port or https://IP:port.

https://app.plex.tv/desktop also fails to show the server or any media.

I have also followed the information at https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/ to make the suggested changes to my firewall to allow secure connections.

Stopping the docker container then starting it temporarily resolves the issue.

I’m unsure what is happening but I haven’t made any changes to my networking setup in a while and Plex was previously working without issue for years before this.

2

Plex Media Server Logs_2026-01-30_15-21-17.zip (5.3 MB)

Here are my server logs if they are needed.

3

DNS inside the docker cannot resolve plex.tv addresses and you are not running the docker in host mode so no the server is not on the same subnet as the rest of your network.

4

If the only alternative was using bridge I would agree, but I was giving it it’s own IP address via custom network type, however I did see the suggested type is host so it has been changed to host.

I have also added an extra parameter to specify DNS.

Is there a way to test DNS from the docker itself so I can verify correct DNS?

5

exec into the container (it’s shell)

curl http://plex.tv

If DNS is resolving, you see this output

Screenshot from 2026-01-30 20-43-06
Screenshot from 2026-01-30 20-43-06766×510 36.8 KB

6

Appreciate it.

I was able to test with the curl command and got that response.

Since you have it working in unraid from your screen shot is there any reason that using a custom network type and specifying a different IP would not work, assuming DNS is resolving?

7

On Unraid, I run HOST networking.
I tried bridge but it didn’t like it.
(too many dns and gateway crossing issues)

One option for you is HOST, with an ADVERTISE_IP (see the docker docs).

If Unraid supports it as regular Linux does, this creates a second IP attached to the host IP.

It uses the same mechanism in the network stack as IPv4 + IPv6

8

So it appears that Unraid does not use the advertise IP command to set a different IP. I attempted that path again and it immediately broke.

So it looks like the only real option is to use host.

Appreciate all the assistance with this.