Unable to complete upgrade

 [✓] Detected ARMv7 processor (with hard-float support)
  [i] Checking for existing FTL binary...
  [i] Downloading and Installing FTL...curl: (7) Couldn't connect to server
  [✗] Downloading and Installing FTL
   Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv7-linux-gnueabihf not found
  [✗] FTL Engine not installed

Following a recent upgrade from buster to bullseye. on a rpi 3B.

 [✓] ** FINISHED DEBUGGING! **

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (7) Couldn't connect to server

[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log

When I scroll through the debug log I see:

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 403 Forbidden
Content-Type: text/html
Content-Length: 341
Date: Fri, 05 Aug 2022 01:24:09 GMT
Server: lighttpd/1.4.59

[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Set-Cookie: PHPSESSID=ogbcof5dmaq1soc4ttnf71tjpa; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Content-type: text/html; charset=UTF-8
Date: Fri, 05 Aug 2022 01:24:09 GMT
Server: lighttpd/1.4.59

also in ftl.log

[2022-08-05 02:03:32.011 485M] WARNING: Unable to remove PORT file: Permission denied
[2022-08-05 02:03:32.011 485M] WARNING: Unable to remove PID file: Permission denied

Finally :

1       2022-08-05 02:23:59  DNSMASQ_WARN          no address range available for DHCP request via lo 

Pi-hole gives the impression of working.
The footer on the admin page shows

* **Pi-hole** [v5.11.4](https://github.com/pi-hole/pi-hole/releases/v5.11.4)
* **FTL** [v5.16.1](https://github.com/pi-hole/FTL/releases/v5.16.1)
* **Web Interface** [v5.13](https://github.com/pi-hole/AdminLTE/releases/v5.13)
 dig github.com

; <<>> DiG 9.16.27-Raspbian <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18288
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;github.com.                    IN      A

;; ANSWER SECTION:
github.com.             24      IN      A       140.82.121.3

;; Query time: 0 msec
;; SERVER: ::1#53(::1)
;; WHEN: Fri Aug 05 16:00:33 BST 2022
;; MSG SIZE  rcvd: 55

pi@pi-hole2:~ $ curl https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv7-linux-gn                                                                                                                            ueabihf > test
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Couldn't conne                                                                                                                            ct to server
pi@pi-hole2:~ $ curl https://docs.pi-hole.net/ftldns/dnsmasq_warn/ > test
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 73788    0 73788    0     0   127k      0 --:--:-- --:--:-- --:--:--  128k

When I have issues updating Pi-Hole, I think of it like this:

You are running the same program you are trying to update.

I would try changing your DNS to something like quad9 or "nextDNS" they both seem like great options. Or, cloudflare also has a few filtered options as well.

Then, you could temporarily use them as your main DNS server just until you get the program updated.

This has no bearing. Pi-hole is involved in the DNS query only. After that, the URL is loaded, the software is downloaded, etc. The choice of DNS server for the Pi-hole host does not change any of this.

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

  • The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
    [i] Debug script running in automated mode
    • Using curl for transmission.
    • curl failed, contact Pi-hole support for assistance.
    • Error message: curl: (7) Couldn't connect to server

[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run

pihole -d

and upload the debug log.

No change!
I have working dns on this pi. I can resolve github.com but curl cannot download the file. I do not know where the debug log is uploaded to but curl cannot upload it. It is not an issue with my network as I have another pihole installation that is happy. This install was happy until I upgraded to bullseye. If it is not a known problem I can wipe and reinstall.

PM this file to me. May take a few PM's to get the whole file.

/var/log/pihole/pihole_debug.log

Did you receive my PMs?