gyoo

No I’m not. I don’t have any crashes or anything of the sort and I am monitoring it very closely. Also, using curl works just fine, so it doesn’t seem to be about the server…

I am thinking of trying caddy, but I don’t think it’s the issue. As I said, a curl command works fine, and I also have a peertube instance that takes way bigger files just fine.

Thanks, I try over there

That’s what I tought, but both cinny and element web have this issue and it sounds like people should be able to go up to 2GB.

Yeah, I can’t find either of those settings in the configuration docs and I wasn’t just sending images.

How would I do that? The curl command already works and the service is being handeld by the reverse proxy, which depends on the domain name to pass the requests correctly. Even if I succeeded, element-web is configured to send the file to the domain name, not the local address.

The idea is to have one nginx container responsible for the tls handling and request distribution (I have more than one service running on the device) and the other for actually handling the request. It keeps things organised.