V5 to v6 2024.07 to 2025.02.1

Is there anything that I need to do during or after the upgrade
I did quickly read the changes and warnings
I make a copy of the v5 config volume map
everything seems to be working but I just want to make sure I have no overlooked anything

is "-e WEBPASSWORD" still correct as I think that is an environment variable
and is "--dns" still valid

I also had custom dhcp assignment in dnsmasq.d/04-pihole-static-shcp.conf I was told I shouldn't have ever edited that file, but what my custom line did was give all unknow devices an address in the 192.168.255.X subnet which was then blocked by a group

I don't mind if this is broken I will just use ignore unknow clients from the GUI

It shows everything is working but it is clearly not this website just went to an nginx error page and took a while to load

my DNS cache metrics also keep resetting

You are using the Docker Container version so you need to migrate your Compose YAML file to the latest version too !!

Basically combine the new v6 YAML and the one you are using now for v5 :wink:

I don't use docker compose, only docker run

I am not an Expert when it comes to Docker but what I mean is the configuration file that goes with your Pi-Hole Container : A LOT has changed from v5 to v6 !! :wink:

as far as I know, there was an automatic conversion of files, every is working, but discourse.pi-hole.net seems really slow loading and I wanted to know about my environment variables

and I would also like some more information on DNS cache optimizer, do it mean the cache does not expire for the time given?

I said your website kept not working
Did it go down

Anyway, I will see how pi-hole runs today, and report back if I have any issues

A post was split to a new topic: Greyscale Query graph on iPhone?

OK, but still : Have a look at Upgrading from v5.x - Pi-hole documentation and check your Docker Container configuration :wink:

No, it isn't.

All of your Pi-hole container's environment variables (as prefixed by -e in a docker run script) should be scrutinised as per our Docker Upgrading from v5.x - Pi-hole documentation.

Other Docker configuration options (like your --dns) remain valid, as they are specific to Docker rather than Pi-hole.

1 Like

sorry but your not being helpful
Its working, I just have a few minor issues

I though it wasn't, but the container is still working, this password must be stored in the database as well

so my main issues at the minute are:

Screenshot 2025-02-19 223723
Should the docker tag be a hyperlink like it used to be

This is the whole reason I took a break from here, no one has actually gave any information about the possible bugs I have found, yes the documentation will help with the variables but that's not going to fix the grey query graph or the fact the docker tag is no a hyperlink

I've split your funny colours post into a separate topic, as its unrelated to your question about your Pi-hole container's environment variables, and thus will need to find a separate solution.

With regards to this topic. I consider Pi-hole's documentation on upgrading from a v5 container to a v6 one as both relevant and helpful to your original question.

I'd also like to remind you about your attitude:
It seems unfair and contradictive that you are abusing nero355 as 'not being helpful', while you are telling me that 'the documentation will help with the variables' when both of us were providing the exact same link, in an effort to answer your original question.

If you continue this way, I'd be rather reluctant to answer any of your posts anymore.

2 Likes

Sorry @nero355, I didn’t mean it like that, the fact is you have said the same thing like three times, and was reacting like my pi-hole was not working, I did overreact and I am sorry for that

I already know I did wrong, and regret saying what I did, I am really trying to be better this time, but sometimes I hit reply without fully thinking
What you don’t see is the amount of post I actually never send at all

1 Like

Also don't know if this is expected but on FTL reload, all the metrics are lost

The lease time can be in seconds, minutes (e.g., "45m"), hours (e.g., "1h"),
days (like "2d"), or even weeks ("1w"). If no lease time is specified (empty),
dnsmasq's default lease time is one hour for IPv4 and one day for IPv6. You
may also use "infinite" as string but be aware of the drawbacks: assigned
addresses are will only be made available again after the lease time has passed
or when leases are manually deleted below.

is that a mistake, as I was told pi-hole DHCP is not using dnsmasq

Pi-Hole is using DNSmasq for years now : It's called FTLDNS and is basically DNSmasq as base and then some extra goodies on top! :wink:

so is it using dnsmasq but he custom FTLDNS version
wouldn't that be better worded as FTLDNS instead of dnsmasq to avoid confusing with normal dnsmasq as the options are slightly different from normal dnsmasq now

04-pihole-static-dhcp.conf was exactly the same as what you would find in dnsmasq
the syntax has changed slightly in V6 as its now in pihole.toml

or am I completely wrong here

the only thing I really have an issue with now is the fact the docker tag is not a hyperlink to the github page for that tag like how it is with the versions

Yes. Some would call it forked version.

I think it's a bit of an assumption that we all know that FTLDNS is DNSmasq but who knows : Maybe it will change in the future ?! :slight_smile:

Could be. And indeed : pihole.toml now keeps ALL the Settings you will ever need pretty much :slight_smile: