The Logs page lets you open your server's log files, including rotated and date-named files, and read past server activity. Within an open file you can search and filter entries by severity (errors, warnings, info, debug, chat, and more), with options for regex, case-sensitive, and inverted matching.

Use the Share button to generate a shareable link to your log. Sensitive details such as IP addresses, auth tokens, and email addresses are redacted before sharing, and you can opt to redact more (UUIDs, coordinates, file paths). Links expire after 3 days by default (you can set anywhere from 1 to 30 days). Sharing a link instead of a screenshot keeps formatting intact for support staff.

On the Console page, use the Errors and Warnings tabs to filter messages by severity, with live counts. Errors appear in red and warnings in yellow. From these filtered tabs you can Export the entries to a .txt file. Look for stack traces (lines starting with "at") to trace the source of an issue.

The console keeps roughly 1,000 recent messages per tab in your browser (console, errors, warnings, and chat each have their own buffer). Older messages scroll out of the in-page buffer, but they're still written to the server's log files, which you can open from the Logs page or File Manager.

You can Export the contents of the Errors, Warnings, and Chat console tabs to a .txt file, and the Logs page has a Download button for the selected log file. You can also reach log files directly in the File Manager under the /logs directory, where files like latest.log and date-named, compressed rotations (e.g. 2024-01-15-1.log.gz) are kept.

Click Clear in the console controls or type clear in the command input. This only clears the local display in your browser — it doesn't delete any log files or affect the running server. New messages keep arriving, and your full history stays available through the Logs page and File Manager.