[Bug]: Add account crashes Windows desktop app #2041

New Issue

GiteaMirror · 2026-02-28T20:01:48-06:00

GiteaMirror commented

2026-02-28 20:01:48 -06:00

Originally created by @avandever on GitHub (Apr 13, 2025).

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

When I try to add an account, I get an error, and I need to restart the app to be able to see any data in existing accounts. In case it helps, I do have SimpleFin set up, and quite a few accounts (21). Syncing existing accounts still works. But I can't even successfully add a new local account.

How can we reproduce the issue?

How can we reproduce the issue?
Start Actual 25.4 on Windows.
Click "Add acount"
See error

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Windows 11

Originally created by @avandever on GitHub (Apr 13, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When I try to add an account, I get an error, and I need to restart the app to be able to see any data in existing accounts. In case it helps, I do have SimpleFin set up, and quite a few accounts (21). Syncing existing accounts still works. But I can't even successfully add a new local account. ![Image](https://github.com/user-attachments/assets/1ca476e3-5e56-48fd-bafa-2a6e799bb357) ### How can we reproduce the issue? How can we reproduce the issue? Start Actual 25.4 on Windows. Click "Add acount" See error ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Windows 11

GiteaMirror added the bug label 2026-02-28 20:01:48 -06:00

GiteaMirror closed this issue

2026-02-28 20:01:49 -06:00

GiteaMirror commented

2026-02-28 20:01:49 -06:00

@alecbakholdin commented on GitHub (Apr 20, 2025):

Could you open dev tools and see if there are any logs when you attempt this? Ctrl + shift + I or f12 generally opens those, and I'm interested in the "console" tab

@alecbakholdin commented on GitHub (Apr 20, 2025): Could you open dev tools and see if there are any logs when you attempt this? Ctrl + shift + I or f12 generally opens those, and I'm interested in the "console" tab

GiteaMirror commented

2026-02-28 20:01:49 -06:00

@MikesGlitch commented on GitHub (Apr 20, 2025):

Hey 👋

The dev tools logs would be really helpful here. You can also get to them by clicking the View menu > Toggle Developer Tools

If you open that, then make it error again, then copy and paste the error in the console to this issue we'll be able to help further.

Can you also confirm if this is happening on the web client or is it just the desktop app?

@MikesGlitch commented on GitHub (Apr 20, 2025): Hey 👋 The dev tools logs would be really helpful here. You can also get to them by clicking the View menu > Toggle Developer Tools ![Image](https://github.com/user-attachments/assets/d66e409b-8cb4-418e-aef8-4d9a6a97525d) If you open that, then make it error again, then copy and paste the error in the console to this issue we'll be able to help further. Can you also confirm if this is happening on the web client or is it just the desktop app?

GiteaMirror commented

2026-02-28 20:01:50 -06:00

@mcalligator commented on GitHub (Apr 20, 2025):

I've also been experiencing this issue since updating to the desktop edition of v25.4.0 on Windows 11. Thanks for the pointer on how to get the developer logs on the Electron client; that was helpful. There are two error messages logged when this happens. I don't yet know my way round the code well enough to go digging, but I'm fairly sure this will be useful to those who do.

First Message

Server Log: [Exception] PostError: PostError: <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot POST /pluggyai/status</pre>
</body>
</html>

    at throwIfNot200 (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:9802)
    at post_post (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:10276)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  meta: undefined,
  reason: '<!DOCTYPE html>\n' +
    '<html lang="en">\n' +
    '<head>\n' +
    '<meta charset="utf-8">\n' +
    '<title>Error</title>\n' +
    '</head>\n' +
    '<body>\n' +
    '<pre>Cannot POST /pluggyai/status</pre>\n' +
    '</body>\n' +
    '</html>\n',
  type: 'PostError'
}

Second Message

Server Log: node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

PostError: PostError: <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot POST /pluggyai/status</pre>
</body>
</html>

    at throwIfNot200 (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:9802)
    at post_post (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:10276)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  meta: undefined,
  reason: '<!DOCTYPE html>\n' +
    '<html lang="en">\n' +
    '<head>\n' +
    '<meta charset="utf-8">\n' +
    '<title>Error</title>\n' +
    '</head>\n' +
    '<body>\n' +
    '<pre>Cannot POST /pluggyai/status</pre>\n' +
    '</body>\n' +
    '</html>\n',
  type: 'PostError'
}

Node.js v20.11.1

@mcalligator commented on GitHub (Apr 20, 2025): I've also been experiencing this issue since updating to the desktop edition of v25.4.0 on Windows 11. Thanks for the pointer on how to get the developer logs on the Electron client; that was helpful. There are two error messages logged when this happens. I don't yet know my way round the code well enough to go digging, but I'm fairly sure this will be useful to those who do. ### First Message ``` Server Log: [Exception] PostError: PostError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /pluggyai/status</pre> </body> </html> at throwIfNot200 (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:9802) at post_post (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:10276) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { meta: undefined, reason: '<!DOCTYPE html>\n' + '<html lang="en">\n' + '<head>\n' + '<meta charset="utf-8">\n' + '<title>Error</title>\n' + '</head>\n' + '<body>\n' + '<pre>Cannot POST /pluggyai/status</pre>\n' + '</body>\n' + '</html>\n', type: 'PostError' } ``` ### Second Message ``` Server Log: node:internal/process/promises:289 triggerUncaughtException(err, true /* fromPromise */); ^ PostError: PostError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /pluggyai/status</pre> </body> </html> at throwIfNot200 (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:9802) at post_post (C:\Program Files\WindowsApps\actualbudget.org.ActualBudget_25.4.0.0_x64__6q3amkrs0bv0p\app\resources\app.asar\build\loot-core\lib-dist\electron\bundle.desktop.js:69:10276) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { meta: undefined, reason: '<!DOCTYPE html>\n' + '<html lang="en">\n' + '<head>\n' + '<meta charset="utf-8">\n' + '<title>Error</title>\n' + '</head>\n' + '<body>\n' + '<pre>Cannot POST /pluggyai/status</pre>\n' + '</body>\n' + '</html>\n', type: 'PostError' } Node.js v20.11.1 ```

GiteaMirror commented

2026-02-28 20:01:50 -06:00

@MikesGlitch commented on GitHub (Apr 21, 2025):

@mcalligator I think the error is saying that pluggyai (a bank sync provider) isn't available in your server.

Do you know what version your server is on? It's important that the server and desktop app versions align so you may need to update to 25.4.0 if not already done.

@MikesGlitch commented on GitHub (Apr 21, 2025): @mcalligator I think the error is saying that pluggyai (a bank sync provider) isn't available in your server. Do you know what version your server is on? It's important that the server and desktop app versions align so you may need to update to 25.4.0 if not already done.

GiteaMirror commented

2026-02-28 20:01:50 -06:00

@mcalligator commented on GitHub (Apr 22, 2025):

Good question @MikesGlitch - I set up Actual Server in a Docker container running on my laptop (with a view to migrating it to my home server in due course), but have not upgraded that in concert with the client. I need to work out how to establish the server version, but in the meantime I can confirm it's a good few months behind that of my client. I'll upgrade the server; hopefully that will fix it. I'll report back here after doing so.

@mcalligator commented on GitHub (Apr 22, 2025): Good question @MikesGlitch - I set up Actual Server in a Docker container running on my laptop (with a view to migrating it to my home server in due course), but have not upgraded that in concert with the client. I need to work out how to establish the server version, but in the meantime I can confirm it's a good few months behind that of my client. I'll upgrade the server; hopefully that will fix it. I'll report back here after doing so.

GiteaMirror commented

2026-02-28 20:01:51 -06:00

@avandever commented on GitHub (Apr 30, 2025):

Just got back to home setup, I strongly suspect now that this is due to still running server 24.8.0...which is odd, given I updated the docker image, but I'll work on figuring that out.

@avandever commented on GitHub (Apr 30, 2025): Just got back to home setup, I strongly suspect now that this is due to still running server 24.8.0...which is odd, given I updated the docker image, but I'll work on figuring that out.

GiteaMirror commented

2026-02-28 20:01:51 -06:00

@avandever commented on GitHub (Apr 30, 2025):

Can confirm, I figured out how to update my docker setup to 25.4.0, and now account adding works fine, including from simplefin.

@avandever commented on GitHub (Apr 30, 2025): Can confirm, I figured out how to update my docker setup to 25.4.0, and now account adding works fine, including from simplefin.

GiteaMirror commented

2026-02-28 20:01:51 -06:00

@mcalligator commented on GitHub (May 4, 2025):

I'll upgrade the server; hopefully that will fix it. I'll report back here after doing so.

OK, apologies for the delay in circling back on this one: yes, @MikesGlitch it was indeed the server version; I've now upgraded that, and it's fixed the problem. The reason it took me so long is that when I downloaded the new Docker image, the path for my Actual Server files somehow got overwritten in my config.json , so it was looking in the wrong place when the client tried to connect with a password. Since the default server file doesn't have a password, the client couldn't authenticate, so I couldn't confirm whether the upgrade had solved the issue. Once I figured that out, I could test it out. Thanks for the help!

@mcalligator commented on GitHub (May 4, 2025): > I'll upgrade the server; hopefully that will fix it. I'll report back here after doing so. OK, apologies for the delay in circling back on this one: yes, @MikesGlitch it was indeed the server version; I've now upgraded that, and it's fixed the problem. The reason it took me so long is that when I downloaded the new Docker image, the path for my Actual Server files somehow got overwritten in my `config.json` , so it was looking in the wrong place when the client tried to connect with a password. Since the default server file doesn't have a password, the client couldn't authenticate, so I couldn't confirm whether the upgrade had solved the issue. Once I figured _that_ out, I could test it out. Thanks for the help!