Trello API returning HTTP 403 CloudFront errors
Asked by Board Genius:

Trying to access <https://api.trello.com/1/members/me/boardStars>

<br />

\`\`\`  
\<!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"\>  
Bad request.  
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: sb4hE3E_eC-tX-b_7bwFw9XR2y5ZR6oG5AiMkJCyNQoIelvGHdWKCg==  
\</PRE\>  
\<ADDRESS\>  
\</ADDRESS\>  
\</BODY\>\</HTML\> at <https://api.trello.com/1/members/me/boardStars> (HTTP status: 403)  
\`\`\`


Answers:
author: Board Genius
body: Still seeing this (for the last 7 hours) when accessing the API via OAuth tokens. API tokens in the URL don't seem to cause the same issue.

comments: author: Adrian Basson
body: Hey man, you still having this issue? Been the same on our side too!


author: Board Genius
body: Yes, still ongoing. Atlassian support downgraded the fix priority since it's not widespread.


author: Board Genius
body: Support got back to me and said the issue should be resolved


author: Dawid Zdrojewski
body: I can confirm that now it works like a snap. Thanks for the info.


author: megamaz
body: Just started getting this issue today. Is this a server or client error? Is there anything I should do? Since it's a 403 I assumed it was a client error and redid my tokens but that didn't fix it.


author: Board Genius
body: It's a server error. Best thing you can do is reach out to Atlassian support and urge them to take a look.


author: Walid
body: Also having this issue.

EDIT: this was the issue for me <https://developer.atlassian.com/changelog/#CHANGE-1459>


author: tzsebe
body: They just got back to me on the bug, with that same link.

I use Py-Trello, and I can see there's a PR in the works to address this.

So.... does Atlassian think it's acceptable to make backwards-incompatible changes without at least several months of notice? This isn't a good look.

I thought maybe I missed a notice due to not being signed up for some API notice list, but since the Py-Trello maintainers were clearly caught off-guard as well, I'm left to assume they just kind of cowboyed out a breaking change.


author: Entrepositive
body: Oh man.. our creds were being rejected. I think it's also 403 but a slightly different error code. Thought I fixed it last week but it flared up again today... not fun.


author: megamaz
body: Same, the error returned. I tried updating py-trello by doing "py -m pip install --upgrade py-trello" but I'm still getting it, and it says I'm on latest.

python 3.11.0, py-trello 0.19.0.


author: tzsebe
body: I don't think they've gotten around to merging the fix. I figured they wouldn't. Luckily, the change is easy to patch. I pretty much just found where the library is installed (from python console, import trello, and just display trello.__file__), and manually updated the few relevant lines of code.


author: Adrian Basson
body: There is a pull request (think it's still there?) with the fix. It's just because they no longer allow a body in the get and the original py-trello library was passing through an empty body but still considered a body. The fix for it is to update to the pull request that is waiting to go into the main branch.  

<https://github.com/sarumont/py-trello/pull/374>  

As mentioned in their comments there are probably other ways to fix it but this worked for me after Trello updated the get calls.


author: Anton Solodkov
body: Good day, I have the same problem since yesterday, how to solve it?

comments: author: Weiming Chen
body: same here. it was working the day before


author: Anton Solodkov
body: yes, everything was working literally yesterday.. how to fix it?


author: Dawid Zdrojewski
body: I guess you have to wait until they fix it :(


author: tzsebe
body: Looks like it's been like this all night (was broken last night too).

It's scary to think that "an API outage" isn't being picked up by their monitoring and paging their onduty. Or more likely, they don't have appropriate external monitoring that goes across the open internet, and the API is fine within their firewall, so they don't test the path to their API that goes through cloudfront.

Either way... scary, in a "this gives me second thoughts about paying for premium in the future" kind of way.


author: Anton Solodkov
body: yes, it's kind of bad.


author: Adrian Basson
body: I have logged a ticket as well but not response yet :(


author: Anton Solodkov
body: please let me know when it's fixed.


author: Adrian Basson
body: We did two tests with postman. For one of us it worked and for myself it presented that error. So it might be IP specific?


author: tzsebe
body: That's what I thought at first, until I saw that many people have the same issue. It's more likely that someone mistakenly deployed a bogus configuration that might be blocking an entire ISP (but only for the API).


author: Walid
body: <https://developer.atlassian.com/changelog/#CHANGE-1459>


author: Adrian Basson
body: Thanks for this.


author: Adrian Basson
body: We are using the python trello client to get the boards and there is no payload in that get call. So oddly works in postman but not for that library now.


author: tzsebe
body: There's a fix that can be applied for those of us that need it asap, referenced in the py-trello issue: <https://github.com/sarumont/py-trello/issues/373>


author: tzsebe
body: Looks like they've suspended the rollout until March 12. This should hopefully give all users enough time to update and migrate.

Thanks for hearing our voice!


author: Adrian Basson
body: We urgently needed a fix and that pull request you mentioned above - i updated py-trello with that which resolved it so thank you!


author: Anton Solodkov
body: how exactly did you solve the problem? I understood that now it worked as before, but how to solve this problem in the future? i also use py-trello


author: Adrian Basson
body: The older py-trello library is doing a get call that is posting through an empty payload. Trello has stopped the ability to do a get call with any payload in it (even if empty) - that's where the error comes from. As mentioned in the link above this is the fix <https://github.com/sarumont/py-trello/issues/373> waiting to be merged into the main branch. Trello also confirmed this. I basically did a pip install on that tree and then it worked again.  

I assume that the main branch will be updated with this fix at some point.


author: Dawid Zdrojewski
body: Same here, when making first call to API I'm continously receiving:

![Screenshot from 2024-02-08 12-13-58.png](https://community.atlassian.com/t5/image/serverpage/image-id/305204i09A94460F092A831/image-size/large?v=v2&px=999 "Screenshot from 2024-02-08 12-13-58.png")

Request ID: JA_o_ffa3LtEHFBcc17SRfBiazLws_Xjg6XU76bbvLx0Q4ZXLBaIqw==

comments: author: Board Genius
body: Still happening here


Tags: rest-api