github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-08 04:49:45 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[Bug]: Unable to sync #2035

New Issue
Closed
opened 2026-02-28 20:01:40 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:01:40 -06:00
Owner
Copy Link

Originally created by @deanpribetic on GitHub (Apr 9, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Upgraded to v25.4.0 via the Proxmox Community Script.

Initially the server wasn't running so I started that with yarn start:server

Went through the bootstrap service and managed to get my data back. Issue now is I am getting errors which say "We had problems syncing your changes. Please report this as a bug by opening a Github issue"

Looking at the logs I can see this:

2025-04-09T22:28:36.824z info: POST 200 / sync/sync
PayloadTooLargeError: request entity too large
at readStream (/opt/actualbudget/node_modules/raw-body/index.js: 163:17)
at getRawBody (/opt/actualbudget/node_modules/raw-body/index.js:116:12)
at read (/opt/actualbudget/node
at rawParser (/opt/actualbudget/node_modules/body-parser/lib/types/raw.js:81:5)
at Layer.handle [as handle_request] (/opt/actualbudget/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/opt/actualbudget/node_modules/express/lib/router/index.js: 328:13)
at /opt/actualbudget/node_modules/express/lib/router/index.js:286:9
at Function process_params (/opt/actualbudget/node_modules/express/1ib/router/index.js: 346:12)
at next (/opt/actualbudget/node_modules/express/1ib/router/index.js:280:10)
at isonParser (/opt/actualbudget/node modules/body-parser/lib/types/ison.is:122:7)

As stated, I am using Proxmox with the Actual Budget LXC. I have 4GB Ram and an 8GB disk provided.

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?

Firefox

Operating System

Linux

Originally created by @deanpribetic on GitHub (Apr 9, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Upgraded to v25.4.0 via the Proxmox Community Script. Initially the server wasn't running so I started that with `yarn start:server` Went through the bootstrap service and managed to get my data back. Issue now is I am getting errors which say "We had problems syncing your changes. Please report this as a bug by opening a Github issue" Looking at the logs I can see this: ``` 2025-04-09T22:28:36.824z info: POST 200 / sync/sync PayloadTooLargeError: request entity too large at readStream (/opt/actualbudget/node_modules/raw-body/index.js: 163:17) at getRawBody (/opt/actualbudget/node_modules/raw-body/index.js:116:12) at read (/opt/actualbudget/node at rawParser (/opt/actualbudget/node_modules/body-parser/lib/types/raw.js:81:5) at Layer.handle [as handle_request] (/opt/actualbudget/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/opt/actualbudget/node_modules/express/lib/router/index.js: 328:13) at /opt/actualbudget/node_modules/express/lib/router/index.js:286:9 at Function process_params (/opt/actualbudget/node_modules/express/1ib/router/index.js: 346:12) at next (/opt/actualbudget/node_modules/express/1ib/router/index.js:280:10) at isonParser (/opt/actualbudget/node modules/body-parser/lib/types/ison.is:122:7) ``` As stated, I am using Proxmox with the Actual Budget LXC. I have 4GB Ram and an 8GB disk provided. ### 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? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:01:40 -06:00
GiteaMirror commented 2026-02-28 20:01:41 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 9, 2025):

set the max upload size env vars or config settings to be bigger

@youngcw commented on GitHub (Apr 9, 2025): set the max upload size env vars or config settings to be bigger
GiteaMirror commented 2026-02-28 20:01:41 -06:00
Author
Owner
Copy Link

@deanpribetic commented on GitHub (Apr 10, 2025):

YEp - that worked. Thankyou!

@deanpribetic commented on GitHub (Apr 10, 2025): YEp - that worked. Thankyou!
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#2035
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?