Large JSON file upload getting nginx 413 error

[girish]

@marcusquinn Oh, did not know that. In fact, the error message seems exactly the same - https://community.cloudflare.com/t/413-request-entity-too-large-upload-limit-100mb/97630 . So @tkd do you use Cloudflare?

[marcusquinn]

@girish Yeah, and it's $20/month per domain for "Pro" to increase that limit.

Hence, I'm looking at a DNS Made Easy + X4B + BunnyCDN combo as an alternative.

A little more work to manage separately but the ability to control costs and features more granularly is necessary when managing a variety of domain needs but aiming for a common system among all of them.

[tkd]

No I'm not using Cloudflare, Cloudron is hosted at Digital Ocean using and I'm connecting direct to the server, as I mentioned above I'm not aware of any proxy or anything between the browser and Cloudron.

[nebulon]

@tkd do you have a test json file for us to work with? If you have non public data in there, you may also send us a mail to support@cloudron.io

So far I wasn't finding a quick way to generate an export with over 100M

[tkd]

@nebulon Sure, it's non public so I will email to support address now thanks.

[nebulon]

Ok, thanks that helped. There are two memory related issues I can reproduce.

1. Memory limit from Cloudron side: With that json import I had to at least bump up the memory limit for that app instance via the Cloudron dashboard to 1Gb temporarily
2. It will still fail due to JavaScript heap out of memory in nodejs

Both issues will result in status code 413, which results in Ghost showing the error message Request is larger than the maximum file size the server allows which is not related to the actual upload size or so, but actually a processing memory requirement issue.

I don't yet have a solution but just wanted to give an update here.

[tkd]

Thanks. This is quite important to us to get this loaded into a Ghost instance. If anyone has any ideas or a temporary work around I'd be happy to know - or if Ghost has another method of importing content that would work with the Cloudron package.

[nebulon]

So the fix, with which I was successfully able to import this file is, to give the javascript engine, which is used by nodejs, more heap space:

node --max-old-space-size=4096  current/index.js

In this case allowing up to 4Gb. The issue is, I am not sure how to put this properly in the package, as this heavily depends on the set memory limit of the whole app instance.

Hopefully we can come up with a good solution later today.

[tkd]

@nebulon Appreciated. If there is any temporary command I can execute in the app's terminal for now that would make this setting would be fine until you have a full fix.

[nebulon]

We will make a new release which contains a env file at /app/data/env
There the max-old-space can be set/overwriten temporarily for the import. The test json in this case worked with a 2Gb limit for me.

The file can be changed using the file manger from the cloudron dashboard or webterminal. Once changed, the app has to be restarted.

Of course first update your ghost instance to latest package version 3.126.1

[girish]

@tkd Docs are here for the new package - https://cloudron.io/documentation/apps/ghost/#importing

[tkd]

Thanks guys, managed to get this working with the new package

[marcusquinn]

Truly heroic support! Happy to know this is covered and tested