Confirm the domain document root and the actual published entry file. Record the current default-document order and any web.config rules. An application using its own routing may not need a physical index page at every route.

1. Open the domain IIS Settings in Plesk and locate Default documents.
2. Review the inherited or custom list. Add the exact supported filename when required, such as index.html, and place it in the intended search order.
3. Check for an old default placeholder that appears earlier than the real entry point. Remove or reorder only what is appropriate to the deployed application.
4. Keep directory browsing disabled unless publishing a file listing is an intentional, reviewed requirement. Save the setting and read validation messages.
5. Request both the directory URL and the explicit entry-file URL. Compare the returned content and any application routing behaviour.

Confirm the root URL serves the expected page and does not reveal a directory listing. Test a subdirectory and an application route so an inherited setting has not changed unrelated behaviour. Check HTTPS and the preferred hostname.

If the explicit file works but the directory does not, inspect the default-document list and inherited web.config. If neither works, check document root, permissions and deployment contents. A 403.14 response often indicates directory-listing/default-document handling, but use the actual IIS error detail to confirm. Restore the recorded list if the new order causes an unintended page to appear.

• Changing a Plesk website document root safely
• Fixing a Plesk Windows website permission problem
• Diagnosing website errors with the Plesk log browser
• Configuring a dedicated IIS application pool in Plesk

• Plesk: Iis Web Server Settings
• Plesk: Changing Virtual Directory Settings