Site logs in ISPmanager
Logs are the first place to look when a site misbehaves. The error log shows why a page returns 500 or a blank screen. The access log shows who opened what: search bots, attacks on the login form, broken links.
Open a log
- "Site logs".
- Three dots on a file → "View". You can also "Download" or "Clear" it.


| File | Contents |
|---|---|
example.com.access.log | all requests to the site |
example.com.error.log | web server and PHP errors |
*-out.log | Node.js or Python app output |
*-error.log | app errors |
Logs of one site: three dots on the site → "Log".

Reading the error log
Look for lines with PHP Fatal error or PHP Parse error at the time of the failure. The line names the file and line number, for example …/wp-content/plugins/plugin-name/file.php on line 120 — the error is in the plugin-name plugin.
A blank page or error 500: open error.log. The last line usually names the file and line with the error.
Reading the access log
Each line has the visitor IP, time, request, response code, referrer and browser. Many requests from one IP to wp-login.php or xmlrpc.php mean password guessing. 404 responses are broken links, 500 are errors to look up in error.log.
Log archives
The panel moves old entries to archives: see the "Number of archives" and "Archive total size" columns. How often this happens and how many archives to keep is set in the site settings, in the logs block.
Panel logs
"Action log" shows which actions were performed in the panel and from which IP. "Access log" in the panel menu shows logins to the panel itself. Check them if you suspect someone else has access.
"Clear" erases the log permanently. If you are investigating an error, download the file first.