How do I revert to a previous version of Pi-hole?

robomaniac · March 3, 2018, 10:29pm

I have followed the instructions to go from 3.3 to 3.2.1 and it works! Got my pi-hole working again!

I did not have to remove the extra line in .conf file. I did not have log-queries=extra

Xtoftjen · March 27, 2018, 1:56pm

How to do this on synology?

jacob.salmela · March 28, 2018, 12:16am

It should be the same...none of the devs have a Synology to test on however.

Xtoftjen · March 28, 2018, 7:43am

cd /etc/.pihole gives the error "no such file or directory"
so I believe the installation folder is different on synology... hence it doesn't work

jacob.salmela · March 28, 2018, 11:39am

It shouldn't be. Try pihole -r

timbo · September 4, 2018, 4:01am

I am not successful in getting the webGUI operational anymore using commands above. Port 53 is listening but not port 80. I suspect that some git changes happened preventing this from working properly. I get git errors and seems to be related to clone depth set by the git server.

Anyone know how to get v3.2.1 working again? v4 is radioactive for me now.

Thanks

Edit: turned out it was the bug where lighttpd failed due to a missing external.conf. It blows my mind how programmers let their programs fail so easily instead of 'test if exists or else touch file' and remove a ton of hassles and problems when their programs lack basic defaults. SMH

Mcat12 · September 5, 2018, 1:53am

What version of lighttpd are you using? So far, it seems that the latest version of lighttpd has a bug/regression which causes that crash.

HellboyPi · September 8, 2018, 9:18pm

How to install Pi-hole v3.3.1 with Web Interface v3.3 and FTL v3.0 on a new system (fresh install, not reverting)?
I'm using a lot of wildcards. Transforming them into regex (Pi-hole v4.x) will impact performance.

I know I can preserve wildcard blocking in v4.x too, by putting the wildcards into another file (example: /etc/dnsmasq.d/88-wildcards.conf), but then I lose logging.

jfb · September 8, 2018, 9:29pm

What leads you to believe this will be the case?

HellboyPi · September 8, 2018, 9:36pm

I have 100000+ wildcards. Most of them are from the notracking domain blocklist. Such large number of wildcards transformed into regex could be problematic.

Found this thread on github:

github.com/pi-hole/FTL

Add user-defined wildcard blocking support

pi-hole:development ← pi-hole:new/show_config_NXDOMAIN_as_blocked

opened 09:41AM - 09 Aug 18 UTC

DL6ER

+17 -9

**By submitting this pull request, I confirm the following (please check boxes, …eg [X]) _Failure to fill the template will close your PR_:** ***Please submit all pull requests against the `development` branch. Failure to do so will delay or deny your request*** - [X] I have read and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md). - [X] I have checked that [another pull request](https://github.com/pi-hole/FTL/pulls) for this purpose does not exist. - [X] I have considered, and confirmed that this submission will be valuable to others. - [X] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [X] I give this submission freely, and claim no ownership to its content. **How familiar are you with the codebase?:** ## 10 --- Locally defined addresses, like ``` address=/my.home.device/192.168.1.123 ``` are shown as "OK (cached)" in the Query Log page. However, users may want to use advanced configurations to implement wildcard blocking behavior using config files and do not want to see these queries being denoted as "OK (cached)" but rather "Pi-holed (wildcard)". This PR adds support for such blocking configurations where we add support for two ways of blocking through config files: 1. `server=/domain/` syntax Example: ``` server=/tobeblocked.com/ ``` This configuration will return `NXDOMAIN` for any request to the domain `tobeblocked.com` ![screenshot at 2018-08-09 11-25-48](https://user-images.githubusercontent.com/16748619/43890900-46bb81c4-9bc8-11e8-8a68-1074c550b78a.png) 2. `address=/domain/ipaddress` syntax Example: ``` address=/tobeblocked2.com/0.0.0.0 address=/tobeblocked2.com/:: ``` This configuration will return `NXDOMAIN` for any request to the domain `tobeblocked.com` ![screenshot at 2018-08-09 11-29-01](https://user-images.githubusercontent.com/16748619/43890982-840dc474-9bc8-11e8-874d-4d98c6fd8f32.png) It should be pointed out that the `address=/.../...` syntax is preferred as many clients show anormal behavior when receiving `NXDOMAIN` replies (for instance, some versions of Firefox re-query domains replied with `NXDOMAIN` more than ten times). _This template was created based on the work of [`udemy-dl`](https://github.com/nishad/udemy-dl/blob/master/LICENSE)._

Possible solution for wildcard logging in v4.x?

DL6ER · September 8, 2018, 10:29pm

Yes, these changes are already in the development version of pihole-FTL and will become available in Pi-hole v4.1.

jfb · September 8, 2018, 11:55pm

Your options appear to be (in what I believe would be the best first order):

Keep running your existing address list as you propose, use V4 and don't convert them to regex. Live without logging until 4.1 (blocking still works properly).
Move your Pi-Hole install to the development branch (with the attendant risks of using development code). You'll get the logging you are looking for.
Revert to previous version - older code, not as fast, etc.

nickie · March 20, 2022, 9:05am

I needed to check if the older version was better in terms of blocking ads with my regular expressions.
It now tells me
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (v5.13) and might be missing future releases.

How do I get to remove this and let it go with the normal updates it finds? I get an update available in the admin space (cause there is the v5.14 available)

P.S.: there is something broken on pihole 5.9. I am reverting to 5.8.1

Koneesha · May 27, 2023, 9:21pm

Would this still be the correct way to revert to a previous version? I have trouble when I try to do the ftl checkout. It never actually finishes anything.

Also how would I know the correct FTL version to get?

yubiuser · May 27, 2023, 9:48pm

Reverting to a previous version in general is not supported. It can work out, but as all components might depend on each other checking out only a single old component might break your Pi-hole.

If you experience an issue, please open a new thread.

Koneesha · May 27, 2023, 10:17pm

Hi yubiuser,

The reason why I would just like to revert back a month or two is because I just updated to the latest version a week or two ago, and since then I have had all sorts of trouble with my existing network. The only change that has been made is the update, and I am curious if that is the culprit.

This is not a permanent solution but just a temporary one so I can sort out my next steps. I have a few google onhubs that are in the network right now and Google has dropped support for them so I cannot change any settings they have.

Because of this I would like to dowgrade to see if that fixes up the network or whether the onHubs are the ones to blame, and then if I would need to buy new network equipment.

yubiuser · May 28, 2023, 8:34am

You can revert the DNS part (FTL) by checking out an older tag like mentioned above. However, you can't checkout older tags on core and web yet. (This will be implemented by Allow to checkout tags via `pihole checkout` by yubiuser · Pull Request #5259 · pi-hole/pi-hole · GitHub - however, checking out core tags before the release of this PR will always fails)

PromoFaux · May 28, 2023, 11:55am

I'd say probably the safest way (and likely easiest) to switch between versions would be to deploy Pi-hole via Docker instead