Error: Unable to update package cache. Please try "\e[1;31m"root
Installing on machine with nextcloud.
What installer or command were you running that generated this error?
GitHub - pi-hole/pi-hole: A black hole for Internet advertisements this site.
Just a copy and paste to a Bitvise SSH terminal window.
The curl -sSL https://install.pi-hole.net | bash
There is ' ' around the command line
copied from git hub
curl -sSL https://install.pi-hole.net | bash
There is 4 x # at the start of the the command
I think I see the problem 2 different results from the web page?
If there's a problem with the package cache then sudo apt update
is failing to run. Try that command manually.
I did apt clean then the install bash command and it still fails.
I have the same error on ubuntu a 2nd pc.
What is the output from sudo apt update
?
Lots of errors
Idea Do we need a Whitelist of all the Linux sources so we dont block them?
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 Index of http://download.virtualbox.org/virtualbox/debian stretch InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Get:5 https://packages.sury.org/php stretch InRelease [6,760 B]
Ign:7 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu cosmic InRelease
Hit:9 http://downloads.mariadb.com/MariaDB/mariadb-10.3/repo/debian stretch InRelease
Err:5 https://packages.sury.org/php stretch InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
Hit:10 http://ftp.hosteurope.de/mirror/packages.dotdeb.org stretch InRelease
Ign:12 https://dl.bintray.com/resin-io/debian stable InRelease
Ign:13 http://downloads.mariadb.com/MaxScale/2.2/debian stretch InRelease
Hit:14 http://deb.playonlinux.com precise InRelease
Get:15 https://dl.bintray.com/resin-io/debian stable Release [1,878 B]
Hit:16 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu zesty InRelease
Get:17 https://dl.bintray.com/resin-io/debian stable Release.gpg [821 B]
Ign:6 http://mirrors.edge.kernel.org/debian stretch InRelease
Ign:17 https://dl.bintray.com/resin-io/debian stable Release.gpg
Hit:18 http://downloads.mariadb.com/Tools/debian stretch InRelease
Get:19 http://ppa.launchpad.net/ondrej/php/ubuntu cosmic InRelease [20.8 kB]
Hit:11 http://mirrors.edge.kernel.org/debian stretch-updates InRelease
Hit:20 http://downloads.mariadb.com/MaxScale/2.2/debian stretch Release
Err:19 http://ppa.launchpad.net/ondrej/php/ubuntu cosmic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
Hit:21 http://mirrors.edge.kernel.org/debian stretch Release
Ign:24 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu disco InRelease
Err:25 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu cosmic Release
404 Not Found
Err:26 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu disco Release
404 Not Found
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
W: GPG error: https://dl.bintray.com/resin-io/debian stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379CE192D401AB61
E: The repository 'https://dl.bintray.com/resin-io/debian stable Release' is not signed.
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.
W: GPG error: http://ppa.launchpad.net/ondrej/php/ubuntu cosmic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
E: The repository 'http://ppa.launchpad.net/ondrej/php/ubuntu cosmic InRelease' is not signed.
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.
E: The repository 'http://ppa.launchpad.net/gezakovacs/ppa/ubuntu cosmic Release' does not 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.
E: The repository 'http://ppa.launchpad.net/openjdk-r/ppa/ubuntu disco Release' does not 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.
root@NextCloud:~#
They aren't blocked, you just don't have the GPG keys for the packages signed by those repositories. That's not something that Pi-hole would have any control over.
Not to mention you have Stretch, Disco, and Cosmic repositories which is just a recipe for system implosion.
I know they should not be there.
Not sure whats going on.
It may be time for a clean system reinstall.
I have Lots of Marie's Wagnwash data no free space to backup.
She wont backup all the work I have done to allow a fresh install.
wget
the proper GPG keys from the repos that have key problems and add them for quick fix eg for https://packages.sury.org/php
:
cd ~
wget https://packages.sury.org/php/apt.gpg
sudo apt-key add - < apt.gpg
EDIT: Forgot to mention, you got to trust these guys not to do harm by adding their key!
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.