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

[GH-ISSUE #7133] [Bug]: SimpleFin Bank Sync fails, Discord not accessible #80422

New Issue
Closed
opened 2026-05-19 04:05:27 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-05-19 04:05:27 -05:00
Owner
Copy Link

Originally created by @networkr0 on GitHub (Mar 5, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7133

What happened?

I was trying to Sync bank accounts when the sync fails and I received multiple Error pop-up windows directing me to http://actualbudget.org/contact, where it offers several links, one to this bug report and several to Discord. I am unable to access Discord to access the discussion of Bank Sync issues and seek answers on how to solve my problem.

Factors:

  • ActualBudget is installed to Proxmox as an LXC container via PVE Helper Scripts.
  • Updates to this instance have been problematic, Notices of new versions, prompting upgrade via apt-get update/upgrade, resulting in various errors during that Debian (APT) upgrade process.
  • Access to instance for daily budgeting and tracking is performed from Mozilla Firefox from MX Linux client.

How can we reproduce the issue?

  1. Open ActualBudget webpage pointing to self hosted instance on my LAN
  2. Highlight "All Accounts", so I can see all transactions from all my accounts.
  3. Hit "Bank Sync", which results in the errors show above.

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @networkr0 on GitHub (Mar 5, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7133 ### What happened? I was trying to Sync bank accounts when the sync fails and I received multiple Error pop-up windows directing me to http://actualbudget.org/contact, where it offers several links, one to this bug report and several to Discord. I am unable to access Discord to access the discussion of Bank Sync issues and seek answers on how to solve my problem. Factors: - ActualBudget is installed to Proxmox as an LXC container via PVE Helper Scripts. - Updates to this instance have been problematic, Notices of new versions, prompting upgrade via apt-get update/upgrade, resulting in various errors during that Debian (APT) upgrade process. - Access to instance for daily budgeting and tracking is performed from Mozilla Firefox from MX Linux client. ### How can we reproduce the issue? 1. Open ActualBudget webpage pointing to self hosted instance on my LAN 2. Highlight "All Accounts", so I can see all transactions from all my accounts. 3. Hit "Bank Sync", which results in the errors show above. ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bugbank syncneeds info labels 2026-05-19 04:05:28 -05:00
GiteaMirror commented 2026-05-19 04:05:31 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Mar 5, 2026):

Are there any errors in the browser or server consoles?

<!-- gh-comment-id:4006423114 --> @matt-fidd commented on GitHub (Mar 5, 2026): Are there any errors in the browser or server consoles?
GiteaMirror commented 2026-05-19 04:05:32 -05:00
Author
Owner
Copy Link

@networkr0 commented on GitHub (Mar 5, 2026):

Are there any errors in the browser or server consoles?

No, the errors are generated from the ActualBudget instance, not the local browser

<!-- gh-comment-id:4006430988 --> @networkr0 commented on GitHub (Mar 5, 2026): > Are there any errors in the browser or server consoles? No, the errors are generated from the ActualBudget instance, not the local browser
GiteaMirror commented 2026-05-19 04:05:32 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Mar 5, 2026):

Are there any errors in the browser or server consoles?

No, the errors are generated from the ActualBudget instance, not the local browser

There have to be some errors somewhere, the console usually spits out the whole lot while giving that error to the UI.

Try opening the console and running the bank sync while it's open

https://appuals.com/open-browser-console/

<!-- gh-comment-id:4006444832 --> @matt-fidd commented on GitHub (Mar 5, 2026): > > Are there any errors in the browser or server consoles? > > No, the errors are generated from the ActualBudget instance, not the local browser There have to be some errors somewhere, the console usually spits out the whole lot while giving that error to the UI. Try opening the console and running the bank sync while it's open https://appuals.com/open-browser-console/
GiteaMirror commented 2026-05-19 04:05:33 -05:00
Author
Owner
Copy Link

@networkr0 commented on GitHub (Mar 5, 2026):

This is what shows in the browser console when attempting bank sync:

HTTPS-Only Mode: Not upgrading insecure request “http://detectportal.firefox.com/canonical.html” because it is exempt.
HTTPS-Only Mode: Not upgrading insecure request “http://detectportal.firefox.com/success.txt?ipv4” because it is exempt.
HTTPS-Only Mode: Not upgrading insecure request “http://detectportal.firefox.com/success.txt?ipv6” because it is exempt.
<!-- gh-comment-id:4006486049 --> @networkr0 commented on GitHub (Mar 5, 2026): This is what shows in the browser console when attempting bank sync: ``` HTTPS-Only Mode: Not upgrading insecure request “http://detectportal.firefox.com/canonical.html” because it is exempt. HTTPS-Only Mode: Not upgrading insecure request “http://detectportal.firefox.com/success.txt?ipv4” because it is exempt. HTTPS-Only Mode: Not upgrading insecure request “http://detectportal.firefox.com/success.txt?ipv6” because it is exempt. ```
GiteaMirror commented 2026-05-19 04:05:34 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 5, 2026):

I think we're not surfacing the correct errors for SimpleFin, but fall back to the default. Which creates confusion.

https://github.com/actualbudget/actual/pull/7125

I think this PR will fix it, but I haven't tested it tbh.. don't have simplefin myself.

<!-- gh-comment-id:4007161539 --> @MatissJanis commented on GitHub (Mar 5, 2026): I think we're not surfacing the correct errors for SimpleFin, but fall back to the default. Which creates confusion. https://github.com/actualbudget/actual/pull/7125 I think this PR will fix it, but I haven't tested it tbh.. don't have simplefin myself.
GiteaMirror commented 2026-05-19 04:05:34 -05:00
Author
Owner
Copy Link

@bennyen commented on GitHub (Mar 6, 2026):

It still occurs for my instance when I use the preview demo: https://deploy-preview-7125.demo.actualbudget.org

None of my accounts have errors right now, but it did emit this error:

Internal error: backend</</syncResponses<@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:2653846
async*backend</<@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:2654097
runHandler@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:82734
backend</exports.initApp/</<@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:3198952
<!-- gh-comment-id:4014800720 --> @bennyen commented on GitHub (Mar 6, 2026): It still occurs for my instance when I use the preview demo: https://deploy-preview-7125.demo.actualbudget.org None of my accounts have errors right now, but it did emit this error: ``` Internal error: backend</</syncResponses<@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:2653846 async*backend</<@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:2654097 runHandler@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:82734 backend</exports.initApp/</<@https://deploy-preview-7125.demo.actualbudget.org/kcab/kcab.worker.aw-XWVX8.js:1:3198952 ```
GiteaMirror commented 2026-05-19 04:05:35 -05:00
Author
Owner
Copy Link

@networkr0 commented on GitHub (Mar 7, 2026):

I think we're not surfacing the correct errors for SimpleFin, but fall back to the default. Which creates confusion.

#7125

I think this PR will fix it, but I haven't tested it tbh.. don't have simplefin myself.

There are no instructions contained in this issue to implement fix

<!-- gh-comment-id:4016711425 --> @networkr0 commented on GitHub (Mar 7, 2026): > I think we're not surfacing the correct errors for SimpleFin, but fall back to the default. Which creates confusion. > > [#7125](https://github.com/actualbudget/actual/pull/7125) > > I think this PR will fix it, but I haven't tested it tbh.. don't have simplefin myself. There are no instructions contained in this issue to implement fix
GiteaMirror commented 2026-05-19 04:05:36 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 7, 2026):

Would you mind checking out this preview build? https://deploy-preview-7152.demo.actualbudget.org/

Another go at solving this problem (warning: I'm still flying totally blind to the actual root cause, but hopefully this works).

<!-- gh-comment-id:4017283775 --> @MatissJanis commented on GitHub (Mar 7, 2026): Would you mind checking out this preview build? https://deploy-preview-7152.demo.actualbudget.org/ Another go at solving this problem (warning: I'm still flying totally blind to the actual root cause, but hopefully this works).
GiteaMirror commented 2026-05-19 04:05:37 -05:00
Author
Owner
Copy Link

@denisborovikov commented on GitHub (Mar 10, 2026):

@MatissJanis I reported about a similar issue with SimpleFin here. I just tried the preview build, and I don't see the issue anymore.

<!-- gh-comment-id:4028026428 --> @denisborovikov commented on GitHub (Mar 10, 2026): @MatissJanis I reported about a similar issue with SimpleFin [here](https://github.com/actualbudget/actual/issues/7114#issuecomment-3993980304). I just tried the preview build, and I don't see the issue anymore.
GiteaMirror commented 2026-05-19 04:05:38 -05:00
Author
Owner
Copy Link

@networkr0 commented on GitHub (Apr 7, 2026):

I seemed to have fixed my existing self-hosted ActualBudget instance by performing an "update" using the 'pve-helper-script' custom update tool rather than a standard apt update/upgrade. After running this "UPDATE" custom command built into the ActualBudget LCT container's console, followed by a reboot, sync errors were eliminated.

<!-- gh-comment-id:4196201414 --> @networkr0 commented on GitHub (Apr 7, 2026): I seemed to have fixed my existing self-hosted ActualBudget instance by performing an "update" using the 'pve-helper-script' custom update tool rather than a standard apt update/upgrade. After running this "UPDATE" custom command built into the ActualBudget LCT container's console, followed by a reboot, sync errors were eliminated.
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 needs info
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#80422
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?