Skip to content

Logs

Read website and application error evidence.

1Overview

Logs provides access to selected website and application logs for your account, helping diagnose HTTP errors, PHP issues, and managed application failures.

Logs in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Logs page with website selection, log type selection, refresh controls, and the log viewing area.

Logs in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

User-panel actions affect only resources owned by the signed-in hosting account. This is an advanced task; schedule it carefully and keep a rollback path.

3Step-by-step workflow

Open Logs, select the domain or application, narrow by time or file, reproduce the issue once, and inspect the corresponding entries. Copy only the relevant error message when contacting support.

  1. Open Logs and choose the website or application involved in the problem.
  2. Select the relevant log type and note the displayed time zone.
  3. Narrow the view to the time the error occurred.
  4. Reproduce the issue once if it is safe to do so.
  5. Refresh the log and locate the matching timestamp, path, and error.
  6. Use the first relevant failure to guide a small fix or include it in a support request.
  7. Remove passwords, tokens, visitor details, and unrelated entries before sharing an excerpt.
  8. Repeat the original check after the fix and confirm the error no longer appears.

4Practical example

Example: a failed application request may create both an access-log entry with an HTTP status and an error-log entry with the cause. Compare their timestamps rather than treating an unrelated older warning as the current fault.

5Verify the result

Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.

  1. Confirm the error no longer appears after a fix.
  2. Use the timestamp and request detail to correlate with application changes.

6Common problems and what to check

The log is empty: check the selected site, log type, and whether the request reached this server.

Timestamps look wrong: compare server and local time zones.

The same error returns: record a new timestamp and the change attempted so support can distinguish a current failure from old entries.

7Security, impact, and rollback

Logs can contain paths, request values, and addresses. Do not publish them or paste secrets into a ticket.

Related guides

Hosting PasswordChange the password for your hosting account.Cron JobsSchedule recurring tasks for your hosting account.See all guides in User hosting panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area