Can't install

Help
1

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

Expected Behaviour:

Install Pi-Hole on Linux Mint 19 Cinnamon v 3.8.9

Actual Behaviour:

"Simple install" method fails as does, manual download and installation. Console dialogue =

tony@Dell:~$ wget -O basic-install.sh https://install.pi-hole.net
--2019-12-12 15:34:55-- https://install.pi-hole.net/
Resolving install.pi-hole.net (install.pi-hole.net)... 78.46.180.80
Connecting to install.pi-hole.net (install.pi-hole.net)|78.46.180.80|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/pi-hole/pi-hole/master/automated%20install/basic-install.sh [following]
--2019-12-12 15:34:56-- https://raw.githubusercontent.com/pi-hole/pi-hole/master/automated%20install/basic-install.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.64.133, 151.101.0.133, 151.101.192.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.64.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 113876 (111K) [text/plain]
Saving to: ‘basic-install.sh’

basic-install.sh 100%[======================================>] 111.21K --.-KB/s in 0.07s

2019-12-12 15:34:57 (1.52 MB/s) - ‘basic-install.sh’ saved [113876/113876]

tony@Dell:~$ sudo bash basic-install.sh

[✓] Root user check

    .;;,.
    .ccccc:,.
     :cccclll:.      ..,,
      :ccccclll.   ;ooodc
       'ccll:;ll .oooodc
         .;cll.;;looo:.
             .. ','.
            .',,,,,,'.
          .',,,,,,,,,,.
        .',,,,,,,,,,,,....
      ....''',,,,,,,'.......
    .........  ....  .........
    ..........      ..........
    ..........      ..........
    .........  ....  .........
      ........,,,,,,,'......
        ....',,,,,,,,,,,,.
           .',,,,,,,,,'.
            .',,,,,,'.
              ..'''.

[✓] Disk space check
[✗] Update local cache of available packages
Error: Unable to update package cache. Please try "apt-get update"

tony@Dell:~$ sudo apt-get update
Ign:1 http://ucmirror.canterbury.ac.nz/linux/mint/packages tara InRelease
Hit:2 http://ucmirror.canterbury.ac.nz/ubuntu bionic InRelease
Hit:3 http://ucmirror.canterbury.ac.nz/ubuntu bionic-updates InRelease
Hit:4 http://ucmirror.canterbury.ac.nz/ubuntu bionic-backports InRelease
Hit:5 http://ucmirror.canterbury.ac.nz/linux/mint/packages tara Release
Ign:6 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:7 https://brave-browser-apt-release.s3.brave.com bionic InRelease
Ign:8 http://dl.google.com/linux/earth/deb stable InRelease
Hit:9 http://archive.canonical.com/ubuntu bionic InRelease
Get:11 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:12 http://linux.teamviewer.com/deb stable InRelease
Hit:13 http://dl.google.com/linux/chrome/deb stable Release
Hit:14 http://linux.teamviewer.com/deb preview InRelease
Hit:15 http://dl.google.com/linux/earth/deb stable Release
Hit:16 https://apt.spideroak.com/ubuntu release InRelease
Get:10 http://ppa.launchpad.net/mmozeiko/rclone-browser/ubuntu xenial InRelease [18.1 kB]
Get:18 https://mega.nz/linux/MEGAsync/xUbuntu_18.04 ./ InRelease [1,310 B]
Err:10 http://ppa.launchpad.net/mmozeiko/rclone-browser/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 29CF6613D67DF04A
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386'
W: GPG error: http://ppa.launchpad.net/mmozeiko/rclone-browser/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 29CF6613D67DF04A
E: The repository 'http://ppa.launchpad.net/mmozeiko/rclone-browser/ubuntu xenial 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.

tony@Dell:~$ sudo bash basic-install.sh

[✓] Root user check

    .;;,.
    .ccccc:,.
     :cccclll:.      ..,,
      :ccccclll.   ;ooodc
       'ccll:;ll .oooodc
         .;cll.;;looo:.
             .. ','.
            .',,,,,,'.
          .',,,,,,,,,,.
        .',,,,,,,,,,,,....
      ....''',,,,,,,'.......
    .........  ....  .........
    ..........      ..........
    ..........      ..........
    .........  ....  .........
      ........,,,,,,,'......
        ....',,,,,,,,,,,,.
           .',,,,,,,,,'.
            .',,,,,,'.
              ..'''.

[✓] Disk space check
[✗] Update local cache of available packages
Error: Unable to update package cache. Please try "apt-get update"

tony@Dell:~$

As you can see I just go around in a circle. I'm not sufficiently Linux literate to know if the answer is in any of the above.

Debug Token:

Don't get far enough to do this.

2

This is an OS problem, not a Pi-Hole problem

3

See: GitHub - mmozeiko/RcloneBrowser: Simple cross platform GUI for rclone as that package is no longer supported.

4

Well, OK to both of you but that doesn't help for, as I said, I'm little more than your beginner Linux user and this is shaping up into one of those situations that sends beginner Linux users back to Windows.

That said, I've had Mint running on this machine for well over a year and have never before had a problem installing any software on it - even proprietary stuff that isn't in the depositories. So if it is an OS problem it seems to be one that Mint only has with Pi-Hole.

5

You have configured Mint to use a repository for the Rclone-browser package. That repository is not configured correctly, there is a missing key that signs all packages from that repository, see the error E: The repository ‘http://ppa.launchpad.net/mmozeiko/rclone-browser/ubuntu xenial InRelease’ is not signed.

The Rclone-browser package seems to be no longer managed or supported by the author of that package, see GitHub - mmozeiko/RcloneBrowser: Simple cross platform GUI for rclone > WARNING: This project is not longer active or maintaned.

This isn't a Pi-hole issue, the package sources are not configured correctly, since it isn't we don't even attempt to install Pi-hole.

6

look in /etc/apt/sources.list for the line containing Rclone... and rem it out, add a "#" to the beginning of the line.

If it is not there, look in /etc/apt/sources.list.d - any file in this directory is used when you run "apt update", edit and rem out anything for rclone.

Once you can run "sudo apt update" you should be able to install pihole

7

Well, it would seem that exactly proprietary stuff is causing your troubles now.

Note that Pi-hole has no other choice than to stop installation if updating/upgrading failed - it cannot know how to deal with missing/defective/conflicting software packages that the system owner (=you) chose to install.

If you follow the github link @DanSchaper has provided, you'll find the following interesting read (click to show)

RcloneBrowser

WARNING: This project is not longer active or maintaned.

Initially I created it only because rclone mount did not work in the beginning. Now mount on Windows works fine, so this project is not useful for me anymore.

I suggest to try out rclone built-in web based GUI instead

So if you still need rclone-browser, you could exclude the offending package from being considered for updates:

sudo apt-mark hold <package-name>

Replace <package-name> respectively.

And don't forget to remember that you put that on hold (click for more).

If you do forget, you can list packages that you excluded from upgrades:

sudo dpkg --get-selections | grep "hold"

You can get a package back in the loop with

sudo apt-mark unhold <package-name>

If you don't need it anymore, you could also uninstall it completely:

sudo apt-get purge --autoremove <package-name>

Again, replace <package-name> respectively.

And you probably want to read a bit more about Package Management

8

Ok, well, thanks for trying at least. I did have rclone on my system - dunno why as I've never heard of it, dunno what it does or why I should want it and have certainly never installed it. Unfortunately removing it hasn't made any difference to Pi-Hole's inability to install itself and I'm not going to give up on Mint just for this so it looks like I'll have to go withoutPi-Hole.

I'm sure there's a simple enough explanation if you know what you're doing, but I've better things to do than to spend hours reading up on and trying to understand package management systems, probably only to discover that's not the problem anyway.

I have installed a few third-party packages without problem so, with respect, it's not an OS problem but an inadequacy with the Pi-Hole installation routine.

Cheers,

9

Above errors are in no way related to the Pi-hole installation!

1 Like
12

I agree and nobody is trying to push you to Windows or whatsoever. We're here trying to help you. If you don't know what to do where exactly, ask and we will help you. I have a lot of experience with Linux (and actually none with Windows) and reading all the posts in here, it doesn't seem that anyone wants to scare you off. It just isn't as easy as "install xyz and you're back on track".

What you're seeing is an issue caused by a broken software source on your system. This is not a Pi-hole problem. In contrast, if you'd have tried to update your Linux before having thought about Pi-hole once, you'd have seen the same errors.

Not knowing which version of Linux Mint you have, I will recommend how to solve this based on the most recent one:

  1. Go to "Software Sources"
    Screenshot%20at%202020-01-01%2023-17-18
    Screenshot%20at%202020-01-01%2023-17-18860×607 36.6 KB
  2. Open the tab "PPAs"
    Screenshot%20at%202020-01-01%2023-17-27
    Screenshot%20at%202020-01-01%2023-17-27860×607 31.7 KB
  3. Uncheck the rclone-browser and also the dl.google one and agree to update your cache
    Screenshot%20at%202020-01-01%2023-17-35
    Screenshot%20at%202020-01-01%2023-17-35860×607 36.4 KB

Try to update your system to the most recent version using the usual update manager before trying to continue. If you cannot find something, show us a screenshot of where you're stuck and we will help you from there on. If something looks different, just tell us what. We're here.

2 Likes
17

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