404 and no DNS after recent update

Ok so i just logging in to the webGUI and saw there where some updates for all parts of pi-hole.

So i logged in thru SSH and did a pihole -up but while this process ran the DNS resolution part got stuck and the DNS resolver never came back up even after 30 min of waiting the dots kept coming that the updater was waiting for the DSN resolver to come back up.

So i did a ctrl+c and afterwards i could not reach the webGUI and more and i could not reach the internet again not on any page so the DNS resolver still didn't work.

I then rebooted my pihole and it still didn,t work somehow i get a 404 when i try to reach the webgui and blocking is still broken?

Please note this setup ran for over 5 years without problems (i have updated may times over this period)
As a temporary fix i added a second DNS to my ASUS router (8.8.8.8) so my network is somewhat functional right now but the pihole is not working as it should.

I, am running pihole stock image on a raspberry pi zero w and i still have SSH access to the installation.
I already ran a pihole -r that was successful but also did not fix the problems.

I have added added a pihole -d -a debug file to this ticket hope someone can give me some hints what went wrong and how to fix them?

Expected Behavior:

I should be able to access the webgui and the pihile should resolve my DNS requests.

Actual Behavior:

can,t reach the webGUI and the pihole does not resolve any DNS requests

Debug Token:

(https://tricorder.pi-hole.net/6fzE5RH3/)

Just found this topic with a similar problem

and this fixed my webgui for now but now i get the error " no upstream servers configured"

What the hell happened with this update? it always worked perfectly without issues and i had it set to recursive DNS and now its all gone?

Seeing a lot of the other topic starting popping up about V6 i think i will just revered back to an backup of yesterday because this is not funny anymore.

p.s. just revered back to 5.x.x and everything works like a charm i also see a thread popping up about HA integration of V6 so for now i will stick to version 5.

And as suggested i another thread please inform users about a major release like this in advanced not everyone has a backup system in place like i do and will have a lot of problems that could have been solved if ppl know this is a major update before they install it.

p.s.s. you can close this ticket

Did you read this before upgrading? Specifically section upgrading and getting started Introducing Pi-hole v6 - Announcements - Pi-hole Userspace

1 Like

Nope

like i mentioned i did not think v5 to v6 would break so many things with so many ppl (as seen on the frontpage right now every min there is a new post about problems upgrading)

Think they also did not read the link you just posted :wink:

Please also note

danschaper his post that it would be a good idea to announce this to everyone before pihole -up is completed :wink:

I got to give credit to the development team and moderator. Not only they make the announcement of a major upgrade but also follow up on the forum with troubleshooting. Sure you get hiccup, but things do break, but solvable and they do a good job following thru.

When I do a pihole -v and see an v5.x.x to v6.x.x, that tells me it's a major upgrade and I check the forum for the official announcement

2 Likes

This happened to me last night as well--for years I have updated my pihole without any issues, but not reading the changes in a major release is my own fault.

So is the following command all we need to "fix" our issue in regards to the DNS upstream?

pihole-FTL --config dns.upstreams 8.8.8.8

Thank you.

If you want to use Google DNS as Upstream then YES! :slight_smile:

You can also use one of the other options ofcourse : 1.1.1.1/9.9.9.9/and so on...

1 Like

TIP! for the next time something like that happens :

  • Start another SSH session to your Pi-Hole.
  • Change the DNS Server used by the OS the way that applies to your situation.
  • Restart the network service used by your OS.

You will now see the Pi-Hole update process finishing succesfully :wink:

Once everything is up and running again you can change the DNS Server used by your OS back to the Pi-Hole : 127.0.0.1

Your debug log shows the web server used by Pi-hole v5 (lighttpd) is still running.

[✗] tcp:0.0.0.0:80 is in use by lighttpd

and the new web server is not able to start.

If you don't use lighttpd anymore, disable it with:

sudo systemctl stop lighttpd.service
sudo systemctl disable lighttpd.service

and restart FTL with:

sudo systemctl restart pihole-FTL.service

Thanks for the reply but as stated in my second post this problem was already solved by another user with the same problem after upgrading to v6.

Anyway i will not be upgrading to v6 for a long time until everything is fixed i understand i had to read all articles and patch notes beforehand but nothing in those notes mentioned anything about the following problems.

  1. Home assistant integration is fully broken with V6 and nothing about this problem can be found in the patch notes. So reading the patch notes could not have prepared me for the fact this would break?

  2. Hosts files is completely and utterly ignored by V6 no idea why and or how but yet again nothing about this problem in the patch notes?

  3. All my recursive DNS options have been deleted as part of this upgrade so after upgrading and fixing the webGUI there was no working DNS resolver offcourse i could have used 8.8.8.8 or 1.1.1.1 in my router but this is not a solution for using recursive DNS with the pi-hole?

Please don,t take this the wrong way i love pi-hole and think the devs are great and all but like i said earlier and someone else also opted here it would have been nice if i typed "pihole -up" and the first message would have been something in the line of:

"please be aware that this update is seen as a major update and might change/reset or remove your configuration completely. please follow this link for more information and press N to cancel the update/upgrade process"

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.