• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Forwarded to devs Errors about a missing index.html file in proxy_error_log when running WordPress on nginx

Maarten

Golden Pleskian
Plesk Guru
Username:

TITLE

Errors about a missing index.html file in proxy_error_log when running WordPress on nginx

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.6 (Sky Tiger)
Plesk Obsidian 18.0.46 Update #1

PROBLEM DESCRIPTION

When you run a WordPress site on nginx, there are errors in the proxy_error_log.
For every page, an error is generated complaining about a missing index.html

STEPS TO REPRODUCE

  1. Install WordPress
  2. Hosting settings: 

    - select "run PHP as FPM application served by nginx" 

    - disable "Custom error documents"
  3. - Apache & nginx Settings:
 disable "Proxy mode"
  4. - tail -f /var/www/vhosts/system/domain.com/logs/proxy_error_log
    "/var/www/vhosts/domain.com/httpdocs/hello-world/index.html" is not found (2: No such file or directory)

ACTUAL RESULT

Errors in proxy_error_log, like:
/var/www/vhosts/domain.com/httpdocs/hello-world/index.html" is not found (2: No such file or directory)

EXPECTED RESULT

Running the site without errors about a missing index.html file.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
From the developer:

I was not able to reproduce the issue.
In general, the option "Serve static files directly by nginx" should be enabled under Plesk > Domains > example.com > Apache & nginx Settings in order to work with static files (e.g. *.html) correctly.
Also, the following article contains information about similar issues:
https://support.plesk.com/hc/en-us/articles/213912945
This issue was fixed in 18.0.34. However, the web configuration might be corrupted.
 
I've tested this on two different Plesk servers:
- CentOS Linux 7.9.2009 / Plesk Obsidian 18.0.45 Update #2 / WordPress 6.0.2 / WP-Toolkit 5.12.3-6596
- AlmaLinux 8.6 / Plesk Obsidian Version 18.0.46 Update #1 / WordPress 6.0.2 / WP-Toolkit 5.12.3-6596

Nginx settings:
FPM application served by nginx
Proxy mode = off
Smart static files processing = on
Serve static files directly by nginx = on

Both give the same issue when you load anything but the homepage.
The Almalinux 8.6 is a new server; no changes in the nginx conf; it's all default.
 
I can confirm having this issue too on my server with AL 8.6 running Plesk 18.0.46 mu1 and WPT 5.12.3-6596. However only when the Permalink setting in WordPress is set to something other than Plain.
 
Last edited:
Thank you, guys.
With the additional details, developers have reproduced the issue and continue investigation.
 
From the developer:

It was found that Nginx looks for index files and can not see them. It might be considered normal behaviour for Nginx in general since the Nginx configuration is set this way.
However, the Nginx configuration can be adjusted by Plesk, so I have created the bug PPPM-13722.
 
Back
Top