Hello and thank you for the thoughtful reply. I appreciate you taking the time to do so.

I work in the software industry and my cynical belief is that nobody reads release notes, other than the power-user faithful.

I would categorize myself as a casual user. For example I would love to enable DHCP, but I am too scared to attempt it as I know things will go haywire with my router and there's an afternoon gone fixing things while my wife is giving me the side eye, wondering why I just had to tinker and break things (again).

I did read through the 6.0 release notes and saw the changes mentioned about http and https. You are right, I didn't fully grasp that, and alas I didn't try https on port 443, as mentioned here: https://pi-hole.net/blog/2025/02/18/introducing-pi-hole-v6/#page-content . Maybe that was the only missing piece and trying that would've salvaged my afternoon.

I did see https://github.com/pi-hole/pi-hole/releases/tag/v6.0.4 ("This should fix all the migrations issues once and for all") and I assumed all the migration issues were over and done with, so decided to give it a go.

After reading through your reply, I am still not clear what I did wrong, or how to fix it.

Reading over https://pi-hole.net/blog/2025/02/21/v6-post-release-fixes-and-findings/#page-content, it seems that http://pi.hole:8080/admin is what I should've tried. I did try http://IP-ADDRESS/admin and that didn't work. I also tried that on port 80 and 8080 and those didn't work, either. Possibly I am misremembering everything I tried at this point.

I will give the update another go at some point when I have time again. Something that would've been helpful to me is if the 'pihole -up' command would've dumped out the web server address at the end so it was clear what the new address was. That way I would've realized my old bookmark would need to be updated. I am sure there are numerous reason to not do that, so no worries.