[Bug]: "We had trouble syncing your changes" #2693

Closed
opened 2026-02-28 20:24:39 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @vgy467 on GitHub (Dec 7, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happened! ActualBudget sync was working, then it tried syncing again and not only did it not work, but it reverted the file back to how it was before today (i.e. reverted all changes done today).

Also, depending on what page is saved, it might show this error message instead: "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a neew issue on GitHub."

Image Image

How can we reproduce the issue?

  • Clicking the "Sync" button on top right of page
  • and also when typing "Ctrl + S" to try to save the changes

I then got a notification saying "We had trouble syncing your changes. Please report this as a bug by [opening a GitHub issue."

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 10

Originally created by @vgy467 on GitHub (Dec 7, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? A bug happened! ActualBudget sync was working, then it tried syncing again and not only did it not work, but it reverted the file back to how it was before today (i.e. reverted all changes done today). Also, depending on what page is saved, it might show this error message instead: "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a neew issue on GitHub." <img width="572" height="98" alt="Image" src="https://github.com/user-attachments/assets/1fbd095e-2ad4-44ae-aea6-9a55552bb14b" /> <img width="594" height="858" alt="Image" src="https://github.com/user-attachments/assets/b5b6f9aa-85e9-40f7-980f-7fbfb8751e68" /> ### How can we reproduce the issue? - Clicking the "Sync" button on top right of page - and also when typing "Ctrl + S" to try to save the changes I then got a notification saying "We had trouble syncing your changes. Please report this as a bug by [opening a GitHub issue." ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 10
GiteaMirror added the bugneeds info labels 2026-02-28 20:24:39 -06:00
Author
Owner

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

first export your data to make sure it doesn't get lost. Then try clearing your browser cache. Also open the browser console and see if there is any more information there.

@youngcw commented on GitHub (Dec 8, 2025): first export your data to make sure it doesn't get lost. Then try clearing your browser cache. Also open the browser console and see if there is any more information there.
Author
Owner

@dsbrown713 commented on GitHub (Dec 10, 2025):

Hello, I am getting a very similar error when trying to sync my server. I am hosting Actual on a VM in GCP (I followed this guide https://github.com/eatonc/actual-gcp) My OS is Windows 11 and I am using Opera as my browser.
In the console, I see this error message when it fails to sync:
Upload failure HTTPError: HTTPError: unsuccessful status code (500): {"status":"error"}
at cloud-storage.ts:58:13
at async fetchJSON (cloud-storage.ts:67:9)
at async upload (cloud-storage.ts:295:5)
PostError: PostError: internal
at throwIfNot200 (post.ts:11:13)
at post.ts:212:17
at async _fullSync (index.ts:671:9)
at async index.ts:561:5
at async app.ts:20:3

I can open my own issue if necessary, but I figured these may be related.

@dsbrown713 commented on GitHub (Dec 10, 2025): Hello, I am getting a very similar error when trying to sync my server. I am hosting Actual on a VM in GCP (I followed this guide https://github.com/eatonc/actual-gcp) My OS is Windows 11 and I am using Opera as my browser. In the console, I see this error message when it fails to sync: Upload failure HTTPError: HTTPError: unsuccessful status code (500): {"status":"error"} at cloud-storage.ts:58:13 at async fetchJSON (cloud-storage.ts:67:9) at async upload (cloud-storage.ts:295:5) PostError: PostError: internal at throwIfNot200 (post.ts:11:13) at post.ts:212:17 at async _fullSync (index.ts:671:9) at async index.ts:561:5 at async app.ts:20:3 I can open my own issue if necessary, but I figured these may be related.
Author
Owner

@youngcw commented on GitHub (Dec 10, 2025):

Hello, I am getting a very similar error when trying to sync my server. I am hosting Actual on a VM in GCP (I followed this guide https://github.com/eatonc/actual-gcp) My OS is Windows 11 and I am using Opera as my browser. In the console, I see this error message when it fails to sync: Upload failure HTTPError: HTTPError: unsuccessful status code (500): {"status":"error"} at cloud-storage.ts:58:13 at async fetchJSON (cloud-storage.ts:67:9) at async upload (cloud-storage.ts:295:5) PostError: PostError: internal at throwIfNot200 (post.ts:11:13) at post.ts:212:17 at async _fullSync (index.ts:671:9) at async index.ts:561:5 at async app.ts:20:3

I can open my own issue if necessary, but I figured these may be related.

@dsbrown713 That seems like your server is inaccessible. Make sure that its running and you can access it. Please open separate tickets

@youngcw commented on GitHub (Dec 10, 2025): > Hello, I am getting a very similar error when trying to sync my server. I am hosting Actual on a VM in GCP (I followed this guide https://github.com/eatonc/actual-gcp) My OS is Windows 11 and I am using Opera as my browser. In the console, I see this error message when it fails to sync: Upload failure HTTPError: HTTPError: unsuccessful status code (500): {"status":"error"} at cloud-storage.ts:58:13 at async fetchJSON (cloud-storage.ts:67:9) at async upload (cloud-storage.ts:295:5) PostError: PostError: internal at throwIfNot200 (post.ts:11:13) at post.ts:212:17 at async _fullSync (index.ts:671:9) at async index.ts:561:5 at async app.ts:20:3 > > I can open my own issue if necessary, but I figured these may be related. @dsbrown713 That seems like your server is inaccessible. Make sure that its running and you can access it. Please open separate tickets
Author
Owner

@github-actions[bot] commented on GitHub (Dec 18, 2025):

This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.

@github-actions[bot] commented on GitHub (Dec 18, 2025): This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2693