# Only indirect access via relay dispite correct setup

**URL:** <https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091>\
**Category:** Remote Access\
**Tags:** server-linux, server-docker, plex-web\
**Created:** [January 3, 2026, 2:38pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091 "2026-01-03T14:38:31Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mats\_lu](https://avatars.discourse-cdn.com/v4/letter/m/e8c25b/32.png) [@mats\_lu](https://forums.plex.tv/u/mats_lu)\
**Post date:** [January 3, 2026, 2:38pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/1 "2026-01-03T14:38:31Z")

</div>

Server Version#: 1.2.20 Plex Pass docker image  
Player Version#: web player, latest ios and android client.

Hi, I’ve just set up a PMS instance on Truenas Scale using their “Apps” (which is Docker). This instance will replace another instance that I ran as a VM on another machine.

I shutdown the old one, changed the dest ip on the fw and nat rules and added all the libraries to the new one and tried to publish it.

Unfortunately even though the port-forwarding is enabled and Plex recognizes that Remote Access is working, I’m unable to access the server from the internet using the ios/android apps and the [plex.tv/desktop](http://plex.tv/desktop) interface with a direct connection. Only indirect/relay is possible.

I’ve redacted my emailadress and public ip from the logs.

 ![indirect](https://global.discourse-cdn.com/plex/original/4X/f/8/0/f80dee66bf303e9a2f4c776d4ea9c74714f156a3.png)

[Plex Media Server Logs\_2026-01-03\_15-25-59.zip](https://forums.plex.tv/uploads/short-url/aOHmE6dIiHUcHu2aFy5IglpjQS8.zip) (52.8 KB)

 ![remote access](https://global.discourse-cdn.com/plex/original/4X/b/7/e/b7ec6dd54d611cd16d6e57ff963a821700ba19b8.jpeg)

What have I missed?

---

<div class="post-metadata">

**Author:** ![veeejay](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@veeejay](https://forums.plex.tv/u/veeejay)\
**Post date:** [January 3, 2026, 2:49pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/2 "2026-01-03T14:49:47Z")

</div>

Put the container into host mode during the config on the TrueNAS, it’s a checkbox on one of the screens. The 172.x.x.x private IP indicates you’re in bridge mode.

---

<div class="post-metadata">

**Author:** ![mats\_lu](https://avatars.discourse-cdn.com/v4/letter/m/e8c25b/32.png) [@mats\_lu](https://forums.plex.tv/u/mats_lu)\
**Post date:** [January 3, 2026, 2:54pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/3 "2026-01-03T14:54:11Z")

</div>

![host mode](https://global.discourse-cdn.com/plex/original/4X/b/b/c/bbc381cb38d1c61061e2af9816bde35eded1a482.png)

This one? But if I can access the instance using the NAS IP, isn’t the network working?

---

<div class="post-metadata">

**Author:** ![veeejay](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@veeejay](https://forums.plex.tv/u/veeejay)\
**Post date:** [January 3, 2026, 2:56pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/4 "2026-01-03T14:56:50Z")

</div>

Yes.

You’re accessing it that way because the container has a mapping for the docker IP to be found. Plex doesn’t know that so it can’t be found at that 172 ip.

---

<div class="post-metadata">

**Author:** ![mats\_lu](https://avatars.discourse-cdn.com/v4/letter/m/e8c25b/32.png) [@mats\_lu](https://forums.plex.tv/u/mats_lu)\
**Post date:** [January 3, 2026, 2:57pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/5 "2026-01-03T14:57:16Z")

</div>

I enabled “Host Network” and it immediately started working. Thank you!

BR

---

<div class="post-metadata">

**Author:** ![veeejay](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@veeejay](https://forums.plex.tv/u/veeejay)\
**Post date:** [January 3, 2026, 2:57pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/6 "2026-01-03T14:57:52Z")

</div>

Glad it’s working. You can make it work in Bridge mode, it’s just easier to put it in host.

---

<div class="post-metadata">

**Author:** ![mats\_lu](https://avatars.discourse-cdn.com/v4/letter/m/e8c25b/32.png) [@mats\_lu](https://forums.plex.tv/u/mats_lu)\
**Post date:** [January 3, 2026, 3:04pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/7 "2026-01-03T15:04:37Z")

</div>

Can you point me to the documentation to do that?

---

<div class="post-metadata">

**Author:** ![veeejay](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@veeejay](https://forums.plex.tv/u/veeejay)\
**Post date:** [January 3, 2026, 3:18pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/8 "2026-01-03T15:18:29Z")

</div>

You basically have to use the custom server access url field in the network settings and add [http://172.16.1.2:32400/](http://172.16.1.2:32400/) so that plex “advertises” that IP as the connection point. In the link below, it shows how to add it to the compose file. The AdvertiseIP variable maps to the custom server access field in the settings.

You also have to add your regular subnet and the docker subnet to the LAN networks field in the plex network settings so that Plex knows they are local and won’t treat your local devices as remote. This is a Plex Pass field, your username says you have one, so just keep that in mind in case you don’t see it.

> **[plexinc/pms-docker - Docker Image](https://hub.docker.com/r/plexinc/pms-docker/)**

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [April 3, 2026, 3:19pm UTC](https://forums.plex.tv/t/only-indirect-access-via-relay-dispite-correct-setup/935091/9 "2026-04-03T15:19:13Z")

</div>

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