The #pihole tells me everything needs to be updated. I seldom update under the theory if it ain't broke, don't fix it, but I don't want to get too far behind because that causes problems too. Like, when I tried to run the "pihole -up" command, it failed and said I needed to do "apt update". But that failed because I guess code name "buster" is too old. So now I have to upgrade the #raspbian OS. Why, oh why, do I have a bad feeling about this?

It took me just shy of 2 f'ing hours to get #raspian migrated from buster to bullseye because it totally broke the networking. The pi's Ethernet interface was no longer configured. Fortunately, I could connect my laptop directly to my modem and use Gemini to walk me through the extensive repairs. I had to switch networking services, create and modify config files. Un-f'ing-believable! An OS upgrade should NEVER break networking, but here we are. Sigh. Everything is back to norbal*.

*See my bio.

I'm now getting 403 Forbidden errors trying to access the pi-hole, which was working but now is not because … 🤷🏼‍♂️ Gemini and ChatGPT have so far failed to resolve the issue. I hate computers.

Day 2 of trying to get my #pihole running on raspbian bullseye. I kept getting 403 Forbidden errors when accessing the dashboard. ChatGPT and Gemini failed totally and kept going around in circles constantly telling me to change file ownership back and forth. All bogus.

Finally, I asked Claude to assume nothing and take me step-by-step through the debug process. It took 60(!), count 'em, steps but it did resolve the issue. There is no way in hell I could have solved this myself.

If A.I. couldn't solve it my next step would be to flash a new SD card and restore my configuration from backup. I don't even remember how I did this the first time.

And this is the reason why I dread even incremental upgrades because the people who code them assume so much knowledge. The pi-hole is great, but maybe I should have bought an appliance.