NPMplus: [warn] Could not build optimal server

Seeing my console logs I am getting this message, I know that its a WARN message, but any info on how to fix this or why i am getting this would be grateful!

[Nginx    ] › ℹ  info      Reloading Nginx
[Global   ] › ⬤  debug     CMD: nginx -s reload
[Global   ] › ⬤  debug     CMD: nginx -tq
[Global   ] › ⬤  debug     CMD: nginxbeautifier -s 4 /data/nginx/proxy_host/121.conf
[Global   ] › ⬤  debug     CMD: certbot-ocsp-fetcher.sh -c /data/tls/certbot/live -o /data/tls/certbot/live --no-reload-webserver --quiet
[Global   ] › ⬤  debug     CMD: nginx -tq
2025/03/23 00:47:55 [warn] 4908#4908: could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size
2025/03/23 00:47:55 [warn] 4908#4908: could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size
2025/03/23 00:47:55 [warn] 4908#4908: could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size
2025/03/23 00:47:55 [warn] 4908#4908: could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size
2025/03/23 00:47:55 [warn] 4908#4908: could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size
2025/03/23 00:47:55 [warn] 4908#4908: could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 30 (16 by maintainers)

Most upvoted comments

Setting it to 0 means that the full before needs to be buffered to ram and if some uploads or downloads a file with multiple gigabytes…I hope you have enough ram… (hope this explains why I will not do this change), but note: disabling buffering may not work when using crowdsec

I think then the reason is that your have 130 hosts, I will increase the hash sizes with the next release