• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question 404 index.html not found for php websites (nignx)

andreios

Regular Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.60 #1
I see on almost al domains the error 404 index.html not found for what ever url.
like this, when the url is 'domain.com/permalink/' the this error is shown "404 domain.com/permalink/index.html not found", website works as expected.
Has something change in the server config recently that could cause this? Can't remember to have seen this before.
I use nginx directly for almost every domain.
 
By default Nginx log every 404 request as an error. So every time a bot (or a human) makes a request to a non existing page it gets logged as an error. You can disable this by adding the directives bellow to the Additional Nginx Directives for your domain in Plesk

Code:
location / {
    log_not_found off;
}
Or if you already have a location / block in your Additional Nginx Directives, add log_not_found off; to it.
 
Not sure if you have understood me. I see on every domain, I think it's at least all WordPress affected, always 404's on every url called.
The called pages work.
The strange thing is that it also tries to call index.html although this is not necessary.

But maybe something has changed with WordPress.

I have hardly any other 404's in the logs and I still want to be able to see 404 issues to debug.
 
Back
Top