That’s the “getting better at not screwing up” part.
That’s the “getting better at not screwing up” part.
Y’all need high availability in your lives.
Because they killed google podcasts and moved it to YouTube music before they had basic equivalent functionality ready.
Giant shirtless executioners then, I guess.
Ark survival evolved is one of my personal favorites
Website is amazingly responsive as well, seems to be working.
This failure essentially means there’s an issue at either the DNS or TLS layers. I’d start looking at TLS, namely trusted root certs and OpenSSL.
As an operator, this who thread reads like a bunch of devs who don’t understand networking and refuse to learn.
Sure, for smaller applications or small dev teams it doesn’t make sense. But for so many other things it does.
Agreed, IaC has helped that process a lot. I just used to curse.
I agree. However… I do have a public repo with my helper scripts in case I need to set them up on a new machine. best of both worlds!
If I had to guess after managing enterprise WAF across hundreds of domains…
It’s either a crowler or vulnerability scanner, and may be scanning by IP address. I don’t think you configured anything wrong.
You may want to add some form of captcha or user agent based filter to get rid of it. Good news is that it’s not necessarily something to worry about.
I’d avoid IP based blocking. It’s only temporarily effective.
I’m personally using Mint for this exact purpose. It just works and I don’t have to think about it much.
I love Mint for the simplicity. My only complaint is the lack of Wayland support for cinnamon.
Nor should it be.
I’m in this comment and I don’t know how to feel about it.
I see 803 forks currently, keep up the good work!
Yeah, exactly. I was about to say flatpak exists and isn’t proprietary.
Also, the snap for docker/compose is hot garbage.