jwbjnwolf
commented
1 year ago Hey see my issue. https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/issues/509
Two things I noticed: One: if using the deny.d conf, by default it blocks .well-known too, which is important I think when it comes to federating with fedi instances.
Two: there is an entry for ninja as a user agent and results in any instance with ninja in the domain, or it's a .ninja domain, it's going to get blocked so you'll need to add that to the allow list for user agents. Going to go through that global list more myself to see what others can be an issue and will update if I see any more.
Edit: Had a look, looks like ninja is the only entry that's an issue from the global list for useragents.
Bit late to your issue though hope helps regardless.
Ok, anarchy is another keyword that's getting useragent blocked too.
Added list to add to allow list of what will definitely lead to false flags in regards to fedi instances. https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/issues/509#issuecomment-1485861526
I run a Mastodon server for a long time now (with this Blocker) and another server owner told me she had connection issues with my server. After some investigation I found out that disabling the Nginx Ultimate Bad Bot Blocker fixed the problem, although her IP address and domain where not blacklisted. Because I still wanted to run the Blocker, I whitelisted the IP address of her server anyway, but unfortunately this didn't work.
Are there any other places inside or outside the globalblacklist I should look? I never had issues with this Blocker interfering with other Mastodon servers before.