Can't update Plex Server any longer



I'm not sure if this has happened since I upgrade Raspbian from Jessie to Stretch - thought I'd done a Plex update since then.

However, whenever I run apt-get update I now get the following regarding the dev2day...

Hit:1 stretch InRelease
Ign:2 stretch InRelease
Err:3 stretch Release

Hit:4 stretch InRelease
Reading package lists... Done
E: The repository ' stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Anyone point me to what's gone wrong?



I suppose you have been temporarily banned from my server for excessive HTTP requests. Just try again in 2 hours :slight_smile:


@uglymagoo said:
I suppose you have been temporarily banned from my server for excessive HTTP requests. Just try again in 2 hours :slight_smile:

I don’t think it’s that as it’s been doing it for a few weeks. I can run the apt-get update having not touched the Pi in 3 weeks and that the above is the response I get back on the first attempt.



Please post the contents of /etc/apt/sources.list.d/pms.list and also try to manually download the InRelease file from your Pi to make sure your network and dns settings are OK, e.g. wget And did you import my repo key correctly? See Plex Installation.

The repo itself is operational. I just checked again and tested everything on my Pi.



The result of trying to get the key again is:
root@raspberrypiHDD:/home/pi# wget -O - | apt-key add -
–2018-04-23 12:56:23--
Resolving (… 2a01:4f8:200:502e::2,
Connecting to (|2a01:4f8:200:502e::2|:443… connected.
ERROR: The certificate of ‘’ is not trusted.
ERROR: The certificate of ‘’ hasn’t got a known issuer.
gpg: no valid OpenPGP data found.

The contents of pms.list is:
deb stretch main

Previously I have been able to connect, it is installed after all. I am beginning to think that whilst the upgrade from Jessie to Stretch appeared to work fine, it maybe hasn’t after all.

I’ve just connected to another Pi on the same network and the request for the key is working there.



Please re-install the package ca-certificates

sudo apt-get install --reinstall ca-certificates


You’re a genius! :slight_smile:

Out of interest, I’m guessing it’s the lines about cert not trusted, but how did you figure it needed ca-certificates reinstalling?



This package contains all the certificates of the certificate authorities, that are trusted by Debian. Take a look at the contents of this package with dpkg -L ca-certificates. This package was damaged, i.e. your local installation was unable to validate that the certificate of was issued by a trusted authority. So it assumed, the server presenting itself as is really a malicious third party. By reinstalling the package, you have restored the ability to check the validity of the certificate of :slight_smile:

And this problem is quite common here in the forum :smiley: