Overview
Rapyd Cloud gives you access to logs at two levels: the individual site and the environment it runs on. Site logs cover application-level activity for a specific WordPress installation, while environment logs cover server-level activity across everything running in that environment. Together, they give you a complete picture of what's happening on your hosting infrastructure.
Both log types support the same core actions: viewing log details, searching entries, downloading logs, refreshing the view, and clearing logs to free up disk space. Clearing logs is permanent and cannot be undone, so downloading first is recommended if you need to retain the data.
In this article, you will find a breakdown of the available log types and step-by-step instructions for viewing, managing, and clearing logs at both the site and environment level.
Site logs
Site logs are scoped to a single WordPress installation. They are accessed from within the site management area and cover application-level activity for that site only.
Available log types
Access logs: A record of every HTTP request made to the site, including the request type, IP address, status code, resource path, and timestamp. Useful for monitoring traffic patterns and identifying unusual or unauthorized access.
Site error logs: Errors returned by the web server for this site, such as 4xx and 5xx responses. A good starting point when a page is returning an error or behaving unexpectedly.
PHP error logs: Errors generated by PHP code running on the site. These include fatal errors, warnings, and notices, and are the primary tool for diagnosing plugin, theme, or custom code issues.
How to access site logs
Step 1: Navigate to your site
From the dashboard, go to Sites and locate the site you want to inspect. Click Manage site.
Step 2: Open the Logs section
In the left-hand navigation menu, click Manage, then select Logs.
Step 3: Select a log type
Use the dropdown at the top of the logs view to switch between Access logs, Site error logs, and PHP error logs.
Environment logs
Environment logs are scoped to the server your sites run on. They cover infrastructure-level activity across all sites in that environment and are accessed from the environment management area.
Available log types
Platform audit logs: Low-level system process events from the server node. These are not typically actionable on their own, but may be relevant when working with the Rapyd Cloud support team on infrastructure-level issues.
Server error logs: Output from the LiteSpeed web server at the environment level, including process lifecycle events and server-level errors. Entries are tagged with a severity level (INFO, NOTICE, WARNING, ERROR) so you can filter for genuine issues. Useful when troubleshooting problems that may originate below the application layer or affect multiple sites.
Stderr logs: Standard error output from server processes. Typically used by developers to diagnose low-level process failures that do not appear in application-level logs.
Database logs: Activity and error output from the MariaDB database service. Helpful for diagnosing slow queries, connection issues, or database-level errors affecting your sites.
Redis logs: Output from the Redis (KeyDB) caching service. Useful when troubleshooting object caching behaviour or cache-related performance issues.
Note:
Environment logs reflect activity across the entire server, not a single site. If you are troubleshooting an issue on one specific site, start with site logs and move to environment logs if the cause is not clear.
How to access environment logs
Step 1: Navigate to your environment
The quickest way is from within your site management area. Click the environment name displayed in the site header to go directly to the environment overview. Alternatively, click the account icon in the top-right corner of the dashboard and select Environments, then find and open the relevant environment.
Step 2: Open the Logs section
Click Logs in the environment navigation menu.
Step 3: Select a log type
Use the dropdown to select the log type you want to view: Platform audit logs, Server error logs, Stderr logs, Database logs, or Redis logs.
Managing logs
The following actions are available for all log types, at both the site and environment level.
Viewing log details
Each log entry has an eye icon in the Log details column. Click it to expand the full details for that entry.
Searching logs
Use the Search bar above the log table to filter entries by keyword.
Refreshing logs
Click the refresh icon to reload the log view and pull in the latest entries.
Downloading logs
Click the download icon to download the currently selected log as a file. If you are planning to clear a log, download it first if you need to retain the data.
Clearing logs
Click the delete icon to clear the currently selected log type. A confirmation dialog will appear before the action is completed.
Important:
Clearing logs is permanent and cannot be undone. Only the currently selected log type is cleared. If you need to retain the data, download the log before proceeding.
Log files can grow large on active sites with frequent errors. Clearing logs periodically is a straightforward way to recover disk space and keep your environment running cleanly.
Conclusion
Site logs and environment logs give you visibility at every layer of your hosting setup. Use site logs when investigating application-level issues on a specific WordPress installation, and environment logs when the issue may be at the server level or affecting multiple sites. If you have any questions or need help interpreting your logs, our support team is available 24/7.