github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-12 03:42:19 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4318] [Bug]: Error when closing file - "Something internally went wrong. You want to restart the app if anything look wrong. Please report this as a new issue on GitHub." #27626

New Issue
Closed
opened 2026-04-18 04:13:41 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-18 04:13:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @ftbboy2115 on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4318

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Hosted on Proxmox CT - Proxmox Helper Scripts

I got the error message, "Something internally went wrong. You want to restart the app if anything look wrong. Please report this as a new issue on GitHub." after updating 25.1.0 -> 25.2.0

I was able to roll-back to 25.1.0, and was able to get things working in the browser again, just not the Desktop app. Seems like any reference to the old file causes issues. (I don't normally use the default storage location set by the app, but since the Desktop app points to that location where old files reside, it seems to contribute to the issue.

How can we reproduce the issue?

After opening a file, close the file. After getting these errors and not being able to close the file, go to File > Manage Files. The page gets stuck on, "Loading global preferences…"

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Windows 11

Originally created by @ftbboy2115 on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4318 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Hosted on Proxmox CT - Proxmox Helper Scripts I got the error message, "Something internally went wrong. You want to restart the app if anything look wrong. Please report this as a new issue on GitHub." after updating 25.1.0 -> 25.2.0 I was able to roll-back to 25.1.0, and was able to get things working in the browser again, just not the Desktop app. Seems like any reference to the old file causes issues. (I don't normally use the default storage location set by the app, but since the Desktop app points to that location where old files reside, it seems to contribute to the issue. ### How can we reproduce the issue? After opening a file, close the file. After getting these errors and not being able to close the file, go to File > Manage Files. The page gets stuck on, "Loading global preferences…" ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Windows 11
GiteaMirror added the bug label 2026-04-18 04:13:41 -05:00
GiteaMirror commented 2026-04-18 04:13:43 -05:00
Author
Owner
Copy Link
Copy Source

@philplaisir commented on GitHub (Feb 6, 2025):

Don't want to create a new issue since this one is similar to the issue I'm having with the desktop app, local File, on Windows 11

The issue/crash I am having since today:

Downloaded a week ago the desktop app from microsoft website. Installed it, was able to import a .qfx file to an account. Was testing and figuring out the app. Deleted this File completely and started fresh with a new local file. Added many transactions to an account manually during the week. Today I tried to import a .qfx file like the other day and the only thing I see is a pop up window appearing for a fraction of a second then closing. Same thing with .csv file. When going to File > Manage Files many pop up messages appear stating:

"Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as new issue on GitHub"

Restarted the app and same bug/crash is appearing. Tried to create new File and same thing happens, can not import anything and everything is frozen once this happened. After uninstalling and reinstalling same thing happens.
The only different thing now compared to earlier in the week is that at start up I receive a pop up meassage telling:

"A new version of Actual is available! Version v25.2.1 of actual was recently released."

<!-- gh-comment-id:2640961604 --> @philplaisir commented on GitHub (Feb 6, 2025): Don't want to create a new issue since this one is similar to the issue I'm having with the desktop app, local File, on Windows 11 The issue/crash I am having since today: Downloaded a week ago the desktop app from microsoft website. Installed it, was able to import a .qfx file to an account. Was testing and figuring out the app. Deleted this File completely and started fresh with a new local file. Added many transactions to an account manually during the week. Today I tried to import a .qfx file like the other day and the only thing I see is a pop up window appearing for a fraction of a second then closing. Same thing with .csv file. When going to File > Manage Files many pop up messages appear stating: "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as new issue on GitHub" Restarted the app and same bug/crash is appearing. Tried to create new File and same thing happens, can not import anything and everything is frozen once this happened. After uninstalling and reinstalling same thing happens. The only different thing now compared to earlier in the week is that at start up I receive a pop up meassage telling: "A new version of Actual is available! Version v25.2.1 of actual was recently released."
GiteaMirror commented 2026-04-18 04:13:43 -05:00
Author
Owner
Copy Link
Copy Source

@youngcw commented on GitHub (Feb 6, 2025):

v25.2.1 is available now. The Microsoft store will probably update tomorrow sometime if thats what you are using. When you can test, please confirm if its been fixed or not.

<!-- gh-comment-id:2641235280 --> @youngcw commented on GitHub (Feb 6, 2025): v25.2.1 is available now. The Microsoft store will probably update tomorrow sometime if thats what you are using. When you can test, please confirm if its been fixed or not.
GiteaMirror commented 2026-04-18 04:13:44 -05:00
Author
Owner
Copy Link
Copy Source

@philplaisir commented on GitHub (Feb 6, 2025):

Noted, I'll try later this weekend if I find time. Will report back when I do, thanks.

<!-- gh-comment-id:2641339520 --> @philplaisir commented on GitHub (Feb 6, 2025): Noted, I'll try later this weekend if I find time. Will report back when I do, thanks.
GiteaMirror commented 2026-04-18 04:13:45 -05:00
Author
Owner
Copy Link
Copy Source

@krelltunez commented on GitHub (Feb 7, 2025):

I'm not seeing an update for the Windows app yet (through the Microsoft Store), but my server was updated to 25.2.1 and I'm still seeing tons of issues. My budgets are basically unusable right now!

<!-- gh-comment-id:2643206549 --> @krelltunez commented on GitHub (Feb 7, 2025): I'm not seeing an update for the Windows app yet (through the Microsoft Store), but my server was updated to 25.2.1 and I'm still seeing tons of issues. My budgets are basically unusable right now!
GiteaMirror commented 2026-04-18 04:13:47 -05:00
Author
Owner
Copy Link
Copy Source

@youngcw commented on GitHub (Feb 7, 2025):

I'm not seeing an update for the Windows app yet (through the Microsoft Store), but my server was updated to 25.2.1 and I'm still seeing tons of issues. My budgets are basically unusable right now

If you are using a server, I recommend not using the Microsoft store app. Using the web app will guarantee that your server and app are the same version.

<!-- gh-comment-id:2643208861 --> @youngcw commented on GitHub (Feb 7, 2025): > I'm not seeing an update for the Windows app yet (through the Microsoft Store), but my server was updated to 25.2.1 and I'm still seeing tons of issues. My budgets are basically unusable right now If you are using a server, I recommend not using the Microsoft store app. Using the web app will guarantee that your server and app are the same version.
GiteaMirror commented 2026-04-18 04:13:49 -05:00
Author
Owner
Copy Link
Copy Source

@krelltunez commented on GitHub (Feb 7, 2025):

I was using that but Windows complains like a Karen when I install it, which gets annoying.

<!-- gh-comment-id:2643279084 --> @krelltunez commented on GitHub (Feb 7, 2025): I was using that but Windows complains like a Karen when I install it, which gets annoying.
GiteaMirror commented 2026-04-18 04:13:50 -05:00
Author
Owner
Copy Link
Copy Source

@ftbboy2115 commented on GitHub (Feb 7, 2025):

I'm not seeing an update for the Windows app yet (through the Microsoft Store), but my server was updated to 25.2.1 and I'm still seeing tons of issues. My budgets are basically unusable right now

If you are using a server, I recommend not using the Microsoft store app. Using the web app will guarantee that your server and app are the same version.

Out of reluctance to jump in with both feet and thus wanting to test that v25.2.1 works as expected, I've got it spun up in a separate proxmox CT, but with a different IP address. (#.#.#.224)
When I point my browser at it, it just hangs at, "Initializing the connection to the local database".
Fortunately, I can still access my main server, which is still on the original ip address (#.#.#.182) and still on v25.1.0

<!-- gh-comment-id:2643757284 --> @ftbboy2115 commented on GitHub (Feb 7, 2025): > > I'm not seeing an update for the Windows app yet (through the Microsoft Store), but my server was updated to 25.2.1 and I'm still seeing tons of issues. My budgets are basically unusable right now > > If you are using a server, I recommend not using the Microsoft store app. Using the web app will guarantee that your server and app are the same version. Out of reluctance to jump in with both feet and thus wanting to test that v25.2.1 works as expected, I've got it spun up in a separate proxmox CT, but with a different IP address. (#.#.#.224) When I point my browser at it, it just hangs at, "Initializing the connection to the local database". Fortunately, I can still access my main server, which is still on the original ip address (#.#.#.182) and still on v25.1.0
GiteaMirror commented 2026-04-18 04:13:50 -05:00
Author
Owner
Copy Link
Copy Source

@MikesGlitch commented on GitHub (Feb 9, 2025):

Fixes in the new release. Let us know if any issues with it. Closing this for now.

<!-- gh-comment-id:2646182880 --> @MikesGlitch commented on GitHub (Feb 9, 2025): Fixes in the new release. Let us know if any issues with it. Closing this for now.
GiteaMirror commented 2026-04-18 04:13:51 -05:00
Author
Owner
Copy Link
Copy Source

@ftbboy2115 commented on GitHub (Feb 9, 2025):

This doesn't look to be resolved. Since I was unable to update the proxmox server, I just exported my files from 25.1.0, spun up a new proxmox CT with 25.2.1 as a fresh install, and imported my files. On the Desktop app, after importing the file, I can see the budget, but when I go to close, I get the error again:

Image

Also, from the browser, it just gets stuck on "Initializing the connection to the local database...".

I closed it after each file import, since that's what the error said to do, and I was eventually able to get the Desktop version to work. Maybe the code is doing some checks/adjustments and throwing the error, but fixing itself? If that's the case, maybe the errors should be delayed until those adjustments are made and subsequently failed thereafter.

Although I was able to get it working, it's certainly not an easy transition, thus I wouldn't consider this issues as resolved.

<!-- gh-comment-id:2646281679 --> @ftbboy2115 commented on GitHub (Feb 9, 2025): This doesn't look to be resolved. Since I was unable to update the proxmox server, I just exported my files from 25.1.0, spun up a new proxmox CT with 25.2.1 as a fresh install, and imported my files. On the Desktop app, after importing the file, I can see the budget, but when I go to close, I get the error again: ![Image](https://github.com/user-attachments/assets/b8e8bcba-ee61-4fad-91a8-ed8a44aaefe2) Also, from the browser, it just gets stuck on "Initializing the connection to the local database...". I closed it after each file import, since that's what the error said to do, and I was eventually able to get the Desktop version to work. Maybe the code is doing some checks/adjustments and throwing the error, but fixing itself? If that's the case, maybe the errors should be delayed until those adjustments are made and subsequently failed thereafter. Although I was able to get it working, it's certainly not an easy transition, thus I wouldn't consider this issues as resolved.
GiteaMirror commented 2026-04-18 04:13:51 -05:00
Author
Owner
Copy Link
Copy Source

@MikesGlitch commented on GitHub (Feb 9, 2025):

@ftbboy2115 The original problem with closing the budget in electron is definitely resolved - it's been verified by a few people already. If it's not working for you the only thing I can think to do is try downloading and installing the version again: https://github.com/actualbudget/actual/releases/tag/v25.2.1.

There may be another issue with importing and then closing but I haven't been able to reproduce it with my budget. If you are still seeing it I'd open another bug just for the Closing budget fails after importing scenario and ideally give us some replication instructions/test data.

The Initializing the connection to the local database hang sounds like a different issue. You could open devtools (ctrl shift i) to see what the error is saying

<!-- gh-comment-id:2646298857 --> @MikesGlitch commented on GitHub (Feb 9, 2025): @ftbboy2115 The original problem with closing the budget in electron is definitely resolved - it's been verified by a few people already. If it's not working for you the only thing I can think to do is try downloading and installing the version again: https://github.com/actualbudget/actual/releases/tag/v25.2.1. There may be another issue with importing and then closing but I haven't been able to reproduce it with my budget. If you are still seeing it I'd open another bug just for the _Closing budget fails after importing_ scenario and ideally give us some replication instructions/test data. The ```Initializing the connection to the local database``` hang sounds like a different issue. You could open devtools (ctrl shift i) to see what the error is saying
GiteaMirror commented 2026-04-18 04:13:52 -05:00
Author
Owner
Copy Link
Copy Source

@philplaisir commented on GitHub (Feb 10, 2025):

Noted, I'll try later this weekend if I find time. Will report back when I do, thanks.

Downloaded v25.2.1 from Microsoft website. Tested for a bit, looks fixed. Thanks

<!-- gh-comment-id:2646750317 --> @philplaisir commented on GitHub (Feb 10, 2025): > Noted, I'll try later this weekend if I find time. Will report back when I do, thanks. Downloaded v25.2.1 from Microsoft website. Tested for a bit, looks fixed. Thanks
GiteaMirror commented 2026-04-18 04:13:52 -05:00
Author
Owner
Copy Link
Copy Source

@lumio commented on GitHub (Apr 18, 2026):

I ran across this issue as I have a very similar problem on iOS with the stock browser (and the PWA).

Basically I migrated from PikaPod, exported my budget and imported it on desktop (in browser) to then use on my phone. I also end up on the "Loading global preferences..." screen.

I'm running ActualBudget now in my own kubernetes k3s cluster behind Tailscale. TLS via let's encrypt, so all of that should be fine I guess. Additionally I set up OIDC with env vars using Pocket ID, so maybe that could also be an issue? I'll try to remove that part and see if it works any better.

// edit: Weirdly enough on desktop it works on any browser. Including Safari

<!-- gh-comment-id:4273299173 --> @lumio commented on GitHub (Apr 18, 2026): I ran across this issue as I have a very similar problem on iOS with the stock browser (and the PWA). Basically I migrated from PikaPod, exported my budget and imported it on desktop (in browser) to then use on my phone. I also end up on the "Loading global preferences..." screen. I'm running ActualBudget now in my own kubernetes k3s cluster behind Tailscale. TLS via let's encrypt, so all of that should be fine I guess. Additionally I set up OIDC with env vars using Pocket ID, so maybe that could also be an issue? I'll try to remove that part and see if it works any better. // edit: Weirdly enough on desktop it works on any browser. Including Safari
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 labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#27626