We have a number of CloudLinux based cPanel servers using the NGINX reverse proxy. Of late, NGINX seems to fail every day at random times on most of the servers. Obviously websites go down during this period of time until it automagically restarts a couple of minutes later. It seems to happen daily. Anyone else running into a similar issue? We're at a point now to simply disable it as the benefits are too little risking sites going down daily.
Hey there! I haven't heard of similar reports of this issue, so it might be best to create a ticket so our team can take a look at one of the machines having the problem.
We have the same problem since at least one or two months. It happens only on the servers that we have installed NGINX caching, I don't remember that happens on servers without NGINX Caching. WHM versions 106.0.10 and 102.0.25
The mail notification when it fails:
The mail notification when it recovers:
The mail notification when it fails:
Salida sin procesar de la comprobación del servicio | The 'nginx' service passed the check: nginx (nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf) is running as root with PID 1113080 (systemd+/proc check method). |
|---|---|
Registro de inicio | nov 22 10:25:08 my.server.com systemd[1]: Reloading nginx - high performance web server. nov 22 10:25:08 my.server.com systemd[1]: Reloaded nginx - high performance web server. nov 22 10:25:18 my.server.com systemd[1]: Reloading nginx - high performance web server. nov 22 10:25:19 my.server.com systemd[1]: Reloaded nginx - high performance web server. nov 22 10:25:29 my.server.com systemd[1]: Reloading nginx - high performance web server. nov 22 10:25:29 my.server.com systemd[1]: Reloaded nginx - high performance web server. nov 22 10:25:38 my.server.com systemd[1]: Reloading nginx - high performance web server. nov 22 10:25:38 my.server.com systemd[1]: Reloaded nginx - high performance web server. nov 22 10:29:50 my.server.com systemd[1]: Reloading nginx - high performance web server. nov 22 10:29:50 my.server.com systemd[1]: Reloaded nginx - high performance web server. |
The mail notification when it recovers:
Salida sin procesar de la comprobación del servicio | The 'nginx' service passed the check: nginx (nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf) is running as root with PID 2488291 (systemd+/proc check method). |
|---|---|
Registro de inicio | nov 22 10:44:49 my.server.com systemd[1]: Starting nginx - high performance web server... nov 22 10:44:49 my.server.com nginx[2488229]: nginx: [warn] could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 1024 or server_names_hash_bucket_size: 128; ignoring server_names_hash_bucket_size nov 22 10:44:49 my.server.com nginx[2488229]: nginx: [warn] could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 1024 or server_names_hash_bucket_size: 128; ignoring server_names_hash_bucket_size nov 22 10:44:49 my.server.com nginx[2488229]: nginx: [warn] could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 1024 or server_names_hash_bucket_size: 128; ignoring server_names_hash_bucket_size nov 22 10:44:49 my.server.com nginx[2488229]: nginx: [warn] could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 1024 or server_names_hash_bucket_size: 128; ignoring server_names_hash_bucket_size nov 22 10:44:49 my.server.com systemd[1]: Started nginx - high performance web server. nov 22 10:58:31 my.server.com systemd[1]: Reloading nginx - high performance web server. nov 22 10:58:31 my.server.com systemd[1]: Reloaded nginx - high performance web server. |
The ticket number is #94505987 , I think the answer can solve the warning message, but i think it will not resolve the random outages. However, I will inform you in the ticket. Thank you so much.
I see our team was able to create case EA-11069 with our developers to look into this for you. We're working on this now, and it sounds like we are going to raise the open file limit for Nginx to resolve this issue in the future. I'll post an update as soon as I have more details to share.
Until we release that fix, you can adjust the value manually using the details here:
Until we release that fix, you can adjust the value manually using the details here:
Seems that didn't crash anymore, thanks to that easy solution. However, it's interesting if cPanel implements the fix in next updates.
Thank you so much.
Thank you so much.
Glad that the issue is solved. You could check for this tag EA-11069 in the next update change logs Change Logs | cPanel & WHM Documentation to confirm the fix is pushed in the updates.
I was having several issues when I enabled NGINX and my WordPress website was very slow to open. It was necessary to Flush Cache and clear everything manually, several times daily. I was thinking about creating a cronjob to force the Nginx cache flush to run about every hour. I got three of my dedicated server running NGINX but with some limitations by disabling some websites and keeping it enabled for others.
After a few days, I decided to completely remove NGINX back to regular Apache on one of the dedicated servers.
Some of my websites use Apache for password protection login pages and for those I had to completely remove NGINX for the website to work again.
Talking about WordPress websites is when the headache starts !!! some website works perfectly and others go offline several times a day and with a very slow loading time.
So, NGINX is good and bad at the same time !!! my viewpoint and opinion ; )
I hope NGINX and Apache hold hands and work in harmony on future updates.
After a few days, I decided to completely remove NGINX back to regular Apache on one of the dedicated servers.
Some of my websites use Apache for password protection login pages and for those I had to completely remove NGINX for the website to work again.
Talking about WordPress websites is when the headache starts !!! some website works perfectly and others go offline several times a day and with a very slow loading time.
So, NGINX is good and bad at the same time !!! my viewpoint and opinion ; )
I hope NGINX and Apache hold hands and work in harmony on future updates.
We pushed the update that resolved this on December 7, which you can see here:
docs.cpanel.net
EasyApache 4 Change Log 2022 | cPanel & WHM Documentation
EasyApache 4 does not use versioning and organizes changes by date only.
docs.cpanel.net