github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Migrating from one server to another causes Payload Too Large error #2968

New Issue
Closed
opened 2026-02-28 20:33:36 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:33:36 -06:00
Owner
Copy Link

Originally created by @Fryuni on GitHub (Feb 26, 2026).

What happened?

I exported my budget file from a managed Actual instance (on PikaPod) and tried to import it an instance running on my VPS.

It has about 2 years worth of data. Apparently that is too much to sync in a single call to the new server, so it doesn't get synced at all.

PayloadTooLargeError: request entity too large
    at readStream (/app/node_modules/raw-body/index.js:163:17)
    at getRawBody (/app/node_modules/raw-body/index.js:116:12)
    at read (/app/node_modules/body-parser/lib/read.js:114:3)
    at rawParser (/app/node_modules/body-parser/lib/types/raw.js:41:5)
    at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)
    at trimPrefix (/app/node_modules/router/index.js:342:13)
    at /app/node_modules/router/index.js:297:9
    at processParams (/app/node_modules/router/index.js:582:12)
    at next (/app/node_modules/router/index.js:291:5)
    at read (/app/node_modules/body-parser/lib/read.js:63:5)

How can we reproduce the issue?

  1. On the old instance:
  2. Open the budget file
  3. Go to Settings
  4. Click on "Export data"
  5. On the new instance:
  6. Click on "Import file"
  7. Pick the file exported from the old instance

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Safari

Operating System

Mac OSX

Originally created by @Fryuni on GitHub (Feb 26, 2026). ### What happened? I exported my budget file from a managed Actual instance (on PikaPod) and tried to import it an instance running on my VPS. It has about 2 years worth of data. Apparently that is too much to sync in a single call to the new server, so it doesn't get synced at all. ``` PayloadTooLargeError: request entity too large at readStream (/app/node_modules/raw-body/index.js:163:17) at getRawBody (/app/node_modules/raw-body/index.js:116:12) at read (/app/node_modules/body-parser/lib/read.js:114:3) at rawParser (/app/node_modules/body-parser/lib/types/raw.js:41:5) at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17) at trimPrefix (/app/node_modules/router/index.js:342:13) at /app/node_modules/router/index.js:297:9 at processParams (/app/node_modules/router/index.js:582:12) at next (/app/node_modules/router/index.js:291:5) at read (/app/node_modules/body-parser/lib/read.js:63:5) ``` ### How can we reproduce the issue? 1. On the old instance: 1. Open the budget file 2. Go to Settings 3. Click on "Export data" 2. On the new instance: 1. Click on "Import file" 2. Pick the file exported from the old instance ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 20:33:36 -06:00
GiteaMirror commented 2026-02-28 20:33:36 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 26, 2026):

You either need to increase the upload size settings in your server or a reverse proxy if you have one. The docs show the env vars for the actual server upload sizes.

@youngcw commented on GitHub (Feb 26, 2026): You either need to increase the upload size settings in your server or a reverse proxy if you have one. The docs show the env vars for the actual server upload sizes.
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#2968
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?