Title: 502 Errors When Site is Proxied via Cloudflare

What is the name of the domain?

arrangerforhirecom

What is the error number?

502

What is the error message?

Bad Gateway

What is the issue you’re encountering

Site won’t load if it’s proxied

What steps have you taken to resolve the issue?

Turn off proxy

What are the steps to reproduce the issue?

Turn on proxy

Hi everyone,

I’m managing several WordPress sites hosted on A2 Hosting and routed through Cloudflare. One of them has recently become inaccessible when Cloudflare proxying is enabled.

:magnifying_glass_tilted_left: Current Behavior:
With Cloudflare proxy enabled (orange cloud) → arrangerforhire.com returns a 502 Bad Gateway error
With Cloudflare proxy disabled (gray cloud) → site loads normally, no errors
This happens regardless of whether Firewall Rules are enabled or not
:fast_reverse_button: Recent Context:
I had created a Firewall Rule to skip WAF, Bot Fight Mode, and rate limits for Jetpack’s known IP ranges, after getting a series of Jetpack uptime alerts over the past few days.
Those downtime alerts may or may not have been valid, but now the site won’t load at all when proxied.
I’ve verified that the origin server is functioning normally via direct access (hosts file test).
No recent plugin changes, and the server itself hasn’t gone offline or overloaded.
:puzzle_piece: Questions:
Is there anything in Cloudflare’s proxying behavior (free plan) that might trigger a 502 even when the origin server is healthy?
Could this relate to the previous Firewall Rule setup for Jetpack (even though it’s now deactivated)?
Is there any way to pinpoint exactly why Cloudflare can’t fetch from the origin in this case?
Any guidance is appreciated! I’d love to bring Cloudflare proxying back online, but only if it’s going to work reliably.

Other sites on the same host (also routed through Cloudflare) include:

Thanks in advance!