You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the problem that every time i start the containers the proxy sets "client_max_body_size" to the following: client_max_body_size ;
wich then causes the following error nginx: [emerg] invalid number of arguments in "client_max_body_size" directive in /etc/nginx/nginx.conf:12
Plane is running on a synology rs1219+ inside docker
Steps to reproduce
Create the installation with docker-compose
Start the project/stack
proxy will crash
Open proxy logs
There is the error
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
latest (0.23.1)
The text was updated successfully, but these errors were encountered:
mario-fox
changed the title
[bug]: plane-proxy remove client_max_body_size on startup
[bug]: plane-proxy removes client_max_body_size on startup from nginx.conf
Nov 28, 2024
Hey @mario-fox,
Could you please check the value of the FILE_SIZE_LIMIT environment variable in the proxy container?
The issue might be caused by the docker-entrypoint.sh script. This script is responsible for performing envsubs inside the nginx.conf file. Verifying the value of FILE_SIZE_LIMIT and restarting the proxy container could help resolve the problem.
Is there an existing issue for this?
Current behavior
I have the problem that every time i start the containers the proxy sets "client_max_body_size" to the following:
client_max_body_size ;
wich then causes the following error
nginx: [emerg] invalid number of arguments in "client_max_body_size" directive in /etc/nginx/nginx.conf:12
Plane is running on a synology rs1219+ inside docker
Steps to reproduce
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
latest (0.23.1)
The text was updated successfully, but these errors were encountered: