The Web Server Log viewer has been redesigned from the ground up. Instead of scrolling through raw text, you now get a searchable table, interactive timeline, and powerful filtering tools to quickly find the entries that matter.

What’s New

• Structured table view: Log entries are organized into columns (Time, IP Address, Method, Path, Status) with expandable rows for full details on each request
• Interactive timeline: A bar chart at the top of the viewer shows how requests are distributed over time. Hover over a bar to see request counts and types, or click to jump directly to those entries in the table
• Search and filter: Search by path, IP address, or status code. Filter by HTTP method (GET, POST, etc.) or response status (200, 404, etc.) using the dropdown menus
• One-click actions: Reload to fetch the latest entries, copy log data to your clipboard, or download the raw log file
• Raw view still available: Switch back to the original raw-text view at any time using the Raw toggle

Supported log types: NGINX Access, NGINX Error, Apache Access, Apache Error, and G-Firewall.

Note: The viewer displays the most recent 500 lines from the underlying log files. NGINX buffers logs and writes them after the buffer reaches approximately 16 KB, unless your web application is in Development Mode.

To access the new Web Server Log, navigate to your web application and Web Server Log, as shown below: 

Learn more about the new Web Server Log view in RunCloud ->

What’s New

• Fixed: Addressed a critical bug that caused unexpected data removal during the cloning process.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

What’s New

• Fixes: Fixed a service execution bug causing OpenLiteSpeed to fail under certain conditions.
• Fixes: Resolved specific environment configuration conflicts affecting WordPress Canvas deployments.
• Improvement: Optimized the teardown logic for web application and database deletion routines.
• Improvement: Expanded log output and improved status event tracking for the web application cloning process.
• New: Added support for defining and applying custom Nginx configuration templates.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

RunCloud now supports LiteSpeed Enterprise (LSWS) as a web server stack for Business and Enterprise plans. Deploy new LiteSpeed Web Servers using a bring-your-own-license (BYOL) model and get the full power of LiteSpeed: LSCache, built-in WAF, QUIC.cloud integration, and better performance under load.

What's new

LiteSpeed Enterprise is now available as a beta as the third web server stack alongside NGINX and OpenLiteSpeed.

• BYOL (Bring Your Own License) Model: Bring any eligible LiteSpeed Enterprise license. The Free Starter license from LiteSpeed covers servers with up to 2GB RAM.
• Business and Enterprise plans: LSWS is available on Business and Enterprise plans. Essential and Professional users see the option grayed out with an upgrade prompt
• New servers only: LSWS is deployed on fresh server instances. Existing Nginx, OpenLiteSpeed, or Docker servers cannot be converted in place.
• License management in dashboard: View license status (active, trial, expired, invalid), check license details (tier, domain limit, worker limit, RAM limit, expiry date), and update your license key from Settings > LiteSpeed in your server dashboard.
• Blocked state protection: If a license is invalid, missing, or expired, the server enters a blocked state. You can still view pages and delete the server, but cannot deploy apps or change settings until a valid license is provided.
• Requires agent 2.18.0+: Make sure your RunCloud agent is up to date before deploying.

Where to find it

Navigate to Connect a New Server and select LiteSpeed Enterprise as your web server stack:

Learn more about how to use LiteSpeed Enterprise on RunCloud ->

What’s New

• Fixed: WordPress download checksum to prevent file truncation.
• Added: Support for LiteSpeed Enterprise.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

Core Upgrades & Security

• Server Stealth: Added a setting to easily hide the Nginx version token in HTTP response headers.
• Crash & Memory Fixes: Patched critical segmentation faults (QUIC/worker shutdowns), a NULL pointer in the SSL cache, and memory bugs that were corrupting HTTP headers.

Routing & Traffic Management

• URI Rewriting: Added native URI rewriting support and patched a related crash involving query strings.
• Header Control: Introduced the response_headers option to easily manage and manipulate HTTP response headers.
• Network Fixes: Resolved total IPv6 connection failures for ASGI applications and stopped the $uri variable from improperly caching.
• Large Uploads: Patched payload limits, reliably allowing uploads larger than 4GiB.

Administration & Logging

• Granular Logs: Introduced per-application and conditional route logging to isolate errors and reduce log noise.
• App Fixes: Fixed PHP error handling to correctly return standard 403 and 404 HTTP errors.
• Clean Reloads: Unix domain listen sockets are now properly deleted during server reconfigurations.

It's no secret that, in light of recent AI developments, concerns about security across open- and closed-source software are growing.

In response, we are excited to introduce Server Patch Management on RunCloud.

Our new Patch Manager brings publicly available patches into a single, manageable interface within your RunCloud dashboard. Instead of manually logging into each server to check for and apply updates, you can now see which servers need attention and apply patches in bulk, all from one place.

Learn More: How to Use Patch Manager in RunCloud

What's New

Patch Manager is now available under Settings in your Workspace and Personal Space, giving you a centralized view of available patches across all your servers.

See exactly which servers need attention: Each patch shows only the servers that match its criteria across OS, web server type, architecture, and more. No more guessing which of your servers are affected by a given vulnerability.

• Eligible server filtering: When you select a patch, only servers that match its criteria (OS, web server type, architecture, etc.) are shown. Servers that don't need the patch or are already patched are automatically excluded, so there's no guesswork involved.
• Bulk patch application: Select multiple eligible servers at once and apply patches in a single action. Acknowledge any reboot requirements and proceed on your schedule.
• Real-time status tracking: Watch each server progress through the patch lifecycle (Not Applied, In Progress, Patched, or Failed) with live updates. Navigate away and come back anytime; status is tracked per server.
• Clear visibility: Every patch explains why certain servers appear (and others don't), with a summary like "3 of 12 total servers match this patch." You'll always know what needs action and what doesn't.
• Audit trail: Every patch applied is logged, including what was applied, when, and by whom.

Where to find it

Navigate to Settings > Patch Manager to see available patches for your servers: 

Note: The Server Patch Manager will surface publicly available patches from upstream sources and provide a structured way to apply them via RunCloud. It is not a vulnerability research or custom patching tool.

What’s New

• Fix: Resolved an issue with ModSecurity configs failing to clone correctly.
• Improvement: Added a recovery notification for the autohealing process.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

RunCloud AI Monitoring continuously analyzes your server's activity to detect anomalies, classify severity, diagnose root causes, and surface remediation steps you can act on immediately.

Note: As AI Monitoring is still in beta, we recommend enabling it on test or non-production servers first. We're actively refining data handling and privacy documentation, which will be published ahead of general availability.

How It Works

• Read-only by design. RunCloud AI observes your server and provides insights. It never runs commands or makes changes automatically. 
• You stay in control. Any suggested commands & next steps are for you to review and run manually. 
• AI isn’t perfect. Recommendations may be incomplete or incorrect. Always verify before making changes.

Learn more in our documentation ->

How to Enable AI Monitoring

AI Monitoring can be enabled by navigating to your server of choice and looking for the new Install RunCloud AI option, as shown below: 

You'll see a one-time consent modal explaining how RunCloud works. Accept the terms, and then click Enable AI Monitoring to enable AI Monitoring on this server.

RunCloud Agent v2.17.12 (Patch)

What’s New

• Fix: Resolved an issue wp-config are not properly updated during cloning.

Deployment Information
This update will automatically roll out to all compatible servers within 72 hours.

• No action is required.
• The update installs seamlessly in the background.

PHP Updates Now Available for NGINX

• PHP 8.5.7
• PHP 8.4.22
• PHP 8.3.31
• PHP 8.2.31

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