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

[Bug]: We had problems syncing your changes. Please report this as a bug by #2249

New Issue
Closed
opened 2026-02-28 20:07:54 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-02-28 20:07:54 -06:00
Owner
Copy Link
Copy Source

Originally created by @Margatos19 on GitHub (Jul 3, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Bug Report: Sync Error in Actual Budget App on Google Cloud

Summary:
I’m experiencing a persistent sync error when using the Actual Budget app hosted on a Google Cloud VM. The error message displayed is:

"We had problems syncing your changes. Please report this as a bug by..."

Steps to Reproduce:

Launch the Actual Budget app (self-hosted on a VM in Google Cloud).

Make any change (e.g., update a transaction, budget, or account).

Wait a few seconds — the error appears without further details.

Expected Behavior:
Changes should sync without errors.

Observed Behavior:
Syncing fails, and the app displays the above error message. There’s no additional information or logs provided in the UI.

What I’ve Tried:

Reinstalling the app completely.

Clearing browser cache and cookies.

Restarting the VM.

Re-deploying from a clean backup.

The error still occurs.

Environment:

Hosting: Google Cloud VM

Browser: (e.g., Chrome Version 137)

App Version: (please include the version of Actual Budget you’re using if known)

How can we reproduce the issue?

How can we reproduce the issue?

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @Margatos19 on GitHub (Jul 3, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Bug Report: Sync Error in Actual Budget App on Google Cloud Summary: I’m experiencing a persistent sync error when using the Actual Budget app hosted on a Google Cloud VM. The error message displayed is: "We had problems syncing your changes. Please report this as a bug by..." Steps to Reproduce: Launch the Actual Budget app (self-hosted on a VM in Google Cloud). Make any change (e.g., update a transaction, budget, or account). Wait a few seconds — the error appears without further details. Expected Behavior: Changes should sync without errors. Observed Behavior: Syncing fails, and the app displays the above error message. There’s no additional information or logs provided in the UI. What I’ve Tried: Reinstalling the app completely. Clearing browser cache and cookies. Restarting the VM. Re-deploying from a clean backup. The error still occurs. Environment: Hosting: Google Cloud VM Browser: (e.g., Chrome Version 137) App Version: (please include the version of Actual Budget you’re using if known) ### How can we reproduce the issue? How can we reproduce the issue? ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bug label 2026-02-28 20:07:54 -06:00
GiteaMirror commented 2026-02-28 20:07:54 -06:00
Author
Owner
Copy Link
Copy Source

@youngcw commented on GitHub (Jul 3, 2025):

Are you using the desktop app or a web browser? Does it say you are connected to your server in the top right?

What does the browser console say when that error pops up?

@youngcw commented on GitHub (Jul 3, 2025): Are you using the desktop app or a web browser? Does it say you are connected to your server in the top right? What does the browser console say when that error pops up?
GiteaMirror commented 2026-02-28 20:07:55 -06:00
Author
Owner
Copy Link
Copy Source

@Margatos19 commented on GitHub (Jul 4, 2025):

It happens on all devices. I’m using Chrome, but I also tried with the desktop app and Edge. The same thing happens on my phone. The server is online, but syncing doesn’t work. I'm copying the error from the console and the Network tab.

Image Image Image
@Margatos19 commented on GitHub (Jul 4, 2025): It happens on all devices. I’m using Chrome, but I also tried with the desktop app and Edge. The same thing happens on my phone. The server is online, but syncing doesn’t work. I'm copying the error from the console and the Network tab. <img width="1442" height="846" alt="Image" src="https://github.com/user-attachments/assets/d41e31de-bcfa-45d7-bd30-deb030e925eb" /> <img width="1910" height="857" alt="Image" src="https://github.com/user-attachments/assets/911bcc85-d06b-4bc3-b567-7682fce6399e" /> <img width="1901" height="846" alt="Image" src="https://github.com/user-attachments/assets/c93ad48f-7eea-4fc8-bcaf-0c398daf7b1a" />
GiteaMirror commented 2026-02-28 20:07:55 -06:00
Author
Owner
Copy Link
Copy Source

@JustAPhrog commented on GitHub (Jul 7, 2025):

I've had same error. I've logged in to mashine using ssh and docker logs shows me this:

qliteError: database or disk is full
    at WrappedDatabase.mutate (file:///app/src/db.js:34:27)
    at file:///app/src/sync-simple.js:23:33
    at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
    at WrappedDatabase.transaction (file:///app/src/db.js:41:39)
    at addMessages (file:///app/src/sync-simple.js:19:8)
    at Module.sync (file:///app/src/sync-simple.js:56:18)
    at file:///app/src/app-sync.js:76:46
    at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)
    at next (/app/node_modules/router/lib/route.js:157:13)
    at Route.dispatch (/app/node_modules/router/lib/route.js:117:3)
Error writing file Error: ENOSPC: no space left on device, write
    at async write (node:internal/fs/promises:742:8)
    at async writeFileHandle (node:internal/fs/promises:499:7)
    at async file:///app/src/app-sync.js:173:9 {
  errno: -28,
  code: 'ENOSPC',
  syscall: 'write'
}
@JustAPhrog commented on GitHub (Jul 7, 2025): I've had same error. I've logged in to mashine using ssh and `docker logs` shows me this: ``` qliteError: database or disk is full at WrappedDatabase.mutate (file:///app/src/db.js:34:27) at file:///app/src/sync-simple.js:23:33 at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24) at WrappedDatabase.transaction (file:///app/src/db.js:41:39) at addMessages (file:///app/src/sync-simple.js:19:8) at Module.sync (file:///app/src/sync-simple.js:56:18) at file:///app/src/app-sync.js:76:46 at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17) at next (/app/node_modules/router/lib/route.js:157:13) at Route.dispatch (/app/node_modules/router/lib/route.js:117:3) Error writing file Error: ENOSPC: no space left on device, write at async write (node:internal/fs/promises:742:8) at async writeFileHandle (node:internal/fs/promises:499:7) at async file:///app/src/app-sync.js:173:9 { errno: -28, code: 'ENOSPC', syscall: 'write' } ```
GiteaMirror commented 2026-02-28 20:07:55 -06:00
Author
Owner
Copy Link
Copy Source

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

I've had same error. I've logged in to mashine using ssh and docker logs shows me this:

qliteError: database or disk is full
    at WrappedDatabase.mutate (file:///app/src/db.js:34:27)
    at file:///app/src/sync-simple.js:23:33
    at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
    at WrappedDatabase.transaction (file:///app/src/db.js:41:39)
    at addMessages (file:///app/src/sync-simple.js:19:8)
    at Module.sync (file:///app/src/sync-simple.js:56:18)
    at file:///app/src/app-sync.js:76:46
    at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)
    at next (/app/node_modules/router/lib/route.js:157:13)
    at Route.dispatch (/app/node_modules/router/lib/route.js:117:3)
Error writing file Error: ENOSPC: no space left on device, write
    at async write (node:internal/fs/promises:742:8)
    at async writeFileHandle (node:internal/fs/promises:499:7)
    at async file:///app/src/app-sync.js:173:9 {
  errno: -28,
  code: 'ENOSPC',
  syscall: 'write'
}

That seems reasonably descriptive. It looks like you've run out of storage space on your server.

@matt-fidd commented on GitHub (Jul 7, 2025): > I've had same error. I've logged in to mashine using ssh and `docker logs` shows me this: > > ``` > qliteError: database or disk is full > at WrappedDatabase.mutate (file:///app/src/db.js:34:27) > at file:///app/src/sync-simple.js:23:33 > at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24) > at WrappedDatabase.transaction (file:///app/src/db.js:41:39) > at addMessages (file:///app/src/sync-simple.js:19:8) > at Module.sync (file:///app/src/sync-simple.js:56:18) > at file:///app/src/app-sync.js:76:46 > at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17) > at next (/app/node_modules/router/lib/route.js:157:13) > at Route.dispatch (/app/node_modules/router/lib/route.js:117:3) > Error writing file Error: ENOSPC: no space left on device, write > at async write (node:internal/fs/promises:742:8) > at async writeFileHandle (node:internal/fs/promises:499:7) > at async file:///app/src/app-sync.js:173:9 { > errno: -28, > code: 'ENOSPC', > syscall: 'write' > } > ``` That seems reasonably descriptive. It looks like you've run out of storage space on your server.
GiteaMirror commented 2026-02-28 20:07:55 -06:00
Author
Owner
Copy Link
Copy Source

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

It happens on all devices. I’m using Chrome, but I also tried with the desktop app and Edge. The same thing happens on my phone. The server is online, but syncing doesn’t work. I'm copying the error from the console and the Network tab.

Image Image Image

Do you have access to the server logs? It looks like an error on that side rather than the browser.

@matt-fidd commented on GitHub (Jul 7, 2025): > It happens on all devices. I’m using Chrome, but I also tried with the desktop app and Edge. The same thing happens on my phone. The server is online, but syncing doesn’t work. I'm copying the error from the console and the Network tab. > > <img alt="Image" width="1442" height="846" src="https://private-user-images.githubusercontent.com/102476950/462515862-d41e31de-bcfa-45d7-bd30-deb030e925eb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTE5MDQyMDQsIm5iZiI6MTc1MTkwMzkwNCwicGF0aCI6Ii8xMDI0NzY5NTAvNDYyNTE1ODYyLWQ0MWUzMWRlLWJjZmEtNDVkNy1iZDMwLWRlYjAzMGU5MjVlYi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwNzA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDcwN1QxNTU4MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0xNzUxNDIxOGE2YzMyNjBhYjczMDc1MWIwM2M2YWQwNmM3MTViYTAzNmY4NTJiNTE3OWY0YThiZWI4MTcyMDdmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.7BRBVuYPwmakrziYyd1CkXl7jBs7bs2PGj02VdSacv8"> <img alt="Image" width="1910" height="857" src="https://private-user-images.githubusercontent.com/102476950/462515863-911bcc85-d06b-4bc3-b567-7682fce6399e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTE5MDQyMDQsIm5iZiI6MTc1MTkwMzkwNCwicGF0aCI6Ii8xMDI0NzY5NTAvNDYyNTE1ODYzLTkxMWJjYzg1LWQwNmItNGJjMy1iNTY3LTc2ODJmY2U2Mzk5ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwNzA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDcwN1QxNTU4MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yNDY5ZjhlM2ZhNGIxOWQxNjNlM2IxZjI4NmZjZWY3NTQ0YzUyZmY0ZmU1NTZjZDgwZTYxYzYwNmRhNzhhOWUxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.g2EftmlAGPpW33u2kNAx6kH_FcrCb7apSAxhT4eE_Sg"> <img alt="Image" width="1901" height="846" src="https://private-user-images.githubusercontent.com/102476950/462515864-c93ad48f-7eea-4fc8-bcaf-0c398daf7b1a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTE5MDQyMDQsIm5iZiI6MTc1MTkwMzkwNCwicGF0aCI6Ii8xMDI0NzY5NTAvNDYyNTE1ODY0LWM5M2FkNDhmLTdlZWEtNGZjOC1iY2FmLTBjMzk4ZGFmN2IxYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwNzA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDcwN1QxNTU4MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04MmZjNjNjMjM0MGZjZDBlZDIyYTUyNDc5YWZiMTU0ZWFiOTU5NTIxZTA3Yjg0ZGIxMzg3OTQ3ZmU2MDgzNzQ2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.4saHDd3AlJsl_Funliw9XUR6FkytnLgqjX3dA7_TyCs"> Do you have access to the server logs? It looks like an error on that side rather than the browser.
GiteaMirror commented 2026-02-28 20:07:56 -06:00
Author
Owner
Copy Link
Copy Source

@Margatos19 commented on GitHub (Jul 8, 2025):

Hey guys, this is clearly happening to several of us. Could it be Google Cloud or something? Could the SSL certificate be failing or something?

@Margatos19 commented on GitHub (Jul 8, 2025): Hey guys, this is clearly happening to several of us. Could it be Google Cloud or something? Could the SSL certificate be failing or something?
GiteaMirror commented 2026-02-28 20:07:56 -06:00
Author
Owner
Copy Link
Copy Source

@youngcw commented on GitHub (Jul 8, 2025):

That often happens when the server is misconfigured and is not persisting data.

@youngcw commented on GitHub (Jul 8, 2025): That often happens when the server is misconfigured and is not persisting data.
GiteaMirror commented 2026-02-28 20:07:56 -06:00
Author
Owner
Copy Link
Copy Source

@Margatos19 commented on GitHub (Jul 9, 2025):

Thanks for the info. How could this be fixed? Do you have any ideas?

@Margatos19 commented on GitHub (Jul 9, 2025): Thanks for the info. How could this be fixed? Do you have any ideas?
GiteaMirror commented 2026-02-28 20:07:56 -06:00
Author
Owner
Copy Link
Copy Source

@jon23d commented on GitHub (Jul 9, 2025):

This has been happening fairly often to me, starting about a month ago. There is nothing helpful in the browser console or the server logs, and is fairly transient. At one point I had a whiff of it being caused by a reverse proxy, but I wasn't able to prove it.

@jon23d commented on GitHub (Jul 9, 2025): This has been happening fairly often to me, starting about a month ago. There is nothing helpful in the browser console or the server logs, and is fairly transient. At one point I had a whiff of it being caused by a reverse proxy, but I wasn't able to prove it.
GiteaMirror commented 2026-02-28 20:07:56 -06:00
Author
Owner
Copy Link
Copy Source

@JustAPhrog commented on GitHub (Jul 9, 2025):

@Margatos19 @jon23d can you check if Actual data is mounted? I see that sth unmount that disk so app cannot store data in it.

@JustAPhrog commented on GitHub (Jul 9, 2025): @Margatos19 @jon23d can you check if Actual data is mounted? I see that sth unmount that disk so app cannot store data in it.
GiteaMirror commented 2026-02-28 20:07:57 -06:00
Author
Owner
Copy Link
Copy Source

@JustAPhrog commented on GitHub (Jul 9, 2025):

I've managed to deal with it! I just add last 2 commits but this is most important.
Then terraform apply and it's repaired!

FYI: This issue is same as your's @Margatos19 I think

@JustAPhrog commented on GitHub (Jul 9, 2025): I've managed to deal with it! I just add last [2 commits](https://github.com/eatonc/actual-gcp/commits/main/) but [this](https://github.com/eatonc/actual-gcp/commit/4cba72479ee302eb1bf2adfbb0a0c8f01227d97e) is most important. Then `terraform apply` and it's repaired! FYI: [This issue](https://github.com/eatonc/actual-gcp/issues/10) is same as your's @Margatos19 I think
GiteaMirror commented 2026-02-28 20:07:57 -06:00
Author
Owner
Copy Link
Copy Source

@proracehsd commented on GitHub (Jul 17, 2025):

I have the same problem. In my case, my installation is hosted on a Synology NAS

@proracehsd commented on GitHub (Jul 17, 2025): I have the same problem. In my case, my installation is hosted on a Synology NAS
GiteaMirror commented 2026-02-28 20:07:57 -06:00
Author
Owner
Copy Link
Copy Source

@matt-fidd commented on GitHub (Aug 3, 2025):

Thanks for all of your help in here, it looks like this isn't caused by Actual, and instead by your personal configurations. If you're still having issues, please reach out on the Discord for individual tech support, that's where we do that sort of thing.

@matt-fidd commented on GitHub (Aug 3, 2025): Thanks for all of your help in here, it looks like this isn't caused by Actual, and instead by your personal configurations. If you're still having issues, please reach out on the Discord for individual tech support, that's where we do that sort of thing.
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#2249