i -think- i've sussed the issue with the loadbalancer; the firewall admin interface was running on port 443 and bound to all interfaces. it -seems- that, when the admin interface is running and haproxy starts up, sometimes when it's been online for a long while it'll not be able to bind..? or something?? i can't explain why it would work at all
not fully sure how long q.p was inaccessible, but basically HAProxy, the load-balancer that handles all q.p traffic, went down, and instead users were being served (for some reason) the login page for the firewall instead. we've been behind HAProxy since the beginning, all that's changed is we've moved from it running on a pfSense appliance, to an OPNsense appliance.
apologies for the outage (again) ._.
@Siphonay youtube thumbnails work for me (replying to ur now deleted tooter)
yeah sure i hate my last workplace for not questioning why someone with known complaints against him would be trying to get rid of the people who complained about him
i hate them for lots of things
but the thing i hate them the most for is making me start again
i'm in a better place now and all, but christ i hate feeling inexperienced like this .w.
absurd purple dweeb, nb/gay/poly, they/them pronouns pls. smooching @htw and @colon_three. runs queer.party. maffsie on birdsite
A silly instance of Mastodon for queer folk and non-queer folk alike. Let's be friends!