mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #4803] [Bug]: goCardless 503 error when bank syncing #43704
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#43704
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ThomasHFWright on GitHub (Apr 13, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4803
Verified issue does not already exist?
What happened?
Running v25.4.0 currently but I've had intermittent connection issues for the last couple updates I applied.
When syncing to my banks in Portugal via goCardless I'm getting an "Internal server error"
I saw a couple other goCardless issues but not with a 503 error, so sorry if this is a duplicate.
Checking the logs I can see the data response is:
data: {
summary: "Couldn't update account transactions",
detail: "Couldn't connect to Institution",
status_code: 503,
type: 'ConnectionError'
}
I've checked with my goCardless account and I have no issues retrieving transactions within the web UI. This happens with both Banco ActivoBank as well as Santander.
EDIT: I have just retried on goCardless and got a 503 error response within the web UI. I'll raise a support ticket with goCardless.
I think I've redacted everything needed from the logs
_actualbudget-actual_server-1_logs.txt
How can we reproduce the issue?
Sync a Portuguese bank account with goCardless where goCardless connects to the bank using SIBS
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox, Chrome
Operating System
Windows 11
@ThomasHFWright commented on GitHub (Apr 14, 2025):
Got a response from goCardless:
As this bank's API provider is SIBS, I can inform you that, unfortunately, SIBS have been experiencing technical difficulties over the past two weeks.
Our engineering team is doing everything they can to get SIBS to fix the issue, however, the communication is very slow. We are looking into more ways to contact them as the issue is quite severe for some of our merchants.
For now, there is nothing we can do to avoid these specific 503 errors. We've bumped a few metrics to avoid resulting in errors where possible, however, these errors will keep happening until SIBS are able to determine the root cause of the issue and resolve it.
@MiguelNdeCarvalho commented on GitHub (Apr 15, 2025):
I am experiencing exactly the same issue, I'm trying to connect accounts from ActivoBank and Millennium and none of them are working. Thanks!
@MatissJanis commented on GitHub (Apr 16, 2025):
👋 Howdy! Unfortunately there is nothing we can do for internal GoCardless errors. Feel free to continue speaking with them to get this to resolution.
Closing as there is no action on our end we could take here.
@lazynooblet commented on GitHub (May 29, 2025):
Did anyone get a fix for this? I'm getting the same 503 error for all bank feeds. I raise a case with GoCardless and they tell me they aren't aware of any issues with the bank sync system and it could be my API implementation.