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 #7422] [Bug]: Claiming of SimpleFIN token fails #52199

New Issue
Open
opened 2026-04-30 20:24:57 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 20:24:57 -05:00
Owner
Copy Link

Originally created by @jbhanks on GitHub (Apr 8, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7422

What happened?

Title: [Bug]: SimpleFIN setup token not being claimed — "Invalid access key" on every attempt

What happened?

I was trying to link a North American bank account using SimpleFIN on a self-hosted instance of actual-server running as a rootless Podman container.

I generated a setup token from beta-bridge.simplefin.org, pasted it into the "Set up SimpleFIN" token field, and clicked "Save and continue". The server logged POST 200 /secret, indicating the token was stored. Interestingly, clicking "Link bank account with SimpleFIN" immediately produced the following in the server logs, without making any outbound request to SimpleFIN:

Apr 08 05:10:38 byblos actualbudget[236599]: Invalid SimpleFIN access key
Apr 08 05:10:38 byblos actualbudget[236599]: Error: Invalid access key
Apr 08 05:10:38 byblos actualbudget[236599]:     at parseAccessKey (file:///app/src/app-simplefin/app-simplefin.js:247:15)
Apr 08 05:10:38 byblos actualbudget[236599]:     at getAccounts (file:///app/src/app-simplefin/app-simplefin.js:292:18)
Apr 08 05:10:38 byblos actualbudget[236599]:     at file:///app/src/app-simplefin/app-simplefin.js:43:32
Apr 08 05:10:38 byblos actualbudget[236599]:     at file:///app/src/app-gocardless/util/handle-error.js:3:9
Apr 08 05:10:38 byblos actualbudget[236599]:     at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)
Apr 08 05:10:38 byblos actualbudget[236599]:     at next (/app/node_modules/router/lib/route.js:157:13)
Apr 08 05:10:38 byblos actualbudget[236599]:     at Route.dispatch (/app/node_modules/router/lib/route.js:117:3)
Apr 08 05:10:38 byblos actualbudget[236599]:     at handle (/app/node_modules/router/index.js:435:11)
Apr 08 05:10:38 byblos actualbudget[236599]:     at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)
Apr 08 05:10:38 byblos actualbudget[236599]:     at /app/node_modules/router/index.js:295:15

The SimpleFIN website continued to show the app connection as "Unclaimed". No accounts were displayed in the UI. The browser console showed:

Error: There was an error communicating with SimpleFIN.
    at m (CreateAccountModal.tsx:89:19)

I confirmed outbound HTTPS connectivity from inside the container to beta-bridge.simplefin.org was working. I also confirmed that manually claiming the same setup token via curl from the host and querying https://beta-bridge.simplefin.org/simplefin/accounts with the resulting credentials returned valid account data with no errors.

I then made the following change to getAccessKey() in /app/src/app-simplefin/app-simplefin.js:

Before:

return new Promise((resolve, reject) => {
    const req = https.request(new URL(token), options, res => {
        res.on('data', d => {
            resolve(d.toString());
        });
    });
    req.on('error', e => { reject(e); });
    req.end();
});

After:

return new Promise((resolve, reject) => {
    const req = https.request(new URL(token), options, res => {
        let data = '';
        res.on('data', d => { data += d.toString(); });
        res.on('end', () => { resolve(data); });
    });
    req.on('error', e => { reject(e); });
    req.end();
});

After restarting the server and entering a fresh setup token, the token was successfully claimed, the SimpleFIN website showed the connection as "Active", and the UI displayed the accounts available for linking.

How can we reproduce the issue?

  1. Run docker.io/actualbudget/actual-server@sha256:5025407e0acdaca972101b1d46ee33fdfee45cf9f2979f0a61104a99d15914fb self-hosted (tested with rootless Podman on Alma Linux, systemd user service)
  2. Navigate to Add Account → "Link bank account with SimpleFIN"
  3. Generate a new Setup Token from beta-bridge.simplefin.org (My Account → New app connection)
  4. Paste the base64 setup token into the token field and click "Save and continue"
  5. Click "Link bank account with SimpleFIN" again without entering anything new
  6. Observe: server logs show Invalid SimpleFIN access key immediately; the SimpleFIN website still shows the connection as "Unclaimed"; no accounts are displayed

Expected: The setup token is claimed and accounts are displayed for linking.

Actual: The error above is thrown every time the "Add bank with SimpleFin" tab is displayed. When the token is actually submitted, it gets added to the database (overwriting any there previously) and nothing else. The token is never claimed.

Environment:

  • Actual Server: docker.io/actualbudget/actual-server:latest (pulled April 2026)
-> # sudo -iu actualbudget podman inspect actualbudget --format '{{.Image}}'
5025407e0acdaca972101b1d46ee33fdfee45cf9f2979f0a61104a99d15914fb

Note: I did use an LLM to generate this report based on the troubleshooting chat where we found the fix, but I checked it over to make sure that it accurately described what I did.

How can we reproduce the issue?

  1. Run docker.io/actualbudget/actual-server@sha256:5025407e0acdaca972101b1d46ee33fdfee45cf9f2979f0a61104a99d15914fb self-hosted (tested with rootless Podman on Alma Linux, systemd user service)
  2. Navigate to Add Account → "Link bank account with SimpleFIN"
  3. Generate a new Setup Token from beta-bridge.simplefin.org (My Account → New app connection)
  4. Paste the base64 setup token into the token field and click "Save and continue"
  5. Click "Link bank account with SimpleFIN" again without entering anything new
  6. Observe: server logs show Invalid SimpleFIN access key immediately; the SimpleFIN website still shows the connection as "Unclaimed"; no accounts are displayed

Expected: The setup token is claimed and accounts are displayed for linking.

Actual: The error above is thrown every time the "Add bank with SimpleFin" tab is displayed. When the token is actually submitted, it gets added to the database (overwriting any there previously) and nothing else. The token is never claimed.

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @jbhanks on GitHub (Apr 8, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7422 ### What happened? --- **Title:** `[Bug]: SimpleFIN setup token not being claimed — "Invalid access key" on every attempt` --- **What happened?** I was trying to link a North American bank account using SimpleFIN on a self-hosted instance of `actual-server` running as a rootless Podman container. I generated a setup token from beta-bridge.simplefin.org, pasted it into the "Set up SimpleFIN" token field, and clicked "Save and continue". The server logged `POST 200 /secret`, indicating the token was stored. Interestingly, clicking "Link bank account with SimpleFIN" immediately produced the following in the server logs, without making any outbound request to SimpleFIN: ``` Apr 08 05:10:38 byblos actualbudget[236599]: Invalid SimpleFIN access key Apr 08 05:10:38 byblos actualbudget[236599]: Error: Invalid access key Apr 08 05:10:38 byblos actualbudget[236599]: at parseAccessKey (file:///app/src/app-simplefin/app-simplefin.js:247:15) Apr 08 05:10:38 byblos actualbudget[236599]: at getAccounts (file:///app/src/app-simplefin/app-simplefin.js:292:18) Apr 08 05:10:38 byblos actualbudget[236599]: at file:///app/src/app-simplefin/app-simplefin.js:43:32 Apr 08 05:10:38 byblos actualbudget[236599]: at file:///app/src/app-gocardless/util/handle-error.js:3:9 Apr 08 05:10:38 byblos actualbudget[236599]: at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17) Apr 08 05:10:38 byblos actualbudget[236599]: at next (/app/node_modules/router/lib/route.js:157:13) Apr 08 05:10:38 byblos actualbudget[236599]: at Route.dispatch (/app/node_modules/router/lib/route.js:117:3) Apr 08 05:10:38 byblos actualbudget[236599]: at handle (/app/node_modules/router/index.js:435:11) Apr 08 05:10:38 byblos actualbudget[236599]: at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17) Apr 08 05:10:38 byblos actualbudget[236599]: at /app/node_modules/router/index.js:295:15 ``` The SimpleFIN website continued to show the app connection as "Unclaimed". No accounts were displayed in the UI. The browser console showed: ``` Error: There was an error communicating with SimpleFIN. at m (CreateAccountModal.tsx:89:19) ``` I confirmed outbound HTTPS connectivity from inside the container to `beta-bridge.simplefin.org` was working. I also confirmed that manually claiming the same setup token via `curl` from the host and querying `https://beta-bridge.simplefin.org/simplefin/accounts` with the resulting credentials returned valid account data with no errors. I then made the following change to `getAccessKey()` in `/app/src/app-simplefin/app-simplefin.js`: **Before:** ```javascript return new Promise((resolve, reject) => { const req = https.request(new URL(token), options, res => { res.on('data', d => { resolve(d.toString()); }); }); req.on('error', e => { reject(e); }); req.end(); }); ``` **After:** ```javascript return new Promise((resolve, reject) => { const req = https.request(new URL(token), options, res => { let data = ''; res.on('data', d => { data += d.toString(); }); res.on('end', () => { resolve(data); }); }); req.on('error', e => { reject(e); }); req.end(); }); ``` After restarting the server and entering a fresh setup token, the token was successfully claimed, the SimpleFIN website showed the connection as "Active", and the UI displayed the accounts available for linking. --- **How can we reproduce the issue?** 1. Run `docker.io/actualbudget/actual-server@sha256:5025407e0acdaca972101b1d46ee33fdfee45cf9f2979f0a61104a99d15914fb` self-hosted (tested with rootless Podman on Alma Linux, systemd user service) 2. Navigate to Add Account → "Link bank account with SimpleFIN" 3. Generate a new Setup Token from beta-bridge.simplefin.org (My Account → New app connection) 4. Paste the base64 setup token into the token field and click "Save and continue" 5. Click "Link bank account with SimpleFIN" again without entering anything new 6. Observe: server logs show `Invalid SimpleFIN access key` immediately; the SimpleFIN website still shows the connection as "Unclaimed"; no accounts are displayed **Expected:** The setup token is claimed and accounts are displayed for linking. **Actual:** The error above is thrown every time the "Add bank with SimpleFin" tab is displayed. When the token is actually submitted, it gets added to the database (overwriting any there previously) and nothing else. The token is never claimed. --- **Environment:** - Actual Server: `docker.io/actualbudget/actual-server:latest` (pulled April 2026) ``` -> # sudo -iu actualbudget podman inspect actualbudget --format '{{.Image}}' 5025407e0acdaca972101b1d46ee33fdfee45cf9f2979f0a61104a99d15914fb ``` - Hosting: Self-hosted, rootless Podman on AlmaLinux 10.1 (systemd user service, machinectl) - Related issues: #6329, #4295, #5346 Note: I did use an LLM to generate this report based on the troubleshooting chat where we found the fix, but I checked it over to make sure that it accurately described what I did. ### How can we reproduce the issue? 1. Run `docker.io/actualbudget/actual-server@sha256:5025407e0acdaca972101b1d46ee33fdfee45cf9f2979f0a61104a99d15914fb` self-hosted (tested with rootless Podman on Alma Linux, systemd user service) 2. Navigate to Add Account → "Link bank account with SimpleFIN" 3. Generate a new Setup Token from beta-bridge.simplefin.org (My Account → New app connection) 4. Paste the base64 setup token into the token field and click "Save and continue" 5. Click "Link bank account with SimpleFIN" again without entering anything new 6. Observe: server logs show `Invalid SimpleFIN access key` immediately; the SimpleFIN website still shows the connection as "Unclaimed"; no accounts are displayed **Expected:** The setup token is claimed and accounts are displayed for linking. **Actual:** The error above is thrown every time the "Add bank with SimpleFin" tab is displayed. When the token is actually submitted, it gets added to the database (overwriting any there previously) and nothing else. The token is never claimed. ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the bank syncbug labels 2026-04-30 20:24:57 -05:00
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
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#52199
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?