Cloudflared and PADD not working after moving to v6

The issue I am facing:

Cloudflared and PADD do not seem to work.

I am assuming with PADD its just not been updated to work with v6 yet..

I was wondering if anyone else had issues with cloudflared. Now, regardless of DoH upstream provider, I get ERR failed to connect to an HTTPS backend

I don't use cloudflared, but I think other users didn't have issues during the v6 beta testing phase. Maybe there is a temporary issue with the upstream DNS server.

Actually you can install the development branch:

https://raw.githubusercontent.com/pi-hole/PADD/refs/heads/development/padd.sh

1 Like

as @rdwebdesign pointed out, the current PADD version is not compatible with Pi-hole v6. You need to use the development branch linked above.

1 Like

Well that solves that. I will have to look into why I have like 25 more clients now.

Maybe, I think its just as probable I am doing something silly :man_shrugging: I did try other providers but got the same result.

after re-installing again it seems to be working.

EDIT: I was mistaken, its still not working and giving the same errors.

cloudflared works on v6, i just installed it on 2 machines afew hours ago, not sure about PADD

heres the guide if you want to refer to it: cloudflared (DoH) - Pi-hole documentation

and this is the endpoint im using: https://security.cloudflare-dns.com/dns-query

1 Like

Yeah its just so odd. I have re-installed twice using that guide but end up with the same problem. PADD works fine using the developmental version.

The other thing is the amount of device has basically doubled since I upgraded to v6, which also seems unusual. I am thinking I am just to a full reset and try again.

EDIT: doing a completely clean install of pi-hole and then installing cloudflared seems to have done the trick.

1 Like

Yay :smiley:

PiHole v6 is awesome when it works, but frankly it should’ve been left in the beta oven for afew more months >.>

I'm using Docker. Is there a way to install the PADD development branch in my pi-hole container?

You could simply download it from within the container from https://raw.githubusercontent.com/pi-hole/PADD/refs/heads/development/padd.sh

or you build the Pi-hole image yourself and use the (not documented) -p argument to specify a PADD branch to include in the image

Thank you! That worked.

I downloaded the development branch (of padd.sh) on my RPI with Raspbian10 and Pihole v6.
But when padd.sh starts I see an error and the resulting dashboard only shows the last DNS request, but nothing else. What am I doing wrong?

Are you running PADD inside docker?

no, directly on my RPI. Sorry if that is a stupid question. Not really familiar with linux and docker stuff. Is it maybe as simple as to remove this "docker tag" somewhere?

The tags should not be there and we need to get to the core of the problem.

Please run bash -x ./padd.sh. It will generate a huge output. Please DM it to me.

Sent the output via DM (huge thx for you support btw).

Not sure if this is relevant, but I'd like to provide a bit of background info:

  • Running on a Raspberry Pi 3B+
  • Raspbian 10
  • PiHole v6

Last time I tried "pihole -up" I got the following message (DNS resolution was not working properly at that point, hence I initiated an update):

I then continued with the suggested command sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
which restored DNS-functionality, but not "padd.sh" functionality (even after downloading the dev-branch).

EDIT: I also checked on the page mentioned in the error, and it seems Raspbian should still be supported, correct?

Raspbian is, but your version is too old. We support versions which also get support from their distributor. Raspbian 10 is EOL since mid 2024.

Then you should stop the update before doing any changes. I wake up today to an unusable network because of the night update

Yes, that's how it looked on my side initially too. No resolution was working anymore, but the "skip os check" fixed pi-hole. Will update my distro now and report back.

Final Edit:

Now all is working again (with the padd.sh dev branch).
Thanks for the amazing support!

You are extremely lucky!

Upgrades from Debian 10 to any newer version should not be done because Debian 11 and 12 demand a much bigger /boot partition !!

Please do not attempt any further upgrades and consider installing a fresh new microSDXC card with Debian 12 or newer in the future :slight_smile:

1 Like