Every so often, we’ll have a day where we’re suddenly blocked from accessing the API. I am guessing it must be IP based blocking, because I can still use the API token to make valid requests from a production console, but our background jobs process suddenly gets blocked from making requests.
When I’ve searched online, this seems to be some Cloudflare protection, but it’s a real nightmare when we’re suddenly unable to use the API for a few hours.
This is the top part of the HTML response (the status is always 403):
<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta http-equiv="X-UA-Compatible" content="IE=Edge"><meta name="robots" content="noindex,nofollow"><meta name="viewport" content="width=device-width,initial-scale=1"><link href="/cdn-cgi/styles/challenges.css" rel="stylesheet"><meta http-equiv="refresh" content="375"></head><body class="no-js"><div class="main-wrapper" role="main"><div class="main-content"><noscript><div id="challenge-error-title"><div class="h2"><span class="icon-wrapper"><div class="heading-icon warning-icon"></div></span><span id="challenge-error-text">Enable JavaScript and cookies to continue</span></div></div></noscript></div></div>
Following a redeployment, one of the processes actually regained access, but another one didn’t. Has anyone seen the same issue before / managed to fix in a reliable way that isn’t just “restart my application until it works again” ?
Thanks,
Alex