New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Super Bot Fight Mode blocks RDP access #556
Comments
Thanks for flagging this one. This sounds like a rules issue, but we'll take a look and confirm. Also, are you using |
Thank you! It was The client failed with This is the firewall event: {
"action": "managed_challenge",
"clientASNDescription": "REDACTED",
"clientAsn": "REDACTED",
"clientCountryName": "US",
"clientIP": "REDACTED",
"clientRequestHTTPHost": "REDACTED",
"clientRequestHTTPMethodName": "GET",
"clientRequestHTTPProtocol": "HTTP/1.1",
"clientRequestPath": "/",
"clientRequestQuery": "",
"datetime": "REDACTED",
"rayName": "REDACTED",
"ruleId": "874a3e315c344b1281ad4f00046aab6f",
"rulesetId": "48ba18287c544bd7bdbe842a294f1ae2",
"source": "firewallManaged",
"userAgent": "Go-http-client/1.1",
"matchIndex": 0,
"metadata": [
{
"key": "ruleset_version",
"value": "4"
},
{
"key": "version",
"value": "3"
},
{
"key": "type",
"value": "customer"
}
],
"sampleInterval": 1
} I was able to connect to the CloudFlare access domain from within the browser and access the 200 OK page. I suppose the |
We are seeing things like git/Gitea be blocked:
Query string: |
Looks like Jenkins build jobs are also being blocked: Query string: |
Hi, I was having trouble connecting to a tunnel for RDP access and tried all suggested tips. After some luck, I found that this access was blocked in the firewall logs as:
Bot Fight Mode for Definite Bots
manage definite bots
Managed Challenge
So, I set Super Bot Fight Mode: Definitely automated to Allow and it works now.
Is this a documentation issue (should note allowing definite bots is required) or a CloudFlare rules issue (this traffic should not be detected as a bot)? I would prefer keeping the protection for bots, but I suppose I can also split out our domains between our teams and public URLs.
The text was updated successfully, but these errors were encountered: