Unable to upload "large" (1.1MB) files

J_Roeleveld 2020-04-20 07:16:46 UTC #1

Hi,

I can succesfully upload files, but when the filesize is 1.1MB, it fails.
I can’t find any hints in the logs (docker logs -f doesn’t show anything useful)
I tried logs from all running containers.

Downloading existing large files (ex. 5.2 MB) works.

For reference:
This is an updated instance, currently running the latest Egroupware CE on Docker.

Many thanks for any help,

Joost

J_Roeleveld 2020-04-20 07:20:35 UTC #2

Extra info:
A “workaround” is to:

Create a draft-email using a different email application
Attach the file to the email
Using the email app of eGroupware, save the file to the filestore (using the orange folder-icon next to the attachment)

RalfBecker 2020-04-20 07:42:24 UTC #3

There is a problem with our Nginx configuration on the host (NOT in the container!), which I thought I fixed, but unfortunately it’s still there:

github.com

EGroupware/build.opensuse.org/blob/master/server:eGroupWare/egroupware-docker-19.1/egroupware-docker/nginx.conf#L39




	server_name _;
	root /var/www/html;


	index index.php index.nginx-debian.html index.html index.htm;


	# include other EGroupware parts like Collabora
	include app.d/egroupware*.conf;


	# other settings
	client_max_body_size 65M;


	# proxy into EGroupware container
	location /egroupware {
		proxy_pass http://127.0.0.1:8080;
		include proxy_params;
		# to allow longer running requests like eg. backup or restore
		proxy_read_timeout    60m;
	}


	# PHP in docroot

You need to delete that “client_max_body_size 65M;” and reload nginx: nginx -s reload

I’ll changed it now for the next maintenance release.

Ralf

J_Roeleveld 2020-04-20 07:51:22 UTC #4

Ralf,

That line was actually missing in my main Nginx server, which is configured as a reverse-proxy to the egroupware-nginx docker container.

After adding that, (and removing the one that is used by the docker) it is now working.

Many thanks for the hint.

Kind regards,

Joost Roeleveld