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!
Some issues are like that, you fix the issue presented and find more issues to fix.
I do it for a day job and have had issues that I can’t explain as anything more than restart a service and now it works, I also run my own kit and have had the same type of issue.
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.
This. If I pay the cost in frustration and anguish and soul-searching and demanding justice from an uncaring god, I want some thing 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.
“So what was the problem in the end?”
“Man, I don’t fucking know.”
- me, every goddamn time
It’s always DNS
Touch it until it works, then never again while it still does.
When you do it for work, you log what you have changed each time you make a change to try to fix it, and you log what you revert, so you can keep track of what you have tried, what worked, and what didn’t and have a clearer idea of what the solution was.
Sometimes it really does take a while to nail down though, and sometimes it isn’t entirely clear why what worked worked. Especially if you’re a junior network engineer without as much experience.
and we do it at work because it makes things easier in the long run!
great idea to do some of this stuff at home too.
Sometimes the problem isn’t on your end. The server might be having issues, or your ISP. Have to rule those out too.
I had bizarre DNS issue I could not figure out. It ended up being that I turned on hardware routing/NAT on my OpenWRT box and then forgot about it
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?
Yeah I’ve got home assistant, a thing built for automating, but I leave that shit to certbot lol
