Let us take a closer look and examine the Plesk error 404. At Bobcares our Server Management support services will give you a complete note on the error and how to remove it.

1. Symptoms for Plesk Error:

• The error given below, open up on all pages except the main page of a WordPress website. The page is hosted on a Plesk for Windows server:

  Not Found HTTP Error 404.0. The resource you are looking for has been deleted, renamed, or is now unavailable.
• WordPress administration panel > Settings > Permalinks are active.
• Meeting WordPress’s fundamental permalink criteria:

  The URL Rewrite 1.1+ module is available on the Microsoft IIS 7+ web server, and PHP 5 is executing as FastCGI.
• The IIS Failed Request Tracing report contains the following error:

  ModuleName IIS Web Core
Notification MAP_REQUEST_HANDLER
HttpStatus 404
HttpReason Not Found
HttpSubStatus 0
ErrorCode The system cannot find the file specified. (0x80070002)

Cause for Plesk error 404

For IIS to handle permalinks correctly, the rewrite rule is either not defined or is specified incorrectly.

Resolution for the Plesk error 404

Follow the steps given below to resolve the Plesk 404 error:

• Firstly log in to the Plesk GUI.
• Go to Domains: abcd.com Go to the File Manager and click New. Then proceed to Create File. Specify the File name as web.configand click OK to create the file.

After that, we have to press on the web.config file. Paste the following command lines into the Code Editor to setup the permalinks web.config:

?xml version="1.0" encoding="UTF-8"?
configuration
system.webServer
rewrite
rules
rule name="WordPress Rule" stopProcessing="true"
match url=".*"
conditions
add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true"
add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true"
conditions
action type="Rewrite" url="index.php"
rule
rules
rewrite
system.webServer
configuration

To save the file, click OK.

2. Plesk 404 Symptoms

Here is another symptom of the error:

• On the website abcd.com, the Plesk default page or 404 errors open up.
• In Domains- abcd.com, the IP address 203.0.113.2 is allocated to the domain abcd.com.
• The domain abcd.com resolves to another IP address globally: dig abcd.com.

  ;; ANSWER SECTION:
abcd.com. 86400 IN A 203.0.113.3

Cause for the Plesk error 404 in this case:

Misconfigured DNS.

Resolution

Set the right A record in Domains > abcd.com > DNS Settings if the DNS is administered by Plesk. If an external DNS server is in use, modify the A record on the external DNS server.

3. Symptoms

•  The domain is unavailable due to a 404 error. The rewrite rules set in the /var/www/vhosts/abcd.com/httpdocs/.htaccess file are ineffective.
• The FPM application is delivered via the Nginx handler and is configured under Domains > abcd.com > PHP Settings.
• In /var/www/vhosts/abcd.com/logs/error_log the following error is shown:

  [error] 20463#0: *1329372 "/var/www/vhosts/abcd.com/httpdocs/en/component/users/index.html" is not found (2: No such file or directory).

Cause

When the FPM application served by Nginx is activated, the website stops using the .htaccess file, and .htaccess rewrite rules are disregarded.

Resolution

• Apply rewriting rules from /var/www/vhosts/abcd.com/httpdocs/.htaccess to Additional Nginx directives under Domains > abcd.com > Apache and Nginx settings. After moving a WordPress website to FPM served by Nginx in Plesk, all pages save the start page fail to load with “404 Not Found.” Please keep in mind that to write the rewrite rules in Nginx syntax.
• Another option is to switch the domain’s PHP support from the FPM application supplied by Nginx to the FPM application served by Apache under Domains > abcd.com > PHP Settings.
• Alternatively, we can try to convert Apache rules to Nginx using htaccess to the Nginx extension.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now learned more about the Plesk error 404. With the support of our Server management support service, we have also seen the steps to resolve the error.