René Mayrhofer :verified: 🇺🇦 🇹🇼<p>I declare partial success with much more aggressive connection, request, and transfer rate throttling in the embedded <a href="https://infosec.exchange/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nginx</span></a> instance that serves my static page (plus the dynamic link maze that caught the stupid "AI" scraper bots...) behind <a href="https://infosec.exchange/tags/traefik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>traefik</span></a> (causing the TLS termination part to be overloaded and blocking authenticated users from legitimate access).</p><p><a href="https://www.mayrhofer.eu.org/post/defenses-against-abusive-ai-scrapers/nginx-default.conf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">mayrhofer.eu.org/post/defenses</span><span class="invisible">-against-abusive-ai-scrapers/nginx-default.conf</span></a> is the current rate limiting config, <a href="https://www.mayrhofer.eu.org/post/defenses-against-abusive-ai-scrapers" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">mayrhofer.eu.org/post/defenses</span><span class="invisible">-against-abusive-ai-scrapers</span></a> has the explanations.</p><p>Something like <a href="https://blog.lrvt.de/configuring-crowdsec-with-traefik/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.lrvt.de/configuring-crowd</span><span class="invisible">sec-with-traefik/</span></a> will probably have to be the next level of escalation to deal with the issue on a global level.</p>