Websites experiencing 421 Misdirected requests after upgrading to CloudLinux's ea-apache24-2.4.64

Update timeline

1. investigating Jul 26, 2025, 10:44 AM UTC

   We are aware of instances where websites on Dedicated or Virtual servers running cPanel and/or Cloudlinux are showing the following error; ``` 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.` ``` The issue is caused by recent updates to Apache introduceing stricter SSL/TLS handling (to address CVEs). Further information can be found via the links below. [Cloudlinux Guide](https://cloudlinux.zendesk.com/hc/en-us/articles/21282870470172-421-Misdirected-Request-Error-After-Recent-ea-apache-Update) [cPanel Guide](https://support.cpanel.net/hc/en-us/articles/33553346450455-Websites-show-421-Misdirected-Request-error-while-using-EA-Nginx-or-other-proxies) [Plesk Guide](https://support.plesk.com/hc/en-us/articles/33500191748887-Websites-hosted-in-Plesk-are-not-accessible-after-a-recent-Apache-update-421-Misdirected-Request) if you have a managed server with us, we have applied a version lock to prevent updates until a fix is released. For any customers seeing this issue and are unable to resolve, or if your service is managed, please do contact our support team for assistance.

2. resolved Jul 28, 2025, 08:24 AM UTC

   Cloudlinux have released a fix for the issue. >The last update >Our developers have identified the issue and pushed the fix. To apply the fix, run the following command: ~~~ yum update ea-apache24* ea-nginx --enablerepo=cl-ea4-testing ~~~ >For servers using Imunify360 with Hardened PHP but not using CloudLinux, use the following command instead: ~~~ yum update ea-apache24* ea-nginx --enablerepo=imunify360-ea-php-hardened-beta ~~~