I'm trying to use the github power up with trello but consistently get this error when I try to link my github account. All of my team also get this issue and it's only recently started happening, we were able to use this Power Up no problems a few weeks ago.
1) I select "Authorize Account"
2) I click on "Link Your Github Account"
3) Then a new window pops up and I see this:
FYI:
I'm using Chrome version:
And I've checked the following browser setting: I have enabled local storage as per the steps here: https://help.trello.com/article/1093-enabling-localstorage.
I don't think we have changed anything recently to have this stop working. Any help is much appreciated.
P.S. I also saw issue https://community.atlassian.com/t5/Trello-questions/Some-team-members-consistently-get-quot-400-Bad-Request-quot-and/qaq-p/1462857?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic#U1464141 which looks similar, but raised by own ticket so I didn't hijack that thread.
Thx in advance, let me know if you need any more information from me!
Hi Colin,
Thanks for reporting this problem. We've had similar reports before and are working hard to figure out the problem.
If you've contacted support, they maybe have asked you to try things like clearing your browser cache, or removing personal settings on the Power-Up and re-authing.
If none of those worked, could you try clearing your localstorage for the "github.trello.services" domain? I've attached a screenshot of where you can find that on Chrome (should be similar for other browsers though).
Also, we are trying to collect as much information about these errors as possible, and we rely on users like you who report them.
When you do encounter these errors, could you try having the network tab open when they happen? Filter down to only ones related to github. Failed requests will have red names. If you could, take a screenshot of the "Headers" and "Preview" tabs of the failed requests.
And finally, any console logs relating to the failures would be appreciated too.
Thanks,
Jireh
Hi,
Thx for responding... my replies inline...
If you've contacted support, they maybe have asked you to try things like clearing your browser cache, or removing personal settings on the Power-Up and re-authing.
I have tried the above and it does not seem to fix it.
If none of those worked, could you try clearing your localstorage for the "github.trello.services" domain? I've attached a screenshot of where you can find that on Chrome (should be similar for other browsers though).
I have tried the above and it does not seem to fix it.
Also, we are trying to collect as much information about these errors as possible, and we rely on users like you who report them.
When you do encounter these errors, could you try having the network tab open when they happen? Filter down to only ones related to github. Failed requests will have red names. If you could, take a screenshot of the "Headers" and "Preview" tabs of the failed requests.
Here is the screenshots you wanted:
And finally, any console logs relating to the failures would be appreciated too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Colin,
Thanks for those screenshots. While I am still investigating the issue, I do have a theory.
It's possible to receive a 400 error from a server if the cookies in the request header are too large. And judging from the screenshot you provided, it's possible that this is happening.
Could you try deleting all cookies on your browser from the "github.trello.services" domain, then trying to re-auth Github again? If you're on Chrome, you can do that by going to "chrome://settings/cookies/detail?site=github.trello.services" and pressing "Remove All".
And if that doesn't work, you can try removing all cookies from all domains on your browser, then trying to auth again.
Thanks again,
Jireh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.