How can I revert back from v6?

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

Raspberry Pi - v6 extremely slow! Minutes, not seconds to switch from screen to screen. How can I revert back to a previous v5?? Please help!

Actual Behaviour:

[replace this text with what is actually happening]

Debug Token:

[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]

Did you read this before upgrading? Introducing Pi-hole v6 - Announcements - Pi-hole Userspace

For existing users, we recommend backing up your current configuration before proceeding, as the upgrade is strictly a one-way operation .

Also - minutes to switch between screens is very wrong... so maybe there is something wrong in your configuration.

If you run off a debug token (pihole -d) then a developer or mod will be able to help you troubleshoot and maybe even fix your issues :wink:

I have had this Pi-hole running on a Raspberry Pi for several years. I have never, ever had any issues until I allowed it to update to v6. Minutes? You better know it. I have actually got up from my desk, fixed a cup of tea and the little animated circular arrows still going. I just want it back like it was. I would like someone to tell me how to revert back to the previous working version, shy of formatting my SD and re-building.

I don't know what you mean by run off a token? My son built this for me years ago. I don't know Linux, or whatever. I did the pihole -d and it told me to run sudo pihole -d which I did not there is a screen full of stuff and what do I do with it?

I just want to be back like it was.

There is a URL listed which starts https://tricorder.pi-hole.net/....... where the ...... are numbers and letters. Copy yours and paste here.

Or just manually transcribe that last part here.

Just to reiterate.

As for the debug token, when you run pihole -d, it will ask at the end of the process if you want to upload the token for developers to view. Choose yes and share the token here please - we can take a look and help you troubleshoot to get it working as expected.

To manage your expectations here, there is no downgrade path here - even if you format your SD and rebuild - installing will always pull the latest version.

If you really really really insist on remaining on version 5 without trying to diagnose and fix your v6 issues (keeping in mind that the issues you are seeing are not normal) - then the only option I can suggest is to set it up as a docker container instead and use a previous tag. But lets try to fix you first...

Ok, after several minutes, it gave me the option to upload the debug log. Which I answered Y. Man, there is a lot of stuff in that log.
I'm thinking maybe I should send my SD to my son and get him to re-install some version of 5.

And the token code it gave you?

Lets not give up too soon, eh?

I did not see a token code. It just went back to the command line. Should I run it again?

See my earlier reply How can I revert back from v6? - #6 by chrislph

I do appreciate the help. I apologize, I don't know this term docker. Also, I started -d again and it is running now for almost a minute.

Edit: https://tricorder.pi-hole.net/3KeHoF6R

OK - I think I know what's happening here...I'm going to ask you a leading question (I think I already know the answer to it :wink: )

What address are you using to access the Pi-hole interface?

192.168.2.254

Can to do a screenshot of the address bar in your browser please?

pihole address bar

OK super - thanks, that absolutely confirms my hypothesis.

So the issue here is that you're using the https:// interface rather than the http:// one. This isn't your fault. When you upgraded, the following things should have happened:

  • A dialog would have been shown asking if you wanted to disable lighttpd, as it is no longer needed
  • If you selected yes (the recommended option) it should have carried on as normal and bound the new web interface to port 80. If you selected no it would have bound the web interface to port 8080.

This is described in the announcement post, specifically:

I've seen a few instances where it has defaulted to port 8080 unexpectedly - and we're still trying to get to the bottom of that, and I can see from your debug token that the plain HTTP interface has indeed defaulted to port 8080. however there are two things you can try to see if there are any improvements:

Something we have noted is that on some older hardware, the HTTPS interface can be very slow due to the increased load on encrypting each request.

If you are only accessing the interface internally, there is no need for HTTPS so you can use the HTTP one instead - this should be much faster for you!

I did select YES to disable lighttpd. My browser changes http to https. I use Firefox. I disable autofill yet it still changes to https. I try Chrome (Brave), refused to connect error. I try Edge, same refused to connect error. My bookmark for Pi-hole is http://192.168.2.254/admin/ I use Microsoft Defender for anti-virus and firewall. Can that be the problem?


Also, the speed is only part of the issue. I have several static IPs set up. I no longer see the static IP chart under Settings>DHCP. I now don't know what is set up and what is not and what the IPs are that I set up. Why was the feature removed in v6?

Well, this is going to sound a bit strange but as I have had a Pi-hole session open all morning and have been going back and forth from this discourse to the Pi-hole session, it seems as if the speed issue has gone away! Strange as it may sound, it is navigating at a reasonable speed. Did it fix itself? This leaves the main issue I have with v6 being the missing static DHCP chart and the fact that I cannot access it with http://