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.

Exactly 😂

Yes, that’s what I tried, but curl worked perfectly fine, while the client refused.

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.

I have actually tried hosting Nextcloud, but I only have 1GB of ram and already running more than 2GB of swap often means the linux kernel crashes because of memory corruption. This is a personnal server, so the main reason is to have a big selling point for my family/friends/close colleagues to switch. It’s also a testing ground for a project with an organisation I’m working with that would use the service for work stuff, and again it’s a big selling point that we can send 50 times the file size as Discord for free.

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.