Skip to main content
We are aware of an issue with a recent Apache update that causes proxied sites to return a "421 Misdirected Request" error. Please see the following article for more information and updates:
Websites show 421 Misdirected Request error while using EA Nginx

EasyApache PHP config file not found: /etc/cpanel/ea4/php.conf

Comments

6 comments

  • DavidN.
    Hello, Would you mind opening a support ticket about this? cPanel Customer Portal My first guess is that the affected user is using jailshell (or no shell access) or is under CloudLinux' CageFS, and don't have access to that file. It could also be that there is some difference in the environment; the environment of cron jobs is substantially different from that of the command line. It could also be something totally different. As a workaround, you might have your user execute the cron job via web request rather than from the command line, with wget -O
    0
  • opt2bout
    Hello, Would you mind opening a support ticket about this? cPanel Customer Portal My first guess is that the affected user is using jailshell (or no shell access) or is under CloudLinux' CageFS, and don't have access to that file. It could also be that there is some difference in the environment; the environment of cron jobs is substantially different from that of the command line. It could also be something totally different. As a workaround, you might have your user execute the cron job via web request rather than from the command line, with wget -O
    0
  • JacobPerkins
    Hi, As an update, we've opened case CPANEL-3680 and we're working on getting a fix in ASAP. Thanks!
    0
  • chrisgrigg
    This is a huge issue and has caused a big issue with billing and a lot of other problems on my server with WHMCS and my clients are having issues as well.
    0
  • JacobPerkins
    Morning, This issue was fixed in v54, and the fix is in v56 and v58. Are you still getting errors?
    0
  • opt2bout
    Morning, This issue was fixed in v54, and the fix is in v56 and v58. Are you still getting errors?

    I can confirm that this issue was resolved way back just after I opened the thread!
    0

Please sign in to leave a comment.