RunCloud now supports ARM servers – an alternative server architecture offering a more efficient solution with lower power consumption and reduced heat output – ideal for cost-effective, scalable data centers.

Supported Configurations

• Native NGINX server
• Native OLS server
• Containerized NGINX server

Note: Containerized OLS servers are not supported with ARM

The server providers that support direct deployments from your RunCloud dashboard that offer ARM server offerings are Hetzner, AWS EC2, Google Cloud Platform, and Azure.

PHP Updates (NGINX)

• PHP 8.3.13
• PHP 8.2.25

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).

Nginx Updates

• nginx-rc 1.27.1.1

Containerized Servers

• Fixed: Issue preventing users from updating firewalls for containerized servers.

RunCloud Agent v2.9.1+3

• Fixed: Issue affecting Redis password and ACL configuration on containerized servers.
• Fixed: Issue with backup archive restoration failure.
• Fixed: SSH session page no longer displays an error when connected to a non-root user on Ubuntu 24.04.

RunCloud Agent v2.9.0+1

• Fixed: Access log and error log paths for OpenLiteSpeed web applications not being updated when ownership is changed.
• Fixed: Occasional error encountered during the installation of RunCloud Hub.

RunCloud Agent v2.8.10+2

• Improvement: Allow custom ModSec configuration files for the custom NGINX server stack.
• Fixed: Addressed the issue with the file manager being unable to open files in some cases.

Note: This update will automatically apply to your server within 72 hours. If you do not receive the update within this timeframe, please contact our support team, and they will help you manually update your server(s).

RunCloud Hub v1.4.7

• Improvement: Added path validation to skip caching invalid paths. 

Containerized Servers

• Improvement: Introduced support for MariaDB version 11.4. 

RunCloud Agent v2.8.8+8

• Fixed: Problem With Blocked IPs in Fail2Ban Not Working After Firewall Deployments.

System User

• Fixed: Unable to Assign Sudo Privileges to Certain System Users.

RunCloud Agent v2.8.8+7

• Fixed: Issue With PHP Configuration During the Deletion of Web Applications.
• Improved: Restoring Backups Leading to a Spike in CPU Usage.

RunCloud Agent v2.8.8+5

• Fixed: Problem encountered during backup restoration

• Improved: Introduced Unique Cache Keys for WooCommerce Sessions to Prevent "Cart-Conflict" Between Site Visitors.
• Improved: Pages With a Set-Cookie Header Are No Longer Cached to Prevent "Session-Conflict" Issues Due to FastCGI/Proxy Cache.
• Improved: Pages With a No-Cache Cache-Control Header Are No Longer Cached, Enhancing Support for More WordPress Plugins.
• Improved: Purge Cache URLs Now Support Query Strings, Enhancing the "Include Cache Query String" Feature.
• Improved: NGINX Cache Key Update for Easier Purging of Pagination URL Variations and URLs With Query Strings When the Current Page Cache is Cleared.

• Improved: Enhanced Purge Cache by URL Functionality to Target Exact Page URL Without Using Wildcards.
• Improved: The WP-CLI runcloud-hub purgeall Command Now Also Clears Cloudflare Cache When the Integration is Enabled.
• Fixed: Warning in WP-CLI When Running Scheduled Purge Cache With Cloudflare Integration Enabled.

Note: If you still have an older version of the plugin installed and do not see an update notification in the WordPress dashboard, you can manually update it using the plugin ZIP file. 

• Fixed: Unable to Clone WordPress Bedrock Applications
• Fixed: Some Pages Encountering an Unexpected Error During Cloning

Note: This update will automatically apply to your server within 72 hours. If you do not receive the update within this timeframe, please contact our support team, and they will help you manually update your server(s).

• Improved: RunCloud Storage Incremental Backup Process
• Improved: Email Reminders for Inactive Servers
• Fixed: Issue With Restoration Process Returning Error 127

Note: This update will automatically apply to your server within 72 hours. If you do not receive the update within this timeframe, please contact our support team, and they will help you manually update your server(s).