- Plesk for Linux
Cannot access a specific location of website, e.g.
http://example.com/some_folder, the following error occurs:
CONFIG_TEXT: Server Error
- If CloudLinux operating system is used, its test page is shown:
CONFIG_TEXT: CloudLinux Test Page
This page is used to test the proper operation of the Apache HTTP server after it has been installed. If you can read this page, it means that the Apache HTTP server installed at this site is working properly.
The following error appears in the
CONFIG_TEXT: [autoindex:error] [pid 16314:tid 140300215322368] [client 203.0.113.2:55714] AH01276: Cannot serve directory /var/www/vhosts/example.com/httpdocs/some_folder/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm,index.shtml) found, and server-generated directory index forbidden by Options directive
The requested directory does not contain index files or directory browsing is not enabled.
Apply one of the following solutions (depending on the desired goal):
- Log into Plesk.
- Check what index files defined in Domains > example.com > Apache & nginx Settings:
- Go to Domains > example.com > File Manager.
- (Optional) Navigate to the required folder, e.g.
- Click the New > Create File button.
Specify one of the following names according to file name from step 2:
and press the OK button.
Click on the created file and insert the required content.
The video below demonstrates an example of the process
- For Plesk on Linux: How to enable/disable directory browsing on Plesk for Linux?
- For Plesk on Windows: How to disable/enable Directory Browsing for a domain in Plesk for Windows
This does not work. It is currently (March 2017) not possible to allow autoindex for a specific subdirectory only, but it only works if the location bracket is omitted, e.g:
But in that case the autoindexing feature applies to the document root and all subdirectories of the website.
@Peter, I've just tested this and it works fine. What Plesk version are you using? Are there any custom configuration templates?
No custom configuration. It only occurs on Onyx and was confirmed by another user, too. Please see cases https://talk.plesk.com/threads/autoindex-on-only-working-for-full-website-not-selectively.342182 and https://talk.plesk.com/threads/autoindex-on-only-works-for-complete-website.342176/ for it. On our 12.5 installations, the behavior is correct. We've not yet digged into this deeper to find out where the difference is in Nginx virtual host files between the two.
Thank you for the details. Plesk developers have already been informed about such behavior and the investigation is in progress.
Issue is still present as per post https://talk.plesk.com/threads/autoindex-on-only-working-for-full-website-not-selectively.342182/#post-841437
I've found that it doesn't work because of specific section in nginx.conf which is described in post above
Hi @Mariusz, tthe solution was already escribed in the article below and link with this article:
Please sign in to leave a comment.