I’m forced to use it at work. It’s the worst because it has so many limitations and performance issues. I’m not satisfied because it’s assumed to be an equivalent and it’s not.

This, and they may have released smolts there after removing the dam.

Y’all need high availability in your lives.

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.

Best way to make the switch is by immersion. I’d also like to add it’s best to do it when you’re not being forced on a timeline, and you have time to deal with it. All my personal machines made the jump 7 years ago and I don’t regret it.

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 see 803 forks currently, keep up the good work!