github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 15:14:02 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4425] [Bug]: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue. #16119

New Issue
Closed
opened 2026-04-14 19:16:49 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-04-14 19:16:49 -05:00
Owner
Copy Link

Originally created by @vchochois on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4425

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I have a
We had problems syncing your changes. Please report this as a bug by opening a GitHub issue.
message at the bottom.
"Server offline" appears at the top right.

Occurs 100% of the time, both on brave browser and desktop app.

Server is self hosted on a synology NAS in container manager

docker logs does not show any issue.

How can we reproduce the issue?

How can we reproduce the issue?

Where are you hosting Actual?

NAS

What browsers are you seeing the problem on?

Chrome, Desktop App (Electron)

Operating System

Windows 11

Originally created by @vchochois on GitHub (Feb 20, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4425 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I have a We had problems syncing your changes. Please report this as a bug by opening a GitHub issue. message at the bottom. "Server offline" appears at the top right. Occurs 100% of the time, both on brave browser and desktop app. Server is self hosted on a synology NAS in container manager docker logs does not show any issue. ### How can we reproduce the issue? How can we reproduce the issue? ### Where are you hosting Actual? NAS ### What browsers are you seeing the problem on? Chrome, Desktop App (Electron) ### Operating System Windows 11
GiteaMirror added the bugneeds info labels 2026-04-14 19:16:49 -05:00
GiteaMirror commented 2026-04-14 19:16:52 -05:00
Author
Owner
Copy Link

@motoridersd commented on GitHub (Feb 21, 2025):

This started happening to me after I updated my server to 25.2.1. The MacOS app had already updated and it was working fine with the server at 25.1.0.

I use the proxmox server script that runs the server with yarn (https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh) and I use an Ngingx Proxy in front of it.

I restored my Proxmox backup of the server at 25.1.0 and things are working again. I wasn't seeing any errors in the logs that would indicate a problem. I was able to open the web interface directly by IP (bypassing NPM) and I was being asked to set up a new password. It seemed like the server had lost its configuration.

Happy to help debug.

<!-- gh-comment-id:2675138184 --> @motoridersd commented on GitHub (Feb 21, 2025): This started happening to me after I updated my server to 25.2.1. The MacOS app had already updated and it was working fine with the server at 25.1.0. I use the proxmox server script that runs the server with yarn (https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh) and I use an Ngingx Proxy in front of it. I restored my Proxmox backup of the server at 25.1.0 and things are working again. I wasn't seeing any errors in the logs that would indicate a problem. I was able to open the web interface directly by IP (bypassing NPM) and I was being asked to set up a new password. It seemed like the server had lost its configuration. Happy to help debug.
GiteaMirror commented 2026-04-14 19:16:52 -05:00
Author
Owner
Copy Link

@twelve2sn commented on GitHub (Feb 21, 2025):

I have this issue as well, though I am running on PikaPods and my status is showing 'Server online'.

<!-- gh-comment-id:2675504209 --> @twelve2sn commented on GitHub (Feb 21, 2025): I have this issue as well, though I am running on PikaPods and my status is showing 'Server online'.
GiteaMirror commented 2026-04-14 19:16:53 -05:00
Author
Owner
Copy Link

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

Can you see if there are any errors in the browser console? If you use an incognito window can you access your server?

<!-- gh-comment-id:2688417873 --> @youngcw commented on GitHub (Feb 27, 2025): Can you see if there are any errors in the browser console? If you use an incognito window can you access your server?
GiteaMirror commented 2026-04-14 19:16:53 -05:00
Author
Owner
Copy Link

@twelve2sn commented on GitHub (Feb 27, 2025):

This is what my browser (Brave) is showing.

Network tab:
Status Code: 413 Payload Too Large

Console tab:
{type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n<head>\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'}

If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015

<!-- gh-comment-id:2688493723 --> @twelve2sn commented on GitHub (Feb 27, 2025): This is what my browser (Brave) is showing. Network tab: Status Code: 413 Payload Too Large Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n<head>\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'} If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015
GiteaMirror commented 2026-04-14 19:16:54 -05:00
Author
Owner
Copy Link

@twelve2sn commented on GitHub (Feb 27, 2025):

Also, I just noticed that using the browser on desktop, it appears that the data has been updated/sync'd with the changes I've been making using the app even though I get the 'we had trouble syncing' message, However, using browser on Android does not reflect any changes I've made this week.

<!-- gh-comment-id:2688524991 --> @twelve2sn commented on GitHub (Feb 27, 2025): Also, I just noticed that using the browser on desktop, it appears that the data has been updated/sync'd with the changes I've been making using the app even though I get the 'we had trouble syncing' message, However, using browser on Android does not reflect any changes I've made this week.
GiteaMirror commented 2026-04-14 19:16:55 -05:00
Author
Owner
Copy Link

@JahJoey commented on GitHub (Mar 1, 2025):

This is also happening to me. My phone seems to be working alright, but desktop is having issues.

I am running it with PikaPod, this has been an issue since the most recent update.

<!-- gh-comment-id:2691903634 --> @JahJoey commented on GitHub (Mar 1, 2025): This is also happening to me. My phone seems to be working alright, but desktop is having issues. I am running it with PikaPod, this has been an issue since the most recent update.
GiteaMirror commented 2026-04-14 19:16:55 -05:00
Author
Owner
Copy Link

@JahJoey commented on GitHub (Mar 1, 2025):

Temporary fix for this for me was to go to the version of the budget that was accurate and syncing. In my case, I opened up and downloaded the budget in Edge and then clicked on the "Reset Sync" in the settings.

Then I redownloaded the version in Chrome and it seems fine now. Do note that this will reset the encryption key and you will need to reset it and redownload on all devices.

<!-- gh-comment-id:2692354927 --> @JahJoey commented on GitHub (Mar 1, 2025): Temporary fix for this for me was to go to the version of the budget that was accurate and syncing. In my case, I opened up and downloaded the budget in Edge and then clicked on the "Reset Sync" in the settings. Then I redownloaded the version in Chrome and it seems fine now. Do note that this will reset the encryption key and you will need to reset it and redownload on all devices.
GiteaMirror commented 2026-04-14 19:16:56 -05:00
Author
Owner
Copy Link

@niouflex49 commented on GitHub (May 12, 2025):

same here had to use my backup, fix is really expected - fingers crossed

<!-- gh-comment-id:2872931608 --> @niouflex49 commented on GitHub (May 12, 2025): same here had to use my backup, fix is really expected - fingers crossed
GiteaMirror commented 2026-04-14 19:16:57 -05:00
Author
Owner
Copy Link

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

This is what my browser (Brave) is showing.

Network tab: Status Code: 413 Payload Too Large

Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'}

If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015

@twelve2sn That looks like either you need to change the upload size settings on your server, or you have a proxy that is limiting the upload size.

<!-- gh-comment-id:2952691532 --> @youngcw commented on GitHub (Jun 7, 2025): > This is what my browser (Brave) is showing. > > Network tab: Status Code: 413 Payload Too Large > > Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'} > > If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015 @twelve2sn That looks like either you need to change the upload size settings on your server, or you have a proxy that is limiting the upload size.
GiteaMirror commented 2026-04-14 19:16:57 -05:00
Author
Owner
Copy Link

@twelve2sn commented on GitHub (Jun 8, 2025):

My issue appears to have been resolved with a patched version after the issue was entered.

From: youngcw @.>
Sent: Saturday, June 7, 2025 10:44 AM
To: actualbudget/actual @.>
Cc: twelve2sn @.>; Mention @.>
Subject: Re: [actualbudget/actual] [Bug]: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue. (Issue #4425)

[https://avatars.githubusercontent.com/u/28542559?s=20&v=4]youngcw left a comment (actualbudget/actual#4425)https://github.com/actualbudget/actual/issues/4425#issuecomment-2952691532

This is what my browser (Brave) is showing.

Network tab: Status Code: 413 Payload Too Large

Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'}

If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015

@twelve2snhttps://github.com/twelve2sn That looks like either you need to change the upload size settings on your server, or you have a proxy that is limiting the upload size.

—
Reply to this email directly, view it on GitHubhttps://github.com/actualbudget/actual/issues/4425#issuecomment-2952691532, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BPYBN53FTGFWBU334456FSL3CMCHTAVCNFSM6AAAAABXR7BO3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJSGY4TCNJTGI.
You are receiving this because you were mentioned.Message ID: @.***>

<!-- gh-comment-id:2953376397 --> @twelve2sn commented on GitHub (Jun 8, 2025): My issue appears to have been resolved with a patched version after the issue was entered. ________________________________ From: youngcw ***@***.***> Sent: Saturday, June 7, 2025 10:44 AM To: actualbudget/actual ***@***.***> Cc: twelve2sn ***@***.***>; Mention ***@***.***> Subject: Re: [actualbudget/actual] [Bug]: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue. (Issue #4425) [https://avatars.githubusercontent.com/u/28542559?s=20&v=4]youngcw left a comment (actualbudget/actual#4425)<https://github.com/actualbudget/actual/issues/4425#issuecomment-2952691532> This is what my browser (Brave) is showing. Network tab: Status Code: 413 Payload Too Large Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'} If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015 @twelve2sn<https://github.com/twelve2sn> That looks like either you need to change the upload size settings on your server, or you have a proxy that is limiting the upload size. — Reply to this email directly, view it on GitHub<https://github.com/actualbudget/actual/issues/4425#issuecomment-2952691532>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPYBN53FTGFWBU334456FSL3CMCHTAVCNFSM6AAAAABXR7BO3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJSGY4TCNJTGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>
GiteaMirror commented 2026-04-14 19:16:58 -05:00
Author
Owner
Copy Link

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

Hey guys, I managed to fix the issue in the most absurd way. Apparently, it was the VPC. I don't know what's so important for this sync. I have the installation on a free VM on Google Cloud. I had to format the entire installation from the ground up, reinstall from scratch, and it worked.

<!-- gh-comment-id:3089556415 --> @Margatos19 commented on GitHub (Jul 18, 2025): Hey guys, I managed to fix the issue in the most absurd way. Apparently, it was the VPC. I don't know what's so important for this sync. I have the installation on a free VM on Google Cloud. I had to format the entire installation from the ground up, reinstall from scratch, and it worked.
GiteaMirror commented 2026-04-14 19:16:58 -05:00
Author
Owner
Copy Link

@akosasante commented on GitHub (Nov 11, 2025):

For other readers having this issue; I ran into it as well. In my case, I have Actual running as a Docker Compose container on a server behind an nginx proxy.

I was able to resolve it after seeing @youngcw 's comment:

This is what my browser (Brave) is showing.
Network tab: Status Code: 413 Payload Too Large
Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'}
If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015

@twelve2sn That looks like either you need to change the upload size settings on your server, or you have a proxy that is limiting the upload size.

I added client_max_body_size 10M; to my nginx server block. I think nginx defaults to 1MB. The payload that was getting sent was just a bit over that (1.3MB) so that's why it was being rejected.

<!-- gh-comment-id:3517235493 --> @akosasante commented on GitHub (Nov 11, 2025): For other readers having this issue; I ran into it as well. In my case, I have Actual running as a Docker Compose container on a server behind an nginx proxy. I was able to resolve it after seeing @youngcw 's comment: > > This is what my browser (Brave) is showing. > > Network tab: Status Code: 413 Payload Too Large > > Console tab: {type: 'error', subtype: '< ! DOCTYPE html>\n< html lang="en">\n\n< meta char…dy>\n< pre>Payload Too Large< /pre>\n< /body>\n< /html>\n'} > > If it helps, I just started using Actual (running the local app) within the past week or so, and imported all of my transactions going back to late 2015 > > [@twelve2sn](https://github.com/twelve2sn) That looks like either you need to change the upload size settings on your server, or you have a proxy that is limiting the upload size. I added `client_max_body_size 10M;` to my nginx server block. I think [nginx](https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size) defaults to 1MB. The payload that was getting sent was just a bit over that (1.3MB) so that's why it was being rejected.
GiteaMirror commented 2026-04-14 19:16:59 -05:00
Author
Owner
Copy Link

@cjfagerstrom commented on GitHub (Feb 1, 2026):

I just started getting this error, but I had previously reconfigured my Nginx to client_max_body_size 200M;

<!-- gh-comment-id:3831241481 --> @cjfagerstrom commented on GitHub (Feb 1, 2026): I just started getting this error, but I had previously reconfigured my Nginx to `client_max_body_size 200M;`
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 bug needs info
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#16119
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?