My team has been receiving API 403 errors on and off since January. They have been much more common in the last week so I am finally reaching out. These issues below are similar but they have been marked as resolved.
My response looks like:
Request blocked.
We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n’
This is blocking our team’s webhooks and is a critical issue for us. I would use the deprecated api but it looks like it will be sunsetted soon. Any assistance is created
Me too! I was going crazy thinking it was my fault. In my case, I did discuss with Asana a bit, and it was potentially related to me calling the “get token from refresh token” endpoint too often. In your case it happens with which endpoint?
Hey I’m getting this error as well. Using asana-python package (v5.1.0) deployed in a Cloud Run instance, though it works locally.
\n\nERROR: The request could not be satisfied\n\n
403 ERROR
\n
The request could not be satisfied.
\n\nRequest blocked.\nWe can\'t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n \nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n \
Hi @Gopesh_Kosala, to help our Infra team investigate are you able to provide us with:
Request ID
API URI
Timestamp
Of your most recent issue.
Our Infra team looked up the information about the issue you posted here but that log looks to be a few days old. If you encounter more or any recent ones (i.e., in the last day) please provide us with the above information.
Hey there! We’re running into exactly the same issue: on and off 403 errors seemingly related to Cloudfront. We’re calling the Asana API via python in a GCP app engine instance. We’re currently on version 5.0.7 of the asana API.
Is there any indication that this is an error on our end (users of the API)? Or is this an asana-side issue? Is this something that we could handle on our end by building in retry logic when we encounter 403s?
We have been investigating this issue off-and-on, but unfortunately we don’t have a whole lot of information based on where these errors seem to be generated. It would be incredibly useful if you encounter a 403 error from cloudfront to include:
timestamp of the error
the cloudfront request ID
the response body you receive
all response headers, if you can provide those
API endpoint you are attempting to hit
How you are making the request, especially anything notable about headers or transfer encoding
My hypothesis right now is your legitimate requests are being mistakenly rejected by our firewall, but datapoints are limited (plus we have a huge volume of actually unauthorized traffic that should receive a 403 response that adds a ton of noise to our signals).
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: UzrDC7FTlZ9kDQKqnE-u9c1frnrgapafBeAYLHVI3MBtFXfsFN4aNg==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
Some timestamps:
2025-04-24 20:21:30.763 HAEC
2025-04-24 20:24:10.329 HAEC
2025-04-24 20:28:01.831 HAEC
The endpoints are never the same, I have several apps failing for various reasons, I can’t easily pinpoint right now, but I can dig deeper if needed.
I am not doing anything specific. What by that is that some of those apps are several years old, they work as expected most of the time.
Thanks for sharing those IDs! The good news is they appear to be the same failure shape as the pervious examples so at least there aren’t multiple issues we need to solve.
It looks like you may be using GCP for hosting - is that correct?
We’ve identified the likely root cause - an overeager firewall rule - and disabled the rule for now. I’d appreciate confirmation if you no longer see this category of failures, or, should you continue to receive 403 responses from CloudFront, additional request IDs to help us investigate and debug further.
Thank you for your patience as we worked through this.