The Raw Logs page lets you read your live server logs without SSH. Pick a tab (Access, Error, FTP, or Login), choose the domain/account and log file, and the last ~500 lines load with auto-refresh. You can also download the full file.

Who can use this

The signed-in account owner. You’ll see only your own logs (domain logs under /var/log/domains/<domain>/ and account logs under /var/log/accounts/<user>/).

What you’ll see

• Tabs: Access, Error, FTP, Login.
• Filters at the top (domain/FTP user + file selector).
• A black, read-only window showing the most recent lines. It auto-refreshes every few seconds and auto-scrolls to the bottom while you’re at the end.

Quick start

1) Click the tab you need (e.g., Error).
2) Pick the Domain (or FTP account on the FTP tab).
3) Choose a Log file from the dropdown (the latest is preselected when available).
4) Watch new lines appear. Use the green Download button to grab the full file.

Tabs explained

• Access — Every HTTP request: method, path, status, bytes, user-agent, IP. Use this to confirm hits, 301/302 flows, or 404 spikes.
• Error — Web/PHP errors for the selected domain: warnings, notices, fatals, and stack traces. Start here for 500 errors and white screens.
• FTP — FTP uploads, logins, and errors for your user(s). Handy for tracing failed credentials or verifying transfers.
• Login — Control-panel sign-ins for your account (success/failure, from which IP).

Controls & behavior

• Domain / FTP account — Filters which log files are listed.
• Log file — Shows the active file(s), including rotated ones (*.gz supported, opened on the fly).
• Auto-refresh — Runs every few seconds. If you scroll up, auto-scroll pauses so your place isn’t lost; scroll back to bottom to resume.
• Download — Saves the selected file exactly as stored on the server.

What to look for

• Access: status codes (404/403 bursts), response size/time, suspicious user-agents, repeated hits from one IP.
• Error: PHP Fatal error, Uncaught Exception, missing files, permission issues. The last lines usually point to the failing plugin/theme/script.
• FTP: repeated login failures (wrong password or blocked IP), transfer successes/errors.
• Login: unknown IPs attempting panel logins → tighten security (2FA, IP Access Control).

Troubleshooting fast

• Website shows 500 → open Error for that domain and read the latest 20–50 lines.
• Files missing → check Access for 404s and the exact path requested.
• Upload failed → check FTP for the transfer and server response.
• “No logs” → the file hasn’t been created yet or the selection is empty; hit the site or wait a moment, then reselect.

Tips

• Use your browser’s find (Ctrl/Cmd + F) to search inside the log viewer.
• Rotate/clear large logs from File Manager if they grow too big (or keep them for audits and download from here).
• Pair this page with Usage History to correlate spikes with errors/hit bursts.