mirror of
https://github.com/louislam/uptime-kuma.git
synced 2024-11-27 16:54:04 +00:00
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 <frank@elsinga.de> --------- Co-authored-by: Frank Elsinga <frank@elsinga.de>
parent
1191165924
commit
71ffb8804e
1 changed files with 4 additions and 1 deletions
|
@ -2,7 +2,10 @@
|
||||||
|
|
||||||
By default, Cloudflare is not API friendly including Uptime Kuma. Cloudflare may block requests from Uptime Kuma.
|
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
|
Related discussion: https://community.cloudflare.com/t/api-403-after-enabling-cloudflare/108078/6
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue