Articles in this section

How to troubleshoot the website availability via Website Log Check in Plesk?

kb: how-to Plesk for Linux Plesk

Applicable to:

  • Plesk for Linux

Question

How to troubleshoot the website availability via Website Log Check in Plesk?

Answer

Website Log Check scans the web server logs for common issues, shows how often a specific issue occurs, and suggests ways to resolve the issue.

Note: If the page is missing enable it with the steps of the 'To enable Website Log Check' section below.

To access and check the Website Log Check:

1. Log in to Plesk

2. Navigate to:

  • Server-wide:
    Tools & Settings > Website Log Check (under “Assistance and Troubleshooting”)
  • For website:
    Websites & Domains > example.com > Logs
     

3. Enable Automatic check or Run manual check for specific time period for one or several websites:

Click on a section to expand

To enable Website Log Check:

1. Connect to the server via SSH

2. Open the /usr/local/psa/admin/conf/panel.ini with the file editor or command below:

# plesk conf panel.ini

3. Add the following lines to the panel.ini file and save it:

CONFIG_TEXT: [websitesDiagnostic]
enabled = true

More information about this feature can be found on the documentation page.

Website Log Check can detect the following issues:

  • PHP-FPM “server reached max_children setting”
  • ModSecurity “Access denied with code 403”
  • PHP “Internal Server error 500: Allowed memory size of XXX exhausted”
  • PHP “open_basedir restriction in effect”
  • Apache .htaccess “403 Forbidden AH01797: client denied by server configuration”
  • Apache “Cannot access a website directory in Plesk: 403 Forbidden”
  • Nginx “Cannot access a website directory in Plesk: 403 Forbidden”
  • Apache .htaccess “403 Forbidden: pcfg_openfile: unable to check htaccess file, ensure it is readable”
  • Nginx “Too many open files”
  • Nginx “502 Bad Gateway: upstream sent too big header while reading response header”
  • Apache “500 Internal Server Error: Option FollowSymLinks not allowed here”
  • ModSecurity “Response body too large”
  • Apache “server reached MaxRequestWorkers setting”
  • PHP request body limit “client intended to send too large body”
  • PHP request body limit “client intended to send too large body”
  • PHP sessions “503 Internal Server Error” or “Failed to read session data”
  • Apache .htaccess “403 Forbidden: pcfg_openfile: unable to check htaccess file, ensure it is readable”
Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.