![]() User to run XO-server as By default, XO-server runs as root. If you need to do any configuration on the system itself (firewall, SSH), check the XOA dedicated section. I have two nginx containers, but one it the Nginx-proxy that handles all network. The configuration file is located at /etc/xo-server/config.toml. ![]() It didn't appear on Nginx logs of the Nextcloud container docker-compose I deployed. That message only appeared on Nginx-proxy container logs. 917,6 +917,7 client intended to send too large body: O bytes. So I just google it and found the easy solution! List: nginx Subject: Re: Bug: custom errorpage doesnt work for HTTP 413 (content. Haven't touch the Nginx-proxy container that provides network to several other containĮDIT-2 SOLVED!! I did solve it because I found this message on the container logs belonging to Nginx-proxy: "client intended to send too large body". Increasing HTTP post file upload limit for Nginx and PHP (WordPress). ![]() ![]() How could I check that? I have a Nginx-proxy container that gives the external network to Nextcloud and other containers, and then a regular Nginx container to configure just Nextcloud.Įdit: Should I set the client_max_body_size on the nginx-proxy container as well? I have just set it on individual nginx container belonging to Nextcloud. Check Nginx Configuration And Restart Next, check our configuration by running sudo nginx -t If it says syntax is ok then we are ready to restart our Nginx. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |