3 minutes ago, cammelspit said:

 Where can I donate to the linuxserver.io? ???

 

Donate button on very first post in this forum.

 

I am sure they would appreciate it!

24 minutes ago, Hoopster said:

 

Donate button on very first post in this forum.

 

I am sure they would appreciate it!

Surely, not as much as I do!

 

Thanks again all of you for the assist!

 

EDIT: I actually get a 404 when hitting the donate button.

Edited August 13, 20187 yr by cammelspit

28 minutes ago, cammelspit said:

Surely, not as much as I do!

 

Thanks again all of you for the assist!

 

EDIT: I actually get a 404 when hitting the donate button.

 

 

https://www.linuxserver.io/donate

Done, thanks again! ?

Done, thanks again! [emoji106]

Glad you worked it out.

Sent from my BND-L34 using Tapatalk

On 8/5/2018 at 2:30 PM, potato said:

Keep getting Connection time out 

 

after updating to the latest plex update 

 

please help ive tried almost everything 

here are logs

 

 

 

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 gratefully 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 Plex Media Server.
Starting dbus-daemon
[services.d] done.
dbus[275]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
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. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface veth0afd1be.IPv6 with address fe80::f6:5ff:febd:cca9.
New relevant interface veth0afd1be.IPv6 for mDNS.
Joining mDNS multicast group on interface vethd14ef46.IPv6 with address fe80::c41e:64ff:fe4e:b6e7.
New relevant interface vethd14ef46.IPv6 for mDNS.
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 vethfc6124b.IPv6 with address fe80::85c:4ff:fe34:8997.
New relevant interface vethfc6124b.IPv6 for mDNS.
Joining mDNS multicast group on interface veth52c8337.IPv6 with address fe80::4848:17ff:fe7d:ccfc.
New relevant interface veth52c8337.IPv6 for mDNS.
Joining mDNS multicast group on interface veth6eefde4.IPv6 with address fe80::1c25:97ff:fedf:570a.
New relevant interface veth6eefde4.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:72ff:fe19:3bc0.
New relevant interface docker0.IPv6 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.IPv6 with address fe80::943b:aff:fe84:c869.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.65.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface bond0.IPv6 with address fe80::1e87:2cff:fe76:1e1a.
New relevant interface bond0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::f6:5ff:febd:cca9 on veth0afd1be.*.
Registering new address record for fe80::c41e:64ff:fe4e:b6e7 on vethd14ef46.*.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::85c:4ff:fe34:8997 on vethfc6124b.*.
Registering new address record for fe80::4848:17ff:fe7d:ccfc on veth52c8337.*.
Registering new address record for fe80::1c25:97ff:fedf:570a on veth6eefde4.*.
Registering new address record for fe80::42:72ff:fe19:3bc0 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::943b:aff:fe84:c869 on br0.*.
Registering new address record for 192.168.1.65 on br0.IPv4.
Registering new address record for fe80::1e87:2cff:fe76:1e1a on bond0.*.
Server startup complete. Host name is AMD-Tower.local. Local service cookie is 18989884.
connect: Connection timed out
connect: Connection timed out
connect: Connection timed out
connect: Connection timed out
connect: Connection timed out
connect: Connection timed out
connect: Connection timed out

I've been having this same issue. Started about 10 days ago. No changes other than updating to latest docker. My logs file look just like this one, except for IP's. Did you resolve the issue? My Plex server is unreachable and the family is getting violent.

 

Edit; It's back online right now, but it goes up and down. Same pattern for last 10 days, but seems to be getting worse.

 

Edit #2; That didn't take long... Down again. Not having any other network type issues I'm aware of. Other dockers working okay. Samba okay, etc.

Edited August 15, 20187 yr by subagon
added new info

19 minutes ago, subagon said:

I've been having this same issue. Started about 10 days ago. No changes other than updating to latest docker. My logs file look just like this one, except for IP's. Did you resolve the issue? My Plex server is unreachable and the family is getting violent.

 

Edit; It's back online right now, but it goes up and down. Same pattern for last 10 days, but seems to be getting worse.

If it comes up for a few seconds every few minutes. Plex is aware there is a problem, not sure when it will be fixed. See my previous post on this issue. I have a link to the Plex forum with my post on it. 

 

The fix, for now? Go back to the previous version. (and no, I don't know how to do that. I wish I could too) 

 

 

Edited August 15, 20187 yr by BCinBC

7 minutes ago, BCinBC said:

The fix, for now? Go back to the previous version. (and no, I don't know how to do that. I wish I could too) 

The Docker and Github links in the first post explain how to install a specific version of Plex.

7 minutes ago, trurl said:

The Docker and Github links in the first post explain how to install a specific version of Plex.

I know that you can specify a build name that the dev has done usually like plexpass, beta, developer etc. But I didn't think it was that trivial to specify a Plex (or other) version number. Thanks, I'll check it out when I get home. Answers are brief as I'm on the train home. I Need 1.13.2, apparently. 

Edited August 15, 20187 yr by BCinBC
Added version number.

The Docker and Github links in the first post explain how to install a specific version of Plex.

Look under your advance network settings in Plex, if you can, they introduce a new feature that you can now bind to a specific network adapter. My is set to listen on all and it's working now.

Sent from my BND-L34 using Tapatalk

Thanks guys, I'll drop back to the prior version and see if that helps.

 

Another quick question, where in the docker are the plex logs? I looked in /var/lib/plexmediaserver/ and it was empty. Running a find from root, but it's taking a long time since it's going thru the media directory too.

Quote

Look under your advance network settings in Plex, if you can, they introduce a new feature that you can now bind to a specific network adapter. My is set to listen on all and it's working now. 

 

Mine is set to "all", but I'll play with it setting to to the unraid interface, br0.

Edited August 15, 20187 yr by subagon

5 minutes ago, subagon said:

Another quick question, where in the docker are the plex logs?

In appdata. appdata/plexmediaserver/Library/Application Support/Plex Media Server/Logs

21 minutes ago, wgstarks said:

In appdata. appdata/plexmediaserver/Library/Application Support/Plex Media Server/Logs

 Thanks, also I just found this to monitor logs in realtime, 

 

docker logs -f plex

 

Edit;

 

Adding output from Plex server log

 

snip

.

.

Aug 14, 2018 21:35:39.151 [0x1470603ff700] ERROR - Sync: could not get sync list 15715627, sync item 23361763 to update status
Aug 14, 2018 21:35:39.151 [0x1470603ff700] ERROR - Sync: could not get sync list 15715627, sync item 23361898 to update status
Aug 14, 2018 21:35:39.151 [0x1470603ff700] ERROR - Sync: could not get sync list 15715627, sync item 27916817 to update status
Aug 14, 2018 21:35:39.344 [0x1470603ff700] WARN - Held transaction for too long (../Versions/VersionGarbageCollector.cpp:78): 0.180000 seconds
Aug 14, 2018 21:35:39.504 [0x1470603ff700] WARN - Held transaction for too long (../Versions/VersionGarbageCollector.cpp:78): 0.150000 seconds
Aug 14, 2018 21:36:16.145 [0x1470577ff700] INFO - AutoUpdate: no updates available
Aug 14, 2018 21:36:29.024 [0x14704e7ff700] WARN - NAT: PMP, timed out waiting for response.
Aug 14, 2018 21:36:29.024 [0x14706a3ff700] ERROR - EventSource: Retrying in 15 seconds.
Aug 14, 2018 21:36:29.024 [0x14706a3ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (be4a8010-28b8-4af9-857d-e288d25c128f, expected 9e4b9a05-f720-41ff-8afd-d115c2047063)
Aug 14, 2018 21:38:52.384 [0x1470373fd700] WARN - NAT: PMP, timed out waiting for response.
Aug 14, 2018 21:38:52.384 [0x14706a1fe700] ERROR - EventSource: Retrying in 15 seconds.
Aug 14, 2018 21:38:52.384 [0x14706a1fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (e652e049-6fac-4b55-8fd5-4e9b9232fcb0, expected c96968dd-43c1-448b-93aa-ca901926cbb5)

 

.

.

snip

Edited August 15, 20187 yr by subagon

If you want to revert to a previous version you’ll need the version number.

https://lime-technology.com/forums/topic/40463-support-linuxserverio-plex-media-server/?do=findComment&comment=607587

Well I installed an old version of Plex (1.13.3.5223-cd1e0da1b) and no luck. I have 4 physical NICs and I've shut all but one of them down (wasn't really using them). Shut down VM manager (no VMs). I did this to shutdown virt0 interface. I reinstalled the current version of Plex (plexpass) and set Plex to listen to all interfaces (it was set to "all" when the issues started). Now the only interfaces it sees are br0 and docker0. Connection is still timing out, going up and down every couple of minutes. Mostly down, only up for a few seconds. Server is running, just connection issue. Not seeing any other connection issues on other dockers or other  computers/devices in the house. I'm running a pfsence router running most current version. Rebooted it a couple of times, because of "NAT" in an error message,  no luck rebooting.

 

That enough for now, late here, off to bed.

Edited August 15, 20187 yr by subagon

@subagon Plex specified 1.13.2 is needed to go back far enough before this networking issue.

 

There's a new option that recently appeared under the Server -> Networking option where you can tell Plex which NIC to use. That code doesn't work properly yet it would seem on docker and VM style containers.

2 hours ago, wgstarks said:

If you want to revert to a previous version you’ll need the version number.

https://lime-technology.com/forums/topic/40463-support-linuxserverio-plex-media-server/?do=findComment&comment=607587

 

That's a neat trick.  Look in this directory for previous reports:

 

/mnt/user/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Crash Reports

 

However, mine's pretty much empty because I've re-installed plex about 13 times with 3 different distros and also blew away the docker file and app file.

 

 

Edited August 15, 20187 yr by BCinBC

@BCinBC

i found a working version number for 1.13.2. Seems like Plex is finally working properly again with this version. :)

 

It's: 1.13.2.5154-fd05be322

 

I found it from randomly searching around in the Plex forums, as I also had deleted my crash reports folder.

2 hours ago, JacobPed said:

@BCinBC

i found a working version number for 1.13.2. Seems like Plex is finally working properly again with this version.

 

It's: 1.13.2.5154-fd05be322

 

I found it from randomly searching around in the Plex forums, as I also had deleted my crash reports folder.

This seems to be working for me. However, I'm still seeing connect timeout errors in the log file. Upside is that everyone is able to watch movies/shows and that's all they care about right now. Just have to sit back and wait for a fix to the current version.

For all those having issues with plex remote access, did you try reverse proxying? I had intermittent connection issues until I reverse proxied. No more connection problems. 

 

https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/proxy-confs/plex.subdomain.conf.sample

3 hours ago, aptalca said:

For all those having issues with plex remote access, did you try reverse proxying? I had intermittent connection issues until I reverse proxied. No more connection problems. 

 

https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/proxy-confs/plex.subdomain.conf.sample

@aptalca The issue is with internal and external connectivity. But this is a great piece of info!

10 minutes ago, BCinBC said:

@aptalca The issue is with internal and external connectivity. But this is a great piece of info!

 

I think what @aptalca is saying try the reverse proxy and that may correct your issues

2 minutes ago, ijuarez said:

 

I think what @aptalca is saying try the reverse proxy and that may correct your issues

Aaah, OK, because my problem isn't' getting to my server remotely... it appears to be my server "getting out" so this may make that part happy. 

10 hours ago, BCinBC said:

Aaah, OK, because my problem isn't' getting to my server remotely... it appears to be my server "getting out" so this may make that part happy. 

 

Normally with remote access, your server contacts the plex server and tells it what its public ip is so the plex server can let the clients know. I think plex is having issues with figuring out its public ip lately. 

 

With reverse proxy, you tell the plex server what the public domain is, and you can turn off the built in remote access service. Clients connect through your domain and letsencrypt/nginx container handles the ssl and proxy