Just found that on the Ubuntu when you posted it, the docker isnt’ up long enoug for me to be able to do that. XML? I’m not scared to touch XML. 
“ServerBindInterface” and set it to the linux name, on linux “ens160” for example.
See how easy?
Hi friends,
I’m currently in the process of building my new Plex server and I’m running Plex inside a LXC container and it sounds like I’m having the same issue here. I’ll try to edit the new shiny network configuration and report back if it fix the issue or not.
Also, PMS installation guide when using a Proxmox 5.1 LXC container might need to be updated if this stuff is permanent
(Tested with both Debian 9.3 and Ubuntu 18.04 container images)
I’ve specified my network interface in the settings and I see no differences 
What I’ve noticed is that secure connection almost never works and playback takes forever to start.
Hopefully the next update fixes it.
I’m sure ChuckPA could use some logs in debug mode.
I’m assuming that it will connect for a few moments, and then vanish. I find that in the logs when it says:
" **DEBUG - MyPlex: We appear to have regained Internet connectivity.**"
is the moment it actually loses external connectivity.
I have this in another thread that I was commenting on.
Yes I looked into the logs and I find
**DEBUG - MyPlex: We appear to have regained Internet connectivity.**
more often than it should. Here’s the media server logs for @ChuckPa
Plex Media Server logs.zip (476.0 KB)
Regarding the “Lost Internet Connectivity” issue we’re all seeing.
1.13.5 introduced the ability to bind to an adapter. That works great.
Unforseen side effect is it disturbed MyPlex.
Engineering is working on that now and , AFAIK, will be in next update. BUT, i’m deep in NAS work so don’t have the absolute latest info on it.
4 Likes
Thanks @ChuckPa! Your assistance and status updates are most appreciated!
I’ll anxiously await the next release. Now I have to figure out if I can even get my docker (in unRAID) to back revision in the mean time.
Thanks @ChuckPa !
I was referring to the LXC guide, since LXC containers are currently broken but if the next update fixes the issue as stated, nothing needs to be updated
I’ve been searching today to find a status but being the weekend 
Sorry
Hi @ChuckPa,
Any news or perhaps suggested workarounds?
Yes, I do have a workaround. PMS 1.13.2 but being unraid, I have no idea as to the ramifications.
It is its own animal, both OS and NAS in one. Not part of my normal support & experience.
That said, PMS 1.13.2 is best option
Think of it as a Docker container that will be the best way to look at it, as that’s what it is.
The same thing was happening on an Ubuntu machine outside of that, so I’ll try something else.
Is this limited in scope to Linux or are Windows and other implementations affected too?
I am Hands Off with Docker and Containers. VMs are hard enough. I need to know a VM is involved right up front because Log files do not report if a hypervisor is present or not.
If you are running the Native app, on the bare host, Ubuntu, Debian, Redhat, Centos, or Fedora then I can always help.
I can help if I know a VM is involved and understand its relationship with the host.
When it gets exotic, it becomes a bigger challenge.
@ChuckPa, I will try a bare metal Ubuntu client for you. I’m a big fan of containers and VM’s.
Hi @ChuckPa, you wouldn’t happen to have a download link for this version, for Ubuntu 64bit? I’ve tried to find the package elsewhere since Plex doesn’t keep old versions but I couldn’t find it.
This version seems to be working for me:
1.13.2.5154-fd05be322
Download link:
https://downloads.plex.tv/plex-media-server/1.13.2.5154-fd05be322/plexmediaserver_1.13.2.5154-fd05be322_amd64.deb
1 Like
Sadly, not for me, tried it with both linuxserver.io’s and plex’s docker. No change.
