Bridged mode trouble

[SecureBot]

When running in bridged mode, the docker container IP gets published to Plex instead of the server IP hosting docker. This gives users the unreachable server error when trying to connect to their server.

If you'd be able to get to the remote access tab, you would see something like this:
Private 172.17.0.2:32400 <- Public External.IP.Address <- Internet

When you would really want to see something like this:
Private 192.168.1.15:32400 <- Public External.IP.Address <- Internet

You can fix running in bridged mode by adding customConnections=" https://docker.host.ip:32400" to preferences.xml

I've tried this, but it still doesn't work for me, it still can't find anything. There should be a possibility to manually specify a server, but apparently it's not available when no server can be found :O...

Did this break with the new plex pass changes?

btw @SecureBot by https://docker.host.ip:32400 you mean the ip of the machine running the docker container, or the ip of the interface that docker creates for the containers?

[SecureBot]

@ismay How long did you give it before you tried and have you restarted the
container?

Go to https://plex.tv/pms/resources.xml and it will show you info about
your server. If running in bridged mode, there should be 3 IP's listed...
Your Docker container IP, Docker host machine IP, and your public IP. If
all three aren't listed, check to make sure the line you put in
preferences.xml conforms to the format of other entries.

Also, I do mean the ip of the machine running the docker container.

There is a harder way to get access to your server to configure it. You can
set up an SSH tunnel to your Docker server and configure your browsers
proxy settings to use the tunnel.

On Thu, May 12, 2016 at 8:01 AM, Ismay notifications@github.com wrote:

I've tried this, but it doesn't work for me. It still doesn't find the
server. There should be a possibility to manually specify a server
https://forums.plex.tv/discussion/175252/manually-add-server-by-ip-hostname,
but apparently it's not available when no server can be found :O...

Did this break with the new plex pass changes?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#36 (comment)

How long did you give it before you tried and have you restarted the
container?

Pretty long, at least 5 minutes, and I've tried it several times.

Go to https://plex.tv/pms/resources.xml and it will show you info about
your server.

Well that's the problem, the plex webinterface can't find my server. So when I go to https://plex.tv/pms/resources.xml it only shows my phone (which I used to register). Nothing else unfortunately.

check to make sure the line you put in preferences.xml conforms to the format of other entries.

I've added the customConnections=" https://docker.host.ip:32400" line to my server's Preferences.xml as an attribute (like the other entries). Could you give me an exact copy of your entire Preferences.xml, just so I can check what it's supposed to look like?

Also, I do mean the ip of the machine running the docker container.

Ok, yeah that's what I thought (and used).

There is a harder way to get access to your server to configure it. You can
set up an SSH tunnel to your Docker server and configure your browsers
proxy settings to use the tunnel.

Well the problem isn't accessing the webinterface. I can access that just fine at myserverip:32400/web. The problem is that the plex web interface can't find a plex server running on my network (which is the same server and docker container as the plex webinterface). And there doesn't seem to be a way to manually specify a server ip..

By the way, my docker interface is bridged with the docker host's interface, and I've forwarded all the relevant ports from the docker container:

docker create \
    --name=plex \
    -p 32400:32400 \
    -p 32400:32400/udp \
    -p 32469:32469 \
    -p 32469:32469/udp \
    -p 5353:5353/udp \
    -p 1900:1900/udp
    -e VERSION=latest \
    -e PUID=1000 -e PGID=1000 \
    -v /config:/config \
    -v /tvseries:/data/tvshows \
    -v /movies:/data/movies \
    linuxserver/plex

So I can access myserverip:32400/web for example from my local network. It's just that plex can't find itself it seems.

[SecureBot]

Your docker create config looks good. Your problem with accessing
myserverip:32400/web and it showing the web interface, but unable to find
the server is what I expect and is the same problem I had. Adding the
customconnections is what fixes that, but I think we are getting ahead of
ourselves, considering what you are seeing in your resources.xml.

It appears that your IP's aren't being published to your plex account. In
your preferences.xml do you see your token? (don't post it here). I had a
problem that even though I logged into my server from
myserverip:32400/web... it was never truly linked to my account. If your
token isn't in your preferences.xml, that where we'll need to start.

Also, post what you can from the log. Run: "docker logs -f plex"

Unfortunately, I wont have access to my server for another few hours, so I
can't show you my preferences.xml yet.

On Thu, May 12, 2016 at 8:51 AM, Ismay notifications@github.com wrote:

By the way, my docker interface is bridged with the docker host's
interface, and I've forwarded all the relevant ports from the docker
container:

docker create
--name=plex
-p 32400:32400
-p 32400:32400/udp
-p 32469:32469
-p 32469:32469/udp
-p 5353:5353/udp
-p 1900:1900/udp
-e VERSION=latest
-e PUID=1000 -e PGID=1000
-v /config:/config
-v /tvseries:/data/tvshows
-v /movies:/data/movies
linuxserver/plex

So I can access myserverip:32400/web for example from my local network

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#36 (comment)

In your preferences.xml do you see your token? Also, post what you can from the log. Run: "docker logs -f plex"

Ok cool, I'll do that when I'm home, will let you know what I find.

Also, maybe my routers firewall is blocking plex's attempts to publish my local plex server ip to my plex account (so to the main plex.tv server). But I have no blocks on outgoing connections though. Are there any protocols (like upnp) that need to be enabled, or incoming ports that need to be forwarded for this to work?

[SecureBot]

Yes, you'll want setup port forwarding. The most important port to forward
is 32400.
https://support.plex.tv/hc/en-us/articles/201543147-What-network-ports-do-I-need-to-allow-through-my-firewall-

Here is a guide for setting up an SSH tunnel with putty. If you do this,
you'll likely get access to your server while the tunnel is open. It's a
temporary solution, but it enables you to login to your server and get the
IP published to your account. The token should then get pulled into your
preferences.xml and the plexpass version should then download and
install the next time you restart the container.
https://anapnea.net/tut_putty_tunneling.php

On Thu, May 12, 2016 at 10:38 AM, Ismay notifications@github.com wrote:

In your preferences.xml do you see your token? Also, post what you can
from the log. Run: "docker logs -f plex"

Ok cool, I'll do that when I'm home, will let you know what I find.

Also, maybe my routers firewall is blocking plex's attempts to publish my
local plex server ip to my plex account (so to the main plex.tv server).
But I have no blocks on outgoing connections though. Are there any
protocols (like upnp), or incoming ports that need to be forwarded for this
to work?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#36 (comment)

Apparently the port forwarding is requested by plex through upnp. I'll set that up as well.

So the contents of my preferences.xml are:

<?xml version="1.0" encoding="utf-8"?>
<Preferences customConnections="192.168.1.5:32400" MachineIdentifier="[number here]" ProcessedMachineIdentifier="[number here]" AnonymousMachineIdentifier="[number here]" agentAutoEnabled.com.plexapp.agents.lastfm.Artists.com.plexapp.agents.vevo="1" MetricsEpoch="1" GracenoteUser="[number here]"/>

Is the machineidentifier the token? Also I tried not specifying a protocol for the custom connection since I can only access the webinterface over http. These are the plex container logs:

-------------------------------------
          _     _ _
         | |___| (_) ___
         | / __| | |/ _ \
         | \__ \ | | (_) |
         |_|___/ |_|\___/
               |_|

Brought to you by linuxserver.io
We do accept donations at:
https://www.linuxserver.io/donations
-------------------------------------
GID/UID
-------------------------------------
User uid:    1000
User gid:    1000
-------------------------------------

*** Running /etc/my_init.d/10_dbus.sh...
*** Running /etc/my_init.d/20_apt_update.sh...
*** Running /etc/my_init.d/30_update_plex.sh...
Plex token not avalible, please login
*** Running /etc/my_init.d/90_chown_plex_owned_files.sh...
*** Running /etc/my_init.d/999_advanced_script.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 31
Starting dbus-daemon
Starting Avahi daemon
Starting Plex Media Server.
Found user 'avahi' (UID 104) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.31 starting up.
dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
WARNING: Failed to contact D-Bus daemon.
avahi-daemon 0.6.31 exiting.
6 3000 /config/Library/Application Support
8192
May 12 21:15:33 61e08b0588d0 syslog-ng[41]: syslog-ng starting up; version='3.5.3'
Starting Avahi daemon
Found user 'avahi' (UID 104) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.31 starting up.
No service file found in /etc/avahi/services.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::42:acff:fe11:3.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 172.17.0.3.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::42:acff:fe11:3 on eth0.*.
Registering new address record for 172.17.0.3 on eth0.IPv4.
Registering HINFO record with values 'X86_64'/'LINUX'.
Server startup complete. Host name is 61e08b0588d0.local. Local service cookie is 1888772992.
May 12 21:17:01 61e08b0588d0 /USR/SBIN/CRON[165]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

[SecureBot]

Your token is not there. If you look at the beginning of your log, it says
that it was not found. Try the SSH tunnel, which let you log in to claim
the server.
On May 12, 2016 5:27 PM, "Ismay" notifications@github.com wrote:

So the contents of my preferences.xml are:

Is the machineidentifier the token? Also I tried not specifying a protocol
for the custom connection since I can only access the webinterface over
http. These are the plex container logs:

---

      _     _ _
     | |___| (_) ___
     | / __| | |/ _ \
     | \__ \ | | (_) |
     |_|___/ |_|\___/
           |_|

Brought to you by linuxserver.io

We do accept donations at:https://www.linuxserver.io/donations

GID/UID

User uid: 1000

User gid: 1000

*** Running /etc/my_init.d/10_dbus.sh...
*** Running /etc/my_init.d/20_apt_update.sh...
*** Running /etc/my_init.d/30_update_plex.sh...
Plex token not avalible, please login
*** Running /etc/my_init.d/90_chown_plex_owned_files.sh...
*** Running /etc/my_init.d/999_advanced_script.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 31
Starting dbus-daemon
Starting Avahi daemon
Starting Plex Media Server.
Found user 'avahi' (UID 104) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.31 starting up.
dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
WARNING: Failed to contact D-Bus daemon.
avahi-daemon 0.6.31 exiting.
6 3000 /config/Library/Application Support
8192
May 12 21:15:33 61e08b0588d0 syslog-ng[41]: syslog-ng starting up; version='3.5.3'
Starting Avahi daemon
Found user 'avahi' (UID 104) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.31 starting up.
No service file found in /etc/avahi/services.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::42:acff:fe11:3.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 172.17.0.3.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::42:acff:fe11:3 on eth0.*.
Registering new address record for 172.17.0.3 on eth0.IPv4.
Registering HINFO record with values 'X86_64'/'LINUX'.
Server startup complete. Host name is 61e08b0588d0.local. Local service cookie is 1888772992.
May 12 21:17:01 61e08b0588d0 /USR/SBIN/CRON[165]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#36 (comment)

Try the SSH tunnel, which let you log in to claim the server.

Hmm, I've tried to open an ssh tunnel to the docker host with

ssh -D 32400 -C -N username@dockerhost.mydomain.net

But that doesn't work (connection refused). The host (dockerhost.mydomain.net) can be pinged and I can open a regular ssh connection to it (ssh username@dockerhost.mydomain.net) over port 22.

I've also tried using the net: host flag when creating the docker btw. Same errors. I really have no idea where this is going wrong. The complete scripts I use to set everything up are pre and post. It seems like I'm following all the instructions to the letter, and that there is just a bug in the current version of the container or I'm missing something.

It seems I'm not the only one wrestling with plex and docker in bridged mode: https://blog.ostanin.org/2013/09/14/plex-media-server-in-docker/

[SecureBot]

Port 32400 is already used by Plex. Try 9090. Your SSH connection is still
connecting over port 22, but you want to open a tunnel on port 9090. Then
you configure your web browser to use port 9090 as a proxy. This makes it
so that you essentially have a more direct connection to the server. Right
now you are connecting to Plex like this: container.ip < docker.host.ip <
your.ip. creating an SSH tunnel takes your IP out of the chain.

Try the SSH tunnel, which let you log in to claim the server.

Hmm, I've tried to open an ssh tunnel to the docker host with

ssh -D 32400 -C -N username@dockerhost.mydomain.net

But that doesn't work (connection refused). The host (
dockerhost.mydomain.net) can be pinged and I can open a regular ssh
connection to it (ssh username@dockerhost.mydomain.net) over port 22.

I've also tried using the net: host flag when creating the docker btw. Same
errors. I really have no idea where this is going wrong. The complete
scripts I use to set everything up are pre
https://github.com/ismay/scripts/blob/master/ubuntu.pre.sh and post
https://github.com/ismay/scripts/blob/master/ubuntu.post.sh. It seems
like I'm following all the instructions to the letter, and that there is
just a bug in the current version of the container or I'm missing something.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#36 (comment)

Ok, so finally some progress. Using this command on a laptop on my local network (but not on the server that's running the plex docker):

ssh -L 8080:localhost:32400 user@dockerhost.mydomain.net

I can connect to the plex server by accessing localhost:8080/web from the laptop, and the setup goes fine. It can find my server, I can stream media, everything.

However, after finishing the setup and saving the server etc., when I close the ssh tunnel, the settings are retained, but the connection to the plex server is lost again.

My resources.xml now looks like this:

<MediaContainer size="1">
<Device name="Plex Server" product="Plex Media Server" productVersion="0.9.16.6.1993-5089475" platform="Linux" platformVersion="4.2.0-36-generic (#41~14.04.1-Ubuntu SMP Tue Apr 19 17:03:32 UTC 2016)" device="PC" clientIdentifier="[myidentifier]" createdAt="1463155827" lastSeenAt="1463155832" provides="server" owned="1" httpsRequired="0" synced="0" publicAddressMatches="1" presence="1">
<Connection protocol="http" address="172.17.0.3" port="32400" uri="http://172.17.0.3:32400" local="1"/>
</Device>
</MediaContainer>

So the ip it's publishing is the ip of my docker container, and not that of my actual server (which is 192.168.1.5).