variables_hash_max_size???

[GreenMatter]

OPNsense is the latest 23.7.9 and Nginx runs but doesn't do its job. I keep getting following error in log:

Code Select Expand


nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size

All proxied services are not available through Nginx giving timeout errors in Nginx log.
I don't know exactly when it happened, I can't find anything related to those directives in Nginx config Or any place in gui to edit their values.

Code Select Expand


root@OPNsense:~ # nginx -T | grep hash
nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
server_names_hash_max_size 1024;
server_names_hash_bucket_size 64;
ip_hash;
ip_hash;
ip_hash;
           hash $remote_addr consistent;
           hash $remote_addr consistent;
           hash $remote_addr consistent;
           hash $remote_addr consistent;
           hash $remote_addr consistent;

Changing server names hash doesn't affect this issue:

Code Select Expand


root@OPNsense:~ # nginx -T | grep hash
nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
server_names_hash_max_size 1536;
server_names_hash_bucket_size 64;
ip_hash;
ip_hash;
ip_hash;
           hash $remote_addr consistent;
           hash $remote_addr consistent;
           hash $remote_addr consistent;
           hash $remote_addr consistent;
           hash $remote_addr consistent;



What could be the reason of this error?