I’ve asked and permission granted.
The thread has now been moved to General (Public) and accessible to all
Is this still an issue or has it been fixed?
I’m curious about upgrading next month to Ubuntu 18.04 LTS without any issues from my old stable 16.04 LTS server. 
This is still an issue unfortunately!
However: if you change the repo path in plexmediaserver.list to “https://downloads.plex.tv/repo/deb public main” (remove the ./ ) it downloads and updates, but you will get a warning when updating the repos.
@“hnernes@live.no” said:
This is still an issue unfortunately!
However: if you change the repo path in plexmediaserver.list to “https://downloads.plex.tv/repo/deb public main” (remove the ./ ) it downloads and updates, but you will get a warning when updating the repos.
Thanks for posting this workaround. When I did this and then ran apt-get update, I received the following error:
W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public but got )
Do I need to remove Plex and then re-install using thisnew repo path?
I’ve the same issue, is there any update?
I AM a PlexPass subscriber and find it kind of incredible that this is still an issue. Can no one simply put the Release file in the repo? Is it THAT hard?
@robross0606 said:
I AM a PlexPass subscriber and find it kind of incredible that this is still an issue. Can no one simply put the Release file in the repo? Is it THAT hard?
Release and even it’s cousin InRelease is there, I just checked 
That’s not the problem. One of the following two entries should work:
deb https://downloads.plex.tv/repo/deb ./public main (works perfectly for Debian 9. Maybe not with Ubuntu 18.04?)
deb https://downloads.plex.tv/repo/deb public main (produces a warning, just ignore it for now)
If none works, please tell me exactly what Linux distribution you are using.
@uglymagoo said:
@robross0606 said:
I AM a PlexPass subscriber and find it kind of incredible that this is still an issue. Can no one simply put the Release file in the repo? Is it THAT hard?
Releaseand even it’s cousinInReleaseis there, I just checked
deb https://downloads.plex.tv/repo/deb ./public main(works perfectly for Debian 9. Maybe not with Ubuntu 18.04?)
deb https://downloads.plex.tv/repo/deb public main(produces a warning, just ignore it for now)If none works, please tell me exactly what Linux distribution you are using.
Can confirm that first entry is not working with Ubuntu 18.04, but second one is working with a warning (expected public but got )
My concern here is that it has been 6 months since this issue was first reported, and there is no correct solution yet. Ubuntu has now released 18.04 (new LTS, thus I have upgraded) and it seems reasonable to expect Plex to have fixed this issue by now.
I think that blaming Ubuntu for this issue is deflecting the issue without justification. I have numerous 3rd-party APT sources configured, and none exhibit these problems. I suspect other reporters will confirm this.
It is perhaps telling that the official Plex guidance for setting up the repository specifies the “distribution” part of the deb line as ./public, treating it as a path. I have never seen this before in any other 3rd party APT source line - I am sure that those who I know to administrate deb repositories would regard this as an antipattern.
This, along with the relative novelty of the deb repository within Plex, makes me suspicious that the repository and sources.list config has been created via an experimental, “try stuff until it works” method.
It seems as though @ChuckPA does not have the resources to properly test different Ubuntu, Debian &c. distributions with Plex. This should be addressed as a matter of urgency - installation and updates are basic hygiene requirements for a paid-for software product - particularly one that prides itself on ease of use, as Plex does.
I am in Customer Support but do handle distro packaging.
I know what must be changed in the Ubuntu repo.
I have it all laid out.
I have other changes to make in other repos as well.
It will all go live together when done.
Regarding Ubuntu 18.04 and its early adopters,
- There is an announcement at the top of this forum regarding a networking race condition for those customers using 18.04 (specifically the new ‘Minimal’ loadout) and PMS startup. A race condition exists when using a SSD with a sufficiently fast processor.
- I deemed it more important to take care of issues preventing actual PMS use like the one above with 18.04 than like this repository warning.
The repo will be addressed when everything new goes live. There is nothing to be gained by patching what is about to be completely replaced.
Regarding the 18.04 issue, the change to PMS startup is already in queue for the next Plex Pass release. It’s only waiting for final Engineering and QA sign-off which occurs weekly
@ChuckPA said:
2. I deemed it more important to take care of issues preventing actual PMS use like the one above with 18.04 than like this repository warning.
@ChuckyPA I didn’t realize Plex support staff were constrained to a single person making the decisions. I thought it was… a company… with money… and people… and a development road map.
As a developer myself, this type of request would generate one or more tickets. Those tickets would be scheduled into a plan (i.e. Agile sprint). Does Plex have an actual development process and a roadmap with allocated resources, or are you one person sitting in a room by yourself making all the decisions?
As I have stated, it’s already on the schedule. The entire repo structure will be overhauled when the new build system goes live. That’s the current plan.
Could I go fix it now, sure. Is it worth the time? Not IMHO because of what it takes to retrofit into the existing. If this were a ‘hard down’, of course I would fix it. But a warning? seriously?
Update:
It’s been an uncanny quiet Monday. I’m sure I will regret saying this too. 
I put in the 3 hours it took to make a surgical change (hotfix). That change has been submitted to Engineering and, specifically, the build team to both review and drop into position.
IF approved, two things will happen:
-
The reference to `./public` in `/etc/apt/sources.list.d/plexmediaserver.list` needs to be returned to its default `public` syntax.(you need to do this to make immediately effective) -
Documentation on the Support Page will be updated to no longer publish the workaround.
To all here.
https://forums.plex.tv/discussion/319999/ubuntu-16-debian-8-users-special-advance-announcement
Thanks ChuckPA for the hard and good work.
I on my end fixed it by switching to docker and my life got suddenly better. 
@ChuckPA said:
I am in Customer Support but do handle distro packaging.I know what must be changed in the Ubuntu repo.
I have it all laid out.
I have other changes to make in other repos as well.
It will all go live together when done.Regarding Ubuntu 18.04 and its early adopters,
- There is an announcement at the top of this forum regarding a networking race condition for those customers using 18.04 (specifically the new ‘Minimal’ loadout) and PMS startup. A race condition exists when using a SSD with a sufficiently fast processor.
- I deemed it more important to take care of issues preventing actual PMS use like the one above with 18.04 than like this repository warning.
The repo will be addressed when everything new goes live. There is nothing to be gained by patching what is about to be completely replaced.
Regarding the 18.04 issue, the change to PMS startup is already in queue for the next Plex Pass release. It’s only waiting for final Engineering and QA sign-off which occurs weekly
Interesting.
My Plex install on 18.04 went without a hitch. Several reboots while configuring, probably a dozen or so restarts without startup issue, but since then at 9d uptime, nice and steady. HW Transcoding and all working for x264/hevc/hevc10bit.
Plex Version 1.13.0.5003.
i3-8100 cpu is a true quad core and is certainly not ‘slow’ but maybe not sufficiently fast?
OS/Plex is on a WD Black SSD NVME pciex4 interface, blazing fast.
H370 chipset with Intel Gigabit.
All Plex libraries are local/internal sata storage. Not loading libraries from network/NAS.
If I can help with logs, let me know. They would only be successful, non-error logs though 
@Curun
So you didn’t encounter the network.target versus network-online.target issue? Excellent.
The race condition exists between the kernel / systemd launching pids faster than the network adapter is ready.
The change made, which is on its way out now, is the safer approach. Instead of using the passive network.target dependency, it uses the active network-online.target dependency which will make certain the adapters are up and running before PMS starts.
The condition encountered was PMS would start before networking was ready and immediately crash.
@“Youri Margarine” said:
Thanks ChuckPA for the hard and good work.
I on my end fixed it by switching to docker and my life got suddenly better.
Your life and everyone’s life will get easier here in the next day or two as that rolls into play.
Please be aware, even though I pulled the upcoming repo info back to here and patched it in, a smooth switch to the new one is not a 100% guarantee. I will be on top of the switchover but anything is possible given the different distros in play
@ChuckPA said:
@Curun**So you didn’t encounter the
network.targetversusnetwork-online.targetissue? ** Excellent.
The race condition exists between the kernel / systemd launching pids faster than the network adapter is ready.
The change made, which is on its way out now, is the safer approach. Instead of using the passivenetwork.targetdependency, it uses the activenetwork-online.targetdependency which will make certain the adapters are up and running before PMS starts.The condition encountered was PMS would start before networking was ready and immediately crash.
Dont know what those are, never saw errors related to such,
Just installed and… oh!, also copied databases from 17.04 installation over. I was careful to maintain same mounting locations from my 17.04 installation, and all libraries, settings and all came up perfectly. It was brilliant!
At the top of the Linux forum, you’ll find my subforum Linux Tips. I tried to pack in some goodies there.
If you or anyone finds something juicy to add, please let me know
