Issue SNI error

[thinkingcap]

Server operating system version

Ubuntu 24.04

Plesk version and microupdate number

Plesk Obsidian 18.0.71

Am getting this error across all sites on one server
"The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection"
Haven't made any changes in last 24hrs.

Any idea what would cause this?

 

[thinkingcap]

Its being looked at by Plesk

echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;" > /etc/nginx/conf.d/fixssl.conf && service nginx restart

Is the work around.

 

[jpveen]

Thanks for sharing!
Suddenly without any change my Ubuntu server with Plesk was not serving any website. This workaround fixed this very quickly.

Running config: Ubuntu 22.04.5 LTS. Plesk version: Plesk Obsidian 18.0.70 Update #2 Web Host Edition
Full error message i got on all sites:
Misdirected Request
The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection.

 

[kristobal1969]

exact same problem as jpveen and same configuration !!
the problem is that I can not access with ssh from my computer. I used to access not so long ago. Only solution is using ssh terminal in plesk (in tools and settings).
Is the patch safe ?

 

[Harm Jakob Tolsma]

Its being looked at by Plesk

echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;" > /etc/nginx/conf.d/fixssl.conf && service nginx restart

Is the work around.

Thanks for sharing!

 

[kristobal1969]

I applied the patch and my sites work again. Thanks but this is not the good periode having problems (holidays).

 

[wstudio]

Thank you !

 

[Sebahat.hadzhi]

Everyone, the issue occurred due to the latest Apache update with the CVE-2025-23048 security fix. By default Nginx doesn’t pass server name through SNI when establishing a connection with the proxied HTTPS server, which interferes with the update. The official workaround is the one you already found in:

• https://support.plesk.com/hc/en-us/...-recent-Apache-update-421-Misdirected-Request

In the meantime, our team is working on a hotfix that will be released soon.

 

[zoltankiraly]

Even after applying the command line fix above, I seem to have some issues with my wordpress multisite's back-end. Could it be related?

 

[rjensen]

@Sebahat.hadzhi

This is the second time this month that a Plesk update broke the webserver. DO BETTER!

 

[Sebahat.hadzhi]

Everyone, our team provided one more directive which needs to be added into nginx config to address the issue. The article is updated, but I am also attaching it here:

echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" /etc/nginx/conf.d/fixssl.conf && service nginx restart

 

[Sebahat.hadzhi]

This is the second time this month that a Plesk update broke the webserver. DO BETTER!

It isn't necessarily Plesk that broke the webserver. The issue occurred due to the latest Apache update introduced for Ubuntu. It impacted the way in which proxy Nginx requests are handled.