github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 12:28:57 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #5346] [Bug]: SimpleFin Sync Not Functioning Properly #51414

New Issue
Closed
opened 2026-04-30 17:54:53 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-30 17:54:53 -05:00
Owner
Copy Link

Originally created by @SplendidAppendix on GitHub (Jul 18, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5346

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Description

I'm currently experiencing significant issues with the SimpleFin sync functionality in my setup. Despite various troubleshooting efforts, I've been unable to establish a stable sync. Whenever I attempt to sync, I encounter repeated failures and a frustrating “SimpleFin dance” where I have to copy and paste my SimpleFin access key multiple times without success.

Environment

  • Setup: LXC container on Proxmox
  • Software Version: 25.7.1

Steps Taken to Troubleshoot

  1. System Checks:

    • Rebooted the system.
    • Adjusted my network settings.
    • Tweaked reverse proxy configurations.

  2. Bank Syncing:

    • Attempted to link accounts via the Bank Sync menu; accounts linked but did not sync properly afterward.

  3. Log Inspection:

    • Checked logs using journalctl and found the following error message indicating a timeout:
Jul 18 13:17:17 actualbudget actual-server[125]: TypeError: fetch failed
Jul 18 13:17:17 actualbudget actual-server[125]:     at node:internal/deps/undici/undici:13510:13
Jul 18 13:17:17 actualbudget actual-server[125]:     at process.processTicksAndRejections (node:internal/process task_queues:105:5)
Jul 18 13:17:17 actualbudget actual-server[125]:     at async getAccounts (file:///usr/lib/node_modules/@actual-app/sync-server/build/src/app-simplefin/app-simplefin.js:315:22)
Jul 18 13:17:17 actualbudget actual-server[125]:     at async getTransactions (file:///usr/lib/node_modules/@actual-app/sync-server/build/src/app-simplefin/app-simplefin.js:282:12)
Jul 18 13:17:17 actualbudget actual-server[125]:     at async file:///usr/lib/node_modules/@actual-app/sync-server/build/src/app-simplefin/app-simplefin.js:75:19 {
Jul 18 13:17:17 actualbudget actual-server[125]:   [cause]: AggregateError [ETIMEDOUT]:
Jul 18 13:17:17 actualbudget actual-server[125]:       at internalConnectMultiple (node:net:1134:18)
Jul 18 13:17:17 actualbudget actual-server[125]:       at internalConnectMultiple (node:net:1210:5)
Jul 18 13:17:17 actualbudget actual-server[125]:       at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
Jul 18 13:17:17 actualbudget actual-server[125]:       at listOnTimeout (node:internal/timers:590:11)
Jul 18 13:17:17 actualbudget actual-server[125]:       at process.processTimers (node:internal/timers:523:7) {
Jul 18 13:17:17 actualbudget actual-server[125]:     code: 'ETIMEDOUT',
Jul 18 13:17:17 actualbudget actual-server[125]:     [errors]: [ [Error], [Error], [Error], [Error] ]
Jul 18 13:17:17 actualbudget actual-server[125]:   }
Jul 18 13:17:17 actualbudget actual-server[125]: }

  1. Console Logging:

    • Tried capturing console logs but found the syncing was hit or miss during my attempts to capture.
    • Whenever I did run it on a blank budget file, I did find it weird that I still got an invalid token console error message.

  2. Network Tests:

    • Ran a script that successfully pulled transaction data from within my container (no network issues observed). Used psybers' script here to test
    • Confirmed internet access from the container by pinging external sites (e.g., google.com).

  3. DNS Configuration:

    • Adjusted DNS settings as another user suggested that issues might relate to DNS after an ISP change.

  4. Linking Attempts:

    • Attempted to link accounts to a blank budget file, but the system fails to accept the token, repeatedly cycling through the token input window.

Current Situation

The sync issue persists over several days, leading me to believe it may not be related to SimpleFin. I've also reverted changes to my reverse proxy that were made to test timeouts, but the syncing problem remains unresolved.

Additional Notes

  • I have attempted to reach out in the Discord, but that sputtered out, causing me to seek help in this forum for troubleshooting.
  • I’d appreciate any guidance or insights into resolving this persistent issue.

Thank you for your assistance!

How can we reproduce the issue?

Install via Proxmox LXC script, log in/open budget, add linked bank account. Error starts.

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @SplendidAppendix on GitHub (Jul 18, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5346 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? ## Description I'm currently experiencing significant issues with the SimpleFin sync functionality in my setup. Despite various troubleshooting efforts, I've been unable to establish a stable sync. Whenever I attempt to sync, I encounter repeated failures and a frustrating “SimpleFin dance” where I have to copy and paste my SimpleFin access key multiple times without success. ## Environment - **Setup:** LXC container on Proxmox - **Software Version:** 25.7.1 ## Steps Taken to Troubleshoot 1. **System Checks:** - Rebooted the system. - Adjusted my network settings. - Tweaked reverse proxy configurations. 2. **Bank Syncing:** - Attempted to link accounts via the Bank Sync menu; accounts linked but did not sync properly afterward. 3. **Log Inspection:** - Checked logs using `journalctl` and found the following error message indicating a timeout: ``` Jul 18 13:17:17 actualbudget actual-server[125]: TypeError: fetch failed Jul 18 13:17:17 actualbudget actual-server[125]: at node:internal/deps/undici/undici:13510:13 Jul 18 13:17:17 actualbudget actual-server[125]: at process.processTicksAndRejections (node:internal/process task_queues:105:5) Jul 18 13:17:17 actualbudget actual-server[125]: at async getAccounts (file:///usr/lib/node_modules/@actual-app/sync-server/build/src/app-simplefin/app-simplefin.js:315:22) Jul 18 13:17:17 actualbudget actual-server[125]: at async getTransactions (file:///usr/lib/node_modules/@actual-app/sync-server/build/src/app-simplefin/app-simplefin.js:282:12) Jul 18 13:17:17 actualbudget actual-server[125]: at async file:///usr/lib/node_modules/@actual-app/sync-server/build/src/app-simplefin/app-simplefin.js:75:19 { Jul 18 13:17:17 actualbudget actual-server[125]: [cause]: AggregateError [ETIMEDOUT]: Jul 18 13:17:17 actualbudget actual-server[125]: at internalConnectMultiple (node:net:1134:18) Jul 18 13:17:17 actualbudget actual-server[125]: at internalConnectMultiple (node:net:1210:5) Jul 18 13:17:17 actualbudget actual-server[125]: at Timeout.internalConnectMultipleTimeout (node:net:1742:5) Jul 18 13:17:17 actualbudget actual-server[125]: at listOnTimeout (node:internal/timers:590:11) Jul 18 13:17:17 actualbudget actual-server[125]: at process.processTimers (node:internal/timers:523:7) { Jul 18 13:17:17 actualbudget actual-server[125]: code: 'ETIMEDOUT', Jul 18 13:17:17 actualbudget actual-server[125]: [errors]: [ [Error], [Error], [Error], [Error] ] Jul 18 13:17:17 actualbudget actual-server[125]: } Jul 18 13:17:17 actualbudget actual-server[125]: } ``` 4. **Console Logging:** - Tried capturing console logs but found the syncing was hit or miss during my attempts to capture. - Whenever I did run it on a blank budget file, I did find it weird that I still got an invalid token console error message. 5. **Network Tests:** - Ran a script that successfully pulled transaction data from within my container (no network issues observed). Used psybers' script [here](https://gist.github.com/psybers/60e7332f93dc59f3ac5f636827921e17) to test - Confirmed internet access from the container by pinging external sites (e.g., google.com). 6. **DNS Configuration:** - Adjusted DNS settings as another user suggested that issues might relate to DNS after an ISP change. 7. **Linking Attempts:** - Attempted to link accounts to a blank budget file, but the system fails to accept the token, repeatedly cycling through the token input window. ## Current Situation The sync issue persists over several days, leading me to believe it may not be related to SimpleFin. I've also reverted changes to my reverse proxy that were made to test timeouts, but the syncing problem remains unresolved. ## Additional Notes - I have attempted to reach out in the Discord, but that sputtered out, causing me to seek help in this forum for troubleshooting. - I’d appreciate any guidance or insights into resolving this persistent issue. Thank you for your assistance! ### How can we reproduce the issue? Install via Proxmox LXC script, log in/open budget, add linked bank account. Error starts. ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-04-30 17:54:53 -05:00
GiteaMirror commented 2026-04-30 17:54:56 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jul 20, 2025):

👋 Hey! Bank sync support is provided through our Discord (https://discord.gg/8JfAXSgfRf). Please feel free to join there and open a thread in #support and someone will be along to help. I'll close this off, but please link through to it in your Discord thread as there is a lot of very thorough information in here that will help to work out what the problem is.

<!-- gh-comment-id:3094611864 --> @matt-fidd commented on GitHub (Jul 20, 2025): 👋 Hey! Bank sync support is provided through our Discord (https://discord.gg/8JfAXSgfRf). Please feel free to join there and open a thread in `#support` and someone will be along to help. I'll close this off, but please link through to it in your Discord thread as there is a lot of very thorough information in here that will help to work out what the problem is.
GiteaMirror commented 2026-04-30 17:54:56 -05:00
Author
Owner
Copy Link

@SplendidAppendix commented on GitHub (Jul 21, 2025):

@matt-fidd Thanks for the follow-up! I had already created a thread, and hadn't gotten anywhere. That's why I opened this issue. Here's the link: https://discord.com/channels/937901803608096828/1390386695530090617

<!-- gh-comment-id:3097880276 --> @SplendidAppendix commented on GitHub (Jul 21, 2025): @matt-fidd Thanks for the follow-up! I had already created a thread, and hadn't gotten anywhere. That's why I opened this issue. Here's the link: https://discord.com/channels/937901803608096828/1390386695530090617
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#51414
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?