[URGENT] 421 Misdirected Request
All my customers are reporting this issue since this morning.
I searched around and it could be related to the last Apache's update (2.4.62).
For instance:
1) NO, it's not related to Cloudflare (disabling it doesn't fix the issue at all)
2) NO, running this command as fix DID NOT HELP:
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
3) NO, running
dnf update
as shown here: https://support.cpanel.net/hc/en-us/articles/33553346450455-Websites-show-421-Misdirected-Request-error-while-using-EA-Nginx does not help.
4) NO, disabling http/2 does not help as well
5) NO, disabling NGINX Manager does not help as well
6) The only temporary solution appears to be completely uninstalling NGINX reverse proxy, which can't be really called a solution as it will negatively impact the performance of every website.
I tried everything I could, and nothing worked. Everyone gets random and frequent "421 Misdirect Request" errors while browsing. Please provide a resolution as soon as possible as I'm sure it's a global issue affecting everyone since the last update, thank you.
-
i am having the exact same issue after the server update itself during this night
0 -
This is happening with us aswell - the update must happened overnight must have caused this.
0 -
This is supposed to resolve the issue (temp rollback) until a fix can be added:
It doesn't work for me. The rollback was done (to ea-apache24-2.4.63-2.6.2), nginx cache cleared for all, but the issue persisted. I tried apache restart, nginx restart, still no good.
Uninstalling nginx on the affected servers seems to be the only solution I can find.
cPRex can you comment on the status of a fix for this, and on why this workaround doesn't work as described? (Does it require a further rollback?)
-1 -
Thanks PeteS, but yours is actually another temporary workaround and not a solution.
1 -
Yes, obviously, but it was preferable to uninstalling nginx (which I had already discovered as a workaround), but after posting I discovered it doesn't work. *eyeroll*
I edited it with that info...
1 -
https://support.cpanel.net/hc/en-us/articles/33553346450455-Websites-show-421-Misdirected-Request-error-while-using-EA-Nginx doesn't work for me either. Yum throws up a lot of errors . For example:
Error: Package: ea-apache24-mod_headers-2.4.64-1.1.1.cpanel.x86_64 (@EA4)
Requires: ea-apache24 = 2.4.64-1.1.1.cpanel
Removing: ea-apache24-2.4.64-1.1.1.cpanel.x86_64 (@EA4)
ea-apache24 = 2.4.64-1.1.1.cpanel
Downgraded By: ea-apache24-2.4.63-2.6.2.cpanel.x86_64 (EA4)
ea-apache24 = 2.4.63-2.6.2.cpanel
Available: ea-apache24-2.4.63-1.4.10.cpanel.x86_64 (EA4)
ea-apache24 = 2.4.63-1.4.10.cpanel
Available: ea-apache24-2.4.63-1.4.11.cpanel.x86_64 (EA4)
ea-apache24 = 2.4.63-1.4.11.cpanel
Available: ea-apache24-2.4.63-2.6.1.cpanel.x86_64 (EA4)
ea-apache24 = 2.4.63-2.6.1.cpanel0 -
Having major issues with this!
0 -
Same issue here, workaround not working and support reacting slow.
0 -
Same issue here the fix proposed on the Plesk support chat didnt help me, tried disabling nginx-http2 with no help, hopefully someone has a solution or maybe cPanel with release a patch for this.
0 -
still not solved this issue if there any solution please share the steps.?
0 -
Similar issue in Plesk yesterday. managed to fix using below command in Plesk as well as cPanel
yum -y upgrade && yum -y update
/scripts/upcp --force
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
worked fine for me.
0 -
Umang Parekh it doesn't work for me on cPanel.
The error is random
1 -
I tried the tutorial but it didn't work
I have two servers using WHM/Cpanel and i noticed one thing is
WHM/Cpanel using OS AlmaLinux v8.10.0 works fine
WHM/Cpanel using OS AlmaLinux v9.6.0 crashes randomlyCould this be related to OpenSSL in OS ?
0 -
mime is centos 7 but got problem Binh Chon
0 -
how to fix ubuntu 22 + WHM.? still no patches
0 -
OpenSSL of OS AlmaLinux v8.10.0
[root@xxxx~]# nginx -V
nginx version: nginx/1.26.3
built by gcc 8.5.0 20210514 (Red Hat 8.5.0-20) (GCC)
built with OpenSSL 1.1.1k FIPS 25 Mar 2021
TLS SNI support enabledOpenSSL of AlmaLinux v9.6.0
[root@yyyy~]# nginx -V
nginx version: nginx/1.26.3
built by gcc 11.4.1 20230605 (Red Hat 11.4.1-2) (GCC)
built with OpenSSL 3.0.7 1 Nov 2022 (running with OpenSSL 3.2.2 4 Jun 2024)
TLS SNI support enabledAll configurations of the 2 servers are the same, the only difference is OpenSSL.
0 -
We pay a fair amount for the license every month, but if there is a problem like this, the response is mediocre and even after a day no fix is available.
1 -
Yeah, I agree, Marvin. We pay for arguably one of the most — if not the most — expensive web hosting panels precisely so that issues like this don't make it into production. That cost should cover proper testing, solid development oversight, and rapid incident response when things do slip through.
At this scale, you’d expect a company of this size to throw ten engineers at the problem at 4 a.m., triage it, and ship a hotfix. Instead, we've got thousands of sites stranded, no official communication, and a silent thread full of frustrated users — while the software vendor stays quiet.
Compare that to Cloudflare, who hit a major issue a few weeks ago — fixed it in an hour, and gave a transparent postmortem. The contrast in accountability and transparency here is telling — and frankly, disappointing.
2 -
Just received a ticket response from a cPanel engineer (name removed — not their fault, they're clearly getting the short end of the stick here). But this was the advice I was given just now:
cPanel Support Ticket Response
I understand you are encountering 421 errors after a recent reboot. I see the server is running Apache 2.4.64, which was recently updated to address some CVEs. Unfortunately, we found this causes 421 errors with our Nginx implementation, as described below. I recommend following this article to receive an update when a fix has been published to the cPanel software.
Websites show "421 Misdirected Request" error while using EA-Nginx
While there is no current workaround, some users have had luck by downgrading the ea-apache24 package.
dnf downgrade ea-apache24
If downgrading Apache does not resolve the issue, the best option would be to remove Nginx from WHM >> Software >> NGINX Manager until a fix has been published.
If you have any more questions or concerns, please don't hesitate to let us know. It’s been a pleasure working with you on this issue, and I hope you are satisfied with the experience!They're suggesting we completely remove NGINX from production servers as a "solution" — as if that's some trivial toggle. I’ve got dozens of custom NGINX rules, tailored caching and buffering configurations, and logs full of vital NGINX-level diagnostics — all of which would be disrupted by this kind of knee-jerk removal.
This isn't a workaround — it’s a surgical strike with a sledgehammer.
And let’s be clear: asking sysadmins to downgrade Apache or gut NGINX entirely without a clean rollback path is a risky move that could lead to even worse instability or broken configurations, especially for users managing live multi-site environments.
We’re paying for a premium, enterprise-tier product. The expectation is that mission-critical bugs like this get triaged, transparently communicated, and hotpatched quickly — not brushed off with a shrug and an “uninstall the problem” message.
Beyond frustrated right now.
2 -
Already downgraded apache this morning and disabled nginx for a couple domains but the problem still exists.
1 -
We performed the downgrade on two servers, but unfortunately it had no effect. Why is it so difficult to find a quick solution to this issue? Also, how is this even possible given that we're on the Release tier? What happened in the Edge and Current tiers?
1 -
So true this is a f'up on epic proportions! The silence is deafening!
1 -
also, if you purchase a license from their partners, like ndchost, you can not ask cpanel for support any more...
cpanel increases the prices a lot for the last a couple of years, just saying
1 -
They updated the workaround with the same info as this morning. But when i disable nginx for websites and downgrade apache the problem still exists. Nothing works
1 -
The 'hotfix' mentioned here https://support.cpanel.net/hc/en-us/articles/33553346450455-Websites-show-421-Misdirected-Request-error-while-using-EA-Nginx doesn't work for me either. There is still random misdirected error :-(
1 -
Hi guys...
We use Engintron and have requested an urgent update due to last night's cPanel update.
"
July 17, 2025 - v2.10
This update resolves a critical issue in the proxying of traffic between Nginx and Apache, after an Apache update by cPanel (system version: Apache/2.4.64 (cPanel)).
If your sites load with a "Misdirected Request" or "421 Misdirected Request" error page, please update to this new release to resolve the issue.
The issue was first spotted on a CentOS 7 server (which apparently got an Apache update by cPanel, although unsupported), then on an AlmaLinux 8 server (still supported by cPanel) and it will most likely cascade to newer releases as well (if it hasn't already), unless cPanel pulls the plug on the update on their end. For context this also occured on the morning of July 17, 2025 on Plesk servers (Plesk and cPanel are owned by the same company for some years now), after a Plesk system upgrade, which indicates possible common development for Apache packages on Plesk and cPanel (and common bugs perhaps…)."
After the update, the problem on our servers has been resolved.
Regards
1 -
this an the last update where they "remove "addonfeatures" directory"... don´t they have some sort of pre-release?? test servers?? or is just an INDIE Software companny? xD
0 -
btw
STABLE 128.0.17 A version that is feature-complete, fully tested, and is in widespread use.
RELEASE (Recommended) 128.0.17 A version that is feature-complete and well tested.
Stable and Release use the same version, and Release witch is recomended says "well tested".. suuuuuure xD0 -
For me it seems to work
I commented out the SNI fixes in
/etc/nginx/conf.d/includes-optional/cpanel-proxy.conf
and then
dnf downgrade ea-apache24
Hope it helps.
0 -
Are you referring to the lines below
# Fix for SNI issue
# proxy_ssl_server_name on;
# proxy_ssl_name $host;
# proxy_ssl_session_reuse off;
I’ve tried that, but the issues persist, also after downgrade ea-apache24.0
Please sign in to leave a comment.
Comments
141 comments