XF Bot Guard

XF Bot Guard 1.4.1

No permission to download
is this addon hiding the rss image link from the footer lol? probably not. i just noticed it missing and now i would have to investigate that lol. the code appears to be there. it is just not appearing for me.
 
is this addon hiding the rss image link from the footer lol? probably not. i just noticed it missing and now i would have to investigate that lol. the code appears to be there. it is just not appearing for me.

No it shouldn't be. It doesn't modify page content at all, with exception to the specific enabled features.
 
yeah it was something else. weird stuff.

so adding index.rss does not appear to work. i have to enter full path to get it to work forums/-/index.rss. is this how it is supposed to work? or just file name should whitelist it for the entire site?
 
yeah it was something else. weird stuff.

so adding index.rss does not appear to work. i have to enter full path to get it to work forums/-/index.rss. is this how it is supposed to work? or just file name should whitelist it for the entire site?

Its a wildcard at the end by default, sorry, it's nearly midnight here and I am tired. It may be better if I just create an option specifically for excluding RSS feed content from protection.
 
that would be nice tbh. because there are rss feeds for forums, and search forums (and more?) and it is just impossible to whitelist them all.
 
so i do not have a second install to verify this but there is something i noticed just now.

addon has a whitelist for xenforo user-agent to allow embedding of links from same forum and others for proper unfurling. this appears to work for page links. but i cannot get them to work for post links. i even whitelisted the ips but even that does not appear to help. just posting here as a fyi and if others could confirm this.

for example. if xenforo community was running the addon:

a link like this https://xenforo.com/community/threads/xf-bot-guard.237990/page-34 unfurls properly.
but a link like this https://xenforo.com/community/threads/xf-bot-guard.237990/post-1786087 does not.

i can assume this is due to addon using light response to provide the required content. but i am not sure why whitelisting the server's ip in my case did not help (not on cloudflare at the moment so it should have worked?).
 
so i do not have a second install to verify this but there is something i noticed just now.

addon has a whitelist for xenforo user-agent to allow embedding of links from same forum and others for proper unfurling. this appears to work for page links. but i cannot get them to work for post links. i even whitelisted the ips but even that does not appear to help. just posting here as a fyi and if others could confirm this.

for example. if xenforo community was running the addon:

a link like this https://xenforo.com/community/threads/xf-bot-guard.237990/page-34 unfurls properly.
but a link like this https://xenforo.com/community/threads/xf-bot-guard.237990/post-1786087 does not.

i can assume this is due to addon using light response to provide the required content. but i am not sure why whitelisting the server's ip in my case did not help (not on cloudflare at the moment so it should have worked?).

Good find. I see the issue and I am preparing a bug fix now. I will be in the next release! Thank you.
 
I sometimes wonder if you even sleep, given the pace at which you release updates for what is actually quite a complex add-on. Great work! (y)
But also look after your own mental health—that’s more important than super-fast updates. ;-) :-)

I was still on v1.2.5 and wanted to move to v1.3.3; I got an error message stating that I needed to update to at least v1.2.9 first before going to v1.3.3—which then worked fine.

I think the presets idea is excellent, because I’m slowly losing track of what settings I should be using and how. That’s great!

However, I’ve run into a bit of a problem now that I’m not quite sure how to handle—how can I resolve this blocker/error? :unsure:
1782203589246.webp
1782204800526.webp

To make matters worse, I’m actually a native German speaker; while I can read and understand English reasonably well, I do stumble a bit here and there. So don't be mad if this turns out to be a stupid question. I'm just a potato, after all. :giggle:😁
 
Last edited:
I sometimes wonder if you even sleep, given the pace at which you release updates for what is actually quite a complex add-on. Great work! (y)
But also look after your own mental health—that’s more important than super-fast updates. ;-) :-)

I was still on v1.2.5 and wanted to move to v1.3.3; I got an error message stating that I needed to update to at least v1.2.9 first before going to v1.3.3—which then worked fine.

I think the presets idea is excellent, because I’m slowly losing track of what settings I should be using and how. That’s great!

However, I’ve run into a bit of a problem now that I’m not quite sure how to handle—how can I resolve this blocker/error? :unsure:
View attachment 340391
View attachment 340393

To make matters worse, I’m actually a native German speaker; while I can read and understand English reasonably well, I do stumble a bit here and there. So don't be mad if this turns out to be a stupid question. I'm just a potato, after all. :giggle:😁

I assume you have the option to allow safe AI crawlers enabled. And what happens, is those sources will be refreshed by the hourly "XF Bot Guard known crawler refresh" cron. If you go and run that cron now, then revisit the health check page - it should be cleared of issue.
 
I sometimes wonder if you even sleep, given the pace at which you release updates for what is actually quite a complex add-on. Great work! (y)
But also look after your own mental health—that’s more important than super-fast updates. ;-) :-)

p.s., appreciate your concern. We've been struck with gastro as a household for the last week. So, a lot of time on my hands sitting around feeling miserable. Slowly getting better now.
 
A small update regarding Yandex. Not all IP addresses the bot uses provide RDNs records. Therefore, the bot may be partially blocked. Two more ASNs need to be whitelisted:
AS13238 # YANDEX LLC
AS44534 # YANDEX (additional network)
 
Last edited:
That's true, but if Yandex is important to you as a search engine, then that's the webmaster's problem.
 
A small update regarding Yandex. Not all IP addresses the bot uses provide RDNs records. Therefore, the bot may be partially blocked. Two more ASNs need to be whitelisted:
AS13238 # YANDEX LLC
AS44534 # YANDEX (additional network)

If you want to add the Yandex IP's / CIDR's to "Excluded IPs/CIDRs/ASNs", then I would add the ones from their page here:


I didn't add these as they don't provide it as a JSON resource like most other search engines do, but I did add rDNS support for them (although as you point out, they may not be implementing this properly on their end, which is something they should resolve).
 
I sometimes wonder if you even sleep, given the pace at which you release updates for what is actually quite a complex add-on. Great work! (y)
But also look after your own mental health—that’s more important than super-fast updates. ;-) :-)

I was still on v1.2.5 and wanted to move to v1.3.3; I got an error message stating that I needed to update to at least v1.2.9 first before going to v1.3.3—which then worked fine.

I think the presets idea is excellent, because I’m slowly losing track of what settings I should be using and how. That’s great!

However, I’ve run into a bit of a problem now that I’m not quite sure how to handle—how can I resolve this blocker/error? :unsure:
View attachment 340391
View attachment 340393

To make matters worse, I’m actually a native German speaker; while I can read and understand English reasonably well, I do stumble a bit here and there. So don't be mad if this turns out to be a stupid question. I'm just a potato, after all. :giggle:😁
I got the same as a warning on version 1.3.3
Screenshot_2026-06-23-22-14-54-235 (1).webp

I assume you have the option to allow safe AI crawlers enabled. And what happens, is those sources will be refreshed by the hourly "XF Bot Guard known crawler refresh" cron. If you go and run that cron now, then revisit the health check page - it should be cleared of issue.
Running "XF Bot Guard known crawler refresh" cron did not work.
 
I will look into reasons why this could happen. There may be a part of that process which is quitting when it shouldn't. But not to worry, the definitions it has are no doubt fine at this point.
 
Back
Top Bottom