-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: GoCardless API responds with 401s #1904
Comments
👋 Thanks for the investigation. Have you reached out to Gocardless/Nordigen about this? Judging from all the information you've provided (and also other folks also reporting Gocardless broken) - I think the issue is on their end. |
Hi @MatissJanis I tried to call It seems like everything works fine with the API itself. |
I just spot-checked v23.10.0, v23.11.0 and Given that the same releases were working completely fine just a couple of days ago - I find it very hard to believe this to be an issue in Actual. So my recommendation here is to reach out to GoCardless. |
Mhh. Yes. That sounds definitely like a Nordigen Issue. I can reach out to them. |
@MatissJanis I have heard back from them and it seems to be no issue with the
which initially yielded the same results as my I see that I did add log lines in I am not sure why the HTTP response say that authorisation headers are missing 🤔. Not sure how to proceed here. I am pasting the support's response for reference:
According to the logs, actual-server generates new access tokens all the time. I don't think expiration is an issue here. |
I love how in-sync we are :) I looked more into it and it is in fact an issue on our end. Though I find it strange how I was able to reproduce it on older Actual releases.. where it should not have been reproducible... Anyways, the fix: actualbudget/actual-server#278 |
Verified issue does not already exist?
What happened?
I have used Nordigen / GoCardless for a while now and it worked smoothly.
This morning it stopped working. Steps I've done so far:
The error I see in the UI:
The UI to set secrets:
What error did you receive?
logs from my fly.io instance
Where are you hosting Actual?
Fly.io
What browsers are you seeing the problem on?
Chrome, Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered: