"File not found." instead of custom 404 file with php-fpm enabled

PeteS

• July 25, 2018 17:30

I found that badfile.php produces "File not found." instead using the 404 error file designated in .htaccess when php-fpm is enabled. I found the solution here: WHM Home " Service Configuration " Apache Configuration " Include Editor Under the "Pre Main Include" section, add: ProxyErrorOverride on But that breaks webmail.domain.tld giving this error: "Access Denied This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required. Additionally, a 401 Unauthorized error was encountered while trying to use an ErrorDocument to handle the request." Anyone get this sorted...?

• 

  cPRex Jurassic Moderator

  • March 03, 2021 20:34

  I wish I knew! That one actually isn't up to us, but is a PHP-FPM thing in general. Here's some more generic, non-cPanel details on that where other users run into the same thing:

  0
• 

  cPRex Jurassic Moderator

  • March 03, 2021 20:55

  Well sure enough - I created a cpanel version 90 machine and checked the page there and you could sort the PHP-FPM column, so I've created case CPANEL-36096 with our developers to look into that. Thanks for your great feedback!

  0
• 

  PeteS

  • March 03, 2021 21:34

  Thanks for the link, I'll check it out. This whole thing has gone sideways from where I thought it should originally, but I'm glad I'm getting my head around it now and feel like it's a better direction. CPANEL-3096 sounds good. Hope you can get them to put that back in (or fix what they broke ;) ).

  0
• 

  PeteS

  • April 30, 2024 18:58

  Did CPANEL-36096 get dropped? I just noticed that in 120.0.2 we *still* can't sort by PHP-FPM, like we used to be able to do.

  ???

  0
• 

  cPRex Jurassic Moderator

  • April 30, 2024 19:44

  Unfortunately yes - since this thread was the only mention of this issue the developers have opted to not fix it.

  0
• 

  cPRex Jurassic Moderator

  • April 30, 2024 19:51

  I know - I just get to be the bearer of bad news sometimes!

  0
• 

  PeteS

  • April 30, 2024 19:51

  *eye roll*

  Thanks Rex!

  0
• 

  PeteS

  • September 30, 2024 07:07
  • Edited

  Since this is the year to respond to 6 y/o posts... lol I realized I never posted my very simple solution to the problem of PHP-FPM ignoring .htaccess ErrroDocument statemetns when the problem is a missing .php file.

  Typically there would be something link this in .htaccess:

  #error pages
  ErrorDocument 404 /404.php
  ErrorDocument 403 /403.php

  This is ignored when PHP-FPM in enabled. (The workarounds discuss at the top part of this thread cause other issues, as documented.)

  Placing this in .htaccess serves to send traffic to a bad .php file name to the 404 handler of choice, the same as for bad non-.php requests (subdirectories, .html, etc.)

  #error pages if PHP-FPM is active
  RewriteEngine on

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule ^.+\.php /404.php [L]

  I hope this helps someone! :)

  1
• 

  cPRex Jurassic Moderator

  • June 20, 2024 13:54

  Thanks for sharing that!

  0
• 

  Peter

  • July 18, 2024 09:15
  • Edited

  Thank you PeteS.

  Works great

  Any idea how to extend that to links without .php at the end ? 
  For instance www.mydomain.com/blah  instead of www.mydomain.com/blah.php
  ErrorDocument handles the former just fine as well

  Also, I assume the error doesn't trickle through this way to the client that  is making the request ?
  If I'm not mistaken the error does go through with ErrorDocument, so that search engines don't index broken links (and don't start indexing 404.php because it's got all those incoming links from broken websites)

  EDIT.  Actually that last bit can be forced by setting the header I believe:
  header("HTTP/1.1 404"); 

  0

Please sign in to leave a comment.