That’s weird. works for me when accessing it on the local network, with the linuxserver.io container.
Remember to update the container with the above version string.
Example:
I do have my local network subnets added in the Plex server network settings, under both “Lan Networks” and “List of IP addresses and networks that are allowed without auth”.
Don’t know if that could have an effect.
It loads fine, but it still gives me the timeouts. Even tried it in Bridge:0 mode with a Fixed IP address. As shown here, currently, I’m in Host mode.
@JacobPed Did you do anything special to your local network? Set up a DNS entry? Enable Network rebinding? (If these mean nothing to you, that’s okay too.)
I’ve only tested that it works on my local network, as that’s where i primarily use my Plex server. Not remotely.
With the newer plex versions I had a ton of issues when I updated to them, as you all have described previously in this thread. I located the mentioned version tag, setup a new linuxserver.io container that points to the same folders with the version tag, and it have been running perfectly ever since. 
Regarding remote connection. Plex client says it should work fine remotely, and the one remote user I have, have not complained. 
I haven’t done anything special other than adding my local subnet in the plex network settings as described previously.
And I don’t have a dns entry or using Network Rebinding.
It’s a fairly vanilla setup in regards to networking, where I only have a NAT forward for remote access, and IPv6 disabled in Plex settings plus the local subnet defined. Nothing more.
This container with the specified network tag is just running in host mode now, as that have been working perfectly fine.
@JacobPed SUCCESS!
I had to do it in unRAID as: Repository: “plexinc/pms-docker:1.13.2.5154-fd05be322” then it pulled correctly for me.
It’s been working for about 18 hours, and I can connect to it instantly. It seems to not correctly use the VERSION even though I had it in there as “1.13.2.5154-fd05be322” It’s in both fields and it’s been working and unRAID is also not nagging me to upgrade it either.
Great to hear you found a working solution. 
Perhaps the issue for why the downgrade didn’t work for you, would have been mentioned in the container logs. But whatever, it works now.
I recall seeing some message like “newer version already installed.”
I think I did a “remove docker and it’s containers” then I re-installed it but selected the wrong template and left linuxserver.io and went with Plex’s one instead. It’s working, and I’m tired of messing with it.
Time to play with the firewalls again… carefully.
I’ll give it a try this week-end.
Meanwhile I’ve tried to rollback to 1.13.2.5154 and it worked well until I rebooted the lxc container to add more ram. Now I wonder if the new network stuff is the source of this issue afterall 
Once, and twice bitten, thrice… super shy. I’m going to let someone else try first…
@ChuckPa, do we know if this has any new network patches or is that still pending? I saw a post where it wasn’t mentioned in the “readme/updated” content.
Anyone have better luck than I with the newer builds?
Gonna give it a try this weekend. Will keep you all updated
Sorry for the delay!
After creating a backup of my LXC container, I’ve decided to take a look at plex without upgrading the version ( 1.13.2.5154) and behold, no issues. I will still create a clone and upgrade that one to the latest version and see if everything works fine and report the result here.
Adding my 2 cents here. I’ve been stuck on version 1.13.2.5154 since the beginning of August when a Plex update caused “Connection Timeout” errors as described by the first post in this thread. Just like the OP, I’m using unraid and running Plex as a docker image. Been a PlexPass user since early 2014 and this is the first time I’ve had an issue with Plex not working.
To the Plex employees, here is the support forum for the Plex docker on the unraid forum (https://forums.unraid.net/topic/40463-support-linuxserverio-plex-media-server/?page=109). The first post I found on this issue is from a user named “Potato” on Aug 5, 2018. many post follow covering the subject.
I hope someone at Plex could take the time to report here as to the status of this issue. The last post from Plex on this thread is over a month old and doesn’t suggest much progress is being made. Someone at Plex might also want to reach out the the maintainers of the docker image at;
https://hub.docker.com/r/linuxserver/plex/
or
Thank you
7 days and no response from Plex. sigh…
Is posting to the forum the only way to report a bug?
As far as we know, they are already aware of this issue and are supposedly working on it. What we do not know is what kind of progress has been made on the issue and if it has been fixed without telling anyone.
Hopefully I will reinstall my server this weekend and give the latest docker image a try.
Thoorium, thanks for the reply. Looking forward to you results.
<soaobox_rant_mode> I was hoping the see a response from Plex on this issue. The last comment from Plex (ChuckPA) in this thread is now nearly 6 weeks old and doesn’t leave me with much hope since ChuckPA little experience with Dockers. I would hope Plex would reach out to the community and/or the maintainers of the Docker image in order to resolve this problem. I just don’t like the lack of updates from Plex on this issue. We the users have no why to know if any progress or action is taking place on this, or any other issues for that matter. I come from a technical background and and vendors I have dealt with have always had some sort of method to report and track bug reports. </soaobox_rant_mode>
Been chasing the rabbit down the hole on this exact same issue for an hour, only to find this thread. It looks like I’m dead in the water, too. Plex is essentially useless in my docker instance. Is there an intermediate workaround?
I’m on Version 1.13.8.5395, both the linuxserver.io docker image and the plex docker both pull this version down automatically 
EDIT: looks like I can specify 1.13.2.5154 in my compose file so it only grabs that version.
Specifying 1.13.2.5154-fd05be322 in my compose file and redeploying makes everything good in the world again.
Sorry if this is old news, but I haven’t seen any news about it…
Back in August a new version of Plex was causing problems with connection timeouts. The network connection would go up and down about every 5 minutes and the log would have line after line of “connection Timeout” errors.
After contacting Plex support and getting no help I decided to just go ahead and try the current Plex release (1.13.8.5395-10d48da0d) and see if the error was still occuring. It’s been a few days and I can report that at least for my system the connection timeout errors are gone.
I saw something on Reddit today and thought I would give it a shot.
On my unRAID box I changed networking from host to bridge. I then added the following port mappings manually:
EDIT: Changing the TCP/UDP settings to match the Docker recommended ports from: https://github.com/plexinc/pms-docker
1900, 32410, 32412, 32413, 32414,:UDP
3005, 8324, 32400, 32469: TCP
Then updated to the latest version of Plex…
So far so good.
Fresh install means wipe the reg and then Plex media from c drive delete the server in devices on the Plex account unistal Plex and install version 1.9.1 till they fix it
