Bjonness406 Posted September 19, 2016 Share Posted September 19, 2016 Clicking "Check for updates" on the Docker page don't find any updates. The check for updates button does not work in 6.1.x, you need to click advanced view and then force update. The check for updates button works on 6.2. Thanks but it doesn't seems to do anything. Here is what I obtain Did I missed something? Does not look like it, no idea then. Hopefully someone other can take a look Quote Link to comment
Guill.St-P Posted September 19, 2016 Share Posted September 19, 2016 Ok, thanks for the help Bjonness406. I don't know if it's related but I don't see the 6.2 update either. In the plugin page, clicking "Check updates" doesn't find any updates. I just moved to a new house and changed my ISP at the same time; I don't know if that can make a difference... Or is it some kind of network setting that I did wrong? Quote Link to comment
Bjonness406 Posted September 19, 2016 Share Posted September 19, 2016 Ok, thanks for the help Bjonness406. I don't know if it's related but I don't see the 6.2 update either. In the plugin page, clicking "Check updates" doesn't find any updates. I just moved to a new house and changed my ISP at the same time; I don't know if that can make a difference... Or is it some kind of network setting that I did wrong? You could try to change your dns server to 8.8.8.8 and 8.8.4.4 Quote Link to comment
Guill.St-P Posted September 19, 2016 Share Posted September 19, 2016 You could try to change your dns server to 8.8.8.8 and 8.8.4.4 I tried it without any success. Here is my default network config: My router is setup to always assign the same ip address to my unRAID server Thanks again for the help! Quote Link to comment
Bjonness406 Posted September 19, 2016 Share Posted September 19, 2016 You could try to change your dns server to 8.8.8.8 and 8.8.4.4 I tried it without any success. Here is my default network config: My router is setup to always assign the same ip address to my unRAID server Thanks again for the help! Set Obtain dns server address automatically to "no", and dns server 1 to "8.8.8.8" and dns server 2 to "8.8.4.4" and try again to update your plugins and plex Quote Link to comment
Guill.St-P Posted September 19, 2016 Share Posted September 19, 2016 Sorry if my previous post wasn't clear I did it just before my previous post (and set it back to my previous settings just before posting my screenshot). It make no difference .... Quote Link to comment
stealth82 Posted September 20, 2016 Share Posted September 20, 2016 I have a question but it's not strictly related to the docker itself? Hope it's not too off-topic... When Plex docker network is configured as Bridge Plex takes a docker network IP in a range that is obviously different from the hosting unRAID one - e.g. the home network is 192.168.1.* and Plex is under 172.17.0.*. Although mapping the Plex port exposes the server to the home network Plex Server keeps the internal IP as a reference. Now everything seems to be working OK until you want to verify how close your Plex server is: if I'm under the home network I would expect the server to be considered nearby - same local network (that's an info you see if you have an iOS app and check what server you're connected to). Unfortunately the server is labeled as remote and not nearby. This screws up with the way content is served - direct play, profiles, etc... Any suggestion on this? Has this problem been considered before? Quote Link to comment
CHBMB Posted September 20, 2016 Share Posted September 20, 2016 Yes, that's why our readme on the github and dockerhub pages states to use host mode networking, and why the xml Unraid template is configured as such. Sent from my LG-H815 using Tapatalk Quote Link to comment
Guill.St-P Posted September 21, 2016 Share Posted September 21, 2016 Sorry if my previous post wasn't clear I did it just before my previous post (and set it back to my previous settings just before posting my screenshot). It make no difference .... I just the manual update to unRAID 6.2 and the Plex update was then available and applied successfully Thanks everybody for the help! Quote Link to comment
karateo Posted September 23, 2016 Share Posted September 23, 2016 Hi! I have been using plex for more than a year now. I noticed in my routers logs blocking access for a few android devices with plex app installed trying to connect to a bogon IP address. I found this address also in Plex docker. Does anyone have any idea what is going on? The weird thing is that the android devices are looking for 172.17.0.1 outside my lan in the internet. I googled before posting and the only think related (I think) is this https://github.com/timhaak/docker-plex/issues/54 09:19:19 firewall,info drop 172 forward: in:bridge-local out:pppoe-out1, src-mac xxxxxxx, proto TCP (SYN), 192.168.1.63:39411->172.17.0.1:32400, len 6 0 ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[274]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted 6 3000 /config/Library/Application Support d Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.2. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. [b]Registering new address record for 172.17.0.1 on docker0.IPv4.[/b] Registering new address record for 192.168.1.2 on br0.IPv4. Server startup complete. Host name is TOWER.local. Local service cookie is 1897350774. Quote Link to comment
nox969 Posted September 23, 2016 Share Posted September 23, 2016 Hi! I have been using plex for more than a year now. I noticed in my routers logs blocking access for a few android devices with plex app installed trying to connect to a bogon IP address. I found this address also in Plex docker. Does anyone have any idea what is going on? The weird thing is that the android devices are looking for 172.17.0.1 outside my lan in the internet. I googled before posting and the only think related (I think) is this https://github.com/timhaak/docker-plex/issues/54 09:19:19 firewall,info drop 172 forward: in:bridge-local out:pppoe-out1, src-mac xxxxxxx, proto TCP (SYN), 192.168.1.63:39411->172.17.0.1:32400, len 6 0 ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[274]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted 6 3000 /config/Library/Application Support d Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.2. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. [b]Registering new address record for 172.17.0.1 on docker0.IPv4.[/b] Registering new address record for 192.168.1.2 on br0.IPv4. Server startup complete. Host name is TOWER.local. Local service cookie is 1897350774. I can confirm that I'm seeing the same. An interface configuration for mDNS group on 172.17.0.1 during the startup and subsequent calls to the 172.* range when using the local web (browser) interface. Now this could also be the reason behind the local web interface being perceivable slower than when accessing via plex.tv. I'll try to do a further analysis this weekend but does anybody have any ideas? Quote Link to comment
interwebtech Posted September 25, 2016 Share Posted September 25, 2016 woah... lol. please explain for us mere mortals Quote Link to comment
Squid Posted September 25, 2016 Share Posted September 25, 2016 woah... lol. please explain for us mere mortals Sparklyballs is just patting himself on the back for the 1M pulls. Egomaniac and all. Quote Link to comment
sparklyballs Posted September 25, 2016 Share Posted September 25, 2016 woah... lol. please explain for us mere mortals Sparklyballs is just patting himself on the back for the 1M pulls. Egomaniac and all. i didn't have much to do with plex docker as it happens. i rewrote some of it when it was rebased. Quote Link to comment
interwebtech Posted September 25, 2016 Share Posted September 25, 2016 woah... lol. please explain for us mere mortals Sparklyballs is just patting himself on the back for the 1M pulls. Egomaniac and all. i didn't have much to do with plex docker as it happens. i rewrote some of it when it was rebased. Congratulations to the team then. Quote Link to comment
Squid Posted September 25, 2016 Share Posted September 25, 2016 Congratulations to the team then. Don't encourage him But yeah, lsio has done some amazing work Quote Link to comment
hernandito Posted September 27, 2016 Share Posted September 27, 2016 If they had a dollar for every time some one pulls.... Quote Link to comment
CHBMB Posted September 27, 2016 Share Posted September 27, 2016 If they had a dollar for every time some one pulls.... Yeah... we don't. Quote Link to comment
DJRon Posted September 29, 2016 Share Posted September 29, 2016 Hi, I am having trouble getting this docker to run. I believe I have it configured correctly (see attached) But when I go to the Plex UI I am unable to add that to my libraries. Please let me know what else I can provide. Thanks, Quote Link to comment
mr-hexen Posted September 29, 2016 Share Posted September 29, 2016 Hi, I am having trouble getting this docker to run. I believe I have it configured correctly (see attached) But when I go to the Plex UI I am unable to add that to my libraries. Please let me know what else I can provide. Thanks, In Plex, you add media by navigating to /media. Quote Link to comment
DJRon Posted September 29, 2016 Share Posted September 29, 2016 When I navigate there there are no sub folders (ie /Movies; /TVShows, etc) which is how they are on the Quote Link to comment
trurl Posted September 29, 2016 Share Posted September 29, 2016 When I navigate there there are no sub folders (ie /Movies; /TVShows, etc) which is how they are on the Don't know what the rest of that sentence was supposed to be. The docker screenshot you posted is assuming that you have a user share named Media, and that user share contains everything you want plex to access. Do you have a user share named Media? Quote Link to comment
CHBMB Posted September 29, 2016 Share Posted September 29, 2016 When I navigate there there are no sub folders (ie /Movies; /TVShows, etc) which is how they are on the Don't know what the rest of that sentence was supposed to be. The docker screenshot you posted is assuming that you have a user share named Media, and that user share contains everything you want plex to access. Do you have a user share named Media? Also remember Linux is case sensitive. Quote Link to comment
mr-hexen Posted September 29, 2016 Share Posted September 29, 2016 Also remember that "/Media" will be at the root of the folder structure. Not sure typing it in will work, so hit the icon to "go up". Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.