Read a website's logs and traffic

Each hosting writes its own nginx and PHP logs in its logs folder. The panel reads them from the node that owns the site, so you do not need a shell to look at them.

Before you start

• You have manage access to the site and the View hostings permission. A read-only grant is refused.

Steps

Read the logs

1. Open Hostings in the sidebar, click the site, and open Monitoring & logs. Scroll to Logs.

2. Click one log:

   Button	Shows
   access.log	The last 200 requests
   error.log	The last 200 lines of nginx and PHP errors
   error.log · 1000	The last 1000 error lines
   PHP slow requests	PHP stack traces of requests that ran longer than 5 seconds, which is what holds the workers. Shown only for sites with PHP.

3. Type in Filter lines (instant, client-side)… to keep only matching lines. A counter shows how many lines match.

4. Tick Follow to fetch the same log again every 3 seconds.

From a shell the same files are in /home/<system-user>/<domain>/logs/. See Paths and services.

See where the traffic comes from

1. Open the Traffic tab.
2. In Window, choose last 24 hours, last 7 days or last 30 days.
3. Read Where the traffic comes from: Country, Requests, Share and Bytes out.

The numbers are parsed from the site’s own access log, so they reach back as far as that log does. Requests from the server itself, such as monitoring probes and cron, are left out. The card needs the GeoIP database, which only the master holds.

The cluster-wide view is on Stats.

Check that it worked

Open the site in a browser, then click access.log. Your request is at the bottom of the list.

If it fails

• “Pick a log above to load its last lines.” stays on screen: no log was chosen, or the node did not answer. Click the button again and check Service health.
• “the GeoIP database is not installed” on Traffic: install it, then reload the tab.
• An empty log on a new site is normal until the first request arrives.
• A 502 or 504 with nothing in error.log: see A website shows an error page.