Bug settings do not work for : Nginx warning optimal variables_hash?

[RamSense]

I'm running the latest OPNsense and Nginx plugin:

OPNsense 25.1-amd64
FreeBSD 14.2-RELEASE
OpenSSL 3.0.15

Nginx log shows this warning:
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

I tried changing the setting, Nginx - configuration - general settings - global HTTP settings:
Hash Bucket Size : 128 and 256
Server Names Hash Max Size : 1024, 2048 and 4096

But all did not seem to work, and the warning remains the same. It looks like this gui setting does not work (anymore?) or am I changing the wrong settings?

Others having this warning also? How to fix?

[RamSense]

Can someone confirm if this setting in Nginx is broken / Bug? Nginx - configuration - general settings - global HTTP settings: [Hash Bucket Size] and [Server Names Hash Max Size] don't work?

[RamSense]

Is there someone with nginx willing to confirm that the Nginx - configuration - general settings - global HTTP settings: [Hash Bucket Size] and [Server Names Hash Max Size] don't work? and report the bug. Thank you in advance

[cookiemonster]

I suggest to not wait for confirmation here, to go ahead and report it. There might not be many nginx users watching the forum.

[RamSense]

I went to cli: 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 4096;
server_names_hash_bucket_size 256;

So it looks like the gui setting is getting in nginx, but the error " 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" remains ??

Why is that? or how cab this be mitigated?