Theme
Site logs
Read Nginx access and error logs for a site without SSH.
Who can use this page? Site read access — Site Manager and assigned User. Open via toolbar Logs or Site logs navigation.
Open logs
- Site toolbar → Logs, or
- Sidebar → Site Logs and choose the site / log type
Log types
| Type | Contents |
|---|---|
| Access | Requests: IP, method, path, status, timing, user agent |
| Errors | Nginx/upstream errors, PHP-FPM failures, 502/504 clues |
Application logs are separate
These are Nginx logs. They can show that an upstream app refused a connection, but they do not contain every Node.js or Python stack trace. For Git build failures, open Git Deployment and inspect the deployment history. For application process output, ask NitHost support for the application process logs.
Reading access logs
Common statuses:
| Status | Meaning |
|---|---|
| 200 | OK |
| 301/302 | Redirect |
| 403 | Forbidden (permissions, firewall, basic auth) |
| 404 | Not found (missing file or bad rewrite) |
| 429 | Rate limited |
| 500 | App error |
| 502/504 | Upstream down or timeout (Node not running, FPM overload) |
Analytics vs logs
- Site Logs — raw recent lines for debugging
- Analytics — aggregated traffic, visitors, response times (robots and login noise excluded)
See Analytics.
Rotation
Access/error logs rotate daily so analytics can catch up. Very old raw lines are not kept forever in the panel viewer — ask NitHost support about longer-term retention.
Privacy
Logs contain IPs and user agents. Treat exports as personal data; do not paste customer logs into public tickets.