Unable to update FTL, likely some issue with the node source stretch release directory links

Help Community Help
1

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

_Expect FTL to update without an error. _

Actual Behaviour:

Getting errors from Pihole -up AND from the regular update process. I think there is some weirdness with how the Pi is trying to get to a specific node source directory?
[✗] Update local cache of available packages
Error: Unable to update package cache. Please try "sudo apt-get update"
Unable to complete update, please contact Pi-hole Support
pi@pihole1:~ $ sudo apt-get update --fix-missing
Ign:1 https://deb.nodesource.com/node_14.x stretch InRelease
Hit:2 Index of /debian stretch InRelease
Hit:3 Index of /raspbian stretch InRelease
Err:4 https://deb.nodesource.com/node_14.x stretch Release
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Reading package lists... Done
E: The repository 'https://deb.nodesource.com/node_14.x 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.

Debug Token:

_https://tricorder.pi-hole.net/IoS3XSo3/_

2

You might check out this post: Unable to update FTL with pihole -up; sudo apt-get update also did not resolve it. It's a common problem with the OS as the repos are shuffled around and new ones release.

3

When the Pi-hole updater runs, it runs apt update. If apt update fails, the Pi-hole updater stops.

The problem you are seeing is at the OS level, not the Pi-hole level.

I recommend that you visit the forums for this OS to resolve this error.

4

Thanks, looking at that post now.

6

That post was missing information and had been partially removed by bots.
I'll keep looking for help at the Stretch/RPI level thanks.

7

Try loading it again.

8

My issue seems to be different. I think it is looking at a nodesource directory that doesn't exist (vs a cert being invalid). I'll find the right place for support on this one. I can get to the URLs manually, but the subdirectories seem to be maligned.

9

The following might be related:

https://github.com/nodesource/distributions/issues/1266

10

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.