request entity too large on json import

[Stefal]

Describe the bug

I can't import a kresus json backup

Context

• Hardware: Old computer with proxmox
• YunoHost version: 11.2.3
• I have access to my server: *Through SSH | through the webadmin |

Steps to reproduce

• If the error occurs in your browser, explain what you did:
  1. Go to 'Kresus Import'
  2. Import a json file with a file size > 1.69MB'
  3. Click on import
  4. See error
     

In the web browser console I see these messages :

An error has occurred with the following information:
        - message: ?
        - stack: no stack
        - stringified: {"message":"?","shortMessage":"?"}

And

État  413  Request Entity Too Large

Expected behavior

Working import

[Stefal]

Just for a quick test, I've removed some transaction from my backup to get a 1.2MB json file, and now I can import it.

What setting should I edit to be able to import my full backup ?

[nicofrand]

Hi!

kresus_ynh/conf/nginx.conf

Line 18 in eb29d92

client_max_body_size 8M;

is supposed to be enough.

I'll double check if something is missing though, next week.

[nicofrand]

Do you have more logs?

[Stefal]

After some trial and errors, I've added client_max_body_size 20M; in the html section of /etc/nginx/nginx.conf and the import was successful.

[Stefal]

I'm not sure it's a good idea to close this issue. Something should be done so nobody would have this problem in the future.

[nicofrand]

Well, I showed you the app already defines the max size. You chose to edit the global system config, without any other logs or info, and I don't know what was modified on your setup, there is nothing else I can do. Le 27 août 2023 19:37:36 GMT+02:00, Stefal ***@***.***> a écrit :

…

I'm not sure it's a good idea to close this issue. Something should be done so nobody would have this problem in the future. -- Reply to this email directly or view it on GitHub: #163 (comment) You are receiving this because you modified the open/close state. Message ID: ***@***.***>

[bnjbvr]

In any case, if you see any possible improvements @Stefal, feel free to make a patch! We welcome contributions :-)