New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridged mode trouble #36

Closed
SecureBot opened this Issue Apr 28, 2016 · 41 comments

Comments

Projects
None yet
8 participants
@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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 12, 2016

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?

ismay commented May 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 12, 2016

@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)

@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)

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 12, 2016

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..

ismay commented May 12, 2016

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..

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 12, 2016

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.

ismay commented May 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 12, 2016

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)

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)

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 12, 2016

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?

ismay commented May 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 12, 2016

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)

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)

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 12, 2016

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

ismay commented May 12, 2016

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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 12, 2016

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)

ismay commented May 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 12, 2016

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)

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)

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

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.

ismay commented May 13, 2016

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.

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

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/

ismay commented May 13, 2016

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

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

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)

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)

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

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.

ismay commented May 13, 2016

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.

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

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).

ismay commented May 13, 2016

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).

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

Maybe it makes sense that it's doing that, because the plex server can only see the interface that docker provides (as I understand it), and that interface has the ip that it's publishing in resources.xml. I don't know however how to force it to use the ip of the docker host instead of the docker container.

Also, I don't understand what the difference is between your setup and mine, because yours works apparently, but mine is a pretty standard docker setup (because a bridge is the docker standard way of dealing with networking) and it doesn't work.

ismay commented May 13, 2016

Maybe it makes sense that it's doing that, because the plex server can only see the interface that docker provides (as I understand it), and that interface has the ip that it's publishing in resources.xml. I don't know however how to force it to use the ip of the docker host instead of the docker container.

Also, I don't understand what the difference is between your setup and mine, because yours works apparently, but mine is a pretty standard docker setup (because a bridge is the docker standard way of dealing with networking) and it doesn't work.

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Great! Now what IP's are listed under https://plex.tv/pms/resources.xml

The goal is to get your docker server IP listed in addition to your Plex
container IP.
On May 13, 2016 12:36 PM, "Ismay" notifications@github.com wrote:

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.


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

Great! Now what IP's are listed under https://plex.tv/pms/resources.xml

The goal is to get your docker server IP listed in addition to your Plex
container IP.
On May 13, 2016 12:36 PM, "Ismay" notifications@github.com wrote:

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.


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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

<Connection protocol="http" address="172.17.0.3" port="32400" uri="http://172.17.0.3:32400" local="1"/>
<Connection protocol="http" address="192.168.1.5" port="32400" uri="http://192.168.1.5:32400" local="1"/>
<Connection protocol="https" address="192.168.1.5" port="32400" uri="https://192.168.1.5:32400" local="1"/>

The last two I've added manually (for the entire contents see above). Doesn't make a difference unfortunately. Still can't connect to the server without the tunnel.

ismay commented May 13, 2016

<Connection protocol="http" address="172.17.0.3" port="32400" uri="http://172.17.0.3:32400" local="1"/>
<Connection protocol="http" address="192.168.1.5" port="32400" uri="http://192.168.1.5:32400" local="1"/>
<Connection protocol="https" address="192.168.1.5" port="32400" uri="https://192.168.1.5:32400" local="1"/>

The last two I've added manually (for the entire contents see above). Doesn't make a difference unfortunately. Still can't connect to the server without the tunnel.

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Did you manually edit resources.XML? We should see your public IP listed
which doesn't seem to be the case. When you set up port forwarding on your
router, what destination IP did you put?
On May 13, 2016 12:57 PM, "Ismay" notifications@github.com wrote:

The last two I've added manually (for the entire contents see above).
Doesn't make a difference unfortunately.


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

Did you manually edit resources.XML? We should see your public IP listed
which doesn't seem to be the case. When you set up port forwarding on your
router, what destination IP did you put?
On May 13, 2016 12:57 PM, "Ismay" notifications@github.com wrote:

The last two I've added manually (for the entire contents see above).
Doesn't make a difference unfortunately.


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

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Also, have you restarted the container since you've made changes?
On May 13, 2016 12:57 PM, "Ismay" notifications@github.com wrote:

The last two I've added manually (for the entire contents see above).
Doesn't make a difference unfortunately.


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

Also, have you restarted the container since you've made changes?
On May 13, 2016 12:57 PM, "Ismay" notifications@github.com wrote:

The last two I've added manually (for the entire contents see above).
Doesn't make a difference unfortunately.


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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

Did you manually edit resources.XML?

No, I've just added it through the plex settings.

We should see your public IP listed which doesn't seem to be the case.

Only if I want to connect from outside my network right? Or is that necessary thing for local discovery as well?

When you set up port forwarding on your router, what destination IP did you put?

I've only set up upnp, and am allowing everything by default. So plex should be able to request its own port forwarding.

ismay commented May 13, 2016

Did you manually edit resources.XML?

No, I've just added it through the plex settings.

We should see your public IP listed which doesn't seem to be the case.

Only if I want to connect from outside my network right? Or is that necessary thing for local discovery as well?

When you set up port forwarding on your router, what destination IP did you put?

I've only set up upnp, and am allowing everything by default. So plex should be able to request its own port forwarding.

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

Also, have you restarted the container since you've made changes?

Nope, not yet. Should I?

ismay commented May 13, 2016

Also, have you restarted the container since you've made changes?

Nope, not yet. Should I?

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Oh, right I was assuming you wanted remote access. I have had luck with
upnp, and I'm not sure you can use it since the container ports are
specified in your container creation config. I would manually specify 32400
and port forward to your 192.168.1.5 address.
On May 13, 2016 1:06 PM, "Ismay" notifications@github.com wrote:

Also, have you restarted the container since you've made changes?

Nope, not yet. Should I?


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

Oh, right I was assuming you wanted remote access. I have had luck with
upnp, and I'm not sure you can use it since the container ports are
specified in your container creation config. I would manually specify 32400
and port forward to your 192.168.1.5 address.
On May 13, 2016 1:06 PM, "Ismay" notifications@github.com wrote:

Also, have you restarted the container since you've made changes?

Nope, not yet. Should I?


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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

Oh, right I was assuming you wanted remote access.

It's definitely something I'd want in the future, but for now I'm trying to get plex to find itself without the ssh tunnel. I think the remote access should be doable after that :).

ismay commented May 13, 2016

Oh, right I was assuming you wanted remote access.

It's definitely something I'd want in the future, but for now I'm trying to get plex to find itself without the ssh tunnel. I think the remote access should be doable after that :).

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Try restarting the container now that you were able to log in. Then post
your preferences XML and an update of the server log and we can see where
we're at.
On May 13, 2016 1:22 PM, "Ismay" notifications@github.com wrote:

Oh, right I was assuming you wanted remote access.

It's definitely something I'd want in the future, but for now I'm trying
to get access to the server without the ssh tunnel. I think the remote
access should be doable after that :).


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

Try restarting the container now that you were able to log in. Then post
your preferences XML and an update of the server log and we can see where
we're at.
On May 13, 2016 1:22 PM, "Ismay" notifications@github.com wrote:

Oh, right I was assuming you wanted remote access.

It's definitely something I'd want in the future, but for now I'm trying
to get access to the server without the ssh tunnel. I think the remote
access should be doable after that :).


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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

Allright, so after a restart it remembers the server, but still can't connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Preferences.xml

<?xml version="1.0" encoding="utf-8"?>
<Preferences customConnections="http://192.168.1.5, https://192.168.1.5" MachineIdentifier="[removed]" ProcessedMachineIdentifier="[removed]" AnonymousMachineIdentifier="[removed]" agentAutoEnabled.com.plexapp.agents.lastfm.Artists.com.plexapp.agents.vevo="1" MetricsEpoch="1" GracenoteUser="[removed]" AcceptedEULA="1" FriendlyName="Plex Server" PlexOnlineToken="[removed]" PlexOnlineUsername="[removed]" PlexOnlineMail="[removed]" CertificateVersion="2" PubSubServerPing="49" PublishServerOnPlexOnlineKey="0" LastAutomaticMappedPort="0" LanguageInCloud="1" ManualPortMappingMode="0"/>

ismay commented May 13, 2016

Allright, so after a restart it remembers the server, but still can't connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Preferences.xml

<?xml version="1.0" encoding="utf-8"?>
<Preferences customConnections="http://192.168.1.5, https://192.168.1.5" MachineIdentifier="[removed]" ProcessedMachineIdentifier="[removed]" AnonymousMachineIdentifier="[removed]" agentAutoEnabled.com.plexapp.agents.lastfm.Artists.com.plexapp.agents.vevo="1" MetricsEpoch="1" GracenoteUser="[removed]" AcceptedEULA="1" FriendlyName="Plex Server" PlexOnlineToken="[removed]" PlexOnlineUsername="[removed]" PlexOnlineMail="[removed]" CertificateVersion="2" PubSubServerPing="49" PublishServerOnPlexOnlineKey="0" LastAutomaticMappedPort="0" LanguageInCloud="1" ManualPortMappingMode="0"/>
@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

When you SSH in and connect to the server, try logging out and logging back
in. Go to the devices tab. Is your server listed?
On May 13, 2016 2:21 PM, "Ismay" notifications@github.com wrote:

Allright, so after a restart it remembers the server, but still can't
connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Preferences.xml


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

When you SSH in and connect to the server, try logging out and logging back
in. Go to the devices tab. Is your server listed?
On May 13, 2016 2:21 PM, "Ismay" notifications@github.com wrote:

Allright, so after a restart it remembers the server, but still can't
connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Preferences.xml


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

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Also what does your remote access tab look like? And when you sign in, are
you clicking on the Server>General tab to do it?

When you SSH in and connect to the server, try logging out and logging
back in. Go to the devices tab. Is your server listed?
On May 13, 2016 2:21 PM, "Ismay" notifications@github.com wrote:

Allright, so after a restart it remembers the server, but still can't
connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Preferences.xml


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

SecureBot commented May 13, 2016

Also what does your remote access tab look like? And when you sign in, are
you clicking on the Server>General tab to do it?

When you SSH in and connect to the server, try logging out and logging
back in. Go to the devices tab. Is your server listed?
On May 13, 2016 2:21 PM, "Ismay" notifications@github.com wrote:

Allright, so after a restart it remembers the server, but still can't
connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Preferences.xml


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

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

And under Network tab, what's listed under custom server access URLs?

Also what does your remote access tab look like? And when you sign in, are
you clicking on the Server>General tab to do it?
On May 13, 2016 2:54 PM

When you SSH in and connect to the server, try logging out and logging
back in. Go to the devices tab. Is your server listed?
On May 13, 2016 2:21 PM, "Ismay" notifications@github.com wrote:

Allright, so after a restart it remembers the server, but still can't
connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Preferences.xml


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

SecureBot commented May 13, 2016

And under Network tab, what's listed under custom server access URLs?

Also what does your remote access tab look like? And when you sign in, are
you clicking on the Server>General tab to do it?
On May 13, 2016 2:54 PM

When you SSH in and connect to the server, try logging out and logging
back in. Go to the devices tab. Is your server listed?
On May 13, 2016 2:21 PM, "Ismay" notifications@github.com wrote:

Allright, so after a restart it remembers the server, but still can't
connect. 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...
Target version: 0.9.16.6.1993-5089475 set by: latest\plexpass
No need to update!
‘/defaults/plexmediaserver’ -> ‘/etc/default/plexmediaserver’
*** 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 35
Starting Plex Media Server.
Starting Avahi daemon
Starting dbus-daemon
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 13 18:13:31 61e08b0588d0 syslog-ng[45]: 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 3175600444.
May 13 18:17:01 61e08b0588d0 /USR/SBIN/CRON[206]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Preferences.xml


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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

The problem is the docker0 bridge on the host. With the setting --net=host, after taking the docker bridge down on the docker host (sudo ip link set docker0 down), everything works as expected (except networking for my other containers of course).

If I restore the docker bridge it can't find the server anymore.

ismay commented May 13, 2016

The problem is the docker0 bridge on the host. With the setting --net=host, after taking the docker bridge down on the docker host (sudo ip link set docker0 down), everything works as expected (except networking for my other containers of course).

If I restore the docker bridge it can't find the server anymore.

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 13, 2016

Strange, because --net=host should mean that networking is shared with the host. So the container shouldn't be dependant on the bridge for networking. Maybe some interference between the two interfaces?

ismay commented May 13, 2016

Strange, because --net=host should mean that networking is shared with the host. So the container shouldn't be dependant on the bridge for networking. Maybe some interference between the two interfaces?

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot May 13, 2016

Are you okay with using --net=host? I try to avoid it for security reasons.

When you try out the nethost enabled container, is the other bridged
container still running?
On May 13, 2016 3:50 PM, "Ismay" notifications@github.com wrote:

Strange, because --net=host should mean that networking is shared with the
host. So the container shouldn't be dependant on the bridge for networking.
Maybe some interference between the two interfaces?


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

Are you okay with using --net=host? I try to avoid it for security reasons.

When you try out the nethost enabled container, is the other bridged
container still running?
On May 13, 2016 3:50 PM, "Ismay" notifications@github.com wrote:

Strange, because --net=host should mean that networking is shared with the
host. So the container shouldn't be dependant on the bridge for networking.
Maybe some interference between the two interfaces?


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

@ismay

This comment has been minimized.

Show comment
Hide comment
@ismay

ismay May 16, 2016

Are you okay with using --net=host? I try to avoid it for security reasons.

I do too, which is why I tried getting it to work with the forwarded ports, but since this is the only way I could get it to work I'll just accept it.

When you try out the nethost enabled container, is the other bridged
container still running?

No I closed it. So but by by disabling the docker bridge for plex server detection and then enabling it afterwards, it works as expected. I do think that the port forwarding setup needs to to be revisited by the linuxserver.io team, because I think there are some bugs to be worked out.

The net=host setup does seem to work if you disable the bridge temporarily though.

ismay commented May 16, 2016

Are you okay with using --net=host? I try to avoid it for security reasons.

I do too, which is why I tried getting it to work with the forwarded ports, but since this is the only way I could get it to work I'll just accept it.

When you try out the nethost enabled container, is the other bridged
container still running?

No I closed it. So but by by disabling the docker bridge for plex server detection and then enabling it afterwards, it works as expected. I do think that the port forwarding setup needs to to be revisited by the linuxserver.io team, because I think there are some bugs to be worked out.

The net=host setup does seem to work if you disable the bridge temporarily though.

@lonix

This comment has been minimized.

Show comment
Hide comment
@lonix

lonix May 23, 2016

Contributor

The fact is the IP getting discovered by plex will be the contianer IP if you are running in bridge mode, this container is build on the premisse of running in host mode, due to excatly this, if anyone has a solution, let us know :)

Contributor

lonix commented May 23, 2016

The fact is the IP getting discovered by plex will be the contianer IP if you are running in bridge mode, this container is build on the premisse of running in host mode, due to excatly this, if anyone has a solution, let us know :)

@krohrsb

This comment has been minimized.

Show comment
Hide comment
@krohrsb

krohrsb Jun 16, 2016

Maybe something is different with my setup but I'm not having any problems. I ran it in --net=host mode as per instructions for quite a while, but figured I would try to remove that, and after removing (and setting up the proper port mappings) I can still connect fine remotely, plex can see the server etc.

Private 172.17.42.13:32400 <- Public 123.123.123.123: 32400 <- Internet Is what it reports (I am also connecting via a remote network at the moment)

I have 32400 forwarded on my router of course.

plex:
  image: linuxserver/plex
  container_name: plex
  hostname: plex
  #net: "host"
  ports:
    - 32400:32400/tcp
    - 1900:1900/udp
    - 8324:8324/tcp
    - 32410:32410/tcp
    - 32411:32411/tcp
    - 32412:32412/tcp
    - 32413:32413/tcp
    - 32414:32414/tcp
  volumes:
    - /opt/services/plex/config:/config
  volumes_from:
    - media-data
  environment:
    - VERSION=latest
    - PUID=110
    - PGID=1001

Docker opts are:
DOCKER_OPTS="-H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --bip=172.17.42.1/24 --dns=8.8.8.8 --dns=172.17.42.1"

Either my setup is unique that enables this or i'm reading the OP's issue wrong.

krohrsb commented Jun 16, 2016

Maybe something is different with my setup but I'm not having any problems. I ran it in --net=host mode as per instructions for quite a while, but figured I would try to remove that, and after removing (and setting up the proper port mappings) I can still connect fine remotely, plex can see the server etc.

Private 172.17.42.13:32400 <- Public 123.123.123.123: 32400 <- Internet Is what it reports (I am also connecting via a remote network at the moment)

I have 32400 forwarded on my router of course.

plex:
  image: linuxserver/plex
  container_name: plex
  hostname: plex
  #net: "host"
  ports:
    - 32400:32400/tcp
    - 1900:1900/udp
    - 8324:8324/tcp
    - 32410:32410/tcp
    - 32411:32411/tcp
    - 32412:32412/tcp
    - 32413:32413/tcp
    - 32414:32414/tcp
  volumes:
    - /opt/services/plex/config:/config
  volumes_from:
    - media-data
  environment:
    - VERSION=latest
    - PUID=110
    - PGID=1001

Docker opts are:
DOCKER_OPTS="-H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --bip=172.17.42.1/24 --dns=8.8.8.8 --dns=172.17.42.1"

Either my setup is unique that enables this or i'm reading the OP's issue wrong.

@SecureBot

This comment has been minimized.

Show comment
Hide comment
@SecureBot

SecureBot Jun 16, 2016

Mine works, but I had to do some extra step to get it there. They key part
is getting your Docker server IP published to Plex. Yours was likely
already published to Plex since you started in host mode and switched to
bridged.

I think there should be a script that ensures the container IP, docker
server IP, and public IP all get published to Plex.

On Thu, Jun 16, 2016 at 1:02 PM, Kyle Brown notifications@github.com
wrote:

Maybe something is different with my setup but I'm not having any
problems. I ran it in --net=host mode as per instructions for quite a
while, but figured I would try to remove that, and after removing (and
setting up the proper port mappings) I can still connect fine remotely,
plex can see the server etc.

Private 172.17.42.13:32400 <- Public 123.123.123.123: 32400 <- Internet
Is what it reports (I am also connecting via a remote network at the moment)

I have 32400 forwarded on my router of course.

plex:
image: linuxserver/plex
container_name: plex
hostname: plex
#net: "host"
ports:
- 32400:32400/tcp
- 1900:1900/udp
- 8324:8324/tcp
- 32410:32410/tcp
- 32411:32411/tcp
- 32412:32412/tcp
- 32413:32413/tcp
- 32414:32414/tcp
volumes:
- /opt/services/plex/config:/config
volumes_from:
- media-data
environment:
- VERSION=latest
- PUID=110
- PGID=1001

Docker opts are:
DOCKER_OPTS="-H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --bip=
172.17.42.1/24 --dns=8.8.8.8 --dns=172.17.42.1"

Either my setup is unique that enables this or i'm reading the OP's issue
wrong.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#36 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AKt4L3pT0SuyWhmJYQ8QvTDTjB-PTIejks5qMYHBgaJpZM4IRd7g
.

Mine works, but I had to do some extra step to get it there. They key part
is getting your Docker server IP published to Plex. Yours was likely
already published to Plex since you started in host mode and switched to
bridged.

I think there should be a script that ensures the container IP, docker
server IP, and public IP all get published to Plex.

On Thu, Jun 16, 2016 at 1:02 PM, Kyle Brown notifications@github.com
wrote:

Maybe something is different with my setup but I'm not having any
problems. I ran it in --net=host mode as per instructions for quite a
while, but figured I would try to remove that, and after removing (and
setting up the proper port mappings) I can still connect fine remotely,
plex can see the server etc.

Private 172.17.42.13:32400 <- Public 123.123.123.123: 32400 <- Internet
Is what it reports (I am also connecting via a remote network at the moment)

I have 32400 forwarded on my router of course.

plex:
image: linuxserver/plex
container_name: plex
hostname: plex
#net: "host"
ports:
- 32400:32400/tcp
- 1900:1900/udp
- 8324:8324/tcp
- 32410:32410/tcp
- 32411:32411/tcp
- 32412:32412/tcp
- 32413:32413/tcp
- 32414:32414/tcp
volumes:
- /opt/services/plex/config:/config
volumes_from:
- media-data
environment:
- VERSION=latest
- PUID=110
- PGID=1001

Docker opts are:
DOCKER_OPTS="-H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --bip=
172.17.42.1/24 --dns=8.8.8.8 --dns=172.17.42.1"

Either my setup is unique that enables this or i'm reading the OP's issue
wrong.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#36 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AKt4L3pT0SuyWhmJYQ8QvTDTjB-PTIejks5qMYHBgaJpZM4IRd7g
.

@phillipuniverse

This comment has been minimized.

Show comment
Hide comment
@phillipuniverse

phillipuniverse Jan 6, 2017

Thanks @blackbarn! Setting those extra ports definitely worked for me. My use case was that I wanted Sonarr and Couchpotato (also running in Docker containers) to notify Plex on download. Since Plex was started up with host networking, that was difficult because for whatever reason I couldn't get the notifications to work with the host 172.17.0.1 it just wouldn't connect. But I couldn't use --link in my docker-compose because of host networking.

Adding all of your port mappings fixed it, and I can continue to use bridged mode (the default), I have my plex server fully accessible outside my network, and I can link my plex container to my other Docker containers.

Thanks again!

Thanks @blackbarn! Setting those extra ports definitely worked for me. My use case was that I wanted Sonarr and Couchpotato (also running in Docker containers) to notify Plex on download. Since Plex was started up with host networking, that was difficult because for whatever reason I couldn't get the notifications to work with the host 172.17.0.1 it just wouldn't connect. But I couldn't use --link in my docker-compose because of host networking.

Adding all of your port mappings fixed it, and I can continue to use bridged mode (the default), I have my plex server fully accessible outside my network, and I can link my plex container to my other Docker containers.

Thanks again!

@phillipuniverse

This comment has been minimized.

Show comment
Hide comment
@phillipuniverse

phillipuniverse Jan 6, 2017

One other caveat: I did have to use the manual port forwarding method at my router because Plex could not auto-detect how to get back to the container.

One other caveat: I did have to use the manual port forwarding method at my router because Plex could not auto-detect how to get back to the container.

@Mumie-hub

This comment has been minimized.

Show comment
Hide comment
@Mumie-hub

Mumie-hub Jan 26, 2017

@phillipuniverse u could setup a static route in your router with Net: 172.17.0.0 Subnet: 255.255.0.0 Gateway <your.dockerhost.ip> advertised by dhcp, that would have done the trick also (i think) :)

Mumie-hub commented Jan 26, 2017

@phillipuniverse u could setup a static route in your router with Net: 172.17.0.0 Subnet: 255.255.0.0 Gateway <your.dockerhost.ip> advertised by dhcp, that would have done the trick also (i think) :)

@krohrsb

This comment has been minimized.

Show comment
Hide comment

krohrsb commented Jan 26, 2017

Also note plex official docker images. Though i have not tried yet. https://forums.plex.tv/discussion/250499/official-plex-media-server-docker-images-getting-started

@tcf909

This comment has been minimized.

Show comment
Hide comment
@tcf909

tcf909 Feb 6, 2017

I've done extensive work with my Plex in docker and found that customConnections really only works well with IP addresses for some reason. I wrote a small bash resolver script that took a DNS entry and translated it to an IP to put in to Preferences.xml and seemed to resolve my previous issues.

tcf909 commented Feb 6, 2017

I've done extensive work with my Plex in docker and found that customConnections really only works well with IP addresses for some reason. I wrote a small bash resolver script that took a DNS entry and translated it to an IP to put in to Preferences.xml and seemed to resolve my previous issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment