# Cloudfront API errors after infrastructure change

**URL:** <https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486>\
**Category:** API & Developers\
**Created:** [28 March 2025 11:46 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486 "2025-03-28T11:46:31Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Titus\_Smith](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/titus_smith/32/101553_2.png) [@Titus\_Smith](https://forum.asana.com/u/Titus_Smith)\
**Post date:** [28 March 2025 11:46 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/1 "2025-03-28T11:46:31Z")

</div>

Hello,

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.

> [@\[Change\] Infrastructure (CDN) rollout and potential new 400 & 403 errors](https://forum.asana.com/t/change-infrastructure-cdn-rollout-and-potential-new-400-403-errors/641280/4):
>
> We previously said https://deprecated-api.asana.com/api/1.0 would be moved on March 1, 2024. It’s still active, but will be disabled in the coming weeks. In the meantime, these TLS ciphers will no longer be supported on https://deprecated-api.asana.com/api/1.0 . AES128-GCM-SHA256 AES128-SHA AES128-SHA256 AES256-GCM-SHA384 AES256-SHA AES256-SHA256 ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES128-SHA256 ECDHE-ECDSA-AES256-SHA ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES128-SHA ECDHE-RSA-AES128-SHA256 ECDHE…

> [@Suddenly Can't access to some apis, like task or make queries](https://forum.asana.com/t/suddenly-cant-access-to-some-apis-like-task-or-make-queries/682039/3):
>
> It is not, the problem was the parameters, “type” was deprecated, Actually I already migrated from payload to url parameters. playload = {“type”: “tag”, “query”: tagName, “count”: 100} ) Thanks anyway for the interesting link to that post.

**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

---

<div class="post-metadata">

**Author:** ![Titus\_Smith](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/titus_smith/32/101553_2.png) [@Titus\_Smith](https://forum.asana.com/u/Titus_Smith)\
**Post date:** [28 March 2025 11:49 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/2 "2025-03-28T11:49:15Z")

</div>

As an addendum, I saw some comments suggesting to avoid GET’s with a body. Our failing requests are all POST’s.

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [28 March 2025 12:23 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/3 "2025-03-28T12:23:45Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Titus\_Smith](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/titus_smith/32/101553_2.png) [@Titus\_Smith](https://forum.asana.com/u/Titus_Smith)\
**Post date:** [28 March 2025 15:17 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/4 "2025-03-28T15:17:02Z")

</div>

I’ve got it on the /duplicate endpoint and /addTask to section endpoint, among others

---

<div class="post-metadata">

**Author:** ![Sameer\_Mehra](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/sameer_mehra/32/278546_2.png) [@Sameer\_Mehra](https://forum.asana.com/u/Sameer_Mehra)\
**Post date:** [28 March 2025 16:55 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/5 "2025-03-28T16:55:06Z")

</div>

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  
\

---

<div class="post-metadata">

**Author:** ![John\_Baldo](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/john_baldo/32/163575_2.png) [@John\_Baldo](https://forum.asana.com/u/John_Baldo)\
**Post date:** [28 March 2025 17:17 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/6 "2025-03-28T17:17:14Z")

</div>

Hi, Thanks for sharing. We are investigating to see what might be causing this.

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [31 March 2025 07:31 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/7 "2025-03-31T07:31:09Z")

</div>

I do notice way more 403 random errors in my logs, and this has been going on for a while…

---

<div class="post-metadata">

**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\
**Post date:** [1 April 2025 17:32 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/9 "2025-04-01T17:32:16Z")

</div>

@Gopesh_Kosala I moved your post to another thread on this issue.

@John_Baldo here is someone else having what looks like the same errors.

---

<div class="post-metadata">

**Author:** ![John\_Vu](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/john_vu/32/97235_2.png) [@John\_Vu](https://forum.asana.com/u/John_Vu)\
**Post date:** [2 April 2025 17:46 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/10 "2025-04-02T17:46:33Z")

</div>

@Gopesh_Kosala, Thank you for bringing this up. I’ve flagged this to our Infra team. They are aware and currently looking into the issue.

---

<div class="post-metadata">

**Author:** ![Gopesh\_Kosala](https://luna1.co/8d76cd.png) [@Gopesh\_Kosala](https://forum.asana.com/u/Gopesh_Kosala)\
**Post date:** [2 April 2025 17:49 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/11 "2025-04-02T17:49:36Z")

</div>

Thanks @John_Vu and @Phil_Seeman

---

<div class="post-metadata">

**Author:** ![John\_Vu](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/john_vu/32/97235_2.png) [@John\_Vu](https://forum.asana.com/u/John_Vu)\
**Post date:** [2 April 2025 21:57 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/12 "2025-04-02T21:57:19Z")

</div>

Hi @Gopesh_Kosala, to help our Infra team investigate are you able to provide us with:

1. `Request ID`
2. `API URI`
3. `Timestamp`

Of your most recent issue.

Our Infra team looked up the information about the issue you posted [here](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/8) 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.

---

<div class="post-metadata">

**Author:** ![Gopesh\_Kosala](https://luna1.co/8d76cd.png) [@Gopesh\_Kosala](https://forum.asana.com/u/Gopesh_Kosala)\
**Post date:** [3 April 2025 08:08 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/13 "2025-04-03T08:08:26Z")

</div>

Hi @John_Vu ,  
Here are the details from the recent request,  
Request ID: dXZBH5CemD7FARBwhH-EZV3ol39s7bLcZPckHgMsqyoCwZmUcggjBg==

API URI: Same as mentioned in the other post (Unable to post the URI here)

Timestamp: 2025-04-03 1:33 PM IST

---

<div class="post-metadata">

**Author:** ![Dedy\_Cds](https://luna1.co/8d76cd.png) [@Dedy\_Cds](https://forum.asana.com/u/Dedy_Cds)\
**Post date:** [3 April 2025 09:40 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/14 "2025-04-03T09:40:31Z")

</div>

Hey, I am also experiencing the same issue since February.  
Got 403 errors and getting more common as well.

The latest request id : CzCH9XsRNXGKZq0JEHIM9tnvYRCdcxEraYmSvfBQXDOTDUunnHb46w==  
Timestamp: 2025-04-01T21:46:00.683939187Z  
Endpoint: PUT /tasks

---

<div class="post-metadata">

**Author:** ![John\_Vu](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/john_vu/32/97235_2.png) [@John\_Vu](https://forum.asana.com/u/John_Vu)\
**Post date:** [3 April 2025 16:53 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/15 "2025-04-03T16:53:26Z")

</div>

Thank you @Gopesh_Kosala and @Dedy_Cds. I’ll pass this info along to our Infra team.

---

<div class="post-metadata">

**Author:** ![Tom\_McCall](https://luna1.co/8d76cd.png) [@Tom\_McCall](https://forum.asana.com/u/Tom_McCall)\
**Post date:** [11 April 2025 16:12 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/16 "2025-04-11T16:12:44Z")

</div>

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?

Thanks,  
Tom

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [14 April 2025 07:26 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/17 "2025-04-14T07:26:15Z")

</div>

This has been going on for weeks now, I hope it gets resolved soon…

---

<div class="post-metadata">

**Author:** ![anon13817504](https://luna1.co/8d76cd.png) [@anon13817504](https://forum.asana.com/u/anon13817504)\
**Post date:** [23 April 2025 22:14 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/18 "2025-04-23T22:14:36Z")

</div>

Hi All,

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).

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [25 April 2025 07:23 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/19 "2025-04-25T07:23:12Z")

</div>

Here are several CloudFront request ID linked to recent failures:

```auto
pUUkb8Hcp5hTjv1iCuKjzJq4AuQHEgMtYLsSdcz9vnXExdqdYVu8gA==
cAuz9eW-GfaDSFrEKs6FOHkFl-UVu9UKH2H4W1CD086hGnaIG2Xf1g==
2XawE1afgUq8VrCPHizKiFWtHfgzLnLzXpBs9y_YuijFOpV9LH5p3g==
-2wp2B7PmFzonTz30Q-JAKYc6tqePmkKnQdY999mfcXZZkHtVCgnBQ==
UzrDC7FTlZ9kDQKqnE-u9c1frnrgapafBeAYLHVI3MBtFXfsFN4aNg==

```

The body is always the same

```auto

<!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.

---

<div class="post-metadata">

**Author:** ![anon13817504](https://luna1.co/8d76cd.png) [@anon13817504](https://forum.asana.com/u/anon13817504)\
**Post date:** [25 April 2025 16:19 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/20 "2025-04-25T16:19:03Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![anon13817504](https://luna1.co/8d76cd.png) [@anon13817504](https://forum.asana.com/u/anon13817504)\
**Post date:** [25 April 2025 21:34 UTC](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486/21 "2025-04-25T21:34:56Z")

</div>

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.

[Next page](https://forum.asana.com/t/cloudfront-api-errors-after-infrastructure-change/1043486.md?page=2)