pixie
pixie copied to clipboard
pixie-io
server_names_hash_bucket_size too low
Describe the bug When deploying self-hosted pixie and if you set a very long domain name, you get the following error in the cloud-proxy-server container:
[emerg] 8#8: could not build server_names_hash, you should increase server_names_hash_bucket_size: 64
nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 64
To Reproduce Set PL_DOMAIN_NAME to a very long domain name (e.g. very.very.long.domain.name.used.in.this.example.org) and see cloud-proxy-server container crash.
Expected behavior It doesn't crash
Screenshots If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.
Logs [emerg] 8#8: could not build server_names_hash, you should increase server_names_hash_bucket_size: 64 nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 64
Additional context I tried to set the env var SERVER_NAMES_HASH_BUCKET_SIZE to 128, but the env var didn't get apply to nginx.
The workaround is to add this line "server_names_hash_bucket_size 128;" to the http context of the nginx.conf file then mount it to the cloud proxy pod.
But what do you think about having it directly to the file, like that people using long domain name won't have to workaround like that, I can PR the changes if you want? or create a new file just for it and include it in the nginx config?
@Sindvero - thanks for reporting back with the solution. We'd be happy to accept a PR with this modification!
Thanks for identifying the fix. Can you make a PR it?
On Wed, Sep 14 2022 at 8:27 PM, Aurelien < @.*** > wrote:
The workaround is to add this line "server_names_hash_bucket_size 128;" to the http context of the nginx.conf file then mount it to the cloud proxy pod.
But what do you think about having it directly to the file, like that people using long domain name won't have to workaround like that, I can PR the changes if you want? or create a new file just for it and include it in the nginx config?
— Reply to this email directly, view it on GitHub ( https://github.com/pixie-io/pixie/issues/590#issuecomment-1247534519 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAUJT3RI4UBNR6YCRHEQTX3V6KJQLANCNFSM6AAAAAAQLT6DNE ). You are receiving this because you are subscribed to this thread. Message ID: <pixie-io/pixie/issues/590/1247534519 @ github. com>