I have two nginx containers, but one it the Nginx-proxy that handles all network. 0, client intended to send too large chunked body: O+O bytes. It didn't appear on Nginx logs of the Nextcloud container docker-compose I deployed. Copyright (C) Igor Sysoev Copyright (C) Nginx, Inc. How to fix client intended to send too large body error in Nginx. That message only appeared on Nginx-proxy container logs. So I just google it and found the easy solution! 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". 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |