Updated to Bullseye - cannot install PiHole

[peic]

First of all, I made a donation to thank you for your past help. I know I have asked for help a few times.

Expected Behaviour:

CURL to Bash command should install PiHole on my new Bullseye OS. (RPI 3B)

Actual Behaviour:

I ran the CURL command in the terminal, and it failed to install. I have tried to disable the RPi as my DNS so that I can isolate the problem, but I can't seem to accomplish this in my router anymore. I have no Internet if I use the new SD card and O/S, so I have to keep using the old one until I get this resolved.

Debug Token:

Not currently relevant.

[jfb]

What is the output of the install script?

[peick]

I found the issue. I was misunderstanding one of the messages during the install. It’s up and running now. But can you tell me how to get the Teleporter backup moved over to the new SD card if it’s on the old SD card?

[deHakkelaar]

Boot from the old SD card.
Check teleporter backup filesize eg 3.7KB in below example:

pi@ph5b:~ $ ls -lh pi-hole-ph5b-teleporter_2022-08-08_13-10-55.tar.gz
-rw-r--r-- 1 root root 3.7K Aug  8 13:10 pi-hole-ph5b-teleporter_2022-08-08_13-10-55.tar.gz

Check disk space available for the /boot partition on the SD card which is FAT32 formatted and can be read by most any OS:

pi@ph5b:~ $ df -h /boot
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  253M   49M  204M  20% /boot

If enough disk space available, copy the backup to the /boot partition:

sudo cp <TELEPORTER_BACKUP_FILE> /boot

Shutdown and insert the old SD card into a client PC with an SD card reader.
Browse on the PC to the SD card and copy the teleporter backup file to a local folder on the PC.
Boot from the new SD and restore the backup via the web GUI importing the backup thats stored locally on the PC.

You can copy over any files this way if your deskptop PC doesnt support reading EXT4 formatted partitions like the one present on Pi-OS,
and if you have enough diskspace available on the FAT32 formatted /boot partition:

pi@ph5b:~ $ lsblk -fp
NAME             FSTYPE FSVER LABEL  UUID      FSAVAIL FSUSE% MOUNTPOINT
/dev/mmcblk0
├─/dev/mmcblk0p1 vfat   FAT32 boot   XXXXXXXX  203.8M    19% /boot
└─/dev/mmcblk0p2 ext4   1.0   rootfs XXXXXXXX   11.4G    16% /

Cleanup these files from the /boot partion when ready because you dont want this one to run full if still booting from it.

I have a Linux desktop/laptop that makes thing easier copying files around with scp:

pi@ph5b:~ $ man scp
[..]
SYNOPSIS
     scp [-346ABCpqrTv] [-c cipher] [-F ssh_config] [-i identity_file]
         [-J destination] [-l limit] [-o ssh_option] [-P port]
         [-S program] source ... target

DESCRIPTION
     scp copies files between hosts on a network.  It uses ssh(1) for data
     transfer, and uses the same authentication and provides the same se‐
     curity as ssh(1).  scp will ask for passwords or passphrases if they
     are needed for authentication.

     The source and target may be specified as a local pathname, a remote
     host with optional path in the form [user@]host:[path], or a URI in
     the form scp://[user@]host[:port][/path].  Local file names can be
     made explicit using absolute or relative pathnames to avoid scp
     treating file names containing ‘:’ as host specifiers.

Eg copying a file on the Pi-hole node to my local PC:

scp <USER>@<REMOTE_IP_OR_HOSTNAME>:<PATH_TO_FILE> <LOCAL_FOLDER>