[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.
-
Great..
Meanwhile I had to downgrade again.
I see this will be my daily "to-do before breakfast" task now, downgrading every single fricking day.
What an extreme lack of service....
0 -
So we had this issue a few weeks ago and it was solved by running this command:
yum update ea-apache24* ea-nginx --enablerepo=cl-ea4-testing
It seems to work but Today I checked our server and the problem is back. Great! It's a legacy server, I guess I will simply have to downgrade Apache now?!0 -
So this command:
Yum downgrade ea-apache24
Is not working, so we are currently stuck with broken upgrade I guess. I really don't have time to deal with this sh*t
0 -
dnf downgrade ea-apache24
0 -
Any known workaround for a Cloudlinux 7/CentOS 7 legacy server. The server is running this Apache version now:
Apache/2.4.65 (cPanel) OpenSSL/1.1.1w Apache mod_bwlimited/1.4
I have no problem downgrading Apache if that's what it takes, the server will be decommissioned in January but I need a solution now. TheYum downgrade ea-apache24
command does not work but perhaps there is a better way?
0 -
Hi,
Today ea-nginx was updated in some servers to version
ea-nginx-1.26.3-15and the error came back, even though Apache was already downgraded and version-locked.This means that in order to “wait for the definitive fix” you actually need to version-lock both Apache and Nginx.
Here are the commands you can use. They will check if the installed version is affected and, if so, downgrade it. In any case, they will apply the version lock:
httpd -V | grep "2.4.64\|2.4.65" && (yum downgrade ea-apache24 -y; yum versionlock add ea-apache24) || (yum versionlock add ea-apache24)rpm -qa | grep "ea-nginx-1.26.3-15" && (yum downgrade ea-nginx -y; yum versionlock add ea-nginx) || (yum versionlock add ea-nginx)0 -
I would *strongly* encourage everyone that is still experiencing this issue to contact CloudLinux directly about the problem.
0 -
I tried downgrading to version 2.4.63-2 on Cloudlinux 7 but there are several apache mods that spit error then, due to dependencies. I don't want to skip the dependencies. What is the best way to force the downgrade to to it for all the mods, not just the apache itself? This is the command I was using:
yum downgrade ea-apache24-2.4.63-2.el7.cloudlinux0 -
tomfra Here is the command we used, which took care of all the dependencies:
yum downgrade ea-apache24-2.4.63
0 -
Does not work, I get errors like these then:
Error: Package: 1:ea-apache24-mod_remoteip-2.4.65-3.el7.cloudlinux.x86_64 (@cloudlinux-ea4-rollout-13)
Requires: ea-apache24 = 1:2.4.65-3.el7.cloudlinux0 -
To contact Cloudlinux
https://cloudlinux.zendesk.com/hc/en-us/requests/new
They will display this article before you finish your contact request.
The "solution" that we already know does not work.
I posted a ticket to Cloudlinux with a link to this thread and encourage others to do the same.
0 -
Richard Brandson - exactly!
tomfra - have you also contacted CloudLinux?
0 -
Just to make it clear: The issue is not that the websites on the server doesn't work, the problem is that many users can not connect to the websites and get a 421 error when they try.
Its not feasible to contact every single user manually (how?) and ask them what they are connecting with and ask them to upgrade. And even doing that doesn't guarantee that they will be able to connect either.
So the solution must be server side.
Maybe the best solution is to look for an alternative to Cloudlinux that works?
0 -
WHM Upgrades Apache every night at aprox 3, and I dont want to versionlock, I want to see if they fix the issue, but until then, if I create a cron job as root to downgrade every day, will it potentially be problematic? Or would it be fine in your opinion?
0 4 * * * dnf downgrade ea-apache24
0 -
cPRex: I tried submitting a support ticket with with CloudLinux but they require some CLN username which I do not have.
But honestly, I am not interested in their "solutions". They solved it a month ago, then broke it again. Don't trust them. The server has some 4 months of life anyway. At this point, I simply want to downgrade Apache to 2.4.6.3
But when I try it, I get a lot of dependencies errors.0 -
tomfrain the CLN username field, put the name of your whm/cpanel license provider if you dont have a username.
0 -
I just received a reply from Cloudlinux
(CloudLinux)
26 Aug 2025, 19:52 EEST
Hello,
Thank you for reaching out and for sharing your experience with this issue. We completely understand how frustrating it must be to face recurring problems with the 421 Misdirected Request error and to have to rely on downgrading as a workaround.
Our development team is actively investigating this bug under the internal task EA4D-694. At this time, there is unfortunately no ETA for the permanent fix, but please rest assured it is being treated with priority.
As a temporary measure, we recommend adding the affected packages to your exclude list so that they are not updated automatically until the fix is released. This will help avoid having to repeatedly downgrade. Please follow the next step:
- Edit
/etc/yum.confwith your preferred editor. - Locate (or add) the
exclude=line. -
Append the following packages:
exclude=ea-apache24* ea-nginx*(include
ea-nginx*only if Nginx is in use on your system) - Save the file.
After this, futureyum updateor automatic updates will skip these packages, preventing the 421 error from recurring until the permanent fix is released.
We truly appreciate your patience while our developers work on this.0 - Edit
-
That's all I've heard on my end as well.
0 -
The "temp solution" suggested by Cloudlinux did not work at all.
WHM did update apache anyway, it made the websites giving errors again, but the "fix" prevented me from downgrading until I edited yum.conf and removed the suggested temp fix again.
So one step forward, two steps back lol...
I am told they are working on it....
0 -
I am surprised you guys are even able to downgrade Apache. I get so many dependency errors it's a no-go for me. Probably Clouldlinux 7 issue.
0 -
Hi,
If you’re still experiencing this issue after upgrading, here’s what worked for me:
After some trial and error, I found that disabling Apache KeepAlive in WHM → Apache Configuration → Global Configuration resolved the problem.
Hope this helps!
0
Please sign in to leave a comment.
Comments
141 comments