Hi,
I am trying to link a Patreon account from my WordPress site and the OAuth flow is being blocked on Patreon’s authorize page before the callback is reached.
What happens:
-
User clicks “Link Patreon” on our site
-
Our site redirects the browser to Patreon OAuth authorize
-
Patreon responds with a Cloudflare block page instead of showing the authorize/consent screen
-
Our callback endpoint is never hit
Error shown by Patreon/Cloudflare:
-
“Sorry, you have been blocked”
-
“You are unable to access patreon.com”
Cloudflare details from the blocked page:
-
Ray ID: 9df9388269aef582
-
Source IP shown on the page: 87.110.25.11
OAuth details:
-
Authorize endpoint: https://www.patreon.com/oauth2/authorize
-
Response type: code
-
Scope: identity identity.memberships
-
Redirect URI: https://test.alltd.org/wp-json/alltd/v1/auth/patreon/callback
Important context:
-
This is a normal browser redirect flow, not a server-side fetch to the authorize endpoint
-
The callback URI above is the one our app uses at runtime
-
The block happens on Patreon before any callback or token exchange occurs
I found a few older forum threads where Patreon staff asked for Ray IDs and source IPs for Cloudflare investigation, so I’m providing both here.
Could someone check whether this request or IP is being blocked by Patreon/Cloudflare, or whether there is any client-side callback validation issue that can surface as this block page?
If needed, I can provide the full authorize URL parameters privately.
Thanks
Jan
PS:
I also reproduced the exact same Cloudflare block from a separate temporary local smoke-test page that bypasses our normal Profile UI and launches the same Patreon authorize flow directly. The new Ray ID is 9e0e7f195952a872, and Patreon still shows source IP 87.110.25.11. This suggests the issue is not specific to our site UI and may be a Cloudflare/WAF block against this client IP/session during the browser authorize step.