• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue nginx "worker_connections are not enough" causing HTTP 500 error pages

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 9.8
Plesk version and microupdate number
18.0.80#5
Hi, I'm seeing thousands of nginx errors in proxy_error_log like:
[alert] 8372#0: *40621122 1024 worker_connections are not enough while connecting to upstream, client: ....

This is new. Before upgrading from AlmaLinux 8.10 to 9.8, users never reported this kind of issue.
The server runs AlmaLinux 9.8 with Plesk Obsidian 18.0.80 #5 and has 24 CPU cores.

Current nginx settings:
/etc/nginx/nginx.conf: worker_processes 1;
/etc/nginx/nginx.conf: worker_connections 1024;
/etc/nginx/ulimit.global_params: worker_rlimit_nofile 40000;

/etc/nginx/ulimit.global_params is from from 2020-12-15
/etc/nginx/nginx.conf is dated 2026-08-10. This date is a bit strange, as there was no system or Plesk update on that day.

Code:
# systemctl show nginx -p LimitNOFILE
LimitNOFILE=4096

# grep -i "Max open files" /proc/$(cat/run/nginx.pid)/limits
Max open files            4096                 4096                 files

What is the Plesk-supported and update-safe way to increase nginx capacity here?
In particular:
  • Is worker_processes 1 expected on a 24-core server?
  • Should worker_processes be set to auto?
  • Should worker_connections be increased?
  • Should LimitNOFILE also be increased?
Thanks.
 
Additional information:

Code:
# stat /etc/nginx/nginx.conf
Modify: 2026-08-10 14:58:55.000000000 +0200
Change: 2026-08-15 03:46:22.269847289 +0200
Birth:  2026-08-05 14:20:54.922420007 +0200

The installed package is:
Code:
# rpm -qf /etc/nginx/nginx.conf
sw-nginx-1.30.4.1-2.redhat.9+p18.0.80.3+t260813.2046.x86_64

It was installed on August 15:
Code:
# rpm -q --qf '%{NAME} %{VERSION}-%{RELEASE} installed: %{INSTALLTIME:date}\n' \
  $(rpm -qf /etc/nginx/nginx.conf)

sw-nginx 1.30.4.1-2.redhat.9+p18.0.80.3+t260813.2046 installed: Sat 15 Aug 2026 03:46:22 AM CEST
Also, rpm -V reports no modification of /etc/nginx/nginx.conf, so the current file matches the one shipped by the Plesk sw-nginx package.

Timeline:
  • 2026-08-05: AlmaLinux 8 → 9 upgrade
  • 2026-08-15: Plesk update to 18.0.80 #3 / installation of the above sw-nginx package

I found an additional important detail.

There is an /etc/nginx/nginx.conf.rpmsave created during the AlmaLinux 8 → 9 upgrade on August 5:
Code:
Modify: 2020-08-08 18:07:47
Change: 2026-08-05 13:56:27

My previous nginx configuration contained "worker_processes auto;" not "worker_processes 1;"

So during the AlmaLinux 8 → 9 upgrade, my nginx.conf was saved as "nginx.conf.rpmsave" and the package-provided configuration restored worker_processes 1;. This would also explain why the worker_connections are not enough issue only appeared after the OS upgrade.

How can I set this to "worker_processes auto;" so that some Plesk update doesn't change it again?
 
The problem is that it’s really hard to get a timely response on GitHub. It’s honestly quite frustrating to discover, bit by bit, how many things the upgrade has broken or caused to stop working properly.

Today I’ve now also that ModSecurity apparently hasn’t been working correctly since the upgrade either. At this point, it’s becoming really frustrating.
 
Back
Top