it’s almost like it happens on a schedule, as it’s happening again right now. I mean, I have a schedule too, it could have been this way for a while, although it was working earlier today.
I verified that it is local to my network – at least, I tried that curl from a couple of systems I can ssh to on other networks, and got similar to you, but continue to get an error here with curl or browsers.
I tried it from a couple of other systems here, and I get an error. When I log in to my work VPN, I don’t get the error.
It’s possible that what appears transient is just the state of my work VPN connection, although I feel like I’m off the VPN enough that I’d have noticed the pattern. I’ll monitor that. And if that’s a workaround, I suppose it will do…