Docker nginx attachment - getting 413 #5198
Replies: 3 comments
-
I just realized that the |
Beta Was this translation helpful? Give feedback.
-
I just tested with the Docker image v1.2.18 and I am able to upload files up to the limit of 32MB. However, I can see on your screenshot that you have Nginx 1.19.3, but the Docker image comes with Nginx 1.18.0 which makes me think that you have a reverse proxy in front of the Kanboard container. This Nginx has probably different settings that the one bundled into the Docker image. |
Beta Was this translation helpful? Give feedback.
-
Ah I did not even think about that. Thanks for catching that, going to go down that route now! Closing this issue for now. |
Beta Was this translation helpful? Give feedback.
-
Actual behaviour
Using the docker image I am not able to attach anything over 1M in size. I am able to upload files that are ~950K, I was able to zip a failing 1M file to just under 1M and get it uploaded like that. I checked the size settings per the documentation, and they both look ok.
Logging in to cli via
docker exec
(I am not sure how to check the running config of nginx like with php so I am assuming that the setting is either incorrect, ignored, overridden)
Expected behaviour
The PHP settings and Nginx settings look like they are set to 32M already. I would expect to be able to upload an attachment up to 32M.
Steps to reproduce
Screenshots
Logs
Logs actually do not show any errors (i dont think it is generating an error, just a legitimate error code for the user). I stopped and started nginx without the daemon mode settings (
nginx -g "daemon off;"
) so that the logs would go directly to the console and I only seen some PHP constant already defined errors which is fine. They are related to the database and my guess is that these just exist in the docker verison.Configuration
Beta Was this translation helpful? Give feedback.
All reactions