Nginx Plugin Changes In Web Interface Aren't Working

Started by ensal, January 31, 2022, 10:35:00 PM

Previous topic - Next topic
Yeah for some reason setting it within the web interface it just won't set it to 5000m max body upload but editing it from the actual nginx.conf file does work. So not sure what the new issue is for that since here's the result from trying to set it from the web interface

2022-02-05T12:20:59 configd.py[15718] [72c5f666-a604-4786-a9b6-42d15ecbc8ca] Script action stderr returned "b'[05-Feb-2022 12:20:59] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful\n\n[05-Feb-2022 12:20:59] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful\n\nnginx: the configuration file /usr/local/etc/nginx/nginx.co'"

QuoteScript action stderr returned "b'[05-Feb-2022 12:20:59] NOTICE:
yep, such a line gets into the backend log when the configuration is successfully checked.

it seems that the behavior of the script has changed a little by nginx some time ago and now requires an additional flag (nginx_reload_quiet) so that the configuration check is silent
https://github.com/opnsense/ports/commit/5a05b2cf815d412adc73610ebceca0ca1cb762a1#diff-98eb80df33697b23b19c8b6753779cc7294e63ba9f94ed847661fcf095a94eb6R20

i will try and make pr if it helps

back to the question: I tried on 21.7.8 and the  'client_max_body_size 5000m;' directive is set successfully in the server and location section

wonder what you mentioned:
Quotewhen hitting Apply it's setting it back to 200m in my nginx.conf
but this is http block (and its no way to change it in gui). server and location blocks do not contain this directive unless they are set in the GUI. sorry, did you check server and location blocks after applying gui parameters?

Just to make sure I follow this. If I set it in the locations then I don't need to set it in the http server section? Sadly I don't have any larger files to test against it at the moment.
Next time I have a large file to upload to my Nextcloud that this is ultimately being set for I can post about it again.

QuoteJust to make sure I follow this.
if you want to apply this max size to whole server then you can cet it at server level. if you want to keep default limit (200M) for server and increase it for just one dir then you can set it at location level.
that is:
Quoteset it in the locations then I don't need to set it in the http server section?
yes  ;)
QuoteI don't have any larger files to test against
https://pinetools.com/random-file-generator  :D