Access logs record every request that comes into your web server: which IP address, which page, which status code, and how much data was transferred. By analyzing these logs, you can track down errors, attacks, and slow-loading pages. In Plesk, you’ll find these logs per domain under Logs, and with the right tools, you can turn raw lines into useful insights.
Where to find access logs in Plesk
Plesk stores separate log files per domain, usually in the folder /var/www/vhosts/[domainname]/logs/. Via the control panel, go to Websites & Domains β your domain β Logs. There you can view or download the access.log directly, without needing SSH access.
Logs are rotated automatically: older files are archived (often compressed as .gz) and a new log file starts. This keeps a single file manageable in size. On servers with heavy traffic, it’s wise to check the rotation settings so logs don’t unnecessarily consume disk space.
Parsing a log line
A standard log line in the Common or Combined Log Format looks like this:
192.168.1.100 - - [10/Jan/2025:13:55:36 +0100] "GET /index.html HTTP/1.1" 200 1234
This can be broken down as follows:
- IP address: 192.168.1.100 β the visitor or bot
- Username: usually a dash, as it’s unused
- Date and time: when the request came in
- HTTP method and path: for example GET /index.html
- Status code: 200 (success), 404 (not found), 500 (server error)
- Bytes transferred: the size of the response
Status codes are the fastest indicator of problems. Codes in the 4xx range indicate errors on the visitor’s side (such as an incorrect or removed URL), while 5xx codes indicate a problem on the server, for example a script that crashes or a database that isn’t responding.
Analyzing logs: step by step
Download the log file
Log in to Plesk, go to Logs, and download the access.log for the desired period to your computer.
Filter by status code
Use SSH commands such as grep " 404 " access.log to find error pages, or grep " 500 " access.log for server errors.
Count the most active IP addresses
With awk '{print $1}' access.log | sort | uniq -c | sort -rn you can immediately see which IPs are generating the most traffic, useful for identifying bots or attacks.
Look for patterns over time
Spikes around a specific time can indicate an automated attack or a slow page being repeatedly requested.
Take action
Block suspicious IPs, fix 404 errors by setting up redirects, and investigate 500 errors together with your application logs.
Tools for log analysis
Manually searching through large log files is time-consuming. These methods make it more practical:
- Plesk web interface: view and download logs directly, without SSH access.
- Command-line tools via SSH: grep and awk are powerful for quick filters and counts.
- AWStats or Webalizer: generate clear graphs and reports from your log files, often available via the control panel.
- Fail2Ban: monitors logs in real time and blocks IPs that repeatedly show suspicious behavior, such as brute-force login attempts.
Log analysis is part of the broader management of your web hosting, just as a well-configured business email environment contributes to reliability. If you get stuck interpreting certain log lines, consult the knowledge base or contact support.
Frequently Asked Questions
How large do access logs normally get?
This depends heavily on your website’s traffic volume. With many visitors or lots of bot traffic, logs can grow quickly, which is why log rotation is important.
Can I have logs analyzed automatically?
Yes. Tools like AWStats can run periodically and generate reports, and Logwatch can send summaries by email.
How long should I keep logs?
That depends on your own policy and any legal obligations. In any case, keep them long enough to be able to investigate incidents afterwards.
Can I analyze logs without SSH access?
Yes, Plesk offers a web-based log viewer that lets you view and download logs to analyze them locally with free tools.
What if I see many suspicious IP addresses in my logs?
Consider blocking them via Fail2Ban or the firewall settings in Plesk, and check whether your passwords and user accounts are still secure.
Conclusion
Access logs in Plesk give you direct insight into who visits your website, which errors occur, and whether suspicious activity is taking place. With the web interface, command-line tools, or reporting software like AWStats, you can quickly extract useful information from these files. Regular monitoring helps identify security risks and performance issues early.