Access Log

The Access Log Viewer lets you inspect web requests for your domains, graph traffic, and watch a live tail — all without SSH. Pick a domain, choose a log (today or a past day), and you’ll see stats, charts, a top-10 breakdown, and the latest 10,000 lines.

Who can use this

The signed-in account owner. You’ll only see logs for domains under your account.

Quick start

1) Choose a Domain from the first dropdown.
2) Choose a Log file (e.g., today (live) or a specific date).
3) The page loads: SummaryChartsTop 10Latest 10,000 lines.
4) Click Download to save the selected log, or Start Live View to follow new requests in real time.

Choosing domain & file

Domain — includes main, addon, parked, and subdomains you own.
Log filetoday (live) shows the current file (access.log); dated entries are rotated logs (access.log-YYYYMMDD.gz).

Summary (last 120,000 lines)

Hits — total requests; Pages — GET/POST requests.
Unique IPs — distinct clients; Visits — unique IP per hour.
Bandwidth — bytes sent; Bots/Humans — basic UA classification.

Charts (traffic & composition)

Over time — by month, day of month, weekday, and hour (spot patterns/spikes).
Status codes — distribution of 2xx/3xx/4xx/5xx responses.
Methods — GET/POST/HEAD/etc.
Humans vs Bots — quick signal for bot surges.
Browsers — top user-agent families.

Top 10 (quick forensics)

Hosts — most active IPs (good to flag abusive scanners).
URLs — most hit paths (find heavy or error-prone endpoints).

Latest 10,000 lines (table)

• Columns: Date/Time, IP, Method, URL, Status, Bytes, Agent.
• Use the table’s search and sort to focus on specific URLs, codes, or IPs.

Live View (3-second tail)

• Click Start Live View to follow access.log in real time; Auto-scroll keeps you at the bottom.
• Click Stop Live View to return to charts and table.

Download the raw log

• Click Download to save the currently selected file exactly as stored (supports .gz rotated logs).

What the lines mean

Each line includes: client IP, timestamp, request method + URL, HTTP status, bytes sent, and user-agent. Example issues:
• Many 404 → missing files or bad links.
• Many 5xx → app/PHP errors (check Error Log too).
• Repeated hits from one IP → consider rate-limiting or blocking.

Troubleshooting

No log files: the domain may not have traffic yet, or logging is disabled.
Charts don’t load: switch to a smaller/closer date; reload the page.
Times look off: timestamps reflect server time stored in the log; UI displays them as parsed from lines.

Tips

• Correlate spikes with Usage History (CPU/RAM).
• Use Security Settings to lock out abusive IPs; block via app firewall or server rules if needed.
• Keep rotated logs for audits; download before clearing if you need a record.

Navigation