Index ¦ Archives ¦ Atom

Owncloud on docker behind nginx-proxy: file size error solved

Wow, this took me a while: I am running an Owncloud server on my private VPS as a Docker container. I orchestrate all the different webapps that run on that server using Docker Compose and make use of the magnificent jwilder/nginx-proxy (in combination with the docker-letsencrypt-nginx-proxy-companion)to serve different domains on the same VPS.

While I was using Owncloud I encountered a nasty upload error every now and then. Something like Error downloading [file] - server replied: Request Entity Too Large or Continue blacklisting: Error downloading [file] - server replied: Request Entity Too Large or simply Error downloading [file] - server replied: Request Entity Too Large and your file stays marked with a red cross or yellow exclamation mark. You get the point. There are a lot of guides on how to setup your Apache configuration to play nicely with Owncloud when it comes to bigger files. But in my case everything was set up using the official Owncloud docker image that comes with all configuration files optimised already.

Finally, today I realized that the Nginx reverse proxy that is running in front of the Apache also demands configuration. Following this part of the documentation you want to volume mount the /etc/nginx/vhost.d folder and add a configuration file for your Owncloud domain:

client_max_body_size 4096m;

Go ahead and reload the nginx container. You might have to move the files that did not sync out of your local Owncloud folder and move them back in for the sync process to trigger again. And you have nice green checkmarks again!

Hoping that I save someone time and headaches... Cheers!

© Thomas Emmerling. Built using Pelican. Theme by Giulio Fidente on github.