Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
-
Unable to open one of the following files, for example https://www.example.com/example.psd:
- psd
- log
- cmd
- exe
- bat
- csh
- sh
-
The following errors are returnedx:
CONFIG_TEXT: 403 Forbidden
nginxOR
CONFIG_TEXT: 403.0 - Forbidden
-
On Windows, the enabled Failed Request Tracing provides with following error:
CONFIG_TEXT: MODULE_SET_RESPONSE_ERROR_STATUS
ModuleName RewriteModule
Notification BEGIN_REQUEST
HttpStatus 403
HttpReason Forbidden
HttpSubStatus 0
ErrorCode The operation completed successfully.
Cause
Expected behavior.
The Block access to potentially sensitive files directive is enabled at the Domains > example.com > WordPress > Security > Details | ">" page, which blocks the execution of the files.
Resolution
-
Go to Domains > example.com > WordPress
-
Security status > View
-
Mark the Block access to potentially sensitive files directive and click the Revert button.
Comments
2 comments
I can't find wordpress>security under the domain, can someone help?
@Aziz Tnani
I have updated the article with the screenshots.
You may also open WordPress Toolkit from the left panel in Plesk, find the needed domain there and check its Security status.
If WordPress Toolkit is not installed on the server, or if the domain doesn't have WordPress, then the issue is not caused by security directives.
Please sign in to leave a comment.