{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiftkbgykvw4a5xzg4uahmqiwktsfkfuhlxujtwf3pqhv3uor5zr4e",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mmvxvpbnt3j2"
  },
  "path": "/t/repeated-false-positive-abuse-handler-flags-on-new-space-creation/176290#post_1",
  "publishedAt": "2026-05-28T10:23:40.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Hello, my organization gets the following error every time we create a new Docker Space and push code to it:\n\n`runtime.abuse.detector = \"abuse-handler\"`, `reason = \"Blocked by abuse-handler by rule: Cloudflare\"`\n\nFlag fires ~2s after the first push, regardless of IP origin. We’ve tried multiple Space names, push patterns (orphan vs normal commits), and IPs from two different ISPs. Renaming existing healthy Spaces does NOT trigger it; only creation + push does.\n\nThe repo is a standard Flask + Next.js Docker app (~150 small files, 2.5 MB total). Other Spaces in the same org work normally with incremental commits via existing GitHub Actions workflows.\n\nHas anyone seen this and managed to get whitelisted? Should I open a private ticket instead?\n\nThanks.",
  "title": "Repeated false-positive abuse-handler flags on new Space creation"
}