github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4742] [Bug]: Internal error when trying to sync accounts with GoCardless when restoring from a backup #79443

New Issue
Open
opened 2026-05-19 02:23:37 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-19 02:23:37 -05:00
Owner
Copy Link

Originally created by @Jonas-Sander on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4742

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When restoring a backup it does not seem like the GoCardless Secret Id and Secret Key are restored.
If a user tries to sync the bank accounts after restoring a backup the message "An internal error has occured" appears.

Since there is no indication that the secrets are not restored it is highly confusing for a user to repair the problem.
I was thinking I had to set up a whole new instance and backfill all changes because I could not get it working again and there was no "Repair GoCardless sync" button or something.

To fix this one has to go to "Add an Account", "Set-up GoCardless for bank-sync" and add the secrets there (again). After that syncing works again.

How can we reproduce the issue?

  1. Set up an Actual instance with a bank account that is synced with GoCardless
  2. Create a Backup of that instance ("Export data")
  3. Delete everything; Set up a new instance.
  4. Import the backup into that instance
  5. Click "Sync" on the bank account that should be connected with GoCardless
  6. See "internal error" occuring

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome, Firefox

Operating System

Linux

Originally created by @Jonas-Sander on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4742 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When restoring a backup it does not seem like the GoCardless `Secret Id` and `Secret Key` are restored. If a user tries to sync the bank accounts after restoring a backup the message "An internal error has occured" appears. Since there is no indication that the secrets are not restored it is highly confusing for a user to repair the problem. I was thinking I had to set up a whole new instance and backfill all changes because I could not get it working again and there was no "Repair GoCardless sync" button or something. To fix this one has to go to "Add an Account", "Set-up GoCardless for bank-sync" and add the secrets there (again). After that syncing works again. ### How can we reproduce the issue? 1. Set up an Actual instance with a bank account that is synced with GoCardless 2. Create a Backup of that instance ("Export data") 3. Delete everything; Set up a new instance. 4. Import the backup into that instance 5. Click "Sync" on the bank account that should be connected with GoCardless 6. See "internal error" occuring ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Chrome, Firefox ### Operating System Linux
GiteaMirror added the help wantedbugbank syncgood first issue labels 2026-05-19 02:23:41 -05:00
GiteaMirror commented 2026-05-19 02:23:44 -05:00
Author
Owner
Copy Link

@Jonas-Sander commented on GitHub (Apr 4, 2025):

In my opinion there are several things that should be corrected:

  1. I should be able to export the GoCardless Secrets with my backup (Yes, I know that there might be security risks and I'm 100% certain I want to do this)
  2. There should be a clear error message in the UI when the secrets are missing and the user tries to sync
  3. There should be a dedicated "repair" button in the case that the credentials are missing
  4. There should be a note that says that the secrets are not exported when creating a backup currently
<!-- gh-comment-id:2778495999 --> @Jonas-Sander commented on GitHub (Apr 4, 2025): In my opinion there are several things that should be corrected: 1. I should be able to export the GoCardless Secrets with my backup (Yes, I know that there might be security risks and I'm 100% certain I want to do this) 2. There should be a clear error message in the UI when the secrets are missing and the user tries to sync 3. There should be a dedicated "repair" button in the case that the credentials are missing 4. There should be a note that says that the secrets are not exported when creating a backup currently
GiteaMirror commented 2026-05-19 02:23:45 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 6, 2025):

👋 Thanks for the report! Added some more tags and I'm hoping the community will fix this.

I should be able to export the GoCardless Secrets with my backup

Secrets are write-only. There is and will not be any way to read them directly or export them unless you back up the sync-server database itself.

There should be a clear error message in the UI when the secrets are missing and the user tries to sync
There should be a dedicated "repair" button in the case that the credentials are missing

This makes sense 👍

There should be a note that says that the secrets are not exported when creating a backup currently

It's not just the secrets that are not exported. Other server configuration data will not be exported either (i.e. all the multi-user configuration, etc.). That being said - a message explaining that only the budget data will be saved in the export would be a welcome addition.

<!-- gh-comment-id:2781530737 --> @MatissJanis commented on GitHub (Apr 6, 2025): 👋 Thanks for the report! Added some more tags and I'm hoping the community will fix this. > I should be able to export the GoCardless Secrets with my backup Secrets are write-only. There is and will not be any way to read them directly or export them unless you back up the sync-server database itself. > There should be a clear error message in the UI when the secrets are missing and the user tries to sync > There should be a dedicated "repair" button in the case that the credentials are missing This makes sense 👍 > There should be a note that says that the secrets are not exported when creating a backup currently It's not just the secrets that are not exported. Other server configuration data will not be exported either (i.e. all the multi-user configuration, etc.). That being said - a message explaining that **only the budget data** will be saved in the export would be a welcome addition.
GiteaMirror commented 2026-05-19 02:23:45 -05:00
Author
Owner
Copy Link

@Jonas-Sander commented on GitHub (Apr 6, 2025):

Thanks for your answer :)

Secrets are write-only. There is and will not be any way to read them directly or export them unless you back up the sync-server database itself.

It's not just the secrets that are not exported. Other server configuration data will not be exported either (i.e. all the multi-user configuration, etc.). That being said - a message explaining that only the budget data will be saved in the export would be a welcome addition.

Is there an easy way to back up this other stuff?
Because the export from the settings page seems like the only way right now, correct?

<!-- gh-comment-id:2781618746 --> @Jonas-Sander commented on GitHub (Apr 6, 2025): Thanks for your answer :) > Secrets are write-only. There is and will not be any way to read them directly or export them unless you back up the sync-server database itself. > It's not just the secrets that are not exported. Other server configuration data will not be exported either (i.e. all the multi-user configuration, etc.). That being said - a message explaining that only the budget data will be saved in the export would be a welcome addition. Is there an easy way to back up this other stuff? Because the export from the settings page seems like the only way right now, correct?
GiteaMirror commented 2026-05-19 02:23:46 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 7, 2025):

So there are two parts to Actual: local application and the sync server. You can use the app without a sync server.

The app allows to export the data of your budget. This is all the data the app has access to.

Sync server has some more data and it unlocks a few extra features (multi user auth, bank sync, etc). The server data is stored in the server. It is not exportable via the UI. The sync server also hosts a replica of the "app data" in order to sync across devices.

To back up the sync server data - you can save the "data" folder in the server. How exactly that is done - very much depends on the way how the server is hosted. Feel free to reach out to the community on Discord to help figure this out (we don't do tech support on github).

<!-- gh-comment-id:2784170991 --> @MatissJanis commented on GitHub (Apr 7, 2025): So there are two parts to Actual: local application and the sync server. You can use the app without a sync server. The app allows to export the data of your budget. This is all the data the app has access to. Sync server has some more data and it unlocks a few extra features (multi user auth, bank sync, etc). The server data is stored in the server. It is not exportable via the UI. The sync server also hosts a replica of the "app data" in order to sync across devices. To back up the sync server data - you can save the "data" folder in the server. How exactly that is done - very much depends on the way how the server is hosted. Feel free to reach out to the community on Discord to help figure this out (we don't do tech support on github).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bank sync bug good first issue help wanted
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#79443
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?