# xCloud v2.9.23

> Released November 19, 2026

**Run Nod by n8n on xCloud Managed or Your Own Cloud Provider**

Every xCloud account (except white-label teams) can now create a Nod server. You can run it on an xCloud Managed plan from 6 GB or on a server from your own cloud provider. OpenLiteSpeed sites also show which firewall rule blocked a request.

## 🔥 New Features

### 🆕 Nod Is Open to All Accounts, on Your Own Provider Too

Before, Nod was a beta that only some teams could see, and it needed an 8 GB xCloud Managed plan. Now every account except white-label teams can order it, on a managed plan from 6 GB or on a server from your own cloud account.

**Who it's for:** Anyone who wants their own personal AI assistant on a server they control.

-   Go to **New Server**, choose **Agentic** and then **Nod**. You can also pick Nod when you sign up or at checkout.
-   Nod runs on xCloud Managed servers and on servers xCloud creates in your Hetzner, DigitalOcean, Vultr, Linode, AWS, Google Cloud or Hostinger account. You can also connect a server from any provider.
-   Under **Server Size**, the smallest plan with 8 GB or more is marked **Recommended** and selected for you. Nod's own minimum is 8 GB RAM.
-   The 6 GB plan carries the label **Nod requires 8GB RAM**. You can still pick it, but Nod may run slowly or stop when memory runs out. Plans under 6 GB can't run Nod.
-   On your own provider, plans under 6 GB are no longer listed once you choose Nod. When you connect your own server, xCloud checks its memory and won't set up Nod if it has less than 6 GB RAM.
-   You can turn a server you already have into a Nod server with **Rebuild Server**, when it has at least 6 GB RAM and its plan includes AI agents.
-   Nod is still an early preview from n8n, so take a backup before each update.

[How to Deploy Nod by n8n on Your Own Server with xCloud](/docs/how-to-deploy-nod-with-xcloud/) · [How to Rebuild a Server Safely with xCloud](/docs/how-to-rebuild-a-server-with-xcloud/)

## 🧑‍💻 For Developers: Public API and MCP

-   **Nod servers:** the Public API accepts `stack: nod` on `POST /cloud-providers/{uuid}/servers` (a connected cloud account), `POST /servers/connect` (your own VPS) and server rebuild. The MCP tools built from the API, such as `servers_connect`, offer Nod too.
-   A plan or server under 6 GB RAM is refused with a 422 error.
-   The Enterprise API does not offer Nod. `POST /api/enterprise/v1.0/server` with `stack: nod` answers 403.

## ⚡ Improvements

-   **Firewall logs on OpenLiteSpeed:** OpenLiteSpeed sites now show a **7G Error Log** and an **8G Error Log** under **Site Monitoring → Logs** while the built-in firewall is on. Each entry shows the visitor IP, the request, the status and the rule that blocked it, as on Nginx sites. The **View Logs** link on the security page opens it. See [How To Enable 8G Firewall in xCloud](/docs/enable-8g-firewall-in-xcloud/).
-   **Server plans for AI agents:** on Linode, Vultr and Google Cloud, plans too small for Hermes Agent or OpenClaw are no longer listed. Before, they were listed and then refused when you created the server.
-   **AI assistant:** a long answer now opens at its first line, with your question at the top of the view. **Jump to latest** takes you to the rest. The thinking row is now one line tall, so the answer no longer shifts when it arrives.

## 🐞 Bug Fixes

**Cloudflare Enterprise**

-   Cloudflare Enterprise now moves with your domain when you migrate a site or a whole server. Your edge settings, SSL certificate and bandwidth stay the same.
-   Deleting the old site or server after a migration no longer cancels Cloudflare Enterprise for a domain the new site serves.
-   The **Domains** step of a server migration now shows a **Cloudflare Enterprise** section for each site that has it, so you know what will happen before you start.

**Nod**

-   Changing a Nod site's domain no longer fails when the new domain gets a Cloudflare multi-domain certificate.
-   Nod no longer says "This host is not permitted" after you restore a backup taken before a domain change.

**Backups**

-   Restoring a full backup from a storage bucket or SFTP into a site with the same domain now finishes. It no longer stops with "wp-config.php not found".

**Git deployment**

-   A deployment that was stopped part-way no longer puts back files you deleted later, such as a plugin you removed.
