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.

I realised that I had put the nginx timeout settings in the wrong endpoint. Now it’s at the right place and I can send 1GB files both inside and outside the pi.

It works with curl, but I don’t really know how to test the web client behind the rathole. The service is only accessible through the reverse proxy, which depends on the domain name to send requests correctly. Even if I managed to access the client in this way, element web would just send the file to the domain name, which would just come back through the rathole.

No, but I’ll try.

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.