LOL Not really, but boy it has been a day. Started at 7:00 am and I finally resolved (?) the issue. In fact I’ve got through every last bit of my network, and at this point in the evening, I actually don’t have a solid reason why the issue was present. Something in my VPN settings glitched, or something got triggered on pFsense and got hung up…something, something with Tailscale. It wasn’t CLoudflare this time. LOL
You ever do so much to a problem that when you ‘fix’ it, you have no real idea what the fix truly was? You ever have a problem and find all the shit you cobbled together in the name of ‘just get it running and back online’? I did, and decided that I would fix that shit too. It took all flippin’ day.
You guys that do this for a living…I salute you! jebus crispies!
ETA: 8 bells and all’s well today.
“So what was the problem in the end?”
“Man, I don’t fucking know.”
- me, every goddamn time
It’s always DNS
Me with Windows issues.
Was it a Windows update?
Was it the release upgrade (e.g. 24H2 -> 25H2)?
Was it the restart?
Was it a driver update?
Some program specific bug?And due to bad naming, convoluted or outdated documentation or fucky SEO from spam sites pretending to know the fix that did X or Y…
At least with Linux you sort of can find the specific fix in a release from the merge/commit notes.
Relevant XKCD
Isn’t there always one? Seems so. LOL
I hate, hate, hate when I fix something and I don’t know why the fix worked (or what the fix even was…). I want my suffering to result in something learned so it doesn’t happen again.
I want my suffering to result in something learned so it doesn’t happen again.
Soooo much this. I’m down to learn about technology any day of the week. But when I ‘fix’ something and I don’t know what the ‘fix’ really was, it is a rush of mixed emotions. I am ecstatic relieved the problem is fixed, but left empty not having learned the ‘why it broke’ in the first place. And then I’m always fearful that the problem will gestate in my lab and rear it’s ugly head again at some other inopportune time.
This. If I pay the cost in frustration and anguish and soul-searching and demanding justice from an uncaring god, I want something for it. I want documentation. I want my lessons learned from the post incident review. I want something I can hack into mgmtConfig to make sure nothing else will do that too.
Struggling for no payoff is the absolute worst thing.
Sometimes the fix has been done but the effect takes a while. For a cache to age out or a change to propogate. It all depends on what you are working with/on. Or you made a change but forgot to restart a specific service.
Meanwhile even though you did a fix correctly and aren’t aware of it, since it doesn’t seem to work you change something else and break it again inadvertently.
Note to self: Scan lab for hidden cameras
How I fixed hardware acceleration on my NUC for Jellyfin.
My docs on how to install/enable HuC/GuC:
And to this day I am procrastinating upgrading my main docker host because I can’t be bothered to either inplace upgrade my Debian 10 (or 11) to a current release and then fix that I restart my whole journey and sacrifice a whole weekend on fixing my card house of a homelab/home infrastructure…
I understand.
I learned again for the nth time that home assistant doesnt like refreshing my cert, and I can’t go to the site to refresh the cert unless it has a valid cert…
Maybe I’ll fix it tomorrow. It’s valid again now.
Why not use a reverse proxy?
When I set it up, I did not know better.
Now? Inertia. Nginx already does it for other things, I haven’t bothered to move home assistant over because home assistant works ( all but one days in a cycle)
“inertia” is a much nicer word than “complacency”.
I’ll be borrowing that.
What’s holding you back from visiting the site to fix it? HSTS?
