Allow MonitorPro through Cloudflare

If Cloudflare returns a challenge instead of the website, MonitorPro may report DOWN or fail a content check.

1. Inspect Cloudflare Security Events to identify the rule or product challenging the request.
2. Identify the public egress IP of the server that performs these MonitorPro checks. Include each checking server deliberately.
3. In Cloudflare Security rules, choose Create rule → Custom rules.
4. Match the intended source IPs. You can also require the User-Agent to contain cPFence MonitorPro.
5. Choose Skip, select only the necessary security components, and save.
6. Run a new MonitorPro check and inspect both its result and Cloudflare events.

Follow Cloudflare’s Skip rule instructions and available skip options. Free Bot Fight Mode cannot be skipped by this action.

Do not trust User-Agent alone

Clients can copy a User-Agent. Restrict the exception to known monitoring sources and avoid a broad skip of every security feature. A changed egress IP needs a reviewed rule update.

MonitorPro’s matching User-Agent is cPFence MonitorPro; a rule save does not establish a successful check.