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

[GH-ISSUE #6326] [Bug]: 413 Content Too Large #16933

New Issue
Closed
opened 2026-04-14 19:54:24 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-14 19:54:24 -05:00
Owner
Copy Link

Originally created by @Rihan9 on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6326

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Hi!
I am unable to use my ActualBudget instance. The syncronization seems broken.

Opening the Dev Console in my browser, I can see a call to:
https://DOMAIN/sync/sync

that respond with:
413 Content Too Large

and I'm pretty sure this is the issue.
I don't have that much data: 3 account and 9 widget in the dashboard, not even a year of data. What should I do? the "Reset Sync" functionality doesn't work.

How can we reproduce the issue?

I don't really know because I can't identify why this is appening.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @Rihan9 on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6326 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Hi! I am unable to use my ActualBudget instance. The syncronization seems broken. Opening the Dev Console in my browser, I can see a call to: `https://DOMAIN/sync/sync` that respond with: `413 Content Too Large` and I'm pretty sure this is the issue. I don't have that much data: 3 account and 9 widget in the dashboard, not even a year of data. What should I do? the "Reset Sync" functionality doesn't work. ### How can we reproduce the issue? I don't really know because I can't identify why this is appening. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror commented 2026-04-14 19:54:25 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Dec 7, 2025):

👋 https://actualbudget.org/docs/faq

I think this is what you are experiencing and should solve it.

Q. Why do I see PayloadTooLargeError: request entity too large when uploading a file?

A. This error can occur when the file exceeds size limits enforced either by Actual itself or by your hosting infrastructure (reverse proxy, container platform, or managed host).

Actual enforces upload size limits that can be configured via environment variables:

ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB (default: 20 MB) - for general uploads
ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB (default: 20 MB) - for sync files
ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB (default: 50 MB) - for encrypted sync files
If you need to upload larger files, increase these values in your environment configuration. Additionally, you may need to adjust upload size settings in your reverse proxy (e.g., client_max_body_size in Nginx/Traefik) or managed hosting provider, as these can also enforce limits. If you're unsure how to change the limit for your setup, ask in the [community Discord](https://discord.gg/pRYNYr4W5A); other self-hosted users often share configuration snippets for their platforms.

If this does not solve it or if you have further questions - please use the community discord for tech support. I'm 99% certain this is due to how you have set-up Actual.

<!-- gh-comment-id:3622049373 --> @MatissJanis commented on GitHub (Dec 7, 2025): 👋 https://actualbudget.org/docs/faq I think this is what you are experiencing and should solve it. ``` Q. Why do I see PayloadTooLargeError: request entity too large when uploading a file? A. This error can occur when the file exceeds size limits enforced either by Actual itself or by your hosting infrastructure (reverse proxy, container platform, or managed host). Actual enforces upload size limits that can be configured via environment variables: ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB (default: 20 MB) - for general uploads ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB (default: 20 MB) - for sync files ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB (default: 50 MB) - for encrypted sync files If you need to upload larger files, increase these values in your environment configuration. Additionally, you may need to adjust upload size settings in your reverse proxy (e.g., client_max_body_size in Nginx/Traefik) or managed hosting provider, as these can also enforce limits. If you're unsure how to change the limit for your setup, ask in the [community Discord](https://discord.gg/pRYNYr4W5A); other self-hosted users often share configuration snippets for their platforms. ``` If this does not solve it or if you have further questions - please use the community discord for tech support. I'm 99% certain this is due to how you have set-up Actual.
GiteaMirror commented 2026-04-14 19:54:26 -05:00
Author
Owner
Copy Link

@Rihan9 commented on GitHub (Dec 7, 2025):

Finded the cause: the locale was incompatible.
I recently switched my chrome installation (from flatpak to native, but this is out of topic) and the new installation was still in my native language (Italian, locale it-IT).
I saw an error message in the console about falling back to anoter locale: Unknown locale it-IT, falling back to it.
I don't have a problem to use the app in English so I switched it to it just to remove this message and now the syncronization works. It doesn make sense to me ahah

<!-- gh-comment-id:3622050656 --> @Rihan9 commented on GitHub (Dec 7, 2025): Finded the cause: the locale was incompatible. I recently switched my chrome installation (from flatpak to native, but this is out of topic) and the new installation was still in my native language (Italian, locale it-IT). I saw an error message in the console about falling back to anoter locale: `Unknown locale it-IT, falling back to it`. I don't have a problem to use the app in English so I switched it to it just to remove this message and now the syncronization works. It doesn make sense to me ahah
GiteaMirror commented 2026-04-14 19:54:26 -05:00
Author
Owner
Copy Link

@Rihan9 commented on GitHub (Dec 7, 2025):

Hi @MatissJanis I didn' t think to check the FAQ, my bad. Just to be safe I bumped them to 10 times the default values.

<!-- gh-comment-id:3622059175 --> @Rihan9 commented on GitHub (Dec 7, 2025): Hi @MatissJanis I didn' t think to check the FAQ, my bad. Just to be safe I bumped them to 10 times the default values.
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
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#16933
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?