Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.
If your server has not received the update after 72 hours, please contact our support team for manual assistance.
You can now easily schedule restarts or run them automatically when required.
1) Scheduled Restart
Restart your server at a fixed time based on your preferred schedule.
2) Restart when required
Automatically restart only when a system update requires it, and run it during your next maintenance window.
In both cases, your Schedule Type can be a simple time-based preset or a Custom Cron Expression, as shown below:
Note: When a restart may be required, you'll see a “Restart Recommended” badge on the server overview or in the servers list. You can also temporarily dismiss this reminder.
Fixes
Improvements
Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.
If your server has not received the update after 72 hours, please contact our support team for manual assistance.
Note: If your server runs on OpenLiteSpeed, RunCloud does not handle PHP version updates. However, once a PHP version update becomes available for OpenLiteSpeed, it should also be automatically available on your server(s).
Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.
If your server has not received the update after 72 hours, please contact our support team for manual assistance.
We’ve added support for up to 5 workspaces on the RunCloud Enterprise plan.
This update expands on the existing Workspaces feature and is especially useful for teams managing multiple environments, brands, or client setups.
The feature is available immediately and requires no changes to existing setups.
You can now fully restart your server directly from within the RunCloud dashboard.
This gives you a fast, controlled way to apply system-level updates, recover from instability, or resolve deep system issues without leaving your RunCloud dashboard.
In your RunCloud dashboard, navigate to the server you want to restart:
From here, you can either:
Open the Quick Actions menu, as shown below,
Or, alternatively, navigate to the server’s Settings area and click Restart Server.
And then, click Restart Server.
Upon doing so, you'll be prompted to confirm that you wish to proceed in the modal.
Once confirmed, your server will begin the restart process.
Before performing a full server reboot, consider whether a service reload is sufficient.
From the Services tab, you can choose to Reload or Restart individual services, such as:
Reloading a service tells it to re-read its configuration files without terminating the main process or dropping active connections. This is the preferred approach when applying configuration changes.
Restarting a service stops and starts that specific service, which may cause brief downtime for that component.
A full server restart should only be used when necessary, such as:
What's New
Deployment Information
Upgraded OpenLiteSpeed to v1.8.5
Includes upstream stability improvements and bug fixes
This release incorporates fixes from the official OpenLiteSpeed 1.8.x branch, focusing on internal stability, protocol handling, and minor edge-case corrections.
For full upstream details, refer to the OpenLiteSpeed 1.8.x release log.
What’s New
Deployment Information
We’ve also released improvements to our email notification system:
Reduced Email Volume
Auto-Unsuppression for Critical Emails
Note: If your server runs on OpenLiteSpeed, RunCloud does not handle PHP version updates. However, once a PHP version update becomes available for OpenLiteSpeed, it should also be automatically available on your server(s).