Hi, I noticed that I don't always get Error 404. For example, if it is a folder then Error 404 is displayed. www.somewebsite.com/folder-x/ So if the folder is Error 404 it shows, but if the file is like for example; www.somewebsite.com/some.php or www.somewebsite.com/some.html (files that do not exist) , then I don't get Error 404, I just get a message "File not found." I would like to get an Error 404 message then too.

It doesn't always show Error 404.

aaPanel_Kern

Hello, please check whether the corresponding directory and file exist? If the file is not accessed correctly, the default access index file (index.html/index.php and other files)

aaP_clous

aaPanel_Kern Hello, please check whether the corresponding directory and file exist? If the file is not accessed correctly, the default access index file (index.html/index.php and other files)

I don't know if you understood the question correctly.
Error 404 occurs when the FOLDER does not exist and that's okay.
What's wrong is that Error 404 doesn't come out when it's a FILE that doesn't exist, for example:
www.somewebsite.com/some.html

.... that file does not exist on the server and I should get Error 404 but unfortunately that is not the case, instead of Error 404 I get the message: File not found.

aaPanel_Kern

Hello, you can modify the default 404 error message or 404.html file.
It is normal to return this response

aaP_clous

aaPanel_Kern Hello, you can modify the default 404 error message or 404.html file.
It is normal to return this response

Is it possible that instead of the response "File not found" I get Error 404? If so, how do I do that?

aaPanel_Kern

Yes, generally, if the file does not exist, it means a 404 error. Please check whether the corresponding file exists.

aaP_clous

How can I set that up, can you tell me?

aaPanel_Kern

Hello, what is the web program you are using? I tested nginx, regardless of whether the directory or the file does not exist, it returns a 404 error. The file is not found.

aaP_clous

aaPanel_Kern apache 2.4

aaPanel_Kern

Hello, apache will return 403 error if the directory does not exist. Show Permission issue
The file does not exist will return a 404 error

aaP_clous

To better understand me, I'm leaving you with a img.

In the picture above you can see that I don't get a 404 error, but only a "File not found" message, although I should get an Error 404.

Below I leave another image where I get a 404 error because it is a folder and not a file.

So when it comes to a folder, Error 404 works properly, but when it comes to a file (first image), then Error 404 doesn't work, I just get a simple message "File not found".

aaPanel_Kern

Hello, this should be the error returned by your website program.

aaP_clous

aaPanel_Kern Hello, this should be the error returned by your website program.

My website program is Apache 2.4 and I know that, The question is how do I fix that?

aaPanel_Kern

Hello, it is recommended that you check .htacces and website programs

aaP_clous

aaPanel_Kern Hello, it is recommended that you check .htacces and website programs

When you say website program, I assume you mean Apache?

aaPanel_Kern

Hello,
Website programs refer to the website program files you use for deployment, such as WordPress, etc.

aaP_clous

aaPanel_Kern
No, it has nothing to do with the 404 error, the script I use does not do anything related to 404 errors or any other error.

The problem is that aapanel (apache) throws a 404 error when it's about a folder that doesn't exist on the server, but when it's about a file that doesn't exist on the server, such as xxxxx.php or xxxxx.html, it doesn't show error 404, but it should.
Just show this (see image):

aaPanel_Kern

Hello, it is recommended that you check the configuration of the website. The following picture shows the content when the newly added website files and directories I tested do not exist.

aaP_clous

I will share my experience. The problem was not with the application I use on the server.

I found the answer here;:
https://stackoverflow.com/questions/50224464/custom-404-shows-file-not-found-for-php-files-instead-of-redirecting

aaP_clous

I want to follow up on this topic because I discovered that it is not a good idea to add:
ProxyErrorOverride On

.. inside the Apache configuration because it can cause problems on some websites.
The problem is that 'File not found' is only shown for .php files, if it is .html, .jpg, etc. it shows a page created for error 404 but if it is .php then the message 'File not found' is shown. So my question was why it doesn't show a custom 404 error for files that don't exist and end with the extension .php

This is the best way to solve this problem for now:
Inside the web config / vhost file (aapanel -> Website -> choose a website -> Config) put this part:

  # Custom 404/403 for static files
<FilesMatch "\.(html|htm|css|js|png|jpe?g|gif|svg|ico)$">
    ErrorDocument 404 /errors/404.html
    ErrorDocument 403 /errors/403.html
</FilesMatch>

and finally put this part in the .htaccess file:

# If the PHP file does not exist → show custom 404
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/admin
RewriteRule \.php$ /errors/404.html [L]

You have to change the path yourself, in my case the error 404 file is located in the root, error folder, error404.html file.

aaP_glupatone638

Yeah, that’s normal behavior on some servers. Directories usually return a proper 404 error, but certain file types can simply display a plain “file not found” message, depending on how the host is configured. If you want them all to return the same 404 page, you’ll need to adjust your server’s error handling rules so both files and folders are treated the same way.

aaP_clous

aaP_glupatone638 Yeah, that’s normal behavior on some servers. Directories usually return a proper 404 error, but certain file types can simply display a plain “file not found” message, depending on how the host is configured. If you want them all to return the same 404 page, you’ll need to adjust your server’s error handling rules so both files and folders are treated the same way.

There's actually a much easier way to do this.
In the virtual host of the domain just put this:

<Directory "/www/wwwroot/yourdomain.com/admin">
    ProxyErrorOverride Off
    ErrorDocument 404 /yourerrorfolder/404.html
    ErrorDocument 403 /yourerrorfolder/403.html
</Directory>

ProxyErrorOverride On

Save and restart apache, after that everything will work correctly and as it should regarding the 404 error