From 71ffb8804e47cb00051b66fb793925160a68d797 Mon Sep 17 00:00:00 2001 From: Bryson Zimmerman Date: Sun, 26 Nov 2023 12:26:49 -0500 Subject: [PATCH] Update Cloudflare-Side-Note.md (#64) * Update Cloudflare-Side-Note.md Added three options for bypassing the Browser Integrity Check * Apply suggestions from code review Markdown fix and wording simplification Co-authored-by: Frank Elsinga --------- Co-authored-by: Frank Elsinga --- Cloudflare-Side-Note.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Cloudflare-Side-Note.md b/Cloudflare-Side-Note.md index 7bc9466..5cacced 100644 --- a/Cloudflare-Side-Note.md +++ b/Cloudflare-Side-Note.md @@ -2,7 +2,10 @@ By default, Cloudflare is not API friendly including Uptime Kuma. Cloudflare may block requests from Uptime Kuma. -You need to disable "Browser Integrity Check" in Cloudflare Dashboard. +You need to disable or bypass "Browser Integrity Check" in Cloudflare Dashboard via one of these methods: +- (Easiest) Add your Uptime Kuma host IP address to [IP Access rules](https://developers.cloudflare.com/waf/tools/ip-access-rules/) as an Allowed address, optionally across every domain in your Cloudflare account +- Allow Uptime Kuma to [bypass the check via WAF Custom Rules](https://developers.cloudflare.com/waf/custom-rules/skip/), only applies to one domain at a time +- Use a [Configuration Rule](https://developers.cloudflare.com/rules/configuration-rules/) to disable the check for your Uptime Kuma IP address Related discussion: https://community.cloudflare.com/t/api-403-after-enabling-cloudflare/108078/6