This repository was archived by the owner on Nov 18, 2025. It is now read-only.
Closed
Conversation
Co-authored-by: matiss <matiss@mja.lv>
|
Cursor Agent can help with this pull request. Just |
✅ Deploy Preview for actualbudget-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This comment has been minimized.
This comment has been minimized.
Co-authored-by: matiss <matiss@mja.lv>
actual-github-bot
bot
added
🔍 ready for review
MatissJanis
added
🚧 WIP
AI generated
and removed
🔍 ready for review
joel-jeremy
approved these changes
Oct 31, 2025
actual-github-bot
bot
added
✅ approved
matt-fidd
approved these changes
Nov 3, 2025
Member
matt-fidd
left a comment
matt-fidd
left a comment
There was a problem hiding this comment.
Great idea, I think it would be better with a new sentence where you talk about possible fixes but I won't block on it.
Co-authored-by: Matt Fiddaman <github@m.fiddaman.uk>
actual-github-bot
bot
added
🔍 ready for review
matt-fidd
approved these changes
Nov 4, 2025
actual-github-bot
bot
added
✅ approved
youngcw
reviewed
Nov 6, 2025
|
|
||
| - **Q.** _Why do I see `PayloadTooLargeError: request entity too large` when uploading a file?_ | ||
|
|
||
| **A.** This happens when the file you are uploading exceeds the maximum request size allowed by the service or infrastructure hosting your Actual instance (for example, a reverse proxy, container platform, or managed host). Actual itself does not enforce this limit, so you’ll need to adjust the upload size settings wherever you deploy Actual. Common fixes include increasing the body size limit in Nginx/Traefik, updating the `client_max_body_size` for Docker behind a proxy, or changing the request size setting in your managed hosting provider. If you’re unsure how to change the limit for your setup, ask in the community Discord; other self-hosted users often share configuration snippets for their platforms. |
Member
There was a problem hiding this comment.
Is it true that we don't enforce a size limit? We have those env vars for upload size and people need to change those sometimes.
Member
Author
There was a problem hiding this comment.
TBH good catch. You are 100% correct
Member
Author
|
Moved to the other repo: actualbudget/actual#6103 |
MatissJanis
deleted the
cursor/add-faq-entry-for-file-size-error-3e1d
branch
actual-github-bot
bot
removed
the
✅ approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request contains changes generated by a Cursor Cloud Agent
Note
Adds a new FAQ explaining
PayloadTooLargeError: request entity too largeduring file uploads and how to resolve it by increasing host/proxy request size limits.Written by Cursor Bugbot for commit 954be0a. This will update automatically on new commits. Configure here.