I don’t usally use the OSMC skin but noticed an update on the Blog page so thought I’d check it out. Unfortunately, installation fails with a pop-up message “please report to the forum”. Here’s a log from one of the Vero’s.
Did the error occur on more than one device?
Anyway, I noticed this in the log:
Feb 21 17:40:16 osmc mediacenter[758]: 2020-02-21 17:40:16.403022 apt_cache_action.py exception value : E:The repository 'http://apt.osmc.tv stretch Release' does no longer have a Release file.
This is very similar to this thread: Update Error The OP in that thread now reports that the problem has gone away, so can you please try again?
I’m running two Vero’s and an OSMC Pi and they all fail. Just tried again, no joy.
I think we can safely assume that they weren’t all hit by cosmic rays at the same time and, since the Release file does exist, it looks like some kind of networking problem.
From a browser on a PC, can you view http://apt.osmc.tv/dists/stretch/Release ? If so, you’ll see that it was created on 16 Feb 2020.
Similarly, from the command line of an OSMC device, can you download the Release file with wget http://apt.osmc.tv/dists/stretch/Release ?
Tried the wget from the command line and I get the following:
osmc@osmc:~$ wget http://apt.osmc.tv/dists/stretch/Release
--2020-02-22 12:57:13-- http://apt.osmc.tv/dists/stretch/Release
Resolving apt.osmc.tv (apt.osmc.tv)... 159.253.212.250
Connecting to apt.osmc.tv (apt.osmc.tv)|159.253.212.250|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://ftp.fau.de/osmc/osmc/apt/dists/stretch/Release [following]
--2020-02-22 12:57:13-- http://ftp.fau.de/osmc/osmc/apt/dists/stretch/Release
Resolving ftp.fau.de (ftp.fau.de)... 81.130.111.239
Connecting to ftp.fau.de (ftp.fau.de)|81.130.111.239|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2020-02-22 12:57:13 ERROR 403: Forbidden.That’s an issue, should be this:
wget http://apt.osmc.tv/dists/stretch/Release --2020-02-22 21:13:21-- http://apt.osmc.tv/dists/stretch/Release Resolving apt.osmc.tv (apt.osmc.tv)... 159.253.212.250 Connecting to apt.osmc.tv (apt.osmc.tv)|159.253.212.250|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://ftp.fau.de/osmc/osmc/apt/dists/stretch/Release [following] --2020-02-22 21:13:21-- http://ftp.fau.de/osmc/osmc/apt/dists/stretch/Release Resolving ftp.fau.de (ftp.fau.de)... 131.188.12.211, 2001:638:a000:1021:21::1 Connecting to ftp.fau.de (ftp.fau.de)|131.188.12.211|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 4145 (4.0K) Saving to: ‘Release’ Release 100%[=====================================================================================================================================>] 4.05K --.-KB/s in 0s 2020-02-22 21:13:22 (102 MB/s) - ‘Release’ saved [4145/4145]
Please also try to view the address from a browser.
Found the source of the problem. I tried the address from a browser and got an in-your-face warning from BT that the site is suspicious. I recalled that recently I had an email from BT about their web protect service, but I thought nothing of it. Turns out it has been activated and the BT web protect service is tagging the OSMC server as high risk. I disabled the BT web protect and downloads are now working again.
I doubt I’m the only OSMC user who has BT internet, so unless anything can be done server-side to prevent this false-positive, it might be worth having this issue posted prominently?
Out of interest, what happens in a browser when (with BT Web Protect enabled) you try to connect to www.fau.de and ftp.fau.de ?
the www.fau.de web page loads fine, but the http://apt.osmc.tv/dists/stretch/Release link gives me this if BT protect is enabled.
There doesn’t seem to be an obvious way for us to appeal this…