Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

413 Request entity too large error on first upload of large imported budget #20

Closed
bjornstark opened this issue Jan 1, 2024 · 4 comments

Comments

@bjornstark
Copy link

I imported a YNAB budget with seven years of transactions. The import went well, but I got the error "This file is not a cloud file" afterwards, and the file refused to sync. The underlying error appeared to be a 413 Request entity too large from the file upload endpoint.

Adding this to /etc/nginx/conf.d/[domain]/actual.d seems to have solved the problem:

client_max_body_size 40M;

@romdim
Copy link

romdim commented Jan 31, 2024

This is weird. I've been getting the same error. I've changed the max size to 100M on the following places:

  • /etc/nginx/conf.d/[domain].d/actual.conf
  • /etc/nginx/conf.d/[domain].conf
  • /etc/nginx/nginx.conf

But even after restarting the service, nothing seems to have done the trick..

@romdim
Copy link

romdim commented Jan 31, 2024

Nevermind, found the solution to my issue. Writing it down for future reference + others. I had to restart the whole nginx service, not just the app. So sudo systemctl restart nginx.

@Quiwy
Copy link
Contributor

Quiwy commented Jul 5, 2024

Same problem here, thanks for the solution

@ericgaspar
Copy link
Member

client_max_body_size 50M; is set as default now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants