[GH-ISSUE #1826] [Bug]: Problems syncing changes #7629

Closed
opened 2026-04-10 17:31:31 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @ExZiByte on GitHub (Oct 25, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1826

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Fresh install of Actual trying to import my transactions in OFX format also tried in the CSV format.

Firefox console has

Error: PostError: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>

What error did you receive?

I get a popup stating "We had problems syncing your changes"

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 10

Originally created by @ExZiByte on GitHub (Oct 25, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1826 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Fresh install of Actual trying to import my transactions in OFX format also tried in the CSV format. Firefox console has ``` Error: PostError: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx</center> </body> </html> ``` ### What error did you receive? I get a popup stating "We had problems syncing your changes" ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 10
GiteaMirror added the bug label 2026-04-10 17:31:31 -05:00
Author
Owner

@hossain-khan commented on GitHub (Aug 7, 2024):

For future reference, I have also experienced same issue.

Request

curl 'https://actual-server/sync/upload-user-file' \
  -H 'DNT: 1' \
  -H 'X-ACTUAL-TOKEN: XYZ' \
  -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36' \
  -H 'Content-Type: application/encrypted-file' \
  -H 'Referer: https://actual-server/static/js/browser-server.Kf_xQo8f.js' \
  -H 'X-ACTUAL-NAME: Expense' \
  -H 'X-ACTUAL-FORMAT: 2' \
  -H 'X-ACTUAL-FILE-ID: fda-xyz-1699' \
  --data-raw 4.1MB-encrypted-file

Response

<html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.18.0 (Ubuntu)</center>
</body>
</html>
  • Server version: v24.8.0
  • Installation: Docker

I am guessing having non-synced local version is fine.

Screenshot 2024-08-11 162212

Screenshot 2024-08-11 162401

Screenshot 2024-08-11 162446

<!-- gh-comment-id:2272530548 --> @hossain-khan commented on GitHub (Aug 7, 2024): For future reference, I have also experienced same issue. ### Request ```sh curl 'https://actual-server/sync/upload-user-file' \ -H 'DNT: 1' \ -H 'X-ACTUAL-TOKEN: XYZ' \ -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36' \ -H 'Content-Type: application/encrypted-file' \ -H 'Referer: https://actual-server/static/js/browser-server.Kf_xQo8f.js' \ -H 'X-ACTUAL-NAME: Expense' \ -H 'X-ACTUAL-FORMAT: 2' \ -H 'X-ACTUAL-FILE-ID: fda-xyz-1699' \ --data-raw 4.1MB-encrypted-file ``` ### Response ```html <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.18.0 (Ubuntu)</center> </body> </html> ``` * Server version: v24.8.0 * Installation: Docker I am guessing having non-synced local version is fine. ![Screenshot 2024-08-11 162212](https://github.com/user-attachments/assets/d68d7625-5d61-4d6f-8cfd-9a221d0c1bc3) ![Screenshot 2024-08-11 162401](https://github.com/user-attachments/assets/faab8b45-8b39-4b45-82c9-4a4164ef6db8) ![Screenshot 2024-08-11 162446](https://github.com/user-attachments/assets/96ab7b0f-6f5a-4b5f-ab87-c7de119c6e22)
Author
Owner

@hossain-khan commented on GitHub (Aug 11, 2024):

Quick update - I reported the same issue at Discord #support


I created new server at pikapod - App: v24.8.0 | Server: v24.8.0
And imported same 2 budget files, and syncing is working fine for both of them.

Must be something wrong with my installation.

I will go through the doc again at https://actualbudget.org/docs/install/docker and post updates on my findings. Thanks

<!-- gh-comment-id:2282888612 --> @hossain-khan commented on GitHub (Aug 11, 2024): Quick update - I [reported](https://discord.com/channels/937901803608096828/1272291577993367654/1272291577993367654) the same issue at Discord `#support` --- I created new server at pikapod - `App: v24.8.0 | Server: v24.8.0` And imported same 2 budget files, and syncing is working fine for both of them. Must be something wrong with my installation. I will go through the doc again at https://actualbudget.org/docs/install/docker and post updates on my findings. Thanks
Author
Owner

@hossain-khan commented on GitHub (Aug 11, 2024):

ℹ️ Update

The issue was specific to my setup of using reverse proxy using Nginx.

By default, the default value for client_max_body_size in Nginx is 1 MB.

After I set that to client_max_body_size 50M; I was able to upload and make the budget file as cloud file. 😅

<!-- gh-comment-id:2282913921 --> @hossain-khan commented on GitHub (Aug 11, 2024): ### ℹ️ Update The issue was specific to my setup of using reverse proxy using Nginx. By default, the default value for `client_max_body_size` in Nginx is `1 MB`. After I set that to `client_max_body_size 50M;` I was able to upload and make the budget file as cloud file. :sweat_smile: ✅
Author
Owner

@pavekovt commented on GitHub (Nov 6, 2024):

For someone how's running Actual in Kubernetes and using nginx ingress controller you can add annotation to your individual ingress resources to increase client_max_body_size:

  • Official NGINX Ingress: nginx.ingress.kubernetes.io/proxy-body-size: "50m"
  • Official Kubernetes Ingress: nginx.org/client-max-body-size: "50m"

Annotation depends of which nginx controller you are running:

If you are using the official NGINX Ingress, the correct annotation is here: https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/

If you are using the official Kubernetes Ingress based on NGINX, the correct annotation is this: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-max-body-size

Source: https://stackoverflow.com/a/73548785

<!-- gh-comment-id:2459812300 --> @pavekovt commented on GitHub (Nov 6, 2024): For someone how's running Actual in Kubernetes and using nginx ingress controller you can add annotation to your individual ingress resources to increase `client_max_body_size`: * Official NGINX Ingress: `nginx.ingress.kubernetes.io/proxy-body-size: "50m"` * Official Kubernetes Ingress: `nginx.org/client-max-body-size: "50m"` Annotation depends of which nginx controller you are running: > If you are using the official NGINX Ingress, the correct annotation is here: https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/ > > If you are using the official Kubernetes Ingress based on NGINX, the correct annotation is this: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-max-body-size Source: https://stackoverflow.com/a/73548785
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#7629