DE

↑ ↓ select, Enter open, Esc close

Find the domains with the most requests on Plesk

harmless rootLogsdebian, ubuntu
root@server
wc -l /var/www/vhosts/system/*/logs/access_ssl_log 2>/dev/null | sort -rn | head -20

Plesk stores the logs of each domain under /var/www/vhosts/system/<domain>/logs/. The command counts the lines in the access_ssl_log of all domains and shows the 20 largest. The top line with total is the overall sum, followed by the domains ordered by number of requests.

Note: Only requests since the last log rotation are counted, and rotation can be configured differently per domain. Plain HTTP requests are in access_log.

Also searched as

  • which domain gets the most requests
  • which website is causing the load
  • plesk requests per domain
  • busiest site on the server

Related one-liners

All in Logs

Count requests per minute in the access log

#awk '{print substr($4, 2, 17)}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

Find the top IP addresses in the access log

#awk '{print $1}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

Analyze Googlebot requests in the access log

#grep -i "googlebot" /var/www/vhosts/system/example.com/logs/access_ssl_log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20
harmlessLogs

Analyze server errors (5xx) in the access log

#awk '$9 ~ /^5[0-9][0-9]$/ {print $9, $7}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

Count HTTP status codes in the access log

#awk '{print $9}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn
harmlessLogs

Filter the access log by time range

#awk -v von="09/Oct/2026:14:00" -v bis="09/Oct/2026:15:00" 'substr($4, 2) >= von && substr($4, 2) < bis' /var/www/vhosts/system/example.com/logs/access_ssl_log
harmlessLogs

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.