Cloudfront API errors after infrastructure change

[Titus_Smith]

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

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

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

[Titus_Smith]

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

[Bastien_Siebman]

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?

[Titus_Smith]

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

[Sameer_Mehra]

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
\

[John_Baldo]

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

[Bastien_Siebman]

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