• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue 421 Misdirected Request on IP address after Apache update

WiseWill

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
Version 18.0.71 Update #1
Getting this error this the Apache update:

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.



Apache Server at 67.200.200.200 Port 443


If I go to Hosting & DNS under the domain that is set as the default site for the IP address. The default site that was set in tools & settings, ip addresses as the default site.

Then under Hosting & DNS go to nginx settings, then Proxy mode and uncheck proxy mode it works perfectly. If I click Proxy mode it gives me the Misdirected Request error.

Proxy mode has then on the setting:
Nginx proxies requests to Apache. Turn off to stop using Apache.

If I turn off to stop using Apache the issue disappears and if I click to use Apache then the issue is there. This was always working before the Apache update and never had any issues.

All domains were having a 421 error after the Apache update which I noticed 3 hours after Plesk installed it. I ran the fix at https://support.plesk.com/hc/en-us/...-recent-Apache-update-421-Misdirected-Request

Which is the echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf && systemctl restart nginx

It fixed the domain names from having the 421 error, but it never fixed the IP default site from have the posted Misdirected Request error.


I contacted Ionos about the issue and they sent a Plesk ticket in, and Plesk replied it was a Cloudflare issue. Well guess what removing Cloudflare did absolutely nothing. The error was there without Cloudflare. The only thing that fixed the issue was turning off Proxy mode to stop using Apache.

The response I got was it is a firewall issue well I contacted the firewall maker, and they advised to disable the firewall. Guess what shocker no firewall the same exact issue. Color me shocked. Proxy mode checked and bam error. Proxy mode unchecked to disable Apache and wammo no issue.

Plesk and Ionos response it has to be a firewall issue. Well, the issue is there is no firewall and still the same error. What firewall does Plesk want me to use as no firewall enabled doesn't even fix the issue?

This what I got from imunify. Even they know it is a known issue related to Apache, but Ionos and Plesk say it is the non-existent firewall and non- existent Cloudflare at this point.

Thank you for contacting Imunify Support!

We sincerely apologize for the inconvenience you’ve encountered. Please rest assured that we are committed to assisting you and resolving the issue promptly.

The issue misdirected request seems to be related to a known issue related to an Apache update, this is indicated here:
https://support.plesk.com/hc/en-us/articles/33500191748887-Websites-hosted-in-Plesk-are-not-accessible-after-a-recent-Apache-update-421-Misdirected-Request

Could you please clarify if the issue is resolved by applying the steps provided on that article from Plesk?

If not, could you please try disabling Imunify360 to see if resolves the issue?
https://cloudlinux.zendesk.com/hc/en-us/articles/4418850990226-How-can-I-disable-Imunify360-without-uninstalling-it

Looking forward to your update.


Does anyone have a fix for Apache breaking the default site of an IP address in tools & settings/ IP addresses if using Apache is used? Disabling proxy mode in Hosting & DNS/ Apache & nginx which disables Apache fixes the issues. Enabling proxy mode in Hosting & DNS/ Apache & nginx which enables Apache breaks it.

The site the with the domain name works just fine after ran the
  1. echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf && systemctl restart nginx
All domains work fine after having ran that, but the IP address won't work anymore since the Apache update. Anyone knows how to fix this as Ionos and Plesk ticket support have no solutions. So going to the internet to see if anyone else has the fix. Looking for a fix that does require disabling proxy mode to disable Apache.

Thank you for helping with the fix as I have not been able to find it other than to stop using Apache.
 

Attachments

  • Screenshot 2025-07-25 204631.png
    Screenshot 2025-07-25 204631.png
    7.4 KB · Views: 6
  • Screenshot 2025-07-25 205136.png
    Screenshot 2025-07-25 205136.png
    30.7 KB · Views: 6
The IP address is distributed as? Shared or Dedicated
SSL/TLS certificate? default or specified?
Default site? none or domain used
 
Running U20.04LTS and the latest Plesk with the Apache mod applied, the default site set on the (shared) primary IP address (ionos vps) works fine, albeit with an SSL warning as the cert is for the domain name and not the IP. (it's the correct cert and site that opens though). Proxy mode is enabled.

Is your preferred domain (in Hosting) set to www.domain.tld or domain.tld?
 
Back
Top