Website access and error logs

Last updated: December 2022

Support Documentation / Website access and error logs

Website access and error logs

Website access logs are stored very briefly. Once used for stats processing, the log file is discarded and a new log file created in its place.

The path to the website logs is:


Replace {uuid} with the website ID which is visible in your browser's address bar when managing the website.

This is the same for Apache, LiteSpeed and OpenLiteSpeed and the log format is always the same regardless of the web server you use. You may find it useful to look at the logs to see if requests are reaching the server, to rule out DNS or firewall issues and also to view the HTTP response code sent back to the client.

To watch the logs in real time you can:

tail -f

This will work until the logs are next cycled.

Error logs

These differ between the 3 web server kinds.


For Apache, run "docker logs apache" and you will see the error log as sent to stdout/stderr.


LiteSpeed logs to /var/local/enhance/litespeedlogs


OpenLiteSpeed logs to /var/local/enhance/openlitespeedlogs