Community
Products
Trello
Questions
Trello API returning HTTP 403 CloudFront errors

Trello API returning HTTP 403 CloudFront errors

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

```
<!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)
```

3 answers

1 accepted

1 vote

Answer accepted

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hey man, you still having this issue? Been the same on our side too!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

Yes, still ongoing. Atlassian support downgraded the fix priority since it's not widespread.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Support got back to me and said the issue should be resolved

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I can confirm that now it works like a snap. Thanks for the info.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Tatsuya Otoshi likes this

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Also having this issue.

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Gene likes this

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

Good day, I have the same problem since yesterday, how to solve it?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

same here. it was working the day before

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Anton Solodkov likes this

yes, everything was working literally yesterday.. how to fix it?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I guess you have to wait until they fix it :(

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

yes, it's kind of bad.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I have logged a ticket as well but not response yet :(

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Anton Solodkov likes this

please let me know when it's fixed.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

https://developer.atlassian.com/changelog/#CHANGE-1459

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Adrian Basson likes this

Thanks for this.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Anton Solodkov likes this

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Same here, when making first call to API I'm continously receiving:

Screenshot from 2024-02-08 12-13-58.png

Request ID: JA_o_ffa3LtEHFBcc17SRfBiazLws_Xjg6XU76bbvLx0Q4ZXLBaIqw==

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Still happening here

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Products

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Get product advice from experts

Join a community group

Advance your career with learning paths

Earn badges and rewards

Connect and share ideas at events

Trello API returning HTTP 403 CloudFront errors

3 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Atlassian Community Events

Ask a question

Start a discussion

Products

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Get product advice from experts

Join a community group

Advance your career with learning paths

Earn badges and rewards

Connect and share ideas at events

Trello API returning HTTP 403 CloudFront errors

3 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Atlassian Community Events