# Xcloud — full content
> Every page of https://xcloud.host as clean markdown in one document. The per-page index is /llms.txt.
---
# xCloud — Host Anything. Deploy Anywhere.
> Managed hosting and server management for WordPress, Laravel, Node.js, Docker and AI agents. Deploy from Git in one click, bring your own cloud provider or ours, and run it all from one control panel.
Host anything. Scale infinitely. Manage with a panel or with AI agents.
Deploy WordPress, WooCommerce, Laravel, Node.js, n8n, AI tools and more from one
platform. Launch on your own cloud provider or on fully managed xCloud servers
in minutes.
- Start free: [https://app.xcloud.host/register](https://app.xcloud.host/register)
- Pricing: [/pricing/](/pricing/)
- Docs: [/docs/](/docs/)
- Support: [/support/](/support/)
## Choose how you want to host
| Option | What it is | Details |
| --- | --- | --- |
| xCloud Hosting | We provision and run the server for you. | [/managed-hosting/](/managed-hosting/) |
| Self-Managed Hosting | Connect your own Ubuntu server from any provider. | [/self-managed-hosting/](/self-managed-hosting/) |
| Managed Billing | White-label reselling with billing handled for you. | [/reseller-hosting/](/reseller-hosting/) |
Full plan details and prices: [/pricing/](/pricing/)
## A modern, accessible control panel
- **xCloud Public API** — automate server and site management programmatically.
- **Team Management** — roles and granular permissions. See [/docs/team-roles-permissions-in-xcloud/](/docs/team-roles-permissions-in-xcloud/).
- **Support for all the stacks you need** — WordPress, WooCommerce, Laravel, Node.js, Docker, static sites.
- **Site Security PRO** — firewall, hardening and malware protection. See [/site-security-pro/](/site-security-pro/).
- **xCloud Mail Delivery** — transactional email for your sites. See [/mail-delivery/](/mail-delivery/).
- **xCloud MailBox** — hosted mailboxes on your own domain. See [/mailbox/](/mailbox/).
## Ship straight from a Git repo
Connect your Git provider and deploy on push, with branch control and rollbacks.
- [/docs/how-to-integrate-a-git-provider-with-xcloud/](/docs/how-to-integrate-a-git-provider-with-xcloud/)
- [/docs/deploy-git-projects-in-one-click-with-xcloud/](/docs/deploy-git-projects-in-one-click-with-xcloud/)
## Tailored solutions
- [/hosting-for-wordpress/](/hosting-for-wordpress/) — Managed WordPress
- [/woocommerce-hosting/](/woocommerce-hosting/) — WooCommerce
- [/laravel-hosting/](/laravel-hosting/) — Laravel
- [/node-js-hosting/](/node-js-hosting/) — Node.js
- [/n8n-hosting/](/n8n-hosting/) — n8n automation
- [/openclaw-hosting/](/openclaw-hosting/) — OpenClaw AI agents
- [/hermes-agent-hosting/](/hermes-agent-hosting/) — Hermes agents
- [/one-click-apps/](/one-click-apps/) — One-click app catalogue
## xCloud AI Assistant
Manage servers and sites conversationally — provisioning, diagnostics and
routine operations handled by an assistant built into the panel.
## Faster performance, stronger security, fully managed
- **Enterprise-grade security** — [/docs/server-and-website-security-with-xcloud/](/docs/server-and-website-security-with-xcloud/)
- **High-performance infrastructure** — tuned web server, caching and NVMe storage
- **Reliability at half the cost** — [/pricing/](/pricing/)
## Global reach
31 datacenter locations worldwide. See [/docs/31-server-locations-worldwide/](/docs/31-server-locations-worldwide/).
## Built-in integrations
| Integration | Docs |
| --- | --- |
| Cloudflare | [/docs/using-xcloud-with-cloudflare-for-dns-management/](/docs/using-xcloud-with-cloudflare-for-dns-management/) |
| Git providers | [/docs/how-to-integrate-a-git-provider-with-xcloud/](/docs/how-to-integrate-a-git-provider-with-xcloud/) |
| Slack | [/docs/configure-slack-integration-in-xcloud/](/docs/configure-slack-integration-in-xcloud/) |
| WhatsApp | [/docs/how-to-configure-integration-with-whatsapp/](/docs/how-to-configure-integration-with-whatsapp/) |
| Google Drive | [/docs/google-drive-for-site-backup-xcloud/](/docs/google-drive-for-site-backup-xcloud/) |
| Mailgun | [/docs/configure-mailgun-for-site-emails/](/docs/configure-mailgun-for-site-emails/) |
| Object Cache Pro | [/docs/integrate-object-cache-pro-with-xcloud/](/docs/integrate-object-cache-pro-with-xcloud/) |
## Support
Real humans, expert engineers, live chat, 24/7/365. See [/support/](/support/).
## More
- Compare xCloud with other platforms: [/compare/](/compare/)
- Customer stories: [/case-studies/](/case-studies/)
- Reviews: [/reviews-and-testimonials/](/reviews-and-testimonials/)
- Blog: [/blog/](/blog/)
- Changelog: [/changelog/](/changelog/)
- Full page catalogue: [/llms.txt](/llms.txt)
---
# How to Get $100 Free Credit from Vultr & Use with xCloud - xCloud
> Learn how to get $100 free credit from Vultr while using xCloud. Bring your Vultr server in xCloud and enjoy seamless WordPress hosting & server management
Have you ever dreamt of a hassle-free and cost-effective WordPress hosting solution? Well, **xCloud** is here to give you the next-gen cloud hosting and server management experience. And not just that, partnering with [**Vultr**](https://www.vultr.com/), this solution brings you advanced features to bring your provider to xCloud and manage it effortlessly.
The best part? You can sign up for Vultr with the code ‘**XCLOUD25**’ and you will get **[$100 free credit from Vultr](/docs/how-to-get-free-hosting-with-vultr/)** & 6 months of FREE hosting.
But that is not all. In xCloud, upon new signups, you can create one server and host up to 10 sites for free using our **Bring Your Own Server** service. So, are you ready to elevate your WordPress hosting experience using Vltr at the most affordable price? Join xCloud today without any delay.
## **xCloud And Vultr Partnership: Get $100 Free Credits While Simplifying Your Hosting Experience**
xCloud’s partnership and seamless compatibility with Vultr take the complexity of hosting and server management. You can bring your own provider **_(Vultr)_** in xCloud & seamlessly manage your servers without any hassle directly from the xCloud dashboard. No need to bounce between xCloud and Vultr—everything you need is right there in your xCloud dashboard. It is hassle-free server management at your fingertips.
Along with that, the xCloud and Vultr partnership also makes hosting and server management all the more affordable for you. As mentioned earlier, you can get $100 free credit from Vultr and use it in xCloud to host your website for FREE for 6 months. Now, let us [**dive into the process**](/docs/how-to-get-free-hosting-with-vultr/) – it is pretty simple, all you need to do is follow some easy steps.
## **Step-by-step Guide: Get $100 Free Credit from Vultr Using xCloud**
We will show you how to set up your server effortlessly while saving big in just a few steps. No more pricey hosting fees, and get on board with a seamless solution that puts money back in your pocket. Let us get started.
### **Step 1: Sign Up in xCloud**
To kickstart, To get started, first, you have to sign up for xCloud. Simply put your credentials and get started.
### Step 2: Bring Your Own Provider (Vultr) in xCloud
Once you are logged in to your xCloud account, start your hosting journey by adding a new server. Simply head to your dashboard and hit the ‘**Create New Server**‘ button.
Next, you will see a list of available services. For this tutorial, opt for a Vultr server by selecting the Vultr option under ‘**Bring your own server service**.’ The best part? Billing for this server will be managed through your Vultr account, and with xCloud, there is **no charge for the first server**. It is that easy!
**Note:** Not only just Vultr, you can also bring other providers to xCloud, such as Digital Ocean and Google Cloud Platform & manage your servers without any hassle. Learn more **👇🏻**
- [How To Set Up a Server with Digital Ocean in xCloud?](/docs/how-to-setup-your-server-with-digital-ocean/)
- [How To Setup a Server With Google Cloud Platform in xCloud?](/docs/first-server-with-google-cloud-platform/)
### **Step 3: Signup in Vultr with xCloud Promo**
Now unlock your **6-month free** hosting offer by signing up on Vultr with the xCloud promo. Simply add your payment method and apply the ‘**XCLOUD25**‘ coupon during signup to claim your **$100** credit for the next six months. Do not miss out—seize the opportunity with the ‘**XCLOUD25**‘ coupon now.
**Note:** If you are already a Vultr user, feel free to skip this step and proceed to the next step to collect the API from Vultr.
#### **Collect API Key from Vultr**
Once you have set up your billing method, the next step is to collect your Vultr API key, which you will need to integrate with xCloud for free server and site management. Head over to your Vultr dashboard and navigate to the **Account → API tab**. From there, simply click on the ‘Enable API’ button.
Your **‘Personal Access Token’** will be automatically generated as shown below. Make sure to copy this API key/token.
Once you have obtained your API key, return to the xCloud dashboard, where you will need to add your Vultr Label and API key for seamless integration.
#### **Add Team Members in Vultr**
To grant your team members access to xCloud via Vultr, ensure they have the necessary permissions set up. This ensures smooth collaboration and usage.
#### **Add Vultr API Key in xCloud**
With xCloud, you can kickstart your server creation process without any initial investment. Simply navigate to the xCloud dashboard and click on ‘**Add New Serve**r’. This action will redirect you to the server selection screen, where you should choose ‘**Vultr**’ to proceed.
Once you have selected ‘Vultr’, input your details including the ‘**Key**’, ‘**Vultr Label**’, and most importantly, your ‘**Vultr API Key**’. Click on ‘Verify’ to finalize the setup and begin harnessing the power of xCloud seamlessly integrated with Vultr.
### **Step 4: Create a Vultr Server in xCloud**
Once your Vultr account is verified, the next step is to add additional details to set up a server using xCloud. From the user-friendly dashboard, you can select your preferred Region, Database Server, Server Size, and more—all in one convenient location.
Once you have filled in all the necessary information, simply click on ‘**Next**,’ and let xCloud take care of the rest. In just a few minutes, xCloud will automatically install and configure everything for you, making the process smooth and hassle-free.
## **Set Your Vultr Server in xCloud & Enjoy a $100 Free Credit**
xCloud offers the dream solution for and budget-friendly WordPress hosting & server management. Partnering with Vultr grants you six months of free hosting on their servers, and signing up with the code **‘**XCLOUD25**’** earns you $100 in free credits.
In xCloud, bringing any provider (e.g., Vultr) is easy; all you need to do is follow the above-mentioned steps. If you are ready to elevate your WordPress hosting & server management, join xCloud today. Hope the blog helps you; please **[subscribe to our blog](/blog/)** and join our [**Facebook community**](https://www.facebook.com/groups/724877699664138) to stay updated.
---
# How to Fix the 408 Request Timeout Error: 7 Easy Ways - xCloud
> Learn reasons behind 408 request timeout error of your website and multiple ways to fix them up both for server side and client side.
Has your website ever encountered a ‘**408 Request Timeout**’ error while browsing? If yes, it is frustrating, right? 408 request timeout error occurs due to delay or interruption between client-server communication. If the server does not respond within the anticipated time, the timeout error happens. In this blog, we will let you know the causes behind [**request timeout errors**](/docs/wordpress-memory-limit-exhausted-error/), and how you can fix these errors (both server-side & client-side) in several ways.
## **What Is the Request Timeout Error?**
The HTTP 408 error, also called the ‘**Request Timeout**’ error, happens when a server does not respond to a user’s request in time. This delay can happen due to having a slow network, too many requests on the server, or problems with the client’s internet connection.
In simple terms, the 408 Request Timeout means the server could not complete the request in the time it expected. This error can occur when people try to [**visit websites**](/guide-how-to-create-a-website/), use web applications, or make API calls, which can interrupt their experience.
For developers and server administrators, it is important to understand why this error happens and how to fix it. By addressing issues like slow networks or overloaded servers, they can improve the reliability and performance of web services, making the experience better for users.
## **The Reasons Behind 408 Request Timeout Error**
A bunch of reasons are behind the 408 request timeout error. Among many of them, the following are the more basic and important ones you need to consider:
**1\. Connection Issues:** Users might have slow or unstable internet connections that can delay sending requests, leading to timeouts.
**2\. Inaccurate URLs:** Mistyped or unavailable URLs can confuse the server, wasting time and causing communication breakdowns that trigger the 408 error.
**3\. Web Server Configuration Errors:** Wrong server settings or not enough resources can slow down request processing, which may result in timeouts and the 408 error.
**4\. Application-Level Problems:** Slow algorithms, database queries, or heavy processes in the application code can cause delays, leading to timeouts and 408 errors.
**5\. Server Overload:** When servers get too many requests at once, they may struggle to handle them quickly, leading to delays or timeouts and causing the 408 error.
As you know why this error occurs, you may be interested to learn how you can fix it. While you can not fix users’ internet connection and other above-mentioned things, the following are a few solutions that you opt for.
## **7 Easy Solutions to Fix 408 Request Timeout Error**
Source: [**KeyCdn**](https://www.keycdn.com/support/408-request-timeout)
All the following solutions are classified into two categories: **client-side solutions and server-side solutions**. Let us start by fixing suggestions for client-side errors.
### **1\. Check the URL Properly**
You need to make sure all your website URLs are without **typos, missing parts, or outdated links**. For any reason, if the URL is wrong, the server might not find the right resource and could time out which leads to a 408 request timeout error. By properly checking and fixing any kind of mistakes in the URL, you can easily solve the issue.
### **2\. Check the Platform’s Status**
When you get a 408 request timeout error specifically on a website or platform, you need to check if the platform has any specific issues. To do the check, you can visit their status page or check their official support channels to see if they have reported any problems. If it is an issue on their end, you may need to wait for them to fix it.
### **3\. Undo Recent Changes**
Sometimes, recent updates or changes to your system can cause conflicts that lead to a 408 error. That is where you need to think about undoing recent changes like software updates, server setting adjustments, or network changes. This can help you figure out if those changes are causing the 408 request timeout error.
### **4\. Remove New Plugins, Modules, or Extensions If There Any**
Plugins, modules, or extensions you have added to your web browser can cause conflicts that lead to 408 request timeouts. You need to disable or temporarily uninstall any new additions you have recently updated or installed.
By doing so, you can have an understanding or determine if these components are causing the 408 error. If the error remains after uninstalling them, please consider finding updated versions or alternative solutions to achieve the same functionality.
Now, let us move to the server-side suggested fixes for the 408 request timeout error. From configuring the server, and examining the logs to debugging the code or script— could be suggested fixes from the server side.
### **5\. Ensure the Server Is Properly Configured**
To fix the 408 request timeout error from the server end, you need to make sure that your server is properly set up to handle incoming requests and respond within the expected time. Plus, check the server’s settings, focusing on resource allocation, connection limits, and timeout values.
After that, adjust these settings as needed to improve performance and handle the expected workload. For more details, refer to the server software’s documentation or support resources.
### **6\. Check the Server Logs**
To understand the 408 request error better, look carefully at the server logs. With the logs, you can have a look at which requests timed out and help identify patterns or common issues. Moreover, catches any error messages, warnings, or signs of slow performance. Analyzing the logs can help you find the root cause and guide you toward a solution.
### **7\. Debug the Applications’ Code or Script**
In some cases, potential bugs may slow down request processing— that is why you need to review any custom scripts or code. Also, look for inefficiencies, long processes, poorly optimized database queries, or anything else that could cause timeouts. Moreover, use performance profiling, logging, or debugging tools to find and fix these issues.
## **Effectively Fix 408 Request Error & Boost Website Performance**
The 408 Request Timeout error can happen for various reasons on both the client and server sides. Understanding these causes is key to fixing the problem quickly. By knowing what triggers this error and applying the right solutions, you can reduce its frequency. Ultimately, it leads to a better user experience and smoother communication between clients and servers.
If you want to read more blogs like this one to fix error issues, [**subscribe to our blogs**](/blog/). And join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to connect people with common interests.
---
# 7 Best Hosting for Lovable Apps in 2026 : Deploy Vibe-Coded Apps Faster (Tested & Benchmarked) - xCloud
> Find out the best hosting for Lovable apps in 2026. Compare speed, pricing, free tiers, and simple deploy options tested in real benchmarks.
[**Self-hosting**](/lovable-hosting/) your Lovable apps on xCloud delivers **97–99% GTmetrix** performance scores at a fraction of Lovable Cloud’s cost, while Cloudflare Pages stands out with the best free tier, offering unlimited bandwidth.
As **vibe coding** evolves from prototype to production, industry experts increasingly recommend moving away from credit-based hosting models toward predictable, flat-rate alternatives.
The vibe coding revolution is reshaping how developers build applications **92% of US developers** now use AI coding tools daily (Second Talent) and Lovable reached **$20M ARR** in just 60 days, making it Europe’s fastest-growing startup. (Vestbee) But as projects scale beyond the MVP stage, the limitations of Lovable Cloud’s credit system create friction that sends users searching for alternatives.
We have analyzed the seven best hosting options for Lovable apps in 2026, with verified pricing, real performance benchmarks, and deployment workflows tested by the xCloud team.
## **TL;DR: Quick decision matrix For Choosing the right Lovable hosting alternatives**
A quick comparison to identify the best hosting option based on cost, performance, developer experience, and scalability – from prototypes to production and agency workflows.
**Rank**
**Provider**
**Starting Price**
**Why Choose**
**Best For**
🥇
xCloud
$5/mo (FREE tier available)
Fastest performance, unlimited apps, any cloud provider
**Best Overall**
🥈
Cloudflare Pages
$0
Unlimited bandwidth, 330+ global PoPs
**Best Free Tier**
🥉
Vercel
$0 (Hobby) / $20/mo Pro
Native Next.js, zero-config deploys
**Best Developer Experience**
**4**
Netlify
$0 / $20/mo Pro
Built-in forms, identity, A/B testing
**Best Form Handling**
**5**
Render
$7/mo
Intuitive UI, managed PostgreSQL
**Best Clean Interface**
**6**
Railway
$5/mo
Instant databases, environment variables
**Best Full-Stack**
**7**
Lovable Cloud
$25/mo credits
One-click, no configuration
**Simplest Setup**
## **Why Lovable Users Are Switching to Self-Hosted Alternatives**
Lovable Cloud is popular for its one-click deployment and $25/month in free cloud credits per workspace. For rapid prototyping, it works well. However, as real-world usage grows, many [**Lovable**](https://lovable.dev/) users report friction that pushes them to explore self-hosted Lovable alternatives.
Across Reddit, Trustpilot, and Medium, developers consistently cite cost unpredictability, deployment issues, and scalability limits as key reasons for switching.
### **Credit system frustrations compound quickly**
The credit-based model creates unpredictable costs. Simple changes like editing button colors consume 0.5 credits, while adding authentication uses 1.2 credits. Users report burning through 100+ credits fixing AI-generated errors each “Fix” attempt costs credits even when the bug originated from Lovable’s side.
One Reddit user summarized the frustration: “I put myself into chat mode, asked a couple of questions and made a manual edit to one word… suddenly I’m down to 3/5 daily credits.” The free tier caps at 5 credits per day (30/month maximum), and there’s no top-up option -you must upgrade plans entirely.
### **Lovable 2.0 deployment issues persist**
Since the 2.0 update, users have reported deployment failures where changes don’t push to production. Comments describe the system as “stuck serving old commits” regardless of code changes. UI quality reportedly degraded compared to 1.0, with users noting that identical prompts produce inferior designs.
### **Why flat-rate hosting solves these problems**
Self-hosted alternatives eliminate credit anxiety entirely. With xCloud’s $5/month flat rate (or completely free tier), agencies and builders can deploy unlimited Lovable apps limited only by server resources – not artificial credit caps. The xCloud approach means predictable costs, whether you deploy 1 app or 100.
### **Comparison Between The Lovable Hosting Providers**
Provider
Free Tier
Paid Price
Bandwidth
Performance
Best For
**xCloud**
✅ 1 server, 10 sites
$5/server/mo
Unlimited\*
97–99% GTmetrix
Agencies, unlimited apps
**Cloudflare Pages**
✅ 500 builds/mo
$5/mo (Workers)
Unlimited
31–53ms TTFB
Global performance
**Vercel**
✅ 100GB, 100 deploys/day
$20/user/mo
1TB
22–60ms static
Next.js apps
**Netlify**
✅ 100GB, 300 build min
$20/member/mo
1TB
Variable
Form-heavy sites
**Render**
✅ Sleeps after 15 min
$7/mo (Starter)
100GB
Standard
Backends, databases
**Railway**
✅ $5 trial credit
$5/mo (Hobby)
Usage-based
Standard
Full-stack
**Lovable Cloud**
✅ $25/mo credits
Usage-based
100GB
Standard
Zero-config
\*xCloud bandwidth depends on your cloud provider (DigitalOcean, Vultr, AWS, etc.)
### **1\. 🥇xCloud – Best for Performance and Unlimited Apps**
**Starting at:** $5/month
**Free tier:** Available
xCloud fundamentally changes [**Lovable hosting**](/lovable-hosting/) economics by replacing credit-based billing with flat-rate pricing. You deploy Lovable apps on your own cloud infrastructure or xCloud’s managed servers and host unlimited applications per server, constrained only by compute resources.
### **xCloud Pricing Breakdown**
**Plan**
**Price**
**Servers**
**Sites**
**Key Features**
Free
$0
1
10
Limited Features
Starter
$5/server/mo
1-5
Unlimited
Full features
Professional
$4/server/mo
6-10
Unlimited
Volume discount
Agency
$3/server/mo
11+
Unlimited
Enterprise scale
For managed servers, xCloud offers plans from $5/month (Newcomer: 1GB RAM, 25GB SSD) to $395/month (Quantum: 58GB RAM, 1TB NVMe). Premium plans feature high-frequency 3GHz+ Intel Xeon CPUs and NVMe storage.
## **Why Agencies Choose xCloud**
For agencies managing multiple Lovable projects, xCloud removes the operational headache of credit allocation. Instead of tracking usage per workspace, all apps deploy to a single server with one predictable monthly cost.
User reviews on Trustpilot consistently highlight performance gains: **97-99% GTmetrix** performance scores and servers running approximately **40% cheaper** and faster than Cloudways.
### **Key Features**
- **Multi-cloud provider support**: DigitalOcean, Vultr, AWS, Google Cloud, Hetzner, including xCloud Managed Server
- **Free SSL certificates** via Let’s Encrypt for every application
- **Push-to-deploy** with GitHub integration
- **One-click Supabase deployment** for your Lovable backend
- **White-label options for agencies** reselling hosting services
Best for: Agencies, builders, and teams wanting unlimited apps with predictable costs,
making it ideal for high-iteration workflows and long-term production deployments.
Visit the [page](/lovable-hosting/) to learn more.
## **2\. 🥇Vercel – Best Developer Experience**
**Starting at: $0 (Hobby) / $20/user/month (Pro)**
Vercel pioneered the modern frontend deployment experience, and their infrastructure excels for React applications the core of every Lovable project. The platform delivers **22–60ms static TTFB** and virtually eliminates cold starts with their Fluid Compute technology.
### **What Vercel does exceptionally well**
The Hobby tier provides generous allowances: **100GB bandwidth, 100 hours of build execution, and 1 million function invocations** monthly. Preview deployments generate automatically for every pull request, enabling rapid iteration on Lovable projects.
Vercel’s **Fluid Compute** (released 2025) keeps at least one serverless function instance warm, achieving **99.37% zero cold starts**. For Lovable apps with API routes or server-side rendering, this translates to consistently snappy responses.
### **Pricing considerations**
**Plan**
**Price**
**Bandwidth**
**Build Hours**
**Best For**
Hobby
$0
100GB
100/mo
Side projects
Pro
$20/user/mo
1TB
Included
Teams, production
Enterprise
Custom
Custom
Custom
Scale, compliance
Pro plans include a **$20 credit** applied toward usage-based resources. Overage pricing runs **$0.60 per million function invocations** and bandwidth charges for traffic spikes.
### **Limitations for Lovable projects**
Vercel optimizes for Next.js applications. While Lovable generates standard React/Vite projects, you’ll need additional configuration compared to Next.js’s zero-config deployment. Vercel also lacks built-in form handling and authentication features you’ll need to implement via Supabase or third-party services.
Best for: Developers wanting a premium DX, teams already using [Next.js](http://next.js), and production apps that require near-zero cold starts and consistent performance.
### **3\. 🥉Cloudflare Pages – Best Free Bandwidth**
**Starting at:** $0 (unlimited bandwidth included)
[**Cloudflare**](https://www.cloudflare.com/) Pages offers the most generous free tier in the industry: unlimited bandwidth with no egress charges, ever. Combined with their 330+ global edge locations, Cloudflare delivers consistently fast performance worldwide benchmarks show 31–53ms TTFB for edge functions globally.
### **The unlimited bandwidth advantage**
Most platforms charge $40–150 per 100GB of bandwidth overages. Cloudflare’s pricing model eliminates this variable entirely. For Lovable apps with unpredictable traffic—viral launches, Product Hunt features, unexpected press coverage – Cloudflare provides insurance against surprise bills.
Free tier specifications
Resource
Free Limit
Paid ($5/mo)
Bandwidth
Unlimited
Unlimited
Build Minutes
500/month
500+
Requests
100,000/day
10M/month
Workers KV Reads
100,000/day
10M/month
Concurrent Builds
1
Multiple
### **Performance benchmarks prove the edge advantage**
Bejamas’ January 2025 testing revealed Cloudflare Workers’ dominance for edge computing:
Region
Cloudflare TTFB
Vercel TTFB
Netlify TTFB
US-West
40ms
1,425ms
210ms
EU-Central
33ms
387ms
106ms
Singapore
35ms
189ms
92ms
Japan
31ms
1,523ms
291ms
For globally distributed users, Cloudflare’s architecture delivers **9x faster cold starts** than traditional serverless functions.
### **Considerations for Lovable apps**
Cloudflare Pages works best for static sites and edge-first architectures. If your Lovable app requires traditional Node.js serverless functions, you’ll use Cloudflare Workers instead—still fast, but requires adapting to their edge-first programming model. Database options are limited to D1 (SQLite-based) or external connections.
Best for: Cost-conscious builders, global audiences, static-heavy Lovable apps, protection against traffic spikes
### **4\. Netlify – Best for Form Handling**
**Starting at:** $0 / $20/member/month (Pro)
Netlify pioneered JAMstack deployment and remains a strong choice for content-focused Lovable applications. Their killer feature: built-in form handling without backend code. Simply add the Netlify attribute to HTML forms and the submissions route automatically.
### **Unique features other platforms lack**
Beyond forms, Netlify offers Netlify Identity for authentication (useful if you’re not using Supabase), native A/B split testing, and extensive build plugins for customization. These integrated features reduce external dependencies for simpler Lovable projects.
### **Pricing Structure**
Netlify transitioned to credit-based pricing in September 2025. Legacy customers retain previous plans, but new users face a system where deployments, bandwidth, and forms all consume credits:
**Action**
**Credit Cost**
Production Deploy
15 credits
Bandwidth (per GB)
10 credits
Form Submission
1 credit
Compute (per GB-hour)
5 credits
Free plans receive 300 credits/month (hard limit – sites pause when exhausted). Pro plans get 3,000 credits/month with $10 per 1,500 additional credits.
### **Performance variability matters**
Bejamas benchmarks revealed significant regional inconsistency. Netlify achieved 7ms TTFB in US-East but 2,406ms in EU-Central Germany, a 340x variance. For globally distributed audiences, this unpredictability may impact user experience.
**Best for:** Marketing sites, contact forms, A/B testing, teams wanting integrated identity management
### **5\. Render – Best Clean Interface**
**Starting at:** $7/month (Starter web service)
Render earned its reputation through simplicity. The dashboard presents clear options without overwhelming configuration panels, making it approachable for vibe coders who aren’t infrastructure specialists.
### **Straightforward pricing model**
Unlike credit-based systems, Render charges predictable amounts per service type:
**Service**
**Starter Price**
**What You Get**
Web Service
$7/month
512MB RAM, 0.5 CPU
PostgreSQL
$6/month
256MB, managed
Redis
$10/month
256MB cache
Background Worker
$7/month
Async processing
Cron Job
$1/month
Scheduled tasks
For Lovable apps requiring backends beyond Supabase, Render’s **managed PostgreSQL** provides a clean alternative with point-in-time recovery and automated backups. (Render)
### **Free tier limitations**
Render’s free tier carries significant constraints: web services **sleep after 15 minutes of inactivity** (causing cold start delays) and free PostgreSQL databases **delete after 30 days**. For anything beyond demos, paid plans become necessary quickly.
### **Real-world cost savings**
A case study from ShowZone documented their migration from Vercel to Render, reducing costs from **$800/month to $40/month** for a large Next.js application. For apps with predictable, steady traffic patterns, Render’s pricing model often wins economically.
**Best for:** Backend-heavy Lovable apps, teams wanting managed databases, developers valuing interface simplicity
### **6\. Railway – Best for Full-Stack**
**Starting at:** $5/month (Hobby)
Railway positions itself as “Heroku’s modern replacement” with one-click database provisioning and automatic framework detection. Deploy your Lovable app and spin up PostgreSQL, Redis, or MongoDB alongside it – no configuration files required.
### **The credit timeline matters**
Railway’s pricing history reflects the broader PaaS industry’s struggle with sustainability:
Date
Change
Pre-2023
$5 recurring monthly credits
August 2023
Removed recurring credits
August 2025
Restored limited free plan ($1/month non-rollover)
### **Current pricing:**
**$5/month Hobby** plan includes $5 usage credit. If usage stays under $5, you pay nothing beyond the subscription. (Railway) The **$5 trial credit** for new users is one-time, not recurring. (Railway)
### **Why backend-heavy apps belong here**
Railway shines when your Lovable project needs more than Supabase provides. Their **Railway Metal** infrastructure (own data centers, not GCP) means predictable performance without cloud provider markup. Environment variables are managed through a clean UI, and PR preview environments spin up automatically.
Best for: Full-stack apps needing multiple databases, teams wanting Heroku-style simplicity, projects outgrowing Supabase
### **7\. Lovable Cloud – Best for Simplicity (but Limited)**
Starting at: $25/month free cloud credits (included with all workspaces)
Lovable Cloud offers the path of least resistance: click deploy, and your app goes live on a \*.lovable.app domain. Every workspace receives $25/month in free cloud credits (separate from the message credits for building).
### When Lovable Cloud makes sense
For rapid prototyping and validating ideas, the integrated deployment eliminates friction entirely. You’re already in the Lovable building – one click extends to hosting. Custom domains work on Pro plans ($25/month), and the Supabase backend is pre-configured.
### Why power users migrate away
The credit model creates anxiety at scale. Building credits (for prompting the AI) and cloud credits (for hosting) operate separately, but both can deplete unexpectedly. When cloud credits are exhausted, you either top up manually, enable auto-top-up with spending caps, or your projects pause.
More critically, once you migrate your project to your own Supabase instance, Lovable can no longer sync changes. The one-way migration means local IDE development becomes mandatory post-export – Lovable becomes a code generator rather than an ongoing development environment.
### Pricing reality check
Plan
Subscription
Message Credits
Cloud Credits
Free
$0
5/day (30/mo max)
$25/mo
Pro
$25/mo
100+5/day
$25/mo
Business
$50/mo
100+5/day
$25/mo
The $25/month covers light usage. Production apps with moderate traffic often exceed this quickly, triggering usage-based billing.
## **Cost Comparison: Credit-Based vs Flat-Rate Hosting**
The fundamental pricing question, do you prefer predictable costs or pay-per-use flexibility?
**Hosting Model**
**Providers**
**Monthly Cost (10 apps)**
**Cost Predictability**
Credit-Based
Lovable Cloud
$25+ (varies with usage)
❌ Variable
Credit-Based
Netlify Pro
$20+ credits overage
❌ Variable
Usage-Based
Vercel Pro
$20+ overages
⚠️ Mostly predictable
Usage-Based
Railway Hobby
$5–50+ (resource dependent)
⚠️ Usage dependent
Flat-Rate
xCloud Starter
$5 fixed
✅ Predictable
Flat-Rate
Cloudflare Pages
$0 – 5 fixed
✅ Predictable
Per-Service
Render
$7+ per service
✅ Predictable
For agencies managing multiple Lovable projects, xCloud’s unlimited apps model provides the clearest economics: $5/month covers everything regardless of how many applications you deploy.
## **How to Deploy Lovable to xCloud in 3 Steps**
Migrating from Lovable Cloud to xCloud takes under 10 minutes. Here’s the complete workflow:
### **Prerequisites**
- Lovable project synced to GitHub (Settings > GitHub Integration)
- xCloud account (free tier works)
- Server provisioned (xCloud managed or your own VPS)
### **Step 1: Clone Your Repository**
- Log into your xCloud dashboard
- Click “New Site” button
- Select your server from the dropdown
- Navigate to the “Lovable” tab
- Choose “Clone A Git Repository”
### **Step 2: Configure Site Settings**
- Enter your custom domain (or use xCloud’s subdomain)
- Select Node.js version matching your project and site user
- Select either Connected Git Provider (recommended for private repos) or Public Repository (paste HTTPS URL) or Private Repository (paste SSH URL)
### Step 3: Deploy and Go Live
- Toggle “Enable push to deploy” for automatic deployments
- Click “Start” to begin initial deployment
- Access your live site via the “Visit Site” button
Future code pushes deploy automatically. xCloud handles SSL certificates, server optimization, and CDN configuration.
## **Frequently Asked Questions**
### **What is vibe coding and why does hosting matter?**
Vibe coding is an AI-assisted development approach coined by Andrej Karpathy in February 2025, where developers describe goals in natural language and AI generates the code. (Medium) The approach has achieved **92% adoption among US developers** and powers **25% of Y Combinator W25 startups** with 95%+ AI-generated codebases. Hosting matters because vibe-coded apps often need rapid iteration – credit-based systems can throttle development velocity.
### **Can I host Lovable apps for free?**
Yes. **Cloudflare Pages** offers unlimited free bandwidth with 500 builds/month. **xCloud’s free tier** includes 1 server and 10 sites. **Vercel Hobby** provides 100GB bandwidth and 100 daily deploys. **Lovable Cloud** itself includes $25/month in free hosting credits.
### **What happened to Fly.io’s free tier?**
Fly.io deprecated all legacy plans in October 2024, moving exclusively to Pay As You Go. New accounts receive only a limited 7-day trial or 2 hours of machine runtime. Legacy users (pre-October 2024) retain their free allowances, but the era of generous Fly.io free hosting has ended.
### **Why did Railway remove its free tier?**
Railway eliminated recurring $5 monthly credits in August 2023 due to unsustainable margins; they reported losing $16 for every $1 of revenue on unlimited compute plans. After achieving profitability through their own data center infrastructure, they restored a limited free plan in August 2025, offering $1/month non-rollover credits.
### **How do Lovable Cloud credits work?**
Lovable operates two separate credit systems: **message credits** for AI prompting while building (5/day free, 100/month on Pro), and **cloud credits** for hosting deployed apps ($25/month included). When cloud credits deplete, projects pause until you add funds or enable auto-top-up.
### **What’s the best hosting for Lovable agencies?**
Industry experts recommend **xCloud** for agencies due to its unlimited apps per server model. At $5/month per server, agencies can deploy dozens of client projects without per-app fees. The white-label options and multi-cloud provider support add flexibility for client requirements.
### **How fast should a Lovable app load?**
Google’s Core Web Vitals define good performance as **TTFB under 200ms, LCP under 2.5 seconds, and page load under 2 seconds**. Cloudflare Pages achieves **31 – 53ms edge TTFB** globally, while Vercel delivers **22–60ms for static content**. xCloud users report **97–99% GTmetrix scores** with properly optimized servers.
### **Can I use Supabase with self-hosted Lovable?**
Absolutely. Export your Lovable project to GitHub, deploy to xCloud or any platform, and connect to Supabase via environment variables (**VITE\_SUPABASE\_URL**, **VITE\_SUPABASE\_PUBLISHABLE\_KEY**). xCloud offers **one-click Supabase deployment** as an alternative to Supabase’s hosted service.
### **What’s the Lovable tech stack?**
Lovable generates **React + Vite + Tailwind CSS** frontends with **Supabase** backends (PostgreSQL, authentication, storage, edge functions). The code exports as standard TypeScript/JavaScript deployable to any Node.js hosting platform.
### **Is self-hosting Lovable apps difficult?**
Not with modern platforms. xCloud’s 3-step process (clone, configure, deploy) takes under 10 minutes. Vercel and Netlify offer similar Git-based deployment. The key requirement: sync your Lovable project to GitHub first, then any platform can pull and deploy automatically.
### **Which hosting has the best uptime?**
Enterprise tiers across major platforms offer **99.99% SLA guarantees** (Vercel, Netlify, Cloudflare). For self-managed hosting, uptime depends on your infrastructure choices. xCloud’s managed servers include monitoring and automated recovery, while bring-your-own-server deployments rely on your provider’s SLA.
### **How do I migrate from Lovable Cloud to xCloud?**
Enable GitHub integration in Lovable (Settings → GitHub), then follow xCloud’s deployment process. Important note from Lovable’s documentation: after migrating to your own Supabase instance, changes made in Lovable will **NOT sync** with your new setup – development continues in your local environment or IDE.
## **Conclusion: The Optimal Lovable Hosting Stack for 2026**
The vibe coding revolution demands hosting infrastructure that scales with creativity rather than constraining it. Credit-based systems made sense for experimentation; production deployments deserve predictable economics.
**For maximum performance and unlimited scaling**, xCloud delivers the strongest value proposition—flat-rate pricing, multi-cloud flexibility, and demonstrated **97–99% GTmetrix performance**. Agencies and prolific builders particularly benefit from deploying unlimited apps without per-project fees.
**For zero-budget launches**, Cloudflare Pages’ unlimited free bandwidth eliminates surprise bills entirely, backed by the industry’s fastest edge network at **31–53ms global TTFB**.
**For developer experience purists**, Vercel’s polish and near-zero cold starts (99.37% with Fluid Compute) justify the $20/month Pro plan for production applications.
**For backend complexity**, Railway and Render provide managed database hosting that extends beyond Supabase’s model when projects demand it.
The platforms that will dominate vibe coding infrastructure share common traits: **code ownership, export flexibility, and predictable pricing**. As AI-generated codebases become production systems rather than prototypes, hosting decisions increasingly impact both velocity and economics.
Industry experts recommend starting with xCloud’s free tier or Cloudflare Pages for initial deployment, then evaluating needs as traffic patterns emerge. The best hosting for your Lovable app ultimately depends on your specific requirements – but the era of accepting credit-based constraints as the only option has definitively ended.
---
# About Us | xCloud
> Find out about us - the team behind xCloud and find out why we created this next-gen WordPress hosting and server management solution.
## About Us
# xCloud: Next-Gen Hosting &
Server Management Solution
Even with countless products and services available in the industry, setting up a cloud server, hosting a website, and later managing the deployed sites has never been simple – especially if you are managing multiple websites at a time. And that’s where the idea of a streamlined hosting and server management system that’s accessible to all came to form.
## xCloud: Next-Gen WordPress Hosting & Server Management Solution
After years of working hard to bring our vision live, **xCloud** simplifies cloud hosting and server management for WordPress, providing you with full control over your websites and **redefining** the way you host, build, and deploy websites!
## xCloud: Next-Gen WordPress Hosting & Server Management Solution
With this next-gen cloud hosting for WordPress, no need for any coding expertise when it comes to server configuration and website management. So, bid farewell to manual setup as here at xCloud, we have got all your hosting and management needs covered with a hassle-free, lightning-fast experience like never before
## Team xCloud
## M Asif Rahman
Founder
## Nazmul Hasan Rupok
Co-Founder
## Afshana Rahman Diya
Co-Founder
## Nasir Nobin
Co-Founder
## Shahjahan Jewel
Partner
## AR Rana
Lead Engineer
## Mishuk Adhikari
Lead Engineer
## Bashar Bhuiyan
Senior Software Engineer (AI/ML)
## Mohammad Shifat Hossain
Lead Support & Product Manager
## Faisal Ibn Aziz
Senior Software Engineer
## Md. Arifur Rahman
Senior Software Engineer
## Nabil Ahmed Emon
Lead Product Designer
## Tasnia Rahman Raima
Deputy Marketing Manager
## Shariful Islam Shaikat
Senior Frontend Developer
## Md. Al-Mosabbir Rakib
Software Developer
## Abir Hasan Dipu
Senior Technical Support Engineer
## Abu Hurayra
Application Security Engineer
## Ashik Hossain Maruf
Motion Designer
## Charina Acuar
Technical Support Engineer
## Easin Arafat
Application Security Engineer
## Esrat Sultana Popy
Frontend Developer
## Fahim Raihan Anando
Product Designer
## Imran Hossain
Motion Designer
## Jan-Jan Garduce
Technical Support Engineer
## Kawser Ahmed Khan Jami
Content Marketing Executive
## Mohaiminul Islam
Creative Designer
## Nazmus Sadat
Technical Support Engineer
## Reduan Masud
Software Test Engineer
## Sadman Akib
Senior Cloud Support Engineer
## Sazzadur Rahman
Frontend Developer
## Shah Newas Mazumder
UX UI Designer
## Sherajus Salekin
Technical Support Engineer
## Towfique Ahmed
Content Marketing Executive
---
# Accessing Your Site Database Easily with Adminer in xCloud: No Code Guide - xCloud
> Adminer in xCloud presents a simplified approach to accessing website databases, eliminating the need for manual database connections.
[**Adminer**](https://www.adminer.org/) is a popular database management tool, often compared to phpMyAdmin. It allows users to manage their databases through a simple and intuitive interface, making tasks such as **browsing, querying, and editing databases** more accessible to users without extensive technical knowledge.
Adminer in xCloud provides a more straightforward approach to accessing website databases, eliminating the need for manual database connections. Today we will learn how to access your site with [**Adminer in xCloud**](/docs/access-site-database-using-adminer-xcloud/).
## **How Adminer Functions & Handles Your Database?**
But before we get into the step-by-step guide on how you can access your site database using Adminer in xCloud, it’s important you understand what Adminer is in more depth.
Overall, as mentioned above, Adminer simplifies the process of managing databases, making it a handy tool for developers, database administrators, and anyone else who needs to interact with databases regularly. How? Let’s dive in deeper to find out.
### **Database Connection**
Adminer facilitates database management by establishing a connection to your chosen database system. Users typically input the necessary connection details such as **host, port, username, password, and database name**.
Once connected, Adminer provides a unified interface for interacting with the database.
### **Database Structure Management**
**Viewing Database Structure:** Adminer allows users to view the structure of their databases, including tables, indexes, fields, and keys.
**Creating and Modifying Tables:** Users can create and modify tables within their databases directly through Adminer. This includes defining fields, setting primary keys, and specifying indexes.
**Dropping Tables:** Adminer enables users to drop tables from their databases when necessary, helping to manage database structure efficiently.
### **Data Manipulation**
**Browsing Data:** Users can browse the data stored in their database tables, viewing individual records and their corresponding fields.
**Inserting, Updating, and Deleting Data:** Adminer allows users to insert new records, update existing ones, and delete unwanted data from their database tables.
**Querying Data:** Users can execute custom SQL queries within Adminer to retrieve specific information from their databases, providing flexibility in data manipulation.
### **Database Import and Export**
**Importing Data:** Adminer and [**Adminer plugin**](https://www.adminer.org/en/plugins/) supports importing data into databases from various file formats such as SQL, CSV, Excel, and XML. This feature streamlines the process of transferring data into the database.
**Exporting Data:** Users can export data from their databases to different formats for backup, analysis, or sharing purposes. Adminer offers options to customize the export format and select specific tables or data subsets.
### **User Management**
Depending on the database system, Adminer may provide functionality for managing database users, privileges, and permissions. This allows administrators to control access to the database and ensure data security.
### **Customization**
Adminer offers some level of customization through plugins and themes. Users can enhance the functionality or change the appearance of the Adminer interface according to their preferences.
### **Security Considerations**
Adminer emphasizes security by providing options to enable or disable access to the tool as needed. Additionally, users are encouraged to follow best practices for securing database connections and permissions.
By offering these features and functionalities, Adminer simplifies the process of managing databases, making it a valuable tool for developers, database administrators, and other professionals working with databases.
## **Easy Guide to Access Site Database with Adminer in xCloud**
**Adminer in xCloud** provides a streamlined approach for accessing site databases, eliminating the need for a manual database connection. While SSH connections offer enhanced security measures, we recommend enabling Adminer only when deemed essential.
Below, we will walk you through the step-by-guide on how you can easily enable Adminer in xCloud and use it to access and manage your website’s database in a few clicks.
### **Step 1: Enable Adminer In xCloud From Dashboard**
First, log in to xCloud with your credentials. Then access your xCloud site dashboard and go to **Access Details → Database**. Adminer is deactivated in the default state.
Click on the ‘**Enable Adminer**‘ button to activate it, then click on the ‘**Launch Adminer**‘ button to open the Adminer dashboard.
### **Step 2: Manage Your Database In Adminer**
Once you’ve enabled and launched Adminer from your xCloud dashboard, you can effortlessly oversee your database tasks. This includes executing SQL commands, importing/exporting data, creating tables, and more.
### **Step 3: Run Command**
Within the Adminer dashboard, users can easily manage their database content using CRUD (Create, Read, Update, Delete) commands. They can effortlessly create new records, browse through existing data, update records to reflect changes, and delete unwanted entries, providing complete control over their database content in a streamlined and user-friendly manner.
### **Import/Export SQL Files**
Importing your existing database into Adminer is a straightforward process that begins with accessing the interface and locating the import feature. Once you’ve navigated to the appropriate section, typically found under the database management options, you’ll be prompted to select the file containing your database data.
With just a few clicks within the Adminer interface, you can export your database and select output options, format, database type, tables, data, and more.
Indeed, managing databases using Adminer in xCloud is incredibly simple and user-friendly.
### **Configure Site Database Using Adminer In xCloud**
Verifying your permissions is essential to ensure you have access to your website’s site management database as a team member. Ensure you are your team’s admin or have legitimate access. If you currently lack access to your team, kindly request your team’s administrator to enable it in the ‘Team Management’ section accessible from your dashboard. However, you automatically possess this access by default if you serve as the Team Admin.
## **Simplify Your Database Management With xCloud**
Adminer streamlines the complexities of database management by offering a comprehensive suite of features within a user-friendly interface. From establishing database connections to performing data manipulation tasks and ensuring security measures. With its flexibility, customization options, and emphasis on security, Adminer stands as a valuable tool for developers and database administrators alike, facilitating seamless database management across various projects and environments.
Did you find this blog helpful? If you do, please [**subscribe to our blog**](/blog/), and don’t forget to join our [**Facebook Community**](https://www.facebook.com/groups/724877699664138) to get our daily updates.
---
# How to Add HTTP Headers And Redirects in WordPress (Without Plugins) - xCloud
> Learn how to manage WordPress HTTP Headers and Redirects efficiently with secure, fast, and reliable server-level rules - no nginx expertise required.
Adding HTTP headers and setting up redirects is one of those tasks every WordPress site needs at some point. You want to add a security header. Or redirect an old URL to a new one. Or send mobile users to a different page. These are everyday requirements for any site that takes performance and security seriously.
The traditional approach? Edit your nginx config file, run a syntax test, reload the server, and hope nothing breaks. Or install a plugin and accept the extra PHP overhead on every request.
Neither option is ideal, especially if you are managing multiple WordPress sites across different clients or projects.
That is where xCloud’s [**Site Rules**](/docs/how-to-create-and-manage-site-rules/) feature comes in. It gives you full control over HTTP headers and redirects for your WordPress sites directly from your dashboard, with built-in safety checks and zero nginx knowledge required.
In this guide, you will learn how to use Site Rules, what you can do with it, and the real-world scenarios where it makes the biggest difference. Let us get started!
## TL;DR
Every HTTP response from your WordPress site carries headers — metadata that controls security, caching, and browser behavior. Most WordPress sites either ignore them or handle them through plugins, which means PHP has to fully load before any rule fires. That is slow, fragile, and unnecessary.
Redirects have the same problem. Plugin-based redirects require the entire WordPress stack to boot up just to tell a browser, “go here instead.” If WordPress throws a fatal error, your redirects die with it — and your SEO takes the hit.
The fix: handle headers and redirects at the server level (nginx), where they fire in milliseconds before PHP even wakes up. xCloud’s Site Rules feature lets you do exactly this through a visual dashboard — no config files, no command line, no risk. It validates every rule before applying it and rolls back automatically if anything breaks.
## **What Are HTTP Headers in WordPress?**
Every time someone visits your WordPress site, a conversation happens between their browser and your server. The browser sends a request. Your server sends back a response. That response includes two things: the actual content (HTML, CSS, images) and a set of **HTTP headers**.
Headers are lines of metadata attached to the response. The visitor never sees them, but the browser reads every single one. They carry instructions: how long to cache this page, whether the connection is secure, which scripts are allowed to run, and whether the page can be loaded inside an iframe on another site.
Think of headers as the rules printed on the envelope, not inside the letter. The letter is your page content. The envelope tells the postal system (the browser) how to handle it — where it came from, how to treat it, what to do if something looks wrong.
Here is a simplified example of what HTTP response headers look like:
```
HTTP/2 200 OK
Content-Type: text/html; charset=UTF-8
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Cache-Control: public, max-age=3600
```
Copy to Clipboard
Each line is a header. Each one tells the browser something specific:
- `Content-Type` says “this is an HTML page.”
- `Strict-Transport-Security` says “always use HTTPS for this domain.”
- `Cache-Control` says “you can cache this for one hour.”
By default, most WordPress hosting setups ship with only the bare minimum headers. The security-critical ones — HSTS, CSP, X-Frame-Options — are usually missing entirely. That is a problem, because modern browsers rely on these headers to protect your visitors from attacks like clickjacking, XSS injection, and protocol downgrade attacks.
The good news: adding them is straightforward once you have the right tool. The bad news: doing it through a WordPress plugin means every response gets slowed down by the PHP overhead of processing those headers. That is why handling headers at the server level — where they get added before PHP even runs — is the approach that actually makes sense.
## **Why Redirects Matter for SEO**
Redirects are not just a convenience feature. They are one of the most SEO-sensitive operations on your entire site.
When you change a URL — whether you are restructuring your blog, rebranding, merging domains, or just fixing a typo in a slug — every inbound link pointing to the old URL becomes a dead end. Backlinks, social shares, bookmarks, internal links from other posts — all of them now point to a page that does not exist.
Without a redirect, those visitors hit a 404. Google’s crawler hits a 404. And here is what happens next:
- **You lose link equity.** Every backlink to that old URL carried ranking power. A 404 throws that away. A properly configured 301 redirect passes the vast majority of that **[link equity](https://betterlinks.io/how-does-link-equity-distribution-impact-seo/)** to the new URL. Google has confirmed this — 301 redirects transfer PageRank.
- **Your pages drop out of the index.** When Googlebot encounters a 404 on a URL it previously indexed, it starts the process of removing that page from search results. If you had a page ranking on page one and you changed the URL without a redirect, you can watch it disappear within days.
- **User experience takes a hit.** A visitor clicking a link from an old article, an email campaign, or a social post lands on a “page not found” screen. They leave. Your bounce rate goes up. Your brand looks careless.
- **Redirect chains kill crawl efficiency.** If you set up a redirect from A → B, and later redirect B → C, you have created a redirect chain. Google will follow up to about 5 hops, but each hop slows down the crawl and dilutes the signal. Plugin-based redirects make it easy to accidentally create chains because there is no centralized view of how rules interact.
- **The wrong redirect type sends the wrong signal.** A 301 tells search engines “this move is permanent — update your index.” A 302 says “this is temporary — keep the old URL in the index.” Using a 302 when you meant a 301 means Google keeps trying to rank the old URL instead of the new one. It is a small mistake with outsized consequences.
Here is the part that makes server-level redirects non-negotiable for SEO: plugin-based redirects only work when WordPress is running. If your site throws a PHP fatal error, a database timeout, or a memory limit issue, your redirect rules stop firing. Every inbound link to an old URL now returns a 500 or 503 error instead of a clean redirect. Google sees server errors on URLs it expects to redirect, and your rankings take a compounding hit the longer the issue persists.
A redirect handled at nginx fires before WordPress loads. It does not care whether your database is down or your latest plugin update broke something. The redirect rule lives in the server config and runs regardless of PHP’s state. For SEO, that reliability is not optional — it is the baseline.
## **Why HTTP Headers and Redirects Belong at the Server Level, Not in WordPress**
Why HTTP Headers and Redirects Belong at the Server Level, not in WordPress
Most WordPress sites handle headers and redirects through plugins, which means the entire PHP stack has to boot up just to add a response header or tell a browser to go somewhere else. There is a faster, more reliable way to do it, and it starts with understanding why the server level is the right place for these rules.
### **The Problem With Plugin-Based Solutions**
When most WordPress users need to add a security header or set up a redirect, they reach for a plugin. And there are plenty of options out there: redirect manager plugins, security header plugins, SEO plugins with redirect features, and more.
But here is the catch. In most cases, redirects handled by plugins require WordPress and PHP to load. Every time a visitor hits your site, the entire WordPress stack has to load. PHP bootstraps. The database connects. Plugins initialize. And then your redirect or header rule fires. That is a lot of overhead for something that could have been handled in milliseconds at the server level.
Plugin-based headers and redirects come with real problems:
- **Performance cost:** Every rule requires WordPress to fully load before it can fire. On a site with multiple redirect rules, that adds up fast.
- **Reliability issues:** If WordPress throws a fatal error, your redirect rules stop working, too. The thing protecting your SEO is only as stable as your least reliable plugin.
- **Maintenance burden:** Plugins need updates, can conflict with other plugins, and add complexity to your stack. You are adding moving parts to solve what is fundamentally a server-level problem.
- **Scope limitations:** Some rules (like host-based redirects for domain consolidation) are difficult or impossible to implement correctly from inside WordPress.
### **Why Nginx Is The Right Place**
When a redirect or header rule lives in nginx, it gets evaluated before PHP ever runs. The request comes in, the rule fires, and the response goes out without touching WordPress at all.
This is faster. It is more reliable. And it is how production web infrastructure is designed to work.
The only barrier has been the technical friction of editing nginx config files by hand. Site Rules removes that barrier entirely.
## **What Is Site Rules?**
**Site Rules is xCloud’s built**\-in system for managing nginx-level HTTP header and redirect rules for your WordPress sites through a visual UI, with zero server access required.
Here is how it works:
1. You define rules through a clean interface
2. xCloud generates the correct nginx config
3. It validates the config against your live server
4. It applies the config only if the validation passes
5. If anything fails, it rolls back automatically
Your site stays up no matter what. Simple as that.
Site Rules supports two types of rules: Header Rules and Redirect Rules. Let us look at each in detail.
## **Best Security Headers for WordPress (With Examples)**
Every HTTP response your server sends includes headers — metadata that tells the browser how to handle the content. Most default configurations leave a lot of these headers either missing or set to insecure defaults.
With Site Rules, you can add, modify, or remove any HTTP response header for your WordPress site. xCloud includes presets for the most commonly needed headers, so you can apply them in one click without remembering the syntax.
Security headers are one of the most impactful things you can add to a WordPress site. They are checked in security audits, flagged by tools like Mozilla Observatory and Google Lighthouse, and they protect your users from real attacks.
Here is what each major security header does, why it matters, and what a good configuration looks like:
### **Strict-Transport-Security (HSTS)**
Tells browsers to always use HTTPS for your domain, even if a user types `http://` manually. This prevents SSL stripping attacks where an attacker downgrades a connection to HTTP. Once a browser sees this header, it will refuse non-HTTPS connections for the duration you specify.
**Example value:**
```
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
```
Copy to Clipboard
This tells the browser: “For the next year, never connect to this domain over plain HTTP. Apply the same rule to all subdomains.” The `preload` directive lets you submit your domain to browser preload lists, so even the first visit is HTTPS-only.
**When to use it:** On every WordPress site that has SSL configured. There is no good reason to skip this.
### X-Content-Type-Options
Set to `nosniff`, this header tells browsers not to guess the content type of a response. Without it, browsers can be tricked into executing a file as JavaScript even when the server says it is plain text. That is a common vector for XSS attacks.
**Example value:**
```
X-Content-Type-Options: nosniff
```
Copy to Clipboard
One line. No configuration needed. Just add it.
### X-Frame-Options
Prevents your site from being embedded in an iframe on another domain. This blocks clickjacking attacks, where an attacker overlays your site inside a hidden iframe and tricks users into clicking things they cannot see.
**Example value:**
```
X-Frame-Options: SAMEORIGIN
```
Copy to Clipboard
Use `SAMEORIGIN` if you embed your own content in iframes (some page builders do this). Use `DENY` if you never need iframe embedding at all.
### Content-Security-Policy (CSP)
The most powerful security header available, and the most complex to configure. CSP lets you define exactly which sources of scripts, styles, images, and other resources are allowed to load on your page. A well-configured CSP can prevent XSS attacks even if an attacker finds an injection vulnerability in your site.
**Example value (starter policy):**
```
Content-Security-Policy: default-src 'self'; script-src 'self' https://cdn.example.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' https://fonts.gstatic.com; frame-ancestors 'self'
```
Copy to Clipboard
This says: only load scripts from my domain and my CDN. Only load fonts from Google Fonts. Do not allow anyone to iframe my site except me. Everything else — default to my own domain only.
💡**A word of caution:** CSP is powerful but can break things if misconfigured. Start with `Content-Security-Policy-Report-Only` to monitor violations without blocking anything, then tighten the policy once you know what your site actually loads.
### Referrer-Policy
Controls how much referrer information is included in requests made from your site. Setting this prevents leaking your internal URL structure to third-party sites.
**Example value:**
```
Referrer-Policy: strict-origin-when-cross-origin
```
Copy to Clipboard
This sends the full URL as a referrer for same-origin requests (useful for your own analytics) but only sends the origin (domain) for cross-origin requests. Your internal URL paths stay private.
### Permissions-Policy
Formerly known as Feature-Policy, this header lets you control which browser features (camera, microphone, geolocation, etc.) your site is allowed to use — and blocks features your site does not need from being accessed by any injected third-party scripts.
**Example value:**
```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=()
```
Copy to Clipboard
The empty parentheses mean “disabled for everyone, including this site.” If your site genuinely needs geolocation (like a store locator), you would set `geolocation=(self)` it instead.
### Putting It All Together
Here is what a well-configured set of security headers looks like for a typical WordPress site:
```
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=()
Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:;
```
Copy to Clipboard
With Site Rules, all of these are available as presets. Click the preset, review the value, hit save, and the header is live on your server in seconds.
👉 Want to learn more about WordPress security headers? Check out our complete guide: **[WordPress Security Headers – A Guide to Keep Your Website Safe](/complete-guide-to-wordpress-security-headers/)**
## Cache Control Headers
Beyond security, header rules are also useful for fine-tuning how your content is cached by browsers and CDNs.
If you are using Cloudflare or another CDN in front of xCloud, your Cache-Control headers determine how long assets are cached at the edge. Getting these right means fewer origin requests, faster global load times, and lower bandwidth costs.
With Site Rules, you can set custom Cache-Control values for your site’s responses without editing any nginx config manually.
## CORS Headers for Headless WordPress
Running WordPress as a headless CMS? Your frontend application (whether it is Next.js, Nuxt, or a mobile app) needs to make cross-origin requests to your WordPress REST API or GraphQL endpoint.
Without proper CORS headers, the browser will block those requests entirely.
With Site Rules, you can add a `Access-Control-Allow-Origin` header and configure any additional CORS headers your setup needs. Your headless frontend can then communicate with WordPress without any issues.
This is a use case where plugin-based CORS solutions often fall short, especially if you need fine-grained control over which origins are allowed or which HTTP methods are permitted.
## How to Add Redirects Without Plugins (Step-by-Step)
Here is how to set up server-level redirects using xCloud’s Site Rules – no plugins, no config files, no SSH required.
### Step 1: Open Site Rules and Start a New Redirect
Log in to your xCloud dashboard, navigate to your site, and go to **Tools → Site Rules** in the left sidebar. Switch to the **Redirect Rules** tab, then click **Add Redirect** in the top right corner. A modal will open with the fields you need.
### Step 2: Configure Your Redirect
Fill in the redirect details:
- **From (Source URL):** The old path you want to redirect, e.g. `/old-blog-post`. No need to include the domain.
- **To (Destination URL):** Where traffic should go — a path on the same site (`/new-blog-post`) or a full URL on another domain (`https://newdomain.com/page`).
- **Redirect Type:** Choose **301 (Permanent)** for URL changes you do not plan to reverse — slug updates, migrations, restructures. Choose **302 (Temporary)** for short-lived redirects like maintenance pages or campaign landing pages. When in doubt, go with 301.
### Step 3: Add Conditions (Optional)
Need the redirect to fire only in specific situations? Click **Attach Condition** to add conditional logic based on:
- **Hostname**: Only redirect requests from a specific domain. One rule can handle an entire domain migration while preserving paths.
- **URI pattern**: Match specific URL patterns for more targeted redirects.
- **Query string**: Only redirect when a specific parameter is present, like `?promo=summer2026`. Great for campaign routing.
- **Device type**: Redirect mobile users to `m.yoursite.com` while desktop users stay on the main site.
Skip this step if the redirect should apply to all matching requests.
### Step 4: Test, Save, and Apply
Before committing anything, click **Test Rule**. xCloud generates the nginx config and runs `nginx -t` against your live server without applying it. You will see whether the rule passes or fails — and if it fails, the exact error so you can fix it first.
Once the test passes, click **Save Rule**. xCloud validates one final time and applies the config. The redirect is now live at the server level, firing before WordPress or PHP even loads. If validation fails at any point, xCloud rolls back automatically. Your site stays up no matter what.
## Redirect Rules: Handle Every Redirect Scenario Without a Plugin
Beyond the basic setup above, here are the specific scenarios where Site Rules handles redirects that plugins struggle with.
### Simple Path Redirects
The most common use case: you have changed a URL and need to redirect the old path to the new one.
- `/old-blog-post-url` → `/new-blog-post-url` (301)
- `/services` → `/what-we-do` (301)
- `/contact-us` → `/contact` (301)
With Site Rules, you enter the source path, the destination, choose 301 or 302, and save. xCloud writes the nginx rewrite rule, validates it, and applies it. No plugin. No PHP overhead. The redirect fires at the nginx level before WordPress even loads.
### URL Structure Migration
You have relaunched your site with a completely new URL structure or migrated from a different CMS with different URL patterns. You have dozens or hundreds of old URLs that need to redirect to new ones, and getting this right matters for SEO.
Site Rules lets you create and manage all of these redirects in one place. Each rule is applied at the nginx level, which means Google and users get clean, reliable 301 redirects that do not depend on WordPress being healthy.
### Domain Consolidation and Rebranding
You are consolidating multiple domains into one, or you have rebranded and have a new domain name. Every request to the old domain needs to redirect to the corresponding page on the new domain.
With Site Rules’ host-based conditions, you can create a redirect rule that only fires when the request comes from a specific domain. It then redirects to the equivalent URL on the new domain, preserving the path.
`If host = old-domain.com → redirect to new-domain.com (same URI, 301)`
One rule handles every page on the old domain. Clean, permanent, and handled entirely at the server level.
### Trailing Slash Normalization
SEO best practice is to be consistent about whether your URLs include a trailing slash. If both versions of a URL return content, search engines may treat them as duplicate pages and split your link equity.
With a redirect rule in Site Rules, you can enforce your preference across your entire site. Redirect all trailing-slash URLs to their non-slash equivalents, or vice versa.
### Conditional Redirects Based on Device Type
Some sites maintain separate mobile and desktop experiences. Rather than relying on JavaScript-based detection (which fires client-side, after the page has started loading), you can handle this at the nginx level.
Site Rules supports device-based redirect conditions. Create a rule that fires only for mobile devices, redirecting them to `m.yoursite.com` or a mobile-specific URL while desktop users continue to the main site. No JavaScript, no plugin, no PHP. Pure server-level logic.
### Conditional Redirects Based on Query Parameters
Running a marketing campaign? Tracking UTM parameters? Need to redirect users who arrive with a specific query parameter to a custom landing page?
Site Rules supports query parameter conditions. Create a rule that only fires when a specific query parameter is present in the URL. This is the kind of conditional logic that is difficult to implement reliably in WordPress plugins but straightforward at the nginx level.
### Temporary Redirects During Maintenance or Campaigns
Not all redirects should be permanent. During site maintenance, you might want to temporarily redirect traffic to a maintenance page. During a campaign, you might want to redirect a specific URL to a time-limited landing page.
Use a 302 (temporary) redirect in Site Rules for these scenarios. When the campaign ends or maintenance is done, delete the rule and the original URL returns to normal. Quickly, safely, and without leaving any permanent redirect baggage in your nginx config.
## Common Mistakes to Avoid
Even with a tool that validates your rules automatically, there are mistakes that pass syntax checks but still hurt your site. Here are the ones that come up most often.
### Using 302 When You Mean 301
This is the single most common redirect mistake in WordPress. You change a URL permanently, but you use a 302 (temporary) redirect instead of a 301. The redirect works — visitors get to the right page — so you assume everything is fine.
It is not. Google treats a 302 as a signal that the old URL should stay in the index. Your new URL does not get the ranking power from the old one. Months later, you are wondering why your rewritten content is not ranking, and the answer is a redirect type you set once and forgot about.
**The fix:** Default to 301 unless you have a specific, time-limited reason for 302 (maintenance page, short campaign).
### Redirect Chains and Loops
Page A redirects to Page B. Later, you redirect Page B to Page C. Now you have a chain: A → B → C. Google will follow it (up to about 5 hops), but each hop adds latency and dilutes the SEO signal.
Worse: if Page C ever redirects back to A, you have a loop. The browser gives up, the user sees an error, and Googlebot flags the URL as broken.
**The fix:** When you create a new redirect, check whether the destination already has a redirect of its own. If it does, point the source directly to the final destination instead. A → C, not A → B → C.
### Forgetting to Redirect Both Slash and Non-Slash Versions
You redirect `/old-page` to `/new-page`. But `/old-page/` (with trailing slash) still returns a 404. Search engines may have indexed either version, and visitors might have bookmarked either one.
**The fix:** Set up trailing slash normalization as a site-wide rule first, so your site is consistent. Then your individual redirects only need to handle one version.
### **Redirecting Everything to the Homepage**
When migrating a site, it is tempting to redirect all old URLs to the homepage rather than mapping each one to the correct new page. Google sees through this. A redirect from a specific blog post to a homepage is treated as a “soft 404” — Google understands the content is gone and does not transfer ranking power.
**The fix:** Map old URLs to their closest equivalent on the new site. If there is genuinely no equivalent page, it is better to let the URL return a proper 404 with a helpful “page not found” message than to redirect it somewhere irrelevant.
### **Adding Security Headers Without Testing Them**
A misconfigured `Content-Security-Policy` header can break your entire site. Scripts stop loading, styles disappear, embedded content vanishes. The site looks like it was built in 1997.
**The fix:** Use `Content-Security-Policy-Report-Only` first. This header tells browsers to report violations without actually blocking anything. Review the reports, adjust your policy, and only switch to the enforcing `Content-Security-Policy` header when you are confident nothing will break.
With Site Rules, you can use the **Test Rule** button to validate the nginx syntax before applying. But keep in mind that a syntactically valid CSP can still break your frontend — the test checks server config, not browser behavior. Always test in a staging environment or with report-only mode first.
### Ignoring Header Rules on Subdomains
You add security headers to your main domain. But your staging site at `staging.example.com`, your CDN subdomain, or your API endpoint at `api.example.com` gets nothing. Attackers target the weakest link.
**The fix:** Apply security headers consistently across every subdomain that serves content. With xCloud, you can manage Site Rules per site, so set up the same header rules on each one.
### Not Setting an Expiry on HSTS
Adding `Strict-Transport-Security` without a reasonable `max-age` value is almost pointless. A `max-age` of 300 seconds (5 minutes) means the browser forgets about HSTS enforcement almost immediately.
**The fix:** Use `max-age=31536000` (one year) as a minimum for production sites. If you are just starting with HSTS, begin with a shorter duration (like 86400 — one day), verify everything works over HTTPS, then increase to a year and add `includeSubDomains`.
## **The Safety System Behind Site Rules**
One of the most important aspects of Site Rules is what happens when something goes wrong. Because sometimes it does, and xCloud has you covered.
### **Automatic Validation Before Every Apply**
Every time you create, update, or delete a rule, xCloud does not just write the config and move on. It follows a strict process:
1. **Generate the new config:** xCloud builds the complete nginx config from all your enabled rules
2. **Write to a temp location:** The new config is written temporarily and is not applied yet
3. **Run nginx -t:** xCloud tests the new config for syntax errors on your live server
4. **Apply if clean:** Only if the test passes does xCloud apply the config and reload nginx
5. **Roll back if it fails:** If the test fails, the previous config is restored immediately, and you see the exact nginx error in your dashboard
This means your site never goes down because of a bad rule. The worst that happens is you see an error message and the rule is not applied.
### Test Rule Without Saving
Not sure how a complex rule will behave? The Test Rule button lets you run the nginx validation check without saving the rule. You will see whether the rule would pass or fail, and if it fails, you will see the exact error before committing anything to your server.
This is especially useful for redirect rules with multiple conditions, where the generated nginx rewrite syntax can be complex to predict.
### Rule Limits
Site Rules enforces sensible limits to keep your nginx config manageable: **up to 10 header rules and 25 redirect rules per site.** This prevents config bloat and keeps your server performing well.
### Drag-and-Drop Rule Priority
Rule order matters, especially for redirects. The first matching rule wins. Site Rules lets you drag and drop rules in the table to set their priority, then hit Save Order to apply the new ordering. You can discard changes before saving if you want to revert.
## Site Rules vs. Plugin-Based Solutions: A Direct Comparison
Site Rules
Plugin-based
When the rule fires
At nginx, before PHP runs
After WordPress + PHP fully load
Performance
Zero PHP overhead
Adds to every request
Reliability
Always fires, independent of WordPress
Stops working if WordPress breaks
Maintenance
No updates needed
Plugin updates, conflict risk
Risk on misconfiguration
Auto-rollback, site stays up
Can cause white screens or errors
Conditional logic
Host, URI, query param, device type
Varies by plugin, often limited
CORS/custom headers
Any header, full control
Limited by the plugin’s supported headers
Cost
Included in xCloud paid plans
Often premium plugin features
## Who Should Use Site Rules?
**WordPress developers** managing client sites who want to add security headers and handle redirects properly without installing plugins for every site.
**Agencies** running large portfolios of WordPress sites who need a reliable, scalable way to manage redirects and headers across all their clients.
**Site owners** who have been putting off security hardening because it seemed too technical. Site Rules makes it approachable for anyone.
**Developers building headless WordPress** who need CORS headers configured correctly for their frontend applications.
**SEO professionals** managing URL migrations, domain consolidations, or ongoing redirect strategies who want server-level reliability.
## Start Managing Headers and Redirects the Right Way
Security headers and redirects are foundational to how a professional WordPress site operates. They affect your security posture, your SEO, your user experience, and your site’s performance under load.
For too long, managing these things properly meant either accepting the overhead of plugins or learning nginx configuration by hand. Most sites ended up with an inconsistent setup that was hard to audit or maintain.
Site Rules changes that. It makes server-level header and redirect management accessible to every WordPress developer and team on xCloud, with built-in safety, a clean UI, and none of the risk that used to come with editing nginx configs manually.
If your sites are running without security headers or managing redirects through plugins, it is worth taking 10 minutes to explore what Site Rules can do.
👉 **Ready to get started?** [**Sign up for xCloud**](https://app.xcloud.host/register) and start managing your WordPress headers and redirects the right way.
If you have found this blog helpful, feel free to [**subscribe**](/blog/) [**to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Advanced Redis Object Caching for Your WordPress Site - xCloud
> Redis object caching enhances the speed and efficiency of websites and applications.
Imagine you have a big bookshelf full of books. Sometimes, when you want to read a book, you have to search through all the shelves to find it. That can take a lot of time!
Now, think of [**Redis object caching**](/docs/how-caching-works-in-xcloud/), like having a small table next to your reading chair. Instead of searching the whole bookshelf every time you want a book, you put your favorite books on the table where they’re easy to grab. So, when you want to read one of them, you can quickly pick it up from the table instead of searching the whole shelf.
In technical terms, Redis object caching is like having a super-fast memory for your website. Instead of fetching information from a slow database every time someone visits your site, Redis stores that information in its memory. So, when someone asks for the same info again, it’s already there, ready to go, making your website load much faster.
We use Redis object caching to speed up websites and make them more efficient. It helps handle lots of visitors without slowing down the site, which is super important for keeping people happy and engaged.
## **What Is Server Side Page Caching**
Before we dive into Redis Full-Page Cache, let’s understand how your website functions.
1. When someone visits your WordPress site, their web browser talks to Nginx (the server).
2. Nginx passes the request to PHP-FPM (a program that runs PHP code).
3. PHP-FPM checks with the database (like MariaDB or MySQL) to get the page content.
4. PHP-FPM processes everything and creates an HTML page.
5. This HTML page is sent back to Nginx.
6. Finally, Nginx sends this HTML page to the visitor’s web browser.
## **Why You Should Always Opt for Server-Side Caching**
When you use server-side page caching, Nginx steps in between Nginx and PHP-FPM. It creates a cached HTML page from PHP-FPM.
So, when another person visits the same WordPress page, your site doesn’t need to do the same PHP and database work again. Nginx just serves the cached page directly.
This makes your server respond much faster after the first load. It also reduces the work for PHP-FPM and MariaDB/MySQL and lowers your server’s CPU usage.
With server-side caching, your server can handle more visitors without needing a bigger setup. This means you can stick with a more affordable server without needing to upgrade.
## **What Is Redis? With Example**
[**Redis**](https://redis.io/), which stands for Remote Dictionary Server, is a free tool that stores data in memory. It’s like having a super-fast digital organizer that helps keep track of different types of information, such as words, lists, numbers, and even geographical locations.
Think of it as a helpful assistant that works alongside databases like MySQL or MariaDB to speed up applications. By storing frequently accessed data close at hand, Redis helps optimize the performance of applications, making them run smoother and faster.
Let’s say you have a website where users can see popular articles. Instead of calculating which articles are popular every time someone visits the page, you can use Redis caching. You calculate the popular articles once, store them in Redis, and then whenever someone visits the page, you quickly fetch the list from Redis instead of recalculating it every time.
This makes your website faster and saves a lot of time and effort!
## **Redis Object Caching for WordPress**
Object caching saves the results of database queries that users ask for. Then, when someone asks for the same thing later, it can give them the answer much faster without asking the database again.
In WordPress, there’s a built-in thing called Object Cache using the [**WP\_Object\_Cache**](https://developer.wordpress.org/reference/classes/wp_object_cache/) class. But there’s a catch: by default, this caching isn’t permanent. That means the saved answers only stick around until the page finishes loading. This isn’t very efficient unless you add a permanent caching system like Redis Object Cache.
## **Understanding Redis Integration with WordPress Cache Plugins**
Unlike regular WordPress cache plugins that focus on speeding up how quickly your website’s pages load by saving static versions of pages, Redis works as a server-side cache. This means it stores data directly on the server to make fetching information faster.
Let’s imagine you have a blog where you post articles about travel destinations. You also have an online shop where you sell travel gear and accessories. To make your site faster, you decide to use a cache plugin.
Most cache plugins focus on storing static versions of your blog posts and shop pages, so they load quickly for visitors. But what about other parts of your site, like the checkout process or interactive features? This dynamic content isn’t cached by default.
With dozens of plugins active on your site, including ones for social media sharing, SEO optimization, and more, your WordPress Admin area might feel sluggish because it’s not caching this dynamic content.
## **Unlocking WordPress Speed: The Role of Redis Explained**
Having a slow WordPress website is frustrating for both visitors and site owners. But you can make your site faster and improve the user experience by using a caching system like Redis.
When Redis is set up on your WordPress site, [**it speeds up**](/tips-to-speed-up-wordpress-websites/) how quickly visitors can access your content. Normally, when someone asks for information on a WordPress site, the system has to search through a database, which takes time.
Redis keeps important information in its memory so it can be quickly accessed when needed. This means data can be retrieved much faster, making your site perform better and reducing the time it takes for pages to load.
## **Using Redis for Query Caching in WordPress**
Have you ever faced the frustration of slow database queries? Query caching could be your saving grace, speeding up these queries using various caching methods while keeping costs manageable!
Imagine you’ve developed an e-commerce app that’s experiencing rapid growth. Your product catalog is extensive, and you have millions of customers—great for business, but it’s straining your technology. Despite efforts to optimize database queries to your primary database (be it MongoDB or PostgreSQL), they’re slowing down. Even with some performance tweaks, it’s not meeting your customers’ expectations.
Redis is a special kind of storage system that mainly handles caching. It helps to ease the burden on your main database by speeding up how quickly you can get information from it.
In e-commerce apps, there’s one type of request that comes up a lot: searching for products. To make product searches faster, you can use Redis in a couple of ways:
1. **Cache prefetching:** You can load up Redis with all the product details beforehand. Then, when someone wants to search for a product, the app can check Redis first instead of going straight to the main database.
2. **Cache-aside pattern:** Instead of loading up Redis with everything in advance, you fill it up as needed. When someone wants to search for a product, the app puts that information into Redis so it’s there for the next person who wants to search for the same thing.
### **Cache Aside Method with Redis Object Caching(Cache Miss)**
\[Redis\]
Let’s break this diagram into some easy points
1. The app asks for some data.
2. The backend looks in Redis to see if it already has that data.
3. If Redis doesn’t have the data (a “cache miss”), the backend gets it from the main database.
4. Once the data is fetched from the database, it’s saved in Redis.
5. Finally, the data is sent back to the app.
### **Cache Aside Method with Redis Object Caching(Cache Hit)**
Now, let’s look at what happens when there’s a “cache hit.” Here’s the same diagram, but with the steps for a “cache hit” highlighted in green.
In a “**cache hit**“:
1. The app asks for data.
2. The backend checks if the data is in Redis.
3. If the data is found (a “cache hit”), it’s sent back to the app right away.
The cache-aside pattern is handy when you:
1. Need to fetch data a lot: Like in e-commerce, where you’re always checking product info.
2. Want to save space and money: Instead of loading up Redis with everything, it only saves what’s needed when it’s needed.
3. Care about costs: The less stuff you store in the cache, the less you have to pay for storage.
## **Precautions to Take Before Implementing Redis Cache in WordPress**
Before you turn on the Redis cache for your WordPress site, it’s crucial to take some precautions. Neglecting these steps could impact your server and lead to significant losses.
### **Go for Staging Site**
Developers recommend testing any changes to your website in a [**staging environment**](/docs/how-to-create-a-staging-environment-in-xcloud/) first. This way, even if something goes wrong, your actual site stays safe. It’s like a practice run where you can learn from any mistakes.
Once you’re confident everything works smoothly, you can “push” those changes to your live site. This means the changes aren’t made to the live site until you decide to do so.
Your staging environment is basically a copy of your real website. It’s not accessible to the public, and search engines can’t see or index it because it’s protected by a password.
### **Configuring WP Config File to Avoid Conflicts**
To ensure the smooth operation of Redis on your Cloudways-hosted site, you’ll need to make a few adjustments in the wpconfig.php file. Here’s how:
1. Log in to your FTP client.
2. Connect to your hosting account.
3. Find the public\_html folder.
4. Inside public\_html, locate the wp-config.php file.
5. Open the wp-config.php file using any text editor.
6. Add the following line of code right after the first line, which is PHP’s opening tag ( Secure your website with an advanced web application Firewall (WAF) and learn the best configurations and tips for hosting security.
Hosting security is a big concern for businesses of all sizes. As websites handle more and more sensitive data, cyberattacks are becoming both more common and more sophisticated. If you run a website, you have to **protect it against threats** like malware, bot traffic, and even distributed denial of service (DDoS) attacks.
A web application firewall (WAF) can provide strong protection. But with today’s growing threats, a basic WAF setup might not be enough. Today, we will explore how advanced WAF configurations can keep your hosting secure, how they work, and how to implement them.
## **What Is a Web Application Firewall (WAF)?**
A Web Application Firewall (WAF) is a security device designed to protect web applications by filtering and monitoring HTTP traffic between a web application and the internet. Unlike traditional firewalls that guard against unauthorized access to the network, WAFs are application-specific. They focus on filtering traffic that directly interacts with the web application. There are three primary types of WAFs:
1. **Network-based WAF** – This type of WAF is installed on-premises and operates at the network level.
2. **Host-based WAF** – Installed directly on the web server, this WAF offers deep customization but can consume resources.
3. **Cloud-based WAF** – Offered as a service, cloud WAFs are easy to implement and scalable.
While traditional WAFs can block common attacks like [**SQL injection**](https://wpdeveloper.com/fortify-wordpress-site-from-sql-injection-9-ways/) and cross-site scripting (XSS), they fall short when faced with complex, evolving threats. This is where the Advanced Web Application Firewall comes in, offering stronger protection with customizable rules and real-time threat intelligence.
## **Why Advanced WAF Configurations Are Crucial for Hosting Security?**
With the rise of automated bots, **DDoS attacks,** and highly targeted application-layer threats, having an advanced WAF configuration gives you the edge in identifying and stopping these threats. An advanced web application firewall doesn’t just block attacks based on static rules; it continuously learns and adapts to new attack patterns, using real-time data. Here’s why advanced configurations are essential:
- **Adaptability**: The modern threat environment is unpredictable and constantly evolving. Hackers constantly find new ways to bypass security defenses. An **advanced web application firewall** can adapt by updating its rules in real time, unlike a traditional WAF, which relies on static configurations.
- **Customization**: Every website is unique. While a basic WAF might offer blanket protection, advanced configurations allow you to customize security settings to suit your specific environment, focusing on the risks that are most relevant to your site.
- **Layer 7 Protection**: Most attacks, like SQL injections or cross-site scripting (XSS), target the application layer. Basic security tools may miss these sophisticated attacks, but an **advanced web application firewall** focuses heavily on application-level security, ensuring thorough protection.
In today’s environment, where even small websites are targets for automated bots and hackers, having an advanced WAF configuration is no longer optional. It’s an essential part of your security strategy.
## **Key Features of Advanced WAF Configurations for Hosting Security**
Now that we understand why advanced configurations are necessary let us dive into some specific settings that can greatly enhance your **Advanced Web Application Firewall**. These configurations will not only protect your web application but also ensure that your hosting environment stays secure and resilient against attacks.
### **1\. Traffic Monitoring And Filtering**
One of the most powerful features of an **Advanced Web Application Firewall** is its ability to monitor and filter **[web traffic in real-time](/managing-traffic-spikes-on-a-shared-server/).** With advanced monitoring, you can analyze traffic patterns and spot unusual activity that could indicate an attack. For example, you can set up rules to block traffic from certain countries or limit the number of requests from a single IP address. This helps protect against brute force attacks and Distributed Denial of Service (DDoS) attempts.
Advanced traffic filtering allows you to create custom rules. You can filter traffic based on headers, cookies, user agents, or even the content of HTTP requests. By customizing these rules, you can block specific attack vectors while allowing legitimate traffic through. This precision is critical in stopping sophisticated attacks without disrupting regular users.
### **2\. Rule Customization Based on Application Type**
Not all web applications are the same, and neither are their security needs. A blog, for instance, will have different vulnerabilities compared to an e-commerce store. With advanced rule customization, you can configure your WAF settings to fit the unique behavior of your application.
For example, e-commerce sites might need stricter security around credit card transactions, while a news site might focus more on protecting its comment sections from spam and cross-site scripting (XSS) attacks. Advanced WAF settings allow you to create specific security profiles for different parts of your web application, ensuring comprehensive coverage.
### **3\. Virtual Patching**
One of the most innovative features of an Advanced Web Application Firewall is virtual patching. In the world of web security, new vulnerabilities are constantly being discovered. But applying patches to fix these vulnerabilities can take time, especially if you are working with complex systems or have limited development resources.
Virtual patching is a lifesaver in these situations. With this feature, your WAF can temporarily block attacks targeting a known vulnerability, giving you time to roll out a proper fix. It acts as a temporary bandage, protecting your application from being exploited while you address the issue behind the scenes.
### **4\. Bot Management And Rate Limiting**
Bots can be both useful and harmful. Some bots index your site for search engines, while others try to exploit your site by scraping data or launching automated attacks. With advanced **WAF** configurations, you can differentiate between good bots and malicious ones.
Bot management tools can block harmful bots or limit their activity, preventing them from overwhelming your servers or scraping sensitive information. **Rate limiting** is another key tool here. This allows you to control how many requests an IP address can make in a certain time period, which helps in mitigating DDoS attacks and reducing server strain.
### **5\. Application Layer Protection (Layer 7)**
When it comes to security, the application layer (Layer 7 of the OSI model) is often the most vulnerable. Most web application attacks, such as SQL injection or cross-site scripting (XSS), happen at this level. A basic firewall might not be able to detect these threats, but an Advanced Web Application Firewall provides specific protections for Layer 7.
With Application Layer Protection, your WAF will inspect the actual content of web requests to detect malicious patterns. For instance, if someone tries to insert malicious SQL queries into your site’s forms, the WAF can block the request before it reaches your database. This layer of protection is essential for preventing some of the most dangerous web attacks.
## **Core Configurations for Advanced Web Application Firewall**
To get the most out of an **Advanced Web Application Firewall (WAF)**, you need to focus on key configurations. These configurations determine how your firewall will react to potential threats and protect your hosting environment from cyber-attacks. Here, we will break down some of the most important settings that every advanced WAF should have.
### **1\. Firewall Policies**
Policies are the backbone of any firewall system. In an **Advanced WAF**, firewall policies are used to define which traffic is allowed and which should be blocked.
- **Default Deny Policies**: This means that unless the traffic explicitly meets specific criteria, it will be blocked. This type of policy is crucial in a hosting environment where the risk of malicious traffic is high.
- **Allow Lists (Whitelisting)**: Trusted IP addresses, users, or applications can be added to the allow list, granting them access while blocking others.
- **Deny Lists (Blacklisting)**: This involves identifying known malicious IP addresses or countries from which attacks typically originate and preventing any traffic from these sources.
### **2\. IP Blacklisting And Whitelisting**
IP blacklisting is one of the most straightforward ways to block malicious traffic. In an **Advanced WAF**, this feature is typically more robust, allowing you to create dynamic blacklists that automatically update based on real-time threat intelligence.
- **Geofencing**: You can block or allow traffic from specific geographical locations based on your business needs.
- **Whitelisting Internal IPs**: This is essential for ensuring that your own employees or trusted partners can access your web applications without being accidentally blocked.
### **3\. Rate Limiting And Traffic Shaping**
Rate limiting controls how many requests a user can make to your web application in a given time. Without rate limiting, an attacker could bombard your server with thousands of requests per second, causing it to slow down or crash.
- **Set Thresholds for Requests**: You can configure your **Advanced WAF** to only allow a certain number of requests per IP address within a specific timeframe.
- **Traffic Shaping**: In some cases, rather than completely blocking excessive traffic, you can “shape” or slow it down to maintain performance without overwhelming the server.
### **4\. Application-Layer Filtering And Protection**
An **Advanced WAF** operates at the application layer, meaning it specifically protects the functionality of your web apps. This layer of protection is especially important against **SQL Injection** and **Cross-Site Scripting (XSS)** attacks, which exploit vulnerabilities in the code.
- **Request Inspection**: Your WAF will inspect each request to ensure it’s legitimate and doesn’t contain harmful code.
- **Blocking Common Vulnerability Exploits**: Preconfigured filters can block well-known application vulnerabilities such as **OWASP Top 10** threats.
### **5\. SSL/TLS Encryption Handling**
SSL/TLS encryption ensures that data passed between a user and a website is secure. However, SSL traffic can sometimes hide malicious activity from less advanced security systems. An **Advanced Web Application Firewall** can inspect SSL traffic without compromising the encryption, providing full visibility into potential threats.
- **SSL Offloading**: Offloading SSL processing to your WAF improves performance by reducing the load on your servers.
- **SSL Traffic Inspection**: Advanced WAFs can decrypt and inspect traffic, ensuring no malicious content is hidden within encrypted data streams.
These core configurations ensure that your **Advanced Web Application Firewall** can provide a high level of security tailored to the needs of your web application.
## **Common Mistakes to Avoid in WAF Configurations**
Configuring an advanced web application firewall can significantly boost your website’s security, but if done incorrectly, it can lead to vulnerabilities or unnecessary complications. Here are some common mistakes to avoid when configuring your WAF:
### **1\. Misconfiguring or Over-configuring the WAF**
One of the most common mistakes is either misconfiguring or over-configuring the WAF. If your configuration is too loose, attackers can find vulnerabilities and exploit them. If it’s too strict, you might end up blocking legitimate users or services, which can frustrate customers and harm your website’s performance.
To avoid this, start with a balanced configuration. Use default settings as a baseline, and then gradually customize the rules based on the traffic patterns and types of threats your site encounters.
### **2\. Failing to Update Rule Sets Regularly**
Cyber threats are always evolving, and if your WAF isn’t regularly updated, it will quickly fall behind. A common mistake is failing to enable dynamic rule updates, which allows the WAF to automatically receive the latest threat intelligence and adjust its defenses accordingly.
Make sure your advanced web application firewall is set to update rule sets in real-time, and manually check for updates from your WAF provider periodically.
### **3\. Not Monitoring WAF Performance Regularly**
Another mistake is the “set it and forget it” approach. After configuring the WAF, many administrators neglect to monitor its performance. Regular monitoring is essential because it helps you identify abnormal traffic patterns, potential weaknesses, and new attack vectors.
Use WAF logs and analytics tools to continuously review how well the firewall is performing. Adjust the settings if you notice unusual activities, such as repeated login attempts, high bot traffic, or unexpected spikes in specific regions.
### **4\. Overlooking Application-Specific Threats**
Not all websites face the same threats. A mistake many site owners make is assuming that all WAF settings apply universally. For example, if your site hosts sensitive user data, you will need stronger security against application-layer attacks like SQL injections and cross-site scripting (XSS). Failing to account for these specific threats can leave your application vulnerable.
When configuring your WAF, tailor it to your site’s specific risks. This will allow the firewall to focus on protecting your most critical areas.
### **5\. Ignoring False Positives**
A WAF may sometimes block legitimate traffic by mistake, which is known as a false positive. Ignoring these false positives can hurt your website’s performance and user experience. Regularly review your WAF’s logs to identify and correct these cases, and adjust the firewall settings accordingly to avoid blocking valid users.
## **How to Choose the Right WAF for Your Hosting Security**
Choosing the right Advanced Web Application Firewall (WAF) is one of the most important decisions you can make for protecting your web applications. With the increasing complexity of cyber threats, your WAF should not just defend against common attacks but also adapt to emerging threats. Below are key considerations to guide you in selecting the ideal WAF for your hosting security needs.
### **1\. Understand Your Web Application’s Security Needs**
The first step in choosing the right WAF is assessing your specific security requirements. Every web application faces different threats based on its functionality, user base, and the types of data it handles. For instance, an e-commerce site that processes credit card payments will need robust protection against SQL injection and cross-site scripting (XSS) attacks, while a content-heavy site may need bot management to prevent scraping and spam. Conducting a security assessment of your application helps determine the types of threats you need protection from.
### **2\. Decide on Deployment Type: Cloud, On-Premises, or Hybrid**
There are three primary deployment models for Advanced WAFs: cloud-based, on-premises, and hybrid. Each comes with its advantages and disadvantages.
- Cloud-based WAFs are hosted by third-party providers, making them easy to set up, highly scalable, and cost-effective. These are ideal for businesses that require rapid deployment without the hassle of managing hardware.
- On-premises WAFs provide greater control over customization and integration with existing network security systems. They are suited for larger enterprises with more complex infrastructure but come with higher upfront costs and maintenance responsibilities.
- Hybrid WAFs combine cloud and on-premises elements, allowing you to leverage the scalability of cloud services while retaining some control over specific security components.
### **3\. Consider Ease of Management And Customization**
A WAF should be easy to manage while offering the flexibility to customize security rules according to your application’s needs. Look for a WAF solution with an intuitive user interface, real-time reporting, and actionable alerts. It should allow for rule customization so that you can tailor it to the traffic patterns and vulnerabilities of your application.
Also, make sure the WAF supports automatic updates to keep up with the latest security threats. Some advanced WAFs integrate AI and machine learning features, which enable them to automatically adapt and block emerging threats without requiring manual input.
### **4\. Focus on Comprehensive Threat Protection**
Your WAF should be able to protect against a wide range of attacks, including:
- **Layer 7 Attacks:** Look for a WAF that protects at the application layer (Layer 7) to guard against attacks like SQL injection, XSS, and cross-site request forgery (CSRF).
- **Bot Management:** Ensure the WAF can differentiate between legitimate bots (such as search engine crawlers) and malicious bots that attempt data scraping or account takeover attacks.
- **DDoS Protection:** Distributed Denial of Service attacks can cripple your website by overwhelming it with traffic. A WAF with built-in DDoS mitigation ensures your site stays online during high-traffic attack events.
- **Virtual Patching:** This feature can block threats that target known vulnerabilities, giving you time to apply actual patches to your web applications.
### **5\. Scalability And Performance**
As your application grows, so will its traffic volume, which means you will need a WAF that can scale alongside your business. Cloud-based WAFs typically offer the best scalability, allowing you to increase resources during traffic spikes. However, even the best WAF can negatively impact performance if not optimized, so be sure to choose a solution that introduces minimal latency.
### **6\. Compliance And Certifications**
Your WAF should meet industry standards and certifications that align with your business’s compliance requirements. For example, if your website handles payment transactions, the WAF should comply with PCI DSS. Businesses operating in regions with strict data protection laws, such as Europe, must also ensure their WAF is compliant with GDPR. Check for certifications like ISO/IEC 27001, which guarantees that the WAF provider adheres to international security standards.
### **7\. Cost And Support**
Lastly, weigh the cost of the WAF against its features and your budget. Most providers offer tiered pricing based on traffic volume, security features, and the number of protected applications. Look for a WAF that offers the best value without sacrificing key security functions. Additionally, reliable customer support is crucial. You should choose a provider that offers 24/7 support in case of a security incident or technical issue.
By considering these factors, you can choose an Advanced Web Application Firewall that best suits your hosting security needs, providing strong, adaptable, and scalable protection.
## **Securing Your Web Application Easily with Advanced WAF Configurations**
An Advanced Web Application Firewall (WAF) is a crucial tool in safeguarding web applications against modern cyber threats. Its ability to provide real-time protection, adapt to emerging vulnerabilities, and offer tailored configurations for various hosting environments ensures robust security. Investing time in configuring and automating your WAF properly will protect your web applications and secure your digital presence in today’s threat landscape.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# xCloud - WordPress Hosting Affiliate Program
> Unlock the potential to earn up to $719.8 in commissions with just a single referral by promoting as xCloud affiliate.
## Affiliate
# Join The xCloud Affiliate Program
Turn your influence into profit & maximize your earnings with each sale. Make your affiliation with xCloud highly rewarding.
[Apply Now](https://affiliate.xcloud.host/)
[Affiliate Dashboard](https://affiliate.xcloud.host/login)
## Up To
20%
### Affiliate Commission Per Sale
Join today and start earning 20% affiliate commission per sale
[Become Our Affiliate Now](https://affiliate.xcloud.host/)
## Perks
## Explore the Benefits of xCloud Affiliate Program
Discover the top advantages of becoming our affiliate partner.
## Lucrative Affiliate Commission
Unlock earnings at your own pace by promoting xCloud & amazing rewards
## Diverse Marketing Materials
Get exclusive promotional materials from us and kick start earring
## Monitor Campaign Performance
Track your growth and monitor your sales, clicks, and more
## Easy To Convert Visitors
Maximize conversions with xCloud – the ideal solution for your audience
## Early Access To News & Updates
Become a part of our team and get early news of our campaigns and releases
## Dedicated Affiliate Manager
Receive professional support from our dedicated team anytime
## Ideal Fit
## Who Can Apply For xCloud Affiliate Program?
It’s super easy to get started as an xCloud affiliate partner.
## Freelancers
## Small Businesses
## Marketers
## Agencies
## Teacher & Trainers
## Content Creators
## Onboarding
## How Does It Work
We welcome anyone with an online presence in xCloud’s affiliate program. Find out if our affiliate program is a right fit for your audience.
## Sign Up For Our Affiliate Program
Fill in the application form & join our affiliate program
## Earn Commissions For Every Sale
Earn 20% Commission for each Successful sale
## Promote xCloud To Your Audience
Create promotional content and share it with your affiliate link
## Earn Commissions For Every Sale
Earn 20% Commission for each Successful sale
## Dos and Don’ts
## How To Promote xCloud: What to Do & Avoid
Make the most out of our affiliate program through proven strategies. Here’s your roadmap of Dos and Don’ts.
- 
### Create videos for YouTube or other video sharing platforms.
- 
### Prepare educational material for on MOOC platforms.
- 
### Promote our tool on social media.
- 
### Write blogs about our solution.
- 
### Promote our solution via Mail.
- 
### Use our banner and logo inside your content.
- 
### Do not distort the facts to get more sells.
- 
### Avoid misrepresenting the benefits of using our tool to get more sells.
- 
### Do not use your own affiliate link to make purchases for personal use.
- 
### Do not share your affiliate link in discount and coupon listing sites.
- 
### Do not share unofficial discount offers.
- 
### Do not run paid ads on branded keywords (including our brand name or variations) to drive affiliate traffic.
Lorem ipsum dolor sit amet, consectetur adipisi cing elit, sed do eiusmod tempor incididunt ut abore et dolore magna
## FAQ’s
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### Is there a cost to join the xCloud Affiliate Program?
No, joining the xCloud Affiliate Program is completely free.
### How do I earn commissions?
Earn commissions by promoting xCloud services and generating sales through your unique affiliate links. You’ll receive a commission for each sale made through your referral.
### Which plans or lifetime offers qualify for commissions, and how do we track users?
We have all plans available to qualify for commissions.
### How are affiliate commissions paid?
Commissions are paid out through your preferred payment method, which you can set up in your affiliate dashboard. Payments are typically processed monthly.
### What is the minimum Pay-out Rate?
Our minimum payout rate is $50.
### How long do affiliates receive commissions for payments made by referred customers?
Affiliates receive commissions for payments made by their referred customers till the end of the first year since the customer’s subscription.
---
# WordPress Hosting for Agencies | xCloud
> WordPress hosting for agencies running client sites. Unlimited sites on every plan, a team and bill per client, free migrations, white label — plus free servers as you grow.
## Who this is for
Agencies, studios and freelancers who host other people's websites — the case where the hosting bill, the client relationship and the maintenance work are three different problems.
xCloud is a management layer over cloud servers. You either take a managed server from us or connect one you already run at DigitalOcean, Vultr, AWS, Google Cloud, Linode or Hostinger, and then run every client site through one panel.
## What matters when the sites aren't yours
**Unlimited sites and unlimited traffic on every plan.** There is no per-site fee. Server size is the only thing that changes your bill, so winning work does not automatically cost you more.
**A team per client, with its own billing.** xCloud separates work into teams. Create one per client or per retainer, invite the people who belong in it, and give each its own billing details and payment method — a client who wants the hosting on their own card can have it without you splitting invoices by hand.
**Roles instead of shared logins.** Developers, contractors and clients get the access their job needs, changed or revoked from Team Settings when an engagement ends.
**Staging with pull and push.** Any site can have a staging environment. Build there, let the client sign off, push to production — then pull production back down when you need to reproduce something real.
**Site isolation.** Every site runs under its own system user, so a compromise on one client's site cannot reach the others sharing the server. On shared hosting across a client book, that is the failure mode that ends relationships.
**Unlimited free migrations.** Our team performs them. Open a support ticket with the site details; there is a short prerequisite list for full server migrations, documented at `/docs/request-for-site-migration-support-from-xcloud/`.
**Monitoring that reaches you first.** Uptime, CPU, RAM and disk per server and per site, with alerts into Slack, WhatsApp or email.
## Pricing
Managed servers start at **$5/month** for 1 GB and run to 64 GB across fifteen plans, every one of them hosting unlimited sites. Bring your own server instead and you pay that provider for the machine and xCloud for the management layer.
There is no agency tier to buy into. See `/pricing/`.
## The xCloud Agency Partner Program
Bring client servers onto xCloud and the platform pays you back in servers. Tier is determined by your **monthly average of active, managed client servers** — there is no revenue target to calculate and no spend commitment to sign.
| | Growth Partner | Elite Partner | Pro Agency Partner |
| --- | --- | --- | --- |
| Active client servers required | 10 | 25 | 50+ |
| Free servers for life | 1 | 2 | 3 |
| License to sell xCloud to your clients | yes | yes | yes |
| Multi-client dashboard | yes | yes | yes |
| Priority partner support | yes | yes | yes |
| Partner badge for your site | yes | yes | yes |
| Preferred partner pricing | — | yes | yes |
| Dedicated migration help | — | yes | yes |
| Dedicated partner manager | — | — | yes |
| SLA priority | — | — | yes |
| Co-marketing | — | — | yes |
### The terms
- **Monthly average counts**, not a peak held for one afternoon.
- **30-day grace period** if you drop below your threshold. After it, only the free servers pause — your account, paid servers and every client site are unaffected, and the allocation resumes when you requalify.
- **Production servers only.** Test and staging deployments do not count, and a new server starts counting after 30 days live.
- **Applications are reviewed.** Onboarding is a short partner assessment call, not a signup form.
### How to join
1. Apply and tell us how many client servers you run and where they are today.
2. Onboard — tier activated, free server provisioned, badge and sales material delivered, added to the partner group.
3. Grow — every client server counts toward the next rung.
Apply at `https://support.xcloud.host/`.
**There is no partner directory yet.** A public listing where businesses find and hire xCloud partner agencies is planned, and is not offered as a benefit until it exists.
### Two adjacent programs, open to anyone
| Program | What it is | Where |
| --- | --- | --- |
| White label reselling | Your brand, logo, domain, packages and prices, billed on your own Stripe account. Clients never see xCloud. | `/reseller-hosting/` |
| Affiliate | 20% commission per sale, for clients you would rather refer than host. | `/affiliates/` |
## Agency hosting vs reseller hosting
They are different things and xCloud does both.
*Agency hosting* means you host client sites on infrastructure you control, billed to you, with the client generally aware of who the host is. *Reseller hosting* means you sell hosting as a product under your own brand, at prices you set, billing the client yourself.
Most agencies start with the first and add the second once hosting is worth billing for on its own. They can run side by side.
## Related
- `/pricing/` — all fifteen managed sizes, plus self-managed
- `/reseller-hosting/` — the white-label program in full
- `/affiliates/` — the 20% referral program
- `/compare/` — xCloud against other hosts
- `/docs/team-roles-permissions-in-xcloud/` — how teams, members and roles work
- `/docs/how-to-create-a-staging-environment-in-xcloud/` — staging, pull and push
- `/docs/how-billing-works-in-xcloud/` — per-team billing
- `/docs/overview-xcloud-white-label-feature/` — white label from the inside
---
# xCloud AI Agent Skills: Manage Servers and Sites by Asking
> xCloud AI Agent Skills let your AI assistant manage servers, sites, WordPress and SSL in plain English from Claude Code. Free, and installs in three commands.
**Note for agents:** this twin is hand-written. `/ai-agent-skills/` is an authored Astro route (`src/pages/ai-agent-skills.astro`), not a WordPress capture, so nothing regenerates this file — edit it alongside the page. The copy on both sides comes from `src/data/aiAgentSkills.ts`.
**Related:** [/mcp/](/mcp/) is the other way to point an agent at xCloud, and the one that works with clients other than Claude Code. [/ai-hosting/](/ai-hosting/) is the hub for everything AI on xCloud.
## Build a site by just asking, in plain English
Tell your AI assistant what you want, and it happens. Spin up a site, set up SSL, check a server, fix an issue. No dashboard, no code, no endpoints to learn.
- Works in Claude Code
- Built on the xCloud Public API
- Free for every xCloud user
## Setup
Connect your xCloud account in a couple of minutes. There is no complex setup.
1. **Install the skills.** Add the xCloud marketplace and install the plugin in Claude Code. Three commands and you are done.
2. **Add your API token.** Generate a token in your xCloud dashboard and add it to your Claude Code. It takes seconds.
3. **Just ask.** Say what you want in plain English. Your assistant does the rest.
### The three commands
```
/plugin marketplace add xCloudDev/xcloud-agent-skills
/plugin install xcloud
/reload-plugins
```
Then put your token in your Claude Code settings rather than in a chat message, so it never lands in conversation history:
```json
{ "env": { "XCLOUD_API_TOKEN": "your-token-here" } }
```
Restart Claude Code so it picks up the token, then ask `Check my xCloud API connection.`
Create a token at [app.xcloud.host/user/api-tokens](https://app.xcloud.host/user/api-tokens). Full walkthrough: [/docs/install-and-use-xcloud-ai-agent-skills/](/docs/install-and-use-xcloud-ai-agent-skills/).
### The five skills
`xcloud:servers` · `xcloud:sites` · `xcloud:wordpress` · `xcloud:ssl` · `xcloud:account`
Your assistant picks from these on its own. You never name them.
## What it does
The skills give your assistant a live line into your whole xCloud account, with the actions to handle what it finds.
| Area | What your assistant can do |
| --- | --- |
| **Server management** | Reboot servers, manage PHP and databases, set cron jobs, run the firewall and fail2ban, and provision WordPress |
| **Site management** | Check status, take and restore backups, manage domains, clear cache, configure SSH, and handle git |
| **WordPress management** | Update plugins and themes, scan for vulnerabilities, check PageSpeed, toggle debug mode, and get a one-time admin login link |
| **SSL management** | Install, renew, and check certificates, including free Let's Encrypt, before they expire |
| **Account and API key tokens** | Check who you are, manage API tokens, review Cloudflare integrations, and list your blueprints |
| **Built for Claude Code** | Use the skills right inside Claude Code. They are open source on GitHub, so you can see exactly what they do |
## Everything you manage on xCloud, now a conversation
- **Say "build me a site".** Your assistant creates the site, configures it, and sets up free SSL, all from one request.
- **Skip the busywork.** It backs up before changes, waits for jobs to finish, and confirms the result. You just watch.
- **Forget the technical stuff.** No endpoints, no IDs, no menus. You speak plain English, and it handles the rest.
## Pricing
**Free.** xCloud AI Agent Skills come with your xCloud account. No new plan, no add-on, no upgrade. The Public API you already have powers them, so they are yours from day one. No tiers, no upgrades, no credit card.
Your AI assistant may have its own usage cost from its provider. That is between you and them; xCloud charges nothing for the skills.
## FAQ
**What are xCloud AI Agent Skills?**
They are a set of skills that let your AI assistant manage your xCloud servers and sites in plain language. You describe what you want, and the assistant does it through the xCloud Public API. There are no endpoints to learn and no dashboard to open.
**Do I need to be a developer to use them?**
No. The whole point is plain language. If you can describe what you want in plain English, you can use the skills, whether that is building a site, checking a server, or renewing SSL.
**How much do they cost?**
Nothing. The skills are included free with your xCloud account. They use the Public API that comes with your account, so there is no extra plan and nothing to upgrade. Your AI assistant may have its own usage cost from its provider.
**Is it safe to let the AI take actions on my account?**
Yes. The skills only act with the permissions on your API token, and you control that token. For bigger changes like updates, the assistant backs up first and can roll back if something looks off, and every result comes straight from your account.
**Which AI assistants do the skills work with?**
The skills run in Claude Code. You install them as a plugin, add your xCloud API token, and you are ready to go. For other clients, use the MCP server at [/mcp/](/mcp/).
## Next
- [/mcp/](/mcp/) — the same account, over MCP, for any MCP client
- [/ai-hosting/](/ai-hosting/) — everything AI on xCloud
- [/ai-agent-hosting/](/ai-agent-hosting/) — hosting for the agents themselves
- [/docs/install-and-use-xcloud-ai-agent-skills/](/docs/install-and-use-xcloud-ai-agent-skills/) — the full setup guide
- [/pricing/](/pricing/) — plans and sizes for the hosting the skills manage
---
# AI Hosting | xCloud
> Deploy Claude Code, Codex, OpenClaw, Hermes, Paperclip, Odysseus or n8n onto a server you own, then operate that server by describing what you want. MCP, Agent Skills and the Public API are free on every xCloud account.
**Note for agents:** `/ai-hosting/` is a hub. It routes to the nine existing AI pages rather than replacing them; each product's own page is canonical for its setup steps and pricing.
## One account, two directions
| Direction | What it means | Cost |
| --- | --- | --- |
| Agents **drive** xCloud | The agent you already use reaches in and operates your infrastructure, through MCP, the Agent Skills or the Public API | Free with every account, including the free plan |
| xCloud **runs** agents | The agents you deploy live on servers you own | Server cost only; two ladders, see the table |
## Direction 1: agents that drive xCloud
Three doors, same account. Every one of them is free with every xCloud account, including the free plan, and every one reaches the same operations. They differ in what you set up and in what holds the credentials.
Every command, endpoint, scope and response below is verbatim from [`/agent-setup/prompt.md`](/agent-setup/prompt.md), which `llms.txt` advertises as the authoritative setup source.
### Door 1: xCloud MCP · [/mcp/](/mcp/)
One endpoint for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, OpenCode or anything else that speaks MCP. OAuth fires the first time the agent reaches for an xCloud tool, so no token sits in a config file, and you revoke access from the dashboard rather than by editing a machine.
```
claude mcp add xcloud --transport http https://app.xcloud.host/mcp
codex mcp add xcloud --url https://app.xcloud.host/mcp
```
Anything that takes an `mcpServers` block:
```json
{ "mcpServers": { "xcloud": { "url": "https://app.xcloud.host/mcp" } } }
```
- Stdio-only clients connect through `npx mcp-remote https://app.xcloud.host/mcp`.
- Headless and CI use a token scoped to `mcp:invoke`, since no browser can finish OAuth.
Clients confirmed in our own docs: Claude Code, Claude Desktop, Cursor, Codex, Windsurf, OpenCode. Anything else speaking Streamable HTTP works too: Google Antigravity, Gemini CLI, Grok and other MCP clients connect through the same endpoint, they are simply not individually certified by us.
Docs: `https://app.xcloud.host/mcp/docs`
### Door 2: xCloud AI Agent Skills · [/ai-agent-skills/](/ai-agent-skills/)
The MCP hands your agent the tools; the skills teach it xCloud's workflows: which tool to reach for, the guardrails, how to poll an asynchronous job to completion, and how to chain a multi-step change. Install both. Five skills ship in one plugin and the agent picks; you never name one.
| Skill | Owns |
| --- | --- |
| `xcloud:servers` | Servers, PHP, databases, cron, firewall and fail2ban, sudo users, services, provisioning |
| `xcloud:sites` | Site lifecycle: status, backups, domains, cache, SSH, git settings, deploys |
| `xcloud:wordpress` | Plugins, themes, updates, WP_DEBUG, magic login, vulnerabilities, PageSpeed |
| `xcloud:ssl` | Certificates: view, install, renew, status, delete |
| `xcloud:account` | Current user, API tokens, Cloudflare integrations, blueprints, health |
```
claude plugin marketplace add xCloudDev/xcloud-agent-skills
claude plugin install xcloud@xcloud-agent-skills
```
Then `/reload-plugins` to activate.
**Safety.** A skill acts only with the permissions on the token you issued, revocable at any time. Before a bigger change it backs up first, waits for the job to actually finish, and can roll back.
### Door 3: xCloud Public API
Everything the MCP exposes is a Public API operation underneath, so there is no capability gap between the paths. Use it directly when the integration lives inside your own product: a backend service, a provisioning script, a CI job, an agent loop of your own.
- **Base URL:** `https://app.xcloud.host/api/v1`
- **Auth:** Bearer token (Laravel Sanctum personal access token)
- **Reference:** OpenAPI 3.0.3 at `https://app.xcloud.host/api/v1/docs`
```bash
curl -s https://app.xcloud.host/api/v1/health
# -> {"status":"ok","version":"v1"}
```
`/health` needs no auth, which is what makes it useful: it isolates a network problem from a credential one.
**Token scopes:** `Full Access`, `read:servers`, `write:servers`, `read:sites`, `write:sites`, `mcp:invoke`. Create them at Settings → Developers → API Tokens, and give each token the narrowest scope that covers its job.
⚠️ **Write operations are asynchronous.** They return a task you poll, not a finished resource, so build in polling and a timeout rather than assuming the thing exists the moment the call returns.
### Things people actually type
Every one of these is inside the documented scope of the five skills:
- "Which of my sites have plugin vulnerabilities?" → `xcloud:wordpress`
- "Reboot staging-01 and tell me when it's back." → `xcloud:servers`
- "Back up the shop before I touch the theme." → `xcloud:sites`
- "Renew the certificate on every domain expiring this month." → `xcloud:ssl`
- "What PHP version is each server on?" → `xcloud:servers`
- "Give me a one-click login to the staging site." → `xcloud:wordpress`
- "Purge the cache on everything in production." → `xcloud:sites`
- "Add a cron job to run the queue worker every minute." → `xcloud:servers`
## Direction 2: agents that run on xCloud
Start from the job, not the brand:
| I want… | Deploy | How you reach it | From | Page |
| --- | --- | --- | --- | --- |
| a coding agent that keeps working after I close the laptop | Claude Code | Terminal, Claude web and mobile apps | $5.00/mo | [/claude-code-hosting/](/claude-code-hosting/) |
| to put the app Codex just built on a real domain | Codex | Your own domain, redeployed on git push | $5.00/mo | [/codex-hosting/](/codex-hosting/) |
| an assistant I can text like a person | OpenClaw | Telegram, WhatsApp, Slack, Discord | $9.99/mo | [/openclaw-hosting/](/openclaw-hosting/) |
| an agent that remembers everything between conversations | Hermes | Telegram, plus your tools, files and APIs | $9.99/mo | [/hermes-agent-hosting/](/hermes-agent-hosting/) |
| a workforce of agents with roles and budgets | Paperclip | Its own dashboard | $9.99/mo | [/paperclip-hosting/](/paperclip-hosting/) |
| a private AI workspace: chat, memory, research, documents | Odysseus | A private web workspace, your own LLM keys | $5.00/mo | [/odysseus-hosting/](/odysseus-hosting/) |
| to automate the plumbing between all of the above | n8n | 500+ integrations, webhooks, AI nodes | $5.00/mo | [/n8n-hosting/](/n8n-hosting/) |
| to run something that is not on this list | Your own stack | Deploy from Git, or a Docker Compose file | $3.00/server/mo | [/self-managed-hosting/](/self-managed-hosting/) |
**Two price ladders, not one.** Claude Code, Codex, Odysseus and n8n run on the standard managed-server ladder (from $5.00/mo). OpenClaw, Hermes and Paperclip run on a dedicated Cloud VPS sized for an always-on agent (from $9.99/mo). Do not merge them. See [/pricing/](/pricing/).
Beyond the table, these also deploy as one-click apps on the same servers: Ollama, LibreChat and Open WebUI. See [/ai-agent-hosting/](/ai-agent-hosting/).
**Odysseus is the exception to "one click".** It deploys from a Docker Compose file. You add the compose file, an admin login and your own external LLM API keys.
### Bring your own model
Anthropic (API key or Claude Code CLI token), OpenAI, OpenRouter, Moonshot AI (Kimi) and Gemini are supported today. Grok, xAI and Mistral are coming.
### Bring your own server
An xCloud Managed Server, or your own machine at DigitalOcean, Vultr, Linode, AWS or another provider. Same control panel either way.
## What it all runs on
- **Hardware:** 3GHz+ Intel Xeon · NVMe SSD · NGINX or OpenLiteSpeed · 31 locations
- **Security:** free SSL, auto-renewed · firewall + fail2ban · automated patching · AI Bot Blocker
- **Recovery:** scheduled backups · any S3-compatible store · snapshots · one-click restore
- **Visibility:** server and site monitoring · access and deploy logs · vulnerability scans · PageSpeed history
## FAQ
**What is free, and what do I pay for?** The control plane is free with every account, including the free plan. You pay only when you run a server. Your AI assistant's model usage is billed by its own provider.
**MCP or the Agent Skills?** MCP first: one endpoint, every MCP-compatible client, no token to store. The Skills are Claude Code-specific and add ready-made workflows on top.
**Why do the prices in the table differ?** Because they are two different products; see the two-ladder note above.
**Can I cancel?** Yes, any time. No lock-in.
## Start
- Create a free account: `https://app.xcloud.host/register`
- Connect via MCP: `https://app.xcloud.host/mcp/docs`
- Browse Agent Skills: `https://app.xcloud.host/agent/skills`
---
# [New Feature] How to Automate Security Updates with xCloud for Better Server Performance - xCloud
> Keep your server secure and automate security updates with xCloud. Reduce vulnerabilities, save time, and ensure optimal performance with no manual effort.
Keeping up with security and performance updates is essential to avoid vulnerabilities and ensure optimal performance. At xCloud, managing these updates has never been easier. You can now [automate security updates](/docs/reboot-server-with-automated-security-updates/) by leveraging the unattended upgrades feature straight from the platform. This managed WordPress hosting solution takes care of your server’s security by **automatically installing critical updates** as soon as they become available.
This way, you do not need to install each update individually. It helps you make sure your server remains secure without manual intervention. Here in this blog, we will discuss and go through how you can **automate security updates** with [**xCloud**](/) and keep your server in great shape.
## **💡 Why You Should Automate Security Updates for Servers**
Security updates are the pillars on which a strong server platform can be built. Without timely updates, servers can become vulnerable to security risks, performance issues, and [**potential downtime**](/best-practices-to-prevent-downtime/). In traditional setups, system or server administrators of a team often need to monitor updates manually and **perform regular maintenance**.
However, xCloud security update automation **eliminates this tedious process** by continuously monitoring critical patches and installing them automatically.
### **🌟 Benefits of Automated Security Updates at xCloud:**
- **24/7 Protection:** xCloud applies security updates automatically as soon as they are released, reducing the window of vulnerability.
- **Enhanced Performance:** You will get the general package updates that boost performance installed automatically at xCloud.
- **No Manual Intervention:** You can save time and effort by letting xCloud handle essential updates in the background.
- **Minimize Downtime:** If any update requires a server to reboot, you can choose an off-peak hour to schedule the reboot. This helps ensure a minimal disruption to your website.
## **🔂 How xCloud Security Update Automation Works**
When it comes to securing your servers, xCloud **makes the process effortless**. Using unattended upgrades, xCloud ensures that all critical updates, from kernel patches to application-level updates like [**Nginx**](https://nginx.org/) or [**PHP**](https://www.php.net/), are automatically applied.
If any updates require a server reboot, especially with **kernel updates**, you will receive notifications in two ways:
1. **Email Notification:** You will [**receive an email**](https://notificationx.com/blog/wordpress-email-marketing-automation-tools/) sent to your team’s email address mentioning that a reboot is necessary for the security update to take effect.
2. **Dashboard Notification:** The xCloud dashboard will send alerts with the message to initiate the reboot with just a few clicks.
With these notifications, you have **full control over reboot management**, making it convenient to update your server at times that work best for your traffic.
## **🖥️ How to Automate Security Updates on Your xCloud Server**
Automating security updates with xCloud is as simple as using other features and functionalities this managed WordPress hosting platform has. It lets you **set up a secure environment** with minimal effort. Follow these steps to manage your server updates:
### **Step 1: Log Into the xCloud Dashboard**
Log in to your [**xCloud app**](https://app.xcloud.host/) and head to your server’s dashboard to see if any updates are pending. If a reboot is needed, the dashboard will display a notification bar indicating which server requires the update with a **‘Reboot Now’** button.
### **Step 2: Reboot or Update the Server**
To apply the update, simply click the ‘**Reboot Now**’ button in the notification bar. This will immediately update your server and apply all necessary security patches. Alternatively, you can go into the **Server Update section** and manually manage the reboot process under the security settings.
### **Step 3: Schedule Automatic Reboots for Security Updates**
For even more convenience, you can automate this process by setting specific times for updates and reboots to occur automatically. Navigate to the ‘**Automatic Update**’ toggle, set your preferred time, and click ‘**Save Settings**’. This ensures that updates happen during off-peak hours to avoid any downtime.
_\[💡_ **_Pro Tip:_** _It is recommended to schedule your server reboots during low-traffic periods to ensure that visitors are not affected by any downtime.\]_
## **📌 Importance of Automated Reboots for Kernel Updates**
Kernel updates are crucial for both **security and performance improvements**. However, these updates often **require a server reboot** to take effect. By automating your security updates with xCloud, you can ensure that these critical patches are applied swiftly and seamlessly. This helps you **protect your server from vulnerabilities** while maintaining optimal uptime.
xCloud not only makes rebooting simple with one-click functionality but also allows you to schedule reboots at a time that is most convenient for you. Once the reboot is complete, your server will be fully updated and secure, as shown below.
### **➕ Additional Features That Complement Security**
Beyond automating security updates, xCloud offers a **suite of additional features** that make server management a breeze:
- **Monitoring & Alerts:** Stay informed about your server’s health with real-time alerts sent to your dashboard or phone via [**Slack**](/docs/configure-slack-integration-in-xcloud/) and [**WhatsApp**](/docs/how-to-configure-integration-with-whatsapp/).
- **Advanced Log Viewer**: Easily access important logs (e.g., **error logs, access logs**) to diagnose potential issues.
- **File & Database Management:** Manage your files securely with SFTP access and take advantage of easy [**database management using Adminer**](/docs/access-site-database-using-adminer-xcloud/).
These features, **combined with automated security updates**, provide a comprehensive approach to managing and securing your servers.
## **🔐 Automate Security Updates & Strengthen Security with xCloud**
By automating your server’s security updates, xCloud helps ensure that your server remains **safe, up-to-date,** and **performing optimally** – all without requiring you to lift a finger. With the ability to schedule reboots and receive real-time notifications, xCloud offers the ultimate solution for server security management. Whether you are managing a single site or multiple servers, automating security updates will save you time, reduce vulnerabilities, and give you peace of mind.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Unlock Full Control of Your Hosting: Automate Server Management with the xCloud API - xCloud
> Automate server management with the xCloud API. Create a token, set your scopes, and run your servers and sites from your own scripts.
If you run more than one or two sites, you have probably felt it. The same logins, the same clicks, and the same routine checks, repeated day after day. Each task on its own takes only a minute, but together they eat into the hours you would rather spend building. As your setup grows, doing everything by hand quietly becomes the thing that slows you down.
This is where the xCloud Public API comes in. It gives you a way to automate server management directly from your own scripts, pipelines, and tools, using the same operations you already run in the dashboard.
Instead of repeating each step yourself, you write the instruction once and let it run whenever you need it. The rest of this guide explains how the API works, how to create your first token, and what you can do once you have one.
## What the xCloud API actually does
Think of the API as a second set of hands. Anything you can do by clicking through the dashboard, you can also do with a simple HTTP request, whether that is listing a server, creating a site, triggering a backup, or checking on performance. The difference is that a request can be saved, scheduled, and repeated without you sitting there to run it. That small shift is what turns a pile of manual chores into a workflow that runs on its own.
Once your tasks live in code rather than in your daily to-do list, a few things become possible that are hard to manage by hand. Here is what that looks like in practice.
### Full platform access
The API mirrors the dashboard, so the operations you already know are all available from your own code. You are not limited to a handful of actions or a cut-down feature set. If you can do it in xCloud, you can almost certainly script it.
### Seamless integration
Your servers do not exist in isolation, and neither should the way you manage them. The API lets you connect xCloud to the tools you already rely on, from CI/CD pipelines to internal scripts and reporting jobs. That means fewer tabs to switch between and fewer steps that depend on someone remembering to do them.
### Automation
Some tasks need to happen on a regular rhythm, like restarts, deployments, and backups. With the API, you can set these to run on a schedule and stop thinking about them. The work still gets done, just without a person triggering it each time.
### Real-time insights
Good decisions depend on knowing what your servers are actually doing. The API lets you pull CPU, memory, disk, and network data on demand, exactly when you need it. From there, you can feed those numbers into your own dashboards or wire them up to alerts that warn you before a small issue becomes a real one.
### Scoped permissions
Not every script needs the keys to everything. The API lets you hand each token a specific set of permissions, with separate read and write access for servers and sites. A reporting tool can be given read-only access, while a deployment script gets just enough to do its job and nothing more.
### Bulk management
Repeating the same change across many sites by hand is slow and easy to get wrong. The API lets you act on many servers and sites in a single workflow, applying the same update everywhere at once. For anyone [**managing sites for clients**](/managed-hosting/), this alone can save hours every week.
## How to create your API token
Getting your first token takes only a few minutes inside the [**xCloud dashboard**](/docs/how-to-access-the-xcloud-api/) The process is simple, but each step matters, so here is how to do it from start to finish.
### Step 1: Open API settings
Log in to your xCloud dashboard to begin. From the left sidebar, go to Settings, select Developers, and then open API Tokens. This is the home for every token tied to your account, and it is where you create, view, and remove them. Click Create New Token to get started.
### Step 2: Name the token and choose permissions
A dialog will appear asking for a name and a set of permissions. Give the token a clear name that tells you where it will be used, such as “Reporting Dashboard” or “Deployment Pipeline,” so you can recognize it later. Then choose the scopes it should carry from the options below.
- Full Access (all permissions)
- read:servers
- write:servers
- read:sites
- write:sites
A good rule of thumb is to give each token the least access it needs to do its job, since a reporting script rarely needs permission to change anything. Once you are set, click Create Token.
### Step 3: Copy and store your token
Your token is shown only once, right after you create it, and it will never be displayed in full again. Copy it straight away and keep it somewhere safe, such as a secrets manager or an environment variable. Avoid pasting it into a plain file or anywhere it might be shared by accident. If you do lose it, you cannot recover the original, so you will simply create a new one and update wherever the old one was used.
## What you can build with it
Now for the more interesting part: what all of this actually saves you. The examples below are some of the most common jobs teams hand over to the API, but they are only a starting point. Each one replaces a task you would otherwise do by hand, often more than once a week.
### Automated WordPress management
Keeping WordPress updated across many sites is important, but doing it manually is tedious. The API lets you [](/hosting-for-wordpress/)**[update plugins, themes, and core](/hosting-for-wordpress/)**, activate what you need, and rescan sites after manual changes. You can run all of this on a schedule, with an optional backup taken before an update so you always have a safe point to return to.
### Deployment pipelines
If you deploy code regularly, the manual steps around each release add up fast. The API lets you trigger Git deployments and clear cache as part of your pipeline, so new code reaches production without extra clicks. This keeps your releases consistent and removes the small mistakes that creep in when steps are done by hand.
### Backups and maintenance
Backups and upkeep are easy to put off until the moment you wish you had not. With the API, you can [start backups](/features/), manage cron jobs, and run routine maintenance at times that suit your traffic rather than your calendar. Setting these to run automatically means the work happens whether or not anyone remembers to do it.
### Security monitoring
Staying on top of security is far easier when the information comes to you.The API lets you pull [](/how-xcloud-keeps-your-wordpress-sites-safe/)**[vulnerability scan results](/how-xcloud-keeps-your-wordpress-sites-safe/)**, manage firewall rules, and review banned IP addresses across your sites. You can build this into a regular check or a dashboard, so a new risk is something you notice quickly rather than weeks later.
### Performance tracking
A site that slows down rarely announces it, which is why steady monitoring matters. The API lets you queue PageSpeed Insights scans and follow Core Web Vitals over time. With that history in hand, you can spot a slowdown early and act on it before it starts to affect your visitors.
### Agency and multi-site work
Managing sites for clients multiplies every routine task by the number of sites you run. The API lets you handle many servers and sites from a single workflow, applying updates and checks across all of them at once. For an agency, this keeps client work organized and frees up time that scaling would otherwise eat away.
## A quick tour of what is available
The full documentation lists every endpoint in detail, but a map helps before you dive in. Here is the lay of the land, grouped by the part of your hosting each set of endpoints controls. Knowing roughly where things sit makes it much faster to find the exact call you need later.
## Server operations
This is where you manage the servers themselves. You can list and inspect them, reboot when needed, manage services, set PHP versions, and read monitoring data. In short, it covers the health and configuration of the machines your sites run on.
### Site management
These endpoints handle everything at the site level. You can create and view sites, and manage SSL certificates, domains, [**staging environments**](/how-to-setup-staging-site-guide/), and deployment logs. It is the day-to-day side of running individual sites rather than the servers beneath them.
### WordPress operations
For WordPress sites, a dedicated set of endpoints handles the software itself. You can list plugins and themes, queue updates for plugins, themes, and core, and activate components. This is what powers the automated WordPress management described earlier.
### Backups and scheduling
Protecting your data and automating recurring jobs both live here. You can trigger backups, check their status, and manage cron jobs at both the server and site level. Together, these cover the routine work that keeps a site safe and running smoothly.
### Security and integrations
This group helps you keep sites protected and connected to outside services. You can review vulnerabilities from Patchstack and Wordfence, manage [**firewall and fail2ban rules**](/docs/server-and-website-security-with-xcloud/)**,** and see connected Cloudflare accounts. It brings your security signals and integrations into the same automated workflow.
### Performance
Finally, a set of endpoints focuses on how fast and healthy your sites are. You can run PageSpeed Insights scans and track Core Web Vitals and Lighthouse scores for each site. This is the data that tells you whether your performance work is paying off.
## Put Your API Token to Work with xCloud Pulse
If you would rather not write any code yet, there is an easy way to put your new token to use right away. xCloud Pulse is a native macOS app that lives in your menu bar and keeps a live view of your whole xCloud account. It is built on the same xCloud Public API you have just set up, so the token you created is all it needs to connect. Best of all, it is free for every xCloud user.
Once connected, Pulse shows every site and server the moment you open it, along with status, SSL, backups, vulnerabilities, and any open issues. You can act on what you find right there, whether that is purging a cache, triggering a backup, or copying a server IP, all without opening a browser. A built-in search lets you jump to any site, server, or action by typing a few letters. Because it is a true native app rather than a browser tab, it stays light on your machine.
In many ways, Pulse is the clearest example of what the API makes possible: a single token, powering a tool you can use every day. Setting it up takes only a few minutes, from installing the app to connecting your account and choosing how often it refreshes. For the full step-by-step setup, head to the [**xCloud Pulse documentation**](/docs/install-and-set-up-xcloud-pulse-macos-menubar/), which walks through everything from installing the app to reading your dashboard.
[Download xCloud Pulse Now](/xcloud-pulse/)
## Start automating & Take Full Control of Your Hosting Today
Moving from manual clicks to a few well-placed scripts is one of the simplest upgrades you can make to how you run your hosting. The setup takes only a few minutes, and the payoff in saved time and fewer repetitive tasks shows up almost right away. You do not have to automate everything at once, either, since even one scheduled task is a clear step forward. The xCloud API puts the full range of dashboard operations within reach of a single request.
The best way to get comfortable is to start small. Create a token, give it the right scopes, and use it to automate server management for one task you repeat often. When you are ready to go further, the API documentation walks through every endpoint so you can keep building at your own pace.
If you found this guide helpful, feel free to subscribe to our blog for more tutorials, guides, and tips on web hosting and server management. You can also join our Facebook community to share ideas and connect with other xCloud users.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and take part in discussions.
---
# AWS Lightsail vs AWS EC2 Instance: Which One Should You Use? - xCloud
> AWS Lightsail vs AWS EC2 Instance: Which one should you use? Compare pricing, features, use cases, and find the right service for your project.
When you build something in the cloud, choosing the right service matters a lot. If you are working with Amazon Web Services (AWS), two options might come up quickly: [**AWS Lightsail and AWS EC2**](/integrate-aws-with-xcloud/) instances. These services help you deploy applications, websites, and virtual servers. But they work differently and serve different needs.
Read the comparison of AWS Lightsail vs AWS EC2 to help you decide which is the better option for your project.
## **What Is AWS Lightsail?**
**AWS Lightsail** is a straightforward cloud service that helps you easily start and manage virtual private servers. It is a good option for beginners looking to explore AWS.
Lightsail aims to simplify cloud computing. You can set up a server in just a few minutes without dealing with complicated networking or configuration.
This service is suitable for developers, small businesses, and hobbyists who want an easy way to host websites, run simple applications, or try out different server setups.
### **Key Features**
- **Pre-configured instances**: You get pre‑built application stacks like WordPress, Node.js, LAMP, or a plain Linux OS with just a few clicks.
- **Fixed monthly pricing**: You pay a flat rate based on your instance type. There are no surprise bills.
- **Built-in services**: Lightsail includes options for load balancers, databases, storage, and DNS.
- **Simple interface**: The dashboard is clean and easy to navigate. You do not need to know how to use the AWS Command Line Interface or deep AWS tools to get started.
### **Common Places Where EC2 Is Used**
Lightsail is best for projects where simplicity matters more than full control. Here are some common examples:
- Hosting a blog or a small website.
- Creating a development or staging server.
- Launching simple web applications.
- Running personal projects or portfolio websites.
If you want to launch something quickly without worrying about low‑level details, Lightsail gives you the tools you need with less hassle.
**What Is an AWS EC2 Instance?**
**Amazon EC2 (Elastic Compute Cloud)** is a powerful and flexible service in the AWS ecosystem. It gives you control over your virtual machines and helps you create customizable and scalable cloud environments.
The main purpose of EC2 is to provide developers and businesses with **flexible computing** **power** in the cloud. With EC2, you can launch many instances, select from a variety of operating systems, and set up your virtual server as you want.
This service is for users who need advanced features, complex setups, or handle heavy workloads. EC2 is commonly used in production environments where high availability, security, and performance are important.
### **Key Features**
- **Wide selection of instance types**: EC2 offers hundreds of instance types based on CPU, memory, storage, and GPU capabilities.
- **Advanced networking**: You get features like VPC (Virtual Private Cloud), subnets, security groups, route tables, and more.
- **Elasticity**: You can scale your infrastructure up or down automatically using Auto Scaling and Elastic Load Balancing.
- **Integration with AWS services**: EC2 works smoothly with almost every other AWS tool, from RDS and S3 to CloudWatch, IAM, and Lambda.
- **Custom AMIs**: You can create and reuse your own server images to speed up deployment across teams or environments.
### **Common Places Where EC2 Is Used**
EC2 is great for large or complex applications that need strong performance and detailed control. Here are some common uses:
- Hosting high-traffic web applications or APIs.
- Running machine learning models or big data processing tasks.
- Deploying containerized workloads using ECS or Kubernetes.
- Managing large-scale enterprise systems or SaaS platforms.
- Setting up custom security, networking, or compliance requirements.
With EC2, you have the power to build almost anything in the cloud, but it comes with a steeper learning curve and more responsibility for management.
## **AWS Lightsail vs AWS EC2 Instance: Feature Comparison**
Now that you understand the basics of both services, let us compare **AWS Lightsail vs AWS EC2 instance** across several critical features. This section will help you see where each service shines and where it may fall short depending on your needs.
### **Pricing – Lightsail vs EC2**
**AWS Lightsail** uses a **fixed monthly pricing model**. You select a plan, and you know exactly how much it will cost you every month. These plans include a set amount of RAM, vCPUs, SSD storage, and data transfer. For example, a Lightsail plan with 2 GB RAM, 1 vCPU, and 60 GB SSD might cost you $10 per month.
**Amazon EC2**, on the other hand, works on a **pay-as-you-go model**. You are billed per second (or per hour for some types) for compute, storage, and data transfer. While this offers flexibility, it also requires you to monitor your usage closely to avoid unexpected costs. EC2 does offer **Savings Plans** and **Reserved Instances** to help reduce long‑term expenses, but these require upfront planning and commitment.
If you are cost-conscious and prefer predictable billing, Lightsail offers better simplicity. EC2 is better if you are optimizing for efficiency, scalability, or advanced workload needs.
### **Ease of Use And Setup**
Lightsail is designed to be **beginner-friendly**. You can launch a server in under a minute using a clean, intuitive dashboard. There is no need to worry about subnets, VPCs, or IAM permissions in the early stages.
EC2 provides **fine-grained control**, but that comes with complexity. You need to configure instance settings, assign security groups, choose an AMI, and possibly use the AWS CLI. While EC2 supports automation and scripting, the initial learning curve is steeper.
If you are new to cloud computing or just want to get something up and running fast, Lightsail offers a smoother experience. EC2 is best if you are comfortable managing AWS infrastructure.
### **Performance And Instance Types**
EC2 clearly wins when it comes to **performance variety**. You can choose from hundreds of instance types tailored to specific tasks, such as compute-intensive, memory-optimized, GPU-based, or general-purpose.
Lightsail offers a **limited set of instance sizes**, typically ranging from 512 MB to 32 GB of RAM. These are great for lightweight workloads, but not for high-demand applications.
If you need custom compute power or want to adjust performance settings precisely, EC2 is a better fit. For simpler workloads, Lightsail’s pre-configured instances are more than enough.
### **Networking And Security**
Lightsail handles networking with basic tools. You get static IPs, a built-in firewall, and private networking between your Lightsail resources. It keeps things simple.
With EC2, networking is more **advanced and flexible**. You can launch instances inside a Virtual Private Cloud (VPC), define custom subnets, use route tables, NAT gateways, internet gateways, and security groups. You have full control over how your network behaves.
So, if you need basic networking, Lightsail is fine. But if your application has complex network architecture, EC2 is the clear winner.
### **Storage Options**
Lightsail bundles SSD storage with your instance. You can add extra storage volumes if needed, but your flexibility is limited.
EC2 lets you choose from multiple types of **Elastic Block Store (EBS)** volumes: General Purpose SSD (gp3), Provisioned IOPS (io2), Throughput Optimized HDD (st1), and others. You can also use **instance store volumes** for high-performance temporary storage.
For demanding storage needs and fine-tuned performance, EC2 offers more choices and better scalability.
### **Scalability**
Lightsail allows for **vertical scaling**. You can upgrade to a larger plan, but that often means migrating your application to a new instance. Lightsail also offers basic load balancers, but horizontal scaling is limited.
EC2 supports **auto scaling groups**, which means your system can scale up or down automatically based on traffic. Combined with **Elastic Load Balancers**, EC2 is ideal for applications that must handle changing demand reliably.
If scalability is critical for your project, EC2 provides more control and options.
### **Management And Monitoring Tools**
Lightsail includes simple monitoring charts in the dashboard. You get basic CPU, network, and disk metrics. These are fine for personal or small business projects.
EC2 integrates with **Amazon CloudWatch**, **CloudTrail**, and other AWS tools. You can monitor nearly everything: CPU, memory, disk, logs, network flow, even user activity. You can create custom dashboards, set alarms, and automate responses to events. If observability and performance tracking are priorities, EC2 gives you more power and depth.
### **Supported OS, Containers, And Apps**
Lightsail supports popular OS choices like Ubuntu, Debian, CentOS, and Amazon Linux. You can launch instances with pre-installed software stacks such as WordPress, Magento, or LAMP.
EC2 supports **all of that and more**. You can choose from thousands of Amazon Machine Images (AMIs), build your own AMIs, and use custom operating systems. EC2 also integrates tightly with **Docker**, **ECS**, **EKS**, and Kubernetes.
If you need total control over your system environment or want to run containers at scale, EC2 is the better option.
### **Backup And Disaster Recovery**
Lightsail lets you create **manual snapshots** of your instances and disks. It is simple and quick, but not automated by default.
EC2 supports both **manual and automated snapshots**, image backups (AMIs), and disaster recovery across **multiple Availability Zones and Regions**. You can build fault‑tolerant architectures using EC2.
For serious production environments where uptime matters, EC2 gives you better disaster recovery options.
### **Ecosystem And Integrations**
Lightsail is a **standalone experience**, although it integrates with a few other AWS services like Route 53 and RDS. It is a good fit for isolated or small setups.
EC2, however, is part of the **full AWS ecosystem**. You can connect your EC2 instances with S3, IAM, Lambda, CloudFront, SNS, RDS, and many more services. This opens the door to building complete cloud architectures.
If you plan to grow your cloud footprint, EC2 offers a lot more flexibility and expansion.
## **Which One to Choose Between Lightsail And EC2?**
When deciding between AWS Lightsail and AWS EC2, think about what your project needs. Some projects require simplicity and speed, while others need power, flexibility, and customization.
### **Simple Websites, Blogs, or Portfolios — Choose Lightsail**
If your goal is to launch a basic website, personal blog, or portfolio, then **AWS Lightsail** is a great choice. It is easy to get started, and you do not need to deal with complex configurations.
Lightsail even provides **pre-built blueprints** for WordPress, Joomla, and other CMS platforms. You can launch a server, attach a domain, and publish content in under an hour. With static IPs, built-in DNS, and automatic snapshots, managing your small website becomes effortless.
Because the pricing is fixed and transparent, you always know what you will pay. This makes Lightsail a popular choice for:
- Freelancers launching personal projects.
- Small business websites.
- Student or hobby websites.
- Developers are testing new ideas.
If you value speed, predictability, and simplicity, Lightsail delivers exactly what you need without the AWS complexity.
### **Small Business Apps or Start‑Ups — Lightsail or EC2 (Depends on Growth)**
If you are building a **web application**, a **mobile backend**, or a **software-as-a-service (SaaS)** product, you could go with either Lightsail or EC2. Your choice depends on how much control you need and how fast you plan to scale.
**Lightsail** works well in the early stages:
- Easy to deploy basic applications.
- Built-in load balancer (though limited in features).
- Managed database add-ons.
- Affordable plans and quick setup.
However, once your app gains traction, you might hit the ceiling. You may need features like auto-scaling, fine-tuned security, or integration with IAM roles and other AWS services.
That is where **EC2 becomes more suitable**. It lets you design scalable architectures from day one:
- Auto scaling groups for traffic spikes.
- Advanced networking and monitoring.
- Tight integration with AWS services like RDS, Lambda, and S3.
If your app has the potential to grow rapidly, it is smarter to start with EC2 or plan a clear path to migrate when the time comes.
### **Growing Apps or Enterprise Workloads — Choose EC2**
When building a system for high-traffic websites, complex enterprise workloads, or resource-heavy apps, **Amazon EC2** is the only choice. Why? Because EC2 gives you:
- High-performance computing.
- Access to GPUs for AI and ML models.
- Security policies and compliance controls.
- Support for hybrid cloud and on-prem integration.
- The ability to manage thousands of servers across multiple availability zones.
Businesses running mission-critical applications need the flexibility to fine-tune their infrastructure. EC2 gives you that freedom. You can optimize performance, minimize downtime, and create custom automation rules.
Whether you are managing a corporate ERP system, financial service platform, or healthcare application with strict compliance, EC2 provides the control you need to stay secure, reliable, and scalable.
### **Migrating from Lightsail to EC2**
What if you start with Lightsail and later decide to move to EC2? That is possible and fairly straightforward but it does require planning. Here are the key steps:
1. Create a snapshot of your Lightsail instance.
2. Export the snapshot to Amazon EC2.
3. Launch a new EC2 instance from the snapshot.
4. Reconfigure DNS, security groups, and networking as needed.
AWS provides documentation to help you with this process. Keep in mind, the environments are not identical, so testing is essential before making the switch.
A common approach is to **prototype on Lightsail**, and once your traffic or infrastructure needs increase, **migrate to EC2** for better flexibility.
## **Pros and Cons of AWS EC2 & Lightsail**
To help you decide, here is a simple comparison of **AWS Lightsail and** **AWS EC2**. Read the table below to learn the benefits and drawbacks of each service, making it easy for you to see which one meets your needs.
### **Lightsail Pros And Cons**
**Pros**
**Cons**
Fixed monthly pricing
Limited instance types and scalability
Beginner-friendly interface
Fewer customization and networking tools
Fast and easy setup
Not ideal for complex apps or high traffic
Includes bundled storage and bandwidth
No support for advanced automation
Pre-configured app templates
Limited AWS integrations
Built-in snapshots and load balancer
No support for spot instances or GPUs
### **EC2 Pros And Cons**
**Pros**
**Cons**
Complete control over compute resources
Requires more configuration and management
Supports wide range of instance types
Pricing can be unpredictable without planning
Advanced networking and security
Steeper learning curve
Full access to AWS ecosystem and services
More responsibility for backups and scaling
Ideal for enterprise and high-performance apps
Separate charges for storage and data transfer
Supports automation, custom AMIs, and autoscaling
Interface is more technical and complex
## **Integrate AWS Server with xCloud Using EC2 Or Lightsail**
xCloud Host integrates smoothly with [**Amazon Web Services**](https://www.facebook.com/share/v/19GyjxdXHW/) (AWS). You can deploy your apps directly using either Lightsail or EC2, depending on what your project needs.
You have the freedom to choose the best setup:
- Choose Lightsail if you want fast deployment with less technical setup. It is perfect for small projects, websites, or MVPs.
- Choose EC2 if you need deep control, high performance, or want to scale your app across complex cloud environments.
With xCloud Host, you do not need to be a cloud expert. You get a clean and user-friendly interface that guides you through every step. Whether you are uploading code, linking domains, or setting up backups, everything is streamlined.
You can manage your entire cloud server from a single dashboard. You can start, stop, monitor, or scale your instance in just a few clicks.
xCloud Host brings the power of AWS to your fingertips, but without the usual hassle. It lets you focus on your app, not the infrastructure.
Watch the walkthrough video here to see how easy it is to deploy with xCloud Host using Lightsail or EC2. It only takes a few minutes to go live.
## **AWS Lightsail vs AWS EC2 Instance:** **Choose Based on your Application’s Preferences**
Choosing between AWS Lightsail vs AWS EC2 instance is not just a technical decision. It is also a decision about your goals, your budget, your experience, and your future growth plans.
If you need something simple, predictable, and fast to launch, then AWS Lightsail is the right place to start. It gives you pre-configured options, a friendly interface, and fixed monthly pricing that works well for blogs, small business apps, and prototypes.
But if you are building something complex, expecting growth, or needing full control over your cloud environment, Amazon EC2 is the better option. It is more flexible, more powerful, and gives you the tools to scale up, optimize, and connect to the full range of AWS services.
Did you find this blog helpful? If you find this blog useful and want to read more blogs like this one, [**Subscribe**](/blog/) to our blogs and join our [**Facebook Community**](https://www.facebook.com/groups/xcloud.community) to connect with more people with common interests.
---
# 7 Best Cloudways Alternatives & Competitors in 2026: Complete Expert Guide - xCloud
> Discover the 7 best Cloudways alternatives for 2026. Compare pricing, performance, and features to save up to 40% with expert recommendations.
Cloudways has powered over **570,000 websites** since its founding, but after DigitalOcean’s acquisition in **2022**, many users are actively researching alternatives of Cloudways due to pricing hikes, limited server control, and slower innovation.
According to [**Trustpilot reviews**](https://www.trustpilot.com/review/xcloud.host), thousands of WordPress professionals are actively migrating to alternatives that offer better value without sacrificing performance.
The managed **cloud hosting** market is projected to reach $527.07 billion by 2032 (according to Fortune Business Insights), and WordPress powers 43.4% of all websites globally (according to W3Techs). With these numbers, choosing the right alternatives can significantly impact your site’s performance, security, and bottom line.
Check out the seven expert-recommended [**best Cloudways alternatives**](/xcloud-vs-cloudways/), comparing pricing, features, and real-world performance data to help you make an informed decision.
## Table of Contents
## **Quick Summary / TL;DR**
Too Long; Didn’t Read? Here’s what you need to know about the best Cloudways alternatives in 2026.
If You Want To…
Use This
Expected Savings
Migration Time
Save 40%+ with the same server specs
xCloud
~40% lower costs
6-30 minutes
Premium managed WordPress
Kinsta
Premium pricing
1-2 hours
Enterprise-grade hosting
WP Engine
Enterprise pricing
2-4 hours
Budget-friendly with Google Cloud
SiteGround
20-30% savings
1-2 hours
Maximum server control
RunCloud
Varies by provider
30-60 minutes
Agency white-label hosting
GridPane
Varies by provider
1-2 hours
Self-managed panel alternative
ServerAvatar
60-70% savings
30-60 minutes
### **Expert Recommendation:**
According to _**[Online Media Masters](https://onlinemediamasters.com/xcloud-review/),**_ xCloud stands out among modern hosting alternatives of Cloudways, delivering approximately 40% cost savings compared to Cloudways.
Among all tested alternatives of Cloudways, xCloud consistently ranks highest for performance thanks to its lightweight control panel and OpenLiteSpeed support. This makes xCloud one of the most recommended Cloudways alternatives for WordPress professionals.
- **Best for Cost-Conscious Users:** **xCloud** – Free tier with 1 server + 10 sites, root access, bring-your-own-provider flexibility
- **Best for Premium WordPress:** Kinsta – Google Cloud C2 machines, 24/7 expert support, enterprise-grade infrastructure
- **Best for Agencies: xCloud or GridPane** – White-label capabilities, team management, client billing features
## **Why WordPress Users Are Leaving Cloudways in 2026**
Before diving into more detail**s**, understanding why users are leaving Cloudways helps identify which Cloudways alternative best fits your needs. Rising costs, limited control, and slower innovation are driving WordPress professionals toward more flexible Cloudways competitors in 2026.
### **The Price Hike Problem**
Cloudways operates as a managed layer on top of cloud providers, adding significant markups to base server costs. According to multiple independent analyses:
- A DigitalOcean server that costs $6/month directly is priced at $14/month on Cloudways (approximately 133% rise)
- Vultr High Frequency servers see similar markups – a $24/month Vultr server costs $60/month on Cloudways (150% rise)
- Google Cloud and AWS servers carry even higher percentage markups.
### **Limited Server Control**
Cloudways does not provide root access to servers. For developers and agencies requiring custom configurations, this limitation can be a dealbreaker. Key restrictions include:
- No SSH root access
- Limited custom NGINX configuration
- No OpenLiteSpeed option
- Restricted Cloudflare Enterprise integration (limited dashboard access)
### **Innovation Concerns Post-Acquisition**
Since DigitalOcean acquired Cloudways, user reviews indicate concerns about:
- Slower [feature development](/features/) compared to competitors
- Price increases
- Reduced focus on multi-cloud flexibility
## **How We Ranked These Cloudways Alternatives**
Industry best practices for evaluating competing platforms include multiple criteria such as cost efficiency, performance, and flexibility. To fairly rank these hosting platforms, we compared each using real-world benchmarks. deliver measurable value beyond marketing claims. The ranking methodology considers:
Criteria
Why It Matters
Weight
Cost vs. Value
Direct comparison with Cloudways pricing at equivalent specs
High
Server Control
Root access, custom configurations, provider flexibility
High
WordPress Optimization
Caching, PHP versions, WordPress-specific features
High
Performance
Server response times, infrastructure quality
High
Migration Ease
Free migration tools, documentation quality
Medium
Support Quality
Response times, expertise level, and availability
Medium
Innovation
Recent feature releases, roadmap activity
Medium
## **Comparing the Best Cloudways Alternatives** **in 2026**
This section breaks down pricing, control, and ideal use cases. Each provider listed below represents a proven option among all comparable providers, helping you quickly identify the strongest alternatives of Cloudways for your specific goals.
Rank
Provider
Starting Price
Server Control
Best For
🥇 1
Kinsta
$35/mo
★★★☆☆ Limited
Premium WordPress, high-traffic sites
🥈 2
xCloud
Free (**Pros**) / $5/mo
★★★★★
Full Root
Cost-conscious users, agencies, developers
🥉 3
WP Engine
$20/mo
★★★☆☆ Limited
Enterprise, agencies needing support
4
SiteGround
$2.99/mo
★★☆☆☆ Minimal
Budget users, beginners
5
RunCloud
$8/mo
★★★★★ Full Root
Developers wanting panel control
6
GridPane
$50/mo
★★★★★ Full Root
Agencies, hosting resellers
7
ServerAvatar
Free / $6.67/mo
★★★★★ Full Root
Budget-conscious developers
## 🥇**1\. Kinsta – Best for Premium Managed WordPress**
Kinsta has established itself as a premium managed WordPress host, consistently ranking among the top performers in independent benchmarks. The platform runs exclusively on Google Cloud Platform’s C2 compute-optimized virtual machines, delivering enterprise-grade infrastructure.
According to industry analysts, Kinsta performs exceptionally well in environments that demand maximum reliability and dedicated WordPress expertise. However, this level of performance comes at a premium price point that may not suit budget-conscious users.
### **Key Features**
- **Google Cloud C2 VMs:** High-performance compute-optimized virtual machines
- **35 Global Data Centers:** Wide geographic coverage
- **Built-in CDN:** Cloudflare-powered content delivery
- **MyKinsta Dashboard:** Custom-built, intuitive control panel
- **24/7 Expert Support:** WordPress-specialized support team
- **Automatic Daily Backups:** One-click restore functionality
### **Pros and Cons**
**Pros**
**Cons**
✅ Google Cloud C2 premium infrastructure
❌ Higher pricing ($35/mo starting)
✅ Excellent support reputation
❌ No root access to servers
✅ User-friendly custom dashboard
❌ Visitor-based pricing can get expensive
✅ Free migrations included
❌ No email hosting included
✅ 35 data center locations
**Best for:** Businesses and high-traffic websites that prioritize reliability over cost, and users who want hands-off management with premium WordPress support.
## **🥈2. xCloud – Best for Cost Savings & Full Server Control**
According to independent reviews from**[Online Media Masters](https://onlinemediamasters.com/xcloud-review/)** and **[Blog Marketing Academy](https://www.blogmarketingacademy.com/xcloud-hosting-review/),** xCloud has emerged as one of the most compelling **Cloudways alternatives** for users prioritizing cost efficiency and server control. Among all **competing platforms** reviewed, xCloud offers the best balance of pricing, performance, and flexibility. This positions xCloud at the top of the **alternatives** Cloudways list for 2026.
xCloud powers over **100,000 websites** across **10,000+ servers** globally (according to xCloud’s 2025 Year in Review), with users consistently reporting **40% cost savings** and noticeably faster performance compared to Cloudways on identical server specifications.
The platform offers a unique “bring your own provider” model – connect servers from Vultr, DigitalOcean, Hetzner, AWS, Google Cloud, Linode, or any Ubuntu VPS. This eliminates the markup entirely, meaning you pay retail prices directly to your cloud provider plus xCloud’s lightweight panel fee. Besides, xCloud provides fully managed hosting with xCloud Managed Servers.
### **Key Features**
- [**Free Tier**](/)**:** Allows the deployment of 1 server and 10 sites at zero cost, ideal for testing
- [**Root Access**](/features/)**:** Full SSH root access to servers (Cloudways doesn’t offer this)
- [**OpenLiteSpeed Support**](/introducing-openlitespeed-server-in-xcloud/)**:** LiteSpeed web server option for superior WordPress performance
- [**7G/8G Firewall**](/features/)**:** Built-in WAF protection against XSS, SQL injection, bad bots
- [**Full Server Backups**](/features/)**:** Complete server-level backups, not just site-level
- [**Unlimited Sites**](/)**:** No restrictions on websites per server
- [**WordPress Management**](https://xcloud.host/wordpress-hosting/)**:** One-click updates for core, themes, and plugins
### **How to Migrate from Cloudways**
xCloud offers free migration assistance for all users. To migrate your server, follow the steps below:
1. Provision a new destination server in xCloud.
2. Enter the source server’s IP address.
3. Set the SSH port and use root as the SSH username.
4. Choose an authentication method and configure
5. Select the server or specific sites you want to migrate.
6. Choose Go Live or Create Demo Site
7. And start the full server migration.
### **Pros and Cons**
**Pros**
**Cons**
✅ ~40% cheaper than Cloudways with same specs
❌ Requires choosing your own cloud provider
✅ Free tier with 1 server + 10 sites
❌ Newer platform (launched 2024)
✅ Full root access to servers
❌ Support relies heavily on documentation
✅ OpenLiteSpeed + NGINX options
✅ 5-star Trustpilot rating (295+ reviews)
✅ Bring any Ubuntu VPS
✅ White-label reseller hosting
**Best for:** Developers, agencies, and WordPress professionals who want maximum control and significant cost savings. Ideal for users comfortable selecting their own cloud provider or those migrating multiple sites from Cloudways.
👉 See our full [xCloud vs Cloudways](/xcloud-vs-cloudways/) head-to-head comparison →
## **🥉 3. WP Engine – Best for Enterprise & Agency Support**
WP Engine positions itself as an enterprise-grade managed WordPress hosting solution, catering to larger organizations, agencies, and high-traffic websites. The platform includes proprietary performance optimizations and a strong agency ecosystem.
According to **Hosting Seekers,** WP Engine remains one of the largest managed WordPress hosting providers globally, with a strong emphasis on scalability and compliance.
### **Key Features**
- **EverCache Technology:** Proprietary caching system
- **Genesis Framework:** Premium theme framework included
- **Multiple Environments:** Development, staging, and production workflows
- **24/7 Expert Support:** WordPress specialists available around the clock
- **Global CDN:** Built-in content delivery network
- **Page Performance Monitoring:** Real-time analytics
### **How to Migrate**
WP Engine provides an automated migration plugin along with white-glove migration services for larger or more complex deployments.
### **Pros and Cons**
**Pros**
**Cons**
✅ Enterprise-grade security and compliance
❌ Premium pricing
✅ Genesis Framework + StudioPress themes
❌ No root access
✅ Excellent agency program
❌ Can be overkill for small sites
✅ Strong developer tools
❌ Complex for beginners
**Best for:** Enterprises, agencies managing multiple client websites, and organizations that require compliance certifications and enterprise-level SLAs.
## **4\. SiteGround – Best Budget Option with Google Cloud**
SiteGround has transitioned from traditional shared hosting to a Google Cloud-powered infrastructure, offering managed WordPress features at competitive introductory prices. According to W3Techs, SiteGround hosts approximately 2.1% of all websites worldwide.
This platform is especially appealing to users moving up from shared hosting who want better performance without dealing with server-level complexity.
### **Key Features**
- **Google Cloud Infrastructure:** All plans run on GCP
- **Site Tools Dashboard:** Modern, user-friendly custom control panel
- **Free CDN:** Cloudflare integration included
- **Staging Environment:** Available on GrowBig and higher plans
- **Daily Backups:** Automatic with easy restore options
- **SuperCacher:** Built-in caching technology
### **How to Implement**
SiteGround provides free migration for one website. Additional migrations cost $30 per site.
### **Pros and Cons**
**Pros**
**Cons**
✅ Google Cloud infrastructure
❌ Renewal prices are significantly higher
✅ Beginner-friendly interface
❌ Limited server control
✅ Excellent 24/7 support
❌ Resource limits on lower plans
✅ Competitive introductory pricing
❌ No root access
**Best for:** Beginners, small businesses, and users looking for a simple WordPress hosting solution with Google Cloud performance at an affordable entry price.
## **5\. RunCloud — Best Panel Alternative for Developers**
[**RunCloud**](/xcloud-vs-runcloud/) functions as a server management control panel, similar to xCloud, allowing users to connect their own VPS and manage WordPress sites through a centralized dashboard. Industry comparisons often highlight RunCloud as a mature platform with extensive documentation.
The platform is geared toward developers who want flexibility and control without being locked into a single hosting provider.
### **Key Features**
- **NGINX + Apache Hybrid:** Flexible web server setup
- **Git Deployment:** Push-to-deploy workflows
- **One-Click SSL:** Let’s Encrypt integration
- **File Manager:** Web-based file access
- **Database Management:** Built-in alternative to phpMyAdmin
- **Atomic Deployment:** Zero-downtime deployments
### **How to Implement**
You can connect any VPS from providers like DigitalOcean, Vultr, Linode, AWS, or others using RunCloud’s installation script.
### **Pros and Cons**
**Pros**
**Cons**
✅ Mature and well-established platform
❌ No free tier for unlimited sites
✅ Excellent documentation
❌ Less WordPress-focused than xCloud
✅ Git integration
❌ No OpenLiteSpeed support
✅ Developer-friendly features
❌ Interface feels less modern
**Best for:** Developers who are comfortable managing servers and want a stable, panel-based solution with strong documentation and community support.
## **6\. GridPane – Best for Hosting Agencies & Resellers**
[**GridPane**](/xcloud-gridpane/) is designed for hosting agencies and professional WordPress developers who require advanced server management combined with client-facing and reseller-focused features. The platform places a strong emphasis on security, performance optimization, and streamlined agency workflows.
According to industry reviews, GridPane offers one of the most comprehensive feature sets available for agencies managing large WordPress portfolios.
### **Key Features**
- **Server Security:** Advanced hardening, monitoring, and proactive protection
- **Nginx + Redis:** Performance-optimized hosting stack
- **Client Billing:** Built-in billing and reseller tools
- **Multitenancy:** Manage multiple clients on the same server
- **Backup Integration:** Support for multiple backup destinations
- **Staging:** One-click staging environments
### **How to Implement**
Connect your VPS through the GridPane dashboard and deploy servers using the platform’s one-click configuration process.
### **Pros and Cons**
**Pros**
**Cons**
✅ Best-in-class agency-focused features
❌ Higher starting price ($50/mo)
✅ Advanced security tooling
❌ Steeper learning curve
✅ Ideal for managing large portfolios
❌ Overkill for simple or small sites
✅ Strong community and support resources
**Best for:** Established agencies managing 20 or more client websites that need advanced security, integrated billing, and professional-grade workflows.
## **7\. ServerAvatar – Best Budget Hosting Control Panel Alternative**
[**ServerAvatar**](/xcloud-vs-serveravatar/) offers functionality similar to xCloud and RunCloud at a more affordable price point, with a focus on simplicity and cost efficiency. The platform supports multiple technology stacks, including LAMP, LEMP, OpenLiteSpeed, and MERN.
Based on the platform’s own comparisons, ServerAvatar positions itself as a budget-friendly Cloudways alternative with lower management overhead and reduced markups.
### **Key Features**
- **Multiple Tech Stacks:** Apache, NGINX, OpenLiteSpeed, and Node.js
- **White-Label Panels:** Client-facing dashboards for resellers
- **Free Plan:** Limited free tier available
- **Multiple Cloud Providers:** DigitalOcean, Vultr, Linode, Hetzner, and more
- **Auto-Installers:** 12+ one-click application installers
- **Request Monitoring:** Advanced logging and performance insights
### **How to Implement**
Servers can be connected using API integration or installed manually via the provided installation script.
### **Pros and Cons**
**Pros**
**Cons**
✅ Very affordable pricing
❌ Fewer WordPress-specific optimizations
✅ Support for multiple tech stacks
❌ Interface is less polished
✅ Solid documentation
❌ Smaller user community
✅ Node.js support
**Best for:** Budget-conscious developers who need support for multiple tech stacks and are willing to trade a refined interface for significant cost savings.
## **Cost Comparison: Cloudways vs Competitors**
Understanding the true cost difference between Cloudways and its leading alternatives requires comparing equivalent server specifications. Many [**Cloudways alternatives**](https://hostinginfo.online/best-cloudways-alternatives/) eliminate provider markups entirely, resulting in substantial long-term savings. This cost breakdown highlights how other modern hosting alternatives outperform Cloudways on price.
### **2GB RAM Server Comparison (Monthly)**
**Provider**
**DigitalOcean 2GB**
**Vultr HF 2GB**
**Your Provider Cost**
**Cloudways**
$28/mo
$60/mo
N/A
[**xCloud**](/)
$12/mo (managed)
$24 + $5 panel
Pay retail + $5/mo
**Kinsta**
N/A
N/A
$35/mo (visitor limits)
**RunCloud**
$12 + $8 panel
$24 + $8 panel
Pay retail + $8/mo
**GridPane**
$12 + $50 panel
$24 + $50 panel
Pay retail + $50/mo
**SiteGround**
N/A
N/A
$14.99/mo (GrowBig)
### **Free Tier Comparison**
**Provider**
**Free Option**
xCloud
✅ 1 server + 10 sites
RunCloud
❌ No free tier
GridPane
❌ No free tier
ServerAvatar
⚠️ Limited free tier
Cloudways
❌ 3-day trial only
## **Feature Comparison Between Cloudways Competitors**
**Features**
xCloud
Kinsta
WP Engine
SiteGround
RunCloud
Root Access
✅
❌
❌
❌
✅
OpenLiteSpeed
✅
❌
❌
❌
❌
Self managed Provider
✅
❌
❌
❌
✅
Free SSL
✅
✅
✅
✅
✅
Staging
✅
✅
✅
✅
✅
Redis Cache
✅
✅
✅
✅
✅
Free Migration
✅
✅
✅
⚠️ (1 site)
❌
White Label
✅
❌
❌
❌
❌
Unlimited Sites
✅
❌
❌
❌
❌
Free Tier
✅
❌
❌
❌
❌
## **Moving to Modern Cloudways Alternatives: How to Migrate From Cloudways**
This migration guide focuses on transitioning safely and efficiently to the best alternative of Cloudways available today. Most alternatives of Cloudways now offer automated tools that minimize downtime and complexity.
### **Pre-Migration Checklist**
1. **Audit Current Sites:** Document all domains, databases, and configurations
2. **Export Backups:** Download full backups from Cloudways
3. **Document DNS Settings:** Record all DNS records before migration
4. **Plan Timing:** Schedule migration during low-traffic periods
### **Step 1: Connect Cloud Provider**
Sign up at xCloud (free tier available). Add your [](https://xcloud.host/vultr-hosting/)Vultr, DigitalOcean, or other provider API key, or use[**xCloud Managed Hosting**](/managed-hosting/) for fully managed servers
### **Step 4: Migrate Sites**
Enter the source server’s IP address. Set the SSH port and use root as the SSH username. Choose an authentication method ‘Password authentication’, or ‘Public key authentication’.
### **Step 5: Verify and Go Live**
Select the server or specific sites you want to migrate. Click Next to proceed. Choose Go Live or Create Demo Site. Start the full server migration.
👉 Watch the step by step tutorial video:
You can follow the official [documentation](/docs/perform-a-full-server-migration-with-xcloud/) to migrate your entire server with all WordPress sites, or refer to the [dedicated guide](/docs/migrate-a-website-with-migrate-guru-plugin/) if you only want to migrate a single WordPress site seamlessly.
## **Common Mistakes When Switching from Cloudways**
### 1\. Underestimating Server Requirements
Avoid downgrading server specs just to save money. Always **match or exceed** your current Cloudways configuration, especially **RAM allocation**, which directly impacts PHP workers and site performance.
### 2\. Ignoring DNS TTL Settings
Before migrating, reduce your DNS TTL to **300 seconds (5 minutes)**. This significantly speeds up DNS propagation when switching servers and helps minimize downtime.
### 3\. Forgetting Email Configuration
Cloudways relies on a **Rackspace email add-on**, which many users overlook during migration. Plan email hosting separately using services like **Google Workspace**, **Microsoft 365**, or xCloud’s [**managed email**](/mailbox/) option.
### 4\. Skipping Staging Tests
Never migrate directly to production. Always test your site on a **staging environment** first. Most of them offer one-click staging, making this step fast and low-risk.
### 5\. Not Backing Up Before Migration
Even if you’re using an automated migration tool, create **manual backups**. Keep your Cloudways account active for **at least 7 days** after migration as a safety net.
## **Frequently Asked Questions**
### Which Cloudways alternative offers the best value for money?
xCloud consistently delivers strong value, with up to 40% cost savings compared to Cloudways at equivalent server specs (as cited by Online Media Masters). Its free tier (1 server, 10 sites) makes it ideal for testing before committing.
### Can I get root access with Cloudways alternatives?
Yes. xCloud, RunCloud, GridPane, and ServerAvatar all provide full root SSH access. Premium managed hosts like Kinsta and WP Engine do not.
### Which Cloudways Competitor is best for WooCommerce stores?
For WooCommerce, xCloud offers excellent value with OpenLiteSpeed support and full Redis object caching.
For fully managed solutions, Kinsta and WP Engine provide advanced WooCommerce-specific optimizations.
### How long does migration from Cloudways take?
Most migrations complete within 10 – 60 minutes, depending on site size. xCloud’s migration system automates the process with minimal downtime.
### Do I need technical knowledge to use xCloud?
xCloud provides more control than Cloudways but remains user-friendly. Its documentation and tutorials cover common workflows, and the managed hosting option requires little technical experience.
### Which alternative has the best support?
Kinsta and WP Engine are widely recognized for top-tier managed hosting support. Among control-panel solutions, xCloud maintains a 5-star rating on Trustpilot, with strong feedback on responsiveness.
### Can I host unlimited websites?
xCloud allows unlimited websites per server. Most managed hosts—such as Kinsta, WP Engine, and SiteGround – limit site counts based on plan tiers.
### What’s the most underrated Cloudways alternative?
xCloud is often considered underrated due to its relatively recent launch in 2022. Despite this, it now supports 10,000+ servers and 100,000+ websites, with rapid feature development and competitive pricing.
### Where can I get help choosing the right alternative?
Start with xCloud’s free plan to test the platform risk-free. For deeper insights, review a detailed xCloud vs Cloudways comparison or contact xCloud support for personalized recommendations.
## **Wrapping Up: Which Cloudways Alternative Should You Choose in 2026?**
The [**managed cloud hosting**](/what-is-cloud-hosting-and-how-does-it-work/) landscape has changed significantly since DigitalOcean acquired Cloudways. With the web hosting market projected to reach $527 billion by 2032 _(according to Fortune Business Insights)_, selecting the right platform has a direct impact on performance, scalability, and long-term costs.
### **Expert Picks by Goal**
**Your Goal**
**Best Choice**
**Expected Savings**
**Best Overall Value**
xCloud
~40% vs Cloudways
**Best Free Tier**
xCloud
1 server + 10 sites free
**Best Premium Support**
Kinsta
Premium pricing
**Best for Enterprise**
WP Engine
Enterprise pricing
**Best for Beginners**
SiteGround
Budget-friendly
**Best for Agencies**
xCloud or GridPane
Varies
### **Recommended Action Plan**
1. **This Week:** Sign up for [xCloud’s free tier](/) and migrate one test site
2. **Week 2:** Compare performance metrics between Cloudways and xCloud
3. **Week 3:** If results meet expectations, migrate remaining sites using [xCloud’s migration tool](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
4. **Week 4:** Cancel your Cloudways subscription after confirming all sites are running correctly
The growing consensus among [**WordPress hosting**](/hosting-for-wordpress/) professionals favors lightweight control panel solutions like xCloud for their balance of cost efficiency, performance, and flexibility. With features such as OpenLiteSpeed, Docker support, full root access, and a free tier to manage 1 server and 10 sites for completely free, xCloud has established itself as a leading Cloudways alternative for users who want maximum value without sacrificing control or performance.
If you have found this blog helpful, feel free to [subscribe to our blogs](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [Facebook community](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Best CMS in 2026: How to Choose the Right Platform for Your Website - xCloud
> Choosing a best CMS in 2026? Compare WordPress, Shopify, Webflow, and headless options. Find the right platform for SEO, AI search, and long-term growth.
Choosing a CMS in 2026 is no longer just a technical decision; it directly affects your SEO, AI visibility, and long-term scalability. If you are planning to build a new website, launch an online store, or move your business to a better platform, you are about to make one of the most important technology decisions of the year.
The Content Management System (CMS) you choose will shape how your team publishes content, how your site performs in search engines, how AI tools like ChatGPT and Google AI Overviews discover your brand, and how easily your business can scale.
In this blog, we are going to walk you through how to select the best CMS for your business in 2026. We will cover the main CMS types, the criteria that actually matter, the leading platforms to consider, and how to match the right hosting setup to the CMS you pick. Without further ado, let us get started.
## TL;DR
Choosing a CMS in 2026 is a five-year decision that shapes your SEO, AI visibility, publishing speed, and scalability. Here is the short version:
- **Know the categories:** Traditional (WordPress, Drupal), Headless (Strapi, Sanity, Contentful), Hybrid, SaaS Builders (Wix, Squarespace, Webflow), and eCommerce-First (Shopify, WooCommerce).
- **Evaluate on seven criteria:** ease of use, customization, performance, security, SEO and AI readiness, integrations, and total five-year cost.
- **The quick recommendations:** WordPress for most businesses, Shopify or WooCommerce for eCommerce, and a headless CMS with Next.js or Laravel for multi-channel or custom apps.
- **Do not skip hosting:** A great CMS on poor hosting still feels slow and insecure. Managed cloud hosting like xCloud handles performance, security, backups, and migration so your team can focus on content.
- **Follow a process:** Define goals, gather stakeholder input, audit your stack, shortlist three to five platforms, test the editor experience, and calculate the true five-year cost before committing.
Pick the first time carefully. Switching CMSs later is painful, expensive, and slows your business down.
## **What Is a Content Management System (CMS)?**
A CMS is a software platform that lets you create, manage, publish, and update digital content without writing code from scratch. It is the system that connects your team to your website, your mobile app, and increasingly, the AI assistants that summarize your content for users around the world.
In 2026, a CMS is no longer just a website tool. It is a strategic platform that supports how your business communicates, markets, and sells across web, mobile, voice, and AI search channels. The platform you pick today shapes how fast your team can publish, how well your site ranks on Google, and whether AI tools like ChatGPT, Perplexity, and Google AI Overviews can find and cite your content.
That makes CMS selection a five-year decision with compounding consequences. The right CMS empowers your team and grows with you. The wrong one quietly drains time, money, and momentum every single month.
## **Why CMS Selection Matters More in 2026**
The CMS landscape has changed at the edges, not the center. WordPress still powers around 43% of all websites and holds over 60% of the CMS market, according to [**W3Techs data**](https://sqmagazine.co.uk/cms-market-share-statistics/) referenced by SQ Magazine. But the way teams use a CMS has shifted significantly over the past two years. Let us look at the key shifts:
### **AI-First Discovery Is Changing the Game**
Search is split between traditional Google results and AI-generated answers from ChatGPT, Gemini, Perplexity, and Google AI Overviews. According to [**Discovered Labs’ SEO research**](https://discoveredlabs.com/blog/best-cms-for-seo-in-2026-wordpress-vs-webflow-vs-headless), AI systems cite content that is structured, authoritative, and easy to interpret programmatically. Your CMS needs to support schema markup and clean structured data without forcing your team into a code editor every time they publish.
### **Headless CMS Adoption Is Surging**
The headless CMS market is growing at over 20% CAGR, expanding from roughly $3.94 billion in 2026 to a projected $22.28 billion by 2034, according to a recent survey. Brands now need to deliver content to websites, mobile apps, smart devices, and AI agents from a single source.
### **Performance Is Non-Negotiable**
Google’s Core Web Vitals and AI ranking signals both reward fast, well-built sites. Your CMS choice directly affects your page speed, Time to First Byte, and Largest Contentful Paint scores. A slow CMS on poor hosting is a competitive disadvantage that compounds every month.
### **Cloud Hosting Is the Default**
Cloud-based CMS deployments now represent over 60% of new implementations. Self-hosting on outdated shared servers is a liability for both performance and security in 2026.
## **The Main Types of CMS in 2026**
Before you compare specific platforms, you need to understand the main CMS categories. Each one solves a different problem, and picking the wrong category is the most common reason CMS projects fail. Let us explore the main types below.
### **Traditional (Coupled) CMS**
A traditional CMS combines the content backend and the frontend into one system. WordPress, Drupal, and Joomla are the most common examples. The CMS controls both how content is created and how it is displayed to visitors. This makes setup straightforward and gives editors a live preview of what they are publishing.
This is the best fit for most small to mid-sized businesses, blogs, marketing sites, and any team that wants visual editing with a large plugin ecosystem.
### **Headless CMS**
A headless CMS separates the content backend from the frontend. Content is stored in a structured format and delivered through APIs to any frontend, whether that is a website built with Next.js, a mobile app, a voice assistant, or an AI agent. Popular options include Strapi, Sanity, Contentful, and Payload CMS.
A headless CMS is ideal for businesses with multi-channel content strategies, SaaS companies, mobile-first products, and teams with strong frontend development resources. The trade-off is a steeper learning curve and higher setup costs.
### **Hybrid CMS**
A hybrid CMS offers both visual editing for non-technical users and API-based content delivery for developers. It blends the simplicity of traditional CMS with the flexibility of headless. Modern WordPress with the REST API and block editor, Drupal, and platforms like Storyblok fit into this category.
This works well for growing businesses that need editor-friendly tools today but want headless flexibility tomorrow.
### **SaaS Website Builders**
SaaS website builders like Wix, Squarespace, and Webflow handle hosting, security, updates, and infrastructure automatically. You pay a monthly fee and build your site through a visual editor. No code, no servers to manage.
This category is great for solo founders, small businesses, designers, and anyone who needs a working site in a few hours without technical setup. The trade-offs are limited customization, vendor lock-in, and monthly costs that compound over time.
### **eCommerce-First CMS**
Shopify, BigCommerce, and WooCommerce on WordPress are built specifically for online stores. They include product catalogs, payment processing, inventory management, and shipping integrations out of the box.
These platforms are the right choice for direct-to-consumer brands, online retailers, and any business where checkout is the primary user action.
## **How to Select the Right CMS: 7 Key Criteria to Evaluate**
Once you understand the categories, the next step is matching your business needs against the available platforms. Use these seven criteria to evaluate any CMS shortlist.
- **Ease of Use for Your Team:** The most powerful CMS is useless if your team dreads logging in. Look for visual editors, real-time previews, and intuitive content workflows that non-technical users can handle without developer help.
- **Customization & Flexibility:** Your CMS should adapt to your needs without rewriting the codebase. Look for a strong plugin ecosystem, a REST or GraphQL API, custom content types, and flexible templates.
- **Performance & Scalability:** Your CMS affects your page speed, traffic handling, and Core Web Vitals scores. Look for built-in caching, CDN integration, and horizontal scalability for traffic spikes.
- **Security & Compliance**: A CMS that gets hacked is worse than no CMS at all. Look for active security patching, two-factor authentication, role-based access controls, and compliance with regulations like GDPR or HIPAA if needed.
- **SEO & AI Citation Readiness:** Your CMS must support schema markup, customizable meta titles, clean URL structures, XML sitemaps, and structured content that AI systems can parse for citation.
- **Integration Capabilities:** Your CMS does not work alone. It needs to connect cleanly with your CRM, email marketing tool, analytics, payment processor, and any custom internal systems.
- **Total Cost of Ownership (TCO):** The sticker price is rarely the real price. Calculate the full five-year cost including hosting, plugins, developer time, security services, training, and migration costs.
According to [**ButterCMS’s selection guide**](https://buttercms.com/blog/how-to-choose-a-cms/), ease of use and integration capabilities tend to be the make-or-break factors for most teams. Test the editing experience yourself before committing to anything.
## **Best CMS Platforms to Consider in 2026**
Now that you know the criteria, let us look at the leading CMS options most businesses should evaluate in 2026. Here is a quick comparison of the most popular platforms by category, use case, and where each one tends to fall short.
**CMS**
**Type**
**Best For**
**Starting Cost**
**Key Limitation**
WordPress
Traditional/Hybrid
Most websites, blogs, content sites
Free (hosting from $5/mo)
Plugin sprawl and security risks if not properly maintained
Shopify
eCommerce SaaS
Online stores, DTC brands
$29/mo
Transaction fees and limited customization outside its ecosystem
Webflow
SaaS Builder
Design-led marketing sites
$14/mo
Steep learning curve and pricing scales quickly with traffic
Wix / Squarespace
SaaS Builder
Small business sites
$14-$23/mo
Vendor lock-in and limited flexibility as you grow
Drupal
Traditional/Enterprise
Government, large publishers
Free (hosting required)
Requires experienced developers; not beginner-friendly
Strapi
Headless (Open Source)
Custom apps, multi-channel
Free (hosting required)
Requires a separate frontend build and ongoing DevOps
Sanity
Headless (SaaS)
Developer-first teams
Free tier + paid
API usage costs can spike at scale
Contentful
Headless (Enterprise)
Large omnichannel brands
$300+/mo
Expensive for small teams; complex permissioning
Laravel + Custom CMS
Custom (PHP Framework)
Bespoke applications
Free (hosting required)
High build cost and full responsibility for maintenance
Node.js + Headless
Custom (JavaScript)
API-first applications
Free (hosting required)
Requires strong in-house engineering for long-term support
For most small to mid-sized businesses in 2026, WordPress is still the safest, most flexible, and most affordable starting point. For eCommerce, Shopify or WooCommerce on WordPress are the leading choices. For multi-channel publishing or custom apps, a headless CMS paired with a modern framework like Next.js or Laravel is the modern path forward.
## **Why Hosting Matters as Much as the CMS Itself**
You might focus all your energy on picking the right CMS and forget about the foundation it runs on. That is a mistake. Your CMS is only as good as the infrastructure running it. A perfectly chosen platform on poor hosting will still feel slow, get hacked, and frustrate your team. A solid CMS on great hosting becomes a competitive advantage that compounds every month.
Your CMS decision is only half the equation. The other half is infrastructure. This is where xCloud comes in. [**xCloud**](/) is a next-generation managed cloud hosting platform built to run modern CMS deployments without the usual operational headaches. Whether you choose WordPress, Laravel, a headless setup, or a custom application, xCloud adapts to your stack.
### **Why xCloud Is The Perfect Choice For Your CMS**
You might be hesitant about managed hosting due to concerns about cost or flexibility. However, once you understand what xCloud brings to the table, hosting your CMS on xCloud can be highly beneficial for your business. Let us explore these benefits below.
- [**Managed WordPress Hosting**](/hosting-for-wordpress/)**:** Fully optimized WordPress hosting with automated updates, daily backups, free SSL, and one-click staging environments. Built-in caching and Cloudflare integration deliver top-tier Core Web Vitals scores.
- [**Laravel Hosting**](/laravel-hosting/)**:** Production-ready Laravel hosting with staging environments, SSL, Git deployments, and tooling built for PHP frameworks. Perfect for custom CMS builds and headless backends.
- [**Node.js Hosting**](/node-js-hosting/)**:** Managed Node.js infrastructure for headless frontends and API-first applications built on frameworks like Next.js, Express, or NestJS.
- [**WooCommerce Hosting**](https://xcloud.host/hosting-for-woocommerce/)**:** Performance-tuned hosting for high-traffic eCommerce stores, capable of handling millions of checkouts per minute.
- **[Bring Your Own Cloud](/self-managed-hosting/):** Connect your existing AWS, DigitalOcean, Google Cloud, Vultr, Linode, or Hostinger VPS to xCloud, or use xCloud’s own managed servers.
- **One Dashboard for Everything:** Manage your CMS, server, SSL, backups, DNS, and email from a single platform without switching between vendor tools.
- **Free Migration Tool:** Move your existing CMS site from any host to xCloud with zero downtime using the built-in migration tool.
- **[Free Mailbox Add-On](/mailbox/):** Get a free professional email account at your custom domain on every xCloud managed server.
## **How to Select the Right CMS: A Step-by-Step Process**
In this section, we are going to show you a practical six-step process for choosing your CMS without getting lost in vendor pitches. To get started, you will need to gather your team and document a few things. Afterward, follow these steps below.
### **Step 1: Define Your Business Goals**
The first step is to understand what your website actually needs to do. Are you selling products, publishing articles, hosting a community, or running a SaaS application? Write down the primary jobs the CMS must support.
You should also identify your secondary goals. For example, you might want SEO optimization, multi-language support, or integration with your existing CRM. Documenting these goals helps you filter out platforms that do not fit your real needs.
### **Step 2: Gather Stakeholder Input**
Once you have your goals, you need to talk to the people who will actually use the CMS every day. Marketing, content, design, and engineering teams all have different needs. Gathering input early prevents costly switching costs later.
Compile a “must-have” and “nice-to-have” feature list based on this input. This list becomes your evaluation rubric for the rest of the process.
### **Step 3: Audit Your Tech Stack**
Now that you know what you need, you should document the tools your CMS must integrate with. List your CRM, marketing automation platform, payment processor, analytics tools, and any custom internal systems.
Any CMS you consider must connect to these tools natively, through plugins, or through APIs. Skip platforms that do not.
### **Step 4: Shortlist 3 to 5 Platforms**
Based on the CMS type and your requirements, narrow your options to three to five platforms. Avoid going broader than that. Comparing fifteen options in detail wastes time and rarely produces a clearer answer than comparing five.
### **Step 5: Test the Editor Experience**
Set up a free trial or demo for each shortlisted platform. Have your content team publish a sample page on each one. The editor experience is the single biggest determinant of whether your team will actually use the CMS or quietly avoid it.
### **Step 6: Calculate the Five-Year Total Cost**
Add up the five-year cost for each shortlisted CMS, including hosting, premium themes, plugins, developer time, and migration risk. The cheapest option to install is often the most expensive to maintain over time.
Once you have completed all these steps, the right CMS for your business is usually obvious. If two platforms still feel equally good, default to the one with the larger community and the easier hiring market.
## **Advanced Tips for Getting the Most From Your CMS**
Before ending this blog, we want to share some advanced tips with you to help you maximize the value of whatever CMS you choose. Let us have a quick look at them.
### **Implement Strong Security Measures**
You should isolate your sites at the server level, enable two-factor authentication for every user, and use a Web Application Firewall (WAF) to protect against common web threats. Keep all themes, plugins, and core files updated with the latest security patches. Cloud hosting platforms like xCloud can be your trusted choice for built-in security and isolation.
### **Optimize Performance With Caching**
You should implement page caching, object caching, and database caching to keep your site fast under load. A built-in caching layer at the hosting level (like xCloud’s NGINX and Object Cache Pro setup) usually outperforms plugin-based caching solutions.
### **Plan Your Backup Strategy**
You should schedule automated daily backups for your CMS database and files, and store backups in remote locations using S3-compatible storage providers. Also, do not forget to regularly test your restore process to ensure quick data recovery if anything goes wrong.
### **Prepare for AI-Driven Content Discovery**
Make sure your CMS supports JSON-LD schema markup natively or through plugins. Structured data is how AI systems like ChatGPT and Google AI Overviews understand and cite your content.
## **Frequently Asked Questions**:
### **What is the best CMS for a small business in 2026?**
For most small businesses, WordPress on managed hosting like xCloud is the best balance of flexibility, ecosystem, cost, and ease of use. For pure eCommerce, Shopify is often simpler. For design-first marketing sites, Webflow is worth a look.
### **Is WordPress still the best CMS in 2026?**
WordPress still powers around 43% of all websites and holds over 60% of the CMS market. It remains the most flexible, well-supported, and affordable CMS for most use cases.
### **Should I use a headless CMS?**
Use a headless CMS if you need to deliver content across multiple channels (web, mobile apps, AI agents) or already have a strong frontend team. For a single website with a small team, it usually adds complexity without enough benefit. Three realities to weigh first:
- **Cost:** Free tiers are misleading. Once you add a separate frontend build, API fees at scale, dual hosting, and developer retainers, expect total costs two to five times higher than a comparable WordPress setup in year one.
- **Developer requirements:** Headless is not no-code. You will need at least one frontend developer fluent in frameworks like Next.js or Astro, and editors lose live preview unless your team builds it.
- **Maintenance:** You are running two systems instead of one. That means backend, frontend, API contracts, separate deployments, and cross-layer debugging. Features that come standard in WordPress become custom builds in headless.
If those trade-offs are worth the flexibility, headless is a strong long-term choice. If not, a hybrid setup like WordPress with the REST API gives you most of the benefits without the overhead.
### **How much should I budget for a CMS in 2026?**
For a typical small business, expect $20 to $100 per month for hosting plus $50 to $500 per year for premium themes and plugins. Headless and enterprise options range from $300 per month to thousands.
### **Can I switch CMSs later?**
Yes, but it is painful and expensive. Most CMSs support content export, but rebuilding templates, integrations, and SEO infrastructure takes significant time. Pick carefully the first time around.
### **Do I need separate hosting for my CMS?**
For self-hosted CMSs like WordPress, Drupal, or open-source headless platforms like Strapi, yes. Managed hosting like xCloud handles the infrastructure, security, and performance optimization so you can focus on content. SaaS platforms like Shopify and Wix include hosting in their monthly fee.
## **Enjoy a Seamless CMS Experience With xCloud**
Selecting the right CMS in 2026 is a strategic decision that shapes your marketing speed, search visibility, customer experience, and operational costs for years. The right platform empowers your team, scales with your business, and adapts to a digital landscape that now includes AI search, voice interfaces, and multi-channel delivery.
For most businesses, the right answer in 2026 is still WordPress on properly tuned managed hosting. For eCommerce, Shopify or WooCommerce are good options. For multi-channel publishing or custom applications, a headless CMS paired with a modern framework like Next.js or Laravel. Whichever path you take, evaluate ease of use, performance, scalability, security, SEO readiness, integrations, and total cost of ownership before committing.
We hope you have learned how to select the right content management system for your business in 2026 from this blog. Now, try [**xCloud’s managed hosting plans**](/managed-hosting/) by yourself and let us know your experience on the [**xCloud Facebook community**](https://www.facebook.com/groups/xcloud.community)**.** Also, do not forget to [**subscribe to our blog**](/blog/) to get updates, helpful resources, and more.
---
# 9 Best DeepSeek Harness Hosting Providers in 2026: Compared on Setup, Cost, Security & 24/7 Uptime (Complete Guide) - xCloud
> Choosing between DeepSeek Harness hosting providers? We compared 9 DeepSeek Harness hosting providers on setup time, real cost, security, and 24/7 uptime. Read now.
_Updated August 2026_
[**DeepSeek Harness**](https://github.com/deepseek-ai/deepseek-harness) passed 141,000 GitHub stars within four days of its August 13, 2026 release, [**per a direct GitHub API query**](https://pasqualepillitteri.it/en/news/11573/deepseek-harness-fastest-github-stars-record), after collecting its first 22,000 stars in 90 minutes. The catch nobody puts in the launch posts: the `dsh` Web UI binds to `127.0.0.1` and stops the moment your laptop sleeps. Scheduled loops, long-running sessions, and anything a teammate or webhook needs to reach all require a server that stays online, and where you run it ends up mattering as much as which model you point it at.
This guide ranks the nine best DeepSeek Harness hosting providers across managed, self-hosted VPS, and serverless setups, and shows what each one actually costs once your own time enters the math.
## Quick Summary / TL;DR
**Too long; didn’t read?** Here is the decision table:
If you want to…
Use this
Best for
Setup time
Skip infrastructure entirely (managed)
[**xCloud**](https://xcloud.host/deepseek-harness/)
Founders, agencies, non-developers
~5 minutes
Get the cheapest reliable VPS for production
**Hetzner Cloud**
Cost-conscious long-term operators
30–60 minutes
Follow the deepest tutorial library while self-hosting
**DigitalOcean**
Engineers who want documentation
30–60 minutes
Get a cheap VPS with guided tooling
**Hostinger VPS**
Solo developers comfortable in a CLI
20–40 minutes
Optimize for global latency
**Vultr**
Distributed teams, 30+ regions
30–60 minutes
Pay nothing while learning
**Oracle Cloud Free Tier**
Tinkerers with patience
45–90 minutes
Pay only when the agent runs (serverless)
**Railway**
Bursty workloads, idle most of the day
10–20 minutes
Pay hourly while testing setups
**LightNode**
People still picking models
5–10 minutes
Get the most RAM per dollar
**Contabo**
Heavy sandbox and multi-session use
30–60 minutes
**The category context:** DeepSeek Harness is a developer preview. [**AgentsPulse’s adoption review**](https://agentspulse.github.io/tutorials/deepseek-harness-and-cordis-why-everything-is-a-plugin/) recommends evaluating it in non-critical, isolated workflows before any production migration, which makes a rebuild-friendly hosting setup more important than usual.
**Best for zero-ops teams:** xCloud, one of the first fully managed DeepSeek Harness services anywhere, running the same managed playbook it proved with [**OpenClaw**](https://xcloud.host/openclaw-hosting/) and [**Hermes Agent**](https://xcloud.host/hermes-agent-hosting/).
**Best for budget self-hosters:** Hetzner Cloud, whose CX22 plan runs dsh with room to spare at under $5/month.
**Best free option:** Oracle Cloud’s always-free ARM tier, 24 GB of RAM for $0, if you can tolerate the sign-up friction.
## Why DeepSeek Harness Needs Hosting Built for Always-On Agents
A [**DeepSeek Harness**](https://xcloud.host/what-is-deepseek-harness/) instance on your laptop is a demo. The features that made it the fastest-growing repository of 2026 only pay off on a machine that never sleeps:
- **The append-only session log** supports resume, fork, and replay, but only accumulates value if sessions persist on durable disk across restarts.
- **Loops and scheduling are plugins**, which means long-running and recurring work is a configuration change rather than an external cron stack. Scheduled work needs a process that exists at the scheduled time.
- **The Web UI binds to localhost** (`127.0.0.1:3080`) by design. Reaching it from anywhere else requires a server with a stable public address, a reverse proxy, SSL, and authentication in front of it.
Here is what a DeepSeek Harness host has to do well:
Requirement
Why it matters
**24/7 uptime**
Scheduled loops only fire while the process runs
**Persistent disk**
Session logs and plugin state must survive restarts
**Node.js 20+ support**
dsh runs on Node; the host must not fight you on runtimes
**Reverse proxy + SSL**
The localhost-only UI needs secure exposure for remote access
**Authentication layer**
An exposed agent with shell tools is a breach waiting to happen
**At least 2 GB RAM**
1 GB works for light API use; sandboxed tool runs want 4 GB
**Outbound API egress**
Continuous calls to DeepSeek, Anthropic, OpenAI, or OpenRouter
**Process supervisor**
systemd or Docker restart policies to recover from crashes
**Backups**
Session history loss means losing your replay and fork trail
Security deserves the extra emphasis in this list. A harness ships with bash and file-editing tools. Exposing that on a public port without auth hands a shell to the internet. The localhost default protects local users; server operators inherit the job of wiring the protection themselves, and that wiring is where most first deployments stall.
## DeepSeek Harness Hosting: 3 Categories You Are Actually Choosing Between
The market splits into three buckets, and most lists conflate them.
Category
What you get
What you handle
Typical price
**Fully managed**
Server + dsh deployed + SSL + auth + backups + updates
Talking to the agent
$9.99/month flat
**Self-hosted VPS**
A Linux box with root access
Everything: install, proxy, SSL, auth, backups, security
$4–25/month
**Serverless / usage-based**
Pay-per-second container that idles when quiet
Build, deploy, observability
Usage-based
As of August 2026, xCloud is one of the first entrants in the fully managed category, days after the harness itself shipped. Hetzner, DigitalOcean, Hostinger, Vultr, Oracle, LightNode, and Contabo are self-hosted infrastructure. Railway is serverless. Each has its place.
## How We Ranked These Hosts
Six factors, weighted by how much they affect a dsh operator’s day-to-day life:
1. **Setup time and effort**: minutes to a working, remotely reachable agent, including proxy, SSL, and auth
2. **24/7 reliability**: uptime record, auto-restart, crash recovery
3. **Security posture**: how much of the exposure problem the host solves for you
4. **Session persistence**: disk durability, backup options, restore time
5. **Cost honesty**: list price vs renewal price vs your time cost
6. **Support quality**: response time and depth when something breaks
Pricing was confirmed against each provider’s public pricing page in August 2026. Runtime requirements come from the [**official DeepSeek Harness repository**](https://github.com/deepseek-ai/deepseek-harness) and early field reports such as [**Flowtivity’s hands-on installation review**](https://flowtivity.ai/blog/deepseek-harness-open-source-agent-explained/). Because the harness is days old, where dsh-specific benchmarks do not yet exist, comparable Node.js agent workloads (OpenClaw, Hermes Agent) are used as a proxy, and that proxy is reasonable: the resource profile of an API-driven Node agent is well established.
## Master Comparison Table
Rank
Provider
Category
Starting Price
Setup Time
Best For
🥇 1
[**xCloud**](https://xcloud.host/deepseek-harness/)
Fully managed
$9.99/mo
~5 min
Zero-ops dsh deployment
🥈 2
**Hetzner Cloud**
Self-hosted VPS
$4.59/mo
30–60 min
Cheapest production VPS
🥉 3
**DigitalOcean**
Self-hosted VPS
$6/mo
30–60 min
Developer documentation
4
**Hostinger VPS**
Self-hosted VPS
$6.49/mo (intro)
20–40 min
Cheap VPS with guided tooling
5
**Vultr**
Self-hosted VPS
$5/mo
30–60 min
Global latency, 30+ regions
6
**Oracle Cloud Free Tier**
Self-hosted VPS
$0
45–90 min
Free always-on learning box
7
**Railway**
Serverless
Pay-per-second
10–20 min
Bursty, idle-mostly use
8
**LightNode**
Self-hosted VPS
Hourly billing
5–10 min
Short-term testing
9
**Contabo**
Self-hosted VPS
~$5.50/mo
30–60 min
Most RAM per dollar
The table reflects sticker prices. Real cost of ownership, including the time tax of self-hosting, is broken down further below.
## 🥇 1. xCloud — Best Fully Managed DeepSeek Harness Hosting
[**xCloud**](https://xcloud.host/deepseek-harness/) is one of the first providers anywhere to ship DeepSeek Harness as a one-click managed service rather than a “here is a Linux box, good luck” VPS. The deployment includes the dsh runtime, a pre-wired reverse proxy with SSL and authentication in front of the localhost-bound Web UI, automatic security updates, and daily backups, wrapped in a $9.99/month flat rate.
That positioning matters because the gap between `npx @deepseek-ai/dsh web` on a laptop and a safely exposed server deployment is exactly the part the official quick start does not cover: reverse proxy, certificate renewal, an auth layer, a systemd unit, and a firewall that keeps port 3080 off the public internet. Each of those steps has its own failure mode. xCloud’s pitch is that you skip the entire sequence and get to the part that is actually interesting, which is building with plugins and putting the agent to work.
The track record is the differentiator. xCloud is built by the team behind [**WPDeveloper**](https://wpdeveloper.com/) and shipped what was, as of April 2026, the only fully managed Hermes Agent service on the market, alongside established managed [**OpenClaw hosting**](https://xcloud.host/openclaw-hosting/) and one-click deployments for n8n, Node.js, WordPress, WooCommerce, and Laravel. The platform runs across AWS, DigitalOcean, Vultr, Google Cloud, Hostinger, Linode, and bring-your-own-Ubuntu servers. DeepSeek Harness joins a proven catalog; only the application is new.
### Key Features
- **One-click deploy**: dsh + reverse proxy + SSL + auth provisioned in roughly five minutes from sign-up
- **Secure by default**: the localhost-only Web UI is exposed through an authenticated, SSL-terminated proxy, closing the most common self-hosting mistake
- **Model-agnostic setup**: paste an API key for DeepSeek, Anthropic, OpenAI, or any OpenAI-compatible endpoint during deployment
- **Session logs preserved across updates**: dsh’s append-only session history survives platform maintenance, with daily backups
- **24/7 expert support** from a team already operating OpenClaw and Hermes Agent fleets
- **14-day money-back guarantee**: long enough to validate the agent against a real workflow
### How to Deploy on xCloud
1. Sign up at [**app.xcloud.host/deepseek-harness**](https://app.xcloud.host/deepseek-harness)
2. Pick a server region close to you or your team
3. Paste your model provider API key
4. Open your dsh Web UI over SSL and start a session in Standard mode
### Pros and Cons
Pros
Cons
✅ One of the first fully managed dsh services on the market
❌ Higher sticker price than a raw $4.59 Hetzner box
✅ Solves the reverse proxy + SSL + auth exposure problem by default
❌ Less low-level customization than a raw root VPS
✅ Managed-agent track record with OpenClaw and Hermes Agent
❌ dsh is a developer preview; platform updates track upstream breaking changes
✅ Daily backups of session logs and plugin state
❌ Scaling up is a server upgrade, not a slider
**Best for:** Founders, agencies, and operators who want the agent running by lunch, not the weekend. Especially worth it for anyone whose hourly rate makes self-hosted setup time the most expensive line item in the whole stack.
## 🥈 2. Hetzner Cloud — Best Budget VPS for Long-Term Production
Hetzner Cloud’s CX22 plan starts at €4.51 (about $4.59) per month for 2 vCPUs, 4 GB RAM, and 40 GB SSD, specs that run DeepSeek Harness with sandboxed tool execution enabled and headroom left over. Hetzner has operated since 1997, owns its data centers in Falkenstein, Nuremberg, and Helsinki, and runs Ashburn and Hillsboro locations for North American latency.
The trade-off is hand-holding: there is none. No dsh template, no one-click button, and tutorials that assume comfort with a Linux terminal. What you get in exchange is the best price-to-performance ratio in this comparison and pricing that does not inflate at renewal.
### Key Features
- **CX22 at ~$4.59/mo** with 4 GB RAM, enough for heavy tool use
- **Hourly billing with monthly cap**: pay for partial months while testing
- **Free 20 GB snapshot storage** for session-log backups
- **Cloud Firewall included**: gate inbound to SSH and your proxy port only
- **API and Terraform provider**: dsh infrastructure as code
- **20 TB included traffic**: generous for continuous API egress
### How to Deploy on Hetzner Cloud
1. Create a project and provision a CX22 with Ubuntu 24.04
2. SSH in and install Node.js 20+ (`curl -fsSL https://deb.nodesource.com/setup_20.x | bash -` then `apt install nodejs`)
3. Install and start the harness: `npx @deepseek-ai/dsh web`
4. Create a systemd unit so dsh restarts on crash and boot
5. Put Caddy or nginx in front with a domain, SSL, and basic auth
6. Configure the Cloud Firewall to allow only 22, 80, and 443
Steps 4 through 6 are where most operators lose their first hour.
### Pros and Cons
Pros
Cons
✅ Cheapest production-grade VPS in this comparison
❌ Zero hand-holding; you debug everything yourself
✅ Stable pricing without renewal inflation
❌ No dsh-specific tooling or templates
✅ 4 GB RAM at a 1 GB price point elsewhere
❌ Support is ticket-based and terse at this tier
✅ Snapshot backups built in
❌ Setup time is the real cost: 30–60 minutes minimum
**Best for:** Engineers running dsh long-term who are comfortable in a terminal and want the lowest possible monthly bill.
## 🥉 3. DigitalOcean — Best for Developer-Friendly Self-Hosting
DigitalOcean droplets start at $6/month for 1 GB RAM, though most DeepSeek Harness operators want the 2 GB tier ($12/month) for sandboxed tool headroom. The pull is not price. It is the documentation: DigitalOcean’s tutorial library covers every step of the Node.js + reverse proxy + SSL recipe in depth, which matters when you are debugging certificate renewal at 11 PM. New accounts get $200 in credit, which covers months of testing.
### Key Features
- **$200 free credit** for new accounts
- **One-click Docker droplet**: run dsh in a container with a mounted volume
- **15+ regions** with private networking
- **Spaces object storage** at $5/month for off-droplet session backups
- **The strongest community tutorial library in hosting** for Node.js, nginx, Caddy, and systemd
- **$1/month automated droplet backups**
### How to Deploy on DigitalOcean
1. Create a Basic Droplet (2 GB / 1 vCPU) with Ubuntu 24.04 and an SSH key
2. Install Node.js 20+ and run `npx @deepseek-ai/dsh web` to verify
3. Add a systemd unit for supervision
4. Point a Cloudflare-proxied domain at the droplet, terminate SSL at Caddy or nginx with auth
5. Enable the $1/month backup option
### Pros and Cons
Pros
Cons
✅ Largest tutorial library and developer community
❌ More expensive than Hetzner for similar specs
✅ $200 sign-up credit funds a long evaluation
❌ No dsh-specific template yet
✅ Strong uptime track record
❌ Backups are a paid opt-in
✅ Easy upgrade path to managed databases and Kubernetes
❌ 2 GB tier costs what Hetzner charges for 4 GB
**Best for:** Engineers who learn by reading tutorials and want a host where every weird deployment question already has a canonical answer.
## 4\. Hostinger VPS — Best Cheap VPS With Guided Tooling
Hostinger’s KVM 2 plan (2 vCPU, 8 GB RAM) starts around $6.49/month on introductory terms and includes a browser terminal, a Docker manager, and an AI assistant (Kodee) that walks through server tasks. There is no DeepSeek Harness template in the Application Catalog yet, which is unsurprising for software this new, but the Docker manager plus generous RAM make it a comfortable middle ground between bare Hetzner and full management.
The catch worth knowing before checkout: Hostinger’s introductory rates renew substantially higher, a pattern documented across its VPS line, and the cheapest rates require long-term contracts. Budget on the renewal price, not the banner price.
### Key Features
- **8 GB RAM on the entry KVM 2 plan**: unusual at this price point
- **Docker manager** for containerized dsh with volume persistence
- **AI assistant (Kodee)** for guided troubleshooting
- **Weekly backups included** on KVM plans
- **NVMe storage** standard
- **24/7 chat support**
### How to Deploy on Hostinger VPS
1. Buy a KVM 2 plan with Ubuntu 24.04
2. Use the browser terminal or SSH to install Node.js 20+
3. Run dsh under Docker with a named volume for session persistence, or bare with systemd
4. Point a domain at the VPS and terminate SSL with Caddy plus basic auth
5. Confirm weekly backups are enabled in hPanel
### Pros and Cons
Pros
Cons
✅ 8 GB RAM at an entry-level price
❌ Renewal pricing well above intro rates
✅ Guided tooling lowers the CLI barrier
❌ Cheapest rates need 24-month terms
✅ Weekly backups included
❌ No dsh template yet
✅ Browser terminal for quick fixes anywhere
❌ You still own proxy, SSL, auth, and updates
**Best for:** Solo developers who want plenty of RAM, some guardrails, and are comfortable committing to a term to lock the price.
## 5\. Vultr — Best for Global Latency
Vultr runs 30+ data centers on six continents, which is the practical reason it appears here. If your team is in Singapore and your agent is in Frankfurt, every Web UI interaction and webhook round-trip carries the distance. Vultr lets you put dsh close to whoever uses it. Pricing starts at $5/month for 1 GB and scales linearly; the standard install recipe works unmodified.
### Key Features
- **30+ regions**: the widest coverage in this comparison
- **Hourly billing** for short-term tests
- **High-frequency CPU plans** for compute-heavy tool runs
- **Block storage and snapshots** for session backups
- **Reserved IPs** for stable webhook and proxy addresses
### How to Deploy on Vultr
1. Pick the region closest to your users
2. Provision a Cloud Compute instance with Ubuntu 24.04 and 2+ GB RAM
3. Install Node.js 20+, run dsh, add a systemd unit
4. Terminate SSL at Caddy or nginx with auth on a reserved IP or domain
### Pros and Cons
Pros
Cons
✅ Best regional coverage of any provider here
❌ No dsh-specific tooling
✅ Hourly billing for experiments
❌ Documentation thinner than DigitalOcean
✅ Reserved IPs for stable endpoints
❌ Performance per dollar trails Hetzner
✅ Consistent pricing across regions
❌ Support depth varies by plan tier
**Best for:** Distributed teams and operators who care about round-trip latency more than absolute price.
## 6\. Oracle Cloud Free Tier — Best Free Always-On Option
Oracle Cloud’s always-free tier includes Ampere A1 ARM compute: up to 4 OCPUs and 24 GB of RAM at no cost, indefinitely. DeepSeek Harness runs on Node.js, Node runs fine on ARM, and 24 GB of free RAM is more than any paid entry in this list provides. For a learning box or a personal agent, the price is unbeatable because there is no price.
The honesty section: Oracle’s sign-up is famously strict (card verification failures are common), free-tier capacity in popular regions sells out, idle instances can be reclaimed under the free tier’s fair-use terms, and the console is built for enterprises, not hobbyists. You pay in friction instead of dollars.
### Key Features
- **4 ARM OCPUs and 24 GB RAM, always free**
- **200 GB block storage** included in the free allotment
- **Full root Ubuntu server**: the standard recipe applies
- **10 TB monthly egress** free, ample for API traffic
- **Real production infrastructure**, not a trial that expires
### How to Deploy on Oracle Cloud Free Tier
1. Create an account (persist through verification) and launch an Ampere A1 instance with Ubuntu 24.04
2. Open only 22, 80, and 443 in both the Security List and the OS firewall (Oracle has two layers; missing one is the classic stall)
3. Install Node.js 20+ for ARM, run dsh, add systemd
4. Terminate SSL with Caddy plus auth on a free subdomain
5. Keep the instance minimally active to avoid idle reclamation
### Pros and Cons
Pros
Cons
✅ Genuinely free with more RAM than any paid entry here
❌ Sign-up friction and regional capacity shortages
✅ ARM performance is strong for Node workloads
❌ Idle instances can be reclaimed
✅ Real infrastructure with generous egress
❌ Enterprise console with a steep learning curve
✅ Room for dsh plus a local model runner if you want one
❌ Two-layer firewall confuses first-timers
**Best for:** Patient tinkerers who want an always-on personal agent for exactly $0 and treat the setup friction as part of the hobby.
## 7\. Railway — Best Serverless / Pay-Per-Second Hosting
Railway sells a platform, not servers: dsh runs in a container that scales to zero when idle and bills per second when active. For an agent that fires on schedules a few times a day, that can cost less than any always-on VPS that idles 95% of the time. The trade-off is cold starts, a few seconds of wake-up before the first response, which is fine for cron-driven loops and noticeable for interactive sessions.
### Key Features
- **Per-second billing** with scale to zero
- **Git-based deploys**: push to deploy, one-click rollback
- **Persistent volumes** for session-log durability
- **Built-in Postgres** if your storage plugin outgrows local files
- **Automatic HTTPS** on generated domains, which shortcuts the SSL step
### How to Deploy on Railway
1. Connect a GitHub repository with a dsh Dockerfile
2. Attach a Railway volume mounted at the dsh data directory
3. Set environment variables for your model API key
4. Add an auth layer (Railway’s HTTPS covers transport, not access control)
5. Push to main; Railway redeploys automatically
### Pros and Cons
Pros
Cons
✅ Costs approach zero when the agent is idle
❌ Cold-start delay on first request
✅ Automatic HTTPS removes one exposure step
❌ You must still add authentication yourself
✅ Git-driven deploys and rollback
❌ Usage pricing is harder to predict than flat VPS
✅ Volumes make session persistence straightforward
❌ Less suited to long interactive sessions
**Best for:** Scheduled research, monitoring, and summary workflows where a few seconds of cold start per invocation is invisible and scale-to-zero savings are real.
## 8\. LightNode — Best for Testing and Hourly Billing
LightNode’s hourly billing (from about $0.018/hour) and 40+ locations make it the evaluation tool of this list. Spin up an instance, test dsh with two different model providers for an afternoon, destroy it, and pay pocket change. Provisioning takes under two minutes, the fastest in this comparison. It is not the right answer for production: support, tooling, and documentation trail the incumbents. Evaluate here, then commit elsewhere.
### Key Features
- **Hourly billing** without commitment
- **Sub-2-minute provisioning**
- **40+ global locations** across Asia, Europe, and the Americas
- **Flexible payment options** including PayPal and crypto
### How to Deploy on LightNode
1. Top up the wallet with $5 and pick a location
2. Provision a 2 GB instance, SSH in within two minutes
3. Install Node.js 20+ and run `npx @deepseek-ai/dsh web` over an SSH tunnel (`ssh -L 3080:127.0.0.1:3080 user@server`), skipping proxy and SSL entirely for throwaway tests
4. Destroy the instance when done
### Pros and Cons
Pros
Cons
✅ Cheapest way to run real multi-region experiments
❌ Not built for long-term production
✅ Fastest provisioning tested
❌ Thin documentation and smaller support team
✅ SSH-tunnel testing needs no exposure setup at all
❌ Performance varies across regions
✅ No contracts
❌ Data is wiped with the instance
**Best for:** Developers in the evaluation phase who want to test dsh in five regions and only pay for the hours used.
## 9\. Contabo — Best RAM Per Dollar
Contabo’s Cloud VPS line starts around $5.50/month for 8 GB of RAM, roughly double what Hetzner gives at the price and quadruple DigitalOcean. For DeepSeek Harness workloads that run multiple concurrent sessions, heavy sandboxed tool execution, or a small local model through an OpenAI-compatible endpoint on the same box, the RAM headroom is the draw. The trade-offs are a setup fee on monthly terms, network performance that trails premium clouds, and support best described as economy class.
### Key Features
- **8 GB RAM from ~$5.50/month**: the best memory ratio in this list
- **Large NVMe or SSD storage allocations** at every tier
- **European and US regions**
- **Optional object storage** for offsite session backups
### How to Deploy on Contabo
1. Order a Cloud VPS with Ubuntu 24.04 (watch for the setup fee on monthly billing)
2. Install Node.js 20+, run dsh, add a systemd unit
3. Terminate SSL with Caddy plus auth
4. Schedule offsite backups of the dsh data directory; snapshots are not the default here
### Pros and Cons
Pros
Cons
✅ Unmatched RAM per dollar for heavy workloads
❌ Setup fee on monthly terms
✅ Room to co-host a local model endpoint
❌ Network and I/O trail premium providers
✅ Big storage allocations for long session archives
❌ Slower support response times
✅ Sensible EU data residency options
❌ No dsh tooling and sparse tutorials
**Best for:** Operators whose agents run many concurrent sessions or heavy sandboxed tools and who want maximum headroom on a minimum budget.
## Resource Requirements: What DeepSeek Harness Actually Needs
The [**official repository**](https://github.com/deepseek-ai/deepseek-harness) targets Node.js, and early operator reports place real-world needs in this range:
Workload
vCPU
RAM
Storage
Notes
Local trial, API models
1
1 GB
10 GB
Laptop-class is fine
Always-on server, light use
1
2 GB
20 GB
Node process + session logs
Sandboxed tools, active daily use
2
4 GB
40 GB
Code execution wants headroom
Multiple concurrent sessions
2–4
8 GB
60 GB
Contabo/Hetzner territory
Co-hosted local model (Ollama)
4+
16 GB+
80 GB+
The model, not dsh, sets the floor
No GPU is required unless you self-host a model on the same machine. The harness calls hosted LLM APIs by default, so the server handles agent logic, sessions, and tools, which is CPU-light work.
## Cost Breakdown: What You Will Actually Pay
Real cost has three components: hosting, LLM tokens, and your time. Token pricing shifted the week dsh launched: [**VentureBeat reports**](https://venturebeat.com/technology/deepseek-harness-launches-as-open-source-rival-to-claude-code-alongside-v4-pro-on-api-with-higher-prices) that DeepSeek moved from flat API pricing to peak and off-peak rates starting August 16, 2026, so token bills now depend on when your loops run as much as how much they run.
Setup
Hosting/mo
Tokens/mo (typical)
Your time/mo
Total monthly
**xCloud managed** + DeepSeek V4
$9.99
$5–20
~$0 (zero ops)
**$15–30**
**Hetzner CX22** + DeepSeek V4
$4.59
$5–20
1–3 hrs ($30–150 at $30–50/hr)
**$40–175**
**DigitalOcean 2 GB** + OpenRouter
$12
$10–25
1–2 hrs
**$52–90**
**Hostinger KVM 2 (intro)** + Claude
$6.49
$15–30
1–2 hrs
**$52–90**
**Vultr 2 GB** + DeepSeek V4
$12
$5–20
1–2 hrs
**$47–85**
**Oracle Free Tier** + DeepSeek V4
$0
$5–20
2–4 hrs (first month)
**$65–220 month 1, then $5–20**
**Railway** + DeepSeek V4
$0–10
$5–20
1–2 hrs
**$35–80**
**LightNode hourly** + any
$2–15
$5–15
30 min
**$22–55**
**Contabo 8 GB** + DeepSeek V4
$5.50
$5–20
1–2 hrs
**$40–80**
The “your time” column is what most comparisons skip. If your billable rate is $50/hour and self-hosting takes two hours of setup plus an hour a month of maintenance, that is $50+ per month on top of a $4.59 bill, and the cheapest VPS quietly becomes one of the most expensive options on the page.
## Setup Difficulty: How Hard Each Path Is in Practice
Provider
Setup time
Skills needed
Ongoing maintenance
**xCloud**
~5 min
None; just a credit card and an API key
Minimal; managed updates
**Hetzner Cloud**
30–60 min
Linux CLI, systemd, Caddy/nginx, firewall
Hours per month
**DigitalOcean**
30–60 min
Linux CLI, Docker or systemd
Hours per month
**Hostinger VPS**
20–40 min
Docker basics or CLI comfort
Moderate
**Vultr**
30–60 min
Linux CLI, systemd
Hours per month
**Oracle Free Tier**
45–90 min
All of the above plus Oracle’s console
Moderate
**Railway**
10–20 min
Git, Docker, env config
Low after initial setup
**LightNode**
5–10 min
Basic terminal, SSH tunneling
Minimal; testing only
**Contabo**
30–60 min
Linux CLI, systemd, backup scripting
Hours per month
## Common Mistakes Operators Make Choosing DeepSeek Harness Hosting
Five patterns already repeating in the first week of deployments:
- **Exposing port 3080 directly.** The Web UI has no built-in public auth story; it expects localhost. Operators who bind to `0.0.0.0` to “make it work” hand an agent with shell tools to the internet. Always front it with an authenticated proxy or an SSH tunnel.
- **Picking the cheapest VPS without budgeting time.** A $4.59 box that takes two hours to secure costs more than $9.99 of managed hosting the moment your hourly rate enters the equation.
- **Forgetting session persistence in Docker.** dsh’s replay and fork features depend on the session log. Running the container without a mounted volume wipes your history on every rebuild.
- **Skipping the process supervisor.** Without systemd or a Docker restart policy, the agent dies on its first crash and stays dead until you notice. The entire 24/7 premise depends on auto-restart.
- **Pinning production to a release candidate.** The repository’s own version string is 0.1.0-rc.5 and the README promises breaking changes. Keep deployments rebuild-friendly and test upgrades before adopting them.
## Audience Mapping: Which One Fits Your Situation
If you are…
Best choice
Why
A founder validating an agent workflow
**xCloud**
5-minute deploy answers “does this help?” this week
An agency running agents for clients
**xCloud**
Multi-server management, backups, and support in one panel
A solo developer comfortable in a terminal
**Hetzner Cloud**
Lowest bill; you will tolerate the setup
An engineer who learns from tutorials
**DigitalOcean**
Every step has a canonical guide
Working with a distributed global team
**Vultr**
Put the agent near its users
A student or hobbyist with $0 budget
**Oracle Free Tier**
24 GB RAM for free, friction included
Running scheduled, cron-style loops only
**Railway**
Scale-to-zero stops paying for idle hours
Still comparing models and regions
**LightNode**
Hourly billing wastes nothing
Running heavy concurrent sandboxed work
**Contabo**
Most RAM per dollar by a wide margin
## Video Resources
For a walkthrough of the architecture you are about to host, DevsKingdom’s 12-minute breakdown of the plugin model is the clearest primer: [**Deepseek Harness: Everything is a Plugin (YouTube)**](https://www.youtube.com/watch?v=xe-aHJLC5UU). For pointing dsh at local and alternative model providers on your own server, this hands-on install session covers the provider configuration end to end: [**DeepSeek Harness + Ollama or Any Other Provider Locally (YouTube)**](https://www.youtube.com/watch?v=iqWtDOeTveI).
## Frequently Asked Questions
### What is the best hosting for DeepSeek Harness in 2026?
For most users, [**xCloud’s managed DeepSeek Harness hosting**](https://xcloud.host/deepseek-harness/) is the practical answer because it removes the entire infrastructure layer, including the reverse proxy, SSL, and authentication the localhost-bound Web UI requires, for $9.99/month. For developers who prefer to self-host, Hetzner Cloud delivers the best price-to-performance, and Oracle’s free tier is the best $0 option.
### Can I run DeepSeek Harness on a cheap 1 GB VPS?
Yes, for light API-driven use. The harness itself is a Node.js process and runs in 1 GB. Enable heavy sandboxed tool execution or multiple concurrent sessions and you want 4 GB, which is why Hetzner’s CX22 (4 GB at $4.59) beats nominally cheaper 1 GB plans.
### Do I need a GPU for DeepSeek Harness hosting?
No. dsh calls hosted LLM APIs (DeepSeek, Anthropic, OpenAI, Bedrock, Vertex, Azure, or any OpenAI-compatible endpoint) by default, so the server only runs agent logic. A GPU becomes relevant only if you co-host a local model with Ollama or vLLM, which is a separate deployment decision.
### Is xCloud the only managed DeepSeek Harness host?
As of August 2026, xCloud is one of the first fully managed options anywhere, days after the harness itself launched. Infrastructure providers in this list give you the raw server; xCloud is the entry that also deploys, secures, supervises, and backs up the application. Expect more managed entrants as the ecosystem matures; expect few with an existing managed-agent fleet behind them.
### How much does it cost to run DeepSeek Harness for a year?
A budget setup on Hetzner with DeepSeek V4 tokens lands around $115–300/year before your time. Managed hosting on xCloud with moderate token use lands around $180–360/year all-in. Note that DeepSeek’s API moved to peak and off-peak pricing on August 16, 2026, so scheduling loops in off-peak windows now directly lowers the token line.
### Why can’t I reach the Web UI from my browser after installing on a VPS?
The Web UI binds to `127.0.0.1:3080`, localhost only, by design. Either open an SSH tunnel (`ssh -L 3080:127.0.0.1:3080 user@server`) or put an SSL-terminated, authenticated reverse proxy in front of it. Do not bind dsh to `0.0.0.0` on a public IP.
### My session history vanished after redeploying. What happened?
Almost always a Docker container without a mounted volume. The append-only session log lives in the dsh data directory; mount it as a named volume (or run on persistent VPS disk) and the resume, fork, and replay features keep working across restarts and rebuilds.
### The agent stops responding every few days until I restart it. What is the fix?
That is a missing process supervisor. Create a systemd unit with `Restart=always` (or Docker `restart: unless-stopped`) so crashes recover automatically. Every provider in this list supports one of the two; managed hosting configures it for you.
### Is it safe to host DeepSeek Harness publicly at all?
Yes, with the right layers: SSL, authentication in front of the UI, a firewall exposing only 22/80/443, and prompt updates while the project iterates through its developer preview. The session log helps here too, since every tool invocation is inspectable after the fact.
### Can DeepSeek Harness run alongside OpenClaw or Hermes Agent on one server?
Yes. They are separate processes with separate ports and data directories. Allocate at least 4 GB RAM for two agents with active tool use, supervise each independently, and back up each data directory on its own schedule. Comparisons between the three are covered in the [**Hermes Agent vs OpenClaw**](https://xcloud.host/hermes-agent-vs-openclaw/) guide.
### Should I wait for DeepSeek Harness to leave developer preview before hosting it?
Waiting is reasonable for production dependencies; the README promises breaking changes. Hosting it now is also reasonable for evaluation and plugin development, which is exactly what a $9.99 managed instance, an hourly LightNode box, or Oracle’s free tier are for. Keep whatever you deploy rebuild-friendly.
### Can I migrate between hosts later?
Yes, easily. Everything important lives in the dsh data directory: session logs, config, and plugin state. Archive it, copy it to the new server, restore, restart. Migration takes minutes and platform lock-in is essentially zero, which lowers the risk of starting anywhere on this list.
## Conclusion: Your 2026 DeepSeek Harness Hosting Roadmap
The DeepSeek Harness hosting decision comes down to a single trade: how much of your week do you want to spend on infrastructure for a project that is itself moving fast?
If the answer is “none,” xCloud’s managed service is the entry on this list built to deliver exactly that, on a playbook already proven with OpenClaw and Hermes Agent. If the answer is “I enjoy it and want the lowest bill,” Hetzner has earned its reputation, and Oracle’s free tier rewards patience with a $0 line item. Everyone else fits between those poles based on the trade-offs you are prepared to make.
### Expert Picks by Goal
Your goal
Best choice
Why
Best fully managed
[**xCloud**](https://xcloud.host/deepseek-harness/)
One of the first managed dsh services, secure exposure handled by default
Best budget VPS
**Hetzner Cloud**
4 GB RAM at $4.59 with honest pricing
Best for developers
**DigitalOcean**
The tutorial library answers everything
Best cheap guided VPS
**Hostinger VPS**
8 GB RAM plus tooling at entry price
Best global reach
**Vultr**
30+ regions on six continents
Best free option
**Oracle Free Tier**
24 GB RAM for $0, friction included
Best serverless
**Railway**
Scale-to-zero for scheduled loops
Best for testing
**LightNode**
Hourly billing, 2-minute provisioning
Best RAM per dollar
**Contabo**
8 GB from ~$5.50/month
**What to do this week:** Pick the row that matches your situation, deploy, and run DeepSeek Harness against one real workflow for two weeks. Either it earns its keep or it does not, and you find out fast. The [**14-day money-back guarantee on xCloud’s managed plan**](https://app.xcloud.host/deepseek-harness) is a free trial of the fastest path; LightNode’s hourly billing is a free trial of the cheapest. Between the two, you can answer the question for under $15.
The pattern from watching OpenClaw and Hermes Agent operators over the past year holds here: the people getting the most out of a new agent are rarely the ones who picked the absolute cheapest host. They are the ones who matched the host to the workload and stopped tinkering with infrastructure once the agent was running. Whichever direction you go, that is the move worth making.
If you found this guide useful, [**subscribe to the xCloud blog**](https://xcloud.host/blog/) for more deep-dive comparisons on hosting AI agents, automation tools, and the open-source stack behind them, or join the [**xCloud Facebook community**](https://www.facebook.com/groups/xcloud.community) to compare setups with other operators.
---
# 9 Best Hermes Agent Hosting Providers in 2026: Compared on Setup, Cost, Memory & 24/7 Uptime (Complete Guide) - xCloud
> Compare 9 best Hermes Agent hosting providers for 2026. Managed, VPS & serverless options ranked by setup time, cost, memory persistence & 24/7 uptime.
Hermes Agent crossed [**90,000 GitHub stars**](https://dev.to/wonderlab/one-open-source-project-a-day-no40-hermes-agent-nous-researchs-self-improving-ai-agent-4ale) within roughly six weeks of launch in February 2026, which makes it one of the fastest-growing open-source AI agents ever shipped. The catch nobody talks about: an agent that learns and remembers across sessions only earns its keep when it actually stays online, and that almost never happens on a laptop. Where you host it ends up mattering as much as which model you point it at.
This guide ranks the nine best Hermes Agent hosting providers across managed, self-hosted VPS, and serverless setups and shows what each one actually costs once you factor in your time.
## Quick Summary / TL;DR
**Too long; didn’t read?** Here is the decision table:
If you want to…
Use this
Best for
Setup time
Skip infrastructure entirely (managed)
**[xCloud](/hermes-agent-hosting/)**
Founders, agencies, non-developers
~5 minutes
Get the cheapest reliable VPS for production
**Hetzner Cloud**
Cost-conscious long-term operators
30–60 minutes
One-click Docker via an Application Catalog
**Hostinger VPS**
Solo developers comfortable in a CLI
15–30 minutes
Use a developer-first VPS with deep tutorials
**DigitalOcean**
Engineers who want documentation
30–60 minutes
Run a Hermes-specialist EU host with one-line install
**Virtua.Cloud**
EU-based privacy-focused users
10–20 minutes
Optimise for global messaging latency
**Vultr**
International messaging users
30–60 minutes
Pay hourly while testing setups
**LightNode**
People still picking models
5–10 minutes
Get always-on VPS with retail-grade support
**Bluehost VPS**
Beginners who want a phone number
30–45 minutes
Pay only when the agent runs (serverless)
**Railway**
Bursty workloads, idle most of the day
10–20 minutes
**Expert consensus:** [**The New Stack’s analysis of persistent AI agents**](https://thenewstack.io/persistent-ai-agents-compared/) argues the hard part of running one isn’t the model — it’s keeping the runtime alive 24/7 without babysitting it. That framing is what separates this list into two camps: managed (xCloud) and self-hosted on a VPS (everyone else).
**Best for solo operators:** Hostinger VPS — the Application Catalog has a [**pre-built**](https://www.hostinger.com/vps/docker/hermes-agent) **[Hermes Agent Docker template](https://www.hostinger.com/vps/docker/hermes-agent).**
**Best for production teams:** xCloud — the only fully managed Hermes Agent service with pre-configured messaging gateways, daily backups, and SSL handled for you.
**Best for budget hawks:** Hetzner — [**Remote OpenClaw’s cost analysis**](https://www.remoteopenclaw.com/blog/hermes-agent-cost-breakdown) found Hetzner has the best price-to-performance ratio of any provider tested.
## **Why Hermes Agent Needs Hosting Built for Persistent AI Agents**
A [**Hermes Agent**](/what-is-hermes-agent-features-and-use-cases/) that runs only on your laptop is not really a learning agent. The whole pitch from Nous Research is the **[three-layer memory architecture](https://hermes-agent.nousresearch.com/docs/)** – active memory in MEMORY.md, session history in SQLite with FTS5 search, and procedural memory as portable skills. That memory only compounds when the agent runs continuously and gets exposed to real workflows. Close your laptop and you’ve paused the part that makes Hermes useful.
There’s a second reason hosting matters: messaging gateway uptime. Hermes can connect to Telegram, Discord, Slack, WhatsApp, Signal, Email, and roughly 10 other channels through one gateway process. That gateway has to be reachable from the internet for inbound webhooks to work. A residential IP behind NAT won’t do — you need a server with a stable public address.
Here is what a Hermes Agent host has to do well:
Requirement
Why it matters
**24/7 uptime**
The learning loop only fires when the agent is running
**Persistent disk storage**
SQLite memory + skills files must survive restarts
**Stable public IP / domain**
Webhooks from Telegram, Discord, Slack require a reachable URL
**At least 2 GB RAM**
1 GB works for CLI-only; browser automation needs 4 GB+
**SSL certificate**
Required by Telegram for secure webhook delivery
**Outbound API egress**
Calls to OpenRouter, Anthropic, OpenAI go out continuously
**Process supervisor**
systemd or Docker restart-policy to recover from crashes
**Backups**
Memory loss = capability loss; backups are non-negotiable
The two paths people take are managed hosting (someone else handles the list above) or self-hosted on a VPS (you handle it, often well, sometimes at 3 AM).
## **Hermes Agent Hosting: 3 Categories You’re Actually Choosing Between**
Before the rankings, a quick frame. The Hermes Agent hosting market splits cleanly into three buckets, and most “best of” lists conflate them.
Category
What you get
What you handle
Typical price
**Fully managed**
Server + Hermes deployed + gateway + SSL + backups + updates
Talking to the agent
$9.99/month flat
**Self-hosted VPS**
A Linux box with root access
Everything: install, gateway config, SSL, backups, security
$4–25/month
**Serverless / usage-based**
Pay-per-second container that hibernates when idle
Build, deploy, observability
$0.000–$0.005 per second
xCloud is the only entrant in the fully managed category as of April 2026. Hetzner, Hostinger, DigitalOcean, Vultr, Virtua.Cloud, LightNode, and Bluehost are self-hosted VPS. Railway is serverless. Each has its place.
## **How We Ranked These Hosts**
This list is built on six factors, weighted by how much they affect a Hermes Agent operator’s day-to-day life.
1. **Setup time and effort** — minutes to a working agent, including LLM API key, gateway, and SSL
2. **24/7 reliability** — uptime track record, auto-restart, crash recovery
3. **Memory persistence** — disk durability, backup options, restore time
4. **Messaging gateway readiness** — how much webhook plumbing the host pre-configures
5. **Cost honesty** — list price vs renewal price vs your time cost
6. **Support quality** — response time and depth when something breaks
Pricing was confirmed against each provider’s public pricing page on April 28, 2026. Resource requirements come from the [official Hermes Agent README](https://github.com/nousresearch/hermes-agent) and field reports from production operators on the r/openclaw subreddit. Where Hermes-specific benchmarks exist, they are cited; where they don’t, comparable Docker workload benchmarks are used as a proxy.
## Master Comparison Table
Rank
Provider
Category
Starting Price
Setup Time
Best For
🥇 1
**[xCoud](/hermes-agent-hosting/)**
Fully managed
$9.99/mo
~5 min
Zero-ops Hermes deployment
🥈 2
**Hetzner Cloud**
Self-hosted VPS
$4.59/mo
30–60 min
Cheapest production VPS
🥉 3
**Hostinger VPS**
Self-hosted VPS
$6.49/mo (intro)
15–30 min
One-click Docker template
4
**DigitalOcean**
Self-hosted VPS
$6/mo
30–60 min
Developer documentation
5
**Virtua.Cloud**
Self-hosted VPS
€5/mo
10–20 min
Hermes-specialist EU host
6
**Vultr**
Self-hosted VPS
$5/mo
30–60 min
Global latency / 30+ regions
7
**LightNode**
Self-hosted VPS
Hourly billing
5–10 min
Short-term testing
8
**Bluehost VPS**
Self-hosted VPS
$19.99/mo
30–45 min
Beginner-friendly support
9
**Railway**
Serverless
Pay-per-second
10–20 min
Bursty / idle-mostly use
The table reflects sticker prices. Real cost-of-ownership — including the time tax of self-hosting — is broken down further down in the cost section.
## 🥇 1. xCloud — Best Fully Managed Hermes Agent Hosting
[xCloud](/hermes-agent-hosting/) is the only host that ships Hermes Agent as a one-click managed service rather than a “here’s a Linux box, good luck” VPS. According to [**xCloud’s product page**](/hermes-agent-hosting/), the deployment includes the Hermes binary, a pre-configured Telegram gateway, free SSL, and security updates — all wrapped in a $9.99/month flat rate.
That positioning matters because the [Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs/) walks new users through Python, uv, Node.js, gateway tokens, systemd unit files, reverse proxies, and SSL renewal. Each of those steps has its own failure mode. xCloud’s pitch is that you skip the entire sequence and get to the part that’s actually interesting — building skills and assigning workflows.
xCloud is built by the same team behind WPDeveloper and runs across **global server locations** on AWS, DigitalOcean, Vultr, Linode, Hostinger VPS, Google Cloud, and bring-your-own-Ubuntu providers. The same managed control panel that the team uses for WordPress, Laravel, and n8n hosting now wraps Hermes Agent with a deployment template.
### **Key Features**
- **One-click deploy** — Hermes Agent + gateway + SSL provisioned in roughly five minutes from sign-up
- **Pre-configured Telegram gateway** — bot token field built into the deploy form; Discord, Slack, WhatsApp, and Signal available out of the box
- **Self-improving skills preserved across updates** — Hermes’ procedural memory survives platform updates
- **Free SSL with auto-renewal** — required for Telegram webhook delivery, handled without configuration.
- **24/7 expert support** with sub-four-hour median response time
- **14-day money-back guarantee** — long enough to validate the agent against a real workflow
### **How to Deploy on xCloud**
With xCloud, deploying Hermes Agent is as simple as signing up, choosing your region, and adding your API keys. Everything runs on xCloud’s managed servers, so the entire stack, from provisioning, SSL, to gateway setup, is taken care of for you. Here’s how to get started:”
1. Sign up at [**xCloud Hermes Agent Hosting**](/hermes-agent-hosting/)
2. Pick a region near your messaging users (the closer to your Telegram/Discord traffic, the lower webhook latency)
3. Paste your LLM provider API key (Nous Portal, OpenRouter, Anthropic, or OpenAI)
4. Paste your Telegram bot token to enable the gateway
5. Open Telegram and message your agent
👉 To learn more with a step-by-step guide, visit the guide to [**deploy your own Hermes Agent with xCloud**](/docs/how-to-deploy-hermes-agent-with-xcloud/).
### Pros and Cons
Pros
Cons
✅ Only fully managed Hermes Agent service on the market
❌ Higher sticker price than a raw $4.59 Hetzner box
✅ Memory and skills survive platform updates without operator action
❌ Less low-level customisation than a raw root VPS
✅ Pre-configured Telegram gateway saves the hardest setup step
❌ Region availability tied to xCloud’s partner clouds (still 30+)
✅ Auto-SSL handled by default
❌ Limited tiers mean scaling up is a server upgrade, not a slider.
**Best for:** Founders, agencies, and operators who want the agent running by lunch, not the weekend. Especially worth it for anyone whose hourly rate makes self-hosted setup time the most expensive line item.
## **🥈 2. Hetzner Cloud — Best Budget VPS for Long-Term Production**
Hetzner Cloud’s CX22 plan starts at €4.51 (about $4.59) per month for 2 vCPUs, 4 GB RAM, and 40 GB SSD — specs that comfortably run Hermes Agent with browser automation enabled. [Remote OpenClaw’s cost-of-running analysis](https://www.remoteopenclaw.com/blog/hermes-agent-cost-breakdown) lands on Hetzner as the best price-to-performance ratio of any provider tested for AI agent workloads.
Hetzner is German, has been around since 1997, and runs its own data centres in Falkenstein, Nuremberg, and Helsinki, plus Ashburn (US East) and Hillsboro (US West) for North American latency. The trade-off is documentation depth: Hetzner’s tutorials assume comfort with a Linux terminal. There is no Hermes Agent template, no Application Catalog one-click button, and no on-call support.
### **Key Features**
- **Dedicated CPU options** — CCX series gives Hermes a CPU core nobody else can hit
- **Hourly billing with monthly cap** — pay for partial months when testing
- **Free 20 GB external snapshot storage** for memory database backups
- **40 Gbps unmetered traffic** — generous for inbound webhook traffic from messaging platforms
- **Cloud Firewall included** — gate inbound to Hermes’ webhook port and SSH only
- **API and Terraform provider** — Hermes Agent infrastructure can be code-managed
### **How to Deploy on Hetzner Cloud**
1. Create a Hetzner Cloud project, generate an API token
2. Provision a CX22 instance with Ubuntu 24.04
3. SSH in and run the [official Hermes installer](https://github.com/nousresearch/hermes-agent): `curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash`
4. Run `hermes setup` to configure your LLM provider
5. Configure systemd: `hermes gateway install` to keep the gateway alive across reboots
6. Point a domain via Cloudflare, set up Caddy or nginx for SSL, configure the Telegram webhook URL
The four steps after step 2 are where most operators lose two hours.
### **Pros and Cons**
Pros
Cons
✅ Cheapest production-grade VPS in this comparison
❌ Zero hand-holding — you debug everything yourself
✅ Stable pricing without renewal-rate inflation
❌ No Hermes-specific tooling or templates
✅ Strong privacy posture (German law, owned data centres)
❌ Limited support hours; no live chat for €4.59 plans
✅ Snapshot-based backups built-in
❌ Setup time is the real cost — 30–60 minutes minimum
**Best for:** Engineers running Hermes long-term who are comfortable in a terminal and want the lowest possible monthly hosting bill.
## **🥉 3. Hostinger VPS — Best One-Click Self-Hosted Setup**
Hostinger added a [dedicated Hermes Agent template](https://www.hostinger.com/vps/docker/hermes-agent) to its Application Catalog in early 2026 — pick “Hermes Agent” from the Docker Manager, paste an LLM API key, click deploy, and you have a working agent on a public IP in under 15 minutes.
According to the [Hostinger setup guide](https://www.hostinger.com/support/how-to-get-started-with-hermes-agent-at-hostinger/), the template handles the Docker volume mounts so memory and skills persist across container restarts, configures the gateway, and exposes the CLI through the VPS terminal. The Hostinger AI assistant (Kodee) can also walk through gateway setup if you get stuck.
The catch worth knowing: Hostinger’s introductory rates renew at substantially higher rates. [**Remote OpenClaw documented**](https://www.remoteopenclaw.com/blog/hermes-agent-cost-breakdown) renewal increases of 140–230% above the introductory price. A $4.99/month plan can renew at $11–15/month, which still beats most US providers but is not the headline number.
### **Key Features**
- **Pre-built Hermes Agent Docker template** in the VPS Application Catalog
- **AI assistant (Kodee)** that helps with deployment and troubleshooting
- **NVMe SSD storage** across all VPS plans
- **Weekly backups included** on KVM 1+ plans
- **Choice of Docker Manager or full root SSH** — flexibility for both new and experienced users
- **24/7 chat support** with reasonable response times
### **How to Deploy on Hostinger VPS**
1. Buy a KVM 2 plan (4 GB RAM recommended for browser automation)
2. In the VPS dashboard, open Docker Manager → Catalog
3. Search “Hermes Agent” → Select → Deploy
4. Provide your LLM API key when prompted
5. SSH or use the browser terminal to run `hermes setup` and configure the messaging gateway
6. Point a domain to the VPS IP for the Telegram webhook
### **Pros and Cons**
Pros
Cons
✅ Fastest one-click deploy outside fully managed services
❌ Renewal pricing 140–230% above intro rates
✅ Hermes Agent template officially maintained
❌ Long-term contracts required for the cheapest rate
✅ NVMe storage standard across plans
❌ Memory/skills persistence still requires understanding Docker volumes
✅ Built-in AI assistant for setup help
❌ You still own SSL, gateway, and updates
**Best for:** Solo developers who want one-click deployment but don’t need fully managed support, and are comfortable signing 24-month terms to lock in the introductory rate.
## 4\. DigitalOcean — Best for Developer-Friendly Self-Hosting
DigitalOcean droplets start at $6/month for 1 GB RAM, though most Hermes Agent users want at least the 2 GB ($12/month) tier for browser automation headroom. The pull isn’t price — it’s the documentation. DigitalOcean’s tutorial library is the most extensive in the developer hosting space, which matters when you’re debugging a Telegram webhook at 11 PM and need a clean answer fast.
[The Top 6 Hermes Agent VPS comparison](https://vpssos.com/top-6-hermes-agent-vps-hosting/) calls out DigitalOcean’s clean interface and stability as the main reasons production Hermes deployments end up there despite the higher price. New users also get $200 in credits, which covers four months on the recommended droplet size.
### Key Features
- **One-click Docker droplet** — Hermes deploys as standard Docker image
- **$200 free credit** for new accounts (4 months on a $50/mo droplet)
- **15+ data centre regions** with private networking
- **Spaces object storage** at $5/month for off-droplet backups
- **Managed databases** if Hermes ever outgrows SQLite
- **Best-in-class community tutorials** — large existing Hermes Agent setup guide library
### How to Deploy on DigitalOcean
1. Create a project, add a Basic Droplet (2 GB / 1 vCPU / 50 GB) with Ubuntu 24.04
2. Add an SSH key, attach a $1/mo backup
3. SSH in and run the official Hermes Agent install script
4. Run `hermes setup` to pick a model provider
5. Configure systemd via `hermes gateway install`
6. Add a Cloudflare-proxied domain for SSL and the Telegram webhook URL
### Pros and Cons
Pros
Cons
✅ Largest tutorial library and developer community
❌ More expensive than Hetzner for similar specs
✅ $200 sign-up credit covers 4+ months
❌ No Hermes-specific template (yet)
✅ Reliable infrastructure with strong uptime track record
❌ Backups are an extra $1/mo opt-in
✅ Easy upgrade path to managed databases or Kubernetes
❌ US-only support for entry tiers
**Best for:** Engineers who learn by reading tutorials and want a hosting provider where every weird Hermes question has already been answered on the company blog.
## 5\. Virtua.Cloud — Best Hermes-Specialist European VPS
[Virtua.Cloud](https://www.virtua.cloud/vps/hermes-agent) markets itself directly to Hermes Agent users — the landing page advertises “16 messaging platforms, 400+ AI models, web dashboard, persistent memory” and includes a one-line install script tuned for Hermes. Plans start at €5/month and the data centres are EU-based (independent European hosting, owned infrastructure).
The deployment flow is the closest a self-hosted VPS comes to fully managed without crossing the line. The installer handles dependencies on Debian 12 or Ubuntu 22.04, installs systemd unit files, and exposes a clean web dashboard alongside the CLI.
### Key Features
- **One-line installer** specifically for Hermes Agent
- **EU data residency** (relevant for GDPR-sensitive users)
- **Web dashboard** for managing config, sessions, and skills
- **DDoS protection** included on all plans
- **Full root SSH access** retained for advanced users
- **Hermes-aware support** — the team actually uses the product
### How to Deploy on Virtua.Cloud
1. Pick Debian 12 or Ubuntu 22.04 at checkout
2. Receive credentials immediately upon provisioning
3. SSH in and run the one-line installer
4. The web dashboard becomes available on a subdomain
5. Configure messaging gateways through the dashboard
6. Done — DDoS protection and base firewall are pre-configured
### Pros and Cons
Pros
Cons
✅ Hermes-aware support — team understands the product
❌ Smaller than Hetzner / DigitalOcean (less documentation breadth)
✅ EU-only data residency for privacy-sensitive users
❌ Limited US/Asia presence for global messaging latency
✅ Web dashboard included alongside the CLI
❌ Pricing is in euros — exchange rate variance for non-EU customers
✅ DDoS protection on all plans
❌ Single-region for most plans
**Best for:** EU-based users who want a Hermes-specialist host with a web UI and don’t need the managed convenience of xCloud. A reasonable middle ground between Hetzner’s bare metal and xCloud’s full managed service.
## 6\. Vultr – Best for Global Messaging Latency
Vultr runs 30+ data centres on six continents, which is the practical reason it shows up in Hermes Agent comparisons. If your Telegram users are in Singapore and your VPS is in Frankfurt, the gateway round-trip adds noticeable latency. Vultr lets you put the agent close to the users.
Pricing starts at $5/month for 1 GB RAM and scales linearly. There is no Hermes-specific template, but Docker is supported on every instance and the standard Hermes installer works without modification.
### Key Features
- **30+ global data centre locations** — most regions of any major VPS provider
- **Hourly billing** for short-term testing
- **High-frequency CPU plans** for compute-bound Hermes workflows
- **Block storage and snapshots** for memory backups
- **IPv6 included** by default
### How to Deploy on Vultr
1. Pick a region close to your primary messaging traffic
2. Provision a Cloud Compute instance with Ubuntu 24.04 and 2+ GB RAM
3. SSH in, install Docker, run the official Hermes Agent install script
4. Configure the gateway via `hermes gateway`
5. Use Cloudflare or Vultr’s reserved IP for the Telegram webhook URL
### Pros and Cons
Pros
Cons
✅ Best regional coverage of any provider in this comparison
❌ No Hermes-specific tooling
✅ Hourly billing for short-term tests
❌ Documentation thinner than DigitalOcean
✅ Reasonable pricing across all regions
❌ Less generous free tier than DigitalOcean
✅ Reserved IPs available for stable webhook URLs
❌ Performance per dollar lags Hetzner
**Best for:** Operators whose Hermes Agent talks to users across multiple continents and who care about gateway-to-user latency more than absolute price.
## 7\. LightNode — Best for Testing and Hourly Billing
LightNode shows up in the [**VPS SOS Hermes Agent comparison**](https://vpssos.com/top-6-hermes-agent-vps-hosting/) primarily because of its hourly billing model and 40+ global locations. Spin up an instance for $0.018/hour, test Hermes for an afternoon, destroy it, and pay roughly $0.15. That’s a useful pattern when you’re still picking which LLM provider works best for your workflows.
LightNode is not the right answer for production. The infrastructure is solid for testing but the support, tooling, and documentation aren’t at Hetzner or DigitalOcean’s level. Use it to evaluate, then move when you’re committed.
### Key Features
- **Hourly billing** without commitment
- **Sub-2-minute provisioning** — fastest deploy in this list
- **40+ global locations** covering Asia, Europe, and the Americas
- **No long-term contracts** required
- **Crypto and PayPal payment options** for flexibility
### How to Deploy on LightNode
1. Sign up, top up the wallet with $5
2. Pick a location and a 2 GB instance
3. SSH in within two minutes, run the Hermes installer
4. Configure for testing — skip the gateway and SSL setup if you’re only using the CLI
5. Destroy the instance when done; data is wiped
### Pros and Cons
Pros
Cons
✅ Hourly billing means cheap experimentation
❌ Not designed for long-term production
✅ Fastest provisioning of any provider tested
❌ Smaller support team than incumbents
✅ 40+ regions for latency testing
❌ Documentation thin; little Hermes Agent specific guidance
✅ Flexible payment options including crypto
❌ Resource performance variable across regions
**Best for:** Developers in the evaluation phase who want to spin up Hermes in five different regions, compare latency, and only pay for the hours used.
## 8\. Bluehost VPS — Best for Beginner-Friendly Always-On Setup
Bluehost is better known for shared WordPress hosting, but its VPS line works for Hermes Agent and shows up on this list for one reason: the support model. Bluehost has phone support, live chat, and an onboarding team that walks first-time VPS users through deployment. None of the cheaper providers offer that.
According to [**Bluehost’s Hermes Agent guide**](https://www.bluehost.com/blog/run-hermes-agent-vps/), their VPS plans give the always-on foundation, root access, and resource control needed for long-running Hermes workflows — and the company’s own engineers wrote the deployment tutorial.
Pricing starts at $19.99/month, which is more than Hetzner and Hostinger but cheaper than the full xCloud managed tier. The middle ground here is real: a beginner-friendly self-hosted experience without paying for full management.
### Key Features
- **Phone and live chat support** — rare at this price tier for VPS
- **Pre-installed Linux distros** with cPanel option
- **Free domain name** with annual plans
- **NVMe storage** across VPS plans
- **Built-in caching and security tools**
### How to Deploy on Bluehost VPS
1. Buy a Standard or Enhanced VPS plan
2. Use Bluehost’s onboarding chat to provision the server with Ubuntu
3. SSH in and run the Hermes Agent install script
4. Configure the gateway and SSL via the included WHM panel or manually
5. Set up the systemd service for auto-restart
### Pros and Cons
Pros
Cons
✅ Phone support included — uncommon for VPS at this price
❌ Roughly 4x the price of Hetzner for similar specs
✅ Beginner-friendly onboarding with hand-holding
❌ No Hermes-specific tooling
✅ Free domain on annual plans
❌ cPanel-style management adds overhead some operators dislike
✅ Long uptime track record
❌ Renewal pricing also climbs after intro period
**Best for:** First-time VPS users who want an always-on Hermes Agent and value being able to call a human when something breaks.
## 9\. Railway — Best for Serverless / Pay-Per-Second Hermes Hosting
Railway is the outlier on this list. It doesn’t sell servers — it sells a platform-as-a-service where Hermes runs in a container that scales to zero when idle and bills per second when active. For a Hermes Agent that only fires a few times per day, Railway can cost less than $5/month while a $5/month always-on VPS sits idle 95% of the time.
The trade-off is cold starts. A scaled-to-zero Hermes Agent takes a few seconds to wake up, which is fine for cron-driven workflows and noticeable for interactive Telegram chat. The right fit depends on what you’re doing with the agent.
### Key Features
- **Per-second billing** with usage-based pricing
- **Scale to zero** when idle
- **Git-based deploys** — push to deploy, rollback in one click
- **Built-in Postgres** for operators who outgrow SQLite
- **Generous free tier** for small workloads
### How to Deploy on Railway
1. Connect a GitHub repository with a Hermes Agent Dockerfile
2. Railway auto-detects Docker, deploys
3. Set environment variables: LLM API key, Telegram bot token, persistent volume mount path
4. Attach a Railway volume for memory persistence
5. Add a custom domain for the Telegram webhook
6. Push to main; Railway redeploys automatically
### Pros and Cons
Pros
Cons
✅ Scales to zero — pay nothing when idle
❌ Cold start delay on first message after idle
✅ Git-driven deploys and rollback
❌ Persistent volumes have stricter size limits
✅ Works well for cron-driven Hermes workflows
❌ Pricing model harder to predict than flat VPS
✅ Built-in Postgres available if needed
❌ Less suited for chat-heavy interactive use
**Best for:** Hermes Agent setups that run scheduled workflows (research, summaries, monitoring) rather than interactive chat — where a few seconds of cold-start latency on each invocation is fine and the cost savings of scale-to-zero are real.
## Resource Requirements: What Hermes Agent Actually Needs
The [official Hermes Agent README](https://github.com/nousresearch/hermes-agent) gives baseline requirements. Real-world numbers from operators land in this range:
Workload
vCPU
RAM
Storage
Bandwidth
CLI-only personal use
1
1 GB
10 GB
100 GB/mo
Single messaging channel
1
2 GB
20 GB
250 GB/mo
Multi-channel gateway (Telegram + Slack + Discord)
2
4 GB
40 GB
500 GB/mo
Multi-channel + browser automation
2–4
4–8 GB
60 GB
1 TB/mo
Heavy automation + multiple concurrent skills
4
8 GB
80 GB
2 TB/mo
The Camofox anti-detection browser introduced in Hermes Agent v0.7.0 needs roughly 2 GB of additional RAM. A $5/month plan with 1 GB RAM that handled Hermes fine in v0.6 will swap heavily in v0.7+ if browser tools are enabled.
## **Cost Breakdown: What You’ll Actually Pay**
Real cost has three components: hosting, LLM tokens, and your time. The first is easy to compare, the second varies wildly, and the third is the line item people forget.
Setup
Hosting/mo
LLM tokens/mo
Your time/mo
Total monthly cost
**xCloud managed** + DeepSeek V4
$9.99
$5–15
~$0 (zero ops)
**$29–39**
**Hetzner CX22** + DeepSeek V4
$4.59
$5–15
1–3 hrs ($30–150 at $30–50/hr)
**$39–169**
**Hostinger KVM 2 (intro)** + Claude Haiku
$6.49
$15–30
1–2 hrs
**$50–85**
**DigitalOcean 2 GB** + OpenRouter
$12
$10–25
1–2 hrs
**$52–87**
**Virtua.Cloud €5** + DeepSeek V4
$5.30
$5–15
1 hr
**$40–80**
**Vultr 2 GB** + Claude Haiku
$12
$15–30
1–2 hrs
**$57–92**
**LightNode hourly** + DeepSeek V4
$13–18
$5–15
30 min
**$33–58**
**Bluehost VPS Standard** + OpenRouter
$19.99
$10–25
1 hr
**$60–95**
**Railway pay-per-second** + DeepSeek V4
$0–10
$5–15
1–2 hrs
**$35–75**
The “your time” column is what most comparisons skip. If your billable rate is $50/hour and self-hosting takes three hours of setup plus an hour a month maintaining it, that’s $50/month on top of the $4.59 Hetzner bill — and the cheapest VPS is suddenly the most expensive option.
## Setup Difficulty: How Hard Each Path Is in Practice
Provider
Setup time
Skills needed
Ongoing maintenance
**xCloud**
~5 min
None — just a credit card
Minimal — managed updates
**Hetzner Cloud**
30–60 min
Linux CLI, systemd, nginx/Caddy, Cloudflare
Hours per month
**Hostinger VPS**
15–30 min
Docker basics, Application Catalog familiarity
Moderate
**DigitalOcean**
30–60 min
Linux CLI, Docker, systemd
Hours per month
**Virtua.Cloud**
10–20 min
Basic Linux comfort
Low — installer handles most
**Vultr**
30–60 min
Linux CLI, Docker, systemd
Hours per month
**LightNode**
5–10 min
Basic terminal use
Minimal — testing only
**Bluehost VPS**
30–45 min
Some Linux comfort, willingness to chat support
Moderate
**Railway**
10–20 min
Git, Docker, Railway-specific config
Low after initial setup
## Common Mistakes Operators Make Choosing Hermes Hosting
Five patterns repeat in production deployments and Reddit threads:
- **Picking the cheapest VPS without budgeting time.** A $4.59 Hetzner box that takes three hours to set up costs more than $9.99 of xCloud once your hourly rate is in the math.
- **Forgetting persistent volumes.** Hermes’ learning loop only matters if memory and skills survive a container restart. Several operators have lost weeks of accumulated skills by running Docker without a mounted volume.
- **Skipping SSL and HTTPS for the gateway.** Telegram requires HTTPS for webhook delivery. Operators who try to wire a plain HTTP webhook spend an hour debugging before realising this.
- **Running v0.7+ on 1 GB RAM.** Camofox browser automation needs 4 GB total. A 1 GB plan that worked fine on v0.6 will OOM on v0.7+.
- **Not setting up a process supervisor.** Without systemd or Docker `restart: unless-stopped`, the agent dies on first crash and stays dead until you SSH in. The whole 24/7 promise depends on auto-restart.
## Audience Mapping: Which One Fits Your Situation
If you are…
Best choice
Why
A founder validating an AI workflow
**xCloud**
5-minute deploy means you find out if Hermes solves your problem this week, not next month
A solo developer comfortable in a terminal
**Hetzner Cloud**
Lowest sticker price, you’ll tolerate the setup
A solo developer who hates Linux configs
**Hostinger VPS**
Application Catalog template skips the worst parts
Running an agency with 5+ Hermes deployments
**xCloud**
Multi-server management in one panel
Building inside the EU with GDPR concerns
**Virtua.Cloud**
EU-only data residency, Hermes-aware team
Connecting to global users on multiple continents
**Vultr**
Region count beats everyone
Just testing for a weekend
**LightNode**
Hourly billing wastes nothing
New to VPS but want self-hosted
**Bluehost VPS**
Phone support catches you when stuck
Running scheduled / cron-only workflows
**Railway**
Scale-to-zero saves real money on idle agents
## Frequently Asked Questions
### **What is the best hosting for Hermes Agent in 2026?**
For most users, [xCloud’s managed Hermes Agent hosting](/hermes-agent-hosting/) is the practical answer because it removes the entire infrastructure layer for $9.99/month. For developers who prefer to self-host, Hetzner Cloud delivers the best price-to-performance, and Hostinger VPS has the smoothest one-click Docker deployment thanks to its [Application Catalog template](https://www.hostinger.com/vps/docker/hermes-agent).
### **Can I run Hermes Agent on a self-managed server?**
Yes, for CLI-only and single-channel use. Hermes Agent without browser automation needs roughly 1 vCPU and 1 GB RAM, which fits comfortably on a self-managed server. Once you enable browser tools (Camofox or Chrome CDP) in v0.7+, plan on 4 GB RAM minimum, which moves you to $9.99–24/month tiers depending on provider.
### **Do I need a GPU for Hermes Agent hosting?**
No. Hermes Agent calls hosted LLM APIs (OpenAI, OpenRouter, Anthropic, Nous Portal) by default, so the VPS only handles agent logic, memory, and the gateway — all CPU-light work. A GPU is only relevant if you decide to run a local LLM via Ollama or vLLM on the same box, which is a different deployment pattern.
### **Is xCloud the only managed Hermes Agent host?**
As of April 2026, yes. Hostinger has a Docker template, Virtua.Cloud has a one-line installer, and Bluehost has a tutorial, but xCloud is the only provider that runs Hermes as a fully managed service with pre-configured gateways, automatic updates, and support that knows the product.
### **How much does it cost to run Hermes Agent for a year?**
A budget setup using Hetzner CX22 + DeepSeek V4 lands around $90–180/year for hosting and tokens combined. A managed setup on xCloud + a moderately-priced model lands around $350–500/year. A premium setup with Claude Sonnet 4.6 on a 4 GB VPS runs $500–1,000/year. The model choice typically dominates the bill once usage scales.
### **Will my agent’s memory and skills persist across server restarts?**
Only if you configure persistent storage correctly. Hermes Agent stores memory in `~/.hermes/` by default. On Docker, mount that path as a named volume. On a VPS, the data lives on the disk and survives reboots automatically. Managed services like xCloud handle this for you and back it up daily.
### **Can Hermes Agent run alongside OpenClaw on the same server?**
Yes. Both projects are documented to coexist on a single VPS, and the [HermesClaw community bridge](https://github.com/nousresearch/hermes-agent) even lets them share a WeChat account. Allocate at least 4 GB RAM if you want both running with browser automation enabled.
### **What happens if Telegram requires SSL for webhooks?**
Telegram’s Bot API requires HTTPS for webhook delivery, period. Self-hosted setups need a domain pointed at the VPS plus Let’s Encrypt, Caddy, or Cloudflare for SSL. Managed services like [xCloud](/hermes-agent-hosting/) handle SSL automatically. This single requirement is why so many self-hosted Hermes deployments stall on day one.
### **Is Hermes Agent good for non-technical users?**
The agent itself is approachable through Telegram or Discord chat once running. The setup is the hard part. For non-technical users, fully managed hosting through xCloud is the realistic option — none of the self-hosted paths in this list are non-developer-friendly, regardless of how the marketing describes them.
### **How does Hermes Agent compare to OpenClaw and Paperclip for hosting?**
All three run on similar VPS specs (2 GB RAM minimum) and the xCloud platform offers [**managed hosting for each at $9.99/month**](/openclaw-vs-paperclip-vs-hermes/). Hermes is the lightest of the three on idle resources because of its single-process architecture. Paperclip needs Postgres, which adds memory overhead. OpenClaw’s resource use scales with the number of messaging channels enabled.
### **Can I migrate from one host to another later?**
Yes. Hermes Agent stores everything important in `~/.hermes/` — memory database, skills, config, credentials. Tar that directory, copy to the new server, untar, restart the agent, and your accumulated skills and memory move with it. The migration takes minutes; the platform lock-in concern is essentially zero.
### **Where can I get help if my Hermes setup breaks?**
For Hermes-specific issues: the [**Nous Research Discord**](https://hermes-agent.nousresearch.com/) and the GitHub Issues tab. For hosting-specific issues: each provider’s own support — xCloud and Bluehost have the most responsive human support for Hermes-related questions specifically.
## **Conclusion: Your 2026 Hermes Agent Hosting Roadmap**
The Hermes Agent hosting decision comes down to a single trade: how much of your weekend do you want to spend on infrastructure?
If the answer is “none,” xCloud’s managed service is the only entry on this list that actually delivers that. If the answer is “I enjoy it and I want the lowest possible bill,” Hetzner Cloud has earned its reputation. Everyone else fits between those two poles based on which trade-offs you’re prepared to make.
### Expert Picks by Goal
Your goal
Best choice
Why
Best fully managed
**[xCloud](/hermes-agent-hosting/)**
Only fully managed Hermes Agent service with pre-configured gateways
Best budget VPS
**Hetzner Cloud**
Best price-to-performance for production workloads
Best one-click deploy
**Hostinger VPS**
Pre-built Hermes Agent template in Application Catalog
Best for developers
**DigitalOcean**
Largest tutorial library and developer community
Best for EU privacy
**Virtua.Cloud**
EU-only data residency with Hermes-aware support
Best for global reach
**Vultr**
30+ regions covering all six continents
Best for testing
**LightNode**
Hourly billing for short-term experiments
Best for beginners
**Bluehost VPS**
Phone support included at the price tier
Best for serverless
**Railway**
Scale-to-zero saves money on idle agents
**What to do this week:** Pick the row that matches your situation, deploy on the matching host, and run Hermes against one real workflow for two weeks. Either it earns its keep, or it doesn’t, and you find out fast. The 14-day money-back guarantee on xCloud’s managed plan gives you a free trial of the fastest path. The hourly billing on LightNode gives you a free trial of the cheapest. Between those two options, you can answer the question for under $25.
The honest take after watching this market for six months: the people getting the most out of Hermes Agent in 2026 are not the ones who picked the absolute cheapest host. They’re the ones who matched the host to the workload and stopped tinkering with infrastructure when the agent was running. Whichever direction you go, that’s the move worth making.
If you found this guide useful, [**subscribe to the xCloud blog**](/blog/) for more deep-dive comparisons on hosting AI agents, automation tools, and the open-source stack powering modern operators. You can also join the **[xCloud Facebook community](https://www.facebook.com/groups/xcloud.community)** to compare setups with other Hermes Agent operators.
---
# 9 Best Hosting for WooCommerce in 2026: Speed, Cost & Scalability Compared - xCloud
> Learn which WooCommerce hosting delivers the fastest speed, lowest real cost, and best scalability in 2026. 9 providers compared with independent benchmarks.
WooCommerce now powers **over 4.17 million live online stores worldwide**, making it the most widely used eCommerce platform by store count, [**according to BuiltWith**](https://trends.builtwith.com/shop/WooCommerce). Yet most of those stores never reach their revenue potential because of one preventable mistake: choosing the wrong hosting. Research from [**Akamai**](https://www.akamai.com/site/en/documents/research-paper/akamai-online-retail-performance-report-milliseconds-are-critical.pdf) shows a 1-second delay in page load time reduces conversions by up to 7%, and [**Colorlib reports**](https://colorlib.com/wp/woocommerce-statistics/) only 33–40% of WooCommerce stores currently pass Google’s Core Web Vitals, compared to 75–78% for Shopify stores.
This guide ranks the 9 best hosting providers for WooCommerce in 2026 based on speed benchmarks, real pricing, scalability under traffic spikes, and WooCommerce-specific features verified across G2, Trustpilot, Capterra, and independent technical reviews.
## **Quick Summary: Best Hosting for WooCommerce at a Glance**
Here is a quick expert guide for you. The table below shows what to pick based on what you actually need:
If You Want To…
Use This
Starting Price
Best For
Cut hosting costs by ~40% vs. Cloudways while keeping managed features
**xCloud**
Free → $5/mo
Stores wanting cost-efficient managed cloud + BYOS
Run a high-traffic store with zero server decisions
**Kinsta**
$35/mo (WooCommerce: $115/mo)
Stores with $100K+ ARR
Scale across multiple cloud providers from one panel
**Cloudways**
$14/mo
Existing Cloudways users, multi-cloud teams
Launch your first WooCommerce store cheaply
**Hostinger**
$2.69/mo
New stores, side projects
Get reliable shared hosting with 24/7 phone support
**SiteGround**
$2.99/mo
Non-technical store owners
Match enterprise speed without enterprise prices
**Rocket.net**
$30/mo
Speed-obsessed merchants
Auto-scale during Black Friday traffic spikes
**Nexcess**
$21/mo
Seasonal peak stores
Run heavy-plugin WooCommerce builds on dedicated VPS
**Liquid Web**
$25/mo
Established stores
Host on a Genesis-friendly managed platform
**WP Engine**
$25/mo (WooCommerce: ~$50/mo)
Agencies, content-driven stores
[**According to Online Media Masters**](https://onlinemediamasters.com/xcloud-review/), xCloud is around 40% cheaper than Cloudways at equivalent server specs, while [**Blog Marketing Academy confirmed**](https://www.blogmarketingacademy.com/xcloud-hosting-review/) xCloud has measurably faster page loads on identical Vultr High Frequency hardware after migrating 11 sites away from Cloudways.
- **Best for Beginners:** [**Hostinger**](https://www.hostinger.com/) has the cheapest entry price with a WooCommerce-optimized stack and 24/7 chat support
- **Best for Growing Stores:** [**xCloud**](/) has a free tier (1 server, 10 sites) plus ~40% lower cost per server vs. Cloudways
- **Best for Enterprise:** [**Kinsta**](https://kinsta.com/) runs on Google Cloud C3D infrastructure with Cloudflare Enterprise included on every plan
## **Why WooCommerce Hosting is Different from Regular WordPress Hosting**
WooCommerce is not a typical WordPress site. [**According to WP101**](https://wp101.com/best-woocommerce-hosting/), every product page, cart action, and checkout triggers database queries, PHP execution, session handling, and frequently a payment gateway API call, all happening in real time. Generic shared hosting that handles a brochure site fine will buckle under WooCommerce traffic.
Three technical factors make WooCommerce uniquely demanding for hosting:
- **Uncacheable pages:** Cart, checkout, and “My Account” pages cannot be cached the same way blog posts are, because each visitor’s session data is unique. [**Kinsta’s documentation**](https://kinsta.com/blog/woocommerce-hosting/) confirms these pages must be excluded from full-page cache to prevent users seeing each other’s carts.
- **PHP workers handle concurrent checkouts:** A single PHP worker can only process one checkout at a time. Stores running flash sales need 4+ PHP workers minimum to avoid timeouts. This is why [**Kinsta recommends its Business 1 plan ($115/month) as the minimum for WooCommerce**](https://kinsta.com/pricing/), since it is the first tier with 4 PHP workers.
- **Database load grows with order volume:** WooCommerce makes hundreds of database calls per page load. Without Redis or Memcached object caching, the database becomes the bottleneck once you exceed roughly 50–100 concurrent shoppers.
Beyond the technical demands, the financial stakes are higher than for any other site type. Research from [**Walmart, cited in a Cloudways speed analysis**](https://www.cloudways.com/blog/site-speed-impact-conversions/), shows a 2% conversion lift for every 1-second improvement in load time. For a store doing $10,000/month, that is roughly $200/month in recovered revenue per second saved, which is far more than the cost difference between any two hosts on this list.
## **How We Ranked the Best WooCommerce Hosting Providers**
Rankings are based on five criteria weighted by impact on store revenue, not on affiliate commission rates or marketing claims:
Criterion
Weight
What We Measured
**Speed under WooCommerce load**
30%
TTFB and LCP on a sample WooCommerce install with 50 products, tested via PageSpeed Insights and GTmetrix
**Real cost (year 1 + year 2)**
25%
Listed pricing including renewal hikes, server fees, and required add-ons
**WooCommerce-specific features**
20%
Cache rules for cart/checkout, Redis support, PHP workers, HPOS compatibility
**Scalability**
15%
Ease of upgrading plans, autoscaling availability, traffic spike handling
**Support quality**
10%
Verified reviews on G2, Trustpilot, and Capterra; response times during checkout issues
Pricing data was verified directly from each provider’s official pricing page in April 2026. Performance claims are cross-referenced with independent reviews from [**Online Media Masters**](https://onlinemediamasters.com), [**Blog Marketing Academy**](https://www.blogmarketingacademy.com), [**Managed WP Guide**](https://managedwpguide.com), and [**WPBeginner**](https://www.wpbeginner.com/best-woocommerce-hosting/).
## Master Comparison: Best WooCommerce Hosting Providers 2026
Rank
Provider
Speed (LCP)
Starting Price
WooCommerce Plan
Best For
🥇 1
**xCloud**
★★★★★ (1.6s avg)
Free → $5/mo
$5/mo + server cost
Cost-efficient managed cloud, BYOS flexibility
🥈 2
**Kinsta**
★★★★★ (1.7s avg)
$35/mo
$115/mo (Business 1)
Premium enterprise stores
🥉 3
**Cloudways**
★★★★ (1.9s avg)
$14/mo
$46/mo (4GB DO)
Multi-cloud teams
4
**Rocket.net**
★★★★★ (1.5s avg)
$30/mo
$30/mo
Speed-obsessed merchants
5
**Nexcess**
★★★★ (2.0s avg)
$21/mo
$21/mo (Spark)
Seasonal autoscaling
6
**WP Engine**
★★★★ (2.1s avg)
$25/mo
~$50/mo (Professional)
Agencies, content stores
7
**SiteGround**
★★★★ (2.0s avg)
$2.99/mo\*
$7.99/mo (GrowBig)\*
Beginner-friendly setup
8
**Hostinger**
★★★ (2.2s avg)
$2.69/mo\*
$3.99/mo (Business)\*
Budget-conscious launch
9
**Liquid Web**
★★★★ (1.9s avg)
$25/mo
$25/mo (Spark)
Heavy-plugin WooCommerce
\*Introductory price; renewal pricing is significantly higher. LCP figures based on aggregated independent benchmarks from Online Media Masters, Managed WP Guide, and PageSpeed Matters.
## 🥇 1. xCloud — Best for Cost-Efficient Managed Hosting + BYOS Flexibility
[**According to Online Media Masters’ independent review**](https://onlinemediamasters.com/xcloud-review/), [**xCloud**](/) is around 40% cheaper than Cloudways at identical server specifications, while running a measurably faster tech stack on the same Vultr hardware. [**Blog Marketing Academy reached the same conclusion**](https://www.blogmarketingacademy.com/xcloud-hosting-review/) after migrating 11 client sites and observing faster TTFB on every site, even on a 1 vCPU / 1GB RAM server.
What makes [**xCloud**](/) different is its dual-mode architecture. You can either use [**xCloud Managed Servers**](/hosting-for-wordpress/) starting at $3/month, or use the Bring Your Own Server (BYOS) model to connect any cloud provider (Vultr, DigitalOcean, AWS, Google Cloud, Linode, Hetzner, or Contabo) and pay just $5/month per server for the control panel. This eliminates the markup that traditional managed hosts add on top of cloud infrastructure, which is the core reason WordPress professionals switched after DigitalOcean acquired Cloudways in 2022.
For WooCommerce specifically, [**xCloud’s WooCommerce Hosting page**](/woocommerce-hosting/) details Redis caching presets tuned for WooCommerce database queries, NGINX FastCGI full-page caching with cart/checkout exclusions configured by default, and OpenLiteSpeed support for stores running LiteSpeed Cache plugin.
### **Key Features**
- **BYOS pricing:** Free for 1 server + 10 sites; $5/server for 1–5 servers; $4 (6–10); $3 (10+), confirmed in [**xCloud’s billing documentation**](/docs/how-billing-works-in-xcloud/)
- **Full root SSH access:** Unlike Kinsta or WP Engine, you have complete server control
- **WooCommerce caching presets:** Pre-configured Redis rules and FastCGI cache exclusions for cart/checkout
- **Free migration:** Bulk + single-site WordPress migration plugin with team-assisted transfers
- **OpenLiteSpeed option:** LiteSpeed web server for stores using LiteSpeed Cache
- **7G/8G Firewall:** Web Application Firewall protection against XSS, SQL injection, bad bots
- **Staging environments:** Every site includes a separate staging environment with one-click “Go Live”
- **100 free transactional emails/month:** Mailgun, SendGrid, Elastic Email integrations
- **No site limits:** Host unlimited WooCommerce stores per server (unlike Kinsta’s per-site pricing)
### **How to Get Started with xCloud for WooCommerce?**
Getting started with [**xCloud**](/) is pretty simple. Pick the path that matches your situation:
**Option A: BYOS (Bring Your Own Server) — Cheapest Path**
1. Sign up for [**xCloud’s**](/) free tier.
2. Sign up for a Vultr or DigitalOcean account (new accounts get $300 / $200 in free credits).
3. Add your cloud provider API key in xCloud’s dashboard.
4. Spin up a Vultr High Frequency server (2 vCPU, 4GB RAM is the sweet spot for WooCommerce).
5. Install WordPress + WooCommerce in one click.
6. Migrate your existing store using xCloud’s free migration plugin.
**Option B: xCloud Managed Hosting — Easiest Path**
1. Choose a plan from [**xCloud’s WooCommerce Hosting page**](/woocommerce-hosting/)
2. Pick a server location closest to your customers.
3. Install WordPress + WooCommerce automatically.
4. Request free migration assistance.
## **Detailed Guides:**
- [**xCloud vs Cloudways: Complete Comparison**](/xcloud-vs-cloudways/)
- [**Best Cloudways Alternatives in 2026**](/best-cloudways-alternatives/)
- [**Best WP Engine Alternatives 2026**](/best-wp-engine-alternatives/)
### **Pros and Cons**
Pros
Cons
✅ ~40% cheaper than Cloudways at equivalent specs (per Online Media Masters)
❌ Requires basic understanding of “control panel + cloud provider” model
✅ Free tier with 1 server + 10 sites
❌ Self-service support model (docs + chat, no phone)
✅ Full root SSH access (rare among managed panels)
❌ Newer than Cloudways/Kinsta, smaller community
✅ OpenLiteSpeed and NGINX both supported
❌ BYOS users pay separately for cloud server
✅ Built-in WooCommerce cache presets
❌ Some advanced features still in active development
✅ White-label option for agencies
**Best for:** Store owners who outgrew shared hosting, agencies managing 5+ WooCommerce sites, and existing Cloudways users feeling squeezed by post-acquisition pricing increases.
## **🥈 2. Kinsta — Best for Premium Enterprise WooCommerce Stores**
[**According to Kinsta’s official pricing page**](https://kinsta.com/pricing/), the company recommends its Business 1 plan ($115/month) as the minimum for WooCommerce stores, specifically because it is the first tier with 4 PHP workers, the threshold needed to handle concurrent checkout sessions without timeouts. [**Managed WP Guide confirms**](https://managedwpguide.com/kinsta-hosting/) this is well-aligned with reality: stores doing meaningful checkout volume will hit ceiling errors on Kinsta’s $35 Starter and $70 Pro plans.
[**Kinsta**](https://kinsta.com/) runs every site in isolated Linux Containers on Google Cloud Platform’s premium tier C3D machines, with Cloudflare Enterprise CDN bundled on every plan. [**G2’s 2026 Best Software Awards**](https://www.g2.com/products/kinsta/) ranks Kinsta #1 for premium WordPress hosting based on 930+ verified reviews averaging 4.8/5.
### Key Features
- **Google Cloud C3D infrastructure:** Same hardware tier used by Google’s own products
- **Cloudflare Enterprise included:** Worth $200+/month if purchased separately
- **Isolated containers:** Other tenants’ traffic spikes can’t slow your store
- **PHP workers per plan:** Starter (2), Pro (2), Business 1 (4), Business 2 (6), Business 3 (8)
- **Free unlimited migrations:** Handled by Kinsta’s migration team, no downtime
- **APM monitoring:** Built-in WordPress performance tool included free
- **30-day money-back guarantee:** Full refund on any plan
### **How to Implement Kinsta for WooCommerce?**
Whenever you’re going to use Kinsta for WooCommerce, keep in mind the entry plans don’t fit production stores. Follow these steps:
1. Sign up at [**Kinsta**](https://kinsta.com/) (no free trial, relies on 30-day money-back guarantee)
2. Choose Business 1 plan ($115/month) for stores doing $5K+ monthly revenue
3. Request free migration via the MyKinsta dashboard
4. Configure WooCommerce caching exclusions (auto-applied on Kinsta)
5. Test checkout under load before pointing DNS
### **Pros and Cons**
Pros
Cons
✅ Top-tier infrastructure (Google C3D + Cloudflare Enterprise)
❌ Expensive at $115/month minimum for WooCommerce
✅ Excellent 24/7 WordPress-specialist support
❌ Per-site pricing punishes multi-store operators
✅ Free migrations on all plans
❌ No phone support, chat-only
✅ Strong CWV pass rates (verified by independent benchmarks)
❌ Rigid plan tiers; overage fees if you exceed visit limits
✅ APM tool included
❌ No free trial, only money-back guarantee
**Best for:** Established WooCommerce stores doing $20,000+ monthly revenue where downtime carries real revenue cost and the founder wants zero infrastructure decisions.
## 🥉 3. Cloudways — Best for Multi-Cloud Teams (with Caveats)
[**According to Managed WP Guide’s Cloudways analysis**](https://managedwpguide.com/cloudways-hosting/), Cloudways serves over 100,000 customers and hosts 570,000+ websites. The platform’s core strength is letting you pick the underlying cloud (DigitalOcean, Vultr, Linode, AWS, or Google Cloud) while [**Cloudways**](https://www.cloudways.com/) handles caching, security patches, and backups on top.
That said, [**Trustpilot reviews**](https://www.trustpilot.com/review/cloudways.com) and [**G2 reviews**](https://www.g2.com/products/cloudways/) document a pattern of pricing increases and support degradation since DigitalOcean’s 2022 acquisition. [**Online Media Masters calculates**](https://onlinemediamasters.com/xcloud-review/) that Cloudways’ Vultr High Frequency 2vCPU/4GB plan at $60/month costs only $24/month on xCloud at retail Vultr pricing, a markup of around 60%.
### Key Features
- **5 cloud providers:** DigitalOcean, Vultr, Linode, AWS, Google Cloud
- **Built-in stack:** Varnish + Redis + Memcached + Nginx + PHP-FPM
- **Cloudflare Enterprise add-on:** $4.99/month per site
- **Object Cache Pro:** Included free on 4GB+ servers (otherwise $95/month standalone)
- **Pay-as-you-go billing:** No long-term contracts
- **Free SSL + automated backups:** Standard on all plans
- **3-day free trial:** No credit card required
### How to Implement Cloudways for WooCommerce?
1. Start the [**3-day free trial at Cloudways**](https://www.cloudways.com/)
2. Choose DigitalOcean (cheapest, best for most stores) or Vultr High Frequency (faster CPU)
3. Pick a 4GB RAM server minimum for WooCommerce ($46/month on DigitalOcean)
4. Use Cloudways Migrator plugin or request paid migration ($25/site)
5. Enable the Cloudflare Enterprise add-on for global speed
### **Pros and Cons**
Pros
Cons
✅ Multi-cloud flexibility
❌ ~60% markup over retail cloud pricing (per OMM benchmarks)
✅ Strong stack with Object Cache Pro on 4GB+
❌ Support quality degraded post-acquisition (per G2 reviews)
✅ Pay-as-you-go billing
❌ Cloudflare Enterprise costs extra ($4.99/site)
✅ 100,000+ customers, mature platform
❌ No root access
✅ 3-day free trial
❌ Phone support requires $100/month upgrade
**Best for:** Existing Cloudways users who don’t want to migrate, agencies that need multi-cloud-vendor support in a single dashboard, and Magento or Laravel stores that need PHP application flexibility.
## 4\. Rocket.net — Best for Speed-Obsessed Merchants
[**Online Media Masters’ Rocket.net review**](https://onlinemediamasters.com/rocket-net-review/) calls [**Rocket.net**](https://rocket.net/) “the best Cloudflare Enterprise implementation in managed WordPress hosting” because it bundles Cloudflare Enterprise with Argo Smart Routing on every plan starting at $30/month, a feature combination that costs $250+/month if assembled separately.
Rocket.net runs every site on a single CPU core dedicated to that site, with Object Cache Pro included free. For WooCommerce stores where checkout speed directly affects conversion, the result is consistently low TTFB and fast LCP scores in independent CrUX data.
### **Key Features**
- **Cloudflare Enterprise on every plan:** Including Argo Smart Routing
- **Object Cache Pro included free:** Normally $95/month standalone
- **Per-site dedicated CPU:** Other sites can’t steal your resources
- **30-day money-back guarantee**
- **Free migrations:** Handled by Rocket.net’s team
### Pros and Cons
Pros
Cons
✅ Best-in-class Cloudflare Enterprise implementation
❌ Higher entry price than budget hosts
✅ Object Cache Pro included free
❌ Smaller ecosystem than Kinsta or Cloudways
✅ Excellent CWV pass rates
❌ Limited to managed WordPress only
✅ Per-site dedicated CPU
❌ No free trial
**Best for:** WooCommerce stores where 200ms of TTFB difference translates to measurable revenue, especially globally distributed customer bases.
## **5\. Nexcess — Best for WooCommerce-Specific Autoscaling**
[**Nexcess**](https://www.nexcess.net/) is owned by Liquid Web and built specifically for WooCommerce stores. Its key differentiator is automatic vertical scaling during traffic spikes. The platform adds CPU and RAM resources during Black Friday or flash sales without merchant intervention.
[**WooCommerce.com’s official partner directory**](https://woocommerce.com/hosting-solutions/) lists Nexcess as a featured WooCommerce hosting partner. Plans include WooCommerce-specific features like image compression, plugin performance monitoring, and pre-installed sales-boosting plugins.
### **Key Features**
- **Auto-scaling resources:** Add CPU/RAM automatically during traffic spikes
- **WooCommerce pre-installed:** Including sales-boosting plugin bundle
- **No renewal price hikes:** Same price year 1 and year 5
- **Built-in performance testing:** Stress testing tools included
- **30-day money-back guarantee**
### **Pros and Cons**
Pros
Cons
✅ Auto-scaling during traffic spikes
❌ Higher entry price than shared hosting
✅ No renewal price increases
❌ WooCommerce/Magento-only focus is restrictive
✅ WooCommerce-specific stack tuning
❌ Smaller global data center footprint
✅ Owned by Liquid Web (established parent)
❌ Less developer flexibility than Cloudways/xCloud
**Best for:** Seasonal or event-driven stores that experience predictable traffic spikes (Black Friday, product launches, viral marketing campaigns).
## **6\. WP Engine — Best for Agencies and Content-Driven Stores**
[**WP Engine**](https://wpengine.com/) is the established premium managed WordPress host, serving over 200,000 customers globally. Its WooCommerce-specific feature, **Dynamic Plugin Loading**, prevents non-checkout plugins from running on checkout pages, a measurable speed win for stores with 30+ plugins.
[**Omnisend’s hosting analysis**](https://www.omnisend.com/blog/best-woocommerce-hosting/) highlights WP Engine’s strength for agencies: the EverCache layer is configured to handle WooCommerce dynamic pages out of the box, and the Genesis framework (acquired by WP Engine in 2018) is included free on all plans.
### **Key Features**
- **Dynamic Plugin Loading:** Stops unnecessary plugins on checkout pages
- **EverCache:** WooCommerce-aware caching layer
- **Genesis Framework included:** $129+ value
- **Global Edge Security:** Cloudflare-powered
- **24/7 chat + phone support:** Phone available on Premium plan and above
### **Pros and Cons**
Pros
Cons
✅ Mature platform with deep WooCommerce expertise
❌ Some plugins blocked from WordPress.org ecosystem
✅ Dynamic Plugin Loading speeds checkouts
❌ Recent acquisition turbulence (private equity)
✅ Genesis framework free
❌ Higher pricing than xCloud or Cloudways
✅ Multi-site agency tools
❌ Restrictive plugin policies vs. fully open hosting
**Best for:** Agencies managing 10+ client WooCommerce sites that benefit from centralized billing, white-label tools, and Genesis framework integration.
## **7\. SiteGround — Best for Beginner-Friendly WooCommerce Setup**
[**SiteGround**](https://www.siteground.com/) runs on Google Cloud Platform with WordPress + WooCommerce pre-installed, in-house SuperCacher technology, and 24/7 phone, chat, and ticket support. [**WPBeginner’s testing**](https://www.wpbeginner.com/best-woocommerce-hosting/) consistently ranks SiteGround as a top pick for beginners due to its straightforward dashboard and migration tools.
The catch: introductory pricing of $2.99–$12/month renews at 5–6× the original rate after the first term. Factor renewal cost into year-2 budgets.
### **Key Features**
- **Google Cloud Platform infrastructure**
- **In-house SuperCacher:** Three-layer caching system
- **24/7 phone support:** Available on all plans
- **Free CDN, SSL, and email:** Included on all paid plans
- **Auto WordPress + WooCommerce updates**
### **Pros and Cons**
Pros
Cons
✅ True 24/7 phone support (rare in shared hosting)
❌ Renewal pricing 5–6× introductory rate
✅ Easy WooCommerce setup for beginners
❌ Resource limits hit faster than VPS-based hosts
✅ Google Cloud infrastructure
❌ Limited PHP workers on entry plans
✅ Free CDN and SSL
❌ No staging on Startup plan
**Best for:** First-time WooCommerce store owners who want hand-holding support and don’t mind year-2 price increases.
## **8\. Hostinger — Best Budget Option for New WooCommerce Stores**
[**Hostinger**](https://www.hostinger.com/) has WooCommerce-optimized shared hosting starting at $2.69/month with WordPress + WooCommerce pre-installed, integrated payment gateways, free SSL, free domain, and a built-in WordPress AI assistant. [**Cybernews ranked Hostinger #1 for WooCommerce in their April 2026 review**](https://cybernews.com/best-web-hosting/woocommerce-hosting/) based on 63 hosts tested over three months.
The trade-off mirrors SiteGround: introductory pricing is dramatically lower than renewal pricing. Stores with serious revenue ambitions will outgrow Hostinger’s shared hosting within 12–18 months and need to migrate.
### **Key Features**
- **WooCommerce pre-installed:** One-click setup
- **Free domain + SSL:** Included on Premium and Business plans
- **AI assistant:** For product descriptions and content
- **24/7 chat support**
- **30-day money-back guarantee**
### **Pros and Cons**
Pros
Cons
✅ Cheapest entry point ($2.69/month)
❌ Significant renewal price increase
✅ WooCommerce-optimized shared hosting
❌ Performance ceiling hit at ~10K monthly visits
✅ Free domain and SSL
❌ Migration path off Hostinger requires effort
✅ AI tools included
❌ Less PHP worker headroom than VPS-based hosts
**Best for:** Brand-new stores validating product-market fit on a tight budget, side-project WooCommerce stores, and dropshipping experiments.
## **9\. Liquid Web — Best for Heavy-Plugin WooCommerce Builds**
[**Liquid Web’s**](https://www.liquidweb.com/) Managed WooCommerce hosting (also marketed as Nexcess Spark) is built on cloud VPS infrastructure with dedicated resources per account. [**HostingAdvice’s testing**](https://www.hostingadvice.com/best/woocommerce-hosting/) highlights Liquid Web’s strength for complex stores running 30+ plugins, where shared hosting collapses.
The pricing starts at $25/month for the Spark plan, with no renewal increases. Liquid Web also has managed VPS plans for stores that have outgrown standard managed hosting.
### **Key Features**
- **Dedicated VPS resources**
- **No renewal price hikes**
- **Built-in performance testing**
- **WooCommerce-specific staging**
- **24/7 phone support:** Included on all plans
### **Pros and Cons**
Pros
Cons
✅ Dedicated VPS resources at managed-host prices
❌ Smaller data center network than Kinsta/Cloudways
✅ No renewal pricing trickery
❌ Less developer-friendly than xCloud/Cloudways
✅ Phone support on all plans
❌ Migration tool less polished than Kinsta’s
✅ Heavy-plugin tolerance
❌ Older dashboard UX
**Best for:** Established WooCommerce stores running 30+ plugins, custom-built themes, and complex integrations that need dedicated resources without enterprise-tier prices.
## **Performance Benchmark Comparison**
Provider
Avg LCP (mobile)
Avg TTFB
CWV Pass Rate
PHP Workers Entry
**xCloud** (4GB Vultr HF)
1.6s
180ms
75%
Configurable
**Kinsta** (Business 1)
1.7s
220ms
78%
4
**Cloudways** (4GB DO)
1.9s
250ms
65%
Configurable
**Rocket.net** (Starter)
1.5s
160ms
80%
Dedicated
**Nexcess** (Spark)
2.0s
280ms
62%
4
**WP Engine** (Professional)
2.1s
300ms
60%
4
**SiteGround** (GrowBig)
2.0s
320ms
55%
Limited
**Hostinger** (Business)
2.2s
380ms
50%
Limited
**Liquid Web** (Spark)
1.9s
240ms
65%
4
_Data aggregated from [**Online Media Masters**](https://onlinemediamasters.com/), [**PageSpeed Matters**](https://www.pagespeedmatters.com/), and [**Managed WP Guide**](https://managedwpguide.com/) benchmarks during Q1 2026, run on identical sample WooCommerce stores with 50 products._
## **Cost Breakdown: True Year-1 vs Year-2 WooCommerce Hosting Cost**
Provider
Year 1 (12 mo.)
Year 2 (12 mo.)
2-Year Total
Renewal Markup
**xCloud** (BYOS, $5 panel + $24 Vultr HF)
$348
$348
$696
0%
**Kinsta** (Business 1)
$1,380
$1,380
$2,760
0%
**Cloudways** (4GB DO)
$552
$552
$1,104
0%
**Rocket.net** (Starter)
$360
$360
$720
0%
**Nexcess** (Spark)
$252
$252
$504
0%
**WP Engine** (Pro)
$300
$300
$600
0%
**SiteGround** (GrowBig)
$96\*
$588
$684
~6×
**Hostinger** (Business)
$48\*
$191
$239
~4×
**Liquid Web** (Spark)
$300
$300
$600
0%
_SiteGround and Hostinger introductory pricing only applies on annual prepay. Monthly billing is significantly higher._
## **Feature Comparison Matrix**
Feature
xCloud
Kinsta
Cloudways
Rocket.net
Nexcess
WP Engine
SiteGround
Hostinger
Liquid Web
Free SSL
✅
✅
✅
✅
✅
✅
✅
✅
✅
Redis Caching
✅
✅
✅
✅
✅
✅
❌
❌
✅
Object Cache Pro
Add-on
✅
4GB+
✅
✅
✅
❌
❌
✅
Cloudflare
Integration
✅
$4.99/site
✅
❌
✅
❌
❌
❌
Full Root SSH
✅
❌
❌
❌
❌
❌
❌
❌
✅
Free Migration
✅
✅
1 site
✅
✅
✅
✅
✅
✅
24/7 Phone Support
❌
❌
$100/mo
❌
✅
✅
✅
❌
✅
WooCommerce Auto-Scaling
❌
❌
Manual
❌
✅
❌
❌
❌
❌
Free Tier Available
✅
❌
3-day
❌
❌
❌
❌
❌
❌
OpenLiteSpeed Support
✅
❌
❌
❌
❌
❌
❌
❌
❌
## **Audience Mapping: Which WooCommerce Hosting is Best for You?**
Your Situation
Best Choice
Expected Outcome
Brand-new store, validating idea, $0 ad budget
**Hostinger Business**
Lowest year-1 cost, easy setup
Growing store, $1K–$10K monthly revenue
**xCloud (BYOS Vultr HF)**
Best price-to-performance ratio
Established store, $10K–$100K monthly revenue
**xCloud Pro / Cloudways / Nexcess**
Reliable performance at sustainable cost
Enterprise store, $100K+ monthly revenue
**Kinsta Business 2 / Rocket.net**
Premium infrastructure, zero infra decisions
Agency managing 5–20 client stores
**xCloud (white-label)**
Centralized control + agency margins
Seasonal store with predictable traffic spikes
**Nexcess**
Auto-scaling during peaks
WooCommerce store with 30+ plugins
**Liquid Web**
Dedicated resources for plugin overhead
Existing Cloudways user feeling priced out
**xCloud**
~40% lower cost at equivalent specs
## **Common Mistakes WooCommerce Store Owners Make with Hosting**
These mistakes cost stores more revenue than the hosting decision itself:
1. **Picking shared hosting for a real store.** Once you have 50+ products and 1,000+ monthly visits, shared hosting becomes the bottleneck on conversions. The $5/month savings vs. a $25/month VPS is dwarfed by lost sales from slow checkout.
2. **Ignoring renewal prices.** A “$2.99/month” host that renews at $14.99/month costs more in year 2 than a $5/month xCloud + $24/month Vultr server combination.
3. **Underprovisioning PHP workers.** 2 PHP workers can handle a few concurrent shoppers but will time out during a flash sale. WooCommerce stores need 4+ PHP workers minimum during peak shopping times.
4. **Skipping object caching.** Without Redis or Memcached, WooCommerce hits the database hundreds of times per page load. Object caching cuts that by 20–60% [**(per WooCommerce statistics from Marketing LTB)**](https://marketingltb.com/blog/statistics/woocommerce-statistics/).
5. **Caching cart/checkout pages incorrectly.** Generic caching plugins will serve another customer’s cart to the wrong shopper. Use WooCommerce-aware caching (built into Kinsta, Cloudways, and xCloud by default).
6. **Hosting checkout in the wrong region.** Server location affects TTFB by 200–500ms. Pick a data center close to where your highest-spending customers live, not where you live.
## **Frequently Asked Questions About Best Hosting for WooCommerce**
### **What is the best hosting for WooCommerce in 2026?**
The best hosting depends on store size and budget. For cost-efficient managed hosting with full control, [**xCloud**](/) is the strongest pick at ~40% lower cost than Cloudways per [**Online Media Masters**](https://onlinemediamasters.com/xcloud-review/). For premium hands-off hosting, Kinsta’s Business 1 ($115/month) is the threshold for serious WooCommerce stores. For the absolute cheapest entry, Hostinger starts at $2.69/month.
### **How much does WooCommerce hosting cost in 2026?**
WooCommerce hosting in 2026 ranges from $2.69/month (Hostinger shared) to $115+/month (Kinsta Business 1, recommended for WooCommerce). [**Swell’s WooCommerce pricing analysis**](https://www.swell.is/content/woocommerce-pricing) puts most growing stores in the $11–$40/month range with cloud-managed providers. Factor in renewal pricing, since SiteGround and Hostinger renew at 4–6× their introductory rates.
### **Can I run WooCommerce on shared hosting?**
You can technically run WooCommerce on shared hosting, but performance suffers once you exceed 1,000 monthly visits or 50 products. Shared hosting plans rarely include enough PHP workers (typically 1–2) to handle concurrent checkouts. For stores generating any meaningful revenue, VPS or managed cloud hosting starting at around $15–$25/month delivers measurably better conversion rates.
### **Why does WooCommerce need special hosting?**
WooCommerce makes hundreds of database calls per page load and runs uncacheable cart/checkout pages that need PHP workers and object caching. Generic shared hosting that handles a brochure site fine will cause checkout timeouts during sales. WooCommerce-specific hosting includes Redis object caching, full-page cache rules that exclude cart/checkout, and PHP workers tuned for concurrent shoppers.
### **Which WooCommerce hosting is the fastest?**
Based on aggregated independent benchmarks, Rocket.net (1.5s avg LCP), [**xCloud**](/) on Vultr High Frequency (1.6s avg LCP), and Kinsta on Business 1+ (1.7s avg LCP) deliver the fastest WooCommerce performance. Speed depends as much on configuration (Redis, image optimization, theme choice) as on the host itself, but premium infrastructure provides a higher ceiling.
### **Is xCloud better than Cloudways for WooCommerce?**
For most WooCommerce stores, [**xCloud**](/) provides better value than Cloudways. [**Online Media Masters’ independent review**](https://onlinemediamasters.com/xcloud-review/) measured around 40% cost savings on identical Vultr High Frequency hardware, with xCloud’s lighter tech stack producing faster page loads. xCloud also has full root SSH access (Cloudways does not), OpenLiteSpeed support, and a free tier. The detailed [**xCloud vs Cloudways comparison**](/xcloud-vs-cloudways/) breaks down feature-by-feature differences.
### **How many PHP workers does WooCommerce need?**
Small WooCommerce stores (under 100 monthly orders) can run on 2 PHP workers. Growing stores need 4 PHP workers minimum to avoid timeouts during concurrent checkouts. High-traffic stores (5,000+ monthly orders or flash sales) should use 6–8 PHP workers. This is why [**Kinsta recommends Business 1 ($115/month)**](https://kinsta.com/pricing/), since it’s the first plan with 4 workers.
### **What is BYOS (Bring Your Own Serve**r) hosting?
BYOS hosting lets you connect your own cloud server (Vultr, DigitalOcean, AWS, Google Cloud, Linode, Hetzner) to a managed control panel. You pay the cloud provider directly at retail prices and pay the panel a small monthly fee for management features. [**xCloud**](/) pioneered this model for WooCommerce, charging $5/month for unlimited sites + control panel features regardless of which cloud provider you use underneath.
### **Do I need a CDN for WooCommerce?**
Yes. A CDN reduces image and asset load times by serving them from servers close to your customers. Cloudflare’s free plan handles most stores; Cloudflare Enterprise (included with Kinsta and Rocket.net) adds Argo Smart Routing for around 30% additional speed gains. [**Hostinger’s CDN**](https://www.hostinger.com/) is included on Business plans and above.
### **How long does it take to migrate a WooCommerce store to a new host?**
Most WooCommerce migrations complete in 1–4 hours of active work plus 24–48 hours for DNS propagation. xCloud, Kinsta, WP Engine, and Liquid Web all have free migration assistance. For self-service migrations, plugins like Migrate Guru or All-in-One WP Migration handle most stores under 5GB. Test the migrated store on a staging URL before pointing DNS.
### **Should I host WooCommerce on AWS or Google Cloud directly?**
Direct AWS/Google Cloud hosting is the cheapest option but requires you to handle server provisioning, security patches, scaling, backups, and WooCommerce-specific caching configuration yourself. Most store owners get better value from a managed control panel ([**xCloud**](/) at $5/month) on top of AWS or Google Cloud, paying retail cloud pricing while getting managed features.
### **What is the most underrated WooCommerce hosting option?**
[**xCloud’s BYOS model**](/best-cloudways-alternatives/) remains underrated because it requires understanding the “control panel + cloud provider” category. Most comparison articles focus only on traditional managed hosts, missing the 60–80% cost savings possible by connecting your own cloud infrastructure while keeping managed WordPress features. For stores willing to learn the model, the savings compound over years.
## **Your 2026 WooCommerce Hosting Decision**
The hosting market has shifted significantly since DigitalOcean acquired Cloudways in 2022. Pricing has gone up, support quality has dropped, and a new generation of lighter, cheaper alternatives, including [**xCloud**](/), Rocket.net, and modern Nexcess plans, now match or exceed Cloudways’ performance at lower cost.
### **Expert Picks by Goal**
Your Goal
Best Choice
Expected Impact
Best Overall Value
**xCloud**
~40% lower cost vs. Cloudways at equivalent performance
Best for Beginners
**Hostinger**
Lowest entry price + WooCommerce pre-installed
Best for Growing Stores
**xCloud (BYOS Vultr HF)**
Sub-2s LCP at $29/mo total
Best for Enterprise
**Kinsta Business 2+**
Google Cloud C3D + Cloudflare Enterprise
Best for Speed Obsession
**Rocket.net**
Cloudflare Enterprise + Object Cache Pro free
Best for Black Friday
**Nexcess**
Auto-scaling during traffic spikes
Best for Agencies
**xCloud (white-label)**
Centralized billing + agency margins
Best for Heavy-Plugin Stores
**Liquid Web**
Dedicated VPS resources
The data-backed action plan:
- **Get started:** Sign up for [**xCloud’s free tier**](/) (1 server + 10 sites)
- **Test first:** Connect a $24/month Vultr High Frequency server and migrate one site
- **Measure baseline:** Run PageSpeed Insights on your current host before switching
- **Compare results:** Re-measure 14 days after migration on xCloud
- **Scale up:** If results meet expectations, migrate the rest of your sites
- **Upgrade if needed:** For fully hands-off enterprise hosting, Kinsta Business 1 ($115/month) is the next step
Whichever host you choose, measure baseline TTFB, LCP, and CWV pass rate before migrating, then re-measure 14 days after. Lock in the host that produces measurable speed gains. Anything else is a guess.
👉 [**Get started with xCloud**](/) — Manage 1 server, 10 sites for Free.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and take part in discussions.
---
# Best Laravel Hosting for Developers: What Developers Should Know Before Choosing a Hosting Provider? - xCloud
> Learn about the best Laravel hosting for developers and how xCloud makes Laravel hosting effortless with powerful features.
[Laravel](/laravel-hosting/) has quickly established itself as one of the most popular PHP frameworks for web application development. Developers admire its elegant syntax, powerful features, and strong community support. As Laravel continues to lead in backend development, the demand for optimized, tailored hosting solutions grows significantly.
xCloud Hosting has met this demand by launching a fully optimized, managed Laravel hosting solution that surpasses the limitations of basic shared hosting. With advanced tools like Supervisor, Laravel Horizon, Queue Workers, and other performance-driven features, xCloud enables developers to deploy and manage Laravel applications with greater efficiency and control.
Let us learn about the best Laravel Hosting for developers and how to [**deploy Laravel projects**](/docs/deploy-laravel-applications/) with xCloud, and what makes xCloud stand out in a competitive landscape.
## **Powerful Built-In Laravel Features with xCloud for Seamless Management**
When you seek Laravel hosting optimized for performance and developer control, the real advantage lies in the features. xCloud Laravel hosting does not simply support Laravel—it enhances your application with integrated tools that many hosting providers overlook.
### **✔️ Supervisor: Automatically Restarts Background Processes**
Laravel developers frequently depend on long-running queue workers to handle tasks such as email dispatching, payment processing, and image conversion. When a worker crashes, Supervisor ensures background processes restart automatically. It runs your queue workers as persistent processes, removing the need for manual restarts after server crashes or reboots.
In essence, your Laravel queue system becomes highly reliable and nearly fail-proof.
### **✔️ Laravel Horizon: Simplifies Real-Time Queue Monitoring**
Laravel Horizon serves as the official dashboard for managing Laravel queues. It offers insights into queue metrics such as job throughput, failure rates, and processing times. On many shared hosts, setting up Horizon can be complex and time-consuming, requiring manual configuration of Redis and terminal commands.
xCloud simplifies this by allowing you to manage Horizon directly from its dashboard.
### **✔️ Queue Workers: Production-Ready from the Start**
Queue workers power asynchronous tasks like processing orders, sending notifications, and managing cron jobs. xCloud provides robust support for these workers, eliminating the need to access your server via SSH to modify settings or restart processes.
With Horizon and Supervisor included, your queue workers function reliably from day one.
### **✔️ CI/CD Integration: Professional Deployment Workflow**
Deployments often introduce complications. xCloud streamlines this process through CI/CD integration for Laravel projects. You can:
- Push code to GitHub, GitLab, or Bitbucket to trigger automatic deployments
- Run migrations, seeders, or other Artisan commands after deployment
- Roll back to previous versions when needed
Each deployment keeps your queue workers and Supervisor processes running without interruption.
### **✔️ Application Environments for Full Lifecycle Control**
xCloud provides separate environments for Local, Staging, and Production, each with its own configuration. This setup allows you to test new features safely without risking downtime in your production environment.
## **How to Get Started with Laravel Hosting on xCloud**
Getting started with **xCloud Laravel hosting** is much simple — especially when compared to traditional providers, where you spend hours on server setup, deployment process, ci/cd and all. With xCloud, every tool you need to launch and scale a production-ready Laravel app is ready out of the box.
Follow this step-by-step guide to launch your project on the **best Laravel hosting, optimized** for performance, scalability, and ease of use.
### **Step 1: Create and Configure Your Site**
To get started, log in to your xCloud dashboard and click on **+New Site**. Choose your preferred server and proceed to the **Laravel** tab. Select **Clone a Git Repository** to deploy your Laravel application. Next, set your **Site Title** and choose a domain. You can opt for a **Demo Site** to test and refine your app, or select **Migrate into a New Domain** for a live deployment. Once your domain settings are configured, click **Next** to continue.
### **Step 2: Set Up Environment**
In the settings section, choose your **PHP version**, define the **Site User**, and specify the **Web Root** directory. When it comes to the database, you have three options: create a new database on the server, connect to an existing one, or skip database setup if not needed. If you choose to create a new database, fill in the database name, username, and password—or use the auto-generated credentials. After setting up your environment and database, proceed to the next step.
### **Step 3: Connect Git & Automate Deployment**
In the **Git Repo** section, enter your repository URL and branch. Enable the **Push to Deploy** feature to generate a **Deployment URL**, which allows for continuous deployment. To automate this, you can optionally add the Deployment URL as a **Webhook** in your Git hosting service (like GitHub). Simply go to the repo’s **Settings**, select **Webhooks**, and paste the URL under **Payload URL**, using application/json as the content type.
_Note: The ‘Deployment URL’ step is not a mandatory step. You can skip this process if you want._
### **Step 4: Finalize Deployment Setup**
Now, specify any commands needed after deployment in the **Deploy Script** section. This could include installing dependencies or running migrations, such as:
```
php8.1 $(which composer) install --no-interaction --prefer-dist --optimize-autoloader --no-dev
php8.1 artisan migrate --force
php8.1 artisan optimize:clear
npm install –-quite
npm run build
```
Copy to Clipboard
**_Note:_** _We can use PHP version 8.3 or 8.4 as well._
Also, copy the **Public Key** from xCloud and add it to your Git repository as a **Deploy Key**. This allows xCloud to securely access and clone your repository via SSH.
### **Step 5: Deploy**
After everything is configured, click **Start** to begin the deployment process. xCloud will handle the migration and setup. Once complete, you will be taken to your site’s dashboard. From there, you can manage your Laravel **Application** and **Environment** settings as needed.
For more details, check out the guide on how to [**deploy Laravel applications with xCloud**](/docs/deploy-laravel-applications/).
## **💡 Why xCloud Excels at the Best Laravel Hosting for Developers**
In a market full of general-purpose cloud hosting providers and Laravel-compatible platforms, **xCloud Laravel Hosting** distinguishes itself as the only solution purpose-built for the Laravel ecosystem. xCloud does not simply support Laravel—it fully understands it. Every component is designed to meet Laravel’s most critical production requirements. From its integrated command runner to easy queue worker management, scheduler, and simplified Horizon control, xCloud removes the need for manual configuration and technical overhead.
### **Effortless Queues and Jobs Management**
Most platforms place the responsibility of setting up queues and installing Supervisor on the developer. xCloud takes a different approach. It includes a built-in Supervisor management panel, so you can manage your queue workers directly from the dashboard—no need to dive into the terminal or wrestle with SSH configurations.
Although Horizon does not come pre-configured, xCloud streamlines worker management, reducing your setup time and allowing you to focus on what matters most—building your application.
### **Optimized for Queues and Background Jobs**
xCloud removes the need for DevOps support, which gives startups and solo developers a significant advantage. It delivers a truly managed Laravel hosting experience with:
- **Real-time queue monitoring**
- **Auto-scaling queue workers based on traffic**
- **Redis tuned for optimal performance**
- **Fault-tolerant Supervisor processes that restart automatically**
You never need to log into a terminal to restart services or troubleshoot failures. In comparison, other platforms may offer Laravel support, but they require you to handle Redis tuning, Supervisor setup, and other critical configurations yourself. This not only increases the risk of errors but also delays project delivery. xCloud removes these hurdles by handling it all for you.
### **Horizon Integration Built for Teams**
xCloud provides a collaborative hosting environment that benefits agencies and development teams managing multiple Laravel projects. With centralized dashboards, project isolation, and version-controlled Git-based deployments, you can manage your Laravel applications seamlessly
These features make xCloud ideal for maintaining client work or adapting to fast-moving product updates.
### **Start Deploying Your Laravel Applications with xCloud**
Laravel has grown far beyond a simple PHP framework. If your application depends on Laravel, then xCloud Laravel Hosting is the environment it deserves. With powerful built-in features that most providers do not offer, xCloud ensures developers spend less time managing infrastructure and more time creating exceptional applications.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# 10 Best Managed Hosting For WordPress in 2026: Expert-Tested for Speed & Security (Complete Guide) - xCloud
> Looking for the best managed hosting for WordPress in 2026? Compare top providers for speed, security, pricing, and scalability in one guide.
Choosing the right managed hosting for WordPress can directly impact your site’s speed, security, and long-term scalability. With WordPress now powering over **[43% of all websites worldwide](https://wordpress.com/blog/2025/04/17/wordpress-market-share/)** (W3Techs), competition for fast, reliable hosting has never been more intense.
In 2026, performance research and industry benchmarks consistently show that **managed hosting for WordPress outperforms [traditional shared hosting](/cloud-hosting-or-traditional/) by 2–3× in load speed**, while also reducing maintenance overhead and security risk.
Let us explore the **10 best [managed hosting for WordPress](/managed-hosting/)**, ranked using real-world performance testing, verified user reviews, and recommendations from experienced WordPress professionals.
## Table of Contents
## **Quick Summary / TL;DR**
[**Managed hosting for WordPress**](/hosting-for-wordpress/) consistently delivers faster load times, stronger security, and less hands-on maintenance than shared hosting.
If you’re running a business site, agency portfolio, or high-traffic blog in 2026, managed hosting is no longer optiona,l it is a performance baseline. The right provider depends on your needs and values brings each provider. Let us see what you need to know:
**If You Want To…**
**Use This**
**Expected Impact**
**Monthly Cost**
**Maximum flexibility with unlimited sites**
xCloud
40% cost savings vs competitors
$5-$395
**Premium enterprise-grade hosting**
Kinsta
99.99% uptime, Google Cloud
$30-$1,650
**Budget-friendly managed hosting**
Hostinger
Fast setup, beginner friendly
$2.99-$6.99
**WordPress-recommended hosting**
SiteGround
Superior support, Google Cloud
$2.99-$7.99
**Agency-level performance**
WP Engine
1.5M+ sites, enterprise security
$20-$600
**Developer-first cloud control**
Cloudways
Multi-cloud flexibility
$11-$400+
**Value-focused performance**
Bluehost
WordPress.org recommended
$2.99-$13.99
**Speed-optimized hosting**
Rocket.net
Enterprise CDN built-in
$25-$80
**Scalable cloud hosting**
Nexcess
Autoscaling, WooCommerce focus
$19-$999
**High-traffic sites**
Pressable
Automattic-owned, WP Cloud
$25-$500
Expert Recommendation: Industry reviewers from WPBeginner, HostingStep, and Blog Marketing Academy recommend starting with xCloud for cost-conscious users who want cloud-level performance (delivering 40% savings compared to Cloudways, according to OnlineMediaMasters).
- **Best for Beginners:** Hostinger – Lowest entry price with managed features and an intuitive interface.
- **Best for Agencies:** xCloud – Unlimited sites, white-label options, and bring-your-own-server flexibility.
- **Best for Enterprise:** Kinsta – Google Cloud Platform with 99.99% uptime guarantee
## **Why Managed Hosting For WordPress Matters in 2026**
Website performance is no longer a technical concern, it is a revenue driver. Research from the Baymard Institute shows that **nearly 70% of shopping carts are abandoned on slow-loading websites**, making speed and reliability critical for any WordPress site with commercial goals.
Managed hosting for WordPress is designed to eliminate the most common performance and security bottlenecks by handling the heavy lifting at the server and platform level:
- **Automatic updates** – Core, plugin, and theme updates are handled proactively to reduce compatibility issues and vulnerabilities
- **Security monitoring** – Continuous malware scanning, firewalls, and intrusion prevention protect sites before issues escalate
- **Performance optimization** – Server-level caching, CDN integration, and database tuning deliver faster load times without manual configuration
- **Expert WordPress support** – Access to technicians who specialize in WordPress-specific issues, not generic hosting problems
- **Daily backups** – Automated backups with one-click restore minimize downtime and data loss risk
Beyond convenience, managed hosting for WordPress delivers measurable risk reduction. **Forrester Research reports that businesses using managed hosting environments experience up to 60% fewer security incidents** compared to [**self-managed hosting**](/self-managed-hosting/) setups.
## **How We Ranked These Hosting Providers**
Our rankings are based on a structured evaluation framework aligned with the methodologies used by leading WordPress industry reviewers such as HostingStep, WPBeginner, and IsItWP.
Each provider was assessed across performance, value, scalability, support quality, security features, developer tools, and verified user feedback to ensure rankings reflect real-world use, not marketing claims.
**Criteria**
**Why It Matters**
**Weight**
**Performance**
Page load times, uptime, and server response
High
**Value**
Features per dollar, transparent pricing
High
**Scalability**
Ability to handle traffic spikes, growth options
High
**Support**
Response time, WordPress expertise, availability
Medium
**Security**
SSL, firewall, malware protection, backups
Medium
**Developer Tools**
Staging, Git, SSH, CLI access
Medium
**User Reviews**
Trustpilot, G2, community feedback
Medium
## **Comparison: Key Overview Of Top Managed Hosting For WordPress At a Glance**
This table provides a side-by-side comparison of the leading managed hosting for WordPress in 2026, highlighting pricing, site limits, and ideal use cases.
Use it to quickly identify which host best matches your budget, technical needs, and growth plans.
**Rank**
**Provider**
**Rating**
**Starting Price**
**Sites Allowed**
**Best For**
🥇 1
xCloud
★★★★★
$5/mo
Unlimited
Agencies & developers wanting cloud control
🥈 2
Kinsta
★★★★★
$30/mo
1-150+
Enterprise sites needing premium performance
🥉 3
Hostinger
★★★★★
$2.99/mo
1-300
Budget-conscious beginners
4
SiteGround
★★★★☆
$2.99/mo
1-unlimited
WordPress.org recommended hosting
5
WP Engine
★★★★☆
$20/mo
1-30+
Agencies needing enterprise reliability
6
Cloudways
★★★★☆
$11/mo
Unlimited
Multi-cloud flexibility seekers
7
Bluehost
★★★★☆
$2.99/mo
1-unlimited
First-time WordPress users
8
Rocket.net
★★★★☆
$25/mo
1-unlimited
Speed-obsessed site owners
9
Nexcess
★★★★☆
$19/mo
1-250
WooCommerce and high-traffic sites
10
Pressable
★★★★☆
$25/mo
1-50+
Automattic ecosystem users
## **🥇 1. xCloud – Best for Unlimited Sites & Cost Efficiency**
**[xCloud](/)** has emerged as one of the most compelling managed WordPress platforms for agencies and developers, combining cloud-level performance with pricing that undercuts most traditional managed hosting. Independent reviewers at OnlineMediaMasters and Blog Marketing Academy highlight xCloud for delivering **up to [40% lower costs](https://xcloud.host/case-studies/wattz-web-design/)** than comparable platforms, without sacrificing speed or control.
The platform currently manages **100,000+ websites across 10,000+ servers worldwide** and maintains a **4.9/5 Trustpilot rating** based on 287+ verified reviews. Its appeal lies in offering advanced cloud features—such as bring-your-own-server flexibility and full Cloudflare integration through a lightweight, performance-focused control panel.
As David Risley of Blog Marketing Academy notes:
> “Every site I moved was noticeably faster on xCloud than it was on Cloudways. This was a direct apples-to-apples comparison, and xCloud was simply faster.”
### **Key Features**
- **Unlimited WordPress sites** – No artificial site limits on any plan
- **Bring Your Own Server (BYOS)** – Connect Vultr, DigitalOcean, AWS, Google Cloud, Hetzner, or Linode
- **One-click deployments** – WordPress, n8n, Node.js, Laravel, PHP apps, and LLM workloads
- **Full Cloudflare integration** – CDN, DNS management, and edge caching included
- **White-label reseller platform** – Create and brand your own hosting service
- **Free SSL certificates** – Let’s Encrypt with automatic renewal
- **NGINX FastCGI caching** – Server-level full-page caching for faster delivery
- **Redis object caching** – Built-in database query optimization
- **Staging environments** – One-click staging with push-to-production
- **Automated backups** – Local and remote backups (Google Drive, Amazon S3)
- **Team collaboration** – Role-based access for agencies and teams
- **WordPress Updates Manager** – Centralized core, plugin, and theme updates
- **Site Security PRO** – Patchstack-powered vulnerability protection ($2/site)
- **30+ global data centers** – Deploy servers close to your audience
### **Pros and Cons**
#### **Pros**
✅ 40% cheaper than Cloudways for the same specs
✅ Unlimited sites on all plans
✅ Lightweight panel = better performance
✅ Full Cloudflare + Redis integration
✅ 4.9/5 Trustpilot rating
✅ Free tier available (1 server, 10 sites)
✅ Lifetime deal option available
#### **Cons**
❌ Learning curve for BYOS setup
❌ Newer platform (launched 2024)
❌ Support relies heavily on documentation
❌ Email hosting requires add-on
### **Best for:**
Agencies managing multiple client sites, developers who want cloud-level control without server maintenance, and cost-conscious teams [migrating from shared hosting](/migrate-wordpress-from-shared-hosting-to-cloud-server/) or Cloudways who need unlimited sites without enterprise pricing.
## **🥈 2. Kinsta – Best for Premium Enterprise Performance**
Kinsta is widely regarded as a top-tier managed hosting for WordPress, built exclusively on **Google Cloud Platform** using C2 compute-optimized virtual machines. This infrastructure-first approach has consistently placed Kinsta among the fastest WordPress hosts in independent performance benchmarks.
With **35+ global data centers** and edge caching delivered through **260+ CDN points of presence**, [**Kinsta**](https://hostinginfo.online/kinsta-review/) is engineered for low latency, high availability, and predictable performance at scale. All plans are backed by a **99.99% uptime SLA**, making it a common choice for mission-critical and high-traffic WordPress deployments.
### **Key Features**
- **Google Cloud C2 infrastructure** – Compute-optimized virtual machines on every plan
- **35+ data centers worldwide** – Reduced latency for global audiences
- **MyKinsta dashboard** – Award-winning, developer-friendly control panel
- **DevKinsta** – Free local WordPress development environment
- **Built-in Application Performance Monitoring (APM)** – No additional cost
- **Free expert migrations** – Hands-off site transfers handled by Kinsta’s team
- **Daily backups** – 14–30 day retention depending on plan tier
- **Free malware cleanup** – Included if your site is compromised
Best for: High-traffic business sites, enterprise WordPress deployments, and developers who prioritize performance over cost and need Google Cloud’s infrastructure.
## 🥉 **3. Hostinger – Best Budget-Friendly Option For Managed Hosting For WordPress**
Hostinger has emerged as the value leader in managed hosting for WordPress, trusted by over 2.5 million customers worldwide (according to Hostinger). With plans starting at $2.99/month and LiteSpeed-powered servers, it delivers managed features at [**shared hosting**](/shared-hosting-vps-or-cloud-hosting/) prices.
WordPress.org officially recommends Hostinger for its combination of performance, features, and affordability.
### **Key Features**
- **LiteSpeed Cache:** Server-level caching for WordPress optimization
- **100-300 websites:** Depending on plan tier
- **Free domain:** Included for the first year
- **Weekly/Daily backups:** Automatic protection
- **Managed WordPress:** Automatic updates and security
- **AI Website Builder:** Quick site creation for beginners
- **Global CDN:** Built-in content delivery network
- **Free SSL Certificates:** Let’s Encrypt certificates included
### Pros and Cons
#### **Pros**
✅ Lowest entry price ($2.99/mo)
✅ LiteSpeed cache performance
✅ Free domain and SSL
✅ WordPress.org recommended
✅ AI website builder included
#### **Cons**
❌ Renewal prices significantly higher
❌ Support quality varies
❌ Limited storage on basic plans
❌ Fewer developer tools than premium hosts
Best for: First-time WordPress users, personal blogs, small business sites, and anyone prioritizing budget while still wanting managed hosting features.
## **4\. SiteGround – Best WordPress.org Recommended Hosting**
[SiteGround](https://hostinginfo.online/siteground-review/) has maintained WordPress.org’s official recommendation since 2004, trusted by owners of 3 million+ domains. Running on Google Cloud infrastructure with proprietary SuperCacher technology, [**SiteGround**](/xcloud-vs-siteground/) consistently ranks among the top performers in independent speed tests.
### Key Features
- **Google Cloud infrastructure:** Enterprise-grade reliability
- **SuperCacher technology:** Proprietary 3-level caching system
- **Daily backups:** Automatic with on-demand options
- **Staging environments:** One-click staging on GrowBig+
- **Free SSL:** Auto-renewed Let’s Encrypt
- **Managed WordPress:** Automatic updates and patches
- **Speed Optimizer plugin:** Free performance plugin
- **24/7 expert support:** Phone, chat, and ticket options
### Pros and Cons
#### **Pros**
✅ Google Cloud infrastructure
✅ Superior customer support
✅ WordPress.org recommended
✅ Free Speed Optimizer plugin
✅ 20+ years hosting experience
#### **Cons**
❌ Renewal prices 3-4x intro price
❌ Storage limits (10-40GB)
❌ Visit caps on each plan
❌ Higher-tier features require GrowBig+
Best for: Users who prioritize customer support quality, WordPress.org endorsement credibility, and Google Cloud’s reliability over raw cost savings.
## **5\. WP Engine – Best Managed for Enterprise Agencies**
WP Engine pioneered managed hosting for WordPress and now powers over 1.5 million websites across 150+ countries. As the only WordPress hosting provider to win the Global Customer Service Department of the Year Stevie Award, WP Engine sets the industry standard for enterprise reliability.
### Key Features
- **EverCache technology:** Proprietary caching for instant page loads
- **Genesis Framework:** Premium theme framework included
- **StudioPress themes:** Premium themes bundled free
- **Global Edge Security:** Cloudflare-powered protection (add-on)
- **60-day backup retention:** Industry-leading backup history
- **Dev, staging, production:** Three environments included
- **24/7 expert support:** WordPress specialists are available always
- **Automated migrations:** Free site transfers included
### Pros and Cons
#### **Pros**
✅ 60-day backup retention
✅ Genesis + StudioPress included
✅ Award-winning support
✅ 1.5M+ sites proven at scale
✅ Three environments per site
#### **Cons**
❌ Premium pricing ($20+/month)
❌ No email hosting
❌ Plugin restrictions (disallowed list)
❌ Limited to WordPress
Best for: Digital agencies, enterprise WordPress deployments, and businesses that value proven reliability and premium support over cost optimization.
## 6\. Cloudways – Best for Multi-Cloud Flexibility
Cloudways offers managed [**cloud hosting**](/what-is-cloud-hosting-and-how-does-it-work/) across five infrastructure providers: DigitalOcean, AWS, Google Cloud, Vultr, and Linode. This flexibility makes it popular among developers who want cloud performance without server management complexity.
### Key Features
- **5 cloud providers:** DigitalOcean, AWS, GCP, Vultr, Linode
- **Pay-as-you-go pricing:** No long-term contracts
- **Managed security:** Firewalls, SSL, and monitoring
- **Staging environments:** One-click staging available
- **24/7 support:** Expert assistance always available
- **Team collaboration:** Multi-user access controls
- **Server cloning:** Duplicate servers instantly
- **Cloudflare integration:** Enterprise CDN add-on
### Pros and Cons
Pros
✅ Multi-cloud provider choice
✅ Pay-as-you-go flexibility
✅ Instant server scaling
✅ 3-day free trial available
✅ 24/7 expert support
#### **Cons**
❌ Markup on cloud provider pricing
❌ Object Cache Pro requires workarounds
❌ No email hosting included
❌ Cloudflare Enterprise limited features
Best for: Developers wanting cloud provider flexibility, users who prefer pay-as-you-go over annual contracts, and those comfortable with slightly technical interfaces.
## 7\. Bluehost – Best for First-Time WordPress Users
Bluehost holds the distinction of being WordPress.org’s longest-running recommended host since 2005. With plans designed specifically for beginners and an AI-powered website builder, Bluehost makes WordPress accessible to everyone.
WPShout’s November 2025 hosting comparison shows Bluehost delivering 0.35s load times in the US – faster than most hosts tested.
### Key Features
- **1-click WordPress install:** Pre-installed and ready
- Free domain: First year included
- Free SSL certificate: Security from day one
- AI site builder: Create sites with AI assistance
- 24/7 WordPress support: Phone and chat available
- LiteSpeed servers: Performance-optimized infrastructure
- Free CDN: Global content delivery included
- Single Sign-On: Access WordPress from Bluehost dashboard
### Pros and Cons
#### **Pros**
✅ WordPress.org recommended since 2005
✅ AI-powered site builder
✅ Free domain first year
✅ Beginner-friendly interface
✅ 30-second support response
#### **Cons**
❌ Renewal prices increase significantly
❌ Basic plans have limited features
❌ Migration plugin for existing sites
❌ Upsells during signup process
Best for: Absolute beginners, first-time website creators, and small businesses wanting WordPress.org-endorsed hosting with minimal technical requirements.
# 8\. Rocket.net – Best for Speed-Obsessed Users
Rocket.net built its entire platform around one goal: delivering the fastest WordPress hosting available. With enterprise-level security configurations and a control panel designed for maximum productivity, Rocket.net appeals to performance-focused site owners.
### Key Features
- **Enterprise CDN:** Full-page caching at the edge
- **WAF protection:** Enterprise-level security included
- **Unlimited bandwidth:** No traffic caps
- **Free migrations:** Expert team handles transfers
- **Daily backups:** Automatic protection
- **Staging sites:** One-click staging environments
- **24/7 support:** Chat support included
- **White-label reseller:** Agency hosting options
### Pros and Cons
#### **Pros**
✅ Enterprise-grade speed
✅ Unlimited bandwidth
✅ Enterprise security included
✅ Free test migrations
✅ White-label reseller options
#### **Cons**
❌ Higher price point ($25+/month)
❌ Fewer data center locations
❌ Newer platform (less track record)
❌ WordPress-only hosting
Best for: Site owners who prioritize raw speed above all else, agencies wanting white-label options, and users willing to pay premium for enterprise-level performance.
## **9\. Nexcess – Best for WooCommerce & High-Traffic Sites**
Nexcess, owned by Liquid Web, specializes in managed WordPress and WooCommerce hosting with automatic scaling capabilities. Their platform intelligently handles traffic spikes without manual intervention.
### Key Features
- **Autoscaling:** Automatic resource allocation for traffic spikes
- **WooCommerce optimized:** Specialized eCommerce hosting
- **Plugin performance monitoring:** Identify slow plugins
- **Visual regression testing:** Catch styling issues before they go live
- **Stencil development:** Local development tools
- **Free migrations:** Expert-assisted transfers
- **Always-on security:** Managed firewalls and monitoring
- **99.99% uptime SLA:** Enterprise-grade reliability
### Pros and Cons
#### **Pros**
✅ Autoscaling for traffic spikes
✅ WooCommerce-optimized
✅ Plugin performance monitoring
✅ Visual regression testing
✅ Liquid Web infrastructure
#### **Cons**
❌ Higher pricing than shared hosts
❌ Interface less intuitive
❌ Fewer global data centers
❌ Primarily US-focused support
Best for: WooCommerce store owners, high-traffic WordPress sites, and businesses expecting significant traffic fluctuations who need automatic scaling.
## 10\. Pressable — Best for Automattic Ecosystem Users
Pressable is owned by Automattic (the company behind WordPress.com and WooCommerce) and runs on the WP Cloud platform. This direct connection to WordPress’s creators provides unique advantages for users invested in the Automattic ecosystem.
### Key Features
- **WP Cloud platform:** Built by WordPress.com’s creators
- **Jetpack included:** Premium Jetpack features bundled
- **24/7 WordPress experts:** Support from WordPress specialists
- **Automatic updates:** Core, themes, and plugins
- **Site activity log:** Full audit trail of changes
- **Free SSL:** Security certificates included
- **Staging sites:** Safe testing environments
- **Free migrations:** Expert-assisted transfers
### Pros and Cons
#### **Pros**
✅ Built by WordPress.com creators
✅ Jetpack Premium included
✅ Direct Automattic support
✅ Site activity logging
✅ WP Cloud infrastructure
#### **Cons**
❌ Limited customization options
❌ Visit-based pricing
❌ Less control than other hosts
❌ Fewer advanced developer tools
Best for: Users already invested in Automattic products (Jetpack, WooCommerce), those wanting WordPress.com-level reliability with self-hosted flexibility.
# Implementation Difficulty Comparison
See how easy or complex it is to get started with each managed hosting provider. Use it to assess required technical skill, setup time, and whether a platform suits beginners, developers, or teams.
Provider
Technical Skill
Setup Time
BYOS Option
Beginner Friendly?
xCloud
Basic-Medium
5-15 mins
✅ Yes
✅ Yes (managed) / ⚠️ (BYOS)
Kinsta
None-Basic
5 mins
❌ No
✅ Yes
Hostinger
None
3 mins
❌ No
✅ Yes
SiteGround
None-Basic
5 mins
❌ No
✅ Yes
WP Engine
None-Basic
5 mins
❌ No
✅ Yes
Cloudways
Basic-Medium
10 mins
✅ Yes
⚠️ Learning curve
Bluehost
None
3 mins
❌ No
✅ Yes
Rocket.net
None-Basic
5 mins
❌ No
✅ Yes
Nexcess
None-Basic
5 mins
❌ No
✅ Yes
Pressable
None
5 mins
❌ No
✅ Yes
## Cost Breakdown: Comparing Price vs Performance Across Hosting Providers
See how managed hosting for WordPress providers stack up on cost at different growth stages.
This table shows where pricing aligns or fails to align with real performance and features.
Provider
Entry Plan
Mid-Tier
High-Tier
Sites Included
Free Tier?
xCloud
$5/mo
$30/mo
$200/mo
Unlimited
✅ Yes
Kinsta
$30/mo
$75/mo
$313/mo
1-3+
❌ No
Hostinger
$2.99/mo
$3.99/mo
$5.99/mo
1-300
❌ No
SiteGround
$2.99/mo
$4.99/mo
$7.99/mo
1-unlimited
❌ No
WP Engine
$20/mo
$49/mo
$115/mo
1-15+
❌ No
Cloudways
$11/mo
$24/mo
$84/mo
Unlimited
❌ No (3-day trial)
Bluehost
$2.99/mo
$5.99/mo
$13.99/mo
1-unlimited
❌ No
Rocket.net
$25/mo
$50/mo
$80/mo
1-25+
❌ No
Nexcess
$19/mo
$49/mo
$149/mo
1-25+
❌ No
Pressable
$25/mo
$45/mo
$90/mo
1-10+
❌ No
## Feature Comparison Matrix
Feature
xCloud
Kinsta
Hostinger
SiteGround
WP Engine
Cloudways
Unlimited Sites
✅
❌
❌
✅ (higher plans)
❌
✅
BYOS Option
✅
❌
❌
❌
❌
✅
Free SSL
✅
✅
✅
✅
✅
✅
Staging
✅
✅
✅
✅
✅
✅
CDN Included
✅
✅
✅
✅
❌
❌
Git Integration
✅
✅
❌
✅
✅
✅
Redis Cache
✅
✅
❌
❌
❌
✅
White-Label
✅
❌
❌
✅
❌
❌
n8n/Node.js
✅
❌
❌
❌
❌
❌
LLM Hosting
✅
❌
❌
❌
❌
❌
Team Management
✅
✅
❌
❌
✅
✅
Free Tier
✅
❌
❌
❌
❌
❌
## Common Mistakes to Avoid
1. Choosing based on intro pricing only – Renewal rates often triple or quadruple. Always check year-2 pricing before committing to long-term contracts.
2. Ignoring site limits – Budget hosts often cap sites at 1-3. If you plan multiple projects, choose unlimited-site providers like xCloud or Cloudways from the start.
3. Overlooking server location – Site speed depends heavily on server proximity to users. Select hosts with data centers near your audience.
4. Skipping staging environments – Making changes directly on live sites causes preventable outages. Always use staging for testing updates.
5. Not testing migrations first – Request test migrations on temporary URLs before committing. This reveals compatibility issues without downtime.
6. Underestimating bandwidth needs – Traffic spikes from viral content or seasonal sales can exceed plan limits, causing overage fees or throttling.
7. Assuming “managed” means fully hands-off – Even managed hosts require attention to plugin updates, content backups, and performance monitoring.
8. Ignoring support quality – 24/7 availability means nothing if support staff can’t solve WordPress-specific problems. Test support before committing.
# Frequently Asked Questions
### 1\. Which managed hosting should beginners start with?
For absolute beginners, Hostinger offers the lowest barrier to entry at $2.99/month with managed features. For those willing to invest slightly more, SiteGround provides superior support that beginners often need.
### 2\. Is managed hosting for WordPress worth the extra cost?
Yes – managed hosting typically costs 2-5x more than shared hosting but delivers measurably faster load times, better security, and time savings on maintenance. Sites with commercial goals (eCommerce, lead generation) see direct ROI from improved performance.
### 3\. Can I host unlimited sites affordably?
xCloud offers unlimited sites on all plans starting at $5/month for managed hosting. The self-managed (BYOS) option allows unlimited sites with just the control panel fee ($5/server/month) plus cloud provider costs.
### How do I migrate my existing WordPress site?
Most managed hosts offer free migrations. Request a test migration first to verify everything transfers correctly before pointing DNS to the new host. xCloud, Kinsta, WP Engine, and Rocket.net all include migration assistance.
### What’s the difference between managed and cloud hosting?
Managed hosting handles WordPress-specific optimization automatically (updates, caching, security). Cloud hosting provides scalable infrastructure but may require manual configuration. xCloud and Cloudways bridge both cloud infrastructures with managed WordPress tools.
### Do managed hosts include email hosting?
Managed hosting handles WordPress-specific optimization automatically (updates, caching, security). Cloud hosting provides scalable infrastructure but may require manual configuration. xCloud and Cloudways bridge both cloud infrastructures with managed WordPress tools.
### Which host handles traffic spikes best?
Nexcess offers true autoscaling that automatically allocates resources during traffic surges. Kinsta’s Google Cloud infrastructure handles spikes well. xCloud allows instant server upgrades or additional server deployment through its cloud provider integrations.
### What security features should I look for?
Essential security features include free SSL certificates, automatic malware scanning, web application firewall (WAF), brute force protection, and isolated site environments. xCloud’s Site Security PRO ($2/site) adds Patchstack vulnerability monitoring.
### Can I switch hosts later without losing my site?
Yes, WordPress sites are portable. All major hosts support migrations. Export your site via plugin (Migrate Guru, All-in-One WP Migration) or request host-assisted migration. Plan 1-2 hours for DNS propagation after switching.
### Which host offers the best developer tools?
xCloud provides the most developer flexibility with SSH access, Git integration, WP-CLI, multiple PHP versions, and support for Node.js, Laravel, and custom applications. Kinsta’s DevKinsta offers excellent local development. WP Engine includes three environments per site.
## **Wrapping Up: Which Managed Hosting For WordPress Is Right for You?**
Selecting the right managed WordPress host depends on your specific priorities: cost optimization, raw performance, developer flexibility, or beginner-friendly simplicity.
### Expert Picks by Goal
Your Goal
Best Choice
Why
Best Overall Value
xCloud
Unlimited sites, 40% cheaper than Cloudways, free tier available
Best for Beginners
Hostinger
$2.99/mo entry, intuitive interface, WordPress.org recommended
Best for Agencies
xCloud
White-label, unlimited sites, team collaboration, BYOS flexibility
Best for Enterprise
Kinsta
Google Cloud C2 VMs, 35 data centers, 99.99% uptime
Best for WooCommerce
Nexcess
Autoscaling, commerce optimization, plugin monitoring
Best Support Quality
SiteGround
20+ years experience, WordPress.org recommended, 24/7 experts
Best Multi-Cloud
Cloudways
5 cloud providers, pay-as-you-go, developer-friendly
Ready to get started? Industry experts recommend beginning with xCloud’s free tier to test cloud-level performance without commitment. Migrate one site first, benchmark the results, then scale as needed.
The hosts that consistently earn expert recommendations share common traits: transparent pricing, WordPress-specific optimization, responsive support, and modern infrastructure. Prioritize these factors over marketing promises, and your WordPress site will perform reliably for years to come.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# 7 Best n8n Hosting Providers in 2026: Complete Comparison Guide for Workflow Automation - xCloud
> Compare the 7 best n8n hosting provider in 2026. See pricing, performance, and expert picks for fast workflow automation provider.
The workflow automation market reached **$23.77 billio**n in 2025 and continues expanding at **9.52%** annually, according to Mordor Intelligence. As businesses adopt n8n – the open-source automation platform with **230,000+** active users according to n8n – choosing the right **[n8n hosting provider](/n8n-hosting/)** has become a critical decision that directly impacts workflow reliability, execution speed, and long-term costs.
Industry data shows **60% of organizations** achieve ROI within 12 months of implementing workflow automation (according to Kissflow), but poor hosting choices lead to workflow failures, slow webhook responses, and unexpected costs.
This guide evaluates seven **[n8n hosting](/n8n-hosting/) providers** through rigorous testing, performance benchmarks, and real-world deployment scenarios to help you make an informed decision.
## Table of Contents
## **TL;DR: Quick Decision Guide** **on n8n Hosting Provider**
**If You Want To…**
**Use This**
**Expected Impact**
**Setup Time**
**Deploy n8n in under 10 minutes**
xCloud
Workflow automation in production
5-8 minutes
**Get maximum workflow executions/dollar**
Hostinger VPS KVM 2
High execution volume at low cost
15-20 minutes
**Scale from small to enterprise**
Kamatera Cloud VPS
Seamless resource scaling
20-30 minutes
**Minimize technical setup**
xCloud Managed n8n
Zero Docker/Node.js configuration
3-5 minutes
**Run AI-powered workflows with GPUs**
xCloud Custom Plans
LLM + n8n integrations
30-45 minutes
**Europe-focused data compliance**
IONOS VPS
GDPR-compliant automation
15-25 minutes
**Maximum RAM per dollar**
Contabo VPS
Memory-intensive workflows
20-30 minutes
### **Expert Recommendation by Use Case**
- **For Beginners:** xCloud offers one-click n8n deployment with managed updates and 24/7 support.
- **For Developers:** Hostinger provides Docker-ready VPS with full root access at competitive pricing.
- **For Enterprises:** Kamatera delivers scalable infrastructure with global reach and 99.95% uptime.
## **Why Your n8n Hosting Choice Directly Impacts Workflow Performance**
[n8n](https://n8n.io/) processes automation workflows differently than traditional applications. According to n8n’s official documentation, each workflow execution involves:
1\. Webhook triggers that must respond within 30 seconds to avoid timeouts
2\. Memory-intensive operations when processing JSON data, file attachments, or API responses.
3\. Persistent background processes that run 24/7 regardless of user activity
4\. Database writes for execution logs, error tracking, and workflow state management
Research from n8n’s scalability benchmark study demonstrates that hosting infrastructure affects:
- **Webhook latency:** Proper hosting reduces webhook response time by 40-75%
- **Execution failures:** Stable servers decrease timeout errors by 60-80%
- **Concurrent workflows:** Adequate RAM allows running 3-5x more simultaneous workflows
- **Cost efficiency:** Right-sized hosting prevents $200-500/month in wasted resources
Automation platform analyst **6sense reports** that over 1,597 companies worldwide now use n8n for workflow automation. Those with optimized hosting report 25-30% productivity increases according to Kissflow automation statistics compared to organizations running n8n on inadequate infrastructure, according to Kissflow automation statistics.
## **How We Ranked the n8n Hosting Providers Based on Testing and Evaluation Criteria**
We evaluated seven [**n8n hosting**](/docs/deploy-n8n-with-xcloud-with-one-click-apps/) providers across eight weighted categories. Each provider underwent real-world deployment testing over a 30-day period.
### **Evaluation Criteria**
**1\. n8n Compatibility (25% of total score)**
- Docker support and container management
- Node.js version compatibility
- PostgreSQL/SQLite database support
- Redis availability for queue mode
**2\. Performance Metrics (20% of total score)**
- Webhook response time (tested with 1,000 concurrent requests)
- Workflow execution speed (measured across 10 standard workflows)
- Memory allocation stability during peak loads
- CPU performance under concurrent executions
**3\. Scalability (15% of total score)**
- Vertical scaling options (RAM/CPU upgrades)
- Horizontal scaling support (multiple worker instances)
- Resource limits per plan tier
- Upgrade/downgrade friction
**4\. Deployment Ease (15% of total score)**
- Set up time from account creation to live n8n instance
- One-click installation availability
- Documentation quality
- Technical knowledge required
**5\. Reliability & Uptime (10% weight)**
- Guaranteed uptime SLA
- Actual uptime measured over 30 days
- Backup frequency and restoration testing
- DDoS protection and security measures
**6\. Support Quality (10% of total score)**
- Response time for technical queries
- n8n-specific expertise
- Support channel availability (chat, email, phone)
- Documentation and community resources
**7\. Cost Efficiency (5% of total score)**
- Price per 1,000 workflow executions
- Total cost of ownership over 12 months
- Hidden fees (backups, SSL, migrations)
- Money-back guarantee period
**8\. Testing Environment:**
- Standard n8n workflows: Data sync, webhook processing, API integrations, scheduled triggers
- Workflow complexity: 5-15 nodes per workflow
- Execution volume: 100-10,000 executions per month
- Test period: 30 days
## **Comparison of the 7 Best n8n Hosting Providers**
Below is an overview of the top n8n hosting providers based on pricing, server resources, Docker support, setup difficulty, and ideal use cases to help you quickly identify the best option for your [**workflow automation**](/how-to-build-an-ai-agent-with-n8n/) needs.
Rank
Provider
Starting Price
RAM
CPU Cores
Storage
Docker Support
Setup Difficulty
Best For
🥇1
xCloud
6.99$/mo
2 – 32 GB
1 – 8 vCPU
50 – 400 GB NVMe
✅ One-click
★☆☆☆☆ Easy
Managed n8n hosting with zero DevOps overhead
🥈2
Hostinger
$4.99/mo
4 – 32 GB
1 – 8 vCPU
50 – 400 GB NVMe
✅ Native
★★☆☆☆ Moderate
Budget-conscious developers needing full control
🥉3
Kamatera
$4.00/mo
1 – 128 GB
2 – 104 vCPU
20 – 4000 GB SSD
✅ Yes
★★★☆☆ Advanced
Enterprises requiring global infrastructure
4
IONOS
$2.00/mo
4 – 24 GB
2 – 8 vCPU
20 -80 GB SSD
✅ Yes
★★☆☆☆ Moderate
European businesses needing GDPR compliance
5
Contabo
$4.42/mo
8 – 18 GB
3 – 6 vCPU
150 – 400 GB SSD
✅ Yes
★★★☆☆ Advanced
Memory-intensive workflow automation
6
HostArmada
$3.69/mo
1 – 16 GB
1 – 8 vCPU
40–320 GB SSD
✅ Yes
★★☆☆☆ Moderate
Balanced performance and support
7
Scala Hosting
$13.95/mo
4 – 128 GB
2 – 24 vCPU
50–2000 GB SSD
✅ Yes
★★☆☆☆ Moderate
Security-focused n8n deployments
### **Impact Rating Based on Workflow Execution Capacity**
Below, you’ll find a simple explanation of each rating level and the type of workloads it is designed to support.
★★★★★ = Exceptional (handles 10,000+ executions/month)
★★★★☆ = Strong (handles 5,000-10,000 executions/month)
★★★☆☆ = Good (handles 1,000-5,000 executions/month)
★★☆☆☆ = Adequate (handles 100-1,000 executions/month)
★☆☆☆☆ = Basic (handles <100 executions/month)
## **Detailed Reviews On The 7 Best n8n Hosting Providers**
Here’s a detailed look at each provider, highlighting strengths, limitations, and ideal use cases. The sections below break down each hosting option so you can easily compare them and choose the right one.
### **🥇 1. xCloud – Best for Managed n8n Hosting with One-Click Deployment**
Industry experts consistently recommend xCloud for organizations prioritizing deployment speed and managed infrastructure over DIY server management. Research from hosting comparison site HostAdvice shows [**managed n8n hosting**](/n8n-hosting/) reduces time-to-production by 75-85% compared to self-configured VPS setups.
xCloud differentiates itself through n8n-optimized infrastructure that removes common deployment friction points. While competitors require manual Docker installation, database configuration, and webhook setup, xCloud provides pre-configured n8n instances that reach production status in under 10 minutes.
Organizations running AI-powered n8n workflows particularly benefit from xCloud’s infrastructure, which provides seamless integration between workflow automation and **[LLM](/docs/how-to-self-host-llms-with-xcloud/)** processing. According to n8n’s 2026 market analysis, businesses combining AI and automation see 40-60% greater efficiency gains than those using automation alone.
#### **Key Features**
- **One-Click n8n Deployment:** Pre-configured Docker containers with PostgreSQL, Redis, and webhook endpoints configured automatically
- **Managed Updates:** Automatic n8n version updates without workflow downtime
- **AI-Ready Infrastructure:** Native integration with LLM hosting for GPT-4, Claude, and custom AI models within the same environment
- **24/7 Technical Support:** n8n-specific expertise with an average response time of 12 minutes for critical workflow issues
- **Free SSL & Backups:** Automated daily backups with 30-day retention and one-click restoration
- **Global CDN:** Webhook response time reduced by 35-50% through geographically distributed endpoints
#### **How to Deploy n8n With xCloud**
Let us show you how to deploy n8n on xCloud using the One Click Apps feature. It explains how to create a site, set basic options, and get n8n running on your server. The steps are simple and suitable for both testing and live use, helping you set up n8n quickly without complex configuration.
- Create an account and log in to **xCloud**, then connect your server
- From the dashboard, click **New Site → Server → One Click Apps**, then select **n8n**
- Enter the site title and tags, then choose the deployment mode **Go Live** for production, **Demo Site** for testing (temporary subdomain)
- Review domain settings, keep the default **Port** and **Site User**, select your **Timezone**, and click **Next** to start installation
- Click **Visit Site** from the dashboard, complete the n8n registration, and access the n8n dashboard to start creating workflows
- Customize configuration using the **Environment Editor** (available on PRO plans)
- Keep n8n up to date by navigating to **Updates → Check for Updates** in the dashboard
For the full detailed step by step process visit this [documentation](/docs/deploy-n8n-with-xcloud-with-one-click-apps/).
### **Pros and Cons**
**Pros**
**Cons**
✅ Zero DevOps knowledge required
❌ Higher cost than self-managed VPS
✅ Managed updates without downtime
❌ Limited to xCloud’s infrastructure regions
✅ AI/LLM integration within the same platform
❌ Custom Docker configurations require a support ticket
✅ 99.9% uptime SLA with automatic failover
❌ Not suitable for users wanting full OS-level access
✅ n8n-specific support team
**Best for:** Small to medium businesses wanting production-ready n8n hosting provider without hiring DevOps engineers. Ideal for teams running 100-10,000 workflow executions per month who value reliability over cost optimization.
**Pricing**: Starting at $6.99/month for 2 GB RAM, 1 vCPU, 50 GB NVMe storage (sufficient for 1,000-3,000 executions/month)
**Real-World Performance:**
- Webhook response time: 145ms average (tested with 1,000 concurrent requests)
- Workflow execution success rate: 99.7% over a 30-day period
- Zero downtime during managed updates
### **🥈 2. Hostinger – Best Budget VPS for Self-Hosted n8n**
According to Gizmodo’s comprehensive n8n hosting provider review, Hostinger provides the best price-to-performance ratio for developers comfortable with self-managed infrastructure. Industry benchmarks show [**Hostinger’s**](https://www.hostinger.com/) KVM 2 plan delivers 8 GB RAM and 2 vCPU cores at $6.99/month, undercutting competitors by 30-40% for equivalent specifications.
Hostinger’s native Docker support eliminates the primary complexity of n8n deployment. Unlike providers requiring manual Docker installation, Hostinger’s VPS control panel includes one-click Docker activation with pre-configured container networking.
n8n deployment testing conducted by Bitcatcha demonstrated Hostinger’s LiteSpeed servers process webhook requests 25-35% faster than Apache-based alternatives, critical for time-sensitive automation workflows.
#### **Key Features**
- **Native Docker Integration:** One-click Docker installation through hPanel control panel with container management GUI
- **LiteSpeed Web Server:** Industry data shows 40% faster request processing compared to Apache/Nginx configurations
- **10 Global Data Centers:** Reduce webhook latency by 50-75ms through geo-optimized server selection
- **NVMe SSD Storage:** Workflow execution logs and database operations run 3-5x faster than traditional SSD
- **Weekly Automated Backups:** Restore n8n instance to any point within the last 4 weeks with zero data loss
- **99.9% Uptime Guarantee:** Backed by Tier-3 data center infrastructure with redundant power and networking
#### **How to Implement**
Basic Docker Setup (15-20 minutes)
1. Purchase Hostinger KVM 2 VPS plan ($6.99/month)
2. Select Ubuntu 22.04 LTS operating system
3. Access hPanel → VPS → Operating System → Enable Docker
4. SSH into server: ssh root@your-vps-ip
5. Run n8n Docker command (see documentation)
6. Access n8n at http://your-vps-ip:5678
7. Configure SSL using Hostinger’s free Let’s Encrypt integration
Follow Hostinger’s detailed n8n deployment [guide](http://hostinger.com/tutorials).
### **Pros and Cons**
**Pros**
**Cons**
✅ Lowest cost per GB of RAM ($0.87/GB)
❌ Requires basic Linux/Docker knowledge
✅ Native Docker support in control panel
❌ Self-managed updates (no automation)
✅ LiteSpeed performance advantage
❌ Support focuses on VPS, not n8n-specific
✅ 10 global server locations
❌ Weekly backups (vs daily with managed providers)
✅ 30-day money-back guarantee
❌ Maximum 8 vCPU cores (limited for large-scale)
**Best for:** Developers with basic Docker experience seeking maximum value for money. Ideal for agencies managing multiple client workflows or businesses running 3,000-15,000 executions per month on a controlled budget.
**Pricing:** KVM 2 plan at $6.99/month (8 GB RAM, 2 vCPU, 100 GB NVMe, 8 TB bandwidth)
**Real-World Performance:**
- Webhook response time: 178ms average
- Docker container restart time: 3.2 seconds
- n8n upgrade downtime: 45 seconds (manual process)
### **🥉 3. Kamatera – Best for Scalable Enterprise n8n Infrastructure**
Enterprise automation demands drive [**Kamatera’s**](https://www.kamatera.com/) position as the leading choice for organizations requiring elastic scalability. According to n8n’s scaling documentation, businesses processing over 10,000 executions per month benefit significantly from horizontally scalable infrastructure – Kamatera’s core strength.
### **Key strengths:**
- 99.95% uptime SLA,
- Hourly billing option,
- Instant vertical scaling,
- Global data centers on 4 continents,
- Custom server configurations from 1-128 GB RAM.
**Best for:** Enterprises running 10,000+ workflow executions monthly with variable loads. Pricing:
Starting at $4.00/month; typical production: $45-75/month
### **4\. IONOS – Best for European Data Compliance & GDPR-Focused n8n Hosting** **Provider**
[**IONOS**](https://www.ionos.com/) emerges as the preferred choice for organizations prioritizing European data sovereignty and GDPR compliance. All infrastructure located in Germany and France with guaranteed data residency.
**Key features:** ISO 27001 & GDPR compliance, personal consultant, snapshot backups, DDoS protection included, full root access.
**Best for:** European businesses requiring GDPR-compliant workflow automation. Pricing: Starting at $2.00/month; recommended VPS Linux M at $8.00/month
### **5\. Contabo – Best for Maximum RAM Per Dollar**
[Contabo](https://contabo.com/en/) dominates the value segment by providing exceptional RAM allocations at budget-friendly pricing. Entry plans start at 8 GB RAM vs 2-4 GB at competitors—approximately 3x more memory at equivalent price points.
**Key strengths:** High RAM allocations (8-18 GB base), NVMe storage option, unlimited bandwidth, European data centers, DDoS protection included.
**Best for:** Memory-intensive n8n workflows with large data processing. Pricing: VPS S SSD at $4.42/month (8 GB RAM)
### **6\. HostArmada – Best for Balanced Performance & Support Quality**
[**HostArmada**](https://hostarmada.com/) distinguishes itself through comprehensive 24/7 support combined with solid technical performance. Daily automated backups with 30-day retention and one-click restoration provide peace of mind for production automation environments.
### **Key features:**
- Daily automated backups,
- SSD storage across all plans,
- 24/7 technical support with n8n knowledge,
- Free website migration,
- Multiple data centers (US, EU, Asia, Australia).
**Best for:** Small businesses valuing responsive support.
**Pricing:** VPS starts at $3.69/month or VPS Business at $7.99/month (recommended)
### **7\. Scala Hosting – Best for Security-Focused n8n Deployments**
**[Scala Hosting](https://www.scalahosting.com/)** positions itself as the security-first [**VPS provider**](/managed-hosting/) through its proprietary SPanel control system and advanced security automation. SShield real-time security monitors and blocks 85-90% of common VPS attack vectors.
**Key features:** SShield real-time security, daily malware scanning, free SSL certificates, SPanel control panel, 99.9% uptime guarantee, full root access.
**Best for:** Organizations with strict security requirements or compliance obligations (HIPAA, SOC 2, PCI-DSS).
**Pricing:** VPS starts at $13.95/month with managed security
### **Performance Benchmarks: Webhook Response Time**
The benchmarks below show how quickly each hosting provider responds to webhook requests during performance testing.
**Provider**
**Avg Response Time**
**95th Percentile**
**Test Load**
**Test Date**
**xCloud**
145ms
198ms
1,000 concurrent
Dec 2025
**Kamatera**
132ms
185ms
1,000 concurrent
Dec 2025
**Scala Hosting**
158ms
215ms
1,000 concurrent
Dec 2025
**IONOS**
165ms
223ms
1,000 concurrent
Dec 2025
**HostArmada**
172ms
238ms
1,000 concurrent
Dec 2025
**Hostinger**
178ms
245ms
1,000 concurrent
Dec 2025
**Contabo**
195ms
268ms
1,000 concurrent
Dec 2025
## **Expert Picks For Best n8n Hosting Providers**
After rigorous testing of seven n8n hosting providers over 30 days, three clear winners emerge for different use cases. Let us see in short:
### **🥇 Best Overall: xCloud**
For businesses prioritizing reliability, ease of deployment, and managed infrastructure, xCloud delivers unmatched value. The one-click deployment, automatic updates, and n8n-specific support justify the slightly higher cost. Organizations running business-critical workflows with 100-10,000 monthly executions will appreciate the zero-downtime updates and 99.9% uptime guarantee.
### **🥈 Best Value: Hostinger**
Developers and technically-proficient teams seeking maximum cost efficiency should choose Hostinger’s KVM 2 plan. At $6.99/month for 8 GB RAM and native Docker support, it delivers 30-40% cost savings compared to managed alternatives. Perfect for agencies managing multiple client workflows or businesses running 3,000-15,000 monthly executions.
### **🥉 Best for Enterprise: Kamatera**
Organizations processing 10,000+ monthly executions with variable loads require Kamatera’s elastic scalability. The 99.95% uptime SLA, hourly billing, and instant vertical scaling provide enterprise-grade reliability without enterprise-grade pricing. Global data centers across 4 continents ensure low webhook latency worldwide.
## **Frequently Asked Questions**
### **1\. Which n8n hosting provider should beginners start with?**
Beginners should start with managed hosting like xCloud, or choose Hostinger if they’re comfortable managing their own server.
Industry data shows 75–85% of beginners successfully deploy n8n within 10 minutes using managed hosting, compared to only 45–60% success rates with self-managed VPS setups that require Docker and Linux knowledge. Managed providers remove technical friction with one-click deployment, automatic updates, and n8n-specific support—allowing you to focus on building workflows instead of infrastructure.
### **2\. Do I need to pay for n8n Cloud, or can I just use hosting?**
You do not need n8n Cloud. n8n itself is free and open-source—you only pay for the hosting infrastructure.
Self-hosting typically saves $35–43 per month (70–86%) compared to n8n Cloud for mid-volume usage. According to n8n’s 2025 community survey, 68% of users choose self-hosting primarily for cost efficiency.
### **3\. How long does it take to see results from workflow automation?**
Most organizations see measurable ROI within 4–12 weeks. Industry research shows 60% of companies achieve ROI within 12 months.
Example: A marketing agency automated client reporting with n8n, reducing 40 hours/month of manual work to just 2 hours. This generated $1,900/month in savings against $15/month hosting costs, resulting in a 12,567% ROI.
### **4\. Is managed n8n hosting worth the extra cost?**
Yes, if your time is worth more than $25–50/hour or you lack Docker/Linux expertise.
Managed hosting saves 4–7 hours per month on setup, updates, troubleshooting, and maintenance. At $25/hour, just 4 saved hours equals $100 in value—for only $10–15 extra hosting cost. Businesses using managed hosting also report up to 90% fewer deployment failures.
### **5\. Will n8n work for my industry or niche?**
Yes. n8n is industry-agnostic and works anywhere APIs or web applications are used.
With 450+ pre-built integrations, n8n supports virtually every use case. Proven industries include:
- E-commerce
- Healthcare
- Real Estate
- Finance
- Marketing Agencies
- SaaS
- Manufacturing
Example: A dental practice automated appointment confirmations and reduced patient no-shows by 40%.
### **6\. What budget is required to run n8n successfully?**
- Minimum viable setup: $5–7/month (small or personal use)
- Business-critical automation: $15–50/month
Generally, the pricing plans are:
- Tier 1 (Personal): $5–10/month → 100–1,000 executions
- Tier 2 (Small Business): $15–35/month → 1,000–5,000 executions
- Tier 3 (Mid-Size): $50–150/month → 5,000–20,000 executions
- Tier 4 (Enterprise): $300–1,000+/month → 50,000+ executions
### **7\. How often should I upgrade my n8n hosting plan?**
Review resource usage monthly and upgrade when RAM consistently exceeds 70–80%.
Upgrade immediately if you notice:
- RAM usage above 75%
- Workflow failures are increasing by 20%+
- Webhook response times over 500 ms
- Database query times increasing by 100%+
Proactive upgrades prevent 90–95% of workflow failures.
### **8\. What’s the most underrated n8n hosting option?**
Contabo offers one of the best RAM-to-price ratios—but requires technical expertise.
You can get 8 GB RAM for $4.42/month, while competitors charge $15–25 for similar specs (70–82% savings). One user reported running 42 active workflows and 12,000 executions/month on Contabo’s base plan—workloads that would cost $45–65/month on managed hosting.
### **9\. Can I migrate my existing n8n instance to better hosting?**
Yes. Most migrations take 30–90 minutes and are low risk.
Migration options:
- Backup & Restore (PostgreSQL): 30–45 minutes
- Export/Import via n8n UI: 15–30 minutes, beginner-friendly
- Managed Migration: Free with some providers
Overall, 95% of migrations were completed successfully with zero data loss.
### **10\. How do I know if my workflows are too complex for my hosting?**
If webhook response times consistently exceed 300 ms or you see timeout errors, your hosting is likely underpowered.
Warning signs:
- More than 5% of webhooks are timing out
- Execution times are doubling unexpectedly
- Database lock errors
- Memory warnings
Recommended RAM by complexity:
- Simple workflows (≈5 nodes): 2 GB RAM
- Medium workflows (10–15 nodes): 4 GB RAM
- Complex workflows (20+ nodes): 8 GB RAM
### 11\. Are there any free n8n hosting options worth using?
Yes—but only for learning or testing.
- Oracle Cloud Free Tier: 4 ARM CPUs, 24 GB RAM, 200 GB storage (requires 2–3 hours of complex setup)
- Railway: ~$5/month in free credits (≈500–1,000 executions)
- Raspberry Pi: $35–75 one-time cost, no SLA
Free hosting is ideal for experimentation. Once workflows become business-critical, investing $6.99–14.99/month is strongly recommended.
### 12\. What happens if my n8n hosting provider goes down?
All workflow executions stop immediately.
Immediate impact:
- Webhooks fail
- Scheduled workflows don’t run
- In-progress executions terminate
Downtime severity:
- 5–15 minutes: minimal impact
- 1–4 hours: moderate impact
- 4–24 hours: significant impact
- 24+ hours: critical
Mitigation best practices:
- Choose providers with 99.9%+ uptime SLAs
- Enable automated daily backups
- Set up monitoring and alerts
With proper preparation, recovery typically takes 45–90 minutes.
### 1\. Which n8n hosting provider should I start with as a beginner?
Start with xCloud for managed hosting or Hostinger for self-managed hosting. Industry data shows 75-85% of beginners successfully deploy n8n using managed hosting (xCloud) within 10 minutes, compared to only 45-60% success rates with self-managed VPS requiring Docker knowledge. xCloud removes technical barriers through one-click deployment, automatic updates, and n8n-specific support.
### 2\. Do I need to pay for a separate n8n Cloud, or can I just use hosting?
n8n software is free and open-source you only pay for the hosting infrastructure to run it. Self-hosting saves $35-43/month (70-86%) compared to n8n Cloud for mid-volume workflows. According to n8n’s 2025 community survey, 68% of users choose self-hosting for cost efficiency.
### 3\. How long until I see results from workflow automation?
Most organizations achieve measurable ROI within 4-12 weeks of deploying n8n. Industry research shows 60% of organizations achieve ROI within 12 months. A marketing agency automated client reporting using n8n, reducing 40 hours/month of manual work to 2 hours – generating $1,900/month savings vs $15/month hosting costs (12,567% ROI).
### 4\. Is managed n8n hosting worth the extra cost?
Yes, if your time costs more than $25-50/hour or you lack Docker/Linux expertise. Managed hosting saves 4-7 hours monthly in setup, updates, troubleshooting, and maintenance. If your time is worth $25/hour: 4 hours × $25 = $100 value for $10-15 additional cost. Businesses using managed hosting report 90% fewer deployment failures.
### 5\. Will n8n work for my specific industry/niche?
Yes, n8n is industry-agnostic and works for any business using web applications or APIs. n8n’s 450+ pre-built integrations cover virtually every industry need. Confirmed applications include: E-commerce, Healthcare, Real Estate, Finance, Marketing Agencies, SaaS Companies, and Manufacturing. A dental practice automated appointment confirmations, reducing no-shows by 40%.
### 6\. What’s the budget needed to run n8n successfully?
Minimum viable budget: $5-7/month for small deployments; $15-50/month for business-critical automation.
**Tier 1 (Personal):** $5-10/month supports 100-1,000 executions. **Tier 2 (Small Business):** $15-35/month supports 1,000-5,000 executions.
**Tier 3 (Mid-Size):** $50-150/month supports 5,000-20,000 executions.
**Tier 4 (Enterprise):** $300-1,000+/month supports 50,000+ executions.
### 7\. How often should I upgrade my n8n hosting plan?
Monitor RAM usage monthly; upgrade when consistently exceeding 70-80% capacity. Upgrade immediately when RAM usage >75%, workflow failures increase >20%, webhook response time >500ms, or database query time increases >100ms. Proactive upgrades prevent 90-95% of workflow failures.
### 8\. How do I know if my workflows are too complex for my current hosting?
Monitor webhook response times, if consistently exceeding 300ms or seeing timeout errors, your hosting is inadequate.
**Red flags**: >5% webhooks timing out, workflow execution time >2x expected, database lock errors, memory warnings.
- Simple workflows (5 nodes): need 2 GB RAM.
- Medium (10-15 nodes): needs 4 GB RAM.
- Complex (20+ nodes): need 8 GB RAM.
### 9\. Are there any free n8n hosting options worth considering?
Oracle Cloud Free Tier and Railway free credits offer viable free hosting, but with limitations.
Oracle Cloud provides 4 ARM CPUs, 24 GB RAM, 200 GB storage – but requires 2-3 hours complex setup.
Railway offers $5 free credits monthly (~500-1,000 executions), good for testing only.
Raspberry Pi costs $35-75 one-time for a permanent self-hosted n8n, but no SLA. F
ree hosting makes sense for learning; once workflows become business-critical, invest $6.99-14.99/month.
### 10\. What happens if my n8n hosting provider goes down?
Workflow executions stop immediately; recovery time depends on your backup strategy.
**Immediate impacts:** All webhook triggers fail, scheduled workflows don’t execute, and in-progress executions terminate. Downtime of 5-15 minutes has minimal impact; 1-4 hours causes moderate impact; 4-24 hours creates significant business impact; 24+ hours is critical.
**Mitigation:** Choose providers with 99.9%+ uptime SLA, implement automated daily backups, and set up monitoring/alerts. The recovery procedure takes 45-90 minutes with proper preparation.
### 11\. Can I migrate my existing n8n instance to better hosting?
Yes – n8n migration takes 30-90 minutes depending on setup complexity.
Three methods:
Method A (Backup & Restore): 30-45 minutes using PostgreSQL dump.
Method B (Export/Import via n8n UI): 15-30 minutes, no technical knowledge needed.
Method C (Managed Migration): Free service from HostArmada/xCloud.
95% of migrations are completed successfully with zero data loss
## **Key Takeaways**
1\. Hosting infrastructure directly impacts n8n performance proper hosting reduces webhook latency by 40-75% and prevents 60-80% of execution failures.
2\. Self-hosting n8n saves 70-86% compared to n8n Cloud for mid-volume workflows while providing unlimited workflow capacity.
3\. RAM is more critical than CPU for n8n – prioritize memory allocation when selecting plans. 2 GB minimum for basic use, 8 GB for production environments.
4\. Managed hosting (xCloud) saves 4-7 hours monthly in maintenance, making it cost-effective for teams where time costs $25+/hour.
5\. Queue mode with Redis becomes essential beyond 2,000-3,000 monthly executions, increasing throughput by 300-500%.
6\. Geographic server location matters – proper placement reduces webhook latency by 40-60%.
The workflow automation market is growing at 9.52% annually, and organizations implementing n8n achieve 60% ROI within 12 months. Your hosting choice determines whether you’re in that successful 60% or struggling with workflow failures and slow performance.
Start with the recommendations in this guide, deploy your first workflows, and scale as your automation needs grow. Whether you choose managed simplicity with xCloud, cost-efficient self-hosting with Hostinger, or enterprise scalability with Kamatera, you now have the data needed to make an informed decision.
Ready to deploy n8n? Your automation journey starts with choosing the right hosting foundation.
Article compiled from 30 days of testing across 7 hosting providers, 10,000+ workflow executions, and analysis of 25+ authoritative sources, including n8n documentation, Mordor Intelligence, Kissflow, 6sense, HostAdvice, Gizmodo, Bitcatcha, and Reddit r/n8n community discussions.
If you have found this blog helpful, feel free to **[subscribe to our blogs](/blog/)** for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and take part in discussions. And do not forget to share what you have built. We would love to see your work.
---
# 7 Best OpenClaw(Clawdbot) Hosting Providers in 2026: From Self-Hosted to Fully Managed (Complete Guide) - xCloud
> Compare the 7 best OpenClaw hosting providers in 2026. Explore self-hosted vs fully managed options, pricing, setup time, and expert picks.
[**OpenClaw**](/openclaw-hosting/), now rebranded as Clawdbot, has become one of the fastest-growing open-source AI projects in GitHub history, amassing over **60,000 stars** in just weeks (according to GitHub).
Created by Peter Steinberger, founder of PSPDFKit, this AI assistant promises what Siri and Alexa never delivered: a **24/7 personal assistant** that actually takes action through WhatsApp, Telegram, and other messaging platforms.
But here’s the catch self-hosting OpenClaw requires Docker expertise, VPS management, and dealing with the dreaded “API Wallet Assassin” problem, where runaway loops can drain hundreds of dollars overnight. This comprehensive guide compares hosting options from fully managed solutions to budget VPS providers, helping you deploy your AI assistant without the 3 AM debugging sessions.
## Quick Summary / TL;DR
Too Long; Didn’t Read? Here’s what you need to know:
If You Want To…
Use This
Expected Impact
Time Required
Deploy with zero DevOps
OpenClaw by xCloud
Live in 60 seconds
Under 1 minute
Self-host on a budget
Hostinger VPS
Full control, $4.99/mo
2-4 hours setup
Scale dynamically
Kamatera
Pay-per-use flexibility
1-2 hours setup
Developer-friendly tools
DigitalOcean
Excellent documentation
1-2 hours setup
Rapid prototyping
Railway
Git-push deployment
30-60 minutes
Maximum GPU power
Vultr
High-performance inference
2-3 hours setup
Complete privacy
Local hardware
Zero cloud dependency
4+ hours setup
**Expert Recommendation:** Industry experts consistently recommend starting with a fully managed solution for non-technical users, as self-hosting OpenClaw requires comfort with Docker, terminal commands, and ongoing maintenance (according to the official Moltbot documentation).
**Best for Beginners:** OpenClaw by xCloud — One-click deployment with pre-configured Telegram and WhatsApp integration, no technical skills required.
**Best for Developers:** DigitalOcean — Excellent documentation, familiar interface, strong community support for troubleshooting.
**Best for Enterprise:** OpenClaw by xCloud (White-Label) — Managed infrastructure with SLA-backed support and custom branding options.
## What is OpenClaw (Clawdbot)?
OpenClaw, renamed to Clawdbot on January 27, 2026, following Anthropic’s trademark request, is an open-source, self-hosted AI personal assistant created by Peter Steinberger (according to the official project documentation). Unlike traditional AI chatbots that simply respond to queries, Open is an agentic AI that takes real actions on your behalf.
The assistant integrates with messaging platforms, including WhatsApp, Telegram, Slack, Discord, Signal, and iMessage, allowing you to interact with it like messaging a colleague. It can execute terminal commands, manage emails, control calendars, browse the web, and even write code – all from a chat interface.
Key capabilities include:
- Persistent memory across conversations that builds understanding over months
- Proactive notifications through scheduled “heartbeats” that check tasks and alert you
- 50+ service integrations including Gmail, Google Calendar, Todoist, GitHub, and smart home devices
- Custom skills marketplace (ClawdHub) with hundreds of community-contributed plugins
- Multi-platform support with the same conversation flowing across all devices
The architecture consists of four components: a Gateway (control plane), Agent (AI brain using Claude, GPT-4, or local models), Memory (persistent storage), and Skills (modular capabilities).
## Why OpenClaw Hosting Matters: Self-Hosted vs Managed
Understanding the hosting decision is critical because OpenClaw requires 24/7 uptime to function as a proactive assistant. The choice between self-hosting and managed hosting dramatically impacts your experience, costs, and time investment.
### The Self-Hosting Challenge
Self-hosting OpenClaw appeals to developers who want complete control, but it comes with significant responsibilities (according to community reports):
Challenge
Impact
Docker configuration
1-4 hours initial setup
VPS management
Ongoing maintenance required
API cost monitoring
Risk of “runaway loops” costing $100-500 overnight
Security hardening
Root access creates vulnerability risks
Manual updates
No automatic patching
Channel setup
Telegram bot tokens, WhatsApp QR codes
SSL configuration
Manual certificate management
### The Managed OpenClaw Alternative
Fully managed hosting eliminates DevOps complexity by handling infrastructure, updates, security, and channel configuration. Users simply sign up and start chatting.
Feature
Self-Hosted VPS
Fully Managed
Setup time
1-4 hours
Under 5 minutes
Technical skill
Docker, Linux, networking
None required
Server management
Your responsibility
Provider handles everything
Updates & patches
Manual
Automatic
SSL certificates
Manual configuration
Auto-provisioned
Telegram/WhatsApp setup
Manual bot creation
Pre-configured
3 AM outages
You fix it
Provider fixes it
Support
Community forums
Dedicated team
## **How We Ranked These Providers**
Rankings in this guide are based on criteria established by industry best practices for AI workload hosting (according to Gartner’s cloud infrastructure evaluation framework):
Criterion
Why It Matters
Weight
Ease of Deployment
Time from signup to running agent
High
Total Cost of Ownership
Server + API + maintenance time
High
Reliability
Uptime guarantees and redundancy
High
Channel Integration
Pre-configured Telegram/WhatsApp support
Medium
Scalability
Ability to handle increased workloads
Medium
Support Quality
Response time and expertise
Medium
Security
Isolation, SSL and more
High
Scoring methodology follows cloud infrastructure best practices, with providers evaluated across all criteria and weighted by importance for AI agent deployments.
## Master Comparison Table
Rank
Provider
Setup Time
Monthly Cost
Best For
Difficulty
Support
🥇 1
OpenClaw by xCloud
★★★★★
$9.99/mo (all-in)
Zero DevOps users
Easy
24/7 human
🥈 2
Hostinger VPS
★★★☆☆
$5.99+/mo + API
Budget self-hosting
Medium
24/7 chat
🥉 3
Kamatera
★★★☆☆
Pay-per-use
Dynamic scaling
Medium
24/7 technical
4
DigitalOcean
★★★★☆
$6+/mo + API
Developers
Medium
Tickets + community
5
Railway
★★★★☆
$5+/mo usage
Rapid prototyping
Easy-Medium
Community
6
Vultr
★★★☆☆
$6+/mo + API
GPU workloads
Medium
Tickets
7
Local Hardware
★★☆☆☆
$0 (hardware cost)
Privacy maximalists
Hard
None
## 🥇 1. OpenClaw Hosting By xCloud – Best for Zero DevOps Deployment
Industry experts consistently recommend fully managed solutions for users who want AI assistant capabilities without infrastructure management overhead (according to cloud hosting best practices). [**OpenClaw**](/openclaw-hosting/) by xCloud represents the only truly managed Moltbot hosting option that eliminates all DevOps requirements.
Unlike VPS providers, where you still configure Docker, manage updates, and handle outages yourself, xCloud deploys your personal AI agent automatically. The entire experience happens through chat, there’s no dashboard or hosting panel to learn. You sign up, xCloud provisions everything behind the scenes, and you start messaging your agent on Telegram.
xCloud has managed over _**10,000 servers**_ across _global locations_ (according to xCloud), bringing enterprise-grade infrastructure expertise to personal AI assistants. The parent company WPDeveloper powers over 6 million websites, demonstrating proven scale and reliability.
### Key Features
- **60-second deployment:** Sign up and your agent is live immediately—no terminal, no configuration
- **Pre-configured channels:** Telegram works out of the box with bot token connection. Anthropic and other built in chaneels coming very soon.
- **Fully managed infrastructure:** Server, updates, SSL, and security handled automatically
### How to Implement
**Getting Started:**
1. Visit this [**page**](/openclaw-hosting/) and create your account
2. Choose your plan (starting at $9.99/month)
3. Connect your Telegram bot token
4. Start chatting with your AI agent
No Docker. No SSL configuration. No debugging at 3 AM.
### Pros and Cons
Pros
Cons
✅ Instant deployment with zero technical setup
❌ Higher base price than raw VPS
✅ Pre-configured Telegram and WhatsApp integration
❌ Less customization than self-hosting
✅ Server included—no additional infrastructure costs
❌ Limited to supported messaging platforms
✅ 24/7 human support for issues
✅ Automatic updates and security patches
✅ White-label options for enterprise
**Best for:** Non-technical users, busy professionals, small teams, and agencies who want a working AI assistant without managing infrastructure. Ideal for anyone who values time over cost savings from DIY hosting.
## **🥈 2. Hostinger VPS – Best for Budget Self-Hosting**
For users comfortable with server administration who want the lowest possible hosting costs, Hostinger offers VPS plans optimized for AI workloads (according to HostAdvice). The platform provides NVMe SSD storage, full root access, and dedicated IPs at competitive prices.
Hostinger’s custom hPanel simplifies VPS management compared to traditional control panels, though users still need to install Docker, configure Moltbot, set up messaging bridges, and handle ongoing maintenance. The 99.9% uptime guarantee across data centers in the US, UK, Singapore, and the Netherlands provides stable infrastructure for always-on assistants.
### Key Features
- **NVMe SSD storage:** Fast read/write speeds for agent operations
- **Full root access:** Complete control over server configuration
- **AI-ready templates:** Pre-configured environments for Python and Node.js workloads
- **99.9% uptime SLA:** Reliable infrastructure across 4 global regions
- **24/7 live chat support:** Assistance with infrastructure issues
### How to Implement
**Option A: Manual Setup**
1. Purchase a VPS plan (minimum 2GB RAM recommended)
2. SSH into your server and install Docker
3. Clone the Moltbot repository
4. Configure your AI model API keys (Anthropic Claude or OpenAI)
5. Set up a Telegram bot via @BotFather or a WhatsApp bridge
6. Configure SSL certificates
7. Set up monitoring and backup scripts
**Option B: Community Scripts** Use community-maintained installation scripts that automate most configuration steps, though you still manage the server.
### Pros and Cons
Pros
Cons
✅ Lowest base hosting cost ($5.99/month)
❌ Requires Docker and Linux knowledge
✅ Full control over configuration
❌ Manual channel setup required
✅ hPanel simplifies server management
❌ You handle updates and security patches
✅ Good global coverage
❌ No pre-configured Moltbot templates
✅ 24/7 chat support for server issues
❌ API costs are additional
**Best for:** Technical users on a budget who enjoy hands-on server management and want maximum control over their AI assistant deployment. Ideal for developers who already manage their own infrastructure.
## 🥉 3. Kamatera – Best for Dynamic Scaling
Kamatera provides over 1,000 custom server configurations with a pay-as-you-go billing model, making it ideal for AI developers who need dynamic resource allocation (according to HostAdvice). The platform’s flexibility allows scaling CPU, RAM, and storage independently based on workload demands.
For Moltbot deployments that vary in intensity—perhaps heavy use during work hours and minimal activity overnight—Kamatera’s model can optimize costs compared to fixed-resource VPS plans. The platform supports GPU options for users running local language models through Ollama.
### Key Features
- **1,000+ configurations:** Customize CPU, RAM, storage, and networking independently
- **Pay-as-you-go billing:** Pay only for resources consumed
- **GPU availability:** Access to NVIDIA GPUs for local model inference
- **99.95% uptime SLA:** Enterprise-grade reliability
- **Global infrastructure:** 18 data center locations worldwide
### **How to Implement**
**Setup Process:**
1. Create an account and configure custom server specs
2. Deploy Ubuntu or your preferred Linux distribution
3. Install Docker and container dependencies
4. Clone and configure Moltbot with your settings
5. Set up messaging platform integrations
6. Configure monitoring for resource usage optimization
### Pros and Cons
Pros
Cons
✅ Highly customizable resource allocation
❌ Steeper learning curve than simplified VPS
✅ Pay-per-use reduces waste
❌ All self-hosting responsibilities apply
✅ GPU options for local models
❌ Costs can spike with heavy usage
✅ 24/7 technical support
❌ No Moltbot-specific assistance
✅ Excellent for variable workloads
**Best for:** AI developers and technical teams who need fine-grained control over resources and prefer usage-based pricing. Ideal for deployments with variable workloads or those experimenting with local language models.
## 4\. DigitalOcean – Best for Developer Experience
DigitalOcean has established itself as a developer-friendly cloud platform with excellent documentation, community tutorials, and a clean interface (according to industry reviews). For developers familiar with the “Droplets” paradigm, deploying Moltbot follows familiar patterns.
The platform’s extensive tutorial library includes guides for Docker, Node.js, and AI application deployment, reducing the learning curve for self-hosting. Community support through forums and Stack Overflow provides troubleshooting resources beyond official support channels.
### Key Features
- **Droplets:** Simple, predictable-priced virtual machines
- **Extensive documentation:** Step-by-step guides for common deployments
- **One-click apps:** Marketplace includes Docker and development tools
- **Spaces:** Object storage for agent data and backups
- **Monitoring:** Built-in metrics and alerting
### How to Implement
**Setup Process:**
1. Create a Droplet (minimum 2GB RAM, 1 vCPU recommended)
2. Use one-click Docker installation from marketplace
3. Follow DigitalOcean’s container deployment guides
4. Configure Moltbot with environment variables
5. Set up domain and SSL via Let’s Encrypt
6. Configure firewall rules and monitoring
### Pros and Cons
Pros
Cons
✅ Exceptional documentation and tutorials
❌ Self-hosting responsibilities
✅ Predictable pricing with no surprises
❌ Support limited to infrastructure
✅ Strong developer community
❌ No Moltbot-specific templates
✅ Clean, intuitive interface
❌ API costs additional
✅ Reliable infrastructure
**Best for:** Developers who value documentation quality and community support. Ideal for those who prefer learning and troubleshooting through comprehensive guides rather than direct support.
## 5\. Railway – Best for Rapid Prototyping
Railway offers a modern deployment platform that bridges the gap between fully managed and self-hosted (according to DataCamp). The git-push deployment model allows developers to ship Moltbot configurations quickly without deep infrastructure knowledge.
The platform handles container orchestration, networking, and basic scaling automatically, reducing operational overhead compared to raw VPS management. However, users still configure the application itself and manage updates.
### Key Features
- **Git-push deployment:** Push code, Railway handles the rest
- **Automatic HTTPS:** SSL certificates provisioned automatically
- **Environment management:** Easy configuration variable handling
- **Usage-based pricing:** Pay for what you consume
- **Team collaboration:** Shared projects and deployment history
### How to Implement
**Setup Process:**
1. Connect your GitHub repository with Moltbot configuration
2. Configure environment variables for API keys
3. Deploy with git push
4. Configure custom domain (optional)
5. Set up messaging platform integrations
### Pros and Cons
Pros
Cons
✅ Fastest path from code to deployment
❌ Less control than VPS
✅ Automatic SSL and networking
❌ Usage costs can accumulate
✅ Modern developer experience
❌ Still requires application configuration
✅ Good for iterating quickly
❌ Community support only
✅ No server management
**Best for:** Developers who want to experiment with Moltbot quickly without infrastructure setup. Ideal for prototyping and testing before committing to production hosting.
## 6\. Vultr – Best for GPU-Accelerated Workloads
Vultr provides high-performance cloud compute with GPU instances suitable for running local language models through Ollama (according to AI hosting benchmarks). For users who want to avoid ongoing API costs by running models locally, Vultr’s GPU offerings provide necessary compute power.
The platform offers bare metal and cloud GPU instances across multiple regions, with NVMe storage for fast model loading. This approach eliminates per-token API costs but requires significantly more technical expertise and higher base hosting costs.
### Key Features
- **GPU instances:** NVIDIA GPUs for local model inference
- **Bare metal options:** Dedicated hardware for maximum performance
- **NVMe storage:** Fast model loading and agent operations
- **Global network:** 32 data center locations
- **Hourly billing:** Flexibility for testing and development
### How to Implement
**Setup Process:**
1. Provision a GPU-enabled instance
2. Install NVIDIA drivers and CUDA toolkit
3. Deploy Ollama for local model serving
4. Configure Moltbot to use local inference
5. Set up messaging integrations
6. Optimize model loading and caching
### Pros and Cons
Pros
Cons
✅ Eliminates per-token API costs
❌ High GPU instance costs ($90+/month)
✅ Complete privacy—no external API calls
❌ Complex setup requiring GPU expertise
✅ Full control over model selection
❌ Model performance varies by hardware
✅ Good for high-volume usage
❌ Significant technical overhead
**Best for:** Advanced users with high-volume AI usage who want to eliminate API costs through local inference. Ideal for privacy-focused deployments or those with specific model requirements.
## **7\. Local Hardware – Best for Maximum Privacy**
Running Moltbot on local hardware—a Mac Mini, old laptop, Raspberry Pi, or home server—provides complete data sovereignty with zero cloud dependency (according to the official Moltbot documentation). Many early adopters in the developer community have driven increased sales of Mac Mini units specifically for this purpose.
This approach requires the most technical expertise and ongoing maintenance but offers the ultimate in privacy and control. Your data never leaves your network, and there are no monthly hosting costs beyond electricity and API fees.
### Key Features
- **Zero hosting costs:** Only hardware investment required
- **Complete privacy:** Data never leaves your network
- **Full customization:** Unlimited configuration options
- **No cloud dependency:** Works offline for local models
- **Physical access:** Direct hardware control and monitoring
### **How to Implement**
**Minimum Requirements:**
- macOS, Linux, or Windows (via WSL2)
- Node.js version 22 or higher
- 4GB RAM minimum (8GB recommended)
- Stable internet connection for messaging bridges
- Static IP or dynamic DNS for external access
**Setup Process:**
1. Prepare hardware with supported operating system
2. Install Node.js and required dependencies
3. Clone Moltbot repository and run setup script
4. Configure AI model API keys
5. Set up messaging platform bridges
6. Configure router for external access (optional)
7. Set up monitoring and alerting
### Pros and Cons
Pros
Cons
✅ Zero ongoing hosting costs
❌ Requires dedicated hardware
✅ Complete data privacy
❌ Complex networking for remote access
✅ Maximum customization
❌ You handle all maintenance and updates
✅ No vendor lock-in
❌ Hardware failures are your problem
❌ Power and cooling considerations
**Best for:** Privacy-focused developers with spare hardware and strong technical skills. Ideal for those who want complete control and don’t mind the maintenance overhead.
## Implementation Difficulty Comparison
Provider
Technical Skill
Time to Deploy
Requires Docker?
Beginner Friendly?
OpenClaw by xCloud
None
1 minute
No
✅ Yes
Railway
Basic
30-60 minutes
Container knowledge
Some learning
DigitalOcean
Intermediate
1-2 hours
Yes
✅ Documentation helps
Hostinger VPS
Intermediate
2-4 hours
Yes
Self-guided
Kamatera
Intermediate
1-2 hours
Yes
Self-guided
Vultr (GPU)
Advanced
2-3 hours
Yes + GPU
Expert only
Local Hardware
Advanced
4+ hours
Yes
Expert only
## True Cost Breakdown
Understanding the total cost of ownership requires looking beyond base hosting prices. Monthly costs include server hosting, AI model API usage, and the often-overlooked value of your time.
Provider
Server Cost
Typical API Cost
Setup Time Value\*
Monthly TCO
OpenClaw by xCloud
$9.99/mo
Bring Your Own API
$0
$9.99
Hostinger VPS
$4.99/mo
$20-50/mo
$150-300 (one-time)
$25-55
DigitalOcean
$6/mo
$20-50/mo
$100-200 (one-time)
$26-56
Railway
$5-15/mo
$20-50/mo
$50-100 (one-time)
$25-65
Kamatera
$5-20/mo
$20-50/mo
$100-200 (one-time)
$25-70
Vultr (GPU)
$90+/mo
$0 (local)
$200-400 (one-time)
$90+
Local Hardware
$0/mo
$20-50/mo
$300-500 (one-time)
$20-50 + hardware
\*Setup time valued at $50/hour for technical work. API costs based on moderate daily usage with Claude or GPT-4.
### The Hidden Cost: Maintenance Time
Self-hosted solutions require ongoing maintenance—updates, security patches, troubleshooting outages, and configuration changes. Industry estimates suggest 2-4 hours monthly for competent administrators (according to DevOps community surveys). At $50/hour, that’s $100-200/month in time investment that managed solutions eliminate.
## Feature Comparison Matrix
Feature
xCloud
Hostinger
Kamatera
DigitalOcean
Railway
Vultr
Local
One-click deploy
✅
❌
❌
❌
⚠️
❌
❌
Server included
✅
✅
✅
✅
✅
✅
❌
Managed updates
✅
❌
❌
❌
⚠️
❌
❌
Auto backups
✅
❌
❌
❌
❌
❌
❌
Pre-configured Telegram
✅
❌
❌
❌
❌
❌
❌
Pre-configured WhatsApp
✅
❌
❌
❌
❌
❌
❌
Auto-SSL
✅
❌
❌
❌
✅
❌
❌
No Docker needed
✅
❌
❌
❌
❌
❌
❌
Dedicated support
✅
⚠️
✅
⚠️
❌
⚠️
❌
White-label option
✅
❌
❌
❌
❌
❌
❌
GPU available
❌
❌
✅
❌
❌
✅
⚠️
## Common Mistakes to Avoid
### 1\. Underestimating API Costs
The “API Wallet Assassin” problem is real (according to community reports). Moltbot operates in loops, potentially making 10+ API calls for a single request. Without monitoring, simple requests can trigger hundreds of dollars in charges overnight.
**Solution:** Set up billing alerts, implement request limits, and monitor usage closely during initial deployment. Managed providers like xCloud include predictable pricing that eliminates this risk.
### 2\. Skipping Security Hardening
Moltbot requires significant system permissions to function. Running it on your main computer with access to crypto wallets, banking credentials, or sensitive data creates serious security risks.
**Solution:** Use dedicated hardware, isolated environments, strict IP whitelisting, and principle of least privilege. Self-hosters should run Moltbot in sandboxed environments separate from sensitive systems.
### 3\. Ignoring Backup Requirements
Your agent’s persistent memory represents months of learned context. Losing it means starting over with a blank slate.
**Solution:** Implement automated daily backups for the memory store and configuration. Test restore procedures before you need them.
### 4\. Choosing Based on Server Price Alone
The cheapest VPS means nothing if you spend 10 hours setting it up and troubleshooting. Total cost of ownership includes your time investment.
**Solution:** Match provider complexity to your skill level. If you’ve never used Docker, the $15/month savings from self-hosting isn’t worth the learning curve when managed options exist.
### 5\. Neglecting Channel Setup Complexity
WhatsApp integration requires Business API access or complex bridge configurations. Telegram needs bot creation and token management. These aren’t trivial for beginners.
**Solution:** Choose providers with pre-configured channel support if messaging integration is critical to your use case.
## Frequently Asked Questions
### Which hosting provider should I start with?
Start with Clawdbot by xCloud if you want a working AI assistant immediately without technical setup. The $20/month price includes everything—server, updates, channel configuration, and support. Only choose self-hosting if you specifically need customizations that managed hosting doesn’t support.
### Do I need to pay for AI model APIs separately?
With self-hosted options, yes – you’ll pay Anthropic (Claude) or OpenAI (GPT-4) separately based on usage. Typical moderate use runs $20-50/month in API costs on top of hosting. Heavy automation users report $100-300/month. Fully managed solutions like xCloud include AI costs in their pricing.
### How long until my AI assistant is useful?
With managed hosting, you can have a working assistant within minutes. Self-hosted deployments typically take 2-4 hours for initial setup, then days to weeks of refinement. The agent becomes more useful over time as it builds persistent memory and you add custom skills.
### Can non-technical users run Clawdbot/Moltbot?
Yes, but only with fully managed hosting. Self-hosting requires comfort with terminal commands, Docker, and server administration. Industry consensus recommends non-technical users choose managed solutions to avoid frustration and security risks.
### What’s the realistic budget for a personal AI assistant?
Budget $20-75/month for a functional setup. Fully managed solutions like xCloud start at $20/month all-inclusive. Self-hosting starts around $5/month for the server plus $20-50/month for API costs. Add $100-300 in time investment for initial setup if self-hosting.
### Will this work for business automation?
Yes, Moltbot excels at business automation through integrations with Gmail, Google Calendar, CRMs, and project management tools. For business use, managed solutions with SLA guarantees and dedicated support are recommended over self-hosting.
### Is running Moltbot on my main computer safe?
Industry experts strongly advise against this (according to security best practices). Moltbot requires system-level permissions that create security risks. Use dedicated hardware, isolated environments, or managed hosting instead.
### What’s the most underrated option?
Railway offers an excellent middle ground that most users overlook. It handles infrastructure automatically while giving developers control over the application layer, making it ideal for those who want faster deployment than VPS without full managed hosting.
### How often should I update my Moltbot deployment?
Self-hosted users should check for updates weekly, as the project evolves rapidly. Apply security patches immediately. Managed solutions handle updates automatically, eliminating this concern.
### Where can I get help with Moltbot issues?
The official Discord community has 8,900+ members and active contributors. For managed hosting, xCloud provides 24/7 support. Self-hosters rely primarily on community resources, GitHub issues, and documentation.
## Conclusion: Your 2026 AI Assistant Roadmap
The AI assistant landscape has fundamentally shifted with Clawdbot/Moltbot, proving that proactive, action-taking AI agents are no longer science fiction (according to industry analysts). With over 60,000 GitHub stars, this represents one of the fastest-growing open-source projects in history—and choosing the right hosting determines whether you get a working assistant or a frustrating project.
### Expert Picks by Goal
Your Goal
Best Choice
Expected Impact
Best Overall ROI
Clawdbot by xCloud
Working assistant in few minutes, $24/mo all-in
Best for Beginners
Clawdbot by xCloud
Zero technical setup, pre-configured channels
Best for Budget Self-Hosting
Hostinger VPS
Lowest server cost at $4.99/mo + API
Best for Developers
DigitalOcean
Excellent documentation and community
Best for Rapid Prototyping
Railway
Git-push deployment, minimal infrastructure
Best for Privacy Maximalists
Local Hardware
Complete data sovereignty
Best for Enterprise
Clawdbot by xCloud (White-Label)
Managed infrastructure with SLA and branding
### Your Next Step
Don’t let infrastructure complexity prevent you from experiencing what a proactive AI assistant can do. If you want the assistant—not the DevOps project—start with fully managed hosting.
**For immediate deployment:** Sign up at clawdbot.xcloud.host and have your AI assistant running in few minutes seconds. Early adopters lock in launch pricing at just $9.99/month permanently.
**For technical exploration:** Set up a DigitalOcean Droplet or Railway project this weekend and experience the self-hosting process firsthand. You’ll quickly understand whether managed or self-hosted fits your preferences.
The future of AI assistants is here. The only question is whether you’ll spend your time using your assistant or maintaining its infrastructure.
---
# Tips & Best Practices to Prevent Downtime And Boost Website Performance - xCloud
> Keep your website running smoothly! Discover tips to prevent downtime and how hosting providers can optimize site performance for success.
A key problem for any online business, whether large or small, is website downtime. A website usually represents the entire business. So, downtimes can lead to irregular visits to your site, tarnish your business image, and can result in reduced profit. However, there are ways to make sure you [**prevent downtime**](/docs/server-gets-disconnected/) whether you run an eCommerce store to sell products, manage corporate sites, or a blog.
This article will guide you through ways you can **prevent downtime** and ensure that your website is always functional for consistent business growth. We will also highlight how [**xCloud Host**](/) can help you achieve **optimal website performance** and reliability along with providing you with some proactive tips to prevent website downtime.
## **🧑💻 Understanding Website Uptime to Prevent Downtime**
Essentially, [**website uptime**](https://www.catchpoint.com/glossary/website-uptime-monitoring) is the total operational time of a system minus its downtime. It indicates how often your **website is live**, working fully functionally, and available for people to browse.
However, most monitoring tools express this **as a percentage**. This percentage is calculated on the basis of the total operational time with reference to the total time available.
Even though the goal is to **reach 100% availability**, an industry standard of [**99.999%**](https://www.uptrends.com/what-is/website-uptime) is seen as extremely good. In the highly competitive online world, website owners need to ensure their sites are always accessible.
### **Why Is Uptime So Important?**
Imagine your website suddenly disappearing. How would it impact your business? Uptime is not just a technical metric, it is a direct reflection of your [**brand’s reliability**](https://wpdeveloper.com/ways-to-protect-your-brand-reputation/) and customer satisfaction.
**📌 Financial loss:** If your site is not operating properly, your brand is **losing money**, particularly when it is an online business or company that directly makes money on the internet.
**📌 Business reputation:** Once your website goes down, you lose visitors who could be your [**potential customers**](https://notificationx.com/blog/discount-alerts-notify-customers-about-sale/). Plus, your regular customers might divert somewhere else looking for their required products and services. This severely damages your company image.
**📌 Online exposure**: Websites that are often not working can be harder to find on search engines. It reduces your **online visibility** and your business is likely to see the face of a big loss.
Think about what would happen if a big online store’s website stopped working during a big sale. They would lose a lot of profits and the customer might not be satisfied. This reveals how crucial it is for companies to ensure that their website is always up and running and that [**they have strategies**](/tips-to-speed-up-wordpress-websites/) to prevent downtime.
## **💡 Tips to Prevent Downtime: Tried & Tested**
Now that you know how website uptime plays a crucial role in ensuring your business’s growth online, let us learn some tips to prevent downtime.
### **📌 Choose a Reliable Hosting Provider**
Creating a dependable website starts with selecting the **right web hosting company**. Consider a cloud hosting service such as [**xCloud Host**](/), which provides better reliability, scalability, and security than older hosting methods. xCloud ensures **smooth website operation** through its powerful server integration, including [**Vultr**](https://www.vultr.com/), [**Google Cloud**](https://cloud.google.com/), [**AWS**](https://aws.amazon.com/), Hetzner, and DigitalOcean to offer high-speed performance, robust security, and automatic scaling. Plus, you can **integrate any server** and connect to xCloud to maximize a personalized experience.
#### **Key Features of xCloud Hosting**
**xCloud** is more than just a hosting service. It is a fully **managed hosting** solution for WordPress designed for ease of use and exceptional performance. Here is why xCloud stands out with its [**extensive features**](/features/):
**🌟 Lightning-fast performance:** Optimized for speed with **NGINX LEMP** Stack, OLS Stack, and page/object caching options.
**🌟 Enhanced security:** Advanced security measures, site isolation, SSL certificates, SFTP/SSH, Fail2Ban, automated firewall protection, and 7G/8G firewall.
**🌟 Seamless integrations:** Integrate with cloud servers, email providers, DNS management, storage options, and Slack/WhatsApp for notifications.
**🌟 Simplified server management:** Utilize full root access, auto-healing, unlimited Sudo users and site deployments, advanced log viewer, automation with Cron jobs, and server/site health monitoring for simplified server management.
**🌟 Efficient site management:** xCloud Host offers advanced extensive features for seamless site management, including staging environments, backup/restore, multiple PHP versions, SFTP/SSH access, multisite, file manager, blueprints, custom NGINX config, WordPress Magic login, WP-Cron/xCloud Cron – all you need in a single place.
**🌟 Streamlined team collaboration:** One account for multiple teams, user roles, user access control, and easy team management.
### **📌 Regularly Monitor Website Performance**
Regularly checking how well your website is working is crucial to **finding any problems** before they cause your site to stop working. Use tools that give you instant warnings if pages are loading slowly, if there are server mistakes, or if there is unusual activity. By watching these details, you can quickly fix problems to prevent website downtime.
#### **Tips for Effective Monitoring**
Good monitoring is important for keeping a website running well and fast. By following these tips to prevent downtime, you can fix issues before they come up and ensure a smooth experience.
**🌟 Set up warnings:** Make warnings for big issues like server overload, high computer use, or sudden big jumps in visitors.
**🌟 Look at visitor numbers:** Knowing when the most people visit helps you get ready for possible overloads.
**🌟 Check regularly:** Plan regular checks to make sure your website stays fast and works well.
### **📌 Implement a Content Delivery Network (CDN)**
A [**Content Delivery Network (CDN)**](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) is a group of servers spread out across various places around the world. A CDN makes websites **load faster** by storing things like **pictures, styles**, and scripts on these servers and giving them to users from the server closest to them. This makes the main server work less and makes the website run better.
Using a CDN can greatly lower the chance of your website going down, especially when many people visit simultaneously. xCloud Hosting works well with top CDN companies, making sure your content reaches users quickly and without problems all over the world.
#### **Benefits of Using a CDN**
A Content Delivery Network (CDN) provides many benefits for companies looking to **enhance their website’s speed**, security, and ability to reach a global audience. Here are a few key advantages:
**🌟 Faster loading:** Quick content delivery lowers the chance of website crashes due to too much traffic.
**🌟 Better security:** CDNs add extra security features, like protection against DDoS attacks.
**🌟 Worldwide access:** Ensures a smooth experience for users no matter where they are located.
### **📌 Regularly Backup Your Website**
Regularly backing up your website is very important because it helps you quickly fix any problems, like server issues, security problems, or data mistakes. Automated backups let you bring your website back to an earlier time with little trouble.
xCloud Hosting offers [**automatic daily backups**](/docs/site-backups-in-xcloud/), so your website’s information is safe and can be quickly fixed if something goes wrong.
#### **Backup Best Practices**
Having a good backup plan is key to keeping your website’s data safe and making sure your business keeps running. Follow these tips to protect your important information.
**🌟 Set up automatic backups:** Plan for backups every day or week to avoid mistakes.
**🌟 Keep backups somewhere safe:** Store backups in a secure place away from your main server to prevent data loss if the server fails.
**🌟 Check backup fixes:** Regularly test restoring from backups to make sure they work properly.
### **📌 Secure Your Website**
Security issues are a major reason why websites go down. A successful cyberattack can shut down your website, steal user information, and harm your reputation. So, it is crucial to take [**strong security measures**](/docs/server-and-website-security-with-xcloud/) to **protect your website** from possible threats and prevent downtime.
xCloud Hosting provides complete security features, such as firewalls, malware checks, and **DDoS protection**, to keep your website safe from attacks.
#### **Security Measures to Implement**
Are you sure your website is safe from cyberattacks? Do not take any risks. Find out about the key security steps you should take to protect your business.
**🌟 SSL certificates:** [**Encrypt the data**](/docs/install-lets-encrypt-ssl-certificate/) sent between your website and users to prevent it from being intercepted.
**🌟 Regular security updates:** Keep your software, plugins, and themes updated to avoid vulnerabilities.
**🌟 DDoS protection:** Use [**protection against**](/docs/security-and-vulnerability-disclosure-protocols/) Distributed Denial of Service (DDoS) attacks to keep your website running during an attack.
### **📌 Optimize Your Website for Performance**
A well-optimized website [**improves user experience**](https://wpdeveloper.com/increase-traffic-improve-user-experience/) and lowers the chances of it going offline. Slow pages can cause server issues, especially when there is a lot of traffic. So, making your website faster clearly has no alternative.
xCloud Hosting provides tools to help you make your website faster, like caching, image compression, and managing your database.
### **Tips for Making Your Website Faster**
Making your website faster is crucial for a good user experience and [**better search results**](https://wpdeveloper.com/wordpress-site-seo-checklists/). Here are some tips to help your website load quicker and work better.
**🌟 Reduce HTTP requests:** Cut down on the number of things on your pages to make them load faster.
**🌟 Use browser caching:** Let users’ browsers save parts of your website, which reduces the server’s work.
**🌟 Compress images:** Use tools to make images smaller without losing quality.
### **📌 Plan for Disaster Recovery**
Even with your best efforts, downtime can happen because of **unexpected events** like natural disasters, hardware problems, or cyberattacks. Having a disaster recovery plan helps you quickly get your **website back online** even if you fail to prevent downtimes.
xCloud Hosting offers strong **disaster recovery options**, including automatic failover systems and data copying across many servers.
#### **Parts of a Disaster Recovery Plan**
A well-thought-out disaster recovery plan is a must for **keeping your website safe** from sudden outages. By taking these steps, you can prevent downtime and make sure your business keeps running.
**🌟 Identify important parts:** Figure out which parts of your website are most important and focus on getting them back first.
**🌟 Automatic failover:** Make sure your website can automatically move to a backup server if something goes wrong.
**🌟 Regular testing:** Test your disaster recovery plan often to make sure it works well and is up to date.
### **📌 Leverage Cloud Hosting for Better Reliability**
Traditional hosting methods sometimes cannot meet the needs of today’s websites, which can cause more chances of your site going offline. Cloud hosting, like [**xCloud Hosting**](https://wpdeveloper.com/why-we-built-xcloud/#:~:text=Besides%2C%20when%20you%20have%20multiple,users%20as%20well%20as%20newcomers.), provides a more reliable service by letting you take advantage of **choosing from multiple servers** for your website. This means that even if one server stops working, your website will still be available.
With xCloud Hosting, you can easily **adjust your resources** to match the amount of visitors you get, making sure your website stays up even when there are sudden increases in traffic.
#### **Advantages of Cloud Hosting**
Imagine experiencing a sudden surge in website traffic during a viral event. Cloud hosting can help you **scale your resources** quickly to accommodate the increased demand and prevent website downtime.
**🌟 High availability:** Multiple servers ensure that your website remains online, even in the event of a server failure.
**🌟 Scalability:** Easily scale resources to match your website’s needs to **prevent downtimes** and overloads.
**🌟 Cost-effective:** Pay only for the resources you use, making cloud hosting a cost-effective solution for maintaining uptime.
## **🚀 Utilize the Best Hosting & Prevent Downtime for Consistent Growth**
Keeping your website online is very important for your online success. By using these tips and the advanced tools from xCloud Hosting, you can greatly **prevent downtime** and make sure your website is always available for visitors. Remember, an always-available website is key to a successful business.
With xCloud Hosting, you have a team committed to **keeping your website running well**, so you can concentrate on growing your business without stressing about downtime.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# 7 Best RunCloud Alternatives in 2026: Manage WordPress Servers Affordably (Complete Guide) - xCloud
> Discover the 7 best RunCloud alternatives in 2026. Compare free tiers, pricing, WordPress features, and find the most affordable server panel.
Server management panels have become essential for WordPress professionals, with the global cloud management market projected to reach $17.1 billion by 2026 _(according to MarketsandMarkets)_.
While RunCloud has served the WordPress community well, recent pricing changes and the discontinuation of their free tier have prompted developers, agencies, and site owners to actively search for RunCloud Alternatives that deliver better value, flexibility, and long-term scalability.
Read this guide to learn about the top RunCloud Alternatives based on hands-on testing, verified user reviews from Trustpilot and G2, and recommendations from industry experts. Each RunCloud alternative was evaluated for pricing, WordPress optimization, support quality, and scalability.
Whether you’re managing a single WordPress site or running an agency with dozens of clients, you’ll find a solution that matches your requirements and budget.
## Table of Contents
## Quick Summary / TL;DR
Too Long; Didn’t Read? Here’s what you need to know about the best RunCloud Alternatives available in 2026:
If You Want To…
Use This
Expected Savings
Setup Time
Get a free tier with unlimited sites
xCloud
Up to 40% vs RunCloud
5 minutes
Maximum WordPress optimization
GridPane
Premium performance
15 minutes
Affordable multi-app hosting
ServerAvatar
$0 starting price
10 minutes
WordPress-focused simplicity
SpinupWP
70% vs managed hosts
8 minutes
Laravel + WordPress flexibility
Ploi
€8/month starting
12 minutes
**Industry Expert Pick for Beginners**: Among all of the RunCloud Alternatives, xCloud offers a genuinely free tier with 1 server and 10 sites, plus a 5-star Trustpilot rating from 297+ verified reviews, making it one of the most beginner-friendly RunCloud Alternatives.
**Best for WordPress Agencies:** GridPane is purpose-built for WordPress professionals with advanced security and Object Cache Pro integration.
**Best for Budget-Conscious Users:** ServerAvatar has a $0/month starting tier with WordPress, PHP, and Node.js support.
## Why WordPress Professionals Are Seeking RunCloud Alternatives in 2026
The server management landscape has shifted significantly. [**According to W3Techs**](https://w3techs.com/technologies/details/cm-wordpress), WordPress powers 43.5% of all websites globally, creating massive demand for efficient server management tools. Here’s why professionals are exploring alternatives:
**Pricing Structure Changes:** RunCloud’s Essentials plan starts at $9/month for a single server, while many modern **RunCloud Alternatives** now offer free tiers or far more generous entry-level plans.
**Free Tier Discontinuation:** RunCloud no longer offers a free tier, pushing budget-conscious users toward alternatives that still provide no-cost options.
**Feature Gaps:** Some users report that advanced features like one-click app deployment for tools like n8n, Mautic, and custom Docker stacks require higher-tier plans or aren’t available at all — a key reason many users migrate to more flexible **RunCloud Alternatives**.
**Support Limitations:** [**According to G2 reviews**](https://www.g2.com/products/runcloud-io/reviews), support on lower-tier RunCloud plans can be limited, with some users noting that “you are on your own with your configuration and applications.”
## **How We Ranked These Alternatives**
The evaluation methodology for these **RunCloud alternatives** follows industry-standard criteria used by hosting experts at publications like WPBeginner and HostingAdvice, ensuring each RunCloud alternative is compared fairly and objectively.
Criterion
Why It Matters
Weight
**Pricing & Value**
Total cost including all needed features
High
**Free Tier Availability**
Entry barrier for testing/small projects
High
**WordPress Optimization**
Caching, staging, one-click installs
High
**User Reviews**
Trustpilot, G2, Capterra ratings
Medium
**Cloud Provider Support**
DigitalOcean, Vultr, AWS, Hetzner, etc.
Medium
**Support Quality**
Response time, technical depth
Medium
**Feature Breadth**
Backups, SSL, monitoring, team management
Medium
## Master Comparison Between the Best RunCloud Alternatives
Rank
Platform
Rating
Free Tier
Starting Price
Best For
🥇
**xCloud**
★★★★★
✅ Yes (1 server, 10 sites)
$0/month
WordPress professionals wanting free tier + growth
🥈
**GridPane**
★★★★★
✅ Yes (Core plan, 25 sites)
$0/month
Agencies demanding maximum WordPress performance
🥉
**ServerAvatar**
★★★★☆
✅ Yes (1 server, 1 site)
$0/month
Multi-stack developers (PHP, Node.js, WordPress)
4
**SpinupWP**
★★★★☆
❌ No
$12/month
WordPress developers wanting clean simplicity
5
**Ploi**
★★★★☆
✅ Yes (1 server, 1 site)
€8/month
Laravel and WordPress hybrid projects
6
**Moss.sh**
★★★☆☆
✅ Yes (1 integration)
$0/month
Teams needing collaboration features
7
**CloudPanel**
★★★★☆
✅ Yes (Open source)
$0/month
Self-hosted enthusiasts wanting full control
## 🥇 xCloud – Best for WordPress Professionals Seeking Value
[**According to Trustpilot**](https://www.trustpilot.com/review/xcloud.host), xCloud has emerged as a leading alternative with a 5-star rating from 297+ verified users. The platform, developed by [**WPDeveloper**](https://wpdeveloper.com/) (the team behind [**Essential Addons for Elementor**](https://essential-addons.com/) with 2M+ active users), has rapidly gained recognition for combining enterprise features with accessible pricing.
What sets xCloud apart from other RunCloud alternatives is its genuinely free tier that includes 1 server and 10 sites – a significant advantage over RunCloud’s paid-only model.
Users consistently report substantial cost savings, with [**Online Media Masters**](https://onlinemediamasters.com/xcloud-review/) noting “up to 40% cost savings at equivalent specs” when comparing to other managed solutions.
The platform supports major cloud providers, including Vultr, DigitalOcean, AWS, Hetzner, Google Cloud, and Linode, giving users flexibility in choosing their infrastructure. Beyond WordPress, xCloud offers one-click deployment for [n8n](/n8n-hosting/) automation workflows, Mautic marketing automation, and custom Docker stacks.
Real user feedback highlights why xCloud is quickly becoming one of the most talked-about RunCloud Alternatives, especially among WordPress freelancers and agencies seeking fast iteration and responsive support. One Trustpilot reviewer shared: “Nearly every suggestion I and others in their Facebook group have shared has been acknowledged, considered, discussed, and in a huge chunk of cases, have actually been implemented… that’s rare in this industry.”
Another user noted significant cost savings: “[**Reduced server costs by 60%**](https://xcloud.host/case-studies/wattz-web-design/) when I switched to xCloud from shared cPanel hosting. Had a few hiccups but nothing xCloud’s amazing support couldn’t handle.”
### Key Features
- **Free Tier:** 1 server, 10 sites, unlimited bandwidth.
- **One-Click Apps:** WordPress, WooCommerce, n8n, Mautic, LLM hosting, and 15+ applications
- **Server Stacks:** LEMP, OpenLiteSpeed, MERN — choose based on your needs
- **Caching:** Full-page NGINX FastCGI caching and Redis Object caching
- **Security:** Free SSL, automatic updates, isolated environments
- **Backups:** Automated backups to AWS S3, DigitalOcean Spaces, or any S3-compatible storage
### How to Get Started with xCloud?
Getting started with xCloud is pretty simple. Follow these steps:
**Option A(Free Tier** **Availabe):**
1. Sign up at xCloud.
2. Connect your cloud provider (Vultr, DigitalOcean, etc.)
3. Deploy your first server in under 5 minutes
4. Install WordPress with one click
**Option B: Managed Hosting**
Choose xCloud’s managed server option starting at $5/month for a fully managed experience with included server resources.
**Helpful Resources:**
- [**How to Create Your First Server with xCloud**](https://xcloud.host/docs/)
- [**WordPress Installation Guide**](https://xcloud.host/docs/)
### Pros and Cons
Pros
Cons
✅ Genuinely free tier with 10 sites
❌ Newer platform (launched 2024)
✅ 5-star Trustpilot rating (297+ reviews)
❌ Email hosting still maturing
✅ One-click n8n, Mautic, Docker deployment
❌ Some advanced features require paid plans
✅ White-label reseller option included
✅ 24/7 support with video call option
**Best for:** WordPress developers, agencies, and freelancers who want enterprise-grade features without enterprise pricing and are evaluating modern **RunCloud Alternatives**. Ideal for those migrating from RunCloud who need a free tier to test before committing.
## 🥈 GridPane – Best for WordPress Agencies Demanding Performance
[**GridPane**](/xcloud-gridpane/) has built a strong reputation among serious WordPress professionals, hosting over 120,000 websites according to their official data. The platform focuses exclusively on WordPress, making it the go-to choice for agencies and developers who prioritize performance and security above all else.
[**According to G2 reviews**](https://www.g2.com/products/gridpane/reviews), GridPane users consistently praise its performance capabilities, with one reviewer noting: “None of the alternative cloud web hosting control panels offer the same level of performance.” The platform includes premium features like Object Cache Pro integration and Fortress security, typically available only in expensive enterprise solutions.
GridPane introduced a free Core plan in late 2025, allowing users to host up to 25 websites on Vultr or their managed PeakFreq servers. This democratizes access to enterprise-grade WordPress hosting for smaller operations.
### Key Features
- **Free Core Plan:** 25 websites, server page caching, Redis object caching, 7G Firewall
- **WordPress-Specific:** WP-CLI, staging environments, WordPress multisite support
- **Security:** Fortress security, Fail2Ban, malware scanning with Maldet + ClamAV
- **Performance:** Object Cache Pro integration, OpenLiteSpeed or Nginx stacks
- **Team Features:** Client portal, white-label branding (higher tiers)
### How to Get Started with GridPane?
**Option A: Free Core Plan**
1. Sign up for GridPane Core (free)
2. Connect your Vultr account or use PeakFreq managed servers
3. Provision your first WordPress-optimized server
4. Deploy sites with built-in security and caching
**Option B: Panel Plan ($100/month)**
Unlock unlimited servers, 50 sites, and support ticket access for growing agencies.
### Pros and Cons
Pros
Cons
✅ Free tier with 25 sites
❌ WordPress-only (no Laravel, Node.js)
✅ Object Cache Pro integration
❌ Paid plans start at $100/month
✅ Enterprise security (Fortress)
❌ Learning curve for non-technical users
✅ Excellent Facebook community support
❌ Limited cloud provider integrations on free tier
✅ Snapshot failover for disaster recovery
**Best for:** WordPress agencies managing 20+ client sites who need maximum performance, advanced security, and don’t mind the WordPress-only limitation.
## 🥉 ServerAvatar – Best for Multi-Stack Developers on a Budget
[**ServerAvatar**](/xcloud-vs-serveravatar/) stands out as a versatile platform supporting WordPress, Laravel, PHP, and Node.js applications — making it ideal for developers working across multiple technology stacks. With a free tier that includes 1 server and 1 site, it’s accessible to beginners while scaling to enterprise needs.
[**According to G2 reviews**](https://www.g2.com/products/serveravatar/reviews), ServerAvatar has earned recognition for its balance of pricing and features. One verified reviewer noted: “ServerAvatar has been fantastic, striking the perfect balance of competitive pricing, good server availability, and highly knowledgeable technical support.”
The platform integrates with 100+ cloud providers, offering flexibility that few competitors match. ServerAvatar also provides a white-label suite for agencies wanting to resell hosting under their own brand.
### Key Features
- **Free Tier:** 1 server, 1 site, essential features included
- **Multi-Stack:** WordPress, Laravel, PHP, Node.js support
- **One-Click Apps:** WordPress, n8n, Mautic, Nextcloud, Moodle, and 15+ applications
- **Server Stacks:** Apache, Nginx, OpenLiteSpeed, MERN
- **Security:** 8G Firewall, Fail2ban, isolated environments
- **Team Management:** Roles, permissions, and alias credentials
### How to Get Started with ServerAvatar?
**Option A: Free Tier ($0/month)**
1. Create a ServerAvatar account
2. Connect your VPS provider (Vultr, Hetzner, DigitalOcean, etc.)
3. Provision a server with your preferred stack
4. Deploy applications via one-click installer
**Option B: Tier 2 ($19/month)**
Unlock up to 25 self-managed servers with team management features.
### Pros and Cons
Pros
Cons
✅ $0 free tier available
❌ Panel not multi-language
✅ Supports 100+ cloud providers
❌ No ModSecurity one-click setup
✅ WordPress + Node.js + Laravel support
❌ Site migration could be smoother
✅ White-label reseller included
✅ Active Facebook community (4.8/5 rating)
**Best for:** Full-stack developers and agencies managing diverse projects across WordPress, Laravel, and Node.js who need maximum provider flexibility at minimum cost.
## 4\. SpinupWP – Best for WordPress Developers Wanting Simplicity
[**SpinupWP**](/xcloud-vs-spinupwp/), created by the team behind WP Migrate, has earned a reputation as one of the cleanest and most developer-friendly RunCloud Alternatives for WordPress-focused professionals. The platform bridges the gap between “scary self-hosting and expensive managed hosting,” as their community describes it.
[**According to Capterra reviews**](https://www.capterra.com/p/10012241/SpinupWP/), SpinupWP users consistently praise its simplicity: “SpinupWP made setting up and managing my own WordPress server super simple. The dashboard is powerful yet intuitive, and the documentation is comprehensive and helpful.”
While SpinupWP doesn’t offer a free tier, its $12/month Personal plan includes all essential features, making it competitive for serious WordPress developers.
### Key Features
- **WordPress-Focused:** Optimized specifically for WordPress with built-in caching and security
- **Clean Dashboard:** Intuitive interface with excellent documentation
- **Git Deployment:** Push code directly from GitHub, GitLab, or Bitbucket
- **Staging:** One-click staging environments for testing
- **Backups:** Automated backups to Amazon S3, DigitalOcean Spaces, etc.
- **REST API & CLI:** Full programmatic control for automation
### How to Get Started with SpinupWP?
**Option A: Personal Plan ($12/month)**
1. Start the free trial.
2. Connect DigitalOcean, Vultr, Linode, or other supported providers
3. Spin up your first WordPress-optimized server
4. Add sites with automatic SSL configuration
**Option B: Team Plan ($39/month)**
Add team members, unlimited servers, and priority support.
### Pros and Cons
Pros
Cons
✅ Best-in-class documentation
❌ No free tier available
✅ Clean, intuitive dashboard
❌ WordPress/PHP only (no Node.js)
✅ Git deployment built-in
❌ No file manager in dashboard
✅ Free plan available
❌ Pricing per-server model
✅ Created by trusted WP developers
**Best for:** WordPress developers who value clean design, excellent documentation, and don’t mind paying for a premium experience. Ideal for those who found managed hosting too restrictive.
## 5\. Ploi – Best for Laravel and WordPress Hybrid Projects
[**Ploi**](https://ploi.io/) has carved out a niche as the preferred server management tool for Laravel developers who also work with WordPress. The platform’s Laravel optimization is unmatched, while still providing solid WordPress support with one-click installation.
[**According to SaaSworthy**](https://www.saasworthy.com/product/ploi-io), Ploi is “generally praised for its ease of use, comprehensive features, and affordability.” The platform starts at €8/month (approximately $10), making it one of the most affordable paid options available.
Ploi’s 2025 recap highlighted significant improvements, including IPv6 support, a CLI tool for terminal-based management, and making Ploi Core completely free and open-source.
### Key Features
- **Laravel Optimized:** Automatic detection and environment editor
- **WordPress Support:** One-click WordPress installation
- **Git Deployment:** GitHub, GitLab, Bitbucket with auto-deploy on push
- **Load Balancers:** Easy load balancer setup
- **DNS Management:** Built-in DNS record management
- **Notifications:** Email, Slack, Discord, Telegram, and mobile app alerts
### Pros and Cons
Pros
Cons
✅ Best Laravel integration
❌ Support can be slow on basic plans
✅ Affordable €8/month starting price
❌ Less WordPress-specific features
✅ 5-day free trial
❌ Limited documentation in some areas
✅ Open-source Ploi Core
❌ Node.js support not out-of-box
✅ Active development and updates
**Best for:** Developers who work primarily with Laravel but also maintain WordPress projects. The €8/month starting price makes it accessible for freelancers and small agencies.
## 6\. Moss.sh – Best for Team Collaboration
**Moss** positions itself as a “virtual sysadmin” that handles server management tasks while enabling team collaboration. The platform is unique in its approach to connecting team members around shared server infrastructure.
With a free tier that includes 1 integration and 25 Git deployments, Moss offers an accessible entry point for small teams. The platform supports WordPress, Laravel, Symfony, and other PHP applications.
### Pros and Cons
Pros
Cons
✅ Free tier available
❌ No backup functionality
✅ Team collaboration focus
❌ Ubuntu only
✅ Zero downtime deployments
❌ Server monitoring costs extra
✅ Clean interface
❌ Limited cloud provider integrations
**Best for:** Development teams who need collaboration features and zero-downtime deployments. Less suitable for solo developers or WordPress-only users.
## 7\. CloudPanel – Best for Self-Hosted Control
**CloudPanel**, is a free, open-source server control panel that has gained significant traction among users searching for self-hosted RunCloud Alternatives with complete control and zero licensing fees.
As an open-source solution, there are no licensing fees — ever.
The platform supports PHP, Node.js, Python, and static sites, making it versatile for various web applications. CloudPanel is particularly popular among users coming from cPanel who want a modern alternative without monthly fees.
### Pros and Cons
Pros
Cons
✅ 100% free and open-source
❌ Self-managed (you handle updates)
✅ No licensing fees ever
❌ No managed server option
✅ Modern, clean interface
❌ Limited compared to paid panels
✅ Active community support
❌ Requires more technical knowledge
**Best for:** Technically proficient users who want maximum control without any recurring panel costs. Ideal for self-hosted enthusiasts and budget-constrained projects.
## Feature Comparison Matrix
Feature
xCloud
GridPane
ServerAvatar
SpinupWP
Ploi
Free Tier
✅
✅
✅
❌
✅
WordPress One-Click
✅
✅
✅
✅
✅
n8n Deployment
✅
❌
✅
❌
❌
Node.js Support
✅
❌
✅
❌
❌
Laravel Support
✅
❌
✅
❌
✅
Team Management
✅
✅
✅
✅
✅
White-Label
✅
✅
✅
❌
❌
OpenLiteSpeed
✅
✅
✅
❌
❌
Object Caching
✅
✅
✅
✅
✅
Git Deployment
✅
✅
✅
✅
✅
## Cost Breakdown: Free vs Paid Options
Platform
Free Option
First Paid Tier
Best Value Plan
xCloud
1 server, 10 sites
$5/mo (managed)
Pro at $19/mo
GridPane
25 sites (Core)
$100/mo (Panel)
Panel at $100/mo
ServerAvatar
1 server, 1 site
$19/mo (Tier 2)
Tier 2 at $19/mo
SpinupWP
Free trial only
$12/mo (Personal)
Team at $39/mo
Ploi
1 server, 1 site
€8/mo
Unlimited at €30/mo
Moss.sh
1 integration
$9/mo (Starter)
Professional at $19/mo
CloudPanel
Full (open-source)
N/A
N/A (free)
## Common Mistakes to Avoid When Switching
1. **Not Testing Migration First:** Always test your migration on a staging site before moving production. Most platforms offer free trials — use them.
2. **Ignoring Server Location:** Choose a data center close to your audience. All platforms support multiple regions — select wisely.
3. **Overlooking Backup Strategy:** Even with built-in backups, maintain off-platform backups. Connect to S3, DigitalOcean Spaces, or similar.
4. **Choosing Based on Price Alone:** The cheapest option isn’t always best. Consider support quality, features you’ll actually use, and long-term scalability.
5. **Forgetting DNS TTL:** Before migration, lower your DNS TTL to 300 seconds (5 minutes) at least 24-48 hours ahead to enable faster propagation.
6. **Not Documenting Current Setup:** Screenshot your RunCloud configurations, note PHP versions, caching settings, and custom rules before switching.
## Frequently Asked Questions
### Which RunCloud alternative should I start with?
Start with xCloud if you want a free tier with room to grow. Among all RunCloud Alternatives, it offers the most generous free plan while remaining scalable for agencies and professionals. It offers the most generous free plan (1 server, 10 sites) and has earned a 5-star Trustpilot rating. For WordPress-only with maximum performance, GridPane’s free Core plan is excellent
### Do I need to pay for a server management panel?
No, several alternatives offer genuinely free tiers. xCloud, ServerAvatar, GridPane (Core), and CloudPanel all have free options. However, paid plans typically include better support and advanced features like team management and white-labeling
### How long does migration from RunCloud take?
Most migrations complete in 1-3 hours per site depending on database size. Platforms like xCloud and ServerAvatar offer free migration tools. Plan for DNS propagation time (up to 24-48 hours) after the technical migration.
### Can I manage non-WordPress sites with these alternatives?
Yes, ServerAvatar, Ploi, and xCloud support Laravel, PHP, Node.js, and other applications. GridPane and SpinupWP are WordPress-only. CloudPanel supports PHP, Node.js, Python, and static sites.
### What’s the most underrated RunCloud alternative?
ServerAvatar is often overlooked despite offering WordPress, Laravel, Node.js, and 100+ cloud provider integrations at $0/month starting. Users report support that “spent hours running tests until problems were completely fixed.
### Will these alternatives work for WooCommerce stores?
Yes, all platforms support WooCommerce. GridPane and xCloud are particularly optimized for WooCommerce with Redis object caching and performance-tuned stacks. For high-traffic stores, GridPane’s Object Cache Pro integration is valuable.
### How do I know if my server resources are adequate?
All platforms provide server monitoring. Start with 2GB RAM for small-medium WordPress sites. Monitor CPU and memory usage for 1-2 weeks, then scale as needed. Most platforms allow vertical scaling without migration.
### What happens to my sites if I cancel my panel subscription?
Your sites remain on your cloud server – you just lose panel access. You’d need to manage via SSH/command line or migrate to another panel. This is why self-hosted options like CloudPanel are attractive for maximum control.
### Can I try multiple alternatives simultaneously?
Absolutely, and you should. Use free tiers to test interfaces, performance, and support responsiveness. Many professionals maintain accounts on 2-3 platforms for different use cases or client requirements.
### Where can I get help if I’m stuck during migration?
Most platforms offer documentation and community forums. xCloud provides 24/7 support with video call options. GridPane has an active Facebook community. SpinupWP’s documentation is considered industry-leading.
## Your 2026 Server Management Roadmap
The server management panel landscape offers more choice than ever, with RunCloud Alternatives now outperforming traditional panels in pricing, flexibility, and feature depth. Based on the analysis above, here are the expert picks by goal:
### Expert Picks by Goal
Your Goal
Best Choice
Why
Best Free Tier
xCloud
1 server, 10 sites
Maximum WordPress Performance
GridPane
Object Cache Pro, Fortress security
Multi-Stack Development
ServerAvatar
WordPress + Node.js + Laravel
Simplest WordPress Experience
SpinupWP
Clean UI, excellent docs
Laravel + WordPress
Ploi
Best Laravel integration
Complete Control (Self-Hosted)
CloudPanel
100% free, open-source
### Action Plan
- **Get started:** Sign up for free tiers on xCloud and GridPane to test interfaces and performance
- **Within 30 Days:** Migrate one non-critical site to your chosen platform and monitor for 2-3 weeks
- **Within 60 Days:** Complete full migration from RunCloud, maintaining documented configurations
The WordPress server management ecosystem continues to evolve rapidly. The alternatives highlighted in this guide represent the current state of the industry, each offering unique advantages for different use cases. Choose the platform that aligns with your technical requirements, budget constraints, and growth trajectory and don’t hesitate to test multiple RunCloud Alternatives before committing long-term.
---
# 6 Best SMTP and Email API Providers for SaaS [2026] - xCloud
> Compare the 6 best SMTP and email API providers for SaaS in 2026: xCloud, Mailtrap, Postmark, Mailgun, Amazon SES, and SendGrid. Pricing, features, trade-offs.
Email is one of the most under-budgeted parts of a typical SaaS stack. The same SMTP relay or email API quietly handles signup verifications, password resets, billing receipts, and real-time alerts. If any of those fail, you lose user trust fast. Sender reputation takes weeks to build and one bad weekend to wreck. Picking the right provider is engineering work, not a marketing decision.
The six best SMTP and email API providers for SaaS in 2026 are **xCloud Mail Delivery, Mailtrap, Postmark, Mailgun, Amazon SES, and SendGrid**. If you run a SaaS app on [**xCloud**](/), the Mail Delivery addon plugs in without any third-party setup. The other five connect through SMTP credentials or REST APIs into Node.js, Laravel, or PHP applications.
The comparison table and decision map below will help you figure out which service matches your stack.
## **Best SMTP and Email API Providers for SaaS: Quick Comparison**
**Provider**
**Primary focus**
**Stream separation**
**Free tier**
**Starting paid plan**
**SDK languages**
**xCloud Mail Delivery**
Native integration with xCloud-hosted apps
Managed (powered by Elastic Email)
100 emails/mo
$1/mo for 100 emails, $3/mo for 3,000 emails
SMTP works with any mail library; native xCloud config
Mailtrap
High deliverability
Native
4,000 emails/mo
$15/mo for 10K emails
Node.js, Ruby, PHP, Python, .NET, Elixir, Java
Postmark
Inbox delivery speed
Native
Trial only
$15/mo for 10K emails
Node.js, PHP, Python, Ruby, .NET, Java, Go
Mailgun
API routing and pre-send validation
Manual
100 emails/day
$15/mo for 10K emails
Node.js, Python, PHP, Ruby, Java, Go, C#
Amazon SES
Cost efficiency for AWS-native SaaS
Manual
3,000 emails/mo from EC2
$0.10 per 1K emails
Full AWS SDK: JS, Python, Java, Go, Ruby, PHP, .NET, Rust, C++, Kotlin
SendGrid
Omnichannel integration
Manual
100/day during 60-day trial
$19.95/mo for 50K emails
Node.js, PHP, Python, Ruby, Java, Go, C#
## **How to Choose the Best SMTP and Email API for Your SaaS in 2026?**
Each SMTP and Email API provider optimizes for a different problem. Some prioritize inbox speed, others minimize cost, and others give you routing control at the expense of setup time. The decision map below matches each provider to the constraint it handles best.
**Decision map:**
- Choose **xCloud Mail Delivery** when you already run your SaaS on xCloud and want transactional email handled inside the same control panel, with no separate vendor account or DNS plumbing for a third party.
- Choose **Mailtrap** when you require high deliverability with native stream separation out of the box.
- Choose **Postmark** when transactional inbox speed matters more than per-send cost.
- Choose **Mailgun** when pre-send email validation and per-domain routing rules are core to your workflow.
- Choose **Amazon SES** when your SaaS already runs on AWS and per-email cost is the binding constraint.
- Choose **SendGrid** when you need broad SDK coverage and want SMS or voice unified under Twilio billing.
Our recommendations are based on the following criteria:
- **Deliverability infrastructure** – stream separation, dedicated IPs, authentication automation, IP warmup
- **Ease of integration** – SDK coverage, setup time, framework and platform support
- **Multi-tenant and transactional email support** – per-domain isolation, template management, support for recurring account-triggered flows (verification, billing, alerts)
- **Analytics and observability** – delivery tracking, bounce and complaint reporting, per-provider breakdown
- **Total cost of ownership** – base pricing, overage fees, dedicated IP costs, engineering time for setup and maintenance
## **xCloud Mail Delivery: Best for SaaS Apps Hosted on xCloud**
[**xCloud Mail Delivery**](/mail-delivery/) is the native SMTP addon built into the xCloud control panel. Instead of opening an account with a separate provider, verifying DNS records on a third-party dashboard, and copying SMTP credentials between two systems, you enable Mail Delivery from the same panel where your sites live. The addon runs on Elastic Email’s infrastructure under the hood, so you get a managed sending network without setting one up yourself.
### **Key features**
- **Setup inside the xCloud panel:** Pick a plan, generate SMTP credentials, and connect your domain — all from the addon dashboard. The SMTP host, port, username, and password drop into your site’s Email Config tab without ever leaving xCloud. For WordPress sites, the integration also wires into the Mail Delivery addon at the site level.
- **Authentication.** SPF, DKIM, and DMARC are handled through the addon. The panel walks you through domain verification, and a default DMARC policy is applied automatically. You can override it with your own policy if you need stricter rules for a particular domain.
- **Deliverability infrastructure.** Mail Delivery routes through reputable shared IPs with active reputation management, anti-spam filtering, and abuse protection. Email tracking links can be stripped automatically so the recipient sees a clean message body.
- **Real-time analytics.** Sending logs, delivery status, and basic analytics live in the same dashboard as your servers and sites. No second tab open to a vendor portal.
- **Works with any stack.** Because Mail Delivery exposes standard SMTP credentials, it works with Laravel’s Mailable classes, Node.js libraries like Nodemailer, PHP’s PHPMailer, and any WordPress SMTP plugin. There’s no SDK lock-in — the same credentials work everywhere SMTP works.
- **No mail server on your web host.** xCloud explicitly recommends against running a mail daemon on the same server as your sites for security and performance reasons. Mail Delivery is the supported alternative, with mail handled on infrastructure built for it.
### **Pricing**
The free tier covers 100 emails per month. Paid plans start at **$3/month for 3,000 emails**, then $4/month for 4,000 emails, and $12/month for 10,000 emails. There is no separate dedicated IP add-on at this tier, the service is built around shared, reputation-managed infrastructure.
### **Why it works for SaaS**
If your SaaS already runs on xCloud, Mail Delivery removes a moving piece from your stack. You’re not paying a second vendor, managing a second dashboard, or rotating API keys across two systems. For small and mid-sized SaaS products sending transactional volume — order confirmations, password resets, WooCommerce invoices, signup verifications — that’s a real reduction in setup and maintenance overhead.
The trade-off is scope. Mail Delivery is built for transactional sending at small to mid volumes, not for high-volume bulk campaigns or use cases that depend on native stream separation between transactional and marketing traffic. If you’re sending hundreds of thousands of mixed-stream emails per month, one of the dedicated providers below will give you more control. For everything below that bar — which is most early- and growth-stage SaaS apps — Mail Delivery is the lowest-friction option.
# **Mailtrap: Best for High Deliverability**
Mailtrap is an [email API and SMTP relay provider](https://mailtrap.io/) for developers and product teams that need their emails to land in the inbox, not the spam folder. It separates transactional and bulk traffic into distinct sending streams by default. That stream separation is the core of its deliverability focus, and most of the features below build on it.
## **Key features**
- **Separate email streams.** Transactional and bulk email run on isolated infrastructure, each with its own IP reputation. A bounce spike on a promotional campaign does not affect delivery of password resets or login codes. The streams are a platform default, not IP pool configuration you wire up yourself.
- **MCP server and skills.** Mailtrap MCP server lets AI coding assistants (VS Code, Cursor, Claude Code, Windsurf, and others) send emails, run sandbox tests, and manage templates through natural language prompts. Open-source skills files are available, drop them into your project and coding agents get the API context they need to write working integrations.
- **Setup and SDKs.** The setup process takes about 5 minutes. Mailtrap covers Node.js, Ruby, PHP, Python, .NET, Elixir, and Java with official SDKs, 25+ framework code snippets for Laravel, Symfony, Django, Rails, and Next.js. Native integrations for Vercel and Supabase are also available.
- **Authentication and IP warmup.** SPF, DKIM, and DMARC are configured automatically once you add the DNS records. DKIM keys rotate every month on their own. Dedicated IPs come with automatic warmup.
- **Analytics.** Drill-down reports break out delivery, opens, clicks, bounces, and spam complaints by mailbox provider, domain, and stream. Email logs are retained for up to 30 days.
- **Webhooks.** Webhooks fire on delivery events with 40 retries every 5 minutes. That retry window means transient failures rarely cause permanent gaps in your event stream.
- **Compliance and uptime.** ISO 27001, SOC 2 Type II, and GDPR certified, with a 99% uptime SLA on distributed infrastructure.
## **Pricing**
The free tier covers 4,000 emails per month. Paid plans start at $15/month for 10,000 emails. The Business plan at $85/month for 100,000 emails includes a dedicated IP and automatic warmup. Enterprise pricing starts at $750/month for 1.5 million emails.
## **Why it works for SaaS**
Most SaaS apps end up running two kinds of email traffic: account-critical messages (login codes, password resets, billing alerts) and bulk product announcements. When both share one IP pool, a marketing send with a soft-bounce spike pulls down placement for the very emails that block users from signing in. Mailtrap handles that separation by default, with no IP pool plumbing on your side.
For SaaS engineering teams running Laravel or Node.js apps on [xCloud Laravel hosting](/laravel-hosting/) or [Node.js hosting](/node-js-hosting/), the SMTP credentials drop into existing config without anything custom on the server side. xCloud isolates environment variables per site, so you can also test multiple providers side by side on the same server without credentials leaking between apps.
# **Postmark: Best for Delivery Speed**
Postmark is an email service built to get your emails into the inbox fast. The platform runs a strict account review before enabling live sending, which keeps shared IP pool neighbors clean. Like Mailtrap, Postmark uses Message Streams to isolate transactional, broadcast, and inbound traffic at the infrastructure level. Other providers leave that separation as your problem. Postmark builds it in.
## **Key features**
- **Setup and SDKs.** New accounts go through a Postmark review before live sending opens, which usually clears within a business day. Setup itself runs 5 to 10 minutes after that, with official libraries for Node.js, PHP, Python, Ruby, .NET, Java, and Go.
- **Message Streams.** Each send carries a stream ID, and Postmark routes transactional, broadcast, or inbound traffic accordingly. The streams are first-class API objects, not a configuration trick layered on top of shared infrastructure.
- **Authentication.** SPF, DKIM, and DMARC are configured during account setup.
- **Webhooks and logs.** Activity logs are retained for 45 days. Webhooks cover delivery, bounce, open, click, and spam complaint events. Every bounce is automatically processed, categorized, and suppressed, which keeps sending hygiene clean without manual work.
- **Dedicated IPs.** Structured warmup is included, but the option is only available to accounts sending 300,000 or more emails per month.
- **Compliance.** SOC 2 Type II certified. Postmark publishes a public status page and maintains a sender compliance team that reviews accounts before enabling live sending.
## **Pricing**
Plans start at $15/month for 10,000 emails. 50,000 emails cost $60.50/month. 125,000 emails run $138/month. Dedicated IPs are $50/month on top, gated to high-volume accounts.
## **Why it works for SaaS**
Postmark works well for SaaS products where the user experience depends on a transactional message arriving fast: magic-link auth, two-factor codes, password resets, real-time billing alerts. Message Streams isolate reputation cleanly without IP pool configuration, which saves noticeable setup time. The catch is cost at scale.
Pricing climbs steeply once volume crosses six figures, and the dedicated IP add-on is locked behind 300K monthly sends. For SaaS apps running below that volume but where every minute of delay erodes user trust, Postmark is hard to beat.
# **Mailgun: Best for API Routing**
Mailgun is an API-first email service for engineering teams that want fine-grained routing and pre-send validation. Its clearest differentiator is a built-in email validation API that checks addresses against DNS/MX records, disposable domain lists, and syntax rules before sending. That step helps avoid the bounce spikes that quietly damage sender reputation at scale.
## **Key features**
- **Setup and SDKs.** Setup runs about 10 to 15 minutes for DNS records, domain verification, and per-domain API keys. Mailgun covers Node.js, Python, PHP, Ruby, Java, Go, and C# with official SDKs, and the PHP SDK alone records over 1.3 million weekly Packagist installs.
- **Email validation API.** If your application collects user-submitted addresses at scale, running them through Mailgun’s validation reduces bounce rates and protects sender reputation. Validation works one address at a time or in bulk, and the result includes both a deliverability classification and the underlying signal.
- **Authentication and stream separation.** SPF, DKIM, and DMARC are configured manually through DNS verification. Stream separation works through multiple sending domains rather than a native stream architecture.
- **Batch sending and routing.** Batch calls accept up to 1,000 recipients per API request with recipient variables for personalization. Domain-specific API keys give per-domain permission control, which is useful for multi-tenant SaaS apps that send on behalf of several customers or product lines.
- **Webhooks and logs.** Webhooks retry for 8 hours on failure. Event logs are retained for up to 30 days depending on plan.
- **Compliance.** SOC 2 Type II and GDPR compliant, offers a 99.99% uptime SLA on Scale plans.
## **Pricing**
The free tier covers 100 emails per day. Paid plans start at $15/month for 10,000 emails, with Foundation at $35/month for 50,000 emails and Scale starting at $90/month for 100,000+ emails. Overage runs around $1.80 per 1,000 emails, the highest of the providers in this list. Dedicated IPs cost $59/month.
## **Why it works for SaaS**
Mailgun fits SaaS teams that already have the engineering capacity to invest in email infrastructure and want explicit control in exchange. The combination of the validation API and per-domain keys works especially well for multi-tenant products that send on behalf of customers, partners, or product lines, where each domain needs its own isolation. The drawback is cost at higher volumes and setup overhead, plus the dedicated IP runs $59/month, the highest in this comparison.
# **Amazon SES: Best for Cost Efficiency on AWS**
Amazon SES is the cheapest SMTP and email API on this list at $0.10 per 1,000 emails with no monthly minimum. That price is real, but so is the engineering work it implies. SES is raw infrastructure. Suppression logic, analytics, templating, and production access approval are pieces you assemble yourself using Lambda, SNS, SQS, and CloudWatch.
## **Key features**
- **Setup and SDKs.** Full setup runs 15 to 20 minutes for DNS authentication, IAM permissions, and CloudWatch metric configuration. New accounts start locked to verified addresses only until AWS approves a production access request, which can sit in a queue for several business days. Once approved, you get full AWS SDK coverage across JavaScript, Python (boto3), Java, Go, Ruby, PHP, .NET, Rust, C++, and Kotlin, and SMTP works with any standard mail library.
- **Authentication.** SPF, Easy DKIM, and DMARC are supported but require manual setup.
- **Events and observability.** SES does not provide native webhooks. Delivery, bounce, and complaint events fire as SNS notifications instead. You consume them with Lambda or SQS to build your own suppression list. Reputation metrics surface through Virtual Deliverability Manager, which is a paid add-on.
- **AWS integrations.** SES has native hooks into Lambda, S3, SNS, EventBridge, and CloudWatch. That is the platform’s clearest practical advantage if your stack already lives on AWS.
- **Compliance.** SES inherits the AWS compliance footprint: SOC 2, ISO 27001, FedRAMP, HIPAA-eligible.
## **Pricing**
$0.10 per 1,000 emails, no monthly minimum. The free tier covers 3,000 emails per month for the first 12 months when sending from EC2 instances. Dedicated IPs cost $24.95/month, the lowest in this list. Attachments and data transfer are billed separately at $0.12/GB.
## **Why it works for SaaS**
Amazon SES is the right call for SaaS teams already on AWS with the in-house DevOps capacity to assemble the surrounding pieces. If your stack already lives on Lambda, S3, and EventBridge, SES drops in alongside the other AWS services with no new vendor relationship to manage, and it inherits AWS’s compliance footprint: SOC 2, ISO 27001, FedRAMP. If you run your SaaS on [xCloud AWS hosting](/docs/how-to-set-up-aws-server-in-xcloud/), SES credentials go into your app’s environment config the same way as any other provider. The catch is that everything other providers include in the box, you build yourself, including the day-to-day work of suppression list maintenance and reputation monitoring.
# **SendGrid: Best for High-Volume Enterprise SaaS**
SendGrid is the longest-running SMTP and email API in this category. The PHP SDK alone has more than 44 million installs on Packagist, and almost any framework has a community integration already written. That adoption is its clearest advantage at enterprise SaaS scale.
## **Key features**
- **Setup and SDKs.** You complete sender verification and domain authentication first, then setup runs about 10 to 15 minutes plus DNS propagation time. SDKs are available for Node.js, PHP, Python, Ruby, Java, Go, and C#. The PHP SDK is around 800 KB because it covers the entire platform (contacts, marketing campaigns, suppression lists, and mail sending) in a single client.
- **Templates.** Server-side dynamic templates with Handlebars are a first-class feature for personalized transactional content.
- **Authentication and stream separation.** SPF, DKIM, and DMARC are configured manually via the domain authentication dashboard. There is no native stream separation. Teams approximate it with IP pools or subuser accounts, both of which carry their own configuration overhead.
- **Webhooks and logs.** Event webhooks retry for 24 hours after a failure, but the free tier caps webhook endpoints at one. Activity logs are retained for 30 days on paid plans.
- **Dedicated IPs.** Available as a paid add-on, not bundled with any plan tier.
- **Compliance.** SOC 2 Type II certified and GDPR compliant under Twilio’s data processing agreements.
## **Pricing**
The free plan is 100 emails per day during a 60-day trial, then expires. Essentials starts at $19.95/month for 50,000 emails. Pro is $89.95/month for 100,000 emails. Premier pricing is custom-quoted.
## **Why it works for SaaS**
SendGrid makes the most sense for enterprise SaaS already running inside the Twilio ecosystem. Unified billing across email, SMS, and voice is useful when your product uses multiple channels for verification and notifications. The breadth of SDK coverage and community integrations means almost any engineer joining your team has probably worked with it before. The downsides are customer support response times and the lack of native stream separation, which means more manual work to keep transactional reputation isolated from bulk sends.
## **Conclusion**
Whichever provider you pick, the integration works the same way: verify your sending domain, grab the SMTP credentials or API key, and add them to your app’s environment variables. If you run on xCloud, the Mail Delivery addon collapses that work into a single panel, pick a plan, verify the domain, and the credentials wire into your site automatically. For the other five providers, expect a few minutes of config inside xCloud after creating the external account.
The more important question is which trade-offs you can live with. xCloud Mail Delivery is the lowest-friction choice for apps already on xCloud at small to mid transactional volumes. Mailtrap and Postmark give you native stream separation so transactional and bulk email stay isolated by default. Mailgun and SendGrid leave that separation to you but offer other advantages: validation for Mailgun, the Twilio ecosystem for SendGrid. SES is the cheapest at scale but expects you to build everything around it. Start with the decision map, test on a free tier, and pay attention to inbox placement rates rather than feature lists.
## **FAQ**
## **What’s the difference between an SMTP relay and an email API?**
An SMTP relay accepts mail through the SMTP protocol and delivers it for you. An email API lets your application send mail through HTTP requests instead. Both end up in the same inbox. The practical difference is integration: SMTP slots into any mail library in any language, while APIs give you template management, scheduling, batch sending, and webhook callbacks for delivery events. Most providers in this list offer both, so you can mix them. Use SMTP for legacy services and the API for newer code.
## **Do SaaS apps need a dedicated IP address?**
It depends on volume. Below 100,000 emails per month, a shared IP pool from a reputable provider works fine as long as that provider keeps its other tenants clean. Above that volume, a dedicated IP gives you full control over your sender reputation, but you also own the 2- to 4-week warmup. Some providers (Mailtrap or Postmark, for example) include the dedicated IP and warmup in the plan price. Others charge it as an add-on between $24.95 and $59 per month.
## **How do I connect an SMTP provider to my xCloud-hosted app?**
After you create an account and verify your sending domain, the provider gives you an SMTP host, port, username, and password (or API key). You add those to your app’s environment variables on the server and point your mailer library at them. xCloud isolates environment variables per site, so different SMTP credentials on the same server stay cleanly separated across apps.
---
# Best WordPress Hosting for Agencies in 2026 | xCloud
> Nine WordPress hosts compared for agencies running client sites — per-site fees, staging, team access, migrations and white label, with what 10 client sites really cost on each.
Written by xCloud, who make one of the products below. Every competitor here gets a real "best for" and every entry — xCloud first — carries an honest drawback, because a comparison where the publisher wins on everything is an advertisement.
Competitor pricing verified **August 2026**.
## Five things that only matter when the sites are not yours
Speed and uptime are table stakes; every host below has them. These are the criteria that change how an agency operates.
1. **What the tenth site costs.** Per-site pricing turns every won pitch into a bigger invoice. Per-server pricing does not. At ten sites this is the difference between $29 and $175 a month.
2. **Client and contractor access.** Can you grant exactly the access someone's job needs and revoke it later, without sharing one login?
3. **Whose name is on the bill.** Absorb hosting into a retainer, have the client pay directly, or sell it under your own brand — a host that supports only one of those picks your business model for you.
4. **Who does the migration.** Every new client is a migration off someone else's host. Free, capped, or self-service is the difference between an afternoon and a billable week.
5. **Isolation between client sites.** If one client's site is compromised, can it reach the others on that server? Per-site system users contain it; cheap shared hosting does not.
## Nine WordPress hosts for agencies, at a glance
| Host | From | Sites included | Best for |
| --- | --- | --- | --- |
| **xCloud** | $5/mo + your server | Unlimited | Agencies scaling past ~5 client sites |
| WP Engine | $96/mo (Growth, 10 sites) | 1 on entry plan | Agencies wanting a mature partner program |
| Kinsta | $35/mo | 1 | Premium performance, single flagship sites |
| Cloudways | $14/mo | Unlimited per server | Multi-cloud flexibility |
| Rocket.net | $25/mo | 1 | Maximum raw speed |
| Pressable | $25/mo | 1 | Automattic / WordPress.com ecosystem |
| Flywheel | $25/mo | 1 | Designers and creative studios |
| SiteGround | $2.99/mo intro | 1 | Small agencies, beginner clients |
| Hostinger | $2.99/mo intro | 1 | Tight budgets |
## What ten client sites actually cost per year
Entry prices are marketing. Same workload — ten production WordPress sites — on each platform's real plan for it:
| Host | Plan required | Per month | Per year |
| --- | --- | --- | --- |
| **xCloud + Vultr 4 GB** | Pro + VPS | $29 | **$348** |
| Cloudways (Vultr 4 GB) | Standard | $60 | $720 |
| Nexcess | Designer | $79.50 | $954 |
| Rocket.net | Business | $80–100 | $960–1,200 |
| WP Engine | Growth | $96 | $1,152 |
| Kinsta | Business (WP 10) | $175 | $2,100 |
The pattern is per-site versus per-server billing. Hosts that bill per site get *more* expensive than WP Engine as an agency grows; hosts that bill per server do not change price when the eleventh site lands.
## The nine, reviewed
### 1. xCloud — agencies scaling past about five client sites
A management layer over cloud servers rather than a host with plans. Take a managed server or connect one you run at DigitalOcean, Vultr, AWS, Google Cloud, Linode or Hostinger; every client site runs through one panel. Sites and traffic are unlimited on every plan. Teams are the agency-relevant piece: one per client, each with its own members, roles and its own billing and payment method.
**Where it falls short:** it is a control panel, not a hands-off host. You still choose a server size and provider. If you want to pay one bill and never see infrastructure, WP Engine or Kinsta will feel calmer. The brand is also younger than everything else here, which matters if a client's procurement asks who hosts them.
### 2. WP Engine — the most developed partner program in the category
Over 10,000 partners, and it shows in the parts that are not hosting: a partner directory that sends real leads to agencies, co-selling support, an awards programme, and Growth Suite for billing and branded client reports. If you want hosting to also be a source of new business, nothing else here matches it.
**Where it falls short:** the most expensive way to host ten sites bar Kinsta, with hard traffic-overage escalation, plugin restrictions and bandwidth caps.
### 3. Cloudways — per-server pricing with a managed feel
The closest competitor to xCloud's model: pick a cloud provider, they manage the stack, sites per server are unlimited. Their agency program is tiered by monthly spend (Bronze → Platinum) with credits, discounts and a partner directory. It ranks first for most agency hosting searches for a reason.
**Where it falls short:** roughly double an equivalent xCloud setup at ten sites, no root access on managed servers, and support quality reports have slipped since the DigitalOcean acquisition.
### 4. Kinsta — one flagship client site where performance is the product
Excellent hosting and few dispute it — Google Cloud premium tier, superb support, a genuinely pleasant panel.
**Where it falls short:** per-site pricing makes it the worst value here at agency scale. Ten sites is $175/mo — more than WP Engine, six times an equivalent xCloud setup. Priced for the site, not the portfolio.
### 5. Pressable — agencies already inside the Automattic ecosystem
Automattic-owned, so close to WordPress.com, Jetpack and WooCommerce, with Jetpack Security included.
**Where it falls short:** a smaller feature surface than WP Engine at comparable price, with no root access or provider choice.
### 6. Rocket.net — agencies selling speed as the deliverable
Enterprise Cloudflare on every plan makes it measurably fast, and it is the easiest host here to demo a before-and-after with.
**Where it falls short:** per-site pricing again ($80–100/mo for ten), and deliberately narrow control beyond the panel.
### 7. Flywheel — design studios handing finished sites to clients
Built for designers; billing transfer hands a finished site and its invoice to the client cleanly.
**Where it falls short:** now WP Engine-owned with less independent investment, per-site pricing, limited developer tooling.
### 8. SiteGround — small agencies whose clients are small businesses
GoGeek supports multiple sites with staging and client collaboration, and support is consistently well rated.
**Where it falls short:** the intro price is the exception — renewals are several times higher, and resource limits arrive quickly under real traffic.
### 9. Hostinger — the tightest budgets
Agency plans and a directory now exist, priced aggressively. If the client will not fund hosting at all, this is the honest answer.
**Where it falls short:** shared infrastructure at entry tiers means noisy-neighbour risk across client sites, and support depth does not match the managed hosts above.
## Which one you should actually pick
- **Under five client sites** — almost anything works; optimise for the workflow you like. SiteGround or Hostinger on budget, Kinsta if one client is paying for excellence.
- **Five to fifty client sites** — where per-site pricing starts hurting. xCloud or Cloudways. xCloud for root access, separate client billing and lower cost; Cloudways if brand familiarity with clients matters more.
- **You want hosting to bring you leads** — WP Engine, honestly. Nothing else here matches their directory and co-selling yet.
- **You want to sell hosting as your own product** — you need white label with your own billing. xCloud and Cloudways do it; most of the rest do not.
## FAQ
**What is the best WordPress hosting for agencies?**
It depends almost entirely on how many client sites you run. Below about five, most hosts are fine — pick on workflow. Between five and fifty, per-server hosts (xCloud, Cloudways) cost dramatically less than per-site hosts (Kinsta, Rocket.net): ten sites is $348/yr versus $2,100. If you want lead generation rather than infrastructure, WP Engine's partner program is the most developed.
**Is agency hosting different from reseller hosting?**
Yes. Agency hosting means hosting client sites on infrastructure you control, billed to you. Reseller hosting means selling hosting as a product under your own brand at your prices, billing the client yourself. Some platforms do both, and they run side by side.
**How much should an agency pay to host ten client sites?**
Between roughly $348 and $2,100 a year for the same ten sites, depending on whether the host prices per server or per site. The difference is not quality — it is the billing model.
**Can I give clients access without sharing my login?**
On the better platforms, yes, through teams and roles. Check before committing — sharing one set of credentials across a client book is how agencies end up with a disclosable security incident.
**Do agency hosting plans include free migrations?**
Usually some, rarely unlimited. Most managed hosts include a fixed number on higher plans and charge beyond that. It matters more than it looks: every new client is a migration off someone else's host.
**Should agencies use white-label hosting?**
If hosting is a line item you want the margin on, yes. If you would rather not own the support relationship for infrastructure, keep the client on their own account.
## Related
- `/agency/` — xCloud for agencies, including the partner program and free-server tiers
- `/pricing/` — all fifteen managed plans plus self-managed
- `/reseller-hosting/` — the white-label program
- `/best-wp-engine-alternatives/` — eleven alternatives compared in depth
- `/best-cloudways-alternatives/` — seven alternatives compared
- `/compare/` — xCloud head-to-head against individual hosts
---
# 11 Best WP Engine Alternatives in 2026: Faster, Cheaper & WordPress.org-Friendly (Complete Guide) - xCloud
> Compare 11 WP Engine alternatives in 2026. Find faster, cheaper, WordPress.org-friendly hosting and the best pick for beginners, agencies, and speed.
Since WordPress.org banned WP Engine from accessing its plugin and theme repositories, over 1.5 million websites have faced uncertainty about automatic updates and long-term platform stability _(according to TechCrunch)_. Combined with WP Engine’s premium pricing starting at $25/month for just one site and aggressive overage billing that catches many users off guard, the search for reliable alternatives has surged dramatically.
Read this guide comparing 11 WP Engine alternatives that industry experts and the WordPress community consistently recommend – covering managed hosting giants like Kinsta and SiteGround, innovative server management platforms like xCloud that offer the BYOS ([**Bring Your Own Server**](/self-managed-hosting/)) model, and performance-focused options like Rocket.net that include premium tools at no extra cost.
## Table of Contents
- [Quick Summary / TL;DR](/best-wp-engine-alternatives/)
- [Why WordPress Users Are Leaving WP Engine in 2026](/best-wp-engine-alternatives/)
- [How These WP Engine Alternatives Were Ranked](/best-wp-engine-alternatives/)
- [Master Comparison: All WP Engine Alternatives at a Glance](/best-wp-engine-alternatives/)
- [Detailed Reviews: The 11 Best WP Engine Alternatives](/best-wp-engine-alternatives/)
- [🥇 1. xCloud – Best for Agencies & Maximum Cost Savings](/best-wp-engine-alternatives/)
- [🥈 2. Kinsta – Best for Premium Performance](/best-wp-engine-alternatives/)
- [🥉 3. Cloudways – Best for Multi-Cloud Flexibility](/best-wp-engine-alternatives/)
- [4\. SiteGround – Best for Beginners & Small Businesses](/best-wp-engine-alternatives/)
- [5\. Rocket.net — Best for Maximum Speed](/best-wp-engine-alternatives/)
- [6\. Nexcess — Best for WooCommerce Stores](/best-wp-engine-alternatives/)
- [7\. Pressable — Best for Automattic Ecosystem](/best-wp-engine-alternatives/)
- [8\. Flywheel – Best for Designers & Creative Agencies](/best-wp-engine-alternatives/)
- [9\. Hostinger — Best Budget Option](/best-wp-engine-alternatives/)
- [10\. Bluehost – Best for WordPress.org Recommendation](/best-wp-engine-alternatives/)
- [11\. InMotion Hosting – Best for US-Based Support](/best-wp-engine-alternatives/)
- [Cost Comparison at Scale: Hosting 10 WordPress Sites](/best-wp-engine-alternatives/)
- [Migration Difficulty Comparison of WP Engine Alternatives](/best-wp-engine-alternatives/)
- [Common Mistakes When Switching from WP Engine](/best-wp-engine-alternatives/)
- [Frequently Asked Questions](/best-wp-engine-alternatives/)
## Quick Summary / TL;DR
**Too Long; Didn’t Read?** Here’s what you need to know:
If You Want To…
Use This
Expected Impact
Monthly Cost
Save 60-80% hosting costs
xCloud (BYOS)
$29/mo for unlimited sites vs $242/mo WP Engine
$5/mo + VPS
Premium Google Cloud performance
Kinsta
99.99% uptime SLA, sub-200ms TTFB
$35/mo
Multi-cloud flexibility
Cloudways
Choose between 5 cloud providers
$14/mo
Beginner-friendly managed hosting
SiteGround
WordPress.org recommended, 24/7 support
$2.99/mo\*
Maximum speed without plugins
Rocket.net
Enterprise Cloudflare CDN + free WP Rocket
$25/mo
WooCommerce optimization
Nexcess
Autoscaling, 6 premium plugins included
$19/mo
Automattic ecosystem benefits
Pressable
Free Jetpack Security Daily included
$25/mo
_\*Introductory pricing; renews at $17.99/mo_
**Expert Recommendation:** According to Online Media Masters’ comprehensive testing, xCloud delivers “40% cost savings compared to Cloudways while matching or exceeding performance benchmarks.” For agencies managing 10+ sites, the BYOS model represents the most cost-effective approach without sacrificing features.
**Best for Beginners:** SiteGround — WordPress.org officially recommended with exceptional 24/7 support and Google Cloud infrastructure at accessible pricing.
**Best for Agencies:** xCloud — Unlimited sites per server, white-label capabilities, and root access starting at $5/month management fee plus your choice of VPS provider.
**Best for Performance Seekers:** Kinsta — Google Cloud C2/C3D machines, 37 data centers, and G2’s Best Software Award 2025 winner with 4.8/5 Trustpilot rating.
## Why WordPress Users Are Leaving WP Engine in 2026
The managed WordPress hosting landscape shifted dramatically when WordPress.org officially banned WP Engine in September 2024, blocking customers from accessing plugin and theme updates through the official repository _(according to WordPress.org news)_. WordPress co-founder Matt Mullenweg publicly called WP Engine “a cancer to WordPress,” creating unprecedented uncertainty for users _(according to TechCrunch)_.
Beyond the WordPress.org drama, users consistently report three primary frustrations:
### Pricing That Scales Aggressively
WP Engine’s Growth plan costs $96/month for just 10 sites with 100,000 monthly visits. Reddit users frequently share experiences like: _“Every other month I am getting an email about some overage and then needing to upgrade to a plan that is 2-3x my current one”_ _(r/Wordpress community feedback)_.
For comparison, hosting 10 WordPress sites costs:
- **WP Engine:** $96-242/month
- **xCloud + Vultr:** $29/month (unlimited sites)
- **Cloudways:** $60/month (unlimited sites per server)
### Plugin Restrictions and Bandwidth Caps
WP Engine restricts certain caching plugins and imposes strict bandwidth limits with overage charges. The forced use of WP Engine’s “Advanced Network” (their Cloudflare proxy) limits direct CDN control for advanced users.
### Support Quality Decline
Trustpilot reviews from 2024-2025 reveal growing concerns: _“They used to be a reliable good company, they are now a complete mess”_ and _“If you have an important website do not put it in the hands of WP engine”_ _(Trustpilot verified reviews)_.
## How These WP Engine Alternatives Were Ranked
Rankings in this guide reflect methodology aligned with industry standards from G2, Trustpilot, and WPBeginner’s testing protocols:
Criterion
Why It Matters
Weight
**Cost Efficiency**
Total cost at scale (1, 10, 25 sites)
High
**Performance**
TTFB, uptime guarantees, infrastructure quality
High
**WordPress.org Compatibility**
No bans, full repository access
High
**Scalability**
Resource allocation, growth handling
Medium
**Feature Set**
Staging, CDN, backups, migrations, SSL
Medium
**User Reviews**
Trustpilot, G2, Reddit community sentiment
Medium
**Support Quality**
Response times, expertise, availability
Medium
## Master Comparison: All WP Engine Alternatives at a Glance
Rank
Provider
Starting Price
Sites Included
Performance
Trustpilot
Best For
🥇 1
**xCloud**
$5/mo + VPS
Unlimited
★★★★★
4.9/5
Agencies, cost-conscious developers
🥈 2
**Kinsta**
$35/mo
1
★★★★★
4.8/5
Premium performance seekers
🥉 3
**Cloudways**
$14/mo
Unlimited/server
★★★★☆
4.7/5
Multi-cloud flexibility
4
**SiteGround**
$2.99/mo\*
1
★★★★☆
4.9/5
Beginners, small businesses
5
**Rocket.net**
$25/mo
1
★★★★★
4.8/5
Speed-focused sites
6
**Nexcess**
$19/mo
1
★★★★☆
4.6/5
WooCommerce stores
7
**Pressable**
$25/mo
1
★★★★☆
N/A
Automattic ecosystem users
8
**Flywheel**
$25/mo
1
★★★★☆
N/A
Designers, creative agencies
9
**Hostinger**
$2.99/mo\*
1
★★★☆☆
4.5/5
Budget-conscious beginners
10
**Bluehost**
$2.95/mo\*
1
★★★☆☆
4.2/5
WordPress.org recommended
11
**InMotion**
$3.29/mo\*
1
★★★☆☆
4.3/5
US-based support preference
## **Detailed Reviews: The 11 Best WP Engine Alternatives**
### **🥇 1. xCloud – Best for Agencies & Maximum Cost Savings**
Industry experts increasingly recognize the BYOS (Bring Your Own Server) model as the most cost-effective approach to managed WordPress hosting. xCloud has emerged as the leader in this category, powering over 100,000 websites across 10,000+ servers _(according to xCloud)_.
What sets xCloud apart is the fundamental pricing model: rather than charging per site like WP Engine ($25-242/month depending on site count), xCloud charges a flat $5/month server management fee plus whatever you pay your cloud provider directly. This means agencies can host unlimited WordPress sites on a $24/month Vultr High Frequency server for a total of $29/month—an 88% savings compared to WP Engine’s Growth plan.
According to Online Media Masters’ independent review, xCloud delivers “40% cost savings [**compared to Cloudways**](/best-cloudways-alternatives/) while matching or exceeding performance benchmarks on equivalent infrastructure.”
#### Key Features
- **Unlimited Sites Per Server:** No artificial limits—host as many WordPress sites as your server can handle
- **BYOS Model:** Connect your own Vultr, DigitalOcean, Linode, Hetzner, AWS, or Google Cloud server
- **Full Root Access:** Complete server control unavailable on traditional managed hosts
- **OpenLiteSpeed Support:** Enterprise-grade caching without plugin overhead
- **White-Label Reseller Tools:** Rebrand the dashboard for client management
- **Free Tier Available:** 1 server, 10 sites.
#### Pricing
Plan
Monthly Cost
Sites
Storage
Best For
**Free**
$0
10
Varies by VPS
Testing, small projects
**Pro (BYOS)**
$5/mo + VPS
Unlimited
Varies by VPS
Agencies, developers
**Managed**
$15-49/mo
Unlimited
25-200GB NVMe
Hands-off management
**Lifetime**
$749 one-time
Unlimited
Varies
Long-term agencies
#### How to Migrate from WP Engine
**Option A: Free Migration Service**
1. Sign up at xCloud(free tier available)
2. Connect your preferred cloud provider
3. Submit a migration request through the dashboard.
4. xCloud team handles the entire transfer
**Option B: Manual Migration**
1. Export WordPress site using All-in-One WP Migration or Duplicator
2. Create a new WordPress site in the xCloud dashboard
3. Import backup to the new installation
4. Update DNS records
#### Pros and Cons
Pros
Cons
✅ 60-80% cost savings vs managed hosts
❌ Requires choosing a VPS provider
✅ Unlimited sites per server
❌ Less turnkey than traditional managed hosting
✅ Full root access and server control
❌ Smaller brand recognition vs Kinsta/Cloudways
✅ White-label agency features
❌ Email hosting needs improvement _(per G2 reviews)_
✅ Free tier with 10 sites
✅ No WordPress.org drama
**Best for:** Agencies managing 5+ client sites who want maximum control and cost efficiency, developers comfortable selecting their own cloud infrastructure, and power users seeking root access without sacrificing managed features.
### 🥈 2. Kinsta – Best for Premium Performance
Kinsta has earned G2’s Best Software Award 2025 and maintains a 4.8/5 Trustpilot rating with over 1,000 reviews, making it the consensus premium choice among WordPress hosting experts. Built entirely on Google Cloud Platform’s C2 and C3D compute-optimized machines, Kinsta delivers performance that benchmarks consistently show exceeds WP Engine _(according to industry testing from WPBeginner and IsItWP)_.
With 37 global data centers and a 99.99% uptime SLA backed by service credits, Kinsta targets high-traffic sites, enterprises, and agencies where performance justifies premium pricing. The MyKinsta dashboard provides staging environments, automatic daily backups, free migrations, and an APM (Application Performance Monitoring) tool that rivals standalone solutions.
#### Key Features
- **Google Cloud C2/C3D Machines:** Fastest compute-optimized instances available
- **37 Data Centers:** Global coverage with automatic failover
- **99.99% Uptime SLA:** Industry-leading guarantee with credits
- **MyKinsta Dashboard:** Intuitive management with staging, analytics, and SSH access
- **Free Cloudflare Integration:** Enterprise-level CDN and DDoS protection
- **APM Tool Included:** Performance monitoring without third-party tools
#### Pricing
Plan
Monthly
Sites
Visits
Storage
Best For
Single 35K
$35
1
35,000
10GB
Personal sites
WP 2
$70
2
70,000
20GB
Small business
WP 5
$115
5
125,000
30GB
Growing agencies
WP 10
$175
10
250,000
50GB
Established agencies
Enterprise
$1,650+
Custom
Custom
Custom
High-traffic sites
#### How to Migrate from WP Engine
**Option A: Free Migration by Kinsta**
1. Sign up for a Kinsta plan
2. Submit migration request via MyKinsta dashboard
3. Kinsta engineers handle the complete transfer
4. Verify site functionality before DNS switch
**Option B: Using Kinsta Migration Plugin**
1. Install the Kinsta Migrations plugin on WP Engine site
2. Enter API credentials from MyKinsta
3. Initiate automated transfer
4. Update DNS after verification
#### Pros and Cons
Pros
Cons
✅ Exceptional Google Cloud performance
❌ Per-site pricing adds up quickly
✅ Best-in-class dashboard (MyKinsta)
❌ PHP worker limits on lower plans
✅ 99.99% uptime SLA with credits
❌ Premium pricing not suitable for beginners
✅ Free APM tool included
❌ 10 sites costs $175/mo vs $29/mo on xCloud
✅ 24/7 expert WordPress support
**Best for:** High-traffic sites generating revenue where performance directly impacts conversions, enterprises requiring SLA guarantees, and agencies serving premium clients who expect top-tier infrastructure.
### 🥉 3. Cloudways – Best for Multi-Cloud Flexibility
Acquired by DigitalOcean in 2022, Cloudways offers a unique multi-cloud approach that lets users choose between five infrastructure providers: DigitalOcean, Vultr, Linode, AWS, and Google Cloud. This flexibility, combined with unlimited sites per server and pay-as-you-go hourly billing, has made Cloudways the go-to choice for developers seeking cloud performance without the complexity of raw server management _(according to WPBeginner’s 2024 testing)_.
[**Cloudways**](/xcloud-vs-cloudways/) maintains a 4.7/5 Trustpilot rating and powers over 570,000 websites _(according to BuiltWith data)_. The platform includes staging environments, server cloning, team collaboration tools, and free SSL certificates.
#### Key Features
- **5 Cloud Providers:** DigitalOcean, Vultr, Linode, AWS, Google Cloud
- **Unlimited Sites Per Server:** No per-site fees
- **Hourly Billing:** Pay only for what you use
- **Server Cloning:** Duplicate environments instantly
- **Free Migration Tool:** Automated WordPress transfers
- **Staging Environments:** One-click staging with push-to-live
#### Pricing
Provider
RAM
Monthly Cost
Direct Cost\*
Markup
DigitalOcean
1GB
$14
$6
2.3x
DigitalOcean
4GB
$50
$24
2.1x
Vultr HF
4GB
$60
$24
2.5x
AWS
2GB
$38.56
~$20
1.9x
Google Cloud
1.7GB
$37.45
~$20
1.9x
#### How to Migrate from WP Engine
**Using Cloudways Migrator Plugin:**
1. Sign up at cloudways.com and launch a server
2. Install Cloudways WordPress Migrator on the WP Engine site
3. Enter destination credentials from the Cloudways dashboard
4. Initiate migration and verify
5. Update DNS records
#### Pros and Cons
Pros
Cons
✅ Choose between 5 cloud providers
❌ ~2x markup over direct VPS costs
✅ Unlimited sites per server
❌ No email hosting included
✅ Hourly billing flexibility
❌ Cloudflare Enterprise integration restrictive
✅ Excellent staging and cloning tools
❌ Support response times vary
✅ No WordPress.org compatibility issues
**Best for:** Developers who want cloud infrastructure flexibility without raw server management, agencies needing multi-cloud deployment options, and users who value pay-as-you-go hourly billing.
### 4\. SiteGround – Best for Beginners & Small Businesses
**[SiteGround](/xcloud-vs-siteground/)** holds the distinction of being one of only three hosts officially recommended by WordPress.org, a status that carries significant weight following the WP Engine ban controversy. With over 27,000 Trustpilot reviews maintaining a 4.9/5 rating, SiteGround has built a reputation for exceptional customer support, beginner-friendly managed WordPress hosting _(according to Trustpilot verified data)_ and one of the best [**WP Engine alternatives**](https://hostinginfo.online/best-wp-engine-alternatives/).
Built on Google Cloud Platform infrastructure since 2020, SiteGround offers performance that exceeds traditional shared hosting while maintaining accessible entry pricing. Their proprietary SuperCacher system and free Speed Optimizer plugin provide caching capabilities typically reserved for premium hosts.
#### Key Features
- **WordPress.org Officially Recommended:** One of only three endorsed hosts
- **Google Cloud Infrastructure:** Enterprise-grade performance at shared hosting prices
- **SuperCacher System:** Custom caching for improved load times
- **24/7 Expert Support:** Consistently rated among the best in the industry
- **Free CDN Included:** Cloudflare integration on all plans
- **Automatic Daily Backups:** Free on all managed WordPress plans
#### Pricing
Plan
Intro Price
Renewal Price
Sites
Storage
Visits
StartUp
$2.99/mo
$17.99/mo
1
10GB
~10,000
GrowBig
$4.99/mo
$24.99/mo
Unlimited
20GB
~100,000
GoGeek
$7.99/mo
$39.99/mo
Unlimited
40GB
~400,000
Cloud
$100+/mo
Same
Custom
Custom
Custom
#### How to Migrate from WP Engine
**Using SiteGround Migrator:**
1. Sign up for SiteGround hosting
2. Install SiteGround Migrator plugin on WP Engine site
3. Generate migration token from SiteGround dashboard
4. Enter token and initiate transfer
5. Verify and update DNS
#### Pros and Cons
Pros
Cons
✅ WordPress.org officially recommended
❌ Steep renewal price increase (~6x)
✅ Outstanding 24/7 support quality
❌ Limited storage on lower plans
✅ Exceptional beginner experience
❌ Not truly “managed” on entry plans
✅ Google Cloud infrastructure
❌ Overage policies can add costs
✅ Free migration service
**Best for:** WordPress beginners prioritizing support quality, small businesses seeking affordable managed hosting, and anyone valuing WordPress.org’s official endorsement for long-term platform stability.
### 5\. Rocket.net — Best for Maximum Speed
Rocket.net has built its entire brand around performance, achieving TTFB (Time To First Byte) benchmarks that consistently outperform competitors in independent testing _(according to WPBeginner and ReviewSignal testing)_. The platform bundles enterprise-grade Cloudflare CDN—the same tier that costs enterprises $5,000+/month directly—with every plan, plus a free WP Rocket plugin license (normally $49-249/year).
Founded in 2020, Rocket.net has quickly earned a 4.8/5 Trustpilot rating with 237+ reviews by focusing exclusively on WordPress performance optimization.
#### Key Features
- **Enterprise Cloudflare CDN:** Full page caching, Argo Smart Routing, image optimization
- **Free WP Rocket Plugin:** Premium caching plugin included (saves $49-249/year)
- **Edge-First Architecture:** Content delivered from 300+ global edge locations
- **Automatic Optimization:** No caching plugins needed—performance built-in
- **24/7 WordPress Expert Support:** All staff are WordPress specialists
- **$1 First Month:** Low-risk trial on all plans
#### Pricing
Plan
Monthly
Sites
Visits
Storage
Best For
Starter
$25
1
250,000
10GB
High-traffic personal sites
Pro
$50
3
500,000
20GB
Small agencies
Business
$80-100
10
1,000,000
40GB
Growing agencies
Agency
$166
25
2,500,000
50GB
Large agencies
#### Pros and Cons
Pros
Cons
✅ Exceptional out-of-box speed
❌ Higher price point than budget options
✅ Enterprise Cloudflare CDN included
❌ Limited storage on lower plans
✅ Free WP Rocket plugin ($49-249 value)
❌ Relatively new company (2020)
✅ 250K visits included on starter plan
❌ Per-site pricing limits scalability
✅ $1 first month trial
**Best for:** Performance-obsessed site owners where speed directly impacts revenue, WooCommerce stores needing fast checkout experiences, and anyone wanting enterprise Cloudflare features without enterprise pricing.
### 6\. Nexcess — Best for WooCommerce Stores
Owned by Liquid Web since its acquisition, Nexcess has carved a niche as the WooCommerce specialist among managed WordPress hosts. Uniquely among competitors, Nexcess promises no renewal price increases—the price you sign up at remains your price forever _(according to Nexcess pricing policy)_.
With autoscaling that handles traffic spikes automatically and six premium WordPress plugins included free (Jetpack, Qubely, WP Starter, Starter Sites, Starter Templates, and a store builder), Nexcess targets e-commerce businesses that need reliability during high-traffic sales events.
#### Key Features
- **No Renewal Price Hikes:** Locked-in pricing unlike competitors
- **Autoscaling Included:** Handles traffic spikes without overage fees
- **6 Premium Plugins Free:** Jetpack, site builders, and templates included
- **Email Hosting Included:** Rare among managed WordPress hosts
- **WooCommerce-Optimized Plans:** Dedicated e-commerce infrastructure
- **Own Data Centers:** US, Europe, and Asia locations
#### Pricing
Plan
Monthly
Sites
Storage
Bandwidth
Best For
Spark
$19
1
8GB
1TB
New stores
Maker
$47.85
5
40GB
4TB
Growing stores
Designer
$79.50
10
80GB
5TB
Multi-store agencies
Enterprise
$999
250
800GB
10TB
Large e-commerce
#### Pros and Cons
Pros
Cons
✅ No renewal price increases
❌ Higher entry price than shared hosts
✅ Autoscaling included free
❌ Dashboard less modern than Kinsta
✅ Email hosting included
❌ Fewer data center locations
✅ WooCommerce-optimized infrastructure
❌ Brand less recognized than competitors
✅ 6 premium plugins free
**Best for:** WooCommerce stores requiring reliable scaling during sales events, e-commerce businesses wanting predictable long-term pricing, and users who need email hosting included with their WordPress plan.
### 7\. Pressable — Best for Automattic Ecosystem
Pressable operates under Automattic ownership—the same company behind WordPress.com, WooCommerce, and Jetpack—giving it unique integration advantages within the WordPress ecosystem. Every Pressable plan includes Jetpack Security Daily (normally $9.95/month) for real-time backups, malware scanning, and spam protection.
This Automattic connection provides a level of WordPress integration that third-party hosts cannot match, making Pressable particularly appealing for users already invested in the Jetpack ecosystem.
#### Key Features
- **Automattic-Owned:** Deep WordPress.com and WooCommerce integration
- **Free Jetpack Security Daily:** Real-time backups, malware scanning included
- **WP Cloud Infrastructure:** Built on Automattic’s proprietary platform
- **Agency Partner Program:** Bulk pricing for resellers
- **Instant Staging:** One-click test environments
- **Expert WordPress Support:** Teams trained on WordPress internals
#### Pricing
Plan
Monthly
Sites
Visits
Storage
Best For
Entry
$25
1
30,000
20GB
Personal projects
Starter
$45
3
50,000
30GB
Small agencies
Pro
$90
5
100,000
50GB
Growing agencies
Agency
Custom
25+
Custom
Custom
Large agencies
_Overage: $1.20 per 1,000 visits or $8 per 10,000 pre-purchased_
#### Pros and Cons
Pros
Cons
✅ Automattic ecosystem integration
❌ Smaller brand recognition
✅ Free Jetpack Security Daily included
❌ Overage fees can accumulate
✅ WP Cloud infrastructure reliability
❌ Fewer data centers than Kinsta
✅ Deep WordPress expertise
❌ Per-site pricing limits scale
**Best for:** Users already using Jetpack who want seamless integration, agencies seeking Automattic-backed infrastructure, and WordPress professionals wanting deep ecosystem access.
### 8\. Flywheel – Best for Designers & Creative Agencies
Flywheel was purpose-built for designers and creative agencies, featuring collaboration tools like client billing transfer, designer-friendly dashboards, and the Local development tool (now used by over 1 million developers). While acquired by WP Engine in 2019, Flywheel maintains its distinct brand identity and agency-focused toolset.
**Important note:** As a WP Engine subsidiary, Flywheel shares infrastructure and is affected by the same WordPress.org restrictions. Users concerned about the WordPress.org drama should consider alternatives not owned by WP Engine.
#### Key Features
- **Designer-Friendly Dashboard:** Beautiful UI built for creative professionals
- **Client Billing Transfer:** Hand off sites with billing included
- **Local Development Tool:** Industry-standard local WordPress development
- **Free Demo Sites:** Show clients work before they commit
- **Site Migration Included:** Free transfers for new customers
- **Collaboration Tools:** Multi-user access with role permissions
#### Pricing
Plan
Monthly
Sites
Visits
Storage
Best For
Starter
$25
1
25,000
10GB
Freelancers
Freelance
$96
10
100,000
20GB
Small agencies
Agency
$242
30
400,000
50GB
Large agencies
Custom
Contact
Custom
Custom
Custom
Enterprise
#### Pros and Cons
Pros
Cons
✅ Industry-best designer experience
❌ Owned by WP Engine (same concerns)
✅ Client billing transfer feature
❌ Affected by WordPress.org restrictions
✅ Free Local development tool
❌ Pricing aligned with WP Engine since acquisition
✅ Beautiful collaboration interface
❌ Not a true “alternative” for WP Engine escapees
**Best for:** Designers and creative agencies prioritizing workflow over infrastructure concerns, freelancers using Local for development, and users who need client billing transfer features.
### 9\. Hostinger — Best Budget Option
Hostinger has become the dominant budget WordPress host, serving over 29 million users worldwide with aggressive pricing and a modernized control panel _(according to Hostinger)_. While not offering the managed features of premium hosts, Hostinger’s WordPress hosting includes LiteSpeed web servers, automatic updates, and free SSL.
For cost-conscious users where maximum savings outweigh premium features, Hostinger delivers acceptable WordPress performance at industry-low prices.
#### Key Features
- **LiteSpeed Web Servers:** Better performance than traditional shared Apache
- **AI Website Builder:** Automated site creation tools
- **Aggressive Pricing:** Among lowest in the industry
- **Global Data Centers:** 9 locations worldwide
- **Free Domain First Year:** Included on annual plans
- **WordPress Auto-Updates:** Automated core and plugin updates
#### Pricing
Plan
Intro Price
Renewal
Sites
Storage
Best For
Single
$2.99/mo
$7.99/mo
1
50GB
Hobby sites
Premium
$2.99/mo
$10.99/mo
100
100GB
Multiple small sites
Business
$3.99/mo
$15.99/mo
100
200GB
Growing businesses
Cloud Startup
$9.99/mo
$24.99/mo
300
200GB
Higher traffic
#### **Pros and Cons**
Pros
Cons
✅ Industry-low entry pricing
❌ Renewal prices significantly higher
✅ LiteSpeed server performance
❌ Support quality inconsistent
✅ Modern control panel
❌ Not truly “managed” hosting
✅ Free domain included
❌ Aggressive upselling in dashboard
**Best for:** Budget-conscious beginners, hobby sites, and users prioritizing cost savings over premium managed features.
### **10\. Bluehost – Best for WordPress.org Recommendation**
Bluehost is one of only three hosts officially recommended by WordPress.org, a designation that provides reassurance following the WP Engine controversy. Hosting over 2 million websites _(according to BuiltWith)_, Bluehost offers a streamlined WordPress experience with one-click installation and 24/7 support.
While not matching premium managed hosts on performance, Bluehost provides reliable shared hosting at accessible pricing for users who value WordPress.org’s endorsement.
#### **Key Features**
- **WordPress.org Officially Recommended:** One of three endorsed hosts
- **Free Domain First Year:** Included on all plans
- **One-Click WordPress Install:** Streamlined setup process
- **24/7 Phone Support:** US-based support team
- **Free SSL Certificate:** Included on all plans
- **30-Day Money-Back Guarantee:** Risk-free trial period
#### **Pricing**
Plan
Intro Price
Renewal
Sites
Storage
Best For
Basic
$2.95/mo
$11.99/mo
1
10GB
Personal sites
Plus
$5.45/mo
$16.99/mo
Unlimited
Unlimited
Multiple sites
Choice Plus
$5.45/mo
$21.99/mo
Unlimited
Unlimited
Privacy protection
Pro
$13.95/mo
$28.99/mo
Unlimited
Unlimited
Higher performance
#### **Pros and Cons**
Pros
Cons
✅ WordPress.org officially recommended
❌ Not truly managed hosting
✅ Free domain and SSL included
❌ Significant renewal price increases
✅ Reliable US-based support
❌ Performance lags premium hosts
✅ 30-day money-back guarantee
❌ Aggressive upselling at checkout
**Best for:** Users prioritizing WordPress.org’s endorsement, beginners wanting a straightforward setup, and budget-conscious site owners comfortable with shared hosting performance.
### **11\. InMotion Hosting – Best for US-Based Support**
InMotion Hosting differentiates itself with entirely US-based support teams and data centers, appealing to businesses requiring domestic hosting and communication. With over 20 years in the industry, InMotion offers WordPress hosting ranging from shared plans to managed VPS options.
#### **Key Features**
- **US-Based Support Team:** All support staff located in United States
- **US Data Centers:** East and West Coast locations
- **Free Website Migration:** Included on all plans
- **90-Day Money-Back Guarantee:** Industry-leading refund period
- **Free SSL and Domain:** Included on annual plans
- **UltraStack Technology:** Performance optimization on managed plans
#### **Pricing**
Plan
Intro Price
Renewal
Sites
Storage
Best For
Core
$3.29/mo
$11.49/mo
1
100GB
Personal sites
Launch
$5.29/mo
$14.49/mo
2
100GB
Small businesses
Power
$5.29/mo
$14.49/mo
3
100GB
Growing sites
Pro
$13.99/mo
$21.99/mo
6
100GB
Serious businesses
#### **Pros and Cons**
Pros
Cons
✅ US-based support team entirely
❌ Performance doesn’t match premium hosts
✅ 90-day money-back guarantee
❌ Significant renewal increases
✅ US data center locations
❌ Fewer global data center options
✅ Free migration service
❌ Dashboard less modern than competitors
**Best for:** US businesses requiring domestic support and data residency, users valuing the 90-day refund period, and those preferring established hosting companies.
## **Feature Comparison: WP Engine vs Top Alternatives**
Feature
WP Engine
xCloud
Kinsta
Cloudways
SiteGround
Rocket.net
Starting Price
$25/mo
$5/mo + VPS
$35/mo
$14/mo
$2.99/mo\*
$25/mo
Sites Included
1
Unlimited
1
Unlimited
1
1
WordPress.org Access
❌ Banned
✅
✅
✅
✅
✅
Root Access
❌
✅
❌
Limited
❌
❌
BYOS Option
❌
✅
❌
❌
❌
❌
White-Label
❌
✅
❌
Partial
❌
❌
Free CDN
✅
Via Provider
✅
✅
✅
✅ Enterprise
Staging
✅
✅
✅
✅
✅
✅
Free Migration
✅
✅
✅
✅
✅
✅
Uptime SLA
99.95%
Varies
99.99%
Varies
99.99%
99.99%
Email Hosting
❌
Via Provider
❌
❌
✅
❌
## **Cost Comparison at Scale: Hosting 10 WordPress Sites**
One of the most significant factors when leaving WP Engine is understanding how costs scale. Here’s what you’ll actually pay to host 10 WordPress sites:
Provider
Plan Required
Monthly Cost
Annual Cost
vs WP Engine Savings
**WP Engine**
Growth
$96/mo
$1,152/yr
—
**xCloud + Vultr 4GB**
Pro + VPS
$29/mo
$348/yr
**70% savings**
**Cloudways Vultr 4GB**
Standard
$60/mo
$720/yr
37% savings
**SiteGround GoGeek**
GoGeek
$40/mo (renewal)
$480/yr
58% savings
**Kinsta WP 10**
Business
$175/mo
$2,100/yr
\-82% (more expensive)
**Rocket.net Business**
Business
$80-100/mo
$960-1,200/yr
0-17% savings
**Nexcess Designer**
Designer
$79.50/mo
$954/yr
17% savings
**Key insight:** At 10 sites, xCloud’s BYOS model delivers 70% savings versus WP Engine while offering unlimited sites—meaning you can continue adding sites without additional cost. Traditional per-site pricing (Kinsta, Rocket.net) actually becomes more expensive than WP Engine at scale.
## **Migration Difficulty Comparison of WP Engine Alternatives**
Provider
Migration Method
Time Required
Technical Skill
Free Migration?
xCloud
Dashboard or plugin
30-60 min
Basic
✅ Yes
Kinsta
Plugin or manual
30-60 min
Basic
✅ Yes
Cloudways
Migrator plugin
30-45 min
Basic
✅ Yes
SiteGround
Migrator plugin
30-45 min
Basic
✅ Yes
Rocket.net
Support-assisted
1-2 hours
None
✅ Yes
Nexcess
Manual or support
1-2 hours
Basic
✅ Yes
Pressable
Dashboard
30-60 min
Basic
✅ Yes
Flywheel
Local or manual
30-60 min
Basic
✅ Yes
Hostinger
Manual
1-2 hours
Intermediate
Limited
Bluehost
Manual
1-2 hours
Intermediate
Limited
InMotion
Support-assisted
1-2 hours
Basic
✅ Yes
## **Common Mistakes When Switching from WP Engin**e
### 1\. Not Checking WordPress.org Compatibility First
Before migrating, verify your chosen alternative has full WordPress.org repository access. Flywheel, as a WP Engine subsidiary, shares the same restrictions. Most other alternatives have no such limitations.
### 2\. Forgetting About Email Hosting
WP Engine doesn’t include email hosting, so you may already have this handled elsewhere. However, if you’re consolidating services, note that only SiteGround and Nexcess among the top alternatives include email hosting. Others require third-party email services.
### 3\. Underestimating DNS Propagation Time
After migrating, DNS changes can take 24-48 hours to propagate globally. Keep your WP Engine site active during this period to prevent downtime. Use tools like whatsmydns.net to monitor propagation.
### 4\. Ignoring Renewal Pricing
Entry-level pricing at SiteGround, Hostinger, and Bluehost increases significantly at renewal—often 5-6x the introductory rate. Factor renewal costs into your long-term budget. Nexcess specifically promises no renewal increases.
### 5\. Choosing Based on Price Alone Without Considering Scale
The cheapest option at 1 site may become expensive at 10+ sites. xCloud and Cloudways offer unlimited sites per server, making them more cost-effective as you scale. Per-site pricing (Kinsta, Rocket.net) compounds quickly.
### 6\. Not Testing Before DNS Switch
Always verify your migrated site works correctly before updating DNS. Test critical functionality including forms, e-commerce checkout, and third-party integrations on the staging or temporary URL provided by your new host.
## Frequently Asked Questions
### Which WP Engine alternative should I start with?
Start with xCloud if you’re comfortable selecting a VPS provider and want maximum cost savings with unlimited sites. Choose SiteGround if you’re a beginner wanting WordPress.org-recommended hosting with excellent support. Select Kinsta if performance is your top priority and budget permits.
### Do I need to pay for premium hosting after leaving WP Engine?
No, every alternative in this guide offers either free tiers (xCloud) or affordable entry points ($2.99-$5/month introductory pricing). However, paid options like Kinsta ($35/mo) and Rocket.net ($25/mo) deliver measurably better performance for sites where speed impacts revenue.
### How long does migration from WP Engine take?
Most migrations complete in 30-60 minutes using automated plugins. Full DNS propagation can take 24-48 hours. Free migration services from Kinsta, xCloud, and Rocket.net handle the technical work, requiring minimal user involvement.
### Will my site be affected by the WordPress.org ban if I switch?
Only if you switch to Flywheel, which is owned by WP Engine and shares the same restrictions. All other alternatives in this guide have full WordPress.org repository access for plugins, themes, and updates.
### Can I migrate multiple sites from WP Engine at once?
Yes, most alternatives support bulk migrations. xCloud and Cloudways are particularly suited for multi-site agencies, offering unlimited sites per server. Kinsta and Rocket.net require migrating one site at a time but offer free migration assistance.
### What’s the budget needed to replace WP Engine adequately?
1. **$0/month:** xCloud free tier (1 server, 10 sites)
2. **$15-30/month:** Quality managed hosting for 1-5 sites (xCloud Pro, SiteGround GrowBig, Cloudways entry)
3. **$50-100/month:** Premium performance or 10+ sites (Kinsta, Rocket.net, xCloud + larger VPS)
### Will WP Engine alternatives work for WooCommerce stores?
Yes, all alternatives support WooCommerce. Nexcess offers WooCommerce-optimized plans with autoscaling specifically designed for e-commerce traffic spikes. Rocket.net’s enterprise Cloudflare CDN excels for fast checkout experiences. xCloud works well for agencies managing multiple WooCommerce sites
### What’s the most underrated WP Engine alternative?
xCloud’s BYOS model remains underrated because it requires understanding the server management panel category. Most comparison articles focus only on traditional managed hosts, missing the 60-80% cost savings possible by connecting your own cloud infrastructure while maintaining managed WordPress features.
### How often should I revisit my hosting choice?
Review hosting annually or when experiencing performance issues, significant traffic growth, or pricing changes at renewal. The managed WordPress hosting market evolves rapidly—new features and pricing changes frequently alter the competitive landscape.
### Where can I get help choosing between alternatives?
- **xCloud:** Free trial with 10 sites, active support team
- **Kinsta:** Demo available via MyKinsta, 24/7 expert support
- **SiteGround:** Known for exceptional 24/7 support quality
- **Reddit communities:** r/Wordpress, r/webhosting for unbiased user experiences
## Wrapping: Your 2026 WP Engine Migration Roadmap
The WordPress.org ban fundamentally changed WP Engine’s position in the managed WordPress market. With alternatives now offering equal or superior performance at 60-80% lower costs, combined with full WordPress.org repository access, the case for migration has never been stronger.
### Expert Picks by Goal
Your Goal
Best Choice
Expected Impact
**Maximum Cost Savings**
xCloud (BYOS)
70% savings, unlimited sites
**Premium Performance**
Kinsta
99.99% uptime, Google Cloud C2/C3D
**Beginner-Friendly**
SiteGround
WordPress.org recommended, excellent support
**Multi-Cloud Flexibility**
Cloudways
5 provider options, hourly billing
**Speed Without Plugins**
Rocket.net
Enterprise Cloudflare CDN, free WP Rocket
**WooCommerce Focus**
Nexcess
Autoscaling, no renewal increases
**Agency Scale**
xCloud
Unlimited sites, white-label, $5/mo management
### Recommended Migration Timeline
1. **This Week:** Sign up for your chosen alternative (most offer free trials or money-back guarantees)
2. **Week 2:** Migrate your lowest-traffic site first as a test
3. **Week 3:** Complete migration of remaining sites
4. **Week 4:** Cancel WP Engine after verifying all sites function correctly
The managed WordPress hosting market has matured significantly since WP Engine’s dominant years. Whether you prioritize cost savings (xCloud), premium performance (Kinsta), or beginner-friendly support (SiteGround), alternatives now match or exceed WP Engine’s capabilities while avoiding the WordPress.org compatibility concerns that now define the platform.
If you have found this blog helpful, feel free to [subscribe to our blogs](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [Facebook community](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Black Friday Web Hosting Deals 2025: Unlock Lifetime Control Panel Access - xCloud
> Black Friday Web Hosting Deals 2025: Unlock lifetime access to xCloud’s powerful hosting control panel with unlimited sites and zero recurring fees.
Stop renting your hosting panel, rather own it for life. Build amazing projects with smart features and manage your server with total freedom. This Black Friday, xCloud is offering exclusive deals that stand out among the best [**Black Friday Web Hosting Deals**](/deal/) 2025.
With a one-time payment, you can access xCloud’s powerful cloud control panel for life, connect your own servers (from Vultr, DigitalOcean, Google Cloud, and more), and enjoy unlimited site deployments, migrations, and advanced features.
There’s never been a better moment to step up your game. Head to our deal page to grab this limited-time Lifetime Deal and experience one of the most valuable Black Friday Web Hosting Deals 2025 available this year.
## **What Our Black Friday Web Hosting Deals Let You Do**?
The xCloud Black Friday Deal can transform the way you manage websites and servers by giving you long-term control without recurring fees.
With a single upfront payment, you unlock lifetime access to a powerful cloud management platform built to scale effortlessly, whether you’re a developer, an agency, a business owner, or someone building multiple projects. Here’s a detailed look at everything this deal enables you to do:
### **Lifetime Access to xCloud’s Control Panel**
With these Black Friday web hosting deals, you eliminate monthly and yearly licensing costs. You pay once and retain lifetime access to the entire xCloud dashboard, including every current feature and all future updates. This long-term access creates predictable costs and gives you the financial freedom to grow without worrying about subscription renewals or upgrade fees. For developers and agencies managing long-term infrastructure, this means complete peace of mind.
### **Bring Your Own Server, Your Way**
Prefer using your [**own servers**](/self-managed-hosting/)? LTD users even get special discounted pricing through xCloud Provider. Unlike platforms that lock you into proprietary hosting, xCloud lets you connect servers from nearly any cloud provider.
Whether you prefer DigitalOcean, [Vultr](https://www.vultr.com/), Hetzner, AWS, Google Cloud, or a custom VPS or dedicated machine, you can integrate your infrastructure directly into the panel. LTD users can even leverage discounted pricing through the xCloud Provider for added convenience. This flexibility ensures you stay in control of performance, cost, and server location at all times.
### **3\. Deploy Unlimited Websites With Zero Added Cost**
Your lifetime license allows you to deploy as many websites as you like, without restrictions or upgrade requirements. Whether you’re hosting dozens of personal projects or managing hundreds of client sites, you’ll never face artificial limits.
You can deploy unlimited WordPress installations, custom applications, staging environments, and app instances, making the platform ideal for agencies, freelancers, and resellers who need unlimited scalability.
### **4\. Move All Your Sites Easily With Free Unlimited Migration**
xCloud makes migration simple by offering free, unlimited website transfers. You can migrate WordPress sites, full servers, and multisite installations seamlessly using automated tools designed to save time and reduce the risk of errors. Even email and DNS configurations can be brought over easily. Whether switching from shared hosting, a VPS, cPanel, or another cloud panel, the transition is smooth and hassle-free.
### **5\. Launch Your Own Hosting Brand With White-Label Access**
Every Lifetime Deal includes full access to a **[white-label reseller panel](/reseller-hosting/)**, enabling you to build your own hosting brand from day one. You can customise the dashboard with your own logo, domain, and branding elements. You control the pricing, client packages, and overall experience. Depending on your LTD tier, you can manage anywhere from **25 to 400 reseller servers**, offering a powerful opportunity to generate recurring revenue under your own name.
## **Who This Black Friday Deal Is Made For**
**xCloud Black Friday Lifetime Deal** is designed for anyone who wants complete control over web hosting without recurring fees, but wants to manage with a panel where they can get anything they want.
- **Developers & Agencies**: Manage multiple client servers from a single, modern panel; use staging, Git deployment, and root access to deliver professional services.
- **Entrepreneurs & Startups**: Bring your own VPS and avoid recurring licensing fees. A one-time payment gives you long-term control.
- **Freelancers**: Scale as you grow. Deploy as many sites as you want, without the usual constraints.
- **Resellers:** Use the reseller panel to launch your own hosting business under your own brand.
## **Why Buy Now**
With a single payment, in this Black Friday Deal, you can secure permanent access to tools that typically require monthly or yearly fees, making this the smartest moment to invest in your digital infrastructure. Beyond the savings, this is your chance to lock in future-proof hosting freedom.
- **Unmatched Lifetime Value** – Instead of paying monthly for a control panel, you pay once and own the license for life.
- **Big Savings, Long-Term** – Pay 1 – 2 years now and skip recurring costs forever.
- **130+ Feature Access** — Most of the features are unlocked for LTD users so that your server management remains seamless.
- **Reseller Panel Included** – Bonus reseller panel ideal for starting your own hosting brand and managing with built-in payment and client management features.
- **Backed by a Trusted Team** – xCloud is built by the WPDeveloper/WPManageNinja team, who already power millions of sites.
- **Risk-Free Trial** – With a 14-day money-back guarantee, you can test before fully committing.
If you are shopping around and comparing options, this offer stands out strongly among the black friday web hosting deals 2025, especially for users wanting complete ownership instead of subscriptions.
[Grab The Deal Now](/deal/)
## **Ready to Experience Future Proof Hosting Control Panel?**
Your next online project deserves the right foundation. With the xCloud Black Friday Lifetime Deal live right now, you can finally launch, scale, or upgrade your hosting environment without worrying about recurring fees, renewal spikes, or platform limitations.
If you are building your first website or managing dozens for clients, this is the moment to secure a powerful, future-proof setup at the lowest cost of the year. Among all **Black Friday Web Hosting Deals 2025**, this one gives you true ownership and lifetime value.
Everything you need is already in place: unlimited site deployments, server flexibility, performance-optimised stacks, white-label tools, and a dashboard built for both beginners and professionals. All that’s left is for you to take advantage of the deal before it disappears.
Jump in and secure your lifetime access before this special offer ends.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# xCloud Blog - Managed Hosting for WordPress Tutorials, Tips & Resources
> Explore our xCloud blog and get updates, tips, deals, and more resources to grow your WordPress website.
## Blog
# Explore, Learn, Excel: xCloud’s Blog & Knowledge Hub
Global server coverage for optimal performance everywhere.
- All
- Features
- News
- Tutorial
- WordPress
- Guide
No Posts Found
[DeepSeek Harness vs OpenCode: Which Coding Agent Should You Run in 2026?](/deepseek-harness-vs-opencode/) 
[DeepSeek Harness vs OpenClaw vs Hermes Agent: Which Agent Harness Should You Run in 2026?](/deepseek-harness-vs-openclaw-vs-hermes-agent/) 
[9 Best DeepSeek Harness Hosting Providers in 2026: Compared on Setup, Cost, Security & 24/7 Uptime (Complete Guide)](/best-deepseek-harness-hosting-providers/) 
[What Is DeepSeek Harness? Features, Architecture & Use Cases Explained (2026)](/what-is-deepseek-harness-features-architecture-use-cases/) 
[Broken Link Checker for WordPress: How to Monitor Your Site’s Links & Images Easily](/broken-link-checker-for-wordpress-monitor-sites-links-images/) 
[Cloudflare CDN Enterprise: Make Your Website Faster and Secure With Global CDN Network](/cloudflare-enterprise-cdn-faster-secure-website/) 
[What Is Laravel? A Complete Beginner’s Guide to the PHP Framework](/what-is-laravel-a-complete-beginners-guide/) 
[What is Buzz Workspace? Features, Use Cases, and How to Deploy It (2026 Guide)](/what-is-buzz-workspace-features-and-use-cases/) 
[Introducing One Click Git Deploy: Ship Any Project the Fastest Way](/one-click-git-deploy-ship-any-project-the-fastest-way/) 
[What Is Web Terminal: How to Manage a Server And Site from Your Browser (Without an SSH Client)](/what-is-web-terminal-how-to-manage-a-server-and-site-from-browser/) 
[Node.js vs Laravel: Key Differences and Which One to Choose](/node-js-vs-laravel-key-differences/) 
[Hermes Agent Docker vs Managed Hosting: Which Should You Choose in 2026?](/hermes-agent-docker-vs-managed-hosting/) 
No more posts
< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 \>
---
# xCloud Brand Resources
> Download the official xCloud brand resources and media kit for consistent and accurate branding of xCloud Hosting across all platforms.
# Get All xCloud Media Kit & Press Resources In One Place
Our logo is a core symbol of the brand. Do not alter or modify it. Use the provided assets from the xCloud Media Kit to maintain harmony and a professional look for our platform.
[Download All Resources](/_mirror/01626baf-xCloud-Brand-Resources.zip)
## About xCloud Hosting
xCloud is a next-generation hosting platform that simplifies hosting management. Launched in 2024, it empowers individuals, developers and businesses with automation, performance, flexibility, and a mission to deliver stability, speed, and security in cloud hosting.
## Brand Colors
The xCloud logo comes in two primary versions: Azure blue and White colors. Azure Blue, White, and Eclipse Dark are the primary colors and give the brand its distinct identity and giving depth and a strong visual foundation.
## Azure Blue: Hexa: 1570EF
1570EF
## White: Hexa: FFFFFF
FFFFFF
## Eclipse Dark: Hexa: 0F111D
0F111D
## xCloud Logo Guideline
To keep the xCloud logo clear and effective, ensure it has adequate surrounding space equal to or greater than the size of the icon symbol, to keep it distinct and visible.
## Brand Typography
xCloud exclusively uses Sora as its brand font, reflecting a sleek, modern aesthetic that shows innovation, while ensuring consistent visual identity across all platforms.
## Typeface
## Font Weights
## Light
## ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789° (!”#$%&?@)
## Regular
## ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789° (!”#$%&?@)
## Medium
## ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789° (!”#$%&?@)
## Semi-Bold
## ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789° (!”#$%&?@)
## Bold
## ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789° (!”#$%&?@)
## xCloud Logo Usage Guidelines
The xCloud logo combines our Cloud icon to represent our brand’s identity. Always use the provided logo files to maintain visual consistency across all platforms.
### The logo consists of the symbol and wordmark, locked up together – always maintain clear space between them.
### The symbol and wordmark can be used side by side or with the wordmark below the symbol.
### Do not use only the symbol as the xCloud logo, and avoid cropping it.
### Do not distort, rotate, or apply reflections to the logo.
### The logo should not be used in a different color or with altered opacity.
## xCloud Official Logo Variations
Find the official logo versions for xCloud. Pick the one that works best for your project while maintaining brand consistency. All variations are included in the xCloud Media Kit.
## Full Logo\_White
[PNG](/_mirror/d114c30f-xCloudxCloud-White-Full-Logo.png)
[SVG](/_mirror/089a18ef-xCloudxCloud-White-Full-Logo.svg)
[JPG](/_mirror/d114c30f-xCloudxCloud-White-Full-Logo.png)
## Full Logo\_Blue
[PNG](/_mirror/778c2dce-xCloudxCloud-Default-Logo.png)
[SVG](/_mirror/4aa6bbed-xCloudxCloud-Default-Logo.svg)
[JPG](/_mirror/778c2dce-xCloudxCloud-Default-Logo.png)
## Full Logo\_Black
[PNG](/_mirror/ee35e3d2-xCloudxCloud-Black-Full-Logo.png)
[SVG](/_mirror/56dea49a-xCloudxCloud-Black-Full-Logo.svg)
[JPG](/_mirror/ee35e3d2-xCloudxCloud-Black-Full-Logo.png)
## Logo Symbol\_Blue
[PNG](/_mirror/7bba25c7-xCloud-blueblack.png)
[SVG](/_mirror/e47c1956-xCloud-blueblack.svg)
[JPG](/_mirror/7bba25c7-xCloud-blueblack.png)
## Full Logo\_Blue/White
[PNG](/_mirror/da9a173f-xCloud-bluewhite.png)
[SVG](/_mirror/e9963ad1-xCloud-bluewhite.svg)
[JPG](/_mirror/da9a173f-xCloud-bluewhite.png)
## Logo Symbol\_White
[PNG](/_mirror/3fcdfdea-xCloudxCloud-White-icon.png)
[SVG](/_mirror/40bb2e2f-xCloudxCloud-White-icon.svg)
[JPG](/_mirror/3fcdfdea-xCloudxCloud-White-icon.png)
## Logo Symbol\_Blue
[PNG](/_mirror/3fcdfdea-xCloudxCloud-White-icon.png)
[SVG](/_mirror/64a88539-xCloudxCloud-icon.svg)
[JPG](/_mirror/3fcdfdea-xCloudxCloud-White-icon.png)
## Logo Symbol\_Black
[PNG](/_mirror/3a67ef24-xCloudxCloud-Black-icon.png)
[SVG](/_mirror/4744ffd0-xCloudxCloud-Black-icon.svg)
[JPG](/_mirror/3a67ef24-xCloudxCloud-Black-icon.png)
## Download the Full xCloud Media Kit and Brand Resources
Access our brand resources, logos, colors, and guidelines from the official xCloud MediaKit to showcase
xCloud accurately across all platforms.
[Download All Resources](/_mirror/01626baf-xCloud-Brand-Resources.zip)
---
# Broken Link Checker for WordPress: How to Monitor Your Site's Links & Images Easily - xCloud
> Need a broken link checker for WordPress? xCloud scans your site for dead links, images, and 404s right from the dashboard. No plugins required.
Finding a 404 error on your website is frustrating, both for you and for your visitors. Someone clicks expecting content and lands on an error page instead. Most won’t try again; they leave, and many never come back.
Broken links are usually the cause. These are hyperlinks that lead to pages or resources that no longer exist, whether on your own site or on external websites you’ve linked to. Deleted pages, changed URLs, expired domains, and server issues all produce them.
Picture a customer trying to buy from your store. They click “Buy Now” and land on an error page instead of checkout. That’s a sale lost to a problem you didn’t know existed.
In this guide, we’ll break down what broken links are, the error types behind them, why every WordPress site needs a broken link checker, and how to find and fix broken links using xCloud’s built-in Broken Link Monitoring, without installing a single plugin.
## Understanding Broken Links and Their Types
### What Is a Broken Link?
A broken link is a hyperlink that points to a page or resource that doesn’t exist or can’t be reached. This happens when a page is deleted, a slug is misspelled, content is moved without a redirect, a domain changes, or the destination server is temporarily unavailable. When someone clicks a broken link, they get an error instead of content, and those errors hurt both user experience and SEO.
Broken links come in three main types:
- **Broken internal links.** Links within your website that don’t work. These connect your own pages to each other, and when they break, they interrupt visitor journeys and search engine crawl paths.
- **Broken outbound links.** Links from your website to other websites that fail. You linked to a resource, and that resource has since moved or disappeared.
- **Broken backlinks.** Links from other websites pointing to your site that no longer resolve, usually because you deleted or moved the target page without a redirect. These waste referral traffic and the link equity those pages earned.
Broken resources go beyond hyperlinks, too. Missing images, stylesheets, scripts, and media files break how pages render even when the page itself loads fine.
## Common Error Types Behind Broken Links
Not every broken link fails the same way. When a link stops working, the server (or the lack of a response) tells you why. These are the error types you’ll encounter, and the ones xCloud’s scanner detects and lets you filter by:
- **404 Not Found.** The page doesn’t exist at that URL. The most common broken link error.
- **Soft 404.** The page returns a success status but shows error or empty content. These are sneaky because standard checks miss them.
- **DNS error.** The domain name can’t be resolved. Common with expired domains or dead external sites.
- **Timeout.** The server took too long to respond, so the request gave up.
- **Server error (5xx).** The destination server failed to process the request.
- **Redirect.** The URL forwards somewhere else. Not broken, but worth reviewing, since redirects add load time and can mask deleted content.
- **Redirect chain.** The URL passes through multiple redirects before resolving. Chains slow visitors down and dilute SEO signals.
- **Blocked request.** The destination refused the request, so the resource couldn’t be verified.
## Why You Need a Broken Link Checker for WordPress
Checking links by hand means opening every page and clicking every link, then repeating the whole exercise regularly, because links keep breaking as content changes and external sites move. On a site with hundreds of pages, manual checking isn’t just slow; it reliably misses things like soft 404s, broken images, and failing scripts that look fine at a glance.
A broken link checker for WordPress automates this. It crawls your pages, tests every link and resource, and reports exactly what’s broken and where.
If your site runs on xCloud, you already have one built in. Broken Link Monitoring lives inside the site dashboard and runs as a managed, server-side scan, so there’s no plugin to install, no external crawler to configure, and no load added to your WordPress application. Here’s what it gives you:
- **Managed scans** – run a scan on demand or on a daily or weekly schedule.
- **Live scan progress** – watch pages scanned, links checked, healthy links, and findings update in real time.
- **Large crawl coverage** – scan up to 5,000 pages in a single run, with a safety limit for very large sites.
- **Broken link and broken image grouping** – see at a glance how many issues need attention.
- **Unverified issue visibility** – review resources xCloud couldn’t verify, such as timeouts, DNS errors, blocked requests, or redirect chains.
- **Filters and search** – narrow findings by issue type, resource type, or ignored status, or search by URL and source page.
- **Cancelable scans** – stop an active scan without losing findings already received.
- **CSV export** – download findings for reporting or external cleanup workflows.
- **Redirect-ready findings** – use broken-link findings as the starting point for fixing links through xCloud redirects.
## Find and Fix Broken Links on Your WordPress Site with xCloud
Before you start, make sure the site is a WordPress site managed in xCloud, your team has access to the Broken Links feature, you have permission to manage broken links for the site, and the site is reachable from the server so xCloud can crawl its pages.
Then follow these steps.
### Step 1: Access Broken Link Monitoring
From your xCloud dashboard, open the WordPress site, then go to **Site Monitoring → Broken Links**.
The Broken Link Monitoring page shows everything in one place: the scan status, schedule, summary counters, filters, and the findings table.
You’ll immediately see whether monitoring is enabled, when the next scan will run, the latest scan status, and the current issue summary.
### Step 2: Review the Scan Summary
The summary cards at the top give you a quick read on the health of the site:
- **Need attention** shows broken links, broken images, and resources xCloud could not verify.
- **Link health** shows healthy links and ignored findings.
- **Coverage** shows pages scanned, links checked, and whether the latest scan completed or is still running.
A zero count under “Need attention” means the site is healthy. Otherwise, the following steps show exactly where the problems are.
### Step 3: Run an On-Demand Scan
Click **Scan now** to start a scan immediately.
While the scan is running, xCloud updates the counters live. You can watch how many pages have been scanned, how many links have been checked, and how many findings have been detected so far.
You don’t need to keep the page open. The scan runs server-side and continues in the background even if you close the tab or move on to something else.
### Step 4: Cancel a Running Scan (Optional)
If a scan was started unintentionally or no longer needs to run, click **Cancel Scan**.
xCloud stops the active run cleanly. Anything discovered before cancellation stays in the findings list, so you don’t lose partial results.
### Step 5: Analyze and Filter Scan Findings
Once a scan has results, the findings table lists each affected source page along with its status and issue counts. To work through them efficiently, you can:
- Search by URL or source page.
- Filter by issue type: 404, DNS error, timeout, redirect, redirect chain, soft 404, or server error.
- Filter by resource type: pages, links, images, stylesheets, scripts, or media.
- Toggle **Show ignored** to include findings you’ve previously ignored.
- Open a finding row to inspect the details.
- Click **Export CSV** to download the full list.
A practical way to triage: filter for 404s on pages first, since those hurt visitors and SEO the most, then move on to broken images and external links.
### Step 6: Fix the Broken Links
With the findings in hand, work through them based on what each issue is:
- **Update the URL** where the target content still exists at a new address, correcting the link at its source page.
- **Set up a redirect in xCloud** where a page was moved or deleted, so the old URL forwards visitors and link equity to the right destination.
- **Remove the link** where the destination is permanently gone and has no replacement.
- **Ignore the finding** where it’s a false positive or intentionally unreachable, so it stops appearing in your active list.
### Step 7: Configure Automated Scan Scheduling
Use the schedule dropdown to choose how often xCloud should scan the site: daily, weekly, or manual only.
The selected schedule controls when the next managed scan runs. For content-heavy sites that publish often, daily scans catch new broken links quickly. For smaller or slower-moving sites, weekly is usually enough.
## Broken Link Monitoring Settings Overview
Option
What it does
Enabled
Turns Broken Link Monitoring on or off for the site.
Daily
Runs a managed scan every day.
Weekly
Runs a managed scan once per week.
Manual only
Disables scheduled scans; you can still run scans manually.
Scan now
Starts a new scan immediately.
Cancel Scan
Stops the active scan run.
Search
Finds results by URL or source page.
Issue filter
Narrows findings by error type, such as 404, DNS error, timeout, redirect, or soft 404.
Resource filter
Narrows findings by resource type, such as pages, links, images, stylesheets, scripts, or media.
Show ignored
Includes ignored findings in the table.
Export CSV
Downloads the findings list for offline review or reporting.
## Scan Limits and Edge Case Handling
Broken Link Monitoring is designed to handle large sites and imperfect network conditions predictably. These are the operational limits and how xCloud behaves when a scan can’t complete normally:
- Broken Link Monitoring is available for WordPress sites.
- A single scan can crawl up to 5,000 pages.
- xCloud also applies a links-checked safety ceiling so oversized scans can’t run indefinitely.
- If a site exceeds the scan budget, xCloud marks the scan as truncated rather than treating it as failed. You still get the findings it collected.
- If a scan stops sending progress, xCloud marks the run as failed so a new scan can start later.
- A cancelled scan keeps the findings discovered before cancellation.
## Find and Fix Broken Backlinks
Broken backlinks work in the other direction: another website links to a page on your site that no longer exists. The visitor clicking that link, and the SEO value the link carries, both hit a 404 on your end.
The fix is entirely on your side, and it doesn’t require contacting anyone. Set up a redirect in xCloud from the dead URL to the most relevant live page. The old backlink starts working again, visitors land on real content, and the link equity that external site was passing to you is preserved instead of lost.
As a habit, whenever you delete or move a page that has been live for a while, add a redirect at the same time. That single step prevents both broken backlinks and the internal 404s your next scan would otherwise catch.
## Benefits of Fixing Broken Links
Staying on top of broken links pays off in several ways:
- **Better user experience.** Visitors reach the content they clicked for instead of error pages. Fewer dead ends means lower bounce rates and more completed journeys, whether that’s reading an article or finishing a purchase.
- **Better crawlability.** Search engines discover and index your site by following links. Working links keep crawl paths open and stop crawl budget being wasted on URLs that lead nowhere.
- **Preserved link equity.** Internal links and backlinks pass authority between pages. Fixing broken links and redirecting removed pages keeps that equity flowing to your live content instead of dead-ending.
- **Stronger SEO performance.** A well-maintained link structure, clean crawl paths, and preserved equity all feed into better search rankings over time.
- **A more professional reputation.** Sites full of dead links look abandoned. Working links signal that the site, and the business behind it, is actively maintained and trustworthy.
- **Early warning for bigger problems.** A cluster of new broken links often points to something larger: a botched migration, a misconfigured plugin, an expired external service. Regular scans surface these issues before they spread.
## Best Practices for Preventing Broken Links
Fixing existing broken links is only half the work. Links decay constantly: you restructure content, external sites move or shut down, media files get replaced, and plugins or themes change how assets are loaded. Without a prevention routine, the findings list you just cleared will refill within months. The practices below turn broken-link management from a periodic cleanup project into a low-effort background process:
- **Turn on scheduled scans.** Set Broken Link Monitoring to daily or weekly so new issues surface automatically instead of accumulating unnoticed. Daily suits sites that publish frequently or link out heavily; weekly is usually enough for smaller or slower-moving sites. With team notifications enabled, new findings reach you without anyone remembering to check.
- **Set up redirects for moved or deleted pages.** Deleting or relocating a page without a redirect breaks every internal link, bookmark, and backlink pointing at it. Use your broken-link findings as the starting point and add redirects in xCloud so old URLs land on the correct content instead of a 404, preserving both visitors and the link equity those URLs have earned.
- **Keep your URL structure stable.** Every URL change is a potential broken link somewhere you can’t see, including on other people’s sites. Plan permalink structures before publishing, avoid renaming slugs on established content, and when a change is unavoidable, redirect the old URL immediately.
- **Review external links periodically.** You can’t control when other sites remove pages, change domains, or shut down, and external rot is invisible until someone clicks. A scheduled scan flags dead external resources as they appear, so you can update, replace, or remove the link before it affects readers.
- **Audit findings after major site changes.** Redesigns, migrations, theme switches, and large content reorganizations are when broken links appear in bulk. Run a manual scan right after any structural change instead of waiting for the next scheduled run.
## Wrapping Up
Broken links quietly cost you visitors, rankings, and sales until someone notices, and by then the damage is done. Finding and fixing them promptly makes your site more dependable and easier for users to navigate, and keeping a scanner running means new issues get caught before your visitors find them.
With Broken Link Monitoring built into xCloud, that whole routine lives in one place: open **Site Monitoring → Broken Links**, run a scan, work through the findings, set a schedule, and let it run in the background. If you manage client sites, the CSV export also gives you a clean list to include in maintenance reports or hand off for cleanup.
Happy fixing!
## Frequently Asked Questions
### Does the page need to stay open while a scan runs?
No. The scan runs server-side on xCloud’s infrastructure. The page shows live progress while it’s open, but the scan continues in the background if you close it.
### How many pages can one scan cover?
A single scan can crawl up to 5,000 pages. xCloud also applies a links-checked safety ceiling, and if a site exceeds the scan budget, the run is marked as truncated with all collected findings kept.
### Does xCloud create a separate task for every page it scans?
No. The streaming scanner uses one background scan run and streams progress back to xCloud in batches, so there’s no queue of thousands of small jobs.
### What happens when xCloud finds new broken links?
New findings appear in the Broken Links table, and team notifications can be sent when new issues are discovered.
### Can I export the findings?
Yes. Click **Export CSV** on the Broken Links page to download the full findings list for reporting or external cleanup.
### Can I stop a scan after it starts?
Yes. Click **Cancel Scan** while the scan is running. xCloud stops the run cleanly and keeps every finding received up to that point.
---
# Buzz Hosting - xCloud
> Managed Buzz worhosting on xCloud. Deploy the open-source AI workspace on a Docker server in one click, with free SSL, backups, and 24/7 support.
## Deploy your AI Agent in 1-Click - Managed Hermes Agent Hosting starts from $9.99
[Get Started Now](/hermes-agent-hosting/)
[](/)
Toggle Menu
Close Menu
[Menu](#)
[Solutions](#)Close SolutionsOpen Solutions
## Hosting Solutions
## Managed WordPress Hosting
Fast, secure WordPress hosting with automated updates, backups and more.
## WooCommerce Hosting
Managed hosting supporting high traffic sites, millions of checkouts per minute.
## Laravel Hosting
Laravel-optimized hosting with staging, SSL, and streamlined deployment tools.
## LLM Hosting
High-performance platform built for hosting large language models.
## n8n Hosting
Managed n8n hosting with optimized performance, a free SSL certificate, and more.
## OpenClaw Hosting
Secure AI agent hosting with Firewall, updates, backups, SSL and more
## Node.js Hosting
Easily deploy server-side or client-side app with Node.js hosting.
## Hosting Addons
Power Up Your Hosting Experience with Premium Addons
[](https://xcloud.host/deploy-openclaw)
[Pricing](/#pricing)
[Providers](#)Close ProvidersOpen Providers
## Cloud Providers
## xCloud Managed Hosting
Fully managed cloud hosting solution with full server backup & more
## DigitalOcean Hosting
Fast, easy cloud deployments on DigitalOcean with $200 credits for new user.
## Vultr Hosting
Feature-packed managed Vultr hosting with $100 free credits.
## Hostinger VPS
Bring your Hostinger VPS and manage with xCloud's advanced control panel.
## Any Provider
Connect your Ubuntu server to our platform and manage with powerful features easily.
## AWS Hosting
Optimized AWS hosting engineered for performance, security, and scalability.
## Google Cloud Hosting
Experience the power of Google Cloud with xCloud's user friendly platform
## Linode Hosting
Unleash the power of Linode servers with our feature-packed panel.
## Next Gen Hosting Built For Stability, Security & Speed
- 
### No Restrictions On Traffic & Sites.
- 
### Full Server Backup
## [Starts at **$5**/Month](#)
[Features](#)Close FeaturesOpen Features
## Features
## App Deployment
## Server Management
## Scheduled Tasks
## Monitoring & Alerts
## Security, SSL, Firewall
## Git, CLI & Dev Tools
## Staging Environments
## Team Collaboration
## Backups & Snapshots
## One Click Apps
## AI Website Builder
[See All Features](/features)
## Managed n8n Hosting:
For Smart & No-Code
Automation
[Learn More](/n8n-hosting/)
[Integrations](#)Close IntegrationsOpen Integrations
## Integrations
## WhatsApp Notifications
Get instant alerts and updates delivered straight to WhatsApp.
## Cloudflare Integration
Deliver content at top speed worldwide with built-in Cloudflare integration.
## Git Provider
Connect your repositories and automatic deployments from your Git projects.
## Google Drive Storage
Securely store automated backups in your Google Drive account for your backup.
## Slack Alerts
Connect to Slack for real-time performance and event notifications.
## Object Cache PRO
Speed Up Your WordPress Application Using Object Cache Pro.
## Mailgun
Integrate Mailgun in WordPress to send transactional emails easily.
## Connect Us :
- [](https://www.facebook.com/xCloud.host)
- [](https://x.com/xCloud_host)
- [](https://www.linkedin.com/company/xcloud.host/)
- [](https://www.youtube.com/@xCloud-Hosting)
- ### [Documentation](/docs)
- ### [Tutorials](https://www.youtube.com/@xCloud-Hosting)
## Get In Touch
Talk to our support team for any issues.
- ### [support@xcloud.host](mailto:support@xcloud.host)
[Talk To Us](/support)
## Join our global community
[](https://www.facebook.com/groups/xcloud.community)
[Resources](#)Close ResourcesOpen Resources
## Resources
## Blog
Read the latest guides, news, insights, and industry updates.
## Comparison Pages
Compare providers, features, and plans to find your perfect match.
## Support Portal
Access support tickets and live expert support 24/7 for any issues.
## Documentation
Step-by-step technical docs to help you build with confidence.
## Case Studies
See how real businesses scale and succeed with xCloud.
## Write for Us
Submit your expert articles, contribute tutorials, guides, and insights.
## Watch & Learn
## Next Gen Hosting Built For Stability, Security & Speed
[See All Videos](https://www.youtube.com/watch?v=oEE9OHo3_48)
[Join Free](https://app.xcloud.host/register)
[Login](https://app.xcloud.host/login)
[Join Free](https://app.xcloud.host/register)
[login](https://app.xcloud.host/login)
[Join Free](https://app.xcloud.host/register)
## Managed Hosting for self-hosted AI workspaces
# Fully Managed
Buzz Workspace Hosting
One-click Deploy.
Run chat, Git repositories, automated workflows, and AI agents in one place using managed Buzz hosting, with consistent performance and no maintenance work.
[Deploy Buzz Now – $24.99/mo](#pricing)
- 
### 24/7 Expert Support
- 
### No Lock-In, Cancel Anytime
## **The Learning Loop**
## Simple Steps To Launch Your Buzz Workspace in Minutes
Deploy and manage your Buzz instance with a carefully designed, streamlined workflow built for consistent speed, stability, and reliability from first deployment to everyday production use.
01
## Choose Your Server
Pick an xCloud managed server or connect your own provider, then set it up as a Docker server to deploy Buzz.
02
## Select Application
Open One Click Apps in your xCloud dashboard and choose Buzz from the available applications to begin the guided setup.
03
## Configure Your Workspace
Add your domain and deployment settings in the xCloud dashboard. We provision the Buzz in your server.
04
## Go Live Right Away
Confirm the setup, go live, and add your people and AI agents to their first channel in just a few clicks.
## Pricing
## Simple Pricing for Your Buzz Workspace
Your workspace grows, your bill does not. Add people and agents without changing the plan.
## Cloud VPS 6GB
## $24.99
Renews at $24.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=f292a3d0-fbcc-4c23-be7b-67f9cd677c69&app=buzz)
- ### 6 GB RAM
- ### 100 GB NVMe SSD
- ### 4 vCPU cores
- ### 30TB Bandwidth
## Popular deal
## Cloud VPS 16GB
## $59.99
Renews at $59.99/mo. Cancel anytime.
[Get started](https://app.xcloud.host/cart/product/checkout?product=33a8077d-dedc-4187-967d-b023ae20ed5c&app=buzz)
- ### 16 GB RAM
- ### 200 GB NVMe SSD
- ### 6 vCPU cores
- ### 30TB Bandwidth
## Cloud VPS 24GB
## $84.99
Renews at $84.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=b9bc978a-fd8e-4aea-a847-02ad127c9bfb&app=buzz)
- ### 24 GB RAM
- ### 300 GB NVMe SSD
- ### 8 vCPU cores
- ### 30TB Bandwidth
## Use Cases
## Built for Teams That Ship With Agents in the Room
These are starting points, not limits. If your agents are already doing real work, they should be doing it where the team can see it.
## Engineering Teams
- ### Repos beside the discussion
- ### Agent-opened patches
- ### Review in the channel
- ### Deploy notes that stay put
## Open Source Projects
- ### A home you actually own
- ### Contributors keep their keys
- ### Public channels, private relay
- ### No seat-based billing
## Agencies
- ### One hive per client
- ### Isolated servers and data
- ### Agents scoped per project
- ### Clean handover at the end
## Startups & Solo Builders
- ### Replace Slack + GitHub sprawl
- ### Flat infrastructure cost
- ### Agents on the team from day one
- ### Move fast without lock-in
## DevOps & SRE
- ### Incident channels with agents
- ### Automated status posts
- ### Signed change history
- ### Runbooks next to the work
## Regulated & Privacy-First
- ### Data on your own server
- ### Region of your choosing
- ### Audit trail on every action
- ### No third-party workspace vendor
## Features
## One Workspace To Build, Ship, & Scale for Your Team.
Docker helps developers build and run applications using containers. Containers bundle everything an application needs into a single, portable package.
- ### Chat, threads, voice, and searchable history
- ### Git repositories and code review in the same room
- ### AI agents as members, with their own identity
- ### One-click deployment, free SSL, and firewall
## Capabilities
## A Workspace built for how AI-native teams actually work
Buzz is an open-source workspace from Block built on the Nostr protocol. The interface feels like any modern chat tool. What’s different is who else is in the channel.
## Channels & Threads
Channels, threads and direct messages your team already knows how to use, with nothing new to learn.
## Voice & Media
Voice conversations and media sharing built into the same workspace as everything else.
## Git Repositories
Code hosting inside the workspace, so the repo, the review and the decision behind it live together.
## Agents as Members
An agent joins with its own identity and permissions instead of a bot token, it posts, reviews and ships like a teammate.
## Signed Identity
Every person and agent is a keypair. Every message, workflow step and Git event is a signed event.
## Automated Workflows
Trigger automations from the conversation and keep the output where the team can see it.
## Model Agnostic
Claude Code, Codex, goose, anything speaking the Agent Client Protocol works. Swap the model, keep the history..
## One Audit Trail
Human or agent, the author field works the same way. Every action traces back to who authorized it.
## Advanced Features
## Ready To Deploy Your AI Assistant?
Whether you run a single automation bot or manage large-scale AI workflows, Clawdbot VPS hosting delivers the reliability, flexibility, and performance your assistant needs to operate without limits. Deploy faster. Scale smarter. Stay in control.
## Fast Provisioning
Deploy faster using an xCloud Managed Server built with optimized stacks and high-speed SSDs.
## Enterprise-grade security
Protect your infrastructure with a free SSL certificate and more advanced security features at no additional cost.
## Intuitive Control Panel
From Server creation to application deployment, everything can be managed from our intuitive control panel.
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
**xCloud** isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Paul Goulart
@freelivingsoul
I set this up locally, tried AWS and Digital Ocean with disappointing results. Setup on Xcloud was easy and it’s still working!
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. xCloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## Your Agent Should Be Running Right Now.
Deploy a persistent Hermes agent in minutes. Connect it to Telegram, tools, files, APIs, and scheduled
tasks — then let it monitor, research, reply, code, report, and automate while you are offline.
[Start Deploying Now](#pricing)
[Read the Guide](/docs/how-to-deploy-hermes-agent-with-xcloud/)
- 
### No Lock-In
- 
### Cancel anytime
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What is Buzz?
Buzz is an open-source collaboration workspace from Block where people and AI agents work together in shared channels. It combines team chat, threads, voice, media sharing, Git repositories, and automated workflows, and it is built on the Nostr protocol so every identity is a keypair and every action is a signed event.
### How do I deploy Buzz on xCloud?
Buzz is available through xCloud’s One Click Apps. Create a Docker server in your xCloud dashboard, open One Click Apps, select Buzz, add your domain, and deploy. xCloud provisions the containers, maps the domain, and issues the SSL certificate for you.
### Do I need a Docker server to run Buzz?
Yes. Buzz runs as a containerised application, so it needs to be deployed on a Docker server. When you create a new server in xCloud, choose Docker as the server type — you can then deploy Buzz to it from One Click Apps.
## xCloud is the future of cloud hosting and server management for WordPress users, streamlining the way you host, deploy, manage or update your websites like never before!
## Get The Latest Updates
- [](https://www.facebook.com/xCloud.host)
- [](https://x.com/xCloud_host)
- [](https://www.linkedin.com/company/xcloud.host/)
- [](https://www.youtube.com/@xCloud-Hosting)
## Address:
xCloud Hosting, LLC. 124 Broadkill Rd #599 Milton, DE 19968-1008
## Products & Services
## Resources
## Compare xCloud
## Addons
## Quick Help
## **Company**
- #### [Privacy Policy](/privacy-policy/)
- #### [Terms and Condition](/terms-and-conditions/)
## A **[WPDeveloper](https://wpdeveloper.com/)** Creation, in Partnership with **[WPManageNinja](https://wpmanageninja.com/)**
## **xCloud Hosting LLC**. All rights reserved.
---
# Case Studies | Real Growth Powered By xCloud
> Explore real client success stories powered by xCloud. Discover how agencies, entrepreneurs, and creators reduce hosting costs, scale websites, and deliver faster, more reliable online experiences with powerful infrastructure.
- ## Discover
- ## Learn
- ## Grow
# Client Success Stories,
Powered by xCloud
Explore success stories of entrepreneurs, creators, bloggers, and small business owners who built and scaled their online presence with xCloud by their side.
## How Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
## Gary Moody
Owner
[See Case Study](/case-study/advanced-web-strategies/)
## How Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud
## Ed Ellingham
Co-Owner, Cloud Nine Web
[See Case Study](https://xcloud.host/cloud-nine-web-agency/)
## How Newman Web Solutions Ensured Perfect Uptime and Seamless Scaling For 120+ WordPress Sites with xCloud
## Lori Newman
Creative Director & Co-Founder
[See Case Study](/case-study/newman-web-solutions-agency/)
## How Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & Node.js Sites Efficiently
## Kevin Heinrichs
CEO
[See Case Study](/case-study/kevin-heinrichs/)
## How Wattz Web Design Saved 50% on Hosting by Migrating 140+ Sites to xCloud
## Donald McGuinn
CEO, Wattz Web Design and Marketing
[See Case Study](https://xcloud.host/case-studies/wattz-web-design/)
[Explore More](/case-studies/)
## Take The Step, Create Your Success Story
Join millions of business owners growing with xCloud. Get powerful tools to build and scale your online presence in
one place. Manage every web project with speed, performance, and seamless deployment.
[Get Started](/case-studies/)
---
# Case Studies | Real Growth Powered By xCloud
> Explore real client success stories powered by xCloud. Discover how agencies, entrepreneurs, and creators reduce hosting costs, scale websites, and deliver faster, more reliable online experiences with powerful infrastructure.
- ## Discover
- ## Learn
- ## Grow
# Client Success Stories,
Powered by xCloud
Explore success stories of entrepreneurs, creators, bloggers, and small business owners who built and scaled their online presence with xCloud by their side.
## How Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
## Gary Moody
Owner
[See Case Study](/case-study/advanced-web-strategies/)
## How Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud
## Ed Ellingham
Co-Owner, Cloud Nine Web
[See Case Study](https://xcloud.host/cloud-nine-web-agency/)
## How Newman Web Solutions Ensured Perfect Uptime and Seamless Scaling For 120+ WordPress Sites with xCloud
## Lori Newman
Creative Director & Co-Founder
[See Case Study](/case-study/newman-web-solutions-agency/)
## How Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & Node.js Sites Efficiently
## Kevin Heinrichs
CEO
[See Case Study](/case-study/kevin-heinrichs/)
## How Wattz Web Design Saved 50% on Hosting by Migrating 140+ Sites to xCloud
## Donald McGuinn
CEO, Wattz Web Design and Marketing
[See Case Study](https://xcloud.host/case-studies/wattz-web-design/)
[Explore More](/case-study/)
## Take The Step, Create Your Success Story
Join millions of business owners growing with xCloud. Get powerful tools to build and scale your online presence in
one place. Manage every web project with speed, performance, and seamless deployment.
[Get Started](/case-study/)
---
# How One Agency Manages 70+ WordPress Sites on xCloud
> See how Advanced WEB Strategies manages 70+ client sites from one dashboard with xCloud, saving over $2K a year and 56 hours a month on maintenance. (148 characters)
[Case Studies](/)[Case Study](/case-study/) Advanced WEB Strategies
# How Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
- ### 6+ Servers Managing with Ease
- ### 70+ Sites Deployed
- ### 5 Minutes to go live with a site
I couldn’t be more satisfied with the process and the exceptional performance of xCloud. It’s been a game-changer for managing our websites efficiently.
#### $2,000/Year
### saving on servers &
upkeep costs
#### 56 hrs/Mo
### saved from routine
maintenance
Gary Moody, Owner
#### Advanced WEB Strategies
Website:
#### [advancedwebstrategies.com](http://advancedwebstrategies.com)
Industry
#### Web Design & Digital Strategy
Location:
#### United States
Websites:
WordPress, Membership, Ecommerce & More
## About Advanced WEB Strategies
Advanced WEB Strategies is a web design and marketing company. Gary Moody runs it. The company builds good websites that do not cost a lot. It helps non-profits and small businesses.
Gary has built websites for more than 20 years. In that time, he tried many ways to host them. He even ran his own server. He also used big-name hosting companies.
## About Wattz Web Design and Marketing
Each one was good at some things but not at others. Some were powerful but hard to use. Some were simple but slow.
## About Wattz Web Design and Marketing
As the company grew, the problems grew too. Support was not steady. Big issues did not get fixed. Every three years, Gary had to renew his servers, and that slowed his work down. He spent too much time fixing his setup instead of helping clients.
## About Wattz Web Design and Marketing
Then Gary found xCloud, and things changed. Now he can focus on what matters most. He builds better websites. He helps clients faster. He grows his company with confidence.
Gary Moody
OwnerOwner
“What truly sets xCloud apart is their exceptional support and service. Their team is incredibly responsive and knowledgeable, always willing to go the extra mile to ensure my clients’ websites run smoothly”
## The Challenges
Inconsistent Support, Server Frustrations, and Performance Bottlenecks
## About Wattz Web Design and Marketing
As Advanced Web Strategies grew, they didn’t struggle with catastrophic outages, they struggled with operational drag. Managing dozens of websites across multiple environments made routine tasks increasingly time-consuming. While nothing was technically broken, the growing complexity created an invisible bottleneck that consumed valuable time and resources. Three areas, in particular, were slowing the team down.
## Managing Client Sites At Scale
With a growing roster of client websites to maintain, Advanced WEB Strategies faced mounting infrastructure challenges. Keeping sites fast, secure, and well-supported was becoming harder to manage effectively at scale.
## Inconsistent Technical Support
Reliable support is essential when client websites are on the line. Gary’s previous hosting partners couldn’t deliver consistent help when urgent issues surfaced, and responses often lacked the urgency or clarity those moments demanded. Over time, this eroded trust and created unnecessary stress.
## Disruptive Server Renewal Cycles
Rigid three-year renewal cycles became a recurring operational headache. Each renewal required time, planning, and coordination that distracted from core business activities, pulling Gary into infrastructure logistics instead of clients and growth.
## Unstable Performance and Backups
Performance instability compounded the strain. Sites experienced noticeable latency, backup and restoration processes were unreliable and complicated, and troubleshooting consumed valuable hours, especially without dependable support to lean on.
## No True Partnership
Beyond the technical concerns sat a deeper issue. Gary felt like just another account in a large hosting system, with no real attentiveness or strategic alignment. For an agency committed to serving non-profits and small businesses, that disconnect had become unacceptable.
## About Wattz Web Design and Marketing
## The Solutions
## xCloud Delivered Simplicity, Speed, and True Partnership
After years of juggling infrastructure challenges, Advanced WEB Strategies needed more than just another hosting provider. The agency needed a streamlined system that combined performance, control, and dependable support. xCloud delivered exactly that.
- 
### One-Click Blueprint Deployments
Gary builds custom Blueprints for each client, launches fully configured staging sites in one click, then reviews, updates DNS, and clicks “Go Live” to publish in minutes.
- 
### Centralized Multi-Site Management
As of Q1 2026, Gary runs 70+ sites from one dashboard, handling plugins, SSL, monitoring, and performance without logging into individual WordPress installs. Hours of maintenance now take minutes.
## _“Spinning up staging sites is a breeze. Updating various plugins on multiple websites is much easier. No more logging in and out of each website, I am able to handle these functions from a single control panel. “_
- 
### Optimized Performance and Stability
Speed improved immediately after the move. Sites load fast even with multiple plugins, latency issues disappeared, and server reboots complete quickly, giving consistent, reliable performance across every site.
- 
### Exceptional Support That Protects Client Relationships
When a site flooded the server and caused a crash, xCloud’s team quickly diagnosed the multiple causes, fixed them, and prevented recurrence, protecting Gary’s client relationship
## The Results
## 70+ Websites Managed Efficiently with Faster Deployments And Stronger Client Confidence
Since moving to xCloud, Advanced WEB Strategies has fundamentally transformed how it deploys, manages, and maintains client websites across its entire portfolio. What was once a fragmented, hard-to-maintain hosting setup has become a streamlined, single-dashboard operation that serves both clients and the agency’s day-to-day work.
With those complexities centralized in a single platform, their focus shifted from managing systems to delivering more value for clients. Instead of asking, “How do we manage all these sites?”, the team could focus on a more important question: “What can we build next?” That shift gave Advanced Web Strategies the operational foundation to scale more efficiently as they continued to grow.
#### $0/yr
### Saved on Servers & Upkeep
#### 0/mo
### Maintenance Time Saved
#### 0+
### Client Sites Managed
#### 0 min
### To Go Live
Gary Moody
Owner, Advanced WEB Strategies
xCloud is a game-changer. It combines powerful server performance with a clean, intuitive interface that makes managing multiple client sites easy. But what truly sets xCloud apart is the support. Their team is responsive, knowledgeable, and always willing to go the extra mile. It’s a breath of fresh air for web professionals like myself.”
## About Wattz Web Design and Marketing
## Share this article
- [](https://www.facebook.com/sharer/sharer.php?u=https://xcloud.host/case-study/advanced-web-strategies/)
- [](https://twitter.com/share?text=Advanced%20WEB%20Strategies&url=https://xcloud.host/case-study/advanced-web-strategies/)
- [](https://www.linkedin.com/shareArticle?title=Advanced%20WEB%20Strategies&url=https://xcloud.host/case-study/advanced-web-strategies/&mini=true)
## Ready to Redefine Your Hosting Experience?
We feel proud to see success stories like Newman Web Solutions Agency thriving with xCloud – it is exactly why we built this platform. Join xCloud to experience the same cost savings, performance improvements, and effortless
management that helped them grow.
[Get Started For Free](https://app.xcloud.host/register)
---
# Cloud Nine Web Agency - xCloud
> Cloud Nine Web streamlined hosting, improved team efficiency, and boosted client satisfaction while managing 200+ sites across 6+ servers with xCloud.
[Case Study](/case-study/) Cloud Nine Web Agency
# [How Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud](https://xcloud.host/case-studies/cloud-nine-web)
- ### Increased client satisfaction
- ### Streamlined hosting operations
- ### Accelerated team efficiency
- ### Reduced labor costs
“The platform’s intuitive interface allows us to delegate tasks to team members who might not have as much experience with more complex panels, which helps us get more done, faster. It’s streamlined our workflow and freed up my time to focus on other priorities.”
## Ed Ellingham
Co-Owner, Cloud Nine Web
#### 6+
### SERVERS MANAGED
#### 150+
### WEBSITES POWERED
#### 200+
### SITES MIGRATED
---
# Kevin Heinrichs
> Discover how Kevin Heinrichs cut hosting costs by 84% with xCloud while running WooCommerce stores and Node.js SaaS platforms with faster performance and full server control.
[Case Studies](/)[Case Study](/case-study/) Kevin Heinrichs Marketing
# How Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & NodeJS Sites Efficiently
- 
### Reduced annual hosting expenses by nearly $2,000
- 
### Run WordPress + Node.js on same platform
- 
### Zero downtime with massive performance
Currently just 3x servers, but planned a lot more since I have a 250x Supreme LTD package. I started to create automation to make new websites.
## Kevin Heinrichs
CEO
#### 10+
### SERVERS MANAGED
#### 120+
### WEBSITES POWERED
#### 100+
### SITES MIGRATED
Client:
#### Kevin Heinrichs Marketing
Website:
#### [kevinheinrichs.com](http://newmanwebsolutions.com)
Industry:
#### eCommerce Store
Location:
United States
## About Kevin Heinrichs & His Infrastructure-Driven Business Model
Kevin Heinrichs is a performance-focused entrepreneur building and scaling multiple WooCommerce stores, dropshipping operations, service-based websites, and Node.js SaaS platforms. His business depends on speed, uptime, and operational flexibility. Every millisecond at checkout matters. Every server decision impacts revenue.
## About Wattz Web Design and Marketing
Unlike traditional agencies managing client projects, Kevin operates a high-volume, automation-driven ecosystem. He continuously launches new websites, experiments with infrastructure setups, and prepares for large-scale expansion. His goal is to automate website creation and scale aggressively in the AI-driven digital economy.
## About Wattz Web Design and Marketing
For Kevin, hosting is not just a technical requirement. It is a strategic growth layer. Infrastructure must be cost-efficient, fast, flexible, and fully controllable. Anything less creates friction, limits scalability, and directly affects business performance.
Kevin Heinrichs
CEO
“Performance is huge, it is so much faster. I can decide to restart a server for updates, that is so much useful then I can do that in not a important time slot like then my customers are sleeping.”
## The Challenges
High Costs, Limited Control, and Scaling Constraints
## About Wattz Web Design and Marketing
As Kevin’s portfolio of WooCommerce stores and SaaS platforms expanded, his previous hosting setup began creating serious operational friction. What initially seemed manageable quickly became expensive, restrictive, and misaligned with his long-term growth strategy.
## Rising Hosting Costs with Slot-Based Pricing
Kevin previously spent nearly $2,000 per year on hosting. Pricing models tied to website slots forced him to pay for capacity he did not always use. For a builder planning to launch and automate hundreds of websites, this structure limited flexibility and made scaling inefficient.
## Lack of Infrastructure Control
One of the most critical pain points was the inability to control server-level decisions. Scheduled server reboots during peak German checkout hours disrupted customer purchases. When visitors could not complete orders, revenue suffered directly. Kevin needed the authority to manage updates and restarts during low-traffic windows, not at times chosen by the provider.
## Performance and Provider Instability
Before switching to xCloud, Kevin experimented with several hosting platforms. Some delivered inconsistent performance. Others limited server-level control. A few improved speed but introduced higher costs or reduced flexibility. None offered the balance of performance, autonomy, and cost efficiency he needed.
For a performance-driven WooCommerce and SaaS operator, these limitations were not minor inconveniences. There were structural barriers to scaling confidently.
## About Wattz Web Design and Marketing
## The Solutions
## Full Control, Faster Deployments, and Infrastructure Built for Scale
After evaluating multiple hosting providers, Kevin transitioned to xCloud with a clear objective: regain infrastructure control, reduce unnecessary costs, and build a scalable foundation for high-volume website creation.
- 
### Complete Server-Level Control
With xCloud, Kevin can decide exactly when to restart servers, apply updates, and manage maintenance windows. This flexibility allows him to schedule technical changes during off-peak hours when customers are asleep, protecting checkout conversions and eliminating revenue disruptions caused by forced provider reboots.
- 
### 84% Massive Cost Efficiency Without Performance Trade-Off
By moving from a slot-based pricing model to xCloud’s infrastructure-driven approach, Kevin reduced his annual hosting expenses by 84%, dropping from nearly $2,000 per year to just under $325. Despite the dramatic reduction in cost, performance improved significantly. His WooCommerce stores now run faster while operating on a far leaner budget.
- 
### One-Click WordPress and Node.js Deployments
xCloud simplified both WordPress and SaaS infrastructure. Kevin can launch WordPress sites instantly using one-click installs and blueprints. For his Node/js platforms, xCloud’s one-click Node/js deployment with direct GitHub integration enables streamlined development workflows and faster iteration cycles.
- 
### Automation-Ready Infrastructure
With a lifetime deal and expansion plans underway, Kevin is building automation systems to spin up new websites efficiently. xCloud’s server creation process, blueprint functionality, database access, and streamlined Hetzner provisioning allow him to prepare for large-scale deployment without operational bottlenecks.
- 
### Flexible Team Access and Collaboration
Even as a solo operator, Kevin values collaborative flexibility. xCloud makes it easy to join a partner’s team and gain secure access to servers when needed. Permission management remains simple and intuitive, reducing administrative overhead. For Kevin, xCloud is not just a hosting provider. It is a performance-focused infrastructure layer that enables aggressive scaling, precise control, and sustainable cost management.
## The Results
## 84% Cost Reduction, Faster Performance, and Scalable Freedom
After migrating to xCloud, Kevin experienced immediate financial and operational impact. The shift was not incremental. It fundamentally changed how he manages and scales his infrastructure.
## 84% Reduction in Annual Hosting Costs
Since migrating to xCloud, Newman Web Solutions has achieved near-perfect uptime across its entire hosting environment. Page load speeds improved significantly, and performance remains consistent even during periods of heavy traffic. Clients noticed the difference almost immediately, frequently commenting on how much faster and smoother their websites feel.
## 120+ Sites Managed Confidently Across 10 Servers
Kevin reduced his annual hosting expenses by nearly $2,000. This 84% cost reduction freed up capital that he can now reinvest into growth, automation, and new projects.
Unlike traditional slot-based pricing, xCloud allows him to scale infrastructure without paying for unused capacity. Cost efficiency now aligns directly with expansion.
## Fast & Stable Performance Without Compromise
Despite the dramatic reduction in cost, Kevin did not sacrifice performance. His WooCommerce stores load faster, his Node.js platforms run smoothly, and overall server responsiveness improved significantly.
He gained something even more valuable than speed: control.He now chooses when to restart servers, apply updates, and manage maintenance windows. No more forced reboots during peak checkout hours. No more revenue risk during critical sales moments.
## Faster Deployments and Workflow Acceleration
WordPress installations now take minutes with one-click setup and blueprints. Node.js deployments connect directly to GitHub, accelerating SaaS development cycles.
Infrastructure that once required manual effort now runs through streamlined processes. This allows Kevin to focus on launching, testing, and scaling instead of managing hosting limitations.
## Built for Aggressive Growth
With three servers already deployed and expansion plans underway, Kevin is building automation systems to generate new websites at scale. xCloud gives him the infrastructure flexibility to expand without introducing cost bottlenecks.
Kevin Heinrichs
CEO
“Switching to xCloud was the best infrastructure decision I made this year. I managed to slash my hosting costs by over 80% without losing a single millisecond of performance. For any serious WooCommerce developer, xCloud isn’t just a tool; it’s a competitive advantage!”
## About Wattz Web Design and Marketing
## Share this article
- [](https://www.facebook.com/sharer/sharer.php?u=https://xcloud.host/case-study/kevin-heinrichs/)
- [](https://twitter.com/share?text=Kevin%20Heinrichs%20Marketing&url=https://xcloud.host/case-study/kevin-heinrichs/)
- [](https://www.linkedin.com/shareArticle?title=Kevin%20Heinrichs%20Marketing&url=https://xcloud.host/case-study/kevin-heinrichs/&mini=true)
## Ready to Redefine Your Hosting Experience?
We feel proud to see success stories like Newman Web Solutions Agency thriving with xCloud – it is exactly why we built this platform. Join xCloud to experience the same cost savings, performance improvements, and effortless
management that helped them grow.
[Get Started For Free](https://app.xcloud.host/register)
---
# Newman Web Solutions Agency
> Learn how Newman Web Solutions migrated 100+ WordPress sites to xCloud, achieved near-perfect uptime, faster performance, and managed 120+ sites across 10 servers.
[Case Studies](/)[Case Study](/case-study/) Newman Web Solution
# 120+ WordPress Sites, Zero Downtime, No Server Headaches : Inside Newman Web Solutions’ Hosting Transformation
- 
### Reduced server support tickets
- 
### Delivered perfect uptime always
- 
### Improved site load speeds
xCloud offered the perfect blend of managed hosting, performance, and ease of use. Their platform is clearly built with agencies and developers in mind”
## Lori Newman
Creative Director & Co-Founder
#### 10+
### SERVERS MANAGED
#### 120+
### WEBSITES POWERED
#### 100+
### SITES MIGRATED
Client:
#### Newman Web Solutions Agency
Website:
#### [newmanwebsolutions.com](http://newmanwebsolutions.com)
Industry:
#### Agency
Location:
United States
## About Newman Web Solutions Agency
For over 15 years, Newman Web Solutions Agency has helped small and mid-sized businesses grow through strategic web design, SEO, branding, and marketing automation. Based in Atlanta and Marietta, Georgia, the agency is known for its high standards, technical expertise, and commitment to client success.
## About Wattz Web Design and Marketing
As their client base expanded, hosting reliability became mission-critical. Recurring downtime, inconsistent performance, and the growing burden of server management were putting unnecessary strain on the team and introducing risks they could no longer afford – especially for high-visibility, high-traffic websites.
Lori Newman
Creative Director & Co-Founder
“xCloud has become a cornerstone of our hosting and maintenance operations. It’s made our processes faster, more reliable, and more scalable. With fewer hosting headaches, our team can focus more on client growth and innovation – making xCloud a key part of our business strategy.”
## The Challenges
Downtime, Server Complexity, and Scaling Risks Were Holding the Agency Back
## About Wattz Web Design and Marketing
As Newman Web Solutions Agency continued to scale, hosting challenges became increasingly difficult to ignore. Managing a large portfolio of client WordPress sites across shared hosting and VPS environments introduced instability, inefficiencies, and unnecessary risk, especially for high-traffic and mission-critical websites.
## Recurring Downtime and Inconsistent Performance
Shared hosting environments frequently led to unpredictable performance and recurring downtime. Even brief outages created frustration for clients and put pressure on the team to respond quickly. For an agency known for reliability and attention to detail, these inconsistencies were unacceptable.
## Limited Support When It Mattered Most
While previous tools offered flexibility, they lacked fully managed support. When performance issues or server-level problems arose, Newman Web Solutions often had to diagnose and resolve them independently. This lack of dependable, expert assistance increased stress and slowed response times during critical situations.
## Operational Risk During High-Traffic Campaigns
The stakes became even higher for clients running public-facing campaigns and high-traffic initiatives. Without the ability to scale resources quickly and confidently, traffic spikes posed a real risk to performance, uptime, and reputation. The agency needed a hosting solution that could handle sudden demand without compromise.
## About Wattz Web Design and Marketing
## The Solutions
## xCloud’s Fully Managed Hosting Built For Agencies At Scale
To overcome performance instability, server complexity, and scaling risks, Newman Web Solutions Agency transitioned its entire hosting operation to xCloud – a platform designed specifically for agencies managing large volumes of WordPress sites.
- 
### Fully Managed Infrastructure Without the Sysadmin Burden
xCloud eliminated the need for hands-on server administration. Server maintenance, updates, and optimizations are handled automatically, allowing the Newman Web Solutions team to focus on client strategy and creative execution rather than infrastructure management. This shift alone freed up significant internal time and reduced operational stress.
- 
### Optimized Web Stacks with LiteSpeed Performance
Performance consistency was a top priority. xCloud’s optimized web stacks and LiteSpeed caching delivered immediate improvements in speed and stability across all client sites. Faster load times, reduced server strain, and reliable uptime became the new standard—without manual tuning or third-party tools.
## _“xCloud has become a cornerstone of our hosting and maintenance operations. It’s made our processes faster, more reliable, and more scalable. With fewer hosting headaches, our team can focus more on client growth and innovation – making xCloud a key part of our business strategy.”_
- 
### One-Click Deployments and Faster Daily Workflows
Launching new WordPress sites, configuring SSL certificates, and managing backups are now handled in minutes. xCloud’s one-click deployments and automated backups streamlined everyday tasks, cutting setup time dramatically and reducing the risk of human error during deployments and updates.
- 
### Seamless Scaling for High-Traffic Campaigns
One of xCloud’s most valuable advantages for Newman Web Solutions is the ability to scale server resources instantly. During high-traffic public campaigns, the team can increase resources on demand, ensuring flawless performance without downtime or overpaying for unused capacity.
## _“xCloud’s support team is outstanding. They’re quick to respond, technically skilled, and genuinely helpful.”_
- 
### Secure Collaboration With Expert Support Team
xCloud enables secure team collaboration with clear role-based permissions, so designers, developers, and project managers can work together while keeping access controlled. When help is needed, xCloud’s support team acts like an extension of your team, providing fast responses and expert guidance on everything from server setup to performance tuning.
## The Results
## 120+ WordPress Sites Running Faster, More Reliably, and With Zero Stress
The transition to xCloud delivered immediate and lasting results for Newman Web Solutions Agency. What was once a source of instability and operational friction is now a dependable, scalable foundation powering the agency’s growth.
## Near-Perfect Uptime and Noticeably Faster Performance
Since migrating to xCloud, Newman Web Solutions has achieved near-perfect uptime across its entire hosting environment. Page load speeds improved significantly, and performance remains consistent even during periods of heavy traffic. Clients noticed the difference almost immediately, frequently commenting on how much faster and smoother their websites feel.
## __“We migrated one of Atlanta’s most well-known public parks – managed by a nonprofit organization in partnership with the City of Atlanta and several others from WP Engine to xCloud. The transition was seamless, and performance improved immediately.”__
## 120+ Sites Managed at Scale With Zero Downtime
Newman Web Solutions now runs more than 120 WordPress sites across 10 servers from a single, intuitive control panel. The team migrated over 100 sites to xCloud without any downtime or business disruption. Automated workflows replaced manual monitoring, and every site went live quickly with improved performance, giving the agency full control and confidence at scale
## Faster Deployments and Fewer Support Tickets
Daily workflows are now dramatically more efficient. New sites can be deployed in minutes instead of hours, SSL certificates are managed automatically, and scaling server resources is instant. As a result, server-related support tickets have dropped significantly – freeing the team to focus on growth, strategy, and creative development.
## Proven Stability During High-Traffic Campaigns
xCloud proved its value during a critical high-traffic public campaign for a nonprofit organization partnered with the City of Atlanta. When traffic surged, server resources were scaled on demand at a lower cost, and the site handled the spike flawlessly without a single slowdown or outage. The successful campaign strengthened client trust and validated Newman Web Solutions’ hosting strategy.
Lori Newman
Creative Director & Co-Founder
“xCloud has completely transformed how we manage hosting for our clients. The performance, reliability, and support are unmatched. Their managed servers, LiteSpeed integration, and responsive team make them the perfect hosting partner for agencies that value speed and peace of mind.”
## About Wattz Web Design and Marketing
## Share this article
- [](https://www.facebook.com/sharer/sharer.php?u=https://xcloud.host/case-study/newman-web-solutions-agency/)
- [](https://twitter.com/share?text=Newman%20Web%20Solution&url=https://xcloud.host/case-study/newman-web-solutions-agency/)
- [](https://www.linkedin.com/shareArticle?title=Newman%20Web%20Solution&url=https://xcloud.host/case-study/newman-web-solutions-agency/&mini=true)
## Ready to Redefine Your Hosting Experience?
We feel proud to see success stories like Newman Web Solutions Agency thriving with xCloud – it is exactly why we built this platform. Join xCloud to experience the same cost savings, performance improvements, and effortless
management that helped them grow.
[Get Started For Free](https://app.xcloud.host/register)
---
# Changelogs - xCloud
> Changelogs Archive - xCloud
## **🔥 New Features**
### [**Cloudflare Enterprise**](https://xcloud.host/docs/how-to-activate-the-cloudflare-enterprise-addon/)
Cloudflare Enterprise is now available on xCloud as a per-domain add-on. You get the same enterprise network the largest brands run on, fully managed by xCloud, for a flat $5 per domain, per month. No Cloudflare account, no enterprise contract, and no DNS work on your side.
Turn it on per domain from Addons → Cloudflare Enterprise, or directly from a site. xCloud handles the zone setup, the certificate, and the routing.
- Serve your site from Cloudflare’s global network across 330+ locations.
- Pay a flat $5 per domain, per month, with no traffic-based charges.
- Get managed SSL on every domain you enable.
- Full page caching at the edge, so visitors are served from the location closest to them.
- Early Hints, so browsers start loading assets before the page response arrives.
- Automatic image optimization, in lossy or lossless mode.
- One-click cache purge across the whole network.
- Enterprise WAF that blocks SQL injection, XSS, and zero-day attempts in real time.
- Advanced DDoS protection at the edge, before traffic reaches your server.
- Browser Integrity Check and one-click Under Attack Mode for when you are being targeted.
- Crawler blocking to stop AI bots from scraping your content.
- Real-time request and data transfer analytics, including Cloudflare-served versus origin traffic.
- Cache performance and top countries, so you can see where your traffic comes from and how much of it never touches your server.
## **🌟 30+ One Click Apps: Self-Host Your Whole Stack in a Couple of Clicks**
We’ve added a big batch of new apps to xCloud One Click Apps, so you can now self-host search, analytics, docs, BI, automation, passwords, media, Git, and more, all in a couple of clicks. Pick an app and xCloud handles the setup, SSL, and config for you. With this release, we now support 30+ one click apps.
## **🆕 New Apps**
1. **Redis** In-memory data store for caching, queues, and fast key-value workloads.
2. **Moodle** Open-source LMS to build courses, run quizzes, and track grades on your server.
3. **BookStack** Open-source wiki and documentation platform for team knowledge bases, SOPs, and internal docs.
4. **Excalidraw** Virtual whiteboard for hand-drawn-style diagrams, wireframes, and flowcharts. Runs entirely in the browser — fast, private, and works offline once loaded.
5. **Metabase** Open-source business intelligence — connect your databases, ask questions in a friendly UI or SQL, and build shareable dashboards. No per-seat pricing, your data stays on your server.
6. **Matomo** Privacy-first, self-hosted web analytics with full data ownership, visitor insights, goals, campaigns, and tag management.
7. **Vaultwarden** Lightweight, Bitwarden-compatible password manager server. Works with all official Bitwarden apps and browser extensions.
8. **Gitea** Lightweight self-hosted Git forge with repos, pull requests, issues, packages, and Actions-compatible CI workflows. Ships SQLite + HTTPS cloning out of the box.
9. **Meilisearch** Lightning-fast, typo-tolerant search engine — an open-source Algolia alternative for apps and websites.
10. **Odoo Community** Open-source business suite with modular CRM, sales, invoicing, inventory, project, website, and e-commerce apps.
11. **Qdrant** Vector database and similarity-search engine for semantic search, recommendations, embeddings, and RAG. Includes REST APIs and a web dashboard.
12. **Plane** Open-source project management for issues, cycles, modules, pages, and team workspaces.
13. **Paperless-ngx** Open-source document management with OCR, full-text search, tagging, and automated organization.
14. **Listmonk** High-performance, self-hosted newsletter and mailing-list manager with subscriber segmentation, campaign analytics, templates, and a REST API.
15. **Keycloak** Open-source identity and access management with single sign-on, OpenID Connect, OAuth 2.0, SAML, user federation, and multi-factor authentication.
16. **Jellyfin** Free, open-source media server for organizing and streaming movies, TV, music, photos, and live TV to web, mobile, and TV clients — no subscriptions or premium gates.
17. **Hoppscotch** Open-source API development workspace for REST, GraphQL, realtime protocols, collections, environments, and teams.
18. **draw.io** Private browser-based diagramming for flowcharts, architecture diagrams, UML, network maps, and more. Stateless server with files saved or exported by the user.
19. **Discourse** Open-source community platform for discussions, support forums, knowledge sharing, and long-form conversations.
20. **Databasus** Self-hosted database backup console for PostgreSQL, MySQL, MariaDB, and MongoDB with schedules, retention, encrypted storage, notifications, and restore workflows.
21. **changedetection.io** Self-hosted website change monitoring for prices, inventory, policy pages, releases, and other web content, with configurable alerts and change history.
22. **Appsmith** Open-source low-code platform for building internal tools, admin panels, dashboards, and database-backed workflows with a visual editor, JavaScript, APIs, and data-source integrations.
23. **Actual Budget** Privacy-focused, local-first personal finance and envelope budgeting with reports, sync, optional bank import, and optional end-to-end encryption.
24. **Activepieces** Open-source workflow automation with a visual builder, AI agents, and hundreds of integrations.
25. **Linkding** Fast, lightweight self-hosted bookmark manager with tags, search, browser extensions, import/export, and an authenticated REST API.
26. **Wiki.js** Modern open-source knowledge base with access control, search, and collaborative editing.
27. **Wallos** Self-hosted subscription tracker for recurring payments, renewal dates, categories, currencies, statistics, and configurable notifications.
28. **Shiori** Lightweight self-hosted bookmark manager with full-text search, tags, import/export, browser extensions, and offline webpage archiving.
29. **PrivateBin** Zero-knowledge encrypted pastebin for expiring text, code, and password-protected links. Encryption and decryption happen in the browser.
30. **pgAdmin** Web-based administration for PostgreSQL, with a secure initial administrator account and persistent server definitions, preferences, sessions, and user files.
31. **ntfy** Private push notifications for scripts, apps, and infrastructure. Publish over HTTP and receive alerts in the web UI or ntfy mobile apps.
---
# v.2.5.1 - xCloud
> Deploy and run an autonomous company powered entirely by AI agents — fully managed on xCloud. No coding or server skills needed.
## 🔥 New Features
### 🆕 [Introducing Paperclip Hosting on xCloud](/docs/how-to-deploy-paperclip-with-xcloud/)
Deploy and run an autonomous company powered entirely by AI agents — fully managed on xCloud. No coding or server skills needed.
Paperclip lets you hire AI employees, set goals and budgets, and let your agents run 24/7. You stay in control. They handle the work.
✅ Full org chart setup – hire AI employees for any role
✅ Set goals and budgets, agents work toward them automatically
✅ Per-agent budgets to prevent runaway API costs
✅ Audit log of every decision and tool call
🌟With xCloud, you get a fully managed server with automatic updates, security, logs, SSH, and more – all in one place.
**📑 Requirements:**
- xCloud Managed Server with at least 4GB RAM
- Dedicated server (no other apps run alongside Paperclip)
### 🆕 [Gemma 4 Variants Support for Ollama](/docs/how-to-use-gemma-4-with-xcloud/)
Gemma 4 is Google’s lightweight open model family – and it’s now supported in Ollama on xCloud. You can pull Gemma 4 variants directly from your Ollama dashboard and connect them to OpenClaw or other agent workflows for fully self-hosted, private, API-cost-free AI.🔥
Great for teams that want to experiment with local models alongside options like DeepSeek R1, or run sensitive workloads entirely on their own infrastructure.
### 🆕 **[Cloudflare Under Attack Mode Toggle](/docs/how-to-turn-on-cloudflare-under-attack-mode/)**
Cloudflare’s Under Attack mode performs additional security checks to help mitigate layer 7 DDoS attacks. Validated users access your website and suspicious traffic is blocked. It is designed to be used as one of the last resorts when a zone is under attack (and will temporarily pause access to your site and impact your site analytics).
You can now enable or disable Cloudflare’s “Under Attack Mode” directly from the Site security settings page of xCloud dashboard.
### **🆕 [Git Integration for Docker Compose Sites](/docs/how-to-deploy-custom-docker-application-from-git-repository/)**
You can now deploy custom Docker Compose projects directly from a Git repository on xCloud. Connect your public, private, or linked Git provider, auto-detect ports from your docker-compose.yml, map services to domains, and go live – all from the xCloud dashboard.
## **🐛 Improvements & Bug Fixes**
📌Fixed Codex authentication flow issue
📌Fixed UI related issues across multiple pages
📌Fixed an issue related to the blank server monitoring page
📌Fixed MySQL installation version issue on Ubuntu 24.04
📌Fixed Docker site deletion getting stuck when a Redis file is missing
📌Fixed package upgrades showing as failed after a reboot
📌Fixed Fail2Ban timeout issue
📌Fixed staging option showing for unsupported WordPress multisite
📌Fixed empty site title issue in Bulk Nginx Customization
---
# v2.5.4 - xCloud
> - Resellers can offer fully managed OpenClaw, Hermes & Paperclip hosting to their own customers.- Customers get AI agent hosting powered by xCloud, while
## 🔥 New Features
### [OpenClaw & Hermes Reseller Panel](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
– Resellers can offer fully managed OpenClaw, Hermes & Paperclip hosting to their own customers.
– Customers get AI agent hosting powered by xCloud, while resellers manage sales and customer access from one place.
– This makes it easier for agencies, hosting providers, and AI service businesses to launch their own AI hosting services without building the infrastructure themselves.
## **✨** Improvements
1. xCloud Free Vulnerability Checker is now up-to-date with the latest Wordfence workflow
2. New clients get a more user-friendly approach to set up their already paid servers during the signup and onboarding process.
3. Server and Site now show the correct MySQL or MariaDB version.
4. Improved the domain update process so the dashboard shows more accurate status updates during domain changes.
5. Improved server provider credential validation with clearer error messages when credentials are incorrect.
6. Improved the WordPress vulnerability scan page with a cleaner layout, better action buttons, and clearer security status.
7. Improved OpenLiteSpeed Rescue Site handling so custom PHP worker settings are preserved.
8. Improved Google Drive restore handling so remote site backup restore errors are shown more clearly instead of failing silently.
9. During ticket creation users can now also see helpful related documentation in real time.
##
🐛 Bug Fixes
1. Fixed an issue where Cloudflare actions could fail if an older Cloudflare integration had an invalid API token.
2. Fixed WP-CLI warnings appearing on WordPress multisite environments.
3. Fixed an issue where whitelabel brand logos and landing page navbar logos could overwrite each other.
4. Fixed incorrect failure titles on site delete, clone, and migration progress pages.
5. Fixed reserved xCloud platform domains being allowed during go-live or additional domain setup.
6. Fixed SSL status showing as failed while certificates were still being generated. It now correctly shows as pending.
7. Fixed the cookie banner showing on error pages and overlapping important error messages.
8. Fixed dropdowns closing unexpectedly when interacting with modals.
9. Fixed OpenClaw session file cleanup to prevent large session files from slowing down the chat UI.
---
# v2.5.5 - xCloud
> Dirty Frag mitigation has been applied across all connected xCloud servers, including xCloud-managed and self-managed servers, via the existing security patch
## Security Release – 🔒 Dirty Frag Linux Kernel Vulnerability Mitigation Applied
Dirty Frag mitigation has been applied across all connected xCloud servers, including xCloud-managed and self-managed servers, via the existing security patch system. The vulnerable kernel modules are safely disabled and unloaded where applicable. Nothing needs to be done from your end, and there is no downtime or reboot requirement.
---
# v0.1.0 - xCloud
> Alpha Launch
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
June 1, 2023
[Back To Changelog](/changelog/)
# v0.1.0
- No categories
### Alpha Launch
---
# v0.2.0 - xCloud
> Beta Launch
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
October 15, 2023
[Back To Changelog](/changelog/)
# v0.2.0
- No categories
### Beta Launch
---
# v1.0.0 - xCloud
> Initial Launch
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
January 31, 2024
[Back To Changelog](/changelog/)
# v1.0.0
- No categories
### Initial Launch
---
# v1.1.0 - xCloud
> New Features Custom Invoice Generator under User Profile Server Timezone update Improvements and Updates Allowed non-22 ports in SSH Added more errors
### New Features
- [Custom Invoice Generator under User Profile](/docs/how-to-generate-custom-invoices/)
- [Server Timezone update](/docs/adjusting-time-zone-settings-in-xcloud-servers/)
### Improvements and Updates
- Allowed non-22 ports in SSH
- Added more errors messages and logs for VULTR API Key integration for users.
- Added Team delete in action menu
### Issues and Bug Fixes
- Backup date and time in server timezone issue is fixed
- Monitoring storage issues fixed
---
# v1.1.1 - xCloud
> Improvements and Updates WP Super Cache related optimization xCloud Migration Plugin related optimizations FastCGI NGINX caching permission improvements
### Improvements and Updates
- WP Super Cache related optimization
- xCloud Migration Plugin related optimizations
- FastCGI NGINX caching permission improvements
- Cloudflare integration auto check turned off on go live domain
- S3 bucket storage integration optimization
- Cloudflare DNS and Origin Certificate updates on Domain Change
### Issues and Bug Fixes
- Auto healing issue fixed
- Database creation issue fixed
- Notification failed issue fixed
- Billing related issues
---
# v1.1.2 - xCloud
> Improvements & Updates Cloudflare SSL generation and UI updates Updates for xCloud managed Email GCP Firewall updates on server creation Cron, site
### Improvements & Updates
- Cloudflare SSL generation and UI updates
- Updates for xCloud managed Email
- GCP Firewall updates on server creation
- Cron, site monitoring and backup updates
### Issues and Bug Fixes
- NGINX cache path update issue on wp-config.php fixed
- Domain update bug fixes(cron, monitoring)
- All events pagination issue fixes
- Server status checker issue fixed
---
# v1.1.3 - xCloud
> Improvements & Updates Improved Database Security for MySQL root user Optimize MySQL max_connections based on RAM during initial setup Ubuntu Version
### Improvements & Updates
- Improved Database Security for MySQL root user
- Optimize MySQL max\_connections based on RAM during initial setup
- Ubuntu Version Compatibility Check before connecting to another provider
- Cronjob related updates
- Install Cloudflare SSL Certificate from app
- Cloudflare Proxy auto enabling while SSL generation on Cloudflare
- WP Cli command related updates
- Cache clear on Theme Activation from xCloud
- FPM sock permission improved
- Added unique WP\_REDIS\_PREFIX on redis object cache installation
- During search-replace, run \`wp config shuffle-salts\` to prevent cache key collisions.
### Issues and Bug Fixes
- GCP Firewall Issue fix
- Billing issue fixes related to xCloud Managed Emails
---
# v1.1.4 - xCloud
> New Features WP Debug ON/OFF from site settings Site Backup download option for remote backups Magic Login Disable Feature PHP 8.3 Improvements & Updates
### New Features
- [WP Debug ON/OFF from site settings](/docs/enable-wp-debug-tool-from-xcloud-dashboard/)
- [Site Backup download option for remote backups](/docs/site-backups-in-xcloud/)
- [Magic Login Disable Feature](/docs/magic-login-in-xcloud/)
- [PHP 8.3](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
### Improvements & Updates
- Automatic site backup delete updates
### Issues and Bug Fixes
- Theme version compare bug fix
- Team switching cache issue bug fix
- Fixed Installation Script for Ubuntu 22.04 for Hostinger VPS
---
# v1.1.5 - xCloud
> New Features xCloud Provider – For LTD users Issues and Bug Fixes Automatic Backup related fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
February 25, 2024
[Back To Changelog](/changelog/)
# v1.1.5
- No categories
### New Features
- [xCloud Provider – For LTD users](/docs/xcloud-provider-for-ltd-users/)
### Issues and Bug Fixes
- Automatic Backup related fixes
---
# v1.1.6 - xCloud
> New Features File Manager Customize Max Input Vars value under Server PHP settings Issues and Bug Fixes Invoice related updates
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
February 26, 2024
[Back To Changelog](/changelog/)
# v1.1.6
- No categories
### New Features
- [File Manager](/docs/access-wordpress-files-in-xcloud/)
- Customize Max Input Vars value under Server PHP settings
### Issues and Bug Fixes
- Invoice related updates
---
# v1.1.7 - xCloud
> New Features 7G Firewall Improvements & Updates Cloudflare Integration limit increased Issues and Bug Fixes Database password validation update GCP UI
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
February 29, 2024
[Back To Changelog](/changelog/)
# v1.1.7
- No categories
### New Features
- [7G Firewall](/docs/use-xcloud-7g-firewall-on-nginx/)
### Improvements & Updates
- [Cloudflare Integration limit increased](/docs/using-xcloud-with-cloudflare-for-dns-management/)
### Issues and Bug Fixes
- Database password validation update
- GCP UI issue fix
---
# v1.1.8 - xCloud
> New Features Custom Cronjob Improvements & Updates Support Ticket Portal for users Staging Domain to Live Domain improvements Sync DNS Records with
### New Features
- [Custom Cronjob](https://xcloud.host/docs/how-to-add-a-custom-cron-job-in-xcloud/)
### Improvements & Updates
- [Support Ticket Portal for users](https://support.xcloud.host/)
- Staging Domain to Live Domain improvements
- Sync DNS Records with Cloudflare integrations
### Issues and Bug Fixes
- Search and Replace bug fixes with Site Cloning
- Invoice related updates
---
# v1.1.9 - xCloud
> New Feature WordPress Multisite
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
March 7, 2024
[Back To Changelog](/changelog/)
# v1.1.9
- No categories
### New Feature
- [WordPress Multisite](/docs/how-to-install-wordpress-multisite-with-xcloud/)
---
# v1.2.0 - xCloud
> New Features Customize PHP Settings for Your Sites Improvements & Updates Full Server Migration updates and fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
March 10, 2024
[Back To Changelog](/changelog/)
# v1.2.0
- No categories
### New Features
- [Customize PHP Settings for Your Sites](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
### Improvements & Updates
- Full Server Migration updates and fixes
---
# v1.2.1 - xCloud
> New Features Hetzner Provider
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
March 12, 2024
[Back To Changelog](/changelog/)
# v1.2.1
- No categories
### New Features
- [Hetzner Provider](/docs/set-up-hetzner-server-in-xcloud/)
---
# v1.2.2 - xCloud
> New Feature Slack integration for notification
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
March 14, 2024
[Back To Changelog](/changelog/)
# v1.2.2
- No categories
### New Feature
- [Slack integration for notification](/docs/configure-slack-integration-in-xcloud/)
---
# v1.2.3 - xCloud
> New Features Firewall Management Improvements & Updates Cloudflare DNS records removal now optional on site/server deletion. Issues and Bug Fixes Fixed
### New Features
- [Firewall Management](/docs/how-to-configure-firewall-management-in-xcloud/)
### Improvements & Updates
- Cloudflare DNS records removal now optional on site/server deletion.
### Issues and Bug Fixes
- Fixed NGINX protocol options redefined warnings
- PHP settings fixes for Site Settings
---
# v1.2.4 - xCloud
> New Features Fail2ban Management Improvements & Updates More PHP Settings Options. Issues and Bug Fixes Server & site delete notification issue fix
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
March 21, 2024
[Back To Changelog](/changelog/)
# v1.2.4
- No categories
### New Features
- [Fail2ban Management](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
### Improvements & Updates
- [More PHP Settings Options.](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
### Issues and Bug Fixes
- Server & site delete notification issue fix with Slack.
---
# v1.2.5 - xCloud
> New Features Custom NGINX Configuration Built in plugin support on Custom Nginx Config. (Hide My WP and Rank Math SEO are added) Improvements & Updates
### New Features
- [Custom NGINX Configuration](/docs/configure-custom-nginx-xcloud/)
- [Built in plugin support on Custom Nginx Config. (Hide My WP and Rank Math SEO are added)](/docs/configure-custom-nginx-xcloud/)
### Improvements & Updates
- Support for shorter domains in Cloudflare integrations
### Issues and Bug Fixes
- Multisite path issue on NGINX
- Site Delete issue fixed with duplicate domain names
---
# v1.2.6 - xCloud
> New Feature Blueprints
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
April 1, 2024
[Back To Changelog](/changelog/)
# v1.2.6
- No categories
### New Feature
- [Blueprints](/docs/how-to-use-blueprints-in-xcloud/)
---
# v1.3.0 - xCloud
> New Feature OpenLiteSpeed Web Server 8G Firewall for OLS servers
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
April 8, 2024
[Back To Changelog](/changelog/)
# v1.3.0
- No categories
### New Feature
- [OpenLiteSpeed Web Server](/introducing-openlitespeed-server-in-xcloud/)
- [8G Firewall for OLS servers](/introducing-openlitespeed-server-in-xcloud/)
---
# v1.3.1 - xCloud
> Improvements & Updates Imagick extension added for OLS Security Improvement for the default FPM sock Issues and Bug Fixes WP-Cron related bug fixing
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
April 9, 2024
[Back To Changelog](/changelog/)
# v1.3.1
- No categories
### Improvements & Updates
- Imagick extension added for OLS
- Security Improvement for the default FPM sock
### Issues and Bug Fixes
- WP-Cron related bug fixing
---
# v1.3.10 - xCloud
> New UI Update Menu Settings Search added New Features Reset File & Folder Permissions With Rescue Site Feature Full Server Backup Schedule Improvements
### New UI Update
- Menu Settings Search added
### New Features
- [Reset File & Folder Permissions With Rescue Site Feature](/docs/reset-file-and-folder-permissions-with-xcloud/)
- [Full Server Backup Schedule](/docs/configure-server-backup-management/)
### Improvements and Updates
- Automatically restart LiteSpeed Server on .htaccess update – using cronjob
- Prevent multiple API call for Email verification.
---
# v1.3.2 - xCloud
> Improvements & Updates Dynamic ssh port on default firewall creation Deny ini, log, conf file on OLS Issues and Bug Fixes PHP default upload limit &
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
April 10, 2024
[Back To Changelog](/changelog/)
# v1.3.2
- No categories
### Improvements & Updates
- Dynamic ssh port on default firewall creation
- Deny ini, log, conf file on OLS
### Issues and Bug Fixes
- PHP default upload limit & timeout adjustment
---
# v1.3.3 - xCloud
> New Features Site Disable Feature to suspend a site temporarily Disable sending credentials to users email Improvements & Updates Backup settings update
### New Features
- [Site Disable Feature to suspend a site temporarily](/docs/disable-site-in-xcloud-hosting/)
- [Disable sending credentials to users email](/docs/how-to-disable-email-notifications/)
### Improvements & Updates
- Backup settings update
- UI – Added Server Filter On Site List Dashboard page
- UI – Added version on App’s footer
### Issues and Bug Fixes
- Team Invitation Expire issue fixed
---
# v1.3.4 - xCloud
> New Features Migrate Sites From cPanel To Managed Hosting At xCloud Improvements & Updates Plugin Update feature related improvements Issues and Bug Fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
April 22, 2024
[Back To Changelog](/changelog/)
# v1.3.4
- No categories
### New Features
- [Migrate Sites From cPanel To Managed Hosting At xCloud](/docs/migrate-sites-from-cpanel-to-xcloud/)
### Improvements & Updates
- Plugin Update feature related improvements
### Issues and Bug Fixes
- Site Clone feature related bug fixes
---
# v1.3.5 - xCloud
> New Features Migrate Sites From cPanel To Managed Hosting At xCloud Improvements & Updates Plugin Update feature related improvements Issues and Bug Fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
April 30, 2024
[Back To Changelog](/changelog/)
# v1.3.5
- No categories
### New Features
- [Migrate Sites From cPanel To Managed Hosting At xCloud](/docs/migrate-sites-from-cpanel-to-xcloud/)
### Improvements & Updates
- Plugin Update feature related improvements
### Issues and Bug Fixes
- Site Clone feature related bug fixes
---
# v1.3.6 - xCloud
> New Features Multisite with Subdomain Support Wildcard SSL support
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
May 2, 2024
[Back To Changelog](/changelog/)
# v1.3.6
- No categories
### New Features
- [Multisite with Subdomain Support](/docs/wordpress-multisite-with-subdomain/)
- Wildcard SSL support
---
# v1.3.7 - xCloud
> New Features Server Resize Feature – xCloud & Vultr servers Full Server Backup Management – xCloud & Vultr servers By default xCloud servers will be
### New Features
- [Server Resize Feature – xCloud & Vultr servers](/docs/how-to-upgrade-your-server-in-xcloud/)
- [Full Server Backup Management – xCloud & Vultr servers](/docs/configure-server-backup-management/)
- By default xCloud servers will be created with Ubuntu 22.04 LTS
### Improvements and Updates
- SSH related security updates
- Cloudflare domain checker update to handle multi-level domains
---
# v1.3.8.1 - xCloud
> Issues and Bug Fixes Billing related bug fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
May 14, 2024
[Back To Changelog](/changelog/)
# v1.3.8.1
- No categories
### Issues and Bug Fixes
- Billing related bug fixes
---
# v1.3.8.2 - xCloud
> Issues and Bug Fixes Billing related bug fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
May 15, 2024
[Back To Changelog](/changelog/)
# v1.3.8.2
- No categories
### Issues and Bug Fixes
- Billing related bug fixes
---
# v1.3.8.3 - xCloud
> Issues and Bug Fixes Full Server Migration Related Bug Fixes
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
May 20, 2024
[Back To Changelog](/changelog/)
# v1.3.8.3
- No categories
### Issues and Bug Fixes
- Full Server Migration Related Bug Fixes
---
# v1.3.8 - xCloud
> Improvements and Updates User can remove attached email provider from site Auto heal apt-get update on various actions Issues and Bug Fixes Multisite sub
### Improvements and Updates
- User can remove attached email provider from site
- Auto heal apt-get update on various actions
### Issues and Bug Fixes
- Multisite sub directory related bug fixes
- Server Monitoring issue fixed after Server Resizing
---
# v1.3.9 - xCloud
> New Features New Storage Provider Integration – Cloudflare R2 Full Server Migration is available for OLS server Improvements and Updates Redis user and prefix
### New Features
- [New Storage Provider Integration – Cloudflare R2](/changelog/)
- [Full Server Migration is available for OLS server](/docs/perform-a-full-server-migration-with-xcloud/)
### Improvements and Updates
- Redis user and prefix isolation with ACLs to enhance site security.
- PHP settings update related fixes
---
# v1.4.0 - xCloud
> New Features Incremental Site Backup PHP Worker count adjustment from Site’s PHP settings Improvements & Updates Automatic Log Cleaning to reduce server
### New Features
- [Incremental Site Backup](/docs/incremental-backup-in-xcloud/)
- PHP Worker count adjustment from Site’s PHP settings
### Improvements & Updates
- Automatic Log Cleaning to reduce server storage
- UI updates – Help Texts and Auto Focus on Form fields
### Issues and Bug Fixes
- Notifications on/off issue fix for email & slack.
---
# v1.4.1 - xCloud
> New Features “No Database Site” clone option Improvements & Updates Validation added on incremental backup. At least 1 full backup is required before
### New Features
- “No Database Site” clone option
### Improvements & Updates
- Validation added on incremental backup. At least 1 full backup is required before initiating an incremental backup.
- Cleanup script execute on random time.
- UI updates – Tutorial Videos added on Help Text Section
### Issues and Bug Fixes
- Redis object cache Issue fixed for OLS sites.
- Local Backup file delete option related fixes.
---
# v1.4.10 - xCloud
> Security Update Vulnerability Fix: LiteSpeed Cache Plugin Upgraded to Version 6.5.0.2 on Client Sites Improvements & Updates PHP FPM worker count
### Security Update
- Vulnerability Fix: LiteSpeed Cache Plugin Upgraded to Version 6.5.0.2 on Client Sites
### Improvements & Updates
- PHP FPM worker count adjustment based on RAM/CPU
- Backup – Timezone related fixes, Incremental File Size monitoring fixes
### Issues & Bug Fixes
- Playground feature bugs fixed
- Fixed auto backup issues with bulk vulnerability scanner setting.
---
# v1.4.11 - xCloud
> Improvements & Updates xCloud Migration Plugin v0.4.7 released Ensured compatibility with MariaDB and Ubuntu 20.04 for better performance and stability.
### Improvements & Updates
- [xCloud Migration Plugin v0.4.7 released](https://xcloud-storage.s3.ap-southeast-1.amazonaws.com/wp-xcloud-migration/wp-xcloud-migration-latest.zip)
- Ensured compatibility with MariaDB and Ubuntu 20.04 for better performance and stability.
- On Server Database list specific site site name and direct access to adminer to manage database is now added.
- Introduced PHP Rescue option and server default version selection for easier configuration.
- Automatically change directory into the site folder upon sFTP/SSH login using Site User to improve user experience.
### Issues & Bug Fixes
- Patched the issue with cPanel site fetching to improve reliability.
- Fail2ban related fixes
---
# v1.4.2 - xCloud
> Improvements & Updates Central cronjob for taking site backups more efficiently to avoid high CPU usage Enhancement with NGINX xframe nullable issue
### Improvements & Updates
- Central cronjob for taking site backups more efficiently to avoid high CPU usage
- Enhancement with NGINX xframe nullable issue
- Automatically fix PHP version during site installation if found broken
### Issues and Bug Fixes
- Server disconnect email, server disk storage, and RAM low warning display issue fix
- SSL manager exception handling
- Migration Plugin Update – Fix issue if mysqldump fails
- Retry with other Cloudflare integrations if fails to create SSL certificate
---
# v1.4.3.1 - xCloud
> Improvements & Updates WhatsApp Disconnect notification added. UI update – Integrations Issues & Bug Fixes Slack notification issue fixed for Invoice
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
July 8, 2024
[Back To Changelog](/changelog/)
# v1.4.3.1
- No categories
### Improvements & Updates
- WhatsApp Disconnect notification added.
- UI update – Integrations
### Issues & Bug Fixes
- Slack notification issue fixed for Invoice
---
# v1.4.3 - xCloud
> New Features WhatsApp Integration Improvements & Updates Users can add more emails from Profile page to get billing related updates. Header Menu Design
### New Features
- [WhatsApp Integration](/docs/how-to-configure-integration-with-whatsapp/)
### Improvements & Updates
- Users can add more emails from Profile page to get billing related updates.
- Header Menu Design Update
- Confirmation Modal added before purchase
- FSM related improvements
---
# v1.4.4 - xCloud
> Security Update Ubuntu Security Update: OpenSSH Vulnerability (CVE-2024-6387)
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
July 9, 2024
[Back To Changelog](/changelog/)
# v1.4.4
- No categories
### Security Update
- Ubuntu Security Update: OpenSSH Vulnerability (CVE-2024-6387)
---
# v1.4.5.1 - xCloud
> Improvements & Updates SSL access enabled for IP sites to support custom SSL Cloudflare error response handling improvements Issues & Bug Fixes File
### Improvements & Updates
- SSL access enabled for IP sites to support custom SSL
- Cloudflare error response handling improvements
### Issues & Bug Fixes
- File manager chmod bug fixed
- Fixed wrong storage info display issue
- Backup date-time format fixed
---
# v1.4.5.2 - xCloud
> Improvements & Updates Cloudflare R2 region fix applied Backup: Not enough space warning message updated. Go Live redirection issue fixed to prevent
### Improvements & Updates
- Cloudflare R2 region fix applied
- Backup: Not enough space warning message updated.
- Go Live redirection issue fixed to prevent staging SSL from remaining active
### Issues & Bug Fixes
- Removed DNS records from Cloudflare for demo sites when deleting a server
- Full Server Migration site fetch issues resolved
- Redis configuration issue solved in site cloning feature
---
# v1.4.5.3 - xCloud
> Improvements & Updates Site overview URL patch implemented Fixed “Go Live” redirection for sites with demo or staging environments Go Live redirection
### Improvements & Updates
- Site overview URL patch implemented
- Fixed “Go Live” redirection for sites with demo or staging environments
- Go Live redirection issue fixed to prevent staging SSL from remaining active
### Issues & Bug Fixes
- Fixed issue with Cloudflare DNS record removal upon server deletion
- Full Server Migration site fetch issues resolved
- Improved handling of Cloudflare error responses
---
# v1.4.5 - xCloud
> New Feature Staging Environment With Pull/Push Feature with Production Site Customize xCloud Test Domain on Demo and Staging Sites Improvements New Filter
### New Feature
- [Staging Environment With Pull/Push Feature with Production Site](/docs/how-to-create-a-staging-environment-in-xcloud/)
- Customize xCloud Test Domain on Demo and Staging Sites
### Improvements
- New Filter Added to sort sites by Production, Staging and Demo Sites
- Validation added for creating site with IP Address.
- Billing related improvements
---
# v1.4.6 - xCloud
> New Feature AWS Integration: Built in support for both EC2 and Lightsail ARM Server Support – xCloud now supports Hetzner ARM servers & adding ARM servers
### New Feature
- [AWS Integration: Built in support for both EC2 and Lightsail](/docs/how-to-set-up-aws-server-in-xcloud/)
- [ARM Server Support – xCloud now supports Hetzner ARM servers & adding ARM servers via Any Provider](/docs/how-to-setup-arm-server-in-xcloud/)
- Users can now connect servers with Ubuntu 24.04 via the Any Provider feature
- PHP 8.3 support on OLS servers
### Improvements & Updates
- Users can switch between xCloud SSL and Cloudflare SSL with ease now
- NGINX HTTP/2 deprecation warning fixed
- Fixed grep PHP working count with default value
### Issues & Bug Fixes
- Pagination filter issue fixed on the site list page
- Server Monitoring Bug Fixes
---
# v1.4.7 - xCloud
> Security Update Vulnerability Fix: LiteSpeed Cache Plugin Upgraded to Version 6.4.1 on Client Sites Improvements & Updates Enhancements to Our Internal
### Security Update
- [Vulnerability Fix: LiteSpeed Cache Plugin Upgraded to Version 6.4.1 on Client Sites](https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/litespeed-cache/litespeed-cache-6301-unauthenticated-privilege-escalation)
### Improvements & Updates
- Enhancements to Our Internal Server Monitoring Systems to Handle High Loads
- Server And Site List Fetching Query Optimization
---
# v1.4.8 - xCloud
> New Feature Vulnerability Scanner For WordPress Server-Side Vulnerability Scanner Setup Automated Vulnerability Updates Immediate Vulnerability Notifications
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
August 25, 2024
[Back To Changelog](/changelog/)
# v1.4.8
- No categories
### New Feature
- [Vulnerability Scanner For WordPress](/docs/vulnerability-checker-in-xcloud/)
- Server-Side Vulnerability Scanner Setup
- Automated Vulnerability Updates
- Immediate Vulnerability Notifications
---
# v1.4.9 - xCloud
> New Feature New Database Server – MariaDB Improvements & Updates Site Disable feature added under action menu. “Vulnerable” filter added on Site List
### New Feature
- [New Database Server – MariaDB](/docs/install-mariadb-with-xcloud/)
### Improvements & Updates
- Site Disable feature added under action menu.
- “Vulnerable” filter added on Site List page.
- Help Text Updated for Sudo user.
### Issues & Bug Fixes
- Payment issue fixed with 3D secure cards.
- Fixed auto backup issues with bulk vulnerability scanner setting.
---
# v1.5.0 - xCloud
> New Features Automatic Server Security & Updates Command Runner Improvements & Updates Sync PHP Settings during Site Clone Update Server Provider
### New Features
- [Automatic Server Security & Updates](/docs/reboot-server-with-automated-security-updates/)
- [Command Runner](/docs/how-to-run-commands-in-your-site-and-server/)
### Improvements & Updates
- Sync PHP Settings during Site Clone
- Update Server Provider Integrations
- User Cannot Create Production Site with xCloud Demo Sites Domain
- User’s Customised Filters Stored for Dashboard, Site & Server List
- REDIS config update
- New Invoice Design
### Issues & Bug Fixes
- Fail2ban fetch ip error handling
- Pagination Issue Fix for Server, Invoices, Bills & Emails Subscription List Page
- Server Provider Logo Issue Fix on Site List, Install Page & Search Bar
- Custom Command Permission Issue and Table Issue Fix
- Top-bar search UI issue fixed
---
# v1.5.1 - xCloud
> New Feature Added OpenLiteSpeed compatibility for Ubuntu 24.04 with Any Provider option Improvements & Updates Users can find Redis Credentials from Site
### New Feature
- Added OpenLiteSpeed compatibility for Ubuntu 24.04 with Any Provider option
### Improvements & Updates
- [Users can find Redis Credentials from Site Dashboard](/docs/how-to-find-the-redis-credentials/)
- Improved cleanup script to all servers
- Updated server monitoring to the latest version
- Minor patch into all OLS servers to fix the warning on openlitespeed -t command
- Added dynamic encryption type assignment based on port for Fluent SMTP.
- Added support for custom rsync SSH ports during site cloning.
- Optimized directory permissions update process.
### Issues & Bug Fixes
- Fixed issue with capitalized domain names causing 302 redirects.
---
# v1.5.2 - xCloud
> Improvements & Updates “Restricted `/var/www` access: site users can navigate to their own site directories (e.g., `/var/www/site.com`) but see
### Improvements & Updates
- “Restricted \`/var/www\` access: site users can navigate to their own site directories (e.g., \`/var/www/site.com\`) but see \`Permission denied\` if listing \`/var/www\`. Full access remains to their home files (\`~/files\`).”
- Cloudflare R2 storage now has incremental site backup support
- The security headers (X-Frame-Options, X-XSS-Protection, X-Content-Type-Options) are now compatible with NGINX FastCGI cached responses.
### Issues & Bug Fixes
- Updated site backup script
---
# v1.6.0 - xCloud
> New Feature – White Label Released Seamless Reseller onboarding Fully custom branding for Client Dashboard Custom Domain Setup For Reseller Dashboard Custom
### [New Feature – White Label Released](https://xcloud.host/xcloud-white-label/)
- [Seamless Reseller onboarding](/docs/setup-reseller-account-with-xcloud-white-label/)
- [Fully custom branding for Client Dashboard](/docs/setup-reseller-account-with-xcloud-white-label/)
- Custom Domain Setup For Reseller Dashboard
- Custom SMTP Setup
- [Customize and Sell xCloud Managed Server at your own price](/docs/create-a-new-product-in-xcloud-white-label/)
- Automated Server Setup
- [Automated Client Billing with Stripe Connect](/docs/setup-reseller-account-with-xcloud-white-label/)
- Reseller Dashboard
- Client Management
- Reseller Can Manage Client Server & Sites
- [Resellers can set up custom landing pages, terms of service, and more using our provided templates.](/docs/customize-reseller-landing-page-in-xcloud/)
- [3D secure card support for Reseller’s clients](/docs/collect-stripe-publishable-key/)
### Improvements & Updates
- Update searchReplaceUrl script to handle only HTTP/HTTPS URLs and skip direct domain names.
- Domain update issue fix for OLS cache.
### Issues & Bug Fixes
- Redis object cache key issue on domain update.
---
# v1.6.1 - xCloud
> New Feature PHP 8.4 support for NGINX servers White Label – New Feature Reseller can add favicon separately Improvements & Updates Resellers clients will
### New Feature
- [PHP 8.4 support for NGINX servers](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
### White Label – New Feature
- [Reseller can add favicon separately](/docs/setup-reseller-account-with-xcloud-white-label/)
### Improvements & Updates
- Resellers clients will not see xCloud label on browser tabs
- White Label product duplicate & display buying, selling price
- Improved help texts on server site creation added docs link on help text
### Issues & Bug Fixes
- Implemented validation to prevent new domain from containing previous domain as a substring
- Issue fixed with server delete option with self managed providers
---
# v1.6.2 - xCloud
> New Feature Telegram Integration for Notification Whitelist or Blacklist any IP Address for Your Website Improvements & Updates xCloud Full Server
### New Feature
- [Telegram Integration for Notification](/docs/configure-integration-with-telegram-in-xcloud/)
- [Whitelist or Blacklist any IP Address for Your Website](/docs/configure-integration-with-telegram-in-xcloud/)
### Improvements & Updates
- [xCloud Full Server Migration now has support for RunCloud OLS servers](/docs/perform-a-full-server-migration-with-xcloud/)
- Payment and Billing related updates
### Issues & Bug Fixes
- Client’s of resellers will not see xCloud favicon on 404 pages
---
# v1.6.3.1 - xCloud
> Improvements & Updates If a full backup isn’t available, incremental backups will now be created TOS and Privacy Policy Links are available on WhiteLabel
### Improvements & Updates
- If a full backup isn’t available, incremental backups will now be created
- TOS and Privacy Policy Links are available on WhiteLabel Signup Page
- Cloudflare R2 endpoints updated for seamless restore functionality
### Issues & Bug Fixes
- Automatic indexing is now handled during site cloning.
- Indexing for staging sites is disabled to avoid SEO conflicts.
- Issue fixed where access tokens weren’t refreshing before deletion processes.
- Enhanced domain validation during playground site creation.
- Resolved issues related to product mismatches in configurations.
- Added and improved checks for server cloning operations.
- Addressed and resolved authorization check issues in site cloning workflows.
---
# v1.6.3 - xCloud
> New Feature Linode/Akamai Cloud Provider Integration Full Server Cloning Improvements & Updates Staging Pull Push Support for mariadb –single-transaction
### New Feature
- [Linode/Akamai Cloud Provider Integration](/docs/integrate-and-setup-linode-server-with-xcloud/)
- [Full Server Cloning](/docs/how-to-clone-full-server-with-xcloud/)
### Improvements & Updates
- Staging Pull Push Support for mariadb –single-transaction while dumping database.
- Billing – Specify connected account while verifying card.
### Issues & Bug Fixes
- xCloud SMTP Email Fixes: Resolved API limit overflow issues and enhanced subaccount handling.
- Telegram fixes: Enhanced integration report display.
- User can not use dot(.) in staging/demo site domain name.
- Billing related fixes
---
# v1.6.4 - xCloud
> New Feature Recreate Site using Local and Remote Backups New Storage Provider Integration Backblaze B2 Added feature to disable The Search Engine Visibility
### New Feature
- [Recreate Site using Local and Remote Backups](/docs/recreate-wordpress-website-from-backups/)
- [New Storage Provider Integration Backblaze B2](https://xcloud.host/docs/integrate-blackblaze-storage-provider/)
- [Added feature to disable The Search Engine Visibility Feature](/docs/search-engine-visibility-in-xcloud/)
### Improvements
- Backups are now faster and more efficient with the optimized MySQL dump commands.
- Indexing Control for Demo Sites
- Domain Name Validation: Added a bash script to check for empty domain names during site creation, updates, migration, and cloning processes.
- Custom Robots.txt Support: Users can now provide and use their own robots.txt file with NGINX configurations.
- Fixed PHP path issue in OpenLiteSpeed default configuration.
---
# v1.6.5 - xCloud
> New Feature Google Drive Backup: Users can now back up their sites to Google Drive. Multilingual in Dashboard – We’ve added full translation support, allowing
### New Feature
- [Google Drive Backup: Users can now back up their sites to Google Drive.](/docs/google-drive-for-site-backup-xcloud/)
- [Multilingual in Dashboard – We’ve added full translation support, allowing users to set their preferred language. Team-based notifications are also now customizable for better workflow management.](/docs/change-the-language-for-xcloud-hosting-panel/)
### Improvements
- Auto-Healing PHP Installation: PHP installation is now auto-healed based on monitoring feedback.
- OpenLiteSpeed now enforces a 301 redirect from HTTP to HTTPS for improved security and SEO, aligning with Nginx behavior.
- Imagick Removal for Ubuntu 24 OLS ARM: Removed Imagick from the OpenLiteSpeed ARM build on Ubuntu 24, as it’s not available yet.
### Issues & Bug Fixes
- Duplicate request\_terminate\_timeout Configuration: Resolved an issue where request\_terminate\_timeout was configured twice in .conf files.
- Redis APT Repository Deprecation: Addressed the deprecation of ppa:redislabs/redis by switching to the official Redis APT repository.
- Notification issue fixed related to team
---
# v1.6.6 - xCloud
> New Feature Multiple Domain options are now available for Demo site and Staging site features. Improvements Issue fixed with Playground Feature Two new xCloud
### New Feature
- Multiple Domain options are now available for Demo site and Staging site features.
### Improvements
- Issue fixed with Playground Feature
- Two new xCloud Managed Email bundles are added.
- Access key IDs are now displayed with limited characters for improved readability and security.
- Reordered language and country listings alphabetically for a more user-friendly experience.
---
# v1.6.7 - xCloud
> New Feature Object Cache Pro Integration – Users can now integrate Object Cache Pro for improved caching performance. Google Cloud Storage Integration – Added
### New Feature
- [**Object Cache Pro Integration** – Users can now integrate Object Cache Pro for improved caching performance.](/docs/integrate-object-cache-pro-with-xcloud/)
- [**Google Cloud Storage Integration** – Added support for backing up sites to Google Cloud Storage.](/docs/integrate-google-cloud-storage-xcloud/)
- [**Show All System Cron Jobs** – Users can now view all system cron jobs for better server management.](/docs/check-cron-job-list-of-all-sites-in-your-server/)
### Improvements
- **Front-End Fix** – Resolved issues where model contents were overflowing.
- **Bills Related Updates** – Improved stability for bill generation and old purchase updates.
- **Help Text Update** – Updated the name and help text URL for server backup on/off settings.
### Issues & Bug Fixes
- **Magic Login Issue Fixed** – Resolved issues affecting magic login functionality.
- **Same Domain Multiple Site Creation Issue** – Fixed a bug preventing multiple sites from being created under the same domain.
- **Team Notification Permission Fixes** – Addressed issues with team-based notification permissions.
- **Inactive Product Display Fix** – Disabled inactive product display in the checkout page for white label users.
---
# v1.6.8 - xCloud
> New Feature AI Bot Blocker – Added an AI Bot Blocker to Nginx and OpenLiteSpeed security options to prevent unwanted automated traffic. Global Settings to
### New Feature
- **[AI Bot Blocker](/docs/enable-ai-bot-blocker-in-xcloud/)** – Added an AI Bot Blocker to Nginx and OpenLiteSpeed security options to prevent unwanted automated traffic.
- **[Global Settings to auto disable File Manager and Adminer](/docs/global-settings-for-file-manager-and-adminer/)**.
- **Migration Plugin with cancel feature**.
### Improvements
- Object Cache Pro is now more compatible with LiteSpeed Cache, ensuring better performance for your sites.
- Site Deletion Notification Fix: We’ve resolved an issue with site deletion notifications to ensure accurate alerts.
### Issues & Bug Fixes
- Users can now create sites with the same domain on different servers, offering more flexibility in server management.
---
# v1.6.9 - xCloud
> New Feature Brotli Compression – Enjoy improved site performance with Brotli compression support Custom Backup Notes – Users can now add custom notes when
### New Feature
- **[Brotli Compression](/docs/brotli-compression-on-xcloud/)** – Enjoy improved site performance with Brotli compression support
- **[Custom Backup Notes](/docs/site-backups-in-xcloud/)** – Users can now add custom notes when creating site backups for better organization.
### Improvements
- Improved server disconnection notifications with a structured schedule.
- Performance and Security optimization for better application performance.
- Profile team name displaying issue and tooltip alignment issue
- Clear search input when clicking on search results
### Issues & Bug Fixes
- Bulk Site fetching issue with Full Server Migration fixed.
---
# v1.7.0 - xCloud
> New Feature Custom PHP Application – Install and manage any custom PHP application beyond WordPress, e.g CodeCanyon or any custom PHP scripts. Magic Login
### New Feature
- [**Custom PHP Application**](/docs/deploy-custom-php-applications-with-xcloud/) – Install and manage any custom PHP application beyond WordPress, e.g CodeCanyon or any custom PHP scripts.
- [**Magic Login Customization**](/docs/how-to-customize-magic-login/) – Customize Magic Login and use your own admin username or email for a more personalized authentication experience.
- [**Better Navigation for Servers and Sites**](https://xcloud.host/docs/navigation-for-your-servers-and-sites-in-xcloud/) – Seamlessly navigate between servers and sites using the new hover navigation feature support.
### Improvements
- Improved UI issue with Command Table is not matching xCloud
### Issues & Bug Fixes
- Fixed caching issue after domain change
- Fixed issue with xCloud Search is not disappearing after clicking the search result
- Fixed issue with provider Logo appears fully white on hover
---
# v1.7.1 - xCloud
> New Feature Staging Management with Custom Domain – Now users can manage their staging sites with their own custom domain! Improvements Added support for
### New Feature
- **[Staging Management with Custom Domain](/docs/how-to-create-a-staging-environment-in-xcloud/)** – Now users can manage their staging sites with their own custom domain!
### Improvements
- Added support for Vulnerability Notification for Slack, WhatsApp & Telegram
- Fixed issues with Magic Login on specific sites.
- Added Community Link in Profile Menu
- Resolved WP installation CLI timeout issue.
- Updated Content for Login & Register Page
- Implemented auto-closing for the mega menu on click.
- Default Sorting Option: Added ability to set default sorting to alphabetical order.
- Site Preview Enhancements: PHP version and server name are now displayed next to site size.
### Issues & Bug Fixes
- White Label Invoice Fetch Issue Fix
---
# v1.7.2 - xCloud
> Improvements Show Visitor Real IP Behind Cloudflare Proxy More test domains are now available for demo/staging sites (wp1.host, 1wp.site) Staging sites with
### Improvements
- [Show Visitor Real IP Behind Cloudflare Proxy](/docs/show-visitor-real-ip-behind-cloudflare-proxy/)
- More test domains are now available for demo/staging sites (wp1.host, 1wp.site)
- Staging sites with custom domain should support multi level domain now.
- Improved SSL renewal reliability and smarter notification scheduling.
### Issues & Bug Fixes
- Fixed a minor issue for getting Ubuntu Version
- Fixed permission issue related to custom php application site creations
- Fixed issue with Laravel icon
- Issue Fixed with adminer info fields
---
# v1.7.3 - xCloud
> New Features WordPress Integrity Checker Improvements Automatically approved playground teams to skip re-verification. “Redirect” is now checked by default
### New Features
- [WordPress Integrity Checker](/docs/verify-wordpress-checksums/)
### Improvements
- Automatically approved playground teams to skip re-verification.
- “Redirect” is now checked by default when adding additional domains for a more seamless setup experience.
- White Label Resellers can check their clients’ transactions from Stripe.
- Prevented duplicate data storage and improved Mega Menu pagination visibility.
### Issues & Bug Fixes
- Fixed issues with invoice list overflow, server delete notice, mobile UI glitches, and xCloud search.
- Resolved exceptions with Grid/List view.
- Resolved issue with OLS server header inconsistencies.
- Fixed White Label billing title formatting issue.
---
# v1.7.4 - xCloud
> New Features WP Fail2Ban with xCloud Improvements Nginx Customization: Support added for custom PHP configurations and custom file name validation (max 30
### New Features
- [WP Fail2Ban with xCloud](/docs/set-up-wp-fail2ban-with-xcloud/)
### Improvements
- **Nginx Customization**: Support added for custom PHP configurations and custom file name validation (max 30 characters).
- **DNS Checker Fix**: Improved accuracy for primary and additional domains.
- SSL Certificate Parsing – Better detection for certificate expiry dates.
- Cloudflare SSL certificate creation endpoint updated
- WordPress Version Support – WordPress 6.8 is now supported with improved version detection.
- Plugin status message improvement
### Issues & Bug Fixes
- Playground bug resolved
- Disk space calculation accuracy improved
- Server and site loading issues fixed
- Free plan downgrade issue addressed
---
# v1.7.5 - xCloud
> New Features Cloudflare Edge Caching with xCloud Improvements Updated version of AWS CLI to version 2 for better compatibility with site backup. Added
### New Features
- [Cloudflare Edge Caching with xCloud](/docs/enable-the-edge-full-page-cache/)
### Improvements
- Updated version of AWS CLI to version 2 for better compatibility with site backup.
- Added system-wide PATH configuration for OpenLiteSpeed CLI tools to enable global access for all users and scripts.
- Refactored validation rules and messages for site user to improve clarity and consistency.
- Removed checksum output for pro plugins to prevent false error reports; checksum issue for pro plugins is now fixed.
- Improved cache control by updating xcloud\_httpd\_config.conf to extend cache duration to 1 year and added new MIME types for optimized performance.
- Implemented new interval-based system for disk space checks to provide timely low disk space warnings.
- Default database and database user with xcloud label will not created anymore.
- Fixed issue where updating SSL incorrectly converted staging sites with custom domains into production sites.
### Issues & Bug Fixes
- Added automatic update of WordPress home URL to HTTPS during installation and upon SSL activation on non-SSL sites.
- Multiselect cursor UI blinking issue fixed
- White label client register issue, Tooltip and other UI issues fixed
---
# v1.7.6.1 - xCloud
> Improvements WhatsApp, Telegram, Slack - Notification support added for Vulnerabilty Shield Pro Integrity Checker detects extra files more smartly and shows
### Improvements
- WhatsApp, Telegram, Slack – Notification support added for Vulnerabilty Shield Pro
- Integrity Checker detects extra files more smartly and shows proper warning status
- Backup restore migration now works smoothly with incremental backups
---
# v1.7.6 - xCloud
> New Features Vulnerability Shield Pro powered by Patchstack for advanced WordPress vulnerability protection. New Storage Provider Integration Hetzner Object
### New Features
- [**Vulnerability Shield Pro** powered by Patchstack for advanced WordPress vulnerability protection.](https://xcloud.host/docs/set-up-vulnerability-shield-pro/)
- [New Storage Provider Integration **Hetzner Object Storage** for Remote Site Backup](/docs/integrate-hetzner-storage-provider/)
- [**Export Feature** – Sites and Servers Data](/docs/export-servers-and-sites-data-with-xcloud/)
### Improvements
- Automatic server provisioning now supports retried payments after initial failures and is fully integrated with the Reseller Program.
- Sort by Z-A & A-Z in server & site list pages.
- Prevent enter & form submit in topbar search both dekstop & mobile version.
- Showing cache status icon in site list.
- Updated Object Cache Pro Debug Mode with improved alignment and refreshed design
---
# v1.7.7 - xCloud
> Improvements Added OPCache settings to enable and disable into the PHP Configuration Rocket-Nginx configuration for WP-Rocket updated to v3.1.0 version.
### Improvements
- [Added OPCache settings to enable and disable into the PHP Configuration](/docs/control-opcache-with-xcloud/)
- [Rocket-Nginx configuration for WP-Rocket updated to v3.1.0 version.](/docs/how-caching-works-in-xcloud/)
- [Filters are added in Vulnerabilty Site List Page to detect PRO and FREE items.](https://app.xcloud.host/user/vulnerable-sites)
- Site Backup issue fixed with bucket import validation to check file types only for bucket imports.
- Suppressed warnings for unchanged files to reduce noise in backup logs
- Improved clarity of site backup script output for better monitoring
- Optimized site backup configuration for better reliability
- Improve message priority logic for success, warning, and error states for integrity monitor feature.
- Add null safety checks for issue filtering for integrity monitor feature.
- Exclude success messages from other issues list for integrity monitor feature.
- Enhance type handling for message computation for integrity monitor feature.
---
# v1.7.8 - xCloud
> New Features Laravel Hosting support in xCloud Powerful Laravel Features:- Queue Management- Scheduler Management- Horizon for Queue Monitoring Supervisor
### New Features
- [Laravel Hosting support in xCloud](/docs/deploy-laravel-applications/)
- Powerful Laravel Features:
– [Queue Management](/docs/set-up-queue-worker-for-laravel-applications/)
– Scheduler Management
– [Horizon for Queue Monitoring](/docs/set-up-laravel-horizon/)
- [Supervisor Process Manager](/docs/supervisor-for-process-management/)
- Redis support for Laravel out of the box
- Site Backup for Laravel – DB Backup support addded
### Improvements
- Server Monitoring page now shows top process for high RAM and CPU usage
- Vulnerabilty Shield Pro related fixings for better notifications
- WP Fail2ban update – Removed Deprecated WP\_FAIL2BAN\_LOG\_COMMENTS\_EXTRA constant from config
- Added white-label domain support in Google Drive callback with improved error handling, OAuth state validation, and refactored code for better readability.
- Added support for large NGINX custom config with a 50,000-character limit to prevent timeout issues.
- Shield pro purchase option given vulnerability page & vulnerable sites page.
- Displaying the actual icons with tooltip according to server state and Switch issue from git clone
### Issues & Bug Fixes
- Replace hardcoded wp command with dynamic path from site configuration (->wp\_cli) for better flexibility and configuration management in integrity checks.
- Translation issue fix for provisioning sites screen
- Refactored SSH key and password update logic to prevent SSH service failures and improve stability, error handling, and configuration validation.
- Issue fix with server resize
- Issue fix with site backup
---
# v1.8.0.1 - xCloud
> New Features BETA access to n8n One Click App
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
May 28, 2025
[Back To Changelog](/changelog/)
# v1.8.0.1
- No categories
### New Features
- BETA access to **n8n** **One Click** **App**
---
# v1.8.0 - xCloud
> New Features Introducing One Click Apps with Node.js support:- Uptime Kuma- phpMyAdmin New demo domain xsql.app for phpMyadmin. Custom domain option for
### New Features
- Introducing **One Click Apps** with Node.js support:
– **[Uptime Kuma](/docs/deploy-uptime-kuma-with-xcloud/)**
– **[phpMyAdmin](/docs/how-to-deploy-phpmyadmin-with-xcloud/)**
- New demo domain **xsql.app** for phpMyadmin.
- Custom domain option for phpMyAdmin
- [**Site Limit** Feature is now available with xCloud Reseller platform](https://xcloud.host/docs/set-site-limits-with-reseller-hosting-program/)
- [User can now change server node version.](/docs/how-to-change-node-version-with-xcloud/)
- [8G Firewall Support is added in NGINX](/docs/enable-8g-firewall-in-xcloud/)
- [PHP 8.4 support for OLS servers](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
### Improvements
- Implemented next site prefix ID management for server.
- Improved NGINX settings update script with modular functions, detailed timestamped logging, enhanced error handling, robust config validation, and better PHP version scanning.
- Updated VPS DNS resolver to Cloudflare during server provisioning.
### Issues & Bug Fixes
- Multiple UI issues fixed including Notes card layout, Git push toggle, settings headings, team card dropdown overlap, small screen dropdown overflow, and provider label alignment.
- AWS provider selection issue fixed in server select page
- Issue fix with white label product creation with backup
---
# v1.8.1 - xCloud
> New Features n8n is now fully supported on xCloud!- Implemented timezone management for n8n sites with proper environment variable updates- Added Environment
### New Features
- [n8n is now fully supported on xCloud!
](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)– Implemented **[timezone management](/)** for n8n sites with proper environment variable updates
– Added [**Environment Editor** for n8n](/) with enhanced variable management using a .env file approach.
– n8n application **[update system](/)**
- [Site Backup and Restore now let you choose what to back up — only files, only the database, or both — instead of always backing up everything together.](/docs/site-backups-in-xcloud/)
- [**Added Ubuntu version selector** — choose between Ubuntu 24.x or 22.x when creating a server.](/docs/create-server-with-preferred-ubuntu-version/)
### Improvements
- Added comprehensive n8n update functionality with user confirmation and timeout handling
- Refactor n8n update notifications with improved language support
- Site Backup Script related improvements
### Issues & Bug Fixes
- Issue fixed with additional domain support during clone site feature
- Multiple fixes in the billing system
---
# v1.8.2 - xCloud
> New Features pCloud Storage Provider — Added support for pCloud as a new backup storage option, expanding cloud storage integration capabilities Korean
### New Features
- [pCloud Storage Provider — Added support for pCloud as a new backup storage option, expanding cloud storage integration capabilities](/docs/how-to-set-up-pcloud-storage-in-xcloud/)
- Korean Language Support — xCloud now supports Korean language in the application interface
### Improvements
- **n8n Enhancements:**
– n8n is now available for free users (removed from beta restrictions)
– Fixed Node.js version requirement validation for n8n installations
– Resolved broken icons issue in n8n applications
– Fixed browser title showing \[DEV\] tag by setting N8N\_RELEASE\_TYPE=stable
- **Enhanced Site Management — Comprehensive site sorting and filtering functionality with:**
– Active/Disabled site filtering options
– Site type filtering (WordPress, Laravel, Custom PHP, PHPMyAdmin, n8n, Uptime Kuma, Mautic)
– Configurable pagination (10, 20, 50, 100 per page)
– Improved sort options with user-friendly labels (“Oldest First”, “Newest First”)
– URL state preservation for all filters and preferences
- Site Creation Progress Updates — Dynamic animation images and new SVG assets for improved visual experience
- Billing System — Added billing service filter for unpaid teams to improve account management
### Issues & Bug Fixes
- Payment Gateway — Multiple fixes for payment gateway functionality and payment success hooks
- WordPress Database Integration — Fixed issue where database password updates weren’t reflected in WordPress wp-config.php files
- Site Filtering — Enhanced filter organization with logical groupings and visual separators
- User Experience — Persistent filter preferences and improved state management across page refreshes
---
# v1.8.3 - xCloud
> New Features Beta Feature Access - Mautic Server Dashboard:- Advanced Filtering: Added comprehensive filters for environment, status, site type, tags,
### New Features
- **Beta Feature Access – Mautic**
- Server Dashboard:
– Advanced Filtering: Added comprehensive filters for environment, status, site type, tags, vulnerabilities, and servers with real-time search
– Smart Sorting & Pagination: Implemented persistent user preferences for sorting (A-Z, date-based) and pagination (10-100 items per page)
– URL State Management: Filter states preserved in URL parameters and restored on page load
– Custom Site Titles: Added ability to set custom titles separate from domain names
– UI Integration: Site titles displayed in lists with domain name tooltips and settings page editing
### Improvements
- **n8n Enhancements:**
– Failure Tracking: Comprehensive update failure tracking with automatic status updates
– Multi-Channel Notifications: Email, Slack, WhatsApp, and Telegram notifications for update failures
– Node.js v20 Requirement: Updated minimum version for better compatibility
– Memory Optimization: Added heap memory limits to prevent JavaScript memory issues
- Detailed Disk Space Alerts: Added total, used, and available storage metrics to low disk space notifications
- Direct Folder ID Retrieval: Updated pCloud scripts to retrieve folder IDs directly from storage provider for improved reliability
- EU Region Support: Fixed pCloud EU region connectivity issues
- Billing System — Added billing service filter for unpaid teams to improve account management
- Modern TLS Only: Disabled TLS 1.0/1.1, enforced TLS 1.2/1.3 for Nginx and OpenLiteSpeed
- Secure Configurations: Added secure cipher suites and SSL handshake improvements
- Performance: Optimized queries for large site collections and memory management
### Issues & Bug Fixes
- Enhanced Confirmation Dialogs: Made resource names bold in deletion confirmation prompts
---
# v1.8.4 - xCloud
> New Features Mautic is released with 1-click app feature in xCloud. Improvements Enhance Server Monitoring- Display Total/Available RAM & Disk metrics on
### New Features
- [**Mautic** is released with 1-click app feature in xCloud.](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
### Improvements
- **Enhance Server Monitoring**
– Display Total/Available RAM & Disk metrics on the server monitoring page
– Added sortable tables for Top Processes (CPU and RAM) and Site Usage.
– Top Processes table now includes a “Site” column with a link to the corresponding site, providing better context.
– Improved the underlying monitoring script for more accurate process information.
- **Improve Magic Login Popup
**– Redesigned the Magic Login button into a split button.
– The primary action provides a direct magic login.
– A dropdown menu offers advanced options, including login with a custom username/email.
– Added a “Remember me” feature for custom logins.
– Updated UI with new icons for a better user experience.
### Issues & Bug Fixes
- Fixed favicon display for n8n one-click installs by updating Nginx to proxy /favicon.ico requests to the n8n container.
---
# v1.8.5 - xCloud
> New Features Upload Site via SFTP to migrate or create sites. New Custom Nginx Block "INSIDE PHP LOCATION BLOCK" type is added. Users can use this block to
### New Features
- **[Upload Site via SFTP to migrate or create sites.](/docs/manually-upload-wordpress-websites-with-sftp/)**
- **New Custom Nginx Block “INSIDE PHP LOCATION BLOCK” type is added.** Users can use this block to add security headers along with fastcgi.
### Improvements
- NGINX Customization UI: The Nginx configuration UI now adapts block types dynamically based on site type (PHP or proxy/Node), with enhanced templates and validation.
- Security Enhancements: Site resource titles in links now escape HTML for improved security.
- Customer Support and Feedback platform related enhancements:
– Userback and Live chat support now auto-syncs user email, billing plan, and team information for logged-in xCloud users.
These will eliminate asking for emails from logged in xCloud app users.
### Issues & Bug Fixes
- Refactored SFTP user creation and password management for migrations.
- Improved validation and error handling for SFTP/database uploads.
---
# v1.8.6 - xCloud
> New Features xCloud Mailbox Feature is released. - Enjoy premium business mailbox starts from $1 only.- Email aliases and forwarding.- Auto DNS record
### New Features
- [**xCloud Mailbox Feature is released.**](/docs/how-to-set-up-xcloud-mailbox-addon/)
– Enjoy premium business mailbox starts from $1 only.
[– Email aliases and forwarding.](/docs/how-to-set-up-xcloud-mailbox-addon/)
[– Auto DNS record management with Cloudflare integration.](/docs/how-to-set-up-xcloud-mailbox-addon/)
[– Configure with email client using IMAP/POP.](/docs/configure-email-client-with-mailbox-addon-xcloud/)
– Use as SMTP provider for transactional (server’s outgoing) emails.
– Secure email sending and receiving.
- Added Graph in **Site Monitoring** section along with filters.
### Improvements
- Centralized Addon Management is released. Users can view and manage all type of addons from dedicated section:
– Mail Delivery
– Vulnerability Shield Pro powered by Patchstack
– Mailbox
- **Site Backup Enhancements**:
– We’ve enhanced storage integrations with real-time status indicators, OAuth re-auth for Google Drive and pCloud, and better error handling.
– Implemented smart auto-delete logic for backups, intelligently managing storage usage without compromising user override options.
– Improved default backup settings handling to make the backup process more predictable and user-friendly.
– Added confirmation dialogs when backups are auto-deleted, reducing accidental deletions and improving user awareness.
- **UI/UX Enhancements**:
– Improved global site/server search functionality by automatically normalizing URLs (removing protocols and trailing slashes), ensuring consistent results regardless of format.
– Enabled real-time updates in search inputs via input and paste event handlers for faster and more responsive user interactions.
– Increased the site path input field size to display full paths clearly, improving visibility and user interaction.
– Made site action dropdowns dynamically adjust their direction, preventing UI cutoffs in tight spaces.
- Added support for auto cleanup of pm2 logs of Node apps.
- Users can now purchase multiple addons at a time from the addons section for:
– Mailbox
– Vulnerability Sheild Pro
### Issues & Bug Fixes
- Fixed visual bugs like the jumping PHP Settings card and incorrect font styling in the SSH key deletion modal for a smoother experience.
- Corrected the “xCloud” typo in the WhiteLabel configuration and improved visibility controls by hiding irrelevant backup settings in phpMyAdmin site overviews.
- Converted phpMyAdmin staging sites to demo environment, content updated so phpMyAdmin now shows “Demo Environment” instead of “Staging Environment”.
---
# v1.8.7 - xCloud
> New Features Custom Blueprints option is now available .You can now add custom themes and plugins to your blueprints using:- Direct Upload – Upload ZIP files
### New Features
- **[Custom Blueprints](/docs/how-to-create-a-custom-blueprint/)** option is now available .You can now add custom themes and plugins to your blueprints using:
– **Direct Upload** – Upload ZIP files manually
– **Download URL** – Add external download links (e.g., premium plugins)
– **CLI Script** – Run custom scripts after blueprint install to auto-configure and customize your site.
### Improvements
- **Smoother Cache Management** – Cache clearing operations now happen in the background, so you won’t experience delays or freezing when purging your site’s cache (Redis, Object Cache, or Cloudflare Edge Cache).
- **Better Server Monitoring** – Improved how we track and display server processes, making it easier to see which sites are using what resources in your monitoring dashboard.
- Custom email delivery providers are now automatically activated when you set them up on a site, eliminating the need for manual activation steps.
- Added Cloudflare integration in full server migration and all other site migration features.
### Issues & Bug Fixes
- Fixed access issues with Cloudflare integration when working across multiple teams, making site migration and domain management smoother.
---
# v1.8.8 - xCloud
> New Features New Server Provider Integration - Hostinger- Users can now integrate their Hostinger account in xCloud to directly create and manage their
### New Features
- **[New Server Provider Integration – Hostinger](/docs/set-up-hostinger-server-with-xcloud/)**
– Users can now integrate their Hostinger account in xCloud to directly create and manage their servers.
- **[MySQL/MariaDB Configuration Management](/docs/configure-mysql-and-mariadb-with-xcloud/)**: Easily optimize database performance without SSH using our new settings panel. Following items were added:
– Max Connections, Max Allowed Packet, InnoDB Buffer Pool Size, InnoDB Buffer Pool Instances, InnoDB Flush Log at Transaction Commit, Slow Query Log, Long Query Time, Sort Buffer Size, Binary Log Expire Time, InnoDB Flush Method
### Improvements
- **Firewall Rule Risk Warnings:** – No more accidental lockouts! xCloud now warns you before adding risky firewall rules, like blocking port 22 (SSH) or all IP. Users will get a clear warning and need to confirm before saving rules that could break access to your server or the xCloud panel.
- PHP version options on Ubuntu 20.04 are now limited to supported versions like PHP 7.4, as newer versions aren’t compatible and Ubuntu 20.04 is deprecated.
- Smarter SSL icons now show Cloudflare, xCloud, or disabled status at a glance across all views for easier recognition.
- Improved email validation now blocks invalid prefixes like i@domain.com and ensures generated passwords always include at least one number.
- Free plan users now see site creation limits with an option to upgrade for full access.
- Updated edge cache rules to exclude all sitemap and robots.txt files from caching for better SEO and compatibility.
- UI Improvements:
– Disabled features like Basic Auth, Backup, and Page Cache now show grayed-out icons in site dashboard.
– Fixed issue with the mailbox banner, once dismissed, it stays hidden and the setup-mailbox button won’t appear again if ignored.
### Issues & Bug Fixes
- Fixed one-click updates for vulnerable plugins and themes on the Vulnerability Shield Pro page, now working seamlessly.
- Improved SSL installation by resolving dpkg config conflicts for smoother setup.
- Fixed SMTP TLS verification issues and updated UI for better mail config experience.
- Fixed DNS controls showing for Cloudflare-managed domains on Full Server Migration feature, now hidden to avoid confusion
- Fixed an issue with CPU monitoring, CPU speed now displays correctly in the monitoring script.
- **System Enhancements:**
– Improved queue reliability by removing faulty processing logic in critical tasks
– Cleaned up old, unused code to simplify the system and improve stability.
---
# v1.8.9 - xCloud
> New Features 7G & 8G Firewall Integration for NGINXUsers can now customize and whitelist rules in the 7G & 8G WAF directly from xCloud, allowing safe
### New Features
- [**7G & 8G Firewall Integration for NGINX**](/docs/whitelist-7g-and-8g-waf-rules-in-xcloud/)
Users can now customize and whitelist rules in the 7G & 8G WAF directly from xCloud, allowing safe traffic (like Elementor, WooCommerce, SEO bots) while keeping your site secure.
- **Improved WordPress Migration Error Handling:
**Automatically detects missing files or corrupt installs with clearer error messages for easier troubleshooting.
- **Flexible Migration without SQL Upload**
Users can now migrate WordPress sites without uploading a .sql file when the database isn’t needed. More flexible migration options for just hosting basic HTML sites.
### Improvements
- Server Monitoring Update: Improved CPU speed detection and clearer upgrade messages for more accurate server insights.
- Vultr Backup Visibility Fixed: Backup lists and pricing now display correctly for Vultr and xCloud Vultr servers.
- Google Drive Backup Fixes: Fixed duplicate file issues for more reliable Google Drive backup operations.
- Custom Opt-in Form Styling: You can now set background colors on opt-in forms to better match your brand.
- Stronger Server Name Validation: Server names now follow stricter rules to avoid errors during setup.
- Fixed team permission issue with billing management
### Issues & Bug Fixes
- White Label Server Creation Fixed: Resolved provisioning issues to ensure smooth server creation in white label environments.
- AWS VPC Setup Fixed: Default VPCs are now correctly configured during AWS server provisioning.
- Billing Menu Visibility: Billing menu now shows correctly in both top navigation and sidebar for permitted users.
- SSH Key Deletion Modal Cleanup: Confirmation input now clears properly when the SSH key deletion modal is canceled.
- Basic Authentication Security Patch: Outdated Basic Auth credentials are now fully overwritten to prevent unauthorized access.
---
# v1.9.0 - xCloud
> New Features Multiple Themes in BluePrints: Add multiple WordPress themes to your BluePrints and choose the active one during site creation. Perfect for
### New Features
- **Multiple Themes in BluePrints:** Add multiple WordPress themes to your BluePrints and choose the active one during site creation. Perfect for flexible site templates.
- **Redesigned Site Backup Management Interface:** Modern tabbed layout with bulk actions, incremental backup visualization, and clearer summaries for easier backup control.
- **Largest Files & Folders Scanner:** Quickly find disk space hogs with color-coded size indicators and sortable results to optimize storage usage.
- **Blank Site Creation for Custom PHP**: Start with a clean slate using an empty PHP site template with a basic welcome page, then upload your apps via SFTP or File Manager.
### Improvements
- Enhanced WordPress security to stop risky plugin and theme actions. This prevents command injection issues and keeps your WordPress sites safer.
- Better server selection with dropdown menus now sorted alphabetically. You can also search servers, making it faster to find the right one when creating, cloning, or migrating sites.
- Automatic DKIM verification added for emails. When you verify DNS records, DKIM is now checked automatically so your emails show your domain in the “signed-by” field instead of the service domain.
### Issues & Bug Fixes
- Fixed several UI display issues: including long task names breaking event views, plugin icons not aligning in Blueprint cards, and Magic Login button design problems in migration screens.
- MariaDB installation issue fixed for smoother server setup.
---
# v1.9.1 - xCloud
> New Features Google PageSpeed Insights Integration – New performance monitoring system with enhanced UI/UX, offering comprehensive site analytics and
### New Features
- **[Google PageSpeed Insights Integration](/docs/how-to-access-page-speed-insights-on-xcloud/)** – New performance monitoring system with enhanced UI/UX, offering comprehensive site analytics and real-time performance tracking. What this feature provides:
– A performance score for your website (mobile and desktop)
– A detailed breakdown of site performance
– Suggestions to fix issues like large images, unused scripts, and slow server response
– Insights into Core Web Vitals (LCP, FID, CLS) so you can meet Google’s speed standards
### Improvements
- Backup Management – UI fixes and improvements, including better restore selection, alignment fixes, and a loading spinner for empty views.
- Refactored and optimized various codebase for better stability and maintainability.
### Issues & Bug Fixes
- Fixed 7G/8G firewall log format naming conflicts
- Fixed duplicate notification issue when deleting a site.
---
# v1.9.2 - xCloud
> New Features Support Portal is now inside your xCloud dashboard 🔥- No separate login, now you can manage tickets right inside the app.- Pick the server, site,
### New Features
- **[Support Portal is now inside your xCloud dashboard 🔥](/docs/access-built-in-support-portal-in-xcloud/)**
– No separate login, now you can manage tickets right inside the app.
– Pick the server, site, and team when opening a ticket.
– **Team members** can handle tickets with **team-based permissions**.
– Securely share Magic Login and SSH access with support when needed.
- [Site cloning now gives you the option to copy site settings from the source site](/docs/clone-site-under-same-different-server-in-xcloud/), including backup preferences (remote & local) and security settings (XML-RPC, X-Frame-Options, 8G Firewall, AI Bot Blocker, WP Fail2Ban). SMTP and others will be added soon.
### Improvements
- If xCloud auto-healing can’t recover a service, your dashboard will show clear status alerts for NGINX/OLS, MySQL, Redis, SSH, and PHP.
- Enhanced 7G/8G Firewall User Experience with improved logging.
- Added Disk Space and RAM Warning Component for Server Overview
### Issues & Bug Fixes
- Fixed Vultr server backup list fetching issue
- Improved PageSpeed Insights error handling.
- Fixed issue with showing the latest backup status for sites.
---
# v1.9.3 - xCloud
> New Features Wasabi Integration - New Storage Provider For Remote Site Backup Enabling HTTP/3 on xCloud for Faster & More Reliable Website Performance
### New Features
- [Wasabi Integration – New Storage Provider For Remote Site Backup](/docs/integrate-wasabi-storage-provider-with-xcloud/)
- [Enabling HTTP/3 on xCloud for Faster & More Reliable Website Performance](/docs/how-to-enable-http-3-in-xcloud/)
- Support for MySQL 8.4 and MariaDB 11.6
### Improvements
- Support Portal now shows specific time and date in conversation page
### Issues & Bug Fixes
- Fixed validation issues with the Custom Blueprint feature.
- Support Ticket Portal now shows the full date and time for each message.
- Fixed an issue where SSL certificates were not installed correctly when cloning a staging site to production. Certificates now install automatically.
- UI Fixes
– Tooltips in the team switcher now display in the proper place so that long team names are easier to read.
– Fixed an issue where reply links from support agents were not visible in light mode.
---
# v1.9.4 - xCloud
> New Features Git Provider Integration – Connect your GitHub account, integrate repositories, and launch projects directly from your dashboard. Also, deploy
### New Features
- [Git Provider Integration](/docs/how-to-integrate-a-git-provider-with-xcloud/) – Connect your GitHub account, integrate repositories, and launch projects directly from your dashboard. Also, deploy projects from both public and private repositories seamlessly.
- [SFTP Storage Backup Support](/docs/integrate-sftp-storage-provider-with-xcloud/) – Integrate SSH storage provider to store site backups. It gives flexibility for teams with existing SFTP infrastructure.
- [Updated PHP Version Management](/docs/how-to-upgrade-php-version-with-xcloud-hosting/) – Get full control of PHP settings on your servers with a new intuitive interface. Install, uninstall, and configure multiple PHP versions with real-time status, OPCache management, and easy default version switching.
- White-Label Invoice Management – White-label admins can now edit client invoices directly and automatically sync email changes with Stripe customer records.
### Improvements
- Auto backups are now enabled by default when creating new servers on xCloud Managed and Provider servers.
- On the xCloud Managed server create page, full server backup is now pre enabled by default with a option to disable after confirming a warning.
- Free plans now assign properly to teams without payment methods.
### Issues & Bug Fixes
- Fixed an issue where successful reboots were incorrectly shown as failed.
- Issue fixed with failed payments.
---
# v1.9.5 - xCloud
> New Features Updates Manager – Update plugins, themes, and WordPress core files on all your sites at once from one dashboard. It makes managing multiple sites
### New Features
- [Updates Manager](/docs/manage-wordpress-updates-with-updates-manager/) – Update plugins, themes, and WordPress core files on all your sites at once from one dashboard. It makes managing multiple sites much easier for agencies and users who manage multiple every day.
### Improvements
- Server updates now handle missing GPG keys automatically for making maintenance smoother.
- Added warnings for SSL issues on n8n sites using OpenLiteSpeed and Let’s Encrypt.
### Issues & Bug Fixes
- Large backup files from pCloud now download with proper headers.
- SFTP backups now restore properly in production without SSH connection issues.
---
# v1.9.6 - xCloud
> New Features Multi Domain Support for Cloudflare Managed Sites – Manage multi site subdomains and multiple additional domains under the same primary domain
### New Features
- [Multi Domain Support for Cloudflare Managed Sites](/docs/using-xcloud-with-cloudflare-for-dns-management/) – Manage multi site subdomains and multiple additional domains under the same primary domain easily.
### Improvements
- PHP security patches can now be detected and installed with one click in PHP configuration, with real-time update notifications.
- Custom web root validation has been improved and now blocks unsafe paths more strictly.
### Issues & Bug Fixes
- Fixed pCloud backup restore issue to properly site backup recovery.
---
# v1.9.7.1 - xCloud
> Issues & Bug Fixes Fixed a issue related to the user role access in the Updates Manager.
This site uses cookies and tracking technologies. You may accept all or customize according to your preferences.
Customize Accept All
## Customize Consent Preferences
×
Please select whether you consent to our use of cookies and related technologies ("Cookies"), as described in our Privacy Policy and Cookie Policy. Expand each section below for more information. You can return at any time from the same web browser to update your preferences. Please note that resetting your browser's cookies will reset your preferences.
▶
#### Required Cookies
Enabled
These Cookies are necessary for core features of this site to operate properly. Because they are needed for the site's operation, they are always set to "Active".
Company
Domain
Userback
app.userback.io
FirstPromoter
xcloud.firstpromoter.com
Crisp
https://crisp.chat
▶
#### Functional Cookies
These Cookies allow us to analyze site usage in order to evaluate and improve performance.
Company
Domain
Microsoft Clarity
clarity.microsoft.com, www.clarity.ms
Google Analytics
analytics.google.com, www.google-analytics.com
▶
#### Advertising / Marketing Cookies
These Cookies help us measure the effectiveness of our marketing efforts, referral programs, and promotional activities.
Company
Domain
Google Tag Manager
www.googletagmanager.com, googletagmanager.com
Meta (formerly Facebook)
connect.facebook.net, facebook.com
Save My Preferences Accept All
October 12, 2025
[Back To Changelog](/changelog/)
# v1.9.7.1
- No categories
### Issues & Bug Fixes
- Fixed a issue related to the user role access in the Updates Manager.
---
# v1.9.7 - xCloud
> Improvements Added hard server reboot option for Reseller Program, allowing resellers and their clients to reboot servers directly from their dashboard with
### Improvements
- Added hard server reboot option for Reseller Program, allowing resellers and their clients to reboot servers directly from their dashboard with confirmation modal to prevent accidental restarts.
- Enhanced WordPress version detection with multiple methods for smarter and more accurate vulnerability scanning.
- Improved update management with real-time status indicators, better error handling, and smoother tracking for plugin and theme updates.
- Added WordPress version validation to ensure only properly formatted versions are processed during scans for increased reliability.
- Added Cloudflare multi-domain indicators to identify sites protected under Cloudflare’s multi-domain setup.
- Added monitoring script sync command to keep vulnerability and version tracking consistent across all sites.
### Issues & Bug Fixes
- Fixed plugin/theme update errors and improved WordPress version normalization.
- Resolved site migration and Cloudflare multi-domain cloning issues.
- Corrected SSL provider icon display and firewall compatibility.
- Fixed backup file deletion for S3-compatible storage.
- Improved OpenLiteSpeed additional domain configuration and Cloudflare edge caching.
---
# v1.9.8 - xCloud
> New Features Resell Hosting with Self Managed Server Provider- Bring your own server such as DigitalOcean, Hetzner, Vultr, Linode, and more and start reslling
### New Features
- [**Resell Hosting with Self Managed Server** **Provider**](/docs/resell-hosting-with-self-managed-server-provider/)
– Bring your own server such as DigitalOcean, Hetzner, Vultr, Linode, and more and start reslling with xCloud Reseller Program.
- [**Smart Currency & Pricing System**](/docs/resell-hosting-with-self-managed-server-provider/)
– Real-time exchange rates powered by OpenExchangeRates API with automatic currency detection and daily updates, helping resellers manage pricing globally with ease.
- Profit & Product Creation Assistance
\-Simplified product creation with built-in profit and loss calculation tools, so resellers can set better prices and maximize their margins.
– Improved Server Creation Flow
– Payment-first setup with invoice generation before provisioning.
– SKU-based product selection for smoother operations.
– Detailed technical error messages for easier troubleshooting.
### Improvements
- SSL Issue Fixed for OLS Server with Multiple Domain Sites
---
# v1.9.9.1 - xCloud
> Issues & Bug Fixes Adminer:- Fixed issues with Adminer Title and DB section- Refactored core script for improved performance and maintainability- Cleaner
## Issues & Bug Fixes
- Adminer:
– Fixed issues with Adminer Title and DB section
– Refactored core script for improved performance and maintainability
– Cleaner SQL execution and multi-query support
– Better form handling, import/export, and schema management
– Enhanced reliability and extensibility for future Adminer updates
---
# v1.9.9 - xCloud
> New Features Node.js Hosting – Full Node.js support is now live on xCloud, giving you the same seamless experience you love with WordPress and Laravel. Deploy
### New Features
- **[Node.js Hosting](/docs/how-to-deploy-a-node-js-application/)** – Full Node.js support is now live on xCloud, giving you the same seamless experience you love with WordPress and Laravel. Deploy modern apps like **Next.js** effortlessly from your public or private Git repositories — all in just a few clicks.
### Improvements
- Adminer Upgrade – Updated to v4.8.1 with multilingual and secure builds.
- WordPress Bulk Access Control – Improved access for non-owner team members. Admins now only see sites they’re allowed to, while “All Access” users keep full visibility.
### Issues & Bug Fixes
- Fixed SFTP Storage Provider import issues during bucket restoration.
- Removed a conflicting slash key handler that was interfering with Support Portal functionality.
- Fixed language inconsistency issues for all notification channels.
- Fixed 7G and 8G firewall log links for OpenLiteSpeed servers
- Fixed the site deletion timeout status, which was not updating after a site deletion failed.
- Redis ACL Fix – Fixed user deletion permission issue during cleanup.
- Local site backup delete option now only shows when local backups exist, reducing UI clutter.
- Improved error handling and state updates for backup deletion jobs.
---
# v2.0 - xCloud
> New Features ✨Self-Host Your Own LLM (like ChatGPT) — You can now deploy and run your own AI models directly inside xCloud using Docker + NGINX. The core
### New Features
- [✨**Self-Host Your Own LLM (like ChatGPT)**](/docs/how-to-self-host-llms-with-xcloud/) — You can now deploy and run your own AI models directly inside xCloud using Docker + NGINX. The core Docker infrastructure is now in place, laying the groundwork for upcoming AI and app hosting capabilities.
### Improvements
- Disabled NGINX Config support for Cloudflare Multi-Domain Architecture to ensure smoother compatibility.
- Added redirect support for additional domains to the main domain in OLS vhConfig.
- 8G Firewall support extended to One-Click Apps.
### Issues & Bug Fixes
- Adminer Dark Theme Loading: Fixed an issue where the dark theme in Adminer (database management tool) wasn’t loading correctly due to corrupted CSS data.
---
# v2.1.0 - xCloud
> New Features Deploy Nextcloud with one click — You can now deploy and manage Nextcloud as a containerized app directly inside xCloud’s Docker+NGINX stack,
### New Features
- **[Deploy Nextcloud with one click](/docs/how-to-set-up-nextcloud-with-one-click/)** — You can now deploy and manage **Nextcloud** as a containerized app directly inside xCloud’s Docker+NGINX stack, unlocking flexible and secure file sharing, storage, and collaboration capabilities.
### Improvements
- Improved Cloudflare integration with better handling for edge/null cases.
- Resellers can edit product descriptions now.
### Issues & Bug Fixes
- Issue fixed with Re-seller’s subscription section in app.
- Fixed multisite login issue by correctly setting HTTP\_COOKIE handling in wp-config.php for WordPress multisite installations.
- Fixed various front end bugs
---
# v2.1.1 - xCloud
> New Features Deploy LibreChat with One Click Apps —LibreChat lets you deploy your own customizable, open-source AI chat platform in just a few clicks. With
### New Features
- [Deploy LibreChat with One Click Apps](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/) —LibreChat lets you deploy your own customizable, open-source AI chat platform in just a few clicks. With this, you can easily manage AI models, configure your environment, and scale as needed. Whether for experimentation or production, LibreChat gives you full control and flexibility without the setup headaches.
- [Set Your Own Default Landing Page](/docs/how-to-set-the-default-site-for-your-server/) – Turn your server’s IP into a branded first impression. With the new Default Site feature, instead of showing a plain, generic default page when someone visits your server’s IP address, you can now point them to any website or domain you choose.
### Improvements
- Error messages now show whether a site or server creation failed for easier troubleshooting.
- Site cloning has been simplified by removing unsupported Docker + Nginx servers from clone options.
### Issues & Bug Fixes
- IP whitelist and blacklist rules on OpenLiteSpeed now work correctly for all site types.
---
# v2.1.3 - xCloud
> New Features Umami is now available under One Click App Section Improvements Users Can Resize LTD Plan on their own now. Users (including reseller clients)
### New Features
- [Umami is now available under One Click App Section](/docs/how-to-install-umami-with-xcloud/)
### Improvements
- [Users Can Resize LTD Plan on their own now.](/docs/how-to-upgrade-xcloud-lifetime-deal-package/)
- Users (including reseller clients) can now view pending server setup items directly on their dashboard after completing a purchase from the cart.
- Storage Space Validation for Docker Apps – Added pre-installation storage checks for all containerized one-click applications (Umami, Nextcloud, LibreChat, OpenWebUI, Ollama). The system now validates available disk space before deployment to prevent installation failures due to insufficient storage, with configurable minimum requirements per application type.
- White Label – Added support for switching between paid plans and free plans
### Issues & Bug Fixes
- Issue fixed with White Label free subscription claim for LTD users
---
# v2.1.4 - xCloud
> New Features Auto-Tune MySQL/MariaDB Configurations - One click Auto Tune feature automatically analyzes server resources and applies optimized values for Max
### New Features
- [Auto-Tune MySQL/MariaDB Configurations](/docs/auto-tune-mysql-mariadb-configurations/) – One click Auto Tune feature automatically analyzes server resources and applies optimized values for Max Connections, Max Allowed Packet, and InnoDB Buffer Pool Size.
### Improvements
- **OPCache Auto-Enablement** – OPCache is now automatically enabled whenever PHP is installed, removing the need for manual activation.
- Added [**LTD conversion** option for self-managed servers](https://d.pr/i/OX53rW) directly from the server sites page.
- Improved storage checks for Docker apps to prevent failed installations.
- Redesigned the unused items warning banner with a cleaner, more informative UI.
- Enhanced Stripe payment handling and reliability for 3DS and recurring payments.
- Fixed package assignment issues and added safeguards against duplicate assignments.
- Added stronger duplicate job prevention across billing processes.
- Improved site file removal with better logging and error handling.
- UI/UX tweaks, including routing fixes and cleaner visibility for Docker site options.
### Issues & Bug Fixes
- Resolved stored invoice job execution errors and improved job timing.
---
# v2.1.5 - xCloud
> New Features Build With AI in xCloud - Powered by Templately: xCloud simplifies site creation with Templately AI. Deploy a site using ready-made templates and
### New Features
- [Build With AI in xCloud – Powered by Templately](/docs/build-a-wordpress-site-with-templately-ai/): xCloud simplifies site creation with Templately AI. Deploy a site using ready-made templates and AI-powered content in just a few minutes.
- [Global Site Backup Feature:](/docs/global-backup-settings-with-xcloud/)
– Central Site Backup Setting Page under Team
– Manage and monitor all Site Backup settings from one place
– Site backup feature is now available in the Site Creation page.
### Improvements
- Root SSH access security improved by disabling login with the root password (key-based only).
- Site backup UI improvement related to auto backup and custom settings.
### Issues & Bug Fixes
- Fixed issue with incremental site backup bugs.
- Fixed issue with ticket SSH permission action.
---
# v2.1.6 - xCloud
> New Features Site Security Pro powered by Patchstack is now available for $2/site for a limited time. Site Security Pro now comes with an integrated
### New Features
- **[Site Security Pro](/docs/set-up-site-security-pro/)** powered by Patchstack is now available for $2/site for a limited time. Site Security Pro now comes with an integrated Patchstack Dashboard for a faster, more seamless security experience.
- Beta access for Supabase One-Click Application.
- Beta access for the Supabase One-Click Application.
### Improvements
- Improved ticket creation experience with new Switch controls for Magic Login and SSH Access. Added clear helper text and better spacing to make support permission options easier to understand.
- Added UI to updated Nextcloud admin password.
### Issues & Bug Fixes
- Fixed a bug where PHP versions were not updating correctly during server setup.
- PHP version info now syncs properly for both Nginx and OpenLiteSpeed servers.
- Fixed the provider connection check issue on the white-label settings page.
---
# v2.1.7 - xCloud
> New Features Deploy Site.pro with One Click Apps: Site.pro lets you launch AI-powered, no-code websites in just a few clicks. With this, you can design
### New Features
- [Deploy Site.pro with One Click Apps](/docs/how-to-install-site-pro-with-xcloud/): Site.pro lets you launch AI-powered, no-code websites in just a few clicks. With this, you can design responsive sites using a drag-and-drop editor, AI-assisted layouts, and ready-made templates.
### Improvements
- [**Global Backup Settings**](/docs/global-backup-settings-with-xcloud/) now processes bulk site backups in batches to ensure smooth site backups.
- Added retry functionality for failed Site Security Pro powered by Patchstack activations with real-time updates.
- Increased the SFTP backup storage IP address character limit from 20 to 200 characters to support longer IPs and domain names.
### Issues & Bug Fixes
- Resolved timeout issues when applying bulk backup settings to large site groups.
---
# v2.1.8 - xCloud
> New Features Deploy Supabase with One Click Apps: Supabase is now available on xCloud as a One-Click App, providing a complete self-hosted backend for modern
### New Features
- [Deploy Supabase with One Click Apps](/docs/how-to-install-supabase-with-xcloud/): Supabase is now available on xCloud as a One-Click App, providing a complete self-hosted backend for modern web applications.
- Lovable Hosting Beta Release: Lovable Hosting is now available in beta on xCloud. All users who registered through the early access form have been granted access.
### Improvements
- Fixed issues when changing Docker-based One-Click Apps domains from demo to live.
- Streamlined LibreChat installs and added copy buttons for admin credentials.
### Issues & Bug Fixes
- Fixed an issue related to the large team photo uploads.
- Resolved as an issue where the “Add New Provider” window wouldn’t open again after closing it.
---
# v2.1.9 - xCloud
> Lovable lets you build and launch full-stack websites and applications by chatting with AI. With this, you can create frontend, backend, and databases automatically, with instant deployment and launch with xCloud – no code required.
### New Features
- [**Deploy Lovable Applications with xCloud**](/docs/deploy-lovable-applications-with-xcloud/): Lovable lets you build and launch full-stack websites and applications by chatting with AI. With this, you can create frontend, backend, and databases automatically, with instant deployment and launch with xCloud – no code required. Moreover, you can easily [**connect Supabase with Lovable**](/docs/how-to-connect-supabase-to-lovable/) for a secure, scalable backend.
### Improvements
- Added team and member search functionality to make team management more efficient.
- Fixed an issue related to the site cloning.
### Issues & Bug Fixes
- Fixed an issue related to the duplicate server provider entries.
- The issue with the Web Root path is fixed on OLS servers.
---
# v2.2.0 - xCloud
> New Features MinIO is now supported with “Any Storage Provider” option in xCloud to take remote site backups. Issues & Bug Fixes Front end issue fixed
### New Features
- [MinIO is now supported with “Any Storage Provider” option in xCloud to take remote site backups.](/docs/site-backups-in-xcloud/)
### Issues & Bug Fixes
- Front end issue fixed with Docker NGINX servers showing WordPress and other apps which are not supported
- Fixed issue with Ollama site failed installation due to low storage.
- Fixed icon issues of mobile-menu item
---
# v2.2.1 - xCloud
> New Features Deploy WireGuard with One Click Apps - WireGuard lets you launch a secure, high-performance VPN in just minutes. With one-click deployment on
### New Features
- [Deploy WireGuard with One Click Apps](/docs/install-wireguard-with-xcloud/) – WireGuard lets you launch a secure, high-performance VPN in just minutes. With one-click deployment on xCloud, you can protect your network using modern encryption, ultra-fast connections, and minimal system resources without any complex configuration.
- Custom Docker with Docker Compose (Beta) – You can now deploy applications using Docker Compose on xCloud. This beta feature makes it easy to launch and manage multi-container applications in just a few clicks.
### Issues & Bug Fixes
- Fixed WordPress site detection issues during full server migration from RunCloud.
- Fixed a UI issue on the Site Clone Progress screen.
- Fixed the Update Manager tab count filter issue.
- Fixed an SSL issue related to live domains in One Click Apps.
---
# v2.2.2 - xCloud
> New Features Custom Docker with Docker Compose – You can now deploy full multi-container applications on xCloud using Docker Compose. Launch a docker
### New Features
- [**Custom Docker with Docker Compose**](/docs/how-to-deploy-custom-docker-with-xcloud/) – You can now deploy full multi-container applications on xCloud using Docker Compose. Launch a docker application either by providing a public Compose file URL or by pasting the file directly – no complex setup required
- [**SSH Access Lockdown**](https://xcloud.host/docs/how-to-restrict-ssh-access-lockdown/) – Secure your servers by restricting SSH(22) access to trusted IP addresses only. Your active IP and required xCloud infrastructure IPs are automatically whitelisted to keep your server secure and accessible.
- [Allow Caching of URLs With Query Strings](/docs/how-to-allow-caching-of-a-url-with-a-query-string/) – Improve performance for pages with query parameters like utm\_source, gclid, or fbclid. Choose which parameters to ignore directly from the xCloud dashboard to enable caching, boost load times, and reduce server load without affecting tracking.
### Improvements
- Added Hungarian language support for a fully localized xCloud experience.
- Enhanced site cloning with clearer errors and an easier retry flow.
- Fixed an issue related to the Fail2Ban compatibility.
- Enhanced site cloning by providing clearer error messages to retry for failed operations.
### Issues & Bug Fixes
- Fixed SSL configuration sync issues in OpenLiteSpeed.
- Resolved delayed UI updates after team deletion.
- Fixed hidden action menus on White Label invoices.
- Fixed cache rule tests to prevent validation errors.
---
# v2.2.3 - xCloud
> New Features Site Snapshots - Create reusable snapshots of your WordPress sites, including files and database, and deploy them instantly on the same server or
### New Features
- **[Site Snapshots](/docs/create-a-snapshot-to-deploy-a-wordpress-site/) –** Create reusable snapshots of your WordPress sites, including files and database, and deploy them instantly on the same server or across different servers. Ideal for agencies and developers who need to spin up pre-configured sites quickly. Snapshot creation progress is tracked in real time, and all snapshots are managed from a dedicated section in your profile.
- ****Node.js v24**** is now available for installation on servers.
### Improvements
- Centralized Credential Security – Sensitive credentials are no longer sent via email by default. Server, database, and Redis credentials are now securely accessible from the dashboard with masked display and reveal or copy options. Email notifications include a new “Send Sensitive Info” toggle, disabled by default, for better security control.
- Optimized OpenLiteSpeed PHP Workers – OpenLiteSpeed sites now automatically calculate the optimal number of PHP workers based on server CPU and RAM, replacing the previous fixed limit. This improves performance and resource utilization, with manual overrides still available from PHP Settings.
- Smarter Server Reboot Notifications – Reboot notifications can now be snoozed for 3, 7, or 30 days, or disabled per server. Newly created servers (under 12 hours old) no longer trigger reboot alerts, and servers with auto-reboot enabled will not send unnecessary notifications. Notifications can be re-enabled anytime from the Security Update page.
- Improved Git Repository Setup – Git repository URLs now automatically append `.git` when missing, and the branch field defaults to `main`, reducing setup errors during Git-based deployments.
- Staging and Demo Domain Customization – Staging and demo domains can now be customized before deployment for Custom PHP, Laravel, Node.js, Lovable, manual migrations, and site migrations, giving more control over development and demo environments.
- Optimized WordPress Bulk Operation History – Resolved memory allocation issues when viewing bulk operation history for large teams by optimizing queries and database indexing.
- Clearer SSH Restriction Notices
- A critical zero-day in the Modular DS plugin was detected and automatically mitigated across all xCloud sites using Site Security Pro powered by Patchstack. Also, all affected sites were auto-updated to v2.5.2 of the plugin and users notified by email, no action required.
### Issues & Bug Fixes
- Invoice Filter Links Fixed
- Nginx configuration has been updated to correctly respect upload size limits, improving large file uploads for applications like Nextcloud.
- Fixed an issue where Patchstack was not activating during staging-to-production pushes. The deployment process now ensures correct activation.
---
# v2.2.4 - xCloud
> Security Update Mitigated another critical vulnerability (CVE-2026-23800, CVSS 10.0) in the Modular DS (Modular Connector) plugin by force-updating all
### Security Update
- Mitigated another critical vulnerability (CVE-2026-23800, CVSS 10.0) in the Modular DS (Modular Connector) plugin by force-updating all affected sites to v2.6.0.
### Issues & Bug Fixes
- Issue fixed with Reseller pane’s logo with signup and login pages.
---
# v2.3.0 - xCloud
> xCloud UI 2.0 introduces a redesigned dashboard built to make site and server management more intuitive and efficient. This release focuses on faster
## 🎉**Introducing xCloud UI 2.0: Experience Faster & Smarter Dashboard**
xCloud UI 2.0 introduces a redesigned dashboard built to make site and server management more intuitive and efficient. This release focuses on faster navigation, clearer visibility, and simpler daily workflows through a more structured and organized xCloud control panel.
### ✨**Revamped Overview Dashboard**
The new Main Overview Dashboard provides a single place to view your overall activities of your team. It shows key information such as servers, sites, vulnerable sites, backups, and billing, helping you manage more quickly.
### ✨**New Site Lists Dashboard**
The All Site Lists Dashboard has been redesigned to simplify managing multiple sites. Site statuses are clearer, and bulk actions allow you to perform common tasks like backups, site enable or disable, and security actions directly from the list without switching between individual sites.
### **Default View and Grid View for All Sites List**
The All Sites List Dashboard opens in Default View, which is designed for managing multiple sites efficiently. In this view, you can use bulk actions and quick controls to perform tasks across many sites at once.
You can switch to Grid View to see each site’s information more clearly. Grid View focuses on visibility, showing site details and status in a more visual layout, making it easier to review individual sites at a glance.
### ✨**Redesigned Single Site Overview Dashboard**
The Single Site Dashboard now displays important site details in a cleaner layout. Resource usage, backups, performance, security, domains, updates, caching, and recent activity are easier to view and manage from one place.
### **✨Updated Top Bar and Sidebar Navigation**
Navigation has been improved with an enhanced Top Bar and Sidebar. Key actions remain accessible, and moving between servers, sites, and settings is more straightforward and consistent.
### ✨**Bulk Actions, Filters, and Sorting**
Bulk actions, filters, and sorting options help reduce repetitive work. These tools make it easier to find, manage, and take action on multiple sites at once.
### ✨**Improved Dark and Light Modes**
Dark and light modes have been updated for better consistency across the platform. Improved contrast and spacing make the interface easier to read during long working sessions.
### ✨**Standardized Icons and Tooltips**
Icons are now consistent across the dashboard, and tooltips provide additional context where needed. This helps reduce confusion and makes actions easier to understand.
### ✨**Updated Color System**
The updated color system improves contrast and visual hierarchy. System and site statuses are easier to identify at a glance, improving overall readability.
🔔 In this first phase, the new UI is available on key pages. Other pages and sections will be updated gradually in upcoming releases. Your feedback is important during this transition. Use the feedback button from the dashboard anytime to help us improve the experience as we continue refining xCloud.
Get more details about the New UI 2.0:
➡️ [_**I**_**_ntroducing xCloud UI 2.0: Built for Faster, Simpler Site & Server Management_**](/introducing-xcloud-ui-2-0/)
---
# V2.3.1 - xCloud
> ✨ Improvements Improved Docker server monitoring and container health visibility. Added usable disk space for all type servers. Improved sync monitoring
### ✨ Improvements
- Improved Docker server monitoring and container health visibility.
- Added usable disk space for all type servers.
- Improved sync monitoring command with a stack-based filter option.
- Improved site filtering with support for filtering by tags.
- Improved site deletion process and site state handling.
### 🔧 Bug Fixes
- Fixed Hetzner server size availability issues during server creation.
- Fixed region compatibility errors for Hetzner servers.
- Fixed notification system errors when integrations are not configured.
---
# v2.3.2 - xCloud
> 🌟 OpenClaw Hosting (Beta): Launch a fully managed AI agent on xCloud with one-click deployment and zero setup. OpenClaw runs on a dedicated managed server,
### 🔥 New Features
**🌟 OpenClaw Hosting (Beta):** Launch a fully managed AI agent on xCloud with one-click deployment and zero setup. OpenClaw runs on a dedicated managed server, comes pre-configured with messaging channels like Telegram, and lets you control real tasks, workflows, and integrations entirely through chat.
Ideal for individuals and teams who want a powerful AI assistant without handling infrastructure, updates, or security.
- Get the environment editor to configure environment variables.
- Control OpenClaw UI turn on/off right from the xCloud dashboard.
- Control OpenClaw versions, check for the lates updates easily.
- AI agent maintains long-term context, executes real tasks, manages files, and connects to external APIs
- One-click deployment on xCloud Managed Servers with no Docker, SSL, or manual setup
- Works across Telegram messaging platforms.
- Bring your own API keys for OpenAI, Gemini and more models. Anthropic is also coming very soon.
- Manage multiple messaging channels from a single dashboard
- Scale CPU, RAM, and storage at any time with fully managed updates and security
- Available only on xCloud Managed Servers and requires more than 4GB RAM.
- Cannot be installed on external or existing servers and runs OpenClaw only
### 🔖 Resources
👉 Visit this page to learn more about [xCloud Managed OpenClaw Hosting](/openclaw-hosting/).
👉 Follow the step-by-step guide to [deploy OpenClaw with xCloud](/docs/how-to-deploy-openclaw-with-xcloud/).
👉 Use this link to purchase and [deploy OpenClaw on xCloud instantly.](https://app.xcloud.host/openclaw/)
---
# v2.3.3 - xCloud
> 🦀 OpenClaw Hosting — Update. Big improvements to the OpenClaw one-click hosting on xCloud:
### 🔥 New Features
🦀 OpenClaw Hosting — Update.
Big improvements to the OpenClaw one-click hosting on xCloud:
- **Anthropic API Key support added**
- **Claude Code Token support** — use your Claude Pro/Max subscription with OpenClaw
- **Browser-based token generation** — Now, there is no need to install the Claude Code CLI manually. Generate your token directly from your browser. This one is a game changer, and no one has done this yet 👏
First, select the **Claude Code CLI** option and then click on **Generate Token**.
Then a screen will appear, and it will help to generate a Claude OAuth token using the same OAuth flow as Claude Code, and the process is absolutely fluent.
- **Telegram Improvements** – Smarter auto-pairing:
When you provide your Telegram User ID during setup, your account is automatically allowlisted. No more running commands to pair your account!
---
# v2.3.4 - xCloud
> 🔥 New Features WordPress New: Enhanced WP Debug Log Viewer inside the xCloud dashboard for faster, clearer troubleshooting Structured fields: Timestamp,
#### 🔥 New Features
#####  WordPress
- **New: [Enhanced WP Debug Log Viewer](/docs/view-logs-and-events-of-your-server-and-site/)** inside the xCloud dashboard for faster, clearer troubleshooting
1. Structured fields: Timestamp, Level, Source, File Path, Message, Line Number
2. Clearer log levels: Warning, Fatal, Database, and more
3. One-click copy for log messages and file paths
4. Search + filter large logs instantly
5. One-click download for offline review or team collaboration
#####  OpenClaw
- **New:** [Update default LLM provider settings directly from xCloud](/docs/how-to-deploy-openclaw-with-xcloud/)
- **New:** [Add or update Telegram channels directly from xCloud](/docs/how-to-deploy-openclaw-with-xcloud/)
#### ✨ Improvements
- Improved Docker log visibility with **container-wise log viewing** for Docker Nginx sites
- Improved UI alignment and spacing consistency across multiple pages
- Added automatic lowercase handling for staging and demo domain names
- Added full **Vietnamese** language support across the UI and all notification channels
- Improved staging site isolation with **unique site users**
- Updated **Cloudflare DNS architecture** for staging
- Added billing type selection for **self-managed server** creation
- Updated the default server OS to **Ubuntu 24.04 LTS** for new servers
#### 🔧 Issues and Bug Fixes
- Fixed RAM display to always show actual monitoring data
- Fixed WhatsApp URL handling and low disk space notification timestamps
- Fixed missing page title on non-WordPress site overview pages
- Fixed JQ installation error handling in backup cron scripts
- Fixed issue with the OpenClaw updater
- Fixed issue with the OpenClaw rescue feature
---
# v2.3.5 - xCloud
> 🌟 FPM Configuration: Site-Level PHP-FPM Configuration Is Now Available on xCloud. You can now control PHP-FPM settings for each site directly from the
### 🔥 New Features
### 🌐 WordPress
🌟 **[FPM Configuration](/docs/how-to-configure-php-settings/):** Site-Level PHP-FPM Configuration Is Now Available on xCloud. You can now control PHP-FPM settings for each site directly from the dashboard without SSH access or manual configuration files. This update lets you tune PHP worker behavior, manage resource usage per site, and handle traffic spikes more reliably while avoiding risky server-wide changes.🚀
- Process Manager Type: Process manager mode used by PHP-FPM to handle requests.
- PM Start Servers: Number of PHP worker processes started when PHP-FPM launches.
- PM Min Spare Servers: Minimum number of idle PHP worker processes kept ready.
- PM Max Spare Servers: Maximum number of idle PHP worker processes allowed.
- PM Max Requests: Number of requests a PHP worker handles before restarting.
- PM Max Children: Maximum number of PHP worker processes that can run at the same time.
### ✨ Improvements
- [Added a new Nginx customization template with ShortPixel Image Optimizer.](/docs/configure-custom-nginx-xcloud/)
- Improved WireGuard management with a Docker image update system and CLI support.
- Improved service restart handling and server alert monitoring across core services.
- Improved language accuracy with corrected Chinese flags and country codes.
- Improved layout, spacing, and alignment consistency across the UI.
### 🔧 Issues and Bug Fixes
- Fixed issues in staging pull and push operations related to storage validation.
- Fixed OpenLiteSpeed SSL synchronization issues for Cloudflare multi-domain certificates.
- Fixed invalid character generation in database user passwords.
- Fixed incorrect site icons appearing in header search results.
- Fixed incorrect global tag counts by applying team-based counting.
- Fixed PHP worker count inconsistencies during site cloning.
- Fixed duplicate server reboot notifications
---
# v2.3.6 - xCloud
> 🌟 Update: OpenClaw Reset (No new server needed): You can now reinstall OpenClaw from scratch on the same server using OpenClaw Reset. With one click, it
### 🔥 New Features
### 🦀 OpenClaw
🌟 [Update: OpenClaw Reset (No new server needed)](/docs/how-to-deploy-openclaw-with-xcloud/)**:** You can now reinstall OpenClaw from scratch on the same server using **OpenClaw Reset**. With one click, it **creates a backup**, **reinstalls a clean setup**, and **generates fresh credentials**.
### ✨ Improvements
- WireGuard updates now run async — no more timeouts during bulk updates
- n8n now requires Node.js 22 (upstream requirement)
- SSH password auth blocked for root on OpenClaw servers — prevents accidental lockout
- PHP Config modal now fully responsive on mobile
- Shorter SSH key display on the “Connect Existing Server” page
- Billing Type Selector & Free Plan — Server creation now supports subscription, lifetime, or free plans. Free plan users get a streamlined flow.
- Site Name Sorting — All Sites page now has clickable A-Z sort on the Site Name column.
### 🔧 Issues and Bug Fixes
- Fixed the pCloud backup deletion crash issue
- Fixed the issue with Server deletion, and now it no longer gets stuck in the deletion\_failed state
- Site sorting across multiple servers now works correctly
- Telegram bot /authenticate handles malformed input gracefully
- GitHub repo count no longer caps at 100
- Items Per Page selector fixed on Events and other tables
- Cookie banner no longer appears on error pages (404, 500, etc.)
---
# v2.3.7 - xCloud
> 🌟 OpenClaw Repair: AI-Powered OpenClaw Repair Agent is now available inside the xCloud dashboard for instant diagnosis and recovery. Run one-click AI-assisted
## **🔥 New Features**
### **🦀 OpenClaw**
**🌟 OpenClaw Repair:** AI-Powered OpenClaw Repair Agent is now available inside the xCloud dashboard for instant diagnosis and recovery. Run one-click AI-assisted health checks for the gateway – no SSH or manual debugging required.
## ✨ Improvements
📌Added temporary sudo users with 12-hour auto-expiration.
📌Added granular domain search & replace controls for updates and SSL changes.
📌Improved domain updates with real-time progress and duplicate prevention.
📌Improved UI consistency across buttons, layouts, and mobile views.
📌Improved OpenClaw Control UI domain and alias access handling.
## 🔧 Issues and Bug Fixes
📌Fixed Free Plan billing for Custom/Any, DigitalOcean, and GCP providers.
📌Fixed WordPress version display after core updates.
📌Fixed 502 errors on the Site Snapshots page.
📌Fixed an issue related to the Site Log export failures.
📌Fixed staging push issues with Patchstack.
📌Fixed resource creation restrictions on inactive packages.
📌Fixed OpenClaw server page crashes.
## 🔖 Resources
[How to Repair OpenClaw with an AI-Powered Agent With xCloud (OpenClaw Troubleshooting)](/docs/how-to-repair-openclaw-with-xcloud/)
---
# v2.3.8 - xCloud
> A brand-new Site Insights menu providing real-time analytics for PHP performance, MySQL queries, and traffic patterns directly from the site dashboard. Gives
## **🔥 New Features**
### **WordPress**
### 🌟 **[Site Insights](/docs/monitor-website-performance-with-site-insights/) – PHP, MySQL & Traffic Analytics**
A brand-new Site Insights menu providing real-time analytics for PHP performance, MySQL queries, and traffic patterns directly from the site dashboard. Gives site owners deep visibility into their application performance without needing external tools.
- **Real-Time Performance Monitoring** — Track live activity across PHP processes, MySQL queries, and website traffic directly from the xCloud dashboard.
- **Traffic & Visitor Insights** — Analyze requests, unique IPs, bots, bandwidth usage, and top URLs to understand how users and crawlers interact with your site.
- **PHP Process Visibility** — Monitor active PHP-FPM processes, detect CPU or memory-heavy scripts, and identify slow pages using PHP slow logs.
- **MySQL Database Analytics** — View active connections, running queries, query performance, slow query logs, and database health metrics.
- **Faster Troubleshooting & Optimization** — Detect slow pages, database bottlenecks, traffic spikes, and server errors quickly to keep your website fast and stable.
### **🌟 OpenClaw – Codex OAuth Token Generator & New Provider Support**
In-app OpenAI Codex OAuth token generator — ChatGPT Plus/Pro subscribers can now generate Codex OAuth tokens directly within xCloud, without needing an external service. A secure PKCE-based flow authenticates with your ChatGPT account and returns a copyable token with next-step instructions. Manual callback fallback included for browsers that block automatic redirects.
- OpenAI Codex (ChatGPT OAuth) — Connect your ChatGPT Plus/Pro subscription as an AI provider for your OpenClaw server without a separate API key
- Z.AI (GLM) — Zhipu AI’s GLM-4.7 model is now a fully active provider option (previously “coming soon”), offering a capable, cost-effective alternative for OpenClaw users
- Gateway mode fix — gateway.mode is now correctly set to local during new OpenClaw server creation, preventing gateway start failures on first setup
- Model persistence fix — Selected AI model now correctly persists after provider updates, written directly to openclaw.json so it survives gateway restarts
### **🌟 xCloud UI 2.0 – Pin/Unpin Sites & Servers**
Pin important sites and servers to keep them at the top of all list views. Pinned items show a visual badge and persist across sorting, filtering, and pagination.
### **🌟 [Cloudways Server Migration](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)**
Easily migrate your existing servers from Cloudways to xCloud with full server migration support, helping you move infrastructure smoothly without complex manual setup.
### 🌟 **Vultr Bandwidth Monitoring**
Monitor bandwidth usage for xCloud-managed Vultr servers directly from the dashboard, giving you clear visibility into network consumption and server traffic.
## ✨**Improvements**
- Better Cloudflare DNS proxy mode detection
- Enforced 4GB minimum RAM for n8n site creation and updates
- Performance score now supports a neutral state when data is unavailable
- Improved backup status logic in the auto backup tab
- Added server name and link on the delete progress page
- Hidden phpMyAdmin sites from site lists and navigation
- High CPU warning banner added on dashboard and server detail pages
- Improved OpenLiteSpeed PHP monitoring and validation
- Better handling for empty site titles during staging domain generation
- Added nginx config safety validation before reload commands
- Multiple UI/UX refinements across layouts, spacing, responsiveness, banners, and dashboard elements
## ✨**Bug Fixes**
- Fixed null reference issue in cron jobs after site deletion
- Fixed server creation failure without provider permission
- Fixed handling for Cloudflare cache rule limit exceeded errors
- Fixed null PHP version issue during PHP installation
- Fixed undefined stack issue in custom provider server creation
- Fixed missing pCloud backup file record issue
- Fixed MariaDB icon showing when no database is installed
- Fixed staging domain generation when site title is empty
- Fixed cloud provider permission bypass caused by improper null check
---
# v2.3.9 - xCloud
> Transactional emails are essential for WordPress websites. When an email quota runs out unnoticed, emails can suddenly stop sending. This update introduces
## **🔥 New Features**
### **Addon**
### **🌟[Mail Delivery Enhancements](/docs/how-to-set-up-xcloud-mail-delivery-addon/)**
Transactional emails are essential for WordPress websites. When an email quota runs out unnoticed, emails can suddenly stop sending. This update introduces smarter Mail Delivery subscription management with Auto Upgrade and 1-click Cloudflare DNS setup to keep email delivery uninterrupted.
- **Auto Upgrade Mail Deliver**y: Automatically upgrades your email plan when usage reaches the limit. xCloud will notify you when your email usage reaches 90% of your available quota. This ensures transactional emails continue sending without disruption.
- **Cloudflare One-Click DNS Verification** — If your domain uses Cloudflare integration, xCloud can automatically add and verify the required DNS records with a single click, eliminating manual DNS configuration.
- **Default Mail Delivery Provider** — Set a default provider so newly created sites automatically use your preferred email delivery configuration.
- **Email Usage Visibility** — View total email quota and available emails directly from the dashboard for better monitoring and planning.
- **Built-in SMTP Configuration** — Access SMTP credentials including username, password, SMTP server, and port directly from the dashboard.
- **API Key Access** — Manage API keys for custom integrations or external applications.
- **Clone Mail Delivery Settings** — When cloning a site, the Mail Delivery configuration is automatically copied so the cloned site inherits the same email setup.
### **🌟Multi-Port Domain Mapping for Docker Compose Sites**
Custom Docker Compose sites can now map multiple domains to different container ports. Perfect for running multiple services under separate domains from a single site.
### **🌟 PHP 8.5 Support for OpenLiteSpeed**
PHP 8.5 is now available for OpenLiteSpeed servers on Ubuntu 24. All PHP extensions are now consistently available across all PHP versions.
### **🌟GridPane OpenLiteSpeed Server Migration**
Migrate your servers from GridPane’s OpenLiteSpeed stack to xCloud. The migration wizard handles the full transfer including sites, databases, and configurations.
## ✨**Improvements**
- Optimized server provisioning by deferring non-essential packages during setup.
### ✨**Bug Fixes**
- Fixed WordPress Bulk Management issue where the Refresh All button failed when groups were collapsed or expanded.
- Fixed dropdown menus being cut off on Mail Delivery, Mailbox, and Security addon pages.
- Fixed SSH Key Editor showing system and migration keys in the sudo user SSH key selector.
- Fixed site cloning error that occurred when the PHP version was not set.
- Fixed PageSpeed Insights temporary network errors triggering false error reports.
---
# v2.4.0 - xCloud
> Cloudflare WAF rule management is now available directly inside xCloud. You can apply common WordPress security protections without creating manual rules in
## **🔥 New Features**
### **🌟** **[Cloudflare WAF Rules Integration](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/)**
Cloudflare WAF rule management is now available directly inside xCloud. You can apply common WordPress security protections without creating manual rules in the Cloudflare dashboard.
- **Cloudflare WAF Security Settings** – Configure essential WordPress protection rules directly from the xCloud dashboard.
- **Allow Good Bots & ACME Validation** – Ensures trusted crawlers and Let’s Encrypt validation requests continue to function normally.
- **Sensitive File Protection** – Blocks direct access to files that should not be publicly exposed.
- **wp-config.php Protection** – Prevents direct access to the WordPress configuration file.
- **XML-RPC Blocking** – Reduces exposure to XML-RPC abuse and brute-force attacks.
- **Author Enumeration Protection** – Blocks requests attempting to discover WordPress usernames.
Each rule is applied as a **Cloudflare WAF custom rule via API** and managed per site directly from xCloud.
### **🔄 New: Easy WordPress Rollback with Backup**
You can now roll back plugins, themes, or WordPress core in a few clicks. Just pick a version from a searchable list and revert instantly. You can also enable automatic backups before rollback.
### **⚙️ New: Auto-Tune PHP, FPM & OPcache**
Added auto-tunes for PHP, FPM, and OPcache settings based on your server RAM. It suggests optimized values instantly and lets you manage full OPcache configuration. Works seamlessly with both Nginx and OpenLiteSpeed.
## ✨**Improvements**
- Improved access log view with search, filters, and bot traffic insights
- Better default OPcache settings applied during PHP installation
- Improved disk usage with clearer stats such as total, used, and free space
- Refreshed support portal design with better visibility and layout
- Improved site controls with “Enable Site” action and quick recovery option
- General UI improvements for spacing, colors, and responsiveness
## ✨**Bug Fixes**
- Reduced false alerts from PageSpeed errors caused by external issues
- Improved retry handling for PageSpeed connection failures
- Fixed incorrect sorting and pagination issues in Site Insights
- Resolved Site Pro deployment-related errors
- Fixed Slack notification issue in vulnerability alerts
- Fixed duplicate DNS record issue in Cloudflare sync
---
# v2.4.1 - xCloud
> Create and manage HTTP header and redirect rules for WordPress sites running NGINX directly from the xCloud UI – no manual nginx config editing required.
## 🔥 New Features
### **WordPress**
#### 🌟[Site Rules](/docs/how-to-create-and-manage-site-rules/) – Manage HTTP Headers & Redirects for WordPress Sites
Create and manage HTTP header and redirect rules for WordPress sites running NGINX directly from the xCloud UI – no manual nginx config editing required.
##### **Add Custom Headers**
Define custom HTTP response headers (security headers, caching headers, CORS, etc.) for your WordPress site directly from the dashboard. Strengthen site security, control browser caching, and manage cross-origin policies without manually editing nginx configuration files.
##### **Redirects**
Set up 301/302 redirects for URLs, paths, or patterns from a clean, intuitive interface. Manage post-migration URL changes, enforce trailing slashes, or route legacy paths to new destinations — all without writing a single rewrite rule by hand.
### **🌟 [Bulk NGINX Customization](/docs/how-to-apply-bulk-nginx-customization/)**
Apply NGINX Configs Across Multiple Sites at Once on xCloud. You can now push custom NGINX configurations to multiple sites on a server in a single operation directly from the dashboard without editing each site individually. 🚀
## **🌟 [Restore Backup To Any Site On Any Server](/docs/how-to-restore-a-backup-to-another-site/)**
Seamless Cross-Site Backup Restoration Is Now Available on xCloud. You can now restore a WordPress backup directly to another existing site without rebuilding anything from scratch. This feature helps you clone live sites to staging, recover broken environments instantly, or reuse recent backups across projects. It simplifies migration workflows, reduces downtime, and gives you full control.
### **🌟 Sidebar Menu Search Is Now Available Again**
Search improves navigation speed across the xCloud dashboard with sidebar menu search. Now users can instantly find exact page locations more easily.
### 🌟**[Site-Level Cron Job Management](/docs/add-a-custom-cron-job-in-xcloud/)**
Added comprehensive **Cron Job Management** directly in the xCloud dashboard at the site level. Users can now create, edit, and delete cron jobs without SSH access, with support for custom schedules, command validation, and execution logs.
### 🌟 **[Staging Hook Scripts](/docs/how-to-create-a-staging-environment-in-xcloud/) — Post-Pull & Post-Push Automation**
Add your own Post-Pull and Post-Push scripts from the Staging Management page. These scripts run automatically after each pull or push, so you can execute custom bash commands without manual work.
Use them to deactivate sync plugins, clear caches, or apply environment-specific settings instantly.
### **✨ Improvements**
- Easy Upgrade From Free To PRO – A new global upgrade modal accessible from anywhere in the app, allowing free plan users to upgrade to the Starter plan without leaving their current page.
- Fatal Error Banners & Notifications – When a fatal PHP error occurs on a site, xCloud now shows a banner on the site dashboard. It also includes a direct link to the error logs for faster debugging. Also, users will get real-time integrated notifications channels and a dashboard.
- Improved warning banner system consistency across dashboard
- Added searchable sidebar navigation
- Improved search component flexibility
- Improved safety during site and server deletion
- Improved cross-server navigation state handling
- Improved gateway health check handling
- Improved backup deletion handling across storage types
## **✨ Bug Fixes**
- Fixed checkout security issues related to duplicate accounts and charges
- Fixed whitelabel server creation failures
- Fixed session handling on password change
- Fixed issues with salt handling during production push
- Fixed staging visibility indexing after database pull
- Fixed SSL-related deletion crashes
- Fixed cache helper CPU loop issue.
- Fixed MySQL install hang in non-interactive environments.
- Fixed PM2 startup issues on reboot for Node.js Git sites.
- Fixed mailbox banner-related issue.
---
# v2.5.0 - xCloud
> The xCloud infrastructure upgrade brings major improvements to the performance, security, and long-term stability of your dashboard. This release focuses on
## 🚀 Introducing the xCloud Infrastructure Upgrade: A Faster and More Secure Dashboard
The xCloud infrastructure upgrade brings major improvements to the performance, security, and long-term stability of your dashboard. This release focuses on faster operations, near-instant navigation, and a modern foundation that keeps xCloud reliable as it continues to grow.
### ✨ What this upgrade brings for you
- **No more waiting on slow operations** – provisioning servers, managing DNS, billing, API calls – all ~40% faster on average
- **Pages load before you expect them to** – xCloud now prefetches the next page before you click, so navigation feels instant
- **Dashboards show content first** – no more staring at a loading screen while everything catches up. Your content appears immediately; heavy data loads behind the scenes
- **Better security** – every package is patched and up to date, with fewer dependencies, meaning fewer things that can go wrong
---
# v2.5.2 - xCloud
> Deploy your own self-improving AI agent with persistent memory, auto-built skills, and multi-platform messaging — fully managed on xCloud. No terminal or
## New Features
### 🆕 [Introducing Hermes Agent Hosting on xCloud](/docs/how-to-deploy-hermes-agent-with-xcloud/)
Deploy your own self-improving AI agent with persistent memory, auto-built skills, and multi-platform messaging — fully managed on xCloud. No terminal or DevOps experience needed.
Hermes Agent remembers you across sessions, builds new skills as it works, and runs 24/7 on autopilot. You sign up, we deploy, you start chatting.
- Persistent memory – remembers everything across sessions, no re-explaining needed.
- Self-building skills – gets smarter the longer it runs by learning from every task.
- Multi-platform messaging – manage from Telegram, Discord, Slack, WhatsApp & more.
- Built-in scheduling for reports, monitoring, and automations.
- 40+ tools out of the box – web search, browser automation, code execution, vision, and more.
🌟 With xCloud, you get one-click deployment, built-in Telegram support, auto SSL, daily backups, managed updates, and security – all in one place.
👉 Visit the [**page**](/paperclip-hosting/) for more details.
## **🐛 Improvements**
📌 Added a combined stack called Agentic for OpenClaw, Paperclip, and Hermes Agent for xCloud Managed Servers.
📌 Added Cloudflare Security Settings support for OpenLiteSpeed sites
## **🐛 Bug Fixes**
📌 Fixed an issue related to Nginx regeneration
📌 Fixed incorrect commit details showing in GIT deployment history
📌 Fixed deployment issues for GitHub auto-deploys
📌 Fixed SSL retry options for failed certificates
📌 Fixed silent failures with Disable Nginx Regeneration across multiple site actions
📌 Fixed SSL-related issues affecting failed certificates, multisite subdomains, and staging/live sites
---
# v2.5.3 - xCloud
> Security Release - 🔒 CVE-2026-31431 ("Copy Fail") Mitigation AppliedAutomatically disables the vulnerable algif_aead Linux kernel module across all connected
**Security Release** – 🔒 CVE-2026-31431 (“Copy Fail”) Mitigation Applied
Automatically disables the vulnerable algif\_aead Linux kernel module across all connected servers — both xCloud-managed and non-managed — via the existing security patch system. The module is permanently blacklisted, safely unloaded if running, and verified blocked without impacting older or custom server configurations. No action required from your side.
---
# v2.5.6 - xCloud
> The xCloud MailBox Addon is now a complete business productivity suite — not just email anymore. Create professional email addresses with your own domain
## 🔥 New Features
### **🚀 [xCloud MailBox](/docs/how-to-set-up-xcloud-mailbox-addon/) – Free Professional Mailbox With Advanced Features**
The xCloud MailBox Addon is now a complete business productivity suite — not just email anymore. Create professional email addresses with your own domain (e.g., yourname@yourbusiness.com), build trust with customers, and manage everything from one place.
- **Free Mailbox for xCloud Server/Provider Users** — Every unique domain hosted on an xCloud Managed or Provider Server now gets one free professional mailbox with the full suite included. No setup fee, no commitment.
- **Professional Email Features** — Threaded conversations, unlimited email signatures, built-in rules engine for auto-filtering and tagging, spam and phishing protection, unified inbox for all accounts, IMAP & POP client support, aliases, mail forwarding, catch-all addresses, mail templates, schedule send, undo send, snooze, and follow-up reminders.
- **Full Business Workspace** — Built-in calendar with smart scheduling, RSVP, recurring events, and resource booking. Shared task lists with due dates, reminders, priority flags, and team collaboration. Personal address book with smart autocomplete. Dark mode and app access on any device.
- **Upgrade to Unlock Even More** — Cloud Drive with file sharing, version history, WebDAV, and sync clients. Built-in document, spreadsheet, and presentation editors with real-time collaboration. Shared contacts across your organization. Read receipts and follow-up reminders.
- **Enterprise-Grade Security** — Two-factor authentication, WebAuthn hardware key support, end-to-end encryption, and premium antivirus, antispam, and antiphishing protection.
- **Plans Starting at Just $1/mo** — 8GB at $1/mo, 25GB at $2.5/mo, 50GB at $5/mo, and 80GB at $8/mo with support for 25+ languages.
- **Easy Migration from Legacy Mailbox** — Existing users can migrate seamlessly to the new mailbox using the built-in migration tool. Move all emails in bulk per domain, keep the same pricing and billing, and unlock more features at no additional cost.
- **AI-Powered Email Productivity** — Auto-generate email replies and subject lines, summarize long email threads in seconds, smart classification to sort your inbox automatically, automate routine tasks with Smart Tasks, and text-to-speech for emails read aloud.
## **✨** Improvements
- Cloudflare integration no longer requires the Origin CA Key, so new Cloudflare users can connect without it.
- Users now see AI-powered answer suggestions while creating support tickets.
## 🐛 Bug Fixes
- Fixed site environment stays as Production when the domain update fails during the demo-to-live transition.
- Fixed Authorization header being dropped on OpenLiteSpeed Node-app reverse proxy.
- Fixed an issue related to the MariaDB database settings.
- Billing accuracy and invoice reconciliation improvements
- Internal admin reporting and MRR visibility enhancements
- Missing bill detection and recovery workflow improvements
- Server billing calculation fixes for resize and plan changes
- Provider data sync improvements for Vultr backups, server size, and billing status
- Mailbox migration backend improvements, including migration flow, plan handling, and provider architecture
- Multi-provider mailbox architecture improvements with OX Mail integration
- Abuse report handling improvements with better queue processing
- WordPress vulnerability scanning performance improvements
- White-label product picker and storage information improvements
- Server SSH authentication state handling improvements
- Domain update rollback improvements for safer failed updates
- Internal API callback error response improvements
- Meta Ads purchase tracking and deduplication improvements
- Internal report access control and permission handling improvements
- Site deletion and PHP-FPM restart safety improvements
- GitHub release and cache handling improvements
- Internal test coverage and rollback test improvements
- Various UI polish, route guards, loader states, and admin action improvements
## 🔖 Resources
- [How to Set Up xCloud MailBox Addon](/docs/how-to-set-up-xcloud-mailbox-addon/)
- [How to Configure Your Email Client with xCloud Mailbox Addon](/docs/configure-email-client-with-mailbox-addon-xcloud/)
- [How to Migrate Emails From Legacy Mailbox To The New xCloud MailBox](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
---
# v2.5.9 - xCloud
> Manage HTTP Headers & Redirects for WordPress Sites. Create and manage HTTP headers and redirect rules for WordPress sites running OLS directly from the
## 🔥 New Features
### 🌟 [Introduced Site Rules For OLS Server](/docs/how-to-create-and-manage-site-rules/)
Manage HTTP Headers & Redirects for WordPress Sites. Create and manage HTTP headers and redirect rules for WordPress sites running OLS directly from the xCloud dashboard.
- **Add Custom Headers**: Define custom HTTP response headers (security headers, caching headers, CORS, etc.) for your WordPress site directly from the dashboard. Strengthen site security, control browser caching, and manage cross-origin policies without manually editing nginx configuration files.
- **Redirects:** Set up 301/302 redirects for URLs, paths, or patterns from a clean, intuitive interface. Manage post-migration URL changes, enforce trailing slashes, or route legacy paths to new destinations — all without writing a single rewrite rule by hand.
### ⚡ Improvements
✅ Patchstack now tracks each site individually for more reliable scans, updates, and SSO.
✅ Vulnerability counts now match across all pages, “Last Scanned” is back, and you’ll get instant alerts on new threats.
### 🐛 Bug Fixes
🔧 Fixed Cloudflare WAF rule that was blocking Googlebot and breaking SEO on 100+ sites.
🔧 Fixed Push-to-Deploy toggle so disabling it actually stops deployments.
🔧 Fixed 502 errors on Node.js, N8N, and Uptime Kuma sites after re-enable.
🔧 Fixed misleading “select at least one database” error when editing database users.
🔧 Fixed orphaned staging sites left behind when deleting a production site.
🔧 Fixed backup table to show the real total instead of just the current page count.
---
# v2.6.0 - xCloud
> Build Trust With Clear Website Maintenance Reports for Your Clients. Generate professional, fully branded site reports for your clients directly from the
## 🔥 New Features
### 🌟 [Client Reports For Professional Branded Website Maintenance Reports](/docs/wordpress-website-maintenance-reports-in-xcloud/)
Build Trust With Clear Website Maintenance Reports for Your Clients. Generate professional, fully branded site reports for your clients directly from the xCloud dashboard in just a few clicks.
- **Comprehensive Site Reports:** Generate reports covering performance, security, backups, updates, and traffic all in one place. Choose your reporting period and customize which sections to include or exclude.
- **Full Branding Control:** Add your own logo, company name, colors, and custom intro/outro messages. Your clients see your brand, not ours.
- **Custom Development Logging:** Log custom development work you delivered during the reporting period so clients see exactly what they’re paying for.
- **Report Preview & History:** Preview reports live before generating to avoid surprises. Access your full report history with download and delete options anytime.
- **Reports Include:** App details and SSL certificate status, WordPress core and plugin/theme update logs, backup summary, security and vulnerability status, snapshots, PageSpeed Insights scores (mobile and desktop), traffic statistics, and custom development entries with hours and descriptions.
## **✨** Improvements
- Improved dashboard workflows for a smoother site and server management experience.
- Enhanced several user interface areas to make key information easier to find and understand.
- Improved overall platform stability and reliability across common actions.
## **✨** Bug Fixes
- Fixed issues affecting some site and server management workflows.
- Resolved minor UI inconsistencies across the dashboard.
- Improved error handling for a more reliable user experience.
---
# v2.6.1 - xCloud
> Reset your server to a day-one clean state without decommissioning, re-provisioning, or starting a new billing cycle. One click resets the stack while your
## 🚀 New Feature
### 🌟 [Introducing Server Rebuild on xCloud](/docs/how-to-rebuild-a-server-with-xcloud/) – One Click to a Fresh Server, Same IP & Billing
Reset your server to a day-one clean state without decommissioning, re-provisioning, or starting a new billing cycle. One click resets the stack while your IP, DNS records, firewall rules, and invoice stay exactly where they are.
- **Switch your web stack:** Choose between NGINX, OpenLiteSpeed, Docker + Nginx, or any of our Agentic stacks (OpenClaw, Paperclip, Hermes) — swap your entire web environment in a single action.
- **Change your database:** Move to MySQL 8.4, MariaDB 11, depending on what your new stack needs.
- **Keep the same public IP:** DNS records, firewall rules, and monitoring URLs stay intact, so there’s nothing to reconfigure on the network side.
- **Keep the same billing cycle:** No new server, no new invoice, no prorated charges, your existing subscription continues uninterrupted.
- **Same security hardening, fresh disk:** SSL, SSH, and 7G-firewall come back automatically on the rebuilt server, so you start clean without losing your baseline protection.
## ⚡ Improvements
- Bills Payment page now displays detailed invoices above the billing history for faster reference.
- Mailbox now correctly shows whether SMTP is available for the user’s plan.
## 🐛 Bug Fixes
- Fixed stale database information appearing after deleting databases or users.
- Fixed renewal billing issues affecting white-label subscriptions.
---
# v2.6.3 - xCloud
> Find anything in xCloud instantly. Press Cmd+K to search across all your servers, sites, and feature pages from anywhere in the dashboard. When you’re on a
## 🚀 New Feature
## Global Search (Cmd+K / Ctrl+K)
Find anything in xCloud instantly. Press Cmd+K to search across all your servers, sites, and feature pages from anywhere in the dashboard. When you’re on a server page, the search automatically scopes to that server’s sites.
You’ll also see smart hints showing which features are available based on your server stack and site type, your recent searches, and provider and site-type logos to help you spot results faster. The old sidebar search has been retired, the new search palette replaces it. Keyboard and accessibility behavior has been polished too (focus handling, Esc to close, scroll-lock).
## Improvements:
- Guided SSH Key Setup Setting up SSH keys is now much easier. A new step-by-step guided UI walks you through the process during the sudo/SSH flow, so first-time setup is smoother and less error-prone.
## 🐛 Bug Fixes
- Fixed an issue with the Hostinger integration
- Fixed an issue with the domain update feature
- Fixed issues with NGINX packages
---
# v2.6.4 - xCloud
> Installing and managing PHP extensions no longer requires SSH access or command-line work. xCloud now lets you view, install, and remove PHP extensions for
## 🔥 New Features
## 🌟 [**PHP Extensions Management**](/docs/how-to-manage-php-extensions-with-xcloud/) – Add PHP Extensions With Clicks, Not Code
Installing and managing PHP extensions no longer requires SSH access or command-line work. xCloud now lets you view, install, and remove PHP extensions for every PHP version directly from the dashboard.
- One-click installation for supported extensions including APCu, Xdebug, LDAP, YAML, and more
- One-click removal of extensions you no longer need
- Dedicated Installed Extensions and Available Extensions sections with extension counts
- Real-time status indicators for every extension
- Built-in protection for core PHP extensions to prevent accidental removal
- Confirmation prompts before extension removal for safer management
- Unified PHP Configuration and Extensions interface for a cleaner management experience
## ✨ Improvements
- Reseller Panel: Resellers can now create products specifically with stacks (NGINX/OLS) or with AI Agents (OpenClaw, Hermes)
- Improved global search result prioritization and navigation experience.
- Added monitoring data source filtering across monitoring views.
## **✨** Bug Fixes
- Fixed Cloudflare redirect SSL issues on multi-domain redirect sites.
- Enhanced white-label stack selection and product management.
---
# v2.6.5 - xCloud
> Take full control of your servers and sites through a modern RESTful API. Automate repetitive tasks, scale your infrastructure, and build directly on top of
## 🔥 New Features
#### 🌟 [xCloud API — Develop, Integrate, and Automate Programmatically](/docs/how-to-access-the-xcloud-api/)
Take full control of your servers and sites through a modern RESTful API. Automate repetitive tasks, scale your infrastructure, and build directly on top of xCloud, all with enterprise-grade security. Create a token in your dashboard settings, set the permissions you need, and start building in about a minute.
- **Auto-provision servers** through the API with no dashboard required.
- **Deploy fully configured sites** in a single API call.
- **Manage SSH and sudo users programmatically**, adding or removing access on demand.
- **Build CI/CD pipelines, client portals, SaaS tools, and internal dashboards** on top of xCloud.
- **Pull live server and site data** into any system you already use.
- **Enterprise-grade security** with token-based, permission-scoped access on every request.
We will continue to expand API capabilities by introducing additional endpoints on a regular basis.
## ✨ Improvements & Bug Fixes
- Improved the payment flow so customers can now securely save cards and pay invoices directly inside xCloud using embedded Stripe payments, with 3D Secure support for future renewals.
- The limit of the additional domain has now been increased per team with Cloudflare.
- Improved MySQL auto-healing so it no longer runs when the server is not in the correct state.
- Fixed an issue related to the Hermes events feed and Status page.
- Fixed MySQL repeatedly trying to repair itself during problems.
- Fixed an activity issue where the site deletion was not showing in the activity log.
- Resolved issues with the Hermes dashboard events feed disconnecting and reduced unnecessary task/poll requests on the Status page.
- Fixed: Improved Vultr managed server creation errors by showing a clear message instead of the unclear “Invalid plan chosen” error.
- Fixed: Local backup auto-delete now self-heals correctly when needed.
- Added support for Hermes live chat with Hermes Agents.
## 🔖 Resources
- [**How to Access the xCloud API**](/docs/how-to-access-the-xcloud-api/)
- [**xCloud API Documentation**](http://xcloud.host/docs/xcloud-api)
---
# v2.6.7 - xCloud
> You can now add Git integration to an existing WordPress or Custom PHP site directly from the site's Git tab, in a single flow. Previously, putting an
## 🔥 New Features
### 🌟[**Git Integration for Existing WordPress & Custom PHP Sites**](/docs/set-up-git-integration-for-existing-wordpress-or-php-site/)
You can now add Git integration to an existing WordPress or Custom PHP site directly from the site’s Git tab, in a single flow. Previously, putting an existing site under Git meant redeploying the project from scratch: create a repository, push your files, set up a deploy key, and get it live.
Now you pick a connected GitHub provider, confirm the prefilled repository name, and review the generated .gitignore. xCloud then creates a private repository, pushes your current site files as the first commit, and configures the deploy key and webhook automatically. Push-to-deploy is available the moment setup completes, with no manual SSH or Git wiring.
### What is included:
✅ Add Git to an existing WordPress or Custom PHP site without redeploying it
✅ Skip the manual setup of repositories, deploy keys, and webhooks
✅ Start from a clean codebase, with sensitive and unnecessary files ignored for you
✅ Get a private repository with your site files captured from the first commit
✅ Use push-to-deploy as soon as setup finishes
Bring existing WordPress and Custom PHP sites under Git control with a single click on xCloud now in just a few clicks. 🚀
## 🌟 [**Laravel Site Cloning**](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Cloning is no longer just for WordPress. Spin up a copy of any Laravel site for staging, testing, or a new environment, without rebuilding it from scratch.
If you have deployed a Laravel site using Git from xCloud, the clone brings your Git settings along with it, so push-to-deploy is ready to go on the new copy. Each clone also gets its own deploy key instead of sharing the original one, keeping your setup clean and secure. Clone, test, and ship with confidence. 🚀
## **🌟 [Hermes Workspace Setup Support](/docs/how-to-set-up-hermes-workspace-with-xcloud/)**
We’ve added Hermes Workspace setup support, including workspace connection/self-hosting flow, token generation, Docker UI support, and optional domain/SSL setup where available.
## ✨Improvements
- Added a dedicated AI Website Builder card for Site.pro sites in Site Overview.
- Added Hermes Workspace setup support.
- Added Laravel site cloning and full server migration support.
- Improved global search with recent servers and sites.
- Improved Server Logs selection workflow.
## 🐛Bug Fixes
- Fixed site deletion + web terminal output related issue.
- Improved Security Analytics to reduce false attack detections and clarify insights.
- Fixed WordPress scan crashes caused by overly long plugin or theme titles.
- Fixed same-server cloning issues that could affect original site database safety.
- Fixed Hermes Codex OAuth token saving and refresh issues.
- Fixed robots.txt handling for proxied Node.js SSR apps.
- Improved client report generation to reduce pending report delays.
- Fixed OpenLiteSpeed PHP worker updates.
---
# v2.6.8 - xCloud
> ✨ Improvements Added Dedicated Server Plans on xCloud Managed Server – Added new General Purpose optimized plans when provisioning dedicated servers, giving
## ✨ Improvements
- **Added Dedicated Server Plans** on xCloud Managed Server – Added new General Purpose optimized plans when provisioning dedicated servers, giving you more sizing options.
- Improved Codex integration to set up the agent harness automatically on connection.
- Improved deployment reliability by ignoring stale tasks that interfered with the deploy guard.
- Patched a security vulnerability (CVE-2026-46331) for stronger server protection.
---
# v2.6.9 - xCloud
> Take full control of your servers and sites by describing what you want in plain language, and let the skills handle the xCloud Public API calls in the
## 🔥 New Features
## 🌟 [xCloud AI Agent Skills](/docs/install-and-use-xcloud-ai-agent-skills/): Manage Your Servers and Sites With Plain Language
Take full control of your servers and sites by describing what you want in plain language, and let the skills handle the xCloud Public API calls in the background with enterprise-grade security. The skills are agent-agnostic: they work with any MCP-compatible AI coding agent, including Claude, Codex, Grok, and others. Create a token in your dashboard settings, install the skills in your agent, and start in about a minute.
- Create a fully configured site with a single prompt, no dashboard required.
- Check the status of any server or site with a single prompt.
- Manage servers, PHP versions, databases, and firewall rules in plain language, on demand.
- Run WordPress updates, vulnerability scans, SSL setup, and site backups just by asking.
- Pull live server and site data into workflows you already use.
- Included with your xCloud account at no additional cost.
- Enterprise-grade security: token-based, permission-scoped access on every request.
## ✨ Improvements
- Improved flash message appearance and timing for cleaner, less distracting alerts.
- Streamlined setup for agentic-only teams by hiding manual site creation.
## 🐛 Bug Fixes
- Fixed an issue related to the support tickets page.
- Fixed the client reports logo issue, which was not displaying properly.
- Fixed server monitoring so CPU usage now shows accurately.
- Fixed an error that could cause the team management page to fail to load.
---
# v2.7.0 - xCloud
> xCloud v2.7.0 brings a more powerful AI Bot Blocker, stronger backup reliability, smoother n8n provisioning, and several improvements across site management,
xCloud v2.7.0 brings a more powerful AI Bot Blocker, stronger backup reliability, smoother n8n provisioning, and several improvements across site management, billing, search, and documentation.
## 🔥 New Features
### [🆕 AI Bot Blocker Management Got Smarter](/docs/enable-ai-bot-blocker-in-xcloud/)
We’ve upgraded the AI Bot Blocker from a simple on/off option into a full management experience for your sites. You can now view the default AI bot blocklist, allow selected bots, and add custom bots to block directly from the Web Server Security page.
Major updates are:
- View the full built-in AI bot blocklist.
- Add bots to an allowlist when you want to let specific AI crawlers access your site.
- Add custom bots to your own blocklist.
- Search and select multiple bots at once for faster management.
- Works with both Nginx and OpenLiteSpeed sites.
This gives you more control over how AI crawlers interact with your websites while keeping the default protection easy to manage.
## ⚡ Improvements
- Added a new Custom Nginx \`main\_location\` option, allowing advanced users to add custom rules inside the main PHP app location block.
- Improved global search so sites can be found even when you paste a full URL like \`https://example.com/\`, not just the plain domain.
- Improved several UI areas, including profile avatar visibility, server creation cards, mobile layouts, analytics controls, and white-label product editing.
- API documentation has been standardized with OpenAPI YAML and Scalar for a cleaner, more consistent developer documentation experience.
## 🐛 Bug Fixes
- Fixed an issue where the dashboard could show incorrect or stale “Next Backup” times. Backup schedules are now calculated from the active site-level backup settings.
- Fixed inherited backup exclude paths for newly created and migrated sites, so backup exclusions are carried over correctly.
- Fixed an issue where sites using remote backups could incorrectly appear as active under the Local Backup tab.
- Improved backup delete handling so xCloud now reconciles backup records correctly even when the remote storage is already clean.
- Improved n8n provisioning by moving long installation tasks into the long-running provisioning flow, reducing queue timeout issues.
- Hardened n8n PM2 startup and update handling to reduce recurring 502/503 errors after updates.
- Added proxy trust configuration for n8n behind the xCloud Nginx reverse proxy.
- Cleaned up fallback n8n PM2 configuration handling.
- Fixed WordPress staging clone failures caused by file ownership issues after \`rsync\`.
- Improved domain update handling so partially completed server rename states can be detected, rolled back, or resumed more safely.
- Fixed duplicate white-label renewal invoices when users retried failed “Renew Now” attempts.
- Improved the Managed Server “Continue Setup” flow so users who already purchased eligible plans can continue deployment correctly.
- Added stronger validation for cloud provider credential labels to prevent invalid provider saves.
- Enterprise and Public API documentation now use a more consistent OpenAPI YAML structure.
---
# v2.7.1 - xCloud
> Paste a repository URL and xCloud takes it from there. It reads the repo, works out what it is, sets everything up, and deploys it. No pipelines to write, no
## 🔥 New Features
### 🌟 [**One-Click Deploy From Git**](/docs/deploy-git-projects-in-one-click-with-xcloud/): The Fastest Way to Ship Any Project on xCloud
Paste a repository URL and xCloud takes it from there. It reads the repo, works out what it is, sets everything up, and deploys it. No pipelines to write, no app type to pick, no CLI tools to install. WordPress, Laravel, Node.js, Docker, or anything else — the same flow for all of your Git projects, live in under a minute.
- Stack detected automatically from your repository.
- Branch is detected automatically.
- AI-generated deploy scripts, created directly from the repository’s own documentation.
- Environment variables filled automatically from your repo’s sample file, with secrets generated safely on the server.
- Domains and SSL are configured automatically, with a domain per service, staging or live.
- One flow for every project type. Setup takes seconds instead of hours.
## 🐞 Bug Fixes
- Restored automatic Redis installation during new server provisioning.
- Fixed provisioning failures for database names containing hyphens.
- Improved WordPress installation reliability with verified ZIP downloads.
- Fixed incorrect Webhook Inactive status reporting on Hermes servers.
---
# v2.7.2.2 - xCloud
> xCloud v2.7.2.2 adds GPT-5.6 support for AI agents and improves deployment, monitoring, WordPress update, and dashboard reliability.
xCloud v2.7.2.2 adds GPT-5.6 support for AI agents and improves deployment, monitoring, WordPress update, and dashboard reliability.
## 🔥 New Features
### 🆕 GPT-5.6 Support for AI Agents
You can now use GPT-5.6 with Hermes, OpenClaw, and Paperclip on xCloud.
- GPT-5.6 Sol, Terra, and Luna models are now available where supported.
- Agent provider settings now make it easier to use the recommended default model or keep a custom model selection.
## ⚡ Improvements
- Improved Git deployments for Laravel and Custom PHP projects. You can configure the web root more easily, and custom environment variables are saved correctly during deployment.
- Improved WordPress update information so the Updates page refreshes the current version and last checked time more accurately.
- Improved site icons in the dashboard with more reliable favicon handling and fallbacks.
- Improved monitoring reliability for newly provisioned servers, even before the first site has been created.
## 🐛 Bug Fixes
- Fixed an issue that could cause temporary network interruptions to trigger false server-disconnected alerts. xCloud now rechecks the server before sending an alert.
- Fixed agent service restart actions for Hermes, OpenClaw, Paperclip, and white-label agent services.
- Fixed an issue that could cause errors when working with sites linked to unavailable or deleted servers.
- Fixed a backup settings issue that could affect backup information loading in some cases.
- Fixed issue with server location display
No action is required. These improvements and fixes are being applied automatically.
---
# v2.7.2 - xCloud
> The old source we used for Nginx is out of date and no longer gets new versions. Now you can move your servers to the official Nginx with a single click. Just
## 🔥 New Features
The old source we used for Nginx is out of date and no longer gets new versions. Now you can move your servers to the official Nginx with a single click. Just click on the ‘Upgrade Nginx’ button from the banner of your dashboard and xCloud does the rest in the background. Your sites stay online the whole time. If something goes wrong, it undoes the change by itself, so it’s completely safe to try. New servers already come with the official Nginx built in.
- New servers use the official Nginx, with all the features included.
- Your sites stay online during the whole upgrade.
- If the upgrade fails, it rolls back on its own, so nothing breaks.
## 🐞 Bug Fixes
- Fixed an issue related to the server deletion failed.
---
# v2.7.3 - xCloud
> xCloud v2.7.3 brings a smoother sign-in and checkout experience, stronger multisite wildcard SSL handling, more flexible Custom Nginx controls, and
xCloud v2.7.3 brings a smoother sign-in and checkout experience, stronger multisite wildcard SSL handling, more flexible Custom Nginx controls, and reliability improvements across the platform.
## 🔥 New Features
### Social Login and Unified Checkout
Sign in with your Google or GitHub account, manage connected accounts, and complete purchases through a simpler unified checkout flow.
📌 Select the stack and product options you need while checking out.
📌 Purchase multiple eligible items in a single checkout.
### Custom Nginx Toggle
Enable or disable an individual Custom Nginx rule without deleting its configuration. Disabled rules keep their settings, so they can be re-enabled whenever needed.
### Region-Based Vultr Plan Availability
When creating a Vultr server, xCloud now checks plan availability for your selected region before provisioning begins.
This helps identify unavailable plans earlier in the server-creation process.
## **🐛 Improvements**
📌 Improved managed wildcard SSL issuance for WordPress multisite subdomain networks, with clearer DNS validation and certificate coverage checks.
📌 Improved the Site Git settings page with clearer action hierarchy.
📌 Updated the web and SSH terminal welcome banner for more accurate colour rendering.
## 🐛 Bug Fixes
📌 Fixed an issue where Magic Login could fail for imported or connected WordPress sites without a configured admin username.
📌 Fixed Magic Login compatibility with the 8G Firewall on OpenLiteSpeed servers.
📌 Fixed an issue where disabling a site could overwrite a customised maintenance page.
📌 Fixed File Manager edit links for filenames containing spaces or special characters.
📌 Fixed phpMyAdmin disable failures so they remain visible and can be retried.
📌 Fixed notification settings so disconnected integration channels clearly show that they must be connected first.
📌 Fixed cases where an unavailable or stale Nginx installation state could affect upgrade handling.
📌 Improved the billing selector layout for purchased packages.
---
# xCloud v2.7.4: Buzz OneClick App & App Templates
> Deploy Buzz on xCloud with the new OneClick App Templates for Docker Nginx servers. Get guided setup, secure WebSockets, and persistent data.
**xCloud v2.7.4 introduces the Buzz OneClick App and OneClick App Templates**, making it easier to deploy supported self-hosted applications on Docker Nginx servers. You can now run your own private Buzz workspace on xCloud with a guided setup, secure WebSockets, and persistent application data.
## 🔥 New Features
### **OneClick App Templates** with **13+ new Apps**
xCloud’s new OneClick App Templates provide a guided way to deploy supported Docker and Node.js applications. xCloud manages the required credentials, ports, configuration values, and template version used during installation.
📌 Install supported applications through a guided setup flow instead of manually preparing Docker Compose files.
📌 Keep installations more predictable with template versions pinned during setup.
📌 Generate and manage required credentials, ports, and configuration values during installation.
### **[Buzz OneClick App Deployment](/docs/how-to-install-buzz-with-xcloud-one-click-apps/)**
You can now deploy [Buzz](https://buzz.xyz) as a OneClick application on compatible Docker Nginx servers. Buzz is a self-hosted workspace where teams and AI agents can collaborate in shared rooms, work with Git, and communicate through signed events.
## Buzz OneClick App Setup on xCloud
📌 Launch your own Buzz relay with a custom domain and secure WebSocket connection.
📌 Connect through the Buzz desktop app or CLI using your own `wss://` relay URL.
📌 Run Buzz with PostgreSQL, Redis, and media storage configured automatically.
📌 Start with a private, membership-controlled relay using your supplied Nostr public key as the owner.
📌 Keep relay data, media uploads, Git repositories, and application data on persistent storage.
The Buzz OneClick App is available for compatible Docker Nginx servers in xCloud. Choose the Buzz template, connect a custom domain, provide the relay owner public key, and let xCloud prepare the required application services and configuration.
### What does the Buzz OneClick App install?
The Buzz template configures the Buzz workspace with PostgreSQL, Redis, media storage, persistent volumes, and WebSocket-ready Nginx proxy handling so teams and AI agents can collaborate through a secure relay.
## 🐛 Improvements
📌 OneClick applications now include controls to start, stop, restart, redeploy, and manage environment configuration after installation.
📌 Improved compatibility checks help prevent templates from being installed on unsupported server stacks.
📌 WebSocket-ready proxy handling makes applications such as Buzz available securely through your xCloud domain.
## 🐛 Bug Fixes
📌 Improved reliability when WordPress updates time out, so sites are less likely to remain stuck in an in-progress update state.
📌 Improved n8n update handling to reduce the risk of an incomplete application replacement.
📌 Fixed billing and mailbox recovery cases so paid services and billing details are reflected more accurately.
---
# v2.7.5 - xCloud
> 🎉 xCloud MCP is here. Connect Claude, Claude Code, Cursor, ChatGPT, Gemini, VS Code, Windsurf, or any MCP-compatible client to your xCloud account and manage
## 🔥 New Features
### [xCloud MCP](https://xcloud.host/docs/how-to-connect-xcloud-mcp-to-ai-agent/)
🎉 xCloud MCP is here. Connect Claude, Claude Code, Cursor, ChatGPT, Gemini, VS Code, Windsurf, or any MCP-compatible client to your xCloud account and manage your servers and sites through a conversation instead of the dashboard.
Describe what you want in plain language and your AI assistant handles it against your real infrastructure:
- Create sites and spin up new environments from a single prompt.
- Deploy without leaving the editor or chat you are already working in.
- Ask why a deploy failed and get pointed to the actual cause.
- Compare staging and production to see what is different.
- Check PHP versions, server load, and site status across everything you run.
- Manage databases, SSL, and server resources without opening a tab.
## ✨ Improvements
- Site User is now visible and editable during the Deploy via Git workflow.
- Renamed **Automatic Delete** to **Backup Retention** for clearer backup management.
## 🐛 Bug Fixes
- Fixed an issue related to the double-clicking **Deploy** could create duplicate sites for the same domain.
- Fixed OpenLiteSpeed **www** redirects to correctly return HTTP 301 responses.
- Fixed deployments stuck related issue.
- Fixed team switching so servers and sites update immediately without requiring a page refresh.
- Fixed Codex OAuth login compatibility for the valid OpenAI accounts.
---
# v2.7.6 - xCloud
> Cloudflare Enterprise is now available on xCloud as a per-domain add-on. You get the same enterprise network the largest brands run on, fully managed by
## **🔥 New Features**
### [**Cloudflare Enterprise**](https://xcloud.host/docs/how-to-activate-the-cloudflare-enterprise-addon/)
Cloudflare Enterprise is now available on xCloud as a per-domain add-on. You get the same enterprise network the largest brands run on, fully managed by xCloud, for a flat $5 per domain, per month. No Cloudflare account, no enterprise contract, and no DNS work on your side.
Turn it on per domain from Addons → Cloudflare Enterprise, or directly from a site. xCloud handles the zone setup, the certificate, and the routing.
- Serve your site from Cloudflare’s global network across 330+ locations.
- Pay a flat $5 per domain, per month, with no traffic-based charges.
- Get managed SSL on every domain you enable.
- Full page caching at the edge, so visitors are served from the location closest to them.
- Early Hints, so browsers start loading assets before the page response arrives.
- Automatic image optimization, in lossy or lossless mode.
- One-click cache purge across the whole network.
- Enterprise WAF that blocks SQL injection, XSS, and zero-day attempts in real time.
- Advanced DDoS protection at the edge, before traffic reaches your server.
- Browser Integrity Check and one-click Under Attack Mode for when you are being targeted.
- Crawler blocking to stop AI bots from scraping your content.
- Real-time request and data transfer analytics, including Cloudflare-served versus origin traffic.
- Cache performance and top countries, so you can see where your traffic comes from and how much of it never touches your server.
## **🌟 30+ One Click Apps: Self-Host Your Whole Stack in a Couple of Clicks**
We’ve added a big batch of new apps to xCloud One Click Apps, so you can now self-host search, analytics, docs, BI, automation, passwords, media, Git, and more, all in a couple of clicks. Pick an app and xCloud handles the setup, SSL, and config for you. With this release, we now support 30+ one click apps.
## **🆕 New Apps**
1. **Redis** In-memory data store for caching, queues, and fast key-value workloads.
2. **Moodle** Open-source LMS to build courses, run quizzes, and track grades on your server.
3. **BookStack** Open-source wiki and documentation platform for team knowledge bases, SOPs, and internal docs.
4. **Excalidraw** Virtual whiteboard for hand-drawn-style diagrams, wireframes, and flowcharts. Runs entirely in the browser — fast, private, and works offline once loaded.
5. **Metabase** Open-source business intelligence — connect your databases, ask questions in a friendly UI or SQL, and build shareable dashboards. No per-seat pricing, your data stays on your server.
6. **Matomo** Privacy-first, self-hosted web analytics with full data ownership, visitor insights, goals, campaigns, and tag management.
7. **Vaultwarden** Lightweight, Bitwarden-compatible password manager server. Works with all official Bitwarden apps and browser extensions.
8. **Gitea** Lightweight self-hosted Git forge with repos, pull requests, issues, packages, and Actions-compatible CI workflows. Ships SQLite + HTTPS cloning out of the box.
9. **Meilisearch** Lightning-fast, typo-tolerant search engine — an open-source Algolia alternative for apps and websites.
10. **Odoo Community** Open-source business suite with modular CRM, sales, invoicing, inventory, project, website, and e-commerce apps.
11. **Qdrant** Vector database and similarity-search engine for semantic search, recommendations, embeddings, and RAG. Includes REST APIs and a web dashboard.
12. **Plane** Open-source project management for issues, cycles, modules, pages, and team workspaces.
13. **Paperless-ngx** Open-source document management with OCR, full-text search, tagging, and automated organization.
14. **Listmonk** High-performance, self-hosted newsletter and mailing-list manager with subscriber segmentation, campaign analytics, templates, and a REST API.
15. **Keycloak** Open-source identity and access management with single sign-on, OpenID Connect, OAuth 2.0, SAML, user federation, and multi-factor authentication.
16. **Jellyfin** Free, open-source media server for organizing and streaming movies, TV, music, photos, and live TV to web, mobile, and TV clients — no subscriptions or premium gates.
17. **Hoppscotch** Open-source API development workspace for REST, GraphQL, realtime protocols, collections, environments, and teams.
18. **draw.io** Private browser-based diagramming for flowcharts, architecture diagrams, UML, network maps, and more. Stateless server with files saved or exported by the user.
19. **Discourse** Open-source community platform for discussions, support forums, knowledge sharing, and long-form conversations.
20. **Databasus** Self-hosted database backup console for PostgreSQL, MySQL, MariaDB, and MongoDB with schedules, retention, encrypted storage, notifications, and restore workflows.
21. **changedetection.io** Self-hosted website change monitoring for prices, inventory, policy pages, releases, and other web content, with configurable alerts and change history.
22. **Appsmith** Open-source low-code platform for building internal tools, admin panels, dashboards, and database-backed workflows with a visual editor, JavaScript, APIs, and data-source integrations.
23. **Actual Budget** Privacy-focused, local-first personal finance and envelope budgeting with reports, sync, optional bank import, and optional end-to-end encryption.
24. **Activepieces** Open-source workflow automation with a visual builder, AI agents, and hundreds of integrations.
25. **Linkding** Fast, lightweight self-hosted bookmark manager with tags, search, browser extensions, import/export, and an authenticated REST API.
26. **Wiki.js** Modern open-source knowledge base with access control, search, and collaborative editing.
27. **Wallos** Self-hosted subscription tracker for recurring payments, renewal dates, categories, currencies, statistics, and configurable notifications.
28. **Shiori** Lightweight self-hosted bookmark manager with full-text search, tags, import/export, browser extensions, and offline webpage archiving.
29. **PrivateBin** Zero-knowledge encrypted pastebin for expiring text, code, and password-protected links. Encryption and decryption happen in the browser.
30. **pgAdmin** Web-based administration for PostgreSQL, with a secure initial administrator account and persistent server definitions, preferences, sessions, and user files.
31. **ntfy** Private push notifications for scripts, apps, and infrastructure. Publish over HTTP and receive alerts in the web UI or ntfy mobile apps.
---
# v2.5.7 - xCloud
> Then you can install the required service as per your need:
## **🔥** New Features
- **⚡ xCloud now provisions servers nearly 50% faster** – We optimized how xCloud prepares new servers. Required services are prioritized first, while non-essential setup tasks are handled more efficiently in the background.
📌 New servers can become ready faster.
📌 Initial setup feels smoother and less blocked.
📌 Users can start working sooner after creating a server.
- **Install Services from the Dashboard** – When you install a site, your required services will be auto-installed. But if you want, you can now also install supported services directly from the server management dashboard.
Instead of relying on manual setup, users can open the Install a Service panel and choose which service or runtime they want to add to the server.
📌 Install services from the server dashboard.
📌 Supported options include PHP, Node.js, Redis, MySQL, and MariaDB.
📌 Version-specific options appear after selecting a service.
📌 Makes server customization easier without manual command-line work.
Visit Server > **Settings**
Then you can install the required service as per your need:
- **Service Auto-Healing Foundation** – xCloud now has a stronger foundation for detecting and recovering failed services.
📌 Services can be tracked more reliably.
📌 Failed or inactive services are easier to detect.
📌 This improves long-term server reliability and prepares xCloud for better automatic recovery flows.
## **✨** Improvements
- **Smarter Service Management** – Server services are now tracked in a more structured and reliable way.
📌 More accurate service status tracking.
📌 Clearer separation between services and runtimes.
📌 Easier management for start, stop, restart, and install actions.
📌 Better foundation for real-time service updates.
- **Live Service Status Updates** — Service actions now provide better real-time feedback in the dashboard.
📌 See service status changes without constantly refreshing the page.
📌 Better visibility when installing, starting, stopping, or restarting services.
📌 Easier to understand what is happening on your server.
- **Clearer Services and Runtime Display** – The server management interface now shows services and runtimes more clearly.
📌 Easier to understand which services are installed.
📌 Cleaner labels for server components.
📌 Better organization for PHP, Node.js, database services, and other runtimes.
- **Improved Database Options** – Database-related options are now cleaner and easier to understand.
📌 Better database picker during site creation.
📌 More consistent naming and capitalization.
📌 Less confusion when selecting database options.
No action is required from users. Existing servers will continue working normally.
## **🐛** Bug Fixes:
📌 Improved WordPress migration verification so xCloud can better confirm when a migration has completed successfully.
---
# v2.5.8 - xCloud
> ✨ Improvements Improved Mailbox Admin Visibility - NEW Mailbox management now has better admin tooling and reporting support. Safer Staging Pull from
## **✨** Improvements
- **Improved Mailbox Admin Visibility** – NEW Mailbox management now has better admin tooling and reporting support.
- Safer Staging Pull from Production – Pulling data from production to staging is now safer. – Sensitive mailer credentials are sanitized during staging sync. WordPress salts are refreshed for staging environments.PHP version parity is improved between production and staging. Helps prevent accidental use of production credentials in staging
- Faster OpenClaw Server Readiness – We improved the infrastructure flow for OpenClaw server creation so eligible OpenClaw servers can be prepared and assigned faster.
- Better Server Resize Billing Flow – Server resize billing now works more smoothly with the invoice payment modal.
- Improved Service Sync ReliabilityWe added a more reliable server service sync flow to keep server service records aligned.
- Cleaner Alert Notifications – We improved alert handling to prevent duplicate notifications for some alert events.This helps reduce noise and keeps notifications more accurate.
- Stronger Supply Chain Protection – We added an npm package safety guard to reduce the risk of installing newly published potentially unsafe packages too quickly.
- The server creation stack input has been updated with better design and positioning.
## **🐛** Bug Fixes:
- Fixed an issue where the Rank Math NGINX rewrite template could generate unsafe or unreliable rewrite output.
- Fixed an issue where the first server bill could be missing in some billing repair flows.
- Fixed a duplicate bill hash issue during server bill repair.
- Fixed server bill matching so products are matched correctly by renewal period.
- Fixed an issue where PHP auto-healing installation could run incorrectly on Al Agent Hosting and Docker-based stacks.
- Fixed a Redis extension issue that could cause instability during PHP installs on OpenLiteSpeed or NGINX servers.
- Fixed an issue where the caching page could appear blank for sites without a Redis password.
- Improved Redis password show/hide behavior on the caching page.
- Hardened the sudo user provisioning script for better reliability.
- Fixed server permission tests and backend handling around the newer server service structure.
---
# v2.6.2 - xCloud
> xCloud v2.6.2 introduces a new interactive browser SSH terminal, a redesigned server creation experience, new Hermes management panels, smarter Docker Compose
xCloud v2.6.2 introduces a new **interactive browser SSH terminal,** a **redesigned server creation experience**, new **Hermes management panels**, **smarter** **Docker Compose environment setup**, and safer confirmation modals for risky server actions. This release also includes server setup improvements, Mailbox validation updates, and multiple reliability fixes across sites, servers, backups, Supabase, WordPress, and dashboard workflows.
## 🚀 New Feature
### [🌟 Interactive Browser SSH Terminal — Open Server & Site Terminal From xCloud Dashboard](/docs/access-web-terminal-in-xcloud/)
Open server, sudo user, or site user terminal sessions directly from the xCloud dashboard, no local SSH client required. Terminal access is permission-controlled and uses secure, single-use session tickets, so server credentials are not exposed to the browser.
### 🌟 Redesigned Server Creation Flow
We redesigned the server creation experience across all supported providers with a cleaner layout, improved plan selection, better stack options, and recommended plan support. This makes launching a new server easier, clearer, and more consistent.
### 🌟 New Hermes Management Panels
Hermes sites now include new dashboard panels for Status, Reset, Environment, and Updates. You can view service status, manage selected settings, reset configuration, and check updates more easily from xCloud.
## ⚡ Improvements
- Safer Confirmation for Risky Server Actions – xCloud now shows a confirmation modal before high-impact actions like restarting the server, NGINX, LiteSpeed, or MySQL/MariaDB. This helps prevent accidental downtime.
- Smarter Docker Compose Environment Setup – Custom Docker Compose setup now detects missing environment variables and helps prepare the .env file automatically. This makes Docker Compose deployments easier and reduces setup errors.
- New server creation now uses Ubuntu 24.04 by default.
- Improved server setup reliability for new servers.
- Improved server plan categorization and recommendation support.
- Improved dashboard design consistency across server creation pages.
- Improved Hermes provider and channel setup instructions.
- Improved Mailbox validation for reserved prefixes.
- Improved service and permission handling across server pages.
## 🐛 Bug Fixes
- Fixed Laravel NGINX 404 handling for PHP-served assets.
- Fixed Supabase install/reinstall port conflict issues.
- Fixed Supabase dashboard password configuration issues.
- Fixed WordPress Git-clone site creation failure.
- Fixed site deletion handling when no database engine exists.
- Fixed CPU monitoring process detection.
- Fixed empty MySQL backup size checks.
- Fixed Wordfence manual scan timestamp saving.
- Fixed sudo username validation.
- Fixed Mailbox admin prefix and API error handling.
- Fixed Site Events per-page dropdown and pagination issues.
---
# v2.6.6 - xCloud
> Introducing xCloud Pulse, a native macOS menu bar companion app for xCloud, built on the upcoming xCloud Public API.
## 🔥 New Features
#### 🌟 [**xCloud Pulse**](/docs/install-and-set-up-xcloud-pulse-macos-menubar/) — Native macOS Menu Bar Companion App
Introducing xCloud Pulse, a native macOS menu bar companion app for xCloud, built on the upcoming xCloud Public API.
xCloud Pulse works like a quick-access xCloud dashboard that lives directly in your Mac menu bar, helping you check important site and server information without opening the browser every time.
With xCloud Pulse, you can:
- See every site and server at a glance, with live status the moment the app opens.
- Check site status, PHP version, SSL, and backup state for any site in one place.
- Catch critical issues, recent activity, warnings, and system logs as they happen.
- Run quick actions such as purge cache, trigger backup, copy a server IP, or open the dashboard, each in a single click.
- Search across every site, server, and action with a fast command palette, the way Spotlight works on your Mac.
- Native macOS app, light on your machine and built on the xCloud Public API.
The goal is simple: make everyday xCloud tasks faster, whether you need to check a site, purge cache, review an issue, or trigger a backup without leaving your workflow.
xCloud Pulse is currently being fine-tuned, with UI improvements and polishing still in progress.
## ✨ Improvements & Bug Fixes
- Added a cleaner and more helpful UI for pending server setup, making it easier for new users to complete pending server creation.
- Improved Git branch search in the Deploy via Git site creation flow, allowing users to search and find more branches more reliably.
## Bug Fixes
- Fixed several billing issues related to self-managed servers.
- Fixed an issue where the “Reading databases with users” event could fail on servers that had no databases.
## 🔖 Resources
- [**How to Access the xCloud API**](/docs/how-to-access-the-xcloud-api/)
- [**xCloud API Documentation**](http://xcloud.host/docs/xcloud-api)
---
# v2.7.7 - xCloud
> Deploy via Git through the xCloud API
## 🔥 New Feature
**Deploy via Git through the xCloud API**
You can now detect a repository’s application type and deploy Git-based projects through the xCloud Public API.
- Detect supported projects before deployment.
- Deploy GitHub, GitLab, and Bitbucket repositories through API-powered workflows.
- Receive clearer guidance when repository access, deploy keys, DNS, or configuration requires attention.
- Use the same guided deployment flow through xCloud MCP and compatible AI tools.
**A redesigned OneClick App catalog**
The OneClick App catalog now makes it easier to discover and compare supported applications.
- Browse apps by category.
- Search and filter the catalog more quickly.• Switch between grid and list views.
- See clearer service names and compatibility information before installation
## ✨ Improvements
- Webmail password self-service – Mail users can now change their own webmail passwords. xCloud also provides clearer guidance when a changed webmail password must be updated in the xCloud panel.
- Public API and MCP responses now provide actionable recovery guidance instead of only generic errors.
- Git deployment setup now displays the deploy key and explains when xCloud cannot add it automatically.
- Server suspension notes now provide clearer billing context for outstanding invoices.
- OneClick App cards have improved labels, badges, categories, and filtering.
- Backup defaults are selected more accurately for sites with or without a database.
## 🐛 Bug Fixes
- Fixed Docker deployments failing because of host-port conflicts left by older containers.
- Fixed Basic Authentication for Node.js sites.
- Fixed PHP and Nginx upload-limit synchronization, including unlimited values.
- Fixed service controls using incorrect identifiers for Redis and other managed services.
- Fixed backups incorrectly reporting harmless liveness output as an error.
- Fixed shared-domain DNS records not being fully removed after site deletion.
- Fixed private repository access, branch detection, deploy script, and configuration handoff issues.
- Fixed backup scheduling errors caused by incomplete frequency settings.
---
# Chatwoot Hosting - xCloud
> Managed Chatwoot hosting on xCloud. Deploy the open-source customer engagement platform on a Docker server in one click, with free SSL, backups, and 24/7 support.
## Deploy your AI Agent in 1-Click - Managed Hermes Agent Hosting starts from $9.99
[Get Started Now](/hermes-agent-hosting/)
[](/)
Toggle Menu
Close Menu
[Menu](#)
[Solutions](#)Close SolutionsOpen Solutions
## Hosting Solutions
## Managed WordPress Hosting
Fast, secure WordPress hosting with automated updates, backups and more.
## WooCommerce Hosting
Managed hosting supporting high traffic sites, millions of checkouts per minute.
## Laravel Hosting
Laravel-optimized hosting with staging, SSL, and streamlined deployment tools.
## LLM Hosting
High-performance platform built for hosting large language models.
## n8n Hosting
Managed n8n hosting with optimized performance, a free SSL certificate, and more.
## OpenClaw Hosting
Secure AI agent hosting with Firewall, updates, backups, SSL and more
## Node.js Hosting
Easily deploy server-side or client-side app with Node.js hosting.
## Hosting Addons
Power Up Your Hosting Experience with Premium Addons
[](https://xcloud.host/deploy-openclaw)
[Pricing](/#pricing)
[Providers](#)Close ProvidersOpen Providers
## Cloud Providers
## xCloud Managed Hosting
Fully managed cloud hosting solution with full server backup & more
## DigitalOcean Hosting
Fast, easy cloud deployments on DigitalOcean with $200 credits for new user.
## Vultr Hosting
Feature-packed managed Vultr hosting with $100 free credits.
## Hostinger VPS
Bring your Hostinger VPS and manage with xCloud's advanced control panel.
## Any Provider
Connect your Ubuntu server to our platform and manage with powerful features easily.
## AWS Hosting
Optimized AWS hosting engineered for performance, security, and scalability.
## Google Cloud Hosting
Experience the power of Google Cloud with xCloud's user friendly platform
## Linode Hosting
Unleash the power of Linode servers with our feature-packed panel.
## Next Gen Hosting Built For Stability, Security & Speed
- 
### No Restrictions On Traffic & Sites.
- 
### Full Server Backup
## [Starts at **$5**/Month](#)
[Features](#)Close FeaturesOpen Features
## Features
## App Deployment
## Server Management
## Scheduled Tasks
## Monitoring & Alerts
## Security, SSL, Firewall
## Git, CLI & Dev Tools
## Staging Environments
## Team Collaboration
## Backups & Snapshots
## One Click Apps
## AI Website Builder
[See All Features](/features)
## Managed n8n Hosting:
For Smart & No-Code
Automation
[Learn More](/n8n-hosting/)
[Integrations](#)Close IntegrationsOpen Integrations
## Integrations
## WhatsApp Notifications
Get instant alerts and updates delivered straight to WhatsApp.
## Cloudflare Integration
Deliver content at top speed worldwide with built-in Cloudflare integration.
## Git Provider
Connect your repositories and automatic deployments from your Git projects.
## Google Drive Storage
Securely store automated backups in your Google Drive account for your backup.
## Slack Alerts
Connect to Slack for real-time performance and event notifications.
## Object Cache PRO
Speed Up Your WordPress Application Using Object Cache Pro.
## Mailgun
Integrate Mailgun in WordPress to send transactional emails easily.
## Connect Us :
- [](https://www.facebook.com/xCloud.host)
- [](https://x.com/xCloud_host)
- [](https://www.linkedin.com/company/xcloud.host/)
- [](https://www.youtube.com/@xCloud-Hosting)
- ### [Documentation](/docs)
- ### [Tutorials](https://www.youtube.com/@xCloud-Hosting)
## Get In Touch
Talk to our support team for any issues.
- ### [support@xcloud.host](mailto:support@xcloud.host)
[Talk To Us](/support)
## Join our global community
[](https://www.facebook.com/groups/xcloud.community)
[Resources](#)Close ResourcesOpen Resources
## Resources
## Blog
Read the latest guides, news, insights, and industry updates.
## Comparison Pages
Compare providers, features, and plans to find your perfect match.
## Support Portal
Access support tickets and live expert support 24/7 for any issues.
## Documentation
Step-by-step technical docs to help you build with confidence.
## Case Studies
See how real businesses scale and succeed with xCloud.
## Write for Us
Submit your expert articles, contribute tutorials, guides, and insights.
## Watch & Learn
## Next Gen Hosting Built For Stability, Security & Speed
[See All Videos](https://www.youtube.com/watch?v=oEE9OHo3_48)
[Join Free](https://app.xcloud.host/register)
[Login](https://app.xcloud.host/login)
[Join Free](https://app.xcloud.host/register)
[login](https://app.xcloud.host/login)
[Join Free](https://app.xcloud.host/register)
## Managed Hosting for self-hosted customer support
# Fully Managed
Chatwoot Support Hosting
Run live chat, email, WhatsApp, and social inboxes in one shared queue using managed Chatwoot hosting, with consistent performance and no maintenance work.
[Deploy Chatwoot Now – $24.99/mo](#pricing)
- 
### 24/7 Expert Support
- 
### No Lock-In, Cancel Anytime
## **How It Works**
## Simple Steps To Launch Your Chatwoot Inbox in Minutes
Deploy and manage your Chatwoot instance with a carefully designed, streamlined workflow built for consistent speed, stability, and reliability from first deployment to everyday production use.
01
## Choose Your Server
Pick an xCloud managed server or connect your own provider, then set it up as a Docker server to deploy Chatwoot.
02
## Select Application
Open One Click Apps in your xCloud dashboard and choose Chatwoot from the available applications to begin the guided setup.
03
## Configure Your Inbox
Add your domain and deployment settings in the xCloud dashboard. We provision Chatwoot on your server.
04
## Go Live Right Away
Confirm the setup, go live, and invite your agents to their first shared inbox in just a few clicks.
## Pricing
## Simple Pricing for Your Chatwoot Inbox
Your team grows, your bill does not. Add agents, inboxes, and channels without changing the plan.
## Cloud VPS 6GB
## $24.99
Renews at $24.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=f292a3d0-fbcc-4c23-be7b-67f9cd677c69&app=chatwoot)
- ### 6 GB RAM
- ### 100 GB NVMe SSD
- ### 4 vCPU cores
- ### 30TB Bandwidth
## Popular deal
## Cloud VPS 16GB
## $59.99
Renews at $59.99/mo. Cancel anytime.
[Get started](https://app.xcloud.host/cart/product/checkout?product=33a8077d-dedc-4187-967d-b023ae20ed5c&app=chatwoot)
- ### 16 GB RAM
- ### 200 GB NVMe SSD
- ### 6 vCPU cores
- ### 30TB Bandwidth
## Cloud VPS 24GB
## $84.99
Renews at $84.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=b9bc978a-fd8e-4aea-a847-02ad127c9bfb&app=chatwoot)
- ### 24 GB RAM
- ### 300 GB NVMe SSD
- ### 8 vCPU cores
- ### 30TB Bandwidth
## Use Cases
## Built for Teams That Talk to Customers All Day
These are starting points, not limits. If your customers are already messaging you in five different places, those messages belong in one queue.
## SaaS Support Teams
- ### Chat widget on every page
- ### Email and chat in one queue
- ### Canned replies that scale
- ### CSAT on every conversation
## Ecommerce Stores
- ### WhatsApp and Instagram DMs
- ### Order questions with full context
- ### Pre-sales chat that converts
- ### Ready for peak season traffic
## Agencies
- ### One inbox per client
- ### Isolated servers and data
- ### White-labelled chat widget
- ### Clean handover at the end
## Startups & Solo Founders
- ### Replace per-seat helpdesk pricing
- ### Flat infrastructure cost
- ### Talk to your users from day one
- ### Move fast without lock-in
## Internal Help Desks
- ### IT and HR requests in one place
- ### Private notes on every thread
- ### Assignment rules per team
- ### Full history that stays put
## Regulated & Privacy-First
- ### Data on your own server
- ### Region of your choosing
- ### Audit trail on every action
- ### No third-party helpdesk vendor
## Features
## One Inbox To Support, Engage, & Scale for Your Team.
Docker helps developers build and run applications using containers. Containers bundle everything an application needs into a single, portable package.
- ### Live chat, email, and social inboxes in one queue
- ### Help center and canned responses in the same place
- ### Automation rules, macros, and CSAT built in
- ### One-click deployment, free SSL, and firewall
## Capabilities
## A Platform built for how customer-facing teams actually work
Chatwoot is an open-source customer engagement platform. The interface feels like any modern shared inbox. What’s different is that you own the server, the data, and the roadmap.
## Shared Inbox
Every conversation from every channel lands in one queue your whole team can see, claim and resolve.
## Omnichannel
Website live chat, email, WhatsApp, Instagram, Messenger, Telegram and SMS, all answered from one screen.
## Help Center
Publish a self-serve knowledge base on your own domain so the common questions never reach an agent.
## Automations & Macros
Route, assign, label and reply automatically with rules that run the moment a conversation arrives.
## Teams & Assignment
Group agents into teams, set round-robin assignment, and keep private notes out of the customer’s view.
## Reports & CSAT
Response times, resolution counts and satisfaction surveys, broken down per agent, team and inbox.
## Contacts & Segments
A contact record behind every conversation, with custom attributes, labels and the full history attached.
## API & Integrations
A REST API, webhooks and agent-bot hooks to wire Chatwoot into the rest of your stack.
## Advanced Features
## Ready To Own Your Customer Conversations?
Whether you answer a handful of chats a day or run a full support desk across every channel, managed Chatwoot hosting delivers the reliability, flexibility, and performance your team needs to reply without limits. Deploy faster. Scale smarter. Stay in control.
## Fast Provisioning
Deploy faster using an xCloud Managed Server built with optimized stacks and high-speed SSDs.
## Enterprise-grade security
Protect your infrastructure with a free SSL certificate and more advanced security features at no additional cost.
## Intuitive Control Panel
From Server creation to application deployment, everything can be managed from our intuitive control panel.
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
**xCloud** isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Paul Goulart
@freelivingsoul
I set this up locally, tried AWS and Digital Ocean with disappointing results. Setup on Xcloud was easy and it’s still working!
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. xCloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## Your Inbox Should Be Live Right Now.
Deploy a production Chatwoot instance in minutes. Connect your website widget, email, WhatsApp, and social
inboxes — then let your team reply, route, automate, and measure it all from one shared queue.
[Start Deploying Now](#pricing)
[Browse One Click Apps](/one-click-apps/)
- 
### No Lock-In
- 
### Cancel anytime
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What is Chatwoot?
Chatwoot is an open-source customer engagement platform where your team answers live chat, email, WhatsApp, Instagram, Messenger, Telegram and SMS from a single shared inbox. It includes a help center, canned responses, automation rules, CSAT surveys and reporting, and because it is self-hosted, every conversation and contact record stays on your own server.
### How do I deploy Chatwoot on xCloud?
Chatwoot is available through xCloud’s One Click Apps. Create a Docker server in your xCloud dashboard, open One Click Apps, select Chatwoot, add your domain, and deploy. xCloud provisions the containers, maps the domain, and issues the SSL certificate for you.
### Do I need a Docker server to run Chatwoot?
Yes. Chatwoot runs as a containerised application alongside PostgreSQL and Redis, so it needs to be deployed on a Docker server. When you create a new server in xCloud, choose Docker as the server type — you can then deploy Chatwoot to it from One Click Apps.
## xCloud is the future of cloud hosting and server management for WordPress users, streamlining the way you host, deploy, manage or update your websites like never before!
## Get The Latest Updates
- [](https://www.facebook.com/xCloud.host)
- [](https://x.com/xCloud_host)
- [](https://www.linkedin.com/company/xcloud.host/)
- [](https://www.youtube.com/@xCloud-Hosting)
## Address:
xCloud Hosting, LLC. 124 Broadkill Rd #599 Milton, DE 19968-1008
## Products & Services
## Resources
## Compare xCloud
## Addons
## Quick Help
## **Company**
- #### [Privacy Policy](/privacy-policy/)
- #### [Terms and Condition](/terms-and-conditions/)
## A **[WPDeveloper](https://wpdeveloper.com/)** Creation, in Partnership with **[WPManageNinja](https://wpmanageninja.com/)**
## **xCloud Hosting LLC**. All rights reserved.
---
# Claude Code Hosting | Build & Manage Seamlessly
> Run Claude Code on a fast, secure, fully managed VPS. Deploy in minutes, keep tasks running around the clock, and manage everything from anywhere.
# **Cluade Code Hosting**
## Host Claude Code on a Fast, Secure VPS Ready in Minutes
Host Anthropic’s agentic coding tool on a dedicated VPS. Start a task, close your laptop, and let Claude Code keep working. You can manage everything from your terminal, browser, or phone.
## **Setup Process**
## Get Your Claude Code Projects Running in a Few Steps
Get Claude Code running on a VPS without the manual server config. From provisioning to a live, persistent environment, every step is streamlined so you can focus on building.
### Choose Deployment Method
Launch an xCloud Managed Server or connect your own from DigitalOcean, Vultr, Linode, AWS, or another provider.
### Configure Your Environment
Set your Node.js version, dependencies, and API keys. Your environment comes pre-configured, so setup stays simple.
### Go Live Right Away
Launch Claude Code and link it to the Claude web or mobile app. Run tasks from anywhere and get notified when they finish.
## Pricing
## Reliable Claude Code Hosting
at a Price You’ll Love
Choose a pay-as-you-go plan on your preferred cloud server. Run unlimited projects with the tools
you need for reliable, always-on development.
- ###### xCloud Managed Server
- ###### Self-Managed Server
### All
### 1 GB
For Personal Use
### 2 gb
For Basic Websites
### 4 gb
For Growing Websites
### 8 gb
For Busier Websites
### 16 gb
For Bigger, Busier Websites
### 32 gb
For HIGH-PERFORMANCE NEEDS
### 48 gb
For HIGH-PERFORMANCE NEEDS
### 58 gb
For HIGH-PERFORMANCE NEEDS
## Elevate your site with xCloud servers—ensuring speed and security, with no hidden charges in the future.
## Premium servers are powered by High-Frequency 3GHz+ Intel Xeon CPUs, lightning-fast memory, and NVMe storage, delivering unmatched speed and performance. General servers, on the other hand, offer a budget-friendly solution for standard workloads
- ###### All
- ###### 1 GB
- ###### 2gb
- ###### 4gb
- ###### 8GB
- ###### 16gb
- ###### 32gb
- ###### 48GB
- ###### 58GB
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
## Business Max
- ### 64 GB RAM
Ultimate plan for unparalleled power
- ### 1280 GB SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 10 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-max)
## $ **399.00** /mo
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
Monthly
Yearly
MonthlyYearly
## Black Friday Special Deal : One-time Payment – LIFETIME Access!
Bring your own server and unlock access to our cloud control panel to enjoy a seamless server and site management experience for a lifetime.
[Grab Lifetime Deal](/deal/)
## Want to explore xCloud first? Try it out for free and then decide!
[Get started](https://app.xcloud.host/register)
## FREE PLAN
- ### 1 Server
- ### 10 Site
## Start your journey without cost
## Starter
- $5/Server (/month)
- 1-5 Servers
- Unlimited Sites
## Perfect for Beginner
## Professional
- $4/Server (/month)
- 6-10 Servers
- Unlimited Sites
## Tailored for Experts
## Agency
- $3/Server (/month)
- 11+ Servers
- Unlimited Sites
## Perfect for Large Teams
## Features
## Built for Everything You Build with Claude Codee
Claude Code is Anthropic’s agentic command-line tool that writes, edits, and ships code straight from your terminal. Hosted on a VPS, it becomes a persistent teammate that works around the clock, from first prompt to production.
- ### Agentic coding, refactoring, and debugging from the terminal
- ### Long-running tasks that don’t stop when your machine does
- ### Full-stack project support with your own dependencies
- ### Easy deployment and integration with your existing infrastructure
## Advanced Features
## Deploy Claude Code Projects on Your VPS for Fast, Secure Performance
Launch Claude Code on a high-performance VPS with no complicated setup. Everything comes pre-configured so you can deploy in minutes and scale with confidence.
## Fast Provisioning
Quickly provision servers and deploy sites with xCloud Managed Servers, DigitalOcean, Vultr, Linode, AWS, or Any Servers.
## Enterprise-grade security
Protect your infrastructure with a free SSL certificate, AI bot blocking, and advanced security features at no additional cost.
## One Click Deployment
Start building your server infrastructure instantly with a streamlined setup that gets you running in just a few clicks.
## Intuitive Control Panel
From Server creation to application deployment and security settings, everything can be managed with few clicks from our easy-to-use hosting control panel.
## Optimised Setup
Your server is pre-optimized with high-performance stacks like Nginx or OpenLiteSpeed and backed by ultra-fast NVMe SSD storage
## Easy DNS Management
Easily manage your DNS records through our intuitive panel. Also, verify your DNS in just 1 click using Cloudflare integration.
## AI Apps
## More AI Apps You Can Deploy on xCloud
From personal assistants to autonomous AI companies, deploy the tools your workflow needs on xCloud.
### OpenClaw Hosting
Deploy Your Personal AI Assistant With Managed OpenClaw Hosting Turn OpenClaw into a working assistant that executes tasks and manages conversations across platforms. Go live in minutes.
[Learn More](/openclaw-hosting/)
### Hermes Agent Hosting
Fully Managed Hermes Agent Hosting. Deploy Hermes Agent in five minutes with persistent memory and connections to Telegram, tools, files, APIs, and scheduled tasks. No server setup, no maintenance.
[Learn More](https://xcloud.host/hermes-hosting/)
### Paperclip Hosting
Run an Autonomous AI Company With Managed Paperclip Hosting Skip the hours of setting up and get a fully managed Paperclip instance live in under a few minutes. With xCloud, focus on building your AI workforce, not complexities.
[Learn More](/paperclip-hosting/)
### Claude Hosting
Deploy Your Personal AI Assistant With Managed OpenClaw Hosting Turn OpenClaw into a working assistant that executes tasks and manages conversations across platforms. Go live in minutes.
[Learn More](/claude-code-hosting/)
### Codex Hosting
Fully Managed Hermes Agent Hosting. Deploy Hermes Agent in five minutes with persistent memory and connections to Telegram, tools, files, APIs, and scheduled tasks. No server setup, no maintenance.
[Learn More](/codex-hosting/)
### Odysseus Hosting
Run an Autonomous AI Company With Managed Paperclip Hosting Skip the hours of setting up and get a fully managed Paperclip instance live in under a few minutes. With xCloud, focus on building your AI workforce, not complexities.
[Learn More](/odysseus-hosting/)
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
xCloud isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
#xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. Xcloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What is Claude Code VPS hosting?
It’s a dedicated server set up to run Claude Code, Anthropic’s agentic coding tool. Instead of running it only on your local machine, you get a persistent, always-on environment that keeps working even when your computer is off.
### Can I access Claude Code remotely?
Yes. You can link your VPS to the Claude web or mobile app, start tasks from anywhere, and get notified when they finish. Your environment stays available whether you’re at your desk or on your phone.
---
# Clickjacking Attack: Attack Examples & Prevention Guide with WordPress Plugins - xCloud
> Discover Clickjacking Attacks, a hidden online threat that tricks users into unintended actions. Learn how these attacks work, recognize them, and protect your website with effective measures.
Have you ever heard of a [**Clickjacking Attack?**](https://wpdeveloper.com/free-tools-to-scan-wordpress-for-vulnerabilities/) When you click, you think you are clicking on one thing, but actually, you are clicking on something totally different that the bad guys set up. Today, we will learn about **clickjacking attacks**, how to spot these tricks and secure our websites! So let us roll on.
## **What Is Clickjacking Attack?**
A Clickjacking Attack is a sneaky trick where hackers make you click on something you did not mean to. Imagine you think you are clicking on a game button, but instead, you are actually liking a page or sharing something on social media without knowing it. That is what Clickjacking Attacks do. They hide the real thing you are clicking on under something that looks safe.
These attacks use a part of web pages called “**frames**” to stack a hidden layer over the visible parts of a website. Because you can not see the hidden part, you think you are clicking on the normal webpage. But really, you are clicking on something the hacker has set up to trick you.
Clickjacking Attacks can be used to do many harmful things:
- They can steal your private info like passwords or account numbers.
- They can take control of your computer by making you click on bad links.
- They can trick you into giving permissions or access to your data.
That is why it is so important to learn about Clickjacking Attacks—so you can avoid being tricked by these hidden dangers.
## **How Clickjacking Attacks Work**
[**Clickjacking Attacks**](https://wpdeveloper.com/social-engineering-attacks-wordpress-security/) are like a magic trick on the internet where what you see is not what you really get. Imagine you are trying to press a button to get a candy from a machine. You see the button and press it. But, what you can not see is that there is a hidden layer over the button. When you press what you think is the candy button, you are actually pressing a button that sends a signal to drop a rock instead of a candy. Let us break down how these attacks work in a simple way:
### **Layering**
Hackers put a transparent layer over something that looks normal on a webpage. This layer is invisible, so you do not know it is there. You might see a button that says “**Play video**,” but right on top of it, invisible to you, is another button.
### **Tricking the Click**
When you click on the “Play video” button, you are actually clicking on the invisible layer. This click can do many things like open a new link, download a file, or change a setting, all without you knowing.
### **Using Frames**
A big part of Clickjacking Attacks is using something called an “**iframe**.” This is a web tool that lets one webpage appear on another webpage. Hackers use iframes to put their invisible layer over the real webpage.
### **The Invisible Trap**
Because the harmful actions are hidden, you think you are safely interacting with legitimate parts of the webpage. Instead, your clicks are going to the invisible layer set up by the hacker.
This is why Clickjacking Attacks decieves people, making it hard to notice you are being tricked. By understanding how these attacks work, you can be more careful and check more closely before clicking on things when you are online.
## **How to Recognize a Clickjacking Attack?**
Understanding when you might be facing a Clickjacking Attack can help you avoid falling victim to one. Here is how to spot the signs:
### **Strange Web Page Behavior**
If you notice that web pages do not behave as expected, it might be a Clickjacking Attack. For example, clicking on a link does not take you where it should, or new windows pop up unexpectedly.
### **Hidden Buttons**
Sometimes, in a Clickjacking Attack, buttons might be hidden under invisible layers. If you click somewhere on a page and something unexpected happens, like a new program downloading, this might be a sign.
### **Check the Website’s Address**
Always look at the [**website’s URL**](https://wpdeveloper.com/how-to-block-ip-address-in-wordpress/) in the address bar. If it looks weird or not like the usual address, it could be a fake site set up for a Clickjacking Attack.
### **Unexpected Requests for Personal Information**
If a normally safe site suddenly asks for your password or other personal information in a strange way, be cautious. This could be a Clickjacking Attack trying to steal your information.
### **Use of Iframes**
Clickjacking Attacks often use iframes (a type of code that lets one website be shown on another website) to trick you. If you are tech-savvy, you can look at the source code of suspicious web pages to check for hidden iframes.
Being alert and knowing these signs can help you avoid Clickjacking Attacks. It is always better to be safe and double-check anything suspicious rather than risk a click that could lead to trouble.
## **Examples of Clickjacking Attacks**
Clickjacking Attacks can happen in many ways. Here are some real examples to help you understand how tricky they can be:
### **Social Media Like Button Scam**
Imagine playing a fun game on a website. You click around to score points, but each click also secretly clicks a **“Like”** button on [**social media**](https://wpdeveloper.com/automatically-social-share-wordpress/)**.** You do not see this happening, but suddenly, you have liked a bunch of pages or posts without knowing. This scam uses Clickjacking to trick you into liking something you did not choose to.
### **Sensitive Actions**
Some Clickjacking Attacks trick you into doing more serious things. For example, you might think you are clicking a button to see a video, but instead, you are clicking a button that turns on your webcam. The bad guys could then watch you without your permission. This type of Clickjacking can be very dangerous because it invades your privacy.
### **Software Installation**
Another common trick is making you download harmful software. You might see a button to play a video or download a free book, but clicking on it actually starts downloading a virus or malware. This happens because the real download button is hidden under a fake one that looks safe.
### **Changing Online Settings**
Some Clickjacking Attacks trick you into changing important settings in your online accounts. For example, you might think you are updating your profile, but you are actually giving permission for apps to access your private info.
### **Fake Ad Clicks**
Hackers sometimes use Clickjacking Attacks to make money by making you click on ads. You think you are clicking on a normal part of a webpage, but each click is actually on an ad that pays the hacker money.
These examples show how Clickjacking Attacks can be used in different ways, from annoying to really harmful. Understanding these can help you stay alert and protect yourself from being tricked online.
## **How to Prevent Clickjacking Attacks**
Stopping Clickjacking Attacks involves making it hard for attackers to trick people into clicking things they should not. Here are some simple steps that anyone, especially website owners, can take to protect against these attacks:
### **X-Frame-Options Header**
This is a setting that website owners can use. It tells web browsers not to let other websites put your web pages inside frames or layers. By setting this to “DENY” or “SAMEORIGIN,” you make sure that no one can put invisible layers over your website. This means no one can trick users into clicking on them.
### **Content Security Policy (CSP)**
This is a more powerful tool for website owners. It lets you control where your web pages can be shown and stops bad people from embedding your content on their own sites. By using CSP, you can stop many types of Clickjacking Attacks by preventing others from framing your content.
### **Regular Updates**
Keep all your software up to date. This includes your web browser, any plugins or themes you use on your website, and any other software. Updates often [**fix security problems**](https://wpdeveloper.com/biggest-cyber-security-mistakes/) that attackers use to carry out Clickjacking Attacks.
### **Educate Users**
Teach people who use your website about Clickjacking Attacks. If they know what to look out for, they can be more careful about where they click, especially on things that seem unusual or out of place.
### **Use Anti-Clickjacking Measures**
Some software tools and browser extensions can detect and stop Clickjacking Attacks. These tools might block clicks that seem suspicious or warn you if a website tries to do something sneaky.
By following these steps, you can make it much harder for attackers to use Clickjacking Attacks against you or anyone who visits your website. It is all about making the internet a safer place for everyone.
## **Use WordPress Plugins to Protect Against Clickjacking Attacks**
If you use WordPress for your website, you can add extra layers of protection against Clickjacking Attacks with the help of plugins. These plugins make it easier to secure your site without needing to be a tech expert. Here are some of the best plugins you can use:
### **Sucuri Security**
[**Sucuri**](https://wordpress.org/plugins/sucuri-scanner/) is a well-known security plugin that offers a variety of features to keep your WordPress site safe. It includes security activity auditing, file integrity monitoring, and malware scanning. Most importantly, it helps prevent Clickjacking Attacks by offering options to add security headers like X-Frame-Options and Content Security Policy (CSP) directly from the plugin settings.
### **iThemes Security**
iThemes plugin offers more than 30 ways to secure your site. One of its features includes strengthening your website’s defenses against Clickjacking Attacks. [**iThemes Security**](https://wordpress.org/plugins/better-wp-security/) allows you to easily set X-Frame-Options headers to prevent others from framing your site. It also offers comprehensive security settings that help protect your website from a variety of threats.
### **Wordfence Security**
[**Wordfence Security**](https://wordpress.org/plugins/wordfence/) is Known for its firewall and malware scanner, Wordfence also provides robust protection against Clickjacking Attacks. The firewall feature blocks malicious traffic, and the plugin includes an option to enhance clickjacking defense by implementing X-Frame-Options and CSP headers.
### **All In One WP Security & Firewall**
This plugin takes a holistic approach to WordPress security. [**All In One WP Security & Firewall**](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/) includes features to block Clickjacking Attacks by adding security headers. It is user-friendly, offering an easy way to apply advanced security measures without needing technical knowledge.
### **BulletProof Security**
[**BulletProof Security**](https://wordpress.org/plugins/bulletproof-security/) offers a range of security features including database security, firewall, and login security. It also protects against Clickjacking Attacks by allowing you to add various security headers easily, ensuring that your site is safeguarded from such threats.
By installing these plugins, you can significantly reduce the risk of Clickjacking Attacks on your WordPress site. Each plugin has its own set of features, so you can choose one that best fits your needs and budget. Remember, keeping your plugins updated is crucial as updates often include security enhancements to protect against new threats.
### **Educate & Stay Aware Against Clickjacking Attacks**
Clickjacking Attacks are clever tricks used by attackers to make you do things on the internet that you did not intend to do, like liking something on social media, enabling your webcam, or downloading malicious software.
These attacks can be harmful, but by understanding how they work and taking the right precautions, you can protect yourself and your website. With the right tools and knowledge, you can maintain a secure web and ensure that your visitors have a safe experience on your site.
If you find this blog helpful and want to read more blogs like this one, [**Subscribe**](/blog/) **to our blogs** and join our [**Facebook Community**](https://www.facebook.com/groups/xcloud.community) to connect with more people with common interests.
---
# Cloud Hosting or Traditional? Here’s What You Really Need to Know - xCloud
> Confused between cloud hosting and traditional hosting? Compare features, benefits, and costs to pick the best fit for your online business.
Choosing the right type of web hosting can be a critical decision for your website or online business. If you are stuck between **cloud hosting or traditional** hosting, you are not alone. Many people ask this exact question when building a new site or planning to scale.
Read the guide to understand both types of hosting. You will learn what they are, how they work, what makes them different, and which one is the right fit for you. Let us start with the basics.
## **What Is Traditional Hosting?**
Traditional hosting refers to the most common way websites have been hosted for decades. This includes shared hosting, virtual private servers (VPS), and dedicated servers. All of these r
ely on a single physical server located in a data center. You rent or lease space on that server from a hosting provider.
### **Shared Hosting**
In [**shared hosting**](/shared-hosting-vps-or-cloud-hosting/), your website sits on the same server as many other websites. All websites share the same resources such as RAM, bandwidth, and CPU power. This type of hosting is very affordable and easy to use. It is ideal for personal blogs, small business sites, or anyone who does not expect large amounts of traffic.
### **VPS Hosting**
VPS hosting or Virtual Private Server hosting offers more control and performance than shared hosting. Here, a physical server is divided into several virtual servers. Each one acts like its own private server. You get more resources, better speed, and more customization options than shared hosting. It is good for medium-sized businesses or growing websites.
### **Dedicated Hosting**
With dedicated hosting, you get the entire server for yourself. No sharing. This gives you full control, maximum performance, and the ability to customize everything from the operating system to the hardware configuration. It is typically used by large enterprises, data-heavy apps, or websites with very high traffic.
### **Key Features of Traditional Hosting**
- Hosted on one physical server
- Fixed resources based on your plan
- Direct control over hardware and software (especially in dedicated hosting)
- Predictable cost structure
- Physical location matters more for speed and data compliance
### **Who Uses Traditional Hosting?**
Traditional hosting is often chosen by:
- Small websites with steady traffic
- Businesses with fixed budgets
- Companies needing strict control over data
- Developers who want full access to the server environment
It is a reliable choice if your needs are simple and stable. But it does come with limitations, especially when it comes to scaling and handling unexpected traffic spikes.
## **What Is Cloud Hosting?**
[**Cloud hosting**](/what-is-cloud-hosting-and-how-does-it-work/) is a modern, flexible way to host websites and applications. Instead of relying on a single physical server, it uses a network of virtual servers that pull resources from a large pool of physical machines spread across multiple data centers. This design gives you access to on-demand computing power, scalable storage, and greater reliability than traditional hosting.
In simple terms, cloud hosting means your website or application is not locked to one physical server. Instead, it lives in a connected environment made up of multiple servers. If one server fails, another takes over instantly. If your site needs more processing power or storage, the system automatically adds it. When demand drops, resources are scaled down so you are not paying for unused capacity. Providers like [**xCloud**](/) make this process seamless, giving businesses the flexibility to grow without worrying about downtime or hardware limits.
### **How Cloud Hosting Works**
The backbone of cloud hosting is **virtualization technology**. A piece of software called a _hypervisor_ splits physical servers into multiple **virtual machines (VMs)**. These VMs are linked together through a central system that manages workloads and allocates resources where they are needed most.
Key components of cloud hosting include:
- **Compute resources** like CPU and RAM, drawn from a pool of servers
- **Cloud storage** that can be expanded instantly without downtime
- **Load balancing** to distribute incoming traffic evenly across servers
- **Redundancy systems** to keep services online during hardware or network failures
- **Pay-as-you-go billing** so you only pay for the resources you actually use
This structure allows websites to handle sudden traffic surges, recover quickly from outages, and operate smoothly for users anywhere in the world.
### **Types of Cloud Hosting**
Not all cloud hosting works the same way. There are several variations based on how resources are shared and who can access them.
#### **1\. Public Cloud Hosting**
This is hosted on infrastructure shared by multiple customers. Examples include AWS, Google Cloud, Microsoft Azure, and **xCloud** that offer competitive performance and cost-effective plans. Public cloud hosting is highly scalable and usually the most affordable option.
#### **2\. Private Cloud Hosting**
Here, the cloud infrastructure is dedicated to a single organization. It is more secure and customizable, making it popular with banks, healthcare providers, and government agencies.
#### **3\. Hybrid Cloud Hosting**
A hybrid setup combines public and private clouds. It gives businesses the flexibility and scalability of the public cloud while keeping sensitive data in a secure private environment.
### **Benefits of Cloud Hosting**
Cloud hosting offers several advantages that make it appealing to businesses and developers:
- **Scalability** – Resources can be added or removed instantly to match demand.
- **Reliability** – Redundant systems ensure high uptime and minimal downtime.
- **Global Reach** – Data centers in multiple regions provide faster delivery to users worldwide.
- **Efficiency** – Hardware resources are used optimally, reducing waste.
- **Lower Maintenance** – The provider manages updates, security, and physical infrastructure. With **xCloud**, businesses get automated updates and strong security protocols without extra effort.
### **Who Uses Cloud Hosting?**
Cloud hosting serves a wide range of needs, from personal projects to large-scale enterprise systems. Examples include:
- **eCommerce** **stores** that see seasonal or unpredictable traffic spikes
- **SaaS applications** that need to serve users globally
- **Blogs and media platforms** expecting steady growth in traffic and content
- **Startups and enterprises** looking for infrastructure that can expand quickly
- **Developers** who want a flexible environment without having to manage servers manually
Cloud hosting is especially valuable when uptime, speed, and growth potential are top priorities. With xCloud’s fully [**managed cloud hosting**](/managed-hosting/) solution businesses can confidently run high-performance websites knowing they have the power, scalability, and reliability to adapt as their needs evolve.
## **Key Differences: Cloud Hosting vs Traditional Hosting**
When deciding between **cloud hosting or traditional** hosting, you need to look at how they perform across several important factors. Each has its own strengths and weaknesses. The right choice depends on your specific needs.
Let us break down the core differences that really matter.
### **Scalability and Performance**
**Cloud hosting** offers unmatched scalability. If your traffic suddenly spikes, cloud servers automatically allocate more resources to keep your website running smoothly. You can scale up or down instantly based on your current demand. This flexibility is perfect for growing businesses or seasonal websites that see fluctuating visitors.
**Traditional hosting**, on the other hand, is much more limited. Whether you use shared, VPS, or dedicated hosting, you get a fixed amount of resources. If your site outgrows those limits, you must upgrade manually. And that upgrade may involve downtime or moving to a new server. If your site experiences an unexpected surge in visitors, traditional hosting may slow down or crash.
### **Reliability and Uptime**
Cloud hosting is built for reliability. Your website is hosted across multiple servers. If one server goes down, another takes over immediately. This redundancy helps maintain high uptime and prevents service interruptions. **Most cloud providers guarantee uptime of 99.9% or more.**
Traditional hosting relies on a single server. If something fails—like hardware, power, or network—it could take your entire website offline. Scheduled maintenance also affects availability unless your host has failover systems in place (which is rare in traditional hosting plans).
### **Security and Privacy**
Security is critical, no matter which hosting method you choose.
Cloud hosting providers usually have advanced security measures in place. These include firewalls, DDoS protection, regular patches, and monitoring. However, because the environment is shared across many clients, there can be concerns about data isolation. It becomes essential to choose a trusted provider and implement additional security layers on your side.
Traditional hosting offers more direct control over security. If you use a dedicated server, you manage everything—from firewall settings to encryption. This can be a big plus for businesses with strict compliance or privacy needs. But with more control comes more responsibility. You need in-house skills to handle server-level security.
### **Cost and Pricing Models**
This is where the two models differ most clearly. **Cloud hosting** uses a pay-as-you-go model. You are billed based on actual usage like how much storage, CPU, or bandwidth you use. This can be cost-efficient if your traffic varies or you need temporary resources. But if you are not careful, costs can rise quickly during high-traffic periods.
**Traditional hosting** uses fixed pricing. You pay a set monthly or yearly fee for a specific plan. It is easy to budget because you know your costs upfront. However, you may end up paying for resources you do not use or needing to upgrade if you run out of capacity.
### **Control and Customization**
Traditional hosting especially with a VPS or dedicated server—offers deep control. You can choose your OS, install custom software, and manage server settings directly. This is ideal for developers or IT teams who need specific configurations.
Cloud hosting usually comes with a managed interface. You can deploy and scale applications easily, but you may not get full access to the server environment. This makes cloud simpler to use but less customizable for complex needs.
### **Environmental Impact**
Cloud hosting is generally more eco-friendly. It makes better use of hardware through shared resources and energy-efficient data centers. Large cloud providers invest in green infrastructure, cooling systems, and renewable energy.
Traditional hosting can be less efficient. Individual servers often sit underused, wasting energy. Older data centers also consume more power.
When you compare cloud hosting and traditional hosting across these categories, it becomes clear they serve different needs. Neither is better for every situation. The best choice depends on what matters most to you—whether that is performance, cost, control, or long-term growth.
## **Benefits of Cloud Hosting**
Now that you understand how cloud hosting works and how it compares to traditional hosting, let us look at what makes cloud hosting such a powerful choice for modern websites and businesses.
Here are the most important benefits of choosing **cloud hosting over traditional hosting**.
### **1\. Instant Scalability**
One of the biggest advantages of cloud hosting is the ability to scale your resources in real time. If your site suddenly goes viral or you launch a new product, the system automatically adds more bandwidth, RAM, or processing power to handle the load. When traffic slows down, it scales down so you are not overpaying.
This level of flexibility is not possible with traditional hosting. There, you are stuck with a fixed set of resources unless you manually upgrade to a higher plan or move to a new server.
With cloud hosting, you are always ready to grow.
### **2\. High Availability and Uptime**
In a cloud hosting setup, your website is not tied to one server. Instead, it lives in a cluster of servers that work together. If one fails, another takes over immediately. This is known as redundancy, and it helps ensure your website stays online even during hardware or network failures.
Most cloud providers guarantee uptime of 99.9% or higher. That level of reliability gives peace of mind, especially for e‑commerce stores or businesses that cannot afford downtime.
By contrast, a traditional server going offline can mean hours of lost traffic and revenue.
### **3\. Better Performance and Speed**
Cloud hosting uses powerful infrastructure and often distributes your website’s content across multiple global locations. This means visitors get faster load times no matter where they are. Many cloud hosts also use load balancing to spread traffic across servers evenly.
Performance matters. Faster sites improve user experience, reduce bounce rates, and help with SEO rankings. With cloud hosting, you can deliver speed and stability to your users, even under high demand.
### **4\. Pay for What You Use**
Traditional hosting locks you into a fixed monthly or yearly fee. Whether you use all your resources or not, you still pay the same amount. Cloud hosting changes that.
With most cloud providers, you pay based on usage. If your site only needs light resources this month, your bill is lower. If traffic surges next month, you only pay for the extra power you used.
This is especially helpful for startups, growing businesses, or websites with unpredictable traffic.
### **5\. Lower Maintenance and Automation**
Cloud providers manage most of the technical details behind the scenes. You do not have to worry about server updates, hardware failures, or configuring backups. They handle it for you.
Most cloud platforms also offer tools to automate tasks like deployments, updates, and scaling. This frees up your time and lets you focus on your business or content instead of server issues.
With traditional hosting, especially dedicated or VPS, you often need to do more work yourself or hire someone to manage your server.
### **6\. Global Reach and Content Delivery**
Cloud platforms often offer multiple data center locations around the world. You can host your site closer to your audience to improve speed and reliability.
Many also integrate with content delivery networks (CDNs) that cache your site across different regions. This global setup is ideal if you serve international visitors or run a global brand.
### **7\. Built-In Tools and Modern Interfaces**
Cloud hosting platforms usually come with easy-to-use dashboards, built-in analytics, automatic backups, and one-click scaling. These tools help you manage your site without needing advanced technical skills.
In traditional hosting, many of these features require manual setup or third-party tools.
Cloud hosting is not just a trend. It is a better way to host websites in many cases. It gives you speed, flexibility, and peace of mind—all while being more cost-effective in the long run if used wisely.
## **Benefits of Traditional Hosting**
While cloud hosting offers modern advantages, traditional hosting still plays an important role. Many businesses choose it because of its simplicity, predictability, and control. Depending on your needs, it might actually be a better fit than cloud hosting.
Let us explore the major benefits of choosing **traditional hosting over cloud hosting**.
### **Predictable Pricing and Budget Control**
Traditional hosting plans come with fixed monthly or yearly prices. You pay a set amount for a defined package of resources. This makes it easy to manage your hosting budget.
For example, if you purchase a VPS plan with 4 GB RAM and 100 GB of storage, your bill stays the same regardless of how many visitors you get until you need to upgrade.
This level of financial predictability is useful for small businesses, nonprofits, or projects with a tight budget.
In contrast, cloud hosting charges vary based on usage. This can lead to unexpected costs if traffic spikes or if resources are not monitored carefully.
### **Greater Control and Customization**
Traditional hosting, especially dedicated hosting, offers full root access to the server. You can choose the operating system, configure software, manage security settings, and customize it exactly how you want.
This is important if you have specific software dependencies, compliance requirements, or want complete control over your environment.
For developers, system administrators, or tech-savvy businesses, traditional hosting gives freedom to fine-tune performance and security.
With cloud hosting, you often work within the provider’s system. There may be restrictions on software versions, admin access, or custom configurations.
### **Simplicity for Basic Needs**
If your website is small or has steady traffic, traditional hosting might be all you need. Shared hosting is especially affordable and easy to use. Many plans include website builders, email services, and one-click installers for WordPress or other CMSs.
You do not need to think about scaling, load balancing, or resource optimization. Just upload your files and go.
For personal blogs, portfolio sites, or basic business pages, traditional hosting can get the job done without overcomplicating things.
### **Dedicated Resources in Certain Plans**
With VPS or dedicated hosting, you get dedicated resources—CPU, RAM, and storage—that are not shared with other users. This gives you consistent performance and avoids the “noisy neighbor” problem common in shared or cloud environments.
This is especially useful for websites that need stability or run heavy applications, like streaming platforms or large databases.
### **Familiar Interfaces and Long-Term Support**
Most traditional hosting providers use familiar tools like cPanel or Plesk. These have been around for years and are widely supported. If you have experience with them, managing your site is easier.
Support teams for traditional hosting are also well-trained in resolving common issues, especially on shared and VPS servers. You may find faster and more personalized help if you stay within this more traditional setup.
### **Better for Compliance or Location-Sensitive Data**
Certain industries, such as finance, legal, and healthcare, must follow strict data regulations. Hosting data on a specific server in a known location may be required.
With traditional hosting, you can often choose the data center location and ensure that data never leaves that region. Cloud hosting sometimes makes this harder, especially when data is stored or backed up across multiple locations.
While cloud hosting is flexible and future-ready, traditional hosting still shines in its own ways. If your website needs are stable, your budget is fixed, or your project requires full server control, traditional hosting is a reliable and proven choice.
## **What Should You Choose?**
You have now seen the features, pros, and cons of both **cloud hosting and traditional hosting**. But how do you decide which one is best for you? The answer depends on your needs, your goals, and the kind of experience you want to create for your visitors.
Let us walk through a step-by-step approach to help you choose confidently.
### **Ask Yourself These Key Questions**
Before choosing between cloud and traditional hosting, ask yourself:
1. **What kind of website are you building?**Is it a blog, an online store, a business site, or a custom web app?
2. **How much traffic do you expect?**Will it stay consistent, or are traffic spikes likely?
3. **How fast do you expect to grow?**Do you need resources that can expand easily over time?
4. **What is your budget model?**Do you prefer fixed costs or can you manage usage-based billing?
5. **Do you have technical expertise or a server management team?**Will you manage the server yourself or rely on support?
6. **Are there any special requirements for data location, compliance, or customization?
**Does your site need to follow strict regulations or run specific software?
## **How to Decide Between Cloud and Traditional Hosting Based on Your Goals**
Your hosting choice depends on what matters most to your business. Think about your growth plans, traffic patterns, budget, and level of control to find the option that best supports your goals.
**Choose Cloud Hosting If:**
- You are building a site that will grow fast or unpredictably
- Your traffic varies from month to month
- You need high uptime and global performance
- You want to launch quickly without dealing with hardware or server setup
- You prefer automation and low maintenance
- Your project is digital-first or depends heavily on online presence
- You are comfortable with usage-based pricing
#### **Choose Traditional Hosting If:**
- Your website has consistent traffic and does not change much
- You prefer fixed pricing and want to avoid unexpected costs
- You need full control over your server environment
- You run legacy software or custom code
- You have the in-house team to manage your server
- You have strict compliance or location-based data policies
- You value predictability and simplicity in hosting
### **Still Not Sure? Go Hybrid or Start Small**
Some companies combine both hosting types. For example, they might use traditional hosting for their core services and cloud hosting for backup, scalability, or temporary traffic needs. This hybrid approach gives flexibility while keeping essential systems under full control.
Also, many providers offer entry-level cloud hosting plans that are affordable and easy to test. You can start small, then scale up as needed.
The choice between **cloud hosting or traditional** hosting is not one-size-fits-all. It is about what works best for your unique situation. Think about the kind of experience you want your users to have, how much control you need, and how you plan to grow.
## **Hosting for Every Scenario: How xCloud Hosting Fits Any Business**
In almost every real-world scenario, cloud hosting proves to be the smarter choice. A small local business might think traditional hosting is enough, but cloud hosting especially with **xCloud,** offers faster speeds, higher uptime, and the ability to scale effortlessly if traffic grows. For online stores, agencies, startups, or media companies, the benefits are even greater. Seasonal sales, multiple client websites, global app launches, and content-heavy platforms all demand flexibility, reliability, and performance that traditional hosting simply cannot match.
With **xCloud**, any type of site for any type of business can run smoothly and grow without limits. From compliance-focused enterprises to fast-moving startups, the platform provides secure infrastructure, [**vertical scaling**](/horizontal-scaling-vs-vertical-scaling/), and managed services that remove technical headaches. While traditional hosting still has a place for small, static projects, cloud hosting done right with **xCloud** is built for today’s demands and tomorrow’s growth.
## **Choose the Right One That is Built for Today, Ready for Tomorrow**
Choosing between cloud hosting and traditional hosting comes down to your goals, growth plans, and technical needs. While traditional hosting may suit basic, low-traffic websites, it often falls short when it comes to performance, scalability, and long-term flexibility.
Cloud hosting especially with xCloud offers the speed, reliability, and on-demand resources that modern websites need. Whether you run a small blog, a busy e-commerce store, or a growing SaaS platform, xCloud gives you the tools to scale confidently and run your site without limits.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# CloudFest 2025 Recap: xCloud’s First Appearance at the World’s Premier Cloud Event - xCloud
> xCloud made its debut at CloudFest 2025, joining the world’s top cloud innovators for four days of tech, talks, and transformative connections.
[**CloudFest 2025**](https://www.cloudfest.com/) – The _**#1 Cloud Conference**_ ends but its energy, innovation, and powerful connections continue to echo in the cloud ecosystem – and xCloud was proud to be a part of this mega event.
It was a milestone – a place of ideas, innovation, and an opportunity to meet at the global epicenter of cloud computing. And for [**xCloud Hosting**](/), this year was extra special. **We officially made our debut at CloudFest**, stepping onto the world stage with pride, passion, and purpose.
Held from March 17–20 at the spectacular **Europa-Park in Rust, Germany**, CloudFest once again brought together the brightest minds in the cloud and hosting industries. From hyperscalers and infrastructure providers to software innovators, SaaS platforms, domain registrars, and everything in between — if it lives in the cloud, it was represented at CloudFest.
And **this year, xCloud was one of them.**
## **xCloud’s First Visit To CloudFest: Memories & Experiences**
Being part of **CloudFest 2025** as a first-time participant was nothing short of exhilarating. Our mission was clear: connect, learn, and discuss what makes xCloud different — our commitment to robust, developer-friendly, performance-driven hosting that blends scalability with simplicity.
Leading the charge was our Founder, **M Asif Rahman**, a passionate entrepreneur, technologist, and community builder who has long been active in the open-source and WordPress spaces. His presence at CloudFest added both credibility and clarity to xCloud’s vision — a hosting platform built by developers, for developers.
From the very first day, we were immersed in an environment of energy and exchange. CloudFest is not just about sitting in conference rooms; it is about engaging in hallway conversations, sharing stories over coffee, and diving deep into the next generation of cloud solutions.
## **Highlights from Our CloudFest Journey**
Joining CloudFest for the first time was not just symbolic, we have long admired the role this event plays in shaping the cloud industry — and finally, we are excited to be a part of it. Here is a look at some key highlights from our first-ever participation:
### **🌐 A Global Meeting Ground**
CloudFest brings together **[attendees from more than 80 countries](https://www.cloudfest.com/attendee-profile)**. The diversity of perspectives and experiences shared was inspiring. From early-stage startups to tech giants, everyone came with an open mind and a shared mission: **_“_**_Push the boundaries of what is possible in the cloud”_**.**
We met with cloud infrastructure providers, software companies, cybersecurity experts, fellow hosting platforms, and entrepreneurs from all over the world. Whether in scheduled meetings or spontaneous chats, the connections we made were real and ripe with potential.
### **🎤 Insightful Keynotes & Technical Deep-Dives**
Sessions like **“AI in Cloud Management”**, **“The New Era of Green Infrastructure”**, and **“Decentralized Hosting and Web3”** gave us valuable insights into the trends shaping tomorrow. We also attended several **WordPress-related sessions**, given our strong roots in the WordPress community.
### **💬 Conversations & Collaborations**
We had **fruitful discussions** about strategic partnerships, possible integrations, and how we can help shape a better, more secure, and scalable web for the next generation. CloudFest is all about collaboration and creating the future.
M Asif Rahman engaged in several impactful conversations with industry veterans, tech leaders, and product builders. From discussing performance optimization techniques to sharing thoughts on scaling container-based architectures, these were not just casual meetups, they were **idea incubators.**
### **🥊 Unexpected Fun: A Boxing Ring in the Tech World?**
Yes, you read that right. CloudFest 2025 isn’t just about sessions and booths — it’s a full-blown experience. One of the most unforgettable sights? A full-size boxing ring in the middle of the expo floor, complete with mock matches, lighting effects, and roaring crowds. It was a bold metaphor for the competitive, high-energy nature of the tech world — and it brought a sense of excitement and edge that only CloudFest could pull off.
Around every corner, there were surprises: themed lounges, immersive booth designs, arcade setups, and even rollercoasters for those who dared to mix adrenaline with innovation. The entire venue at Europa-Park felt like a tech amusement park – vibrant, buzzing, and packed with possibility.
## **🚀 Learning from the Best**
We had the opportunity to explore **extraordinary solutions** in web security, DDoS mitigation, automation workflows, and container orchestration. These insights will directly influence our roadmap and help deliver an even more powerful hosting experience for our users.
> CloudFest is on a whole different level! Good to see WordPress being an important part of it. Alhamdulillah for the amazing growth of xCloud, we have tons more to do. Godspeed!
>
> – _M Asif Rahman_, Founder of xCloud
The sessions and discussions helped us sharpen our perspective on the evolving cloud landscape from AI-powered automation and edge computing to multi-cloud architectures and green hosting initiatives. Every insight collected is now a data point in how we evolve xCloud forward.
## **Thank You, CloudFest – See You in 2026!**
To everyone who visited CloudFest, talked with us, collaborated, or even just shared a smile – **THANK YOU**. Our first CloudFest was amazing. We return with stronger ideas, a bigger network, and renewed momentum to push xCloud forward. **CloudFest 2025 may be over, but the journey it inspired has only just begun.**
We are already looking forward to the next one! Until then, let us keep pushing boundaries, embracing collaboration, and celebrating the open-source community we are all a part of.
Stay tuned — the best of xCloud is on the horizon. 🚀
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Cloudflare CDN Enterprise: Make Your Website Faster and Secure With Global CDN Network - xCloud
> Cloudflare Enterprise CDN on xCloud: global edge caching, WAF and DDoS protection on any domain, managed entirely from your dashboard for $5/month.
The first time most site owners ask what Cloudflare Enterprise costs, the conversation ends fast. There is no price on the website, no checkout button, and the answer that eventually comes back is a sales call, an annual contract, and a number widely reported to start around $5,000 a month. So they settle for the free plan and move on, assuming Enterprise is for companies with a procurement department.
That assumption is now out of date. The xCloud Cloudflare Enterprise add-on attaches any domain to an Enterprise contract that already exists, for $5 per domain per month, with no contract of your own, no Cloudflare account, and no nameserver change.
This guide breaks down how the $5 price is possible, exactly what is included, how it compares with every other way of buying Cloudflare Enterprise in 2026, and how to switch it on in three steps.
**Key takeaways:**
- Cloudflare Enterprise is normally a negotiated annual contract with no public price. The xCloud add-on attaches your domain to xCloud’s existing contract as a custom hostname, which is the only reason $5 per domain is possible.
- The add-on includes the full Enterprise suite: CDN across 330+ cities, full-page edge caching, tiered caching, managed WAF, unmetered DDoS protection, rate limiting, image optimization, and analytics, all managed from the xCloud dashboard.
- Your DNS provider and nameservers stay exactly where they are. Setup is one CNAME record, and xCloud snapshots your DNS and restores it if you ever cancel.
- Only two hosts sell Cloudflare Enterprise per domain: xCloud at $5 and Cloudways at $4.99. Everyone else bundles it into hosting plans that require moving your sites onto their servers.
- Each domain includes 100 GB of bandwidth a month, then $0.02/GB prorated, with no hard cap and no forced upgrade.
## **What Is the Cloudflare Enterprise Add-on and Why Does a $5 Price Exist**
The Cloudflare Enterprise add-on is a fully managed, per-domain integration that puts your website on Cloudflare’s Enterprise network. Your domain joins xCloud’s Enterprise account as a custom hostname through Cloudflare for SaaS, so you get the Enterprise CDN, managed WAF, unmetered DDoS protection, and full-page edge caching for $5 a month per domain, with every setting controlled from the panel you already use.
You are not buying a plan. You are joining one. The cost is a share of a network already paid for rather than a new subscription, which is also why tiered caching and full-page edge caching are included here when they are paid extras or hand-written rules on Cloudflare’s own Pro and Business plans.
### **Why Speed and Edge Security Decide Your Site’s Fate**
The stakes are concrete. [**Research from Google**](https://www.thinkwithgoogle.com/marketing-strategies/app-and-mobile/mobile-page-speed-new-industry-benchmarks/) found that as page load time goes from one second to three, the probability of a visitor bouncing rises by 32 percent, and search engines weigh both speed and availability in rankings. On the security side, attacks do not wait for you to notice: bots and exploit scans hit servers daily, and a security plugin can only act after a request has already reached your origin and spent its CPU. Edge protection resolves both problems in the same place, before traffic ever touches your server. For the wider picture on what your host should be protecting, see our guide to [**web hosting security best practices**](https://xcloud.host/web-hosting-security-best-practices/).
## **How Much Does Cloudflare Enterprise Really Cost?**
Cloudflare does not publish an Enterprise price. It is sold as a negotiated annual contract, quoted per organisation on traffic, domain count, and add-on products, and entry-level deals are widely reported to start around $5,000 a month.
Here is how Cloudflare’s published self-serve plans compare, checked August 2026 at [**cloudflare.com/plans**](https://www.cloudflare.com/plans/):
**Plan**
**Price**
**What you get**
Free
$0
Static asset CDN, unmetered DDoS
Pro
$25/month per domain
Adds image optimization, fuller WAF ruleset
Business
$250/month per domain
Advanced WAF, prioritized support
Enterprise
Negotiated annual contract
Managed WAF rulesets, priority routing, tiered caching, custom hostnames
Tiered caching is a paid extra on all three self-serve plans, and none of them cache full HTML pages at the edge without you writing the rules yourself. On the [**xCloud Cloudflare Enterprise add-on**](https://xcloud.host/cloudflare/), both are included in the $5.
## **Every Way to Get Cloudflare Enterprise, Compared**
There are exactly three routes to Cloudflare Enterprise today: hosts that bundle it free while you host with them, hosts that sell it per domain, and Cloudflare directly. Prices checked August 2026.
**xCloud add-on**
**Bundled hosting (Kinsta, 10Web, BigScoots, Convesio, Levamo)**
**Cloudways add-on**
**Cloudflare direct**
Price
$5/month per domain
$23 to $50/month hosting plans
$4.99/month per domain, $1.99 above 25 domains
$250/month (Business); Enterprise negotiated
Runs on servers you own
Yes (DigitalOcean, AWS, Vultr, Hetzner, Linode, or managed xCloud)
No, their platform only
No, their platform only
Yes
Any stack
Yes: WordPress, WooCommerce, Laravel, static, PHP
Mostly WordPress
WordPress and Woo
Yes
Keep your DNS and nameservers
Yes, one CNAME
Varies
Yes
No, DNS moves to Cloudflare
DNS set up for you and restored on cancel
Yes
n/a
Manual CNAME both ways
No
Custom cache bypass paths per site
Yes
Varies
No
Manual rules
Contract
None, cancel per domain any time
Tied to hosting
None
Annual (Enterprise)
Where the alternatives win, honestly: Cloudways offers a 30-day trial and drops to $1.99 per domain above 25 domains, and it has automatic selective cache purging, which xCloud does not have yet. The bundled hosts charge no line item at all, as long as your sites live on their servers, which is exactly the lock-in the free bundle is designed to create. For a wider look at how the two platforms compare beyond this add-on, see the [**xCloud vs Cloudways comparison**](https://xcloud.host/xcloud-vs-cloudways/).
## **What You Get for $5 per Domain**
Everything below runs on Cloudflare’s Enterprise tier and is included in the flat price.
### **1\. Global CDN across 330+ cities**
Static assets and full HTML pages are served from whichever Cloudflare location is closest to your visitor, instead of a round trip to your server. Every continent loads from the nearest edge, not from one distant origin.
### **2\. Full-page edge caching**
Whole HTML pages are cached at the edge, so time-to-first-byte stops depending on your server at all. This is the feature that moves real load times rather than just offloading images, and it is a paid extra or a hand-written rule everywhere below the Enterprise tier.
### **3\. Tiered caching**
Nearby data centres share what they have already fetched instead of each asking your origin separately, cutting origin requests by up to 60 percent.
### **4\. Enterprise managed WAF**
Cloudflare-managed rulesets sit in front of your site and drop OWASP-class attacks, exploit scans, and zero-days before they arrive. If you want to tune it, here is how to [**enable Cloudflare WAF rules in xCloud**](https://xcloud.host/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/).
### **5\. Unmetered DDoS protection**
Volumetric attacks are absorbed at the edge at layers 3, 4, and 7, with no surcharge and no cap, by one of the largest networks on the internet. For emergencies, [**Under Attack Mode**](https://xcloud.host/docs/how-to-turn-on-cloudflare-under-attack-mode/) adds an extra check for every visitor.
### **6\. Rate limiting, browser integrity check, and AI crawler blocking**
Requests are counted per IP in 60-second windows, with a managed challenge above the threshold. The default is 200 requests a minute and can be customised for your domain via support ticket. Known AI crawlers can be blocked from scanning or collecting your content with one toggle.
### **7\. Everything managed from the xCloud dashboard**
There is no second dashboard and no Cloudflare account to create. Traffic, cache, and security analytics run from the last 30 minutes back to 30 days, with top pages, countries, devices, and IPs, plus one-click worldwide cache purge, image optimization, SSL cipher profiles, ScrapeShield email obfuscation, and managed edge SSL on every domain. Timeouts run at 200 seconds and can be raised per use case up to Cloudflare’s 6,000-second limit. If you need visitor IPs in your server logs, here is how to [**show real visitor IPs behind the Cloudflare proxy**](https://xcloud.host/docs/show-visitor-real-ip-behind-cloudflare-proxy/).
## **Activate the Cloudflare Enterprise Add-on in 3 Steps**
Setup is not a migration. Your DNS provider stays where it is, your nameservers stay where they are, and one record changes.
1. **Enable the add-on:** In your xCloud dashboard, open Addons, find Cloudflare Enterprise, hit Enable, pick the domain from the dropdown, and pay. $5 for the month, no contract attached.
2. **Add one CNAME record:** xCloud shows you the exact record to add at your existing DNS provider. The domain joins xCloud’s Cloudflare account as a custom hostname while your DNS host stays unchanged.
3. **Refresh, and you are live:** The domain status flips to Active with sensible defaults already on. The Settings tab is there whenever you want to change caching, WAF, or anything else.
If your DNS already sits in a Cloudflare account connected to xCloud, the records are applied for you automatically. And if you ever cancel, xCloud restores your DNS from the snapshot it took at setup, reinstating your previous SSL. The full walkthrough is in the guide to [**activating the Cloudflare Enterprise add-on**](https://xcloud.host/docs/how-to-activate-the-cloudflare-enterprise-addon/).
## **Who Should Enable It**
- **WooCommerce stores:** Product pages served from the edge, carts and checkout kept dynamic, WAF in front of payments. Pairs naturally with [**WooCommerce hosting**](https://xcloud.host/woocommerce-hosting/) built for high-traffic checkouts.
- **Agencies and freelancers:** Enable it per client site and rebill it as a line item, at a price that leaves room for margin.
- **Content and media sites:** Heavy pages served worldwide from the edge, with AI crawlers blocked from scraping them.
- **Launch and campaign sites:** Traffic spikes absorbed at the edge, so your origin stays calm through launch day.
- **Membership and SaaS:** Rate limiting and Under Attack Mode keep logged-in experiences fast and protected.
The caching is WordPress and WooCommerce aware out of the box: logged-in sessions, wp-admin, the REST API, carts, checkout, my-account, feeds, and sitemaps are bypassed automatically, so shoppers never see someone else’s basket, and you can add your own bypass paths per site. It also runs on Laravel, static sites, and custom PHP, on [**managed**](https://xcloud.host/managed-hosting/) or [**self-managed**](https://xcloud.host/self-managed-hosting/) servers alike.
## **Put Your Site on Cloudflare Enterprise for $5 Today**
Cloudflare Enterprise used to be a decision made for you: either sign an annual contract, or move your sites to a host that bundles it as a lock-in. The xCloud add-on removes both conditions. It runs on infrastructure you own, follows the site if you change providers, and switches off per domain whenever you want. Enable it on one site, watch the cache ratio and security events in the Analytics tab for a week, and decide with your own numbers.
We hope this guide helped you understand exactly how Cloudflare Enterprise pricing works and how to get it without the contract. Now, [**enable the Cloudflare Enterprise add-on**](https://app.xcloud.host/addons/cloudflare-enterprise) on a domain and let us know your experience in the [**xCloud Facebook community**](https://www.facebook.com/groups/xcloud.community). Also, do not forget to [**subscribe to our blog**](https://xcloud.host/blog/) to get updates, helpful resources, and more.
## **Frequently Asked Questions**
### **How much does Cloudflare Enterprise cost?**
Cloudflare does not publish an Enterprise price. It is a negotiated annual contract quoted per organisation, with entry-level deals widely reported to start around $5,000 a month. The xCloud add-on attaches your domain to an existing Enterprise contract for $5 per domain per month, with no contract or Cloudflare account of your own.
### **Is there a free trial?**
Not at the moment. At $5 per domain with no contract you can enable it on your own site and cancel whenever you want, but billing starts straight away, and add-ons are non-refundable once activated.
### **Does the price include subdomains?**
One subscription covers the root domain and its www version. Other hostnames like shop.example.com or app.example.com are separate $5 subscriptions, so you enable only the ones that need it and remove any single one without touching the rest.
### **Is bandwidth unlimited?**
Each subscription includes 100 GB per month, which covers the vast majority of WordPress sites since edge caching means most requests never reach your server. Beyond that, usage is billed at $0.02/GB, prorated, with data transfer visible in the add-on’s Analytics tab. No hard cap, no forced upgrade.
### **Is this the same CDN as Cloudflare’s free plan?**
Same network, higher tier. Free and Enterprise both serve from 330+ cities, but Enterprise adds managed WAF rulesets, priority routing, tiered caching, and full-page HTML caching, the things that move time-to-first-byte rather than just offloading images.
### **Do I need to move my nameservers or DNS?**
No. The add-on runs on Cloudflare for SaaS as a custom hostname, so your registrar and DNS provider stay exactly where they are and you add one CNAME record. That is the key difference from signing up with Cloudflare directly, which expects your nameservers to move.
### **Will it affect my SEO?**
It should help. Search engines weigh page speed and availability, and this improves both: pages come off the edge, and the WAF and DDoS mitigation keep the site reachable during attacks that would otherwise take your server, and the crawler, offline.
---
# Using Cloudflare Firewall Rules to Secure Your Web App - xCloud
> Discover how to enhance your web app security with Cloudflare firewall rules with a simple guide to protect your site from cyber threats effectively.
Web application security is getting more and more important with the rapidly evolving technology. Website owners need robust security measures to protect their web apps and sensitive data with the increasing number of cyber threats.
One powerful tool for enhancing web app security is Cloudflare which is a Google product. Cloudflare provides an array of services designed to [**improve website performance**](/advanced-redis-object-caching-for-wordpress/), security, and safeguarding web applications. Today, we will explore how **Cloudflare firewall rules** can help secure your web app and best practices to protect your web applications without any hassle.
## 🍀**Understanding Cloudflare Firewall Rules**
Web application security is important nowadays. With ever-evolving [**cyber threats**](https://wpdeveloper.com/biggest-cyber-security-mistakes/), having a reliable line of defence is essential. This is where Cloudflare firewall rules come into play. Let us discuss what firewall rules are, how they work, and why they are vital for securing your web app.
### 🔆**What Are Cloudflare Firewall Rules?**
Cloudflare firewall rules are a powerful set of configurations that allow you to define precise security measures for incoming traffic to your web application. These rules act as filters that control which requests can access your site based on specific conditions you set. By utilizing these rules, you can manage and mitigate various types of threats, enhancing the security of your web application.
### 🔆**How Do Cloudflare Firewall Rules Work?**
[**Cloudflare firewall rules**](https://developers.cloudflare.com/firewall/cf-firewall-rules/) operate at the application layer of the **Open Systems Interconnection (OSI)** model. This means they focus on the specifics of incoming **HTTP requests** to your site, allowing you to filter traffic based on criteria such as IP address, country of origin, URL patterns, and more.
When a request is made to your site, the firewall rules are evaluated sequentially based on their priority. Each rule consists of a matching condition and an action to perform if the condition is met. Actions can include allowing, blocking, challenging, or logging the request.
### 🔆**Why Use Cloudflare Firewall Rules for Web App Security?**
Firewall rules is an effective way to secure your web application with setting up rules to secure your web applications for several reasons:
- **Granular Control:** The rules allow you to create highly specific conditions, giving you granular control over the traffic that reaches your site.
- **Scalability:** Cloudflare’s infrastructure is built to handle massive [**amounts of traffic**](https://wpdeveloper.com/how-to-check-website-traffic-for-any-site/), making their firewall rules scalable for websites of all sizes.
- **Performance:** The rules are evaluated at Cloudflare’s edge servers, which means they do not affect your site’s performance.
- **Ease of Use:** Cloudflare provides an intuitive user interface and extensive documentation, making it easy to set up and manage firewall rules.
Firewall rules offer a robust and flexible solution for web app security, providing website owners with the tools they need to protect their sites from malicious traffic and other potential threats.
## **3 Easy Steps Guide to Set Up Cloudflare Firewall Rules**
Setting up a Cloudflare rule could be a challenging task. There are many firewall rules for WordPress. We will discuss here how to **block particular countries from visiting your site**. You can block one country or as many as you want. You can also allow access to your website to only one country. For example, we will block visitors from all countries except the USA. So follow the steps below:
### **Step 1: Log in to Cloudflare Choose Your Domain**
Start with logging in to your Cloudflare dashboard. From here, choose the domain name for which you want to set up the firewall rule with Cloudflare
After selecting the domain that you want to secure more or applying the firewall rules, find the **‘Firewall’** button from the top bar and click on it.
### **Step 2: Create a Firewall Rule with Cloudflare**
Here, you can see a **‘Create a Firewall rule’** button, hit on the button to create a new firewall rule.
### **Step 3: Block All Countries Except the USA**
From here, we must need to provide the necessary information. First, give a ‘Rule name’ according to your choice.
Then head on to the **‘Field’** section and choose **‘Country’** from the dropdown and set the **‘Operator’** does not equal. Next, go to the **‘Value’** and choose USA as your country.
Finally, from the action drop-down, select **‘Block’**, and then click on the Deploy button.
There are different types of firewall rules you can use for different purposes. You can set them up easily and make your site more secure than ever.
## ⛳ **Benefits of Using Firewall Rules with Cloudflare**
Cloudflare’s firewall rules are not just another security feature, they offer many benefits that make them an essential tool for any website owner. Let us dive into the **key advantages of using firewall rules with Cloudflare** to secure your web application.
### 🔆 **Enhanced Security**
Security is paramount for any web application, and Cloudflare firewall rules provide robust protection against a wide range of threats. By allowing you to set specific conditions to filter incoming traffic, the rules help defend against common attacks like **DDoS, SQL injection,** **cross-site scripting**, and more. This proactive defense mechanism ensures that your website remains secure even as threats evolve.
### **🔆 Ease of Use**
One of the standout features of Cloudflare firewall rules is their ease of use. Cloudflare provides an intuitive dashboard that simplifies the process of creating and managing rules. Even if you are not a seasoned IT professional, you can easily set up and adjust firewall rules to suit your needs. The user-friendly interface ensures that website owners can take control of their security without needing extensive technical expertise.
### 🔆 **Customization**
Every web application is unique, and Cloudflare recognizes this by offering highly customizable firewall rules. You can set conditions based on a variety of parameters, such as **IP address**, **HTTP methods, and country of origin**. This level of customization allows you to tailor the security settings to match your specific requirements, ensuring that you only allow legitimate traffic while blocking potential threats.
### 🔆 **Real-Time Analytics**
Another significant benefit of using firewall rules is the access to [**real-time analytics**](https://wpdeveloper.com/blogging-statistics-trends-data-ultimate-list/). Cloudflare provides detailed reports on traffic and security events, allowing you to monitor and analyze incoming requests. This visibility helps you understand the nature of threats targeting your web application and adjust your security measures accordingly. The analytics also provide insights into the effectiveness of your firewall rules, enabling you to fine-tune your configurations for optimal protection.
### 🔆 **Performance Optimization**
Cloudflare’s infrastructure is designed for high performance, and the firewall rules are no exception. The rules are processed at Cloudflare’s edge servers, which means that your web application’s performance is not impacted. This edge-based processing ensures that malicious traffic is filtered out before it even reaches your server, optimizing your application’s performance while maintaining security.
### 🔆 **Scalability**
Whether you are running a small [**personal blog**](https://blog.templately.com/start-personal-food-blog-guide/) or a large e-commerce platform, Cloudflare firewall rules are scalable to meet your needs. Cloudflare’s global network is built to handle massive amounts of traffic, so you can be confident that your web application will remain secure even during traffic spikes or large-scale attacks.
## ⛳ **Best Practices for Using Cloudflare Firewall Rules**
Using firewall rules is an effective way to secure your web application, but it is essential to follow best practices to maximize their effectiveness and minimize potential issues. Here, we will discuss key strategies and tips for using firewall rules with Cloudflare effectively.
### 🔆 **Whitelist Trusted IPs**
Whitelisting trusted IP addresses ensures that your key stakeholders, such as employees or partners, always have access to your site. This is particularly useful for internal users who need consistent access. Start by identifying the IP addresses that should have unrestricted access to your web application. Once identified, create a firewall rule that allows traffic from these trusted IPs and set it as a high-priority rule. This ensures that these IPs are always permitted access, preventing unnecessary disruptions.
### 🔆 **Block Malicious Traffic**
One of the primary functions of firewall rules is to block malicious traffic. Cloudflare simplifies this by providing analytics and threat intelligence. Use Cloudflare’s tools to identify sources of malicious traffic. Based on your findings, create rules that [**block malicious traffic**](https://wpdeveloper.com/how-to-block-ip-address-in-wordpress/) from these sources, such as specific IP addresses or user agents. This helps keep your application secure from known threats.
### 🔆 **Rate Limiting**
Rate limiting prevents abuse of your web application, such as brute force login attempts or scraping. Determine which parts of your web application are most sensitive to excessive requests, like login pages or API endpoints. Set up firewall rules to limit the number of requests per minute from a single IP address. You can choose to either block or challenge requests that exceed this limit, helping to protect your application from overload and abuse.
### 🔆 **Monitor And Adjust Rules**
Regular monitoring and adjustment of your firewall rules are crucial for maintaining optimal security. Use Cloudflare’s analytics to keep an eye on incoming traffic and spot potential issues or unusual patterns. Based on your monitoring, adjust the rules to respond to new threats or optimize existing protections. This ensures your firewall rules remain effective and up-to-date.
### 🔆 **Leverage Managed Rulesets**
Cloudflare offers managed rulesets that provide protection against common threats, such as SQL injection and cross-site scripting. In your firewall settings, enable relevant managed rulesets for your web application. If necessary, customize these rulesets to better fit your specific needs, providing tailored protection against common threats.
### **🔆 Test Your Rules**
Before fully implementing new firewall rules, it is crucial to test them to ensure they don’t unintentionally block legitimate traffic. Cloudflare offers a preview mode that shows how the rule will behave without actually blocking or challenging traffic. When enabling new rules, monitor their effects closely and be ready to adjust them if they impact legitimate users. This cautious approach helps avoid disruptions to valid traffic.
### 🔆 **Document Your Rules**
Proper documentation of your firewall rules helps maintain clarity and facilitates future adjustments. Give each rule a descriptive name that reflects its purpose. Document the conditions and actions of each rule, as well as the rationale behind them. This makes it easier to manage and update your firewall rules over time.
## ⛳ **Common Use Cases for Cloudflare Firewall Rules**
Cloudflare firewall rules are versatile tools that can be used to address a variety of security and traffic management needs. In this section, we will look at several common use cases for these rules and how they can enhance the security and functionality of your web application.
### 🔆 **DDoS Protection**
**Distributed Denial of Service (DDoS)** attacks are a prevalent threat to web applications, overwhelming servers with a flood of traffic. Firewall rules can help mitigate these attacks in a couple of ways. First, you can block known attack sources by using firewall rules to block IP addresses or networks that are known to participate in DDoS attacks. Additionally, you can implement rate-limiting rules to restrict the number of requests from individual IP addresses or networks, limiting the impact of DDoS attacks.
### 🔆 **Preventing SQL Injection**
[**SQL injection**](https://wpdeveloper.com/fortify-wordpress-site-from-sql-injection-9-ways/) is a common web application attack where malicious SQL statements are inserted into an entry field for execution. Firewall rules can help prevent this by blocking requests containing common SQL injection patterns, such as SELECT and UNION keywords combined with specific characters. Moreover, you can use Cloudflare’s managed rulesets to block known SQL injection techniques automatically.
### 🔆 **Blocking IPs or Countries**
Sometimes, you may want to restrict access to your web application based on IP addresses or geographic regions. Cloudflare makes this straightforward. You can create rules to block traffic from specific IP addresses or ranges that are known to be malicious or unwanted. Additionally, you can use firewall rules to block or allow traffic from specific countries based on your business needs or security concerns.
### 🔆 **Custom Access Control**
Cloudflare firewall rules offer the flexibility to implement custom access control based on various criteria. For instance, you can create rules that restrict access to specific URLs or URL patterns based on criteria such as IP address, user agent, or HTTP method. You can also use firewall rules to restrict access to sensitive areas of your website, such as administrative pages, by IP address or other identifying characteristics.
### 🔆 **Protecting APIs**
APIs are often targeted by malicious actors seeking to exploit vulnerabilities or overload the system. Firewall rules can help protect your APIs by restricting access based on IP address, API key, or other identifying factors. Additionally, you can implement rate-limiting rules to prevent abuse of your APIs and ensure fair usage.
### 🔆 **Enforcing User Agent Policies**
User agents identify the client making a request, and firewall rules can be used to enforce policies based on this information. You can create rules to block requests from known malicious or suspicious user agents or allow only specific user agents if your web application is intended for specific clients.
These rules provide versatile solutions for a wide range of use cases, including DDoS protection, preventing SQL injection, blocking specific IPs or countries, custom access control, protecting APIs, and enforcing user agent policies. By leveraging these use cases, you can [**enhance the security**](https://wpdeveloper.com/backup-wordpress-site/) and functionality of your web application.
## ⛳ **Troubleshooting Firewall Rules and Tips to Manage**
Despite the best planning and implementation, issues may arise when using firewall rules. Here, we will explore common problems and provide debugging tips so that you already know how to resolve the issues if they arise.
### 💠 **Common Issues**
There are many problems that could arise, which is making problems. From many, these are the common [**troubleshooting issues**](https://wpdeveloper.com/502-bad-gateway-error/) we are discussing below:
- **Legitimate Traffic Blocked:** One common issue is when legitimate traffic gets blocked unintentionally. This often happens when rules are too broad or too strict.
- **Unexpected Behavior:** Sometimes, firewall rules might not behave as expected, often due to rule precedence issues or overlapping conditions.
- **Performance Impact:** While rare, firewall rules can sometimes impact site performance if they are misconfigured or overly complex.
### 💠 **Debugging Tips**
Check out these debugging tips so that you can ensure the firewall rules you have created run smoothly without making problems further:
- **Use the Firewall Analytics:** Cloudflare provides detailed analytics for its firewall, showing which rules are triggered and how often. Use this to identify problem rules.
- **Review Rule Order:** Cloudflare evaluates firewall rules in order of priority. Review the order of your rules to ensure that higher-priority rules do not unintentionally override lower-priority ones.
- **Test with Preview Mode:** Before fully enabling a rule, use Cloudflare’s preview mode to test how it will behave with incoming traffic. This helps catch issues before they impact real users.
- **Adjust Rule Conditions:** If a rule is blocking legitimate traffic, consider refining the conditions to be more specific. For example, instead of blocking all traffic from a country, you might block specific IP ranges or use rate limiting.
- **Check Rule Actions:** Make sure the actions for your rules are appropriate. For example, if you are testing a new rule, you might want to log traffic rather than block it outright.
## **🥷 Setup Cloudflare Firewall Rules & Secure Your Web App**
Cloudflare firewall rules are a vital tool for any website owner looking to enhance the security of their web application. With their flexibility, customisation options, and powerful analytics, these rules provide a robust defense against a wide range of threats. By following best practices and troubleshooting issues effectively, you can leverage Cloudflare firewall rules to keep your web application secure and running smoothly.
If you find this blog helpful and want to read more blogs like this one, [**Subscribe**](/blog/) to our blogs and Join our [**Facebook Community**](https://www.facebook.com/groups/xcloud.community) to connect with more people with common interests.
---
# Cloudflare Enterprise CDN Pricing — $5 per Domain | xCloud
> Cloudflare Enterprise CDN, WAF and DDoS protection for $5 per domain per month. Compare it against Cloudflare's Free, Pro ($25) and Business ($250) plans — no Cloudflare account, no nameserver change, managed from your xCloud dashboard.
## Cloudflare Enterprise CDN for $5 a domain
Cloudflare's Enterprise tier normally means a contract negotiated at volume, priced in the thousands per month. xCloud already holds one — so you can put a single domain behind it for five dollars. Global CDN across 330+ cities, full-page edge caching, managed WAF and unmetered DDoS protection, switched on from the dashboard you already use.
No Cloudflare account · No nameserver change · No contract — cancel any domain, any time
| | |
|---|---|
| 330+ | Cloudflare cities serving your pages |
| Full-page | HTML cached at the edge, not just assets |
| Up to 60% | Fewer requests hitting your origin |
| Unmetered | DDoS mitigation at layers 3, 4 and 7 |
The traffic path: your visitor → the Cloudflare Enterprise edge (330+ cities, WAF, DDoS, full-page cache) → your server on xCloud. Cache hits are served at the edge and attacks are dropped there; only what's left reaches your origin. Every switch on that middle layer lives in your xCloud dashboard — no Cloudflare account, no second login.
## Cloudflare Enterprise pricing, flat per domain
**$5 per domain, per month.** Each subscription covers one domain, and subdomains count as their own domain. Enable the ones that need it, manage them together on the Addons page, and remove any one of them without touching the rest. Includes 100 GB of bandwidth a month; beyond that it's $0.02/GB, prorated.
Included on every enabled domain:
- Cloudflare Enterprise network, 330+ cities
- Full-page edge caching and static CDN caching
- Tiered caching across Cloudflare's network
- Enterprise managed WAF and unmetered DDoS
- 100 GB bandwidth per month, then $0.02/GB
- Image optimization, Early Hints, ScrapeShield
- Traffic, cache and security analytics in-panel
- One-click worldwide cache purge
- Per-domain billing — remove a domain any time
No free trial, and add-on purchases are non-refundable once activated — check the domain and billing details before you subscribe. There's no contract and no minimum term.
[Get started](https://app.xcloud.host/register)
## Every other way to get Cloudflare Enterprise
Six hosts bundle it free — as long as you move your sites onto their servers. One other sells it per domain. Here is the whole picture, including the rows where we come off worse.
| | xCloud add-on (on servers you own) | Bundled hosting (Kinsta, 10Web, Levamo, BigScoots, Convesio) | Cloudways (add-on, on their platform) | Cloudflare direct |
|---|---|---|---|---|
| Runs on your own cloud account | Yes | Their platform | Their platform | Yes |
| Any stack — WordPress, Laravel, static, PHP | Yes | Mostly WordPress | WordPress & Woo | Yes |
| Custom cache bypass paths, per site | Yes | Varies | — | Manual rules |
| Bandwidth included, per domain | 100 GB, then $0.02/GB | Plan limits | Quota, then $0.02/GB | Yes |
| Full-page caching at the edge | Yes | Yes | WordPress & Woo | Manual rules |
| Keep your DNS provider and nameservers | Yes | Varies | Yes | — |
| DNS set up for you, and restored on cancel | Yes | n/a | Manual CNAME | — |
| Switch it off per domain, any time | Yes | Change host | Yes | Annual contract |
| No separate Cloudflare account | Yes | Yes | Yes | — |
| Volume discount | $5 flat | n/a | $4.99 | Negotiated |
| Automatic selective cache purge | — | Varies | Yes | Varies |
| **Pricing** | **$5/month per hostname — root and www together — 100 GB included, then $0.02/GB** | $23–$50/month hosting plan — Cloudflare included only while you host there | $4.99/month per hostname — plus $0.02/GB once the bandwidth quota runs out | $250/month per domain — add-ons billed separately — Enterprise on annual contract |
xCloud and Cloudways bill the same way: per hostname, with the root domain and its www counted together, and every other hostname its own subscription. Cloudflare direct bills per zone, so subdomains are covered by the one plan — the single thing that route does more cheaply, at fifty times the price. Cloudways falls to $1.99 per domain only above 25 domains.
The xCloud price is the add-on, on top of the plan you already have. Bundled figures are each host's cheapest plan carrying Cloudflare Enterprise — 10Web $23, Levamo $29, BigScoots $35, Kinsta $35, Convesio $50 — and Cloudflare's are its published month-to-month rates. All checked 4 August 2026, with Cloudways verified in a live account. See [cloudflare.com/plans](https://www.cloudflare.com/plans/).
### How much does Cloudflare Enterprise cost?
Cloudflare doesn't publish an Enterprise price. It's sold as a negotiated annual contract, quoted per organisation on traffic, domain count and which add-on products you want, and entry-level deals are widely reported to start around $5,000 a month. That's the tier this add-on runs on — you're joining xCloud's existing contract as a custom hostname rather than signing one of your own, which is the only reason a per-domain price of $5 is possible.
### What about the Free, Pro and Business plans?
Cloudflare's free plan gives you CDN caching for static assets and unmetered DDoS protection, which is genuinely good and enough for many sites. Pro is $25 a month per domain and adds image optimization and a fuller WAF ruleset. Business is $250 a month per domain. Tiered caching is a paid extra on top of all three, and none of them cache full HTML pages at the edge without you writing the rules yourself.
### Do I have to move my DNS or nameservers?
No — and this is where the add-on differs from signing up to Cloudflare directly. Their own plans expect you to move your domain's nameservers to Cloudflare and run DNS there. This runs on Cloudflare for SaaS instead: your domain joins xCloud's account as a custom hostname, so your registrar and DNS provider stay exactly where they are and you add one CNAME record.
### Is this the same CDN as Cloudflare's free one?
It's the same network, on a higher tier. Free and Enterprise both serve from 330+ cities, but Enterprise adds the managed WAF rulesets, priority routing, tiered caching, and full-page edge caching for WordPress and WooCommerce — the things that move time-to-first-byte rather than just offloading images.
### Some hosts include Cloudflare Enterprise free. Why pay $5?
Because free comes with their servers attached. Kinsta, Rocket.net, Levamo, 10Web, Convesio and BigScoots all bundle Cloudflare Enterprise at no line-item cost, and every one of them requires you to host with them to get it — it's a reason to stay, which is what it's designed to be. The xCloud add-on runs on infrastructure you own: your DigitalOcean, AWS, Vultr, Hetzner or Linode account, or a managed xCloud server, whichever you already chose. If you move providers next year the add-on moves with you. $5 a domain is what it costs to not have that decision made for you.
### How does this compare to the Cloudways add-on?
Cloudways is the only other host selling Cloudflare Enterprise per domain, at $4.99 falling to $1.99 above 25 domains, and they offer a 30-day trial where we don't. On list price and billing unit the two are effectively the same — both charge per hostname with the root domain and its www counted together, and both meter bandwidth per domain at $0.02 per gigabyte beyond the included quota. What differs is everything around it. We set your DNS up automatically and put it back the way we found it if you cancel, reinstating your previous SSL, where theirs is a manual CNAME both ways. You can add your own cache bypass paths per site; their documentation says custom cookie exclusion is currently unavailable. Their edge page caching is limited to WordPress and WooCommerce, while ours also runs on Laravel, static sites and custom PHP. And ours runs on infrastructure you own rather than on their platform. Where they're ahead: the free trial, the volume pricing, and automatic selective cache purging, which we don't have yet.
Related reading: [Activating the add-on](/docs/how-to-activate-the-cloudflare-enterprise-addon/) · [Enabling WAF rules](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/) · [Under Attack Mode](/docs/how-to-turn-on-cloudflare-under-attack-mode/) · [Cloudflare DNS management](/docs/using-xcloud-with-cloudflare-for-dns-management/) · [Visitor IPs behind the proxy](/docs/show-visitor-real-ip-behind-cloudflare-proxy/)
## Faster pages, blocked attacks, and one place to see both
Every feature below runs on Cloudflare's Enterprise tier.
### Performance — your site loads from the city your visitor is in
Static assets and full HTML pages are served from whichever of Cloudflare's 330+ locations is closest, instead of a round trip to your server. Tiered caching keeps neighbouring data centres sharing what they've already fetched rather than each one asking your origin separately, cutting origin requests by up to 60%.
- **Global CDN** — content served from 330+ Cloudflare cities worldwide.
- **Edge page caching** — whole HTML pages cached at the edge, so time-to-first-byte stops depending on your server.
- **Static content caching** — images, CSS and JavaScript across the global CDN with one toggle.
- **Tiered caching** — nearby data centres share what they've already fetched instead of each asking your origin.
- **Early Hints (103)** — browsers start preloading critical assets before the final response arrives.
- **WooCommerce-aware caching** — carts, checkout and logged-in sessions bypass the cache automatically.
### Security — attacks stop at the edge, not on your server
A security plugin can only act once the request has already reached your origin and spent its CPU. Cloudflare's managed WAF rulesets sit in front of the site and drop OWASP-class attacks, exploit scans and zero-days before they arrive. Volumetric DDoS is absorbed by one of the largest networks on the internet — unmetered, at layers 3, 4 and 7.
- **Enterprise WAF** — Cloudflare-managed rulesets catching emerging threats, including zero-days.
- **Unmetered DDoS** — volumetric attacks dropped at the edge at layers 3, 4 and 7, no surcharge, no cap.
- **Rate limiting** — managed challenges for IPs that exceed the request threshold.
- **Browser integrity check** — requests with suspicious or missing HTTP headers are blocked.
- **Under Attack Mode** — every visitor passes an extra check before reaching the site.
- **AI crawler blocking** — stop known AI crawlers scanning or collecting your content.
- **Managed edge SSL** — Cloudflare edge certificates on every domain, with live status in your domain table.
### Control & insight — all of it inside the panel you already use
There is no second dashboard and no Cloudflare account to create. Every toggle, every purge and every report lives in xCloud, next to the server and site they belong to. Traffic, cache performance and security events go back as far as 30 days and as fine as the last 30 minutes — top pages, countries, devices and IPs — and cache purges go out worldwide from the Overview tab.
- **One-click purge** — push an update live worldwide from the Overview tab.
- **Traffic analytics** — requests and data transfer from the last 30 minutes to the last 30 days.
- **Cache analytics** — see what's being served from the edge and what still reaches your origin.
- **Security events** — every block and challenge, with the top pages, countries, devices and IPs behind them.
- **Image optimization** — Polish-style compression, lossy, lossless or off, per site.
- **SSL cipher profiles** — choose the cipher suite used between visitors and the edge.
- **ScrapeShield** — email addresses obfuscated so bots can't harvest them.
## Live in three steps, not a migration
Your DNS provider stays where it is. Your nameservers stay where they are. One record changes.
1. **Enable the add-on** — in your xCloud dashboard, open Addons, find Cloudflare Enterprise and hit Enable. Pick the domain from the dropdown and pay: $5 for the month, no contract attached to it.
2. **Add one CNAME record** — xCloud shows you the exact record to add at your existing DNS provider. Your nameservers do not move and your DNS host does not change; the domain joins xCloud's Cloudflare account as a custom hostname.
3. **Hit refresh, and you're live** — refresh the domain status; it flips to Active. Sensible defaults are already on, and the Settings tab is there when you want to change caching, WAF or anything else.
[Read the full activation guide](/docs/how-to-activate-the-cloudflare-enterprise-addon/)
## Built for every site that can't afford to be slow
A slow or unprotected site never fails loudly. It bleeds: **rankings slip** as search engines rank faster competitors above you; **conversions leak** as slow pages push up bounce rates; **attacks arrive unannounced**, because without edge protection you find out when the site is already down.
- **WooCommerce stores** — catalogue and product pages come off the edge while carts and checkout stay dynamic, and the WAF sits in front of the payment flow.
- **Agencies & freelancers** — turn it on for the client sites that need it, at a per-domain cost you can put on an invoice as a CDN and security line item.
- **Content & media sites** — serve heavy pages and images worldwide from the edge, and block AI crawlers from scraping the work you're paid for.
- **Launch & campaign sites** — absorb the spike, and anything that shows up alongside it, at the edge, so your origin stays calm through the launch.
- **Membership & SaaS** — rate limiting, Under Attack Mode and real-time security reporting keep logged-in experiences fast and protected.
- **Global audiences** — visitors on every continent load from the nearest of 330+ locations instead of one distant server.
## Frequently asked questions
**What exactly is the Cloudflare Enterprise add-on?**
A fully managed, per-domain integration that puts your website on Cloudflare's Enterprise network. Enterprise normally means a contract negotiated directly with Cloudflare at volume. xCloud already holds that contract, so you get global CDN acceleration, enterprise WAF and DDoS protection, edge caching, image optimization and real-time analytics for $5 a domain — with no negotiation, no minimum commitment and no Cloudflare account of your own.
**Do I need my own Cloudflare account?**
No. Cache rules, WAF toggles, purges, analytics and security events are all in your xCloud dashboard. Setup is smoothest if your domain already sits in a Cloudflare account that's connected to xCloud, because the configuration is then applied for you automatically — but that account is only ever used for your DNS records, not for the add-on itself.
**How is $5 possible when Cloudflare Business is $250?**
Because you're not buying a plan — you're joining one. xCloud holds an Enterprise contract with Cloudflare and the add-on attaches your domain to it as a custom hostname, so the cost is a share of a network already paid for rather than a new subscription. That is also why tiered caching and full-page edge caching are included here, when they're paid extras or hand-written rules on Cloudflare's own Pro and Business plans.
**Is there a free trial?**
Not at the moment. At $5 per domain with no contract you can enable it, run it on your own site and cancel whenever you want — but it starts billing straight away.
**Is the add-on refundable?**
No. Like every xCloud add-on, the Cloudflare Enterprise add-on is non-refundable once the subscription is activated. Add-on purchases are final, so check the domain, price and billing details before you subscribe. The full terms are in the xCloud Refund Policy.
**Does the price per domain include subdomains?**
One subscription covers the root domain and its www version. Other hostnames — shop.example.com, app.example.com, staging.example.com — are separate subscriptions at $5 per hostname per month, so you enable only the ones you need. Manage them together from the Addons page, and remove any single one without touching the rest.
**Is bandwidth really unlimited?**
Each domain subscription includes 100 GB of bandwidth per month, which covers the vast majority of WordPress sites — full-page edge caching means most requests are served from Cloudflare's edge without touching your server. Usage beyond 100 GB is billed at $0.02/GB, prorated, so a high-traffic site pays transparently for what it uses instead of hitting a hard cap or a forced upgrade. You can monitor your data transfer anytime in the Analytics tab of the addon.
**Can I purge the cache from my WordPress dashboard?**
You can purge per site from the xCloud dashboard today. A plugin to purge from wp-admin is planned as part of a central xCloud plugin — the purge capability is already built, it just needs wiring into WordPress.
**How does rate limiting work, and can I change the threshold?**
Rate limiting counts requests per IP in 60-second windows and applies a managed challenge above the threshold, which keeps bots, scrapers and brute-force traffic off your server. The default is 200 requests a minute and we're still tuning it across sites. It isn't a hard Cloudflare cap: if the default doesn't suit your site — a busy store, say — open a support ticket and we'll customise the threshold for your domain. Self-serve control is on the roadmap.
**Is there still a 100-second timeout limit?**
No. On Enterprise the timeout isn't fixed the way it is on the free plan. We currently run it at 200 seconds and can raise it further per use case — Cloudflare allows up to 6,000. If you have a legitimate long-running process hitting 524 errors, open a support ticket.
**Does it work with WordPress and WooCommerce?**
Yes, and the caching is aware of both. Full pages are cached at the edge, while edge page caching automatically bypasses logged-in sessions, wp-admin, wp-login, the REST API, WooCommerce and EDD carts, checkout, my-account, feeds and sitemaps — so shoppers never see someone else's basket. You can add your own bypass paths per site in the Cache Bypass Paths setting; anything under them is never cached at the edge and always loads fresh from your server. When you turn on Edge Page Caching, xCloud disables local page caching for that site so the two layers can't conflict.
**Can I change the caching and security settings?**
Yes. Early Hints, ScrapeShield, static caching, edge page caching, image optimization and the SSL cipher profile are all switchable, as are the WAF, rate limiting, browser integrity check, Under Attack Mode and AI crawler blocking. The defaults are already tuned; save after changing a toggle and xCloud persists it for the site.
**What analytics do I get?**
Request summary, cache performance and security events, over ranges from the last 30 minutes to the last 30 days, with your top pages, countries, devices and IPs — all in the xCloud dashboard rather than a separate Cloudflare console.
**Will this affect my SEO?**
It should help. Search engines weigh page speed and availability, and this improves both — pages come off the edge, and the WAF and DDoS mitigation keep the site reachable during attacks that would otherwise take your server, and the crawler, offline.
## Stop paying for visitors who leave before the page loads
Enterprise speed and always-on protection on any domain, for $5 a month. One CNAME, live in minutes, and yours to switch off whenever you want.
[Enable it on a domain](https://app.xcloud.host/register) · [See how it works](/docs/how-to-activate-the-cloudflare-enterprise-addon/)
No contract · Cancel any domain at any time
Cloudflare, the Cloudflare logo and related marks are trademarks of Cloudflare, Inc., registered in the U.S. and other countries. xCloud is not affiliated with, endorsed by or sponsored by Cloudflare.
---
# Codex Hosting – Launch and Scale AI-Built Apps Faster
> Deploy and host Codex-built apps in minutes. Connect Git, configure your app, and launch on high-performance cloud servers with one-click deployment.
# **Cluade Code Hosting**
## Codex Hosting to Take AI-Built Apps From Code to Live In Minutes
Deploy the apps and prototypes you build with Codex on infrastructure you fully own. Connect your repository, configure once, and push to LIVE in minutes, no manual server setup, no DevOps overhead.
## **Setup Process**
## Go Live With Your Codex in a Few Simple Steps
Get your Codex project running quickly with a step-by-step flow, from setup to launch, manage everything in one place, with deployment simplified so you can focus on building.
### Choose Deployment Method
Clone your Codex-built project directly from a Git repository and prepare your application for deployment in seconds.
### Configure Your Environment
Set your domain, Node.js version, build command, start command, environment variables, and other essential application settings based on your project requirements.
### Go Live Right Away
Review your configuration and deploy instantly. Push your latest code to the connected branch and your live application can be updated automatically.
## Pricing
## Reliable Codex Hosting
at a Price You’ll Love
Choose a pay-as-you-go plan on your preferred cloud server. Run unlimited projects with the tools
you need for reliable, always-on development.
- ###### xCloud Managed Server
- ###### Self-Managed Server
### All
### 1 GB
For Personal Use
### 2 gb
For Basic Websites
### 4 gb
For Growing Websites
### 8 gb
For Busier Websites
### 16 gb
For Bigger, Busier Websites
### 32 gb
For HIGH-PERFORMANCE NEEDS
### 48 gb
For HIGH-PERFORMANCE NEEDS
### 58 gb
For HIGH-PERFORMANCE NEEDS
## Elevate your site with xCloud servers—ensuring speed and security, with no hidden charges in the future.
## Premium servers are powered by High-Frequency 3GHz+ Intel Xeon CPUs, lightning-fast memory, and NVMe storage, delivering unmatched speed and performance. General servers, on the other hand, offer a budget-friendly solution for standard workloads
- ###### All
- ###### 1 GB
- ###### 2gb
- ###### 4gb
- ###### 8GB
- ###### 16gb
- ###### 32gb
- ###### 48GB
- ###### 58GB
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
## Business Max
- ### 64 GB RAM
Ultimate plan for unparalleled power
- ### 1280 GB SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 10 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-max)
## $ **399.00** /mo
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
Monthly
Yearly
MonthlyYearly
## Black Friday Special Deal : One-time Payment – LIFETIME Access!
Bring your own server and unlock access to our cloud control panel to enjoy a seamless server and site management experience for a lifetime.
[Grab Lifetime Deal](/deal/)
## Want to explore xCloud first? Try it out for free and then decide!
[Get started](https://app.xcloud.host/register)
## FREE PLAN
- ### 1 Server
- ### 10 Site
## Start your journey without cost
## Starter
- $5/Server (/month)
- 1-5 Servers
- Unlimited Sites
## Perfect for Beginner
## Professional
- $4/Server (/month)
- 6-10 Servers
- Unlimited Sites
## Tailored for Experts
## Agency
- $3/Server (/month)
- 11+ Servers
- Unlimited Sites
## Perfect for Large Teams
document.addEventListener(“DOMContentLoaded”, function () { function centerActiveTab() { if (window.innerWidth > 767) return; // Only run on screen widths ≤ 767px var navParent = document.querySelector(“.xcloud\_\_pricing-tab .tabTitles”).parentElement; // The scrolling container (Parent) var activeTab = document.querySelector(“.xcloud\_\_pricing-tab .tabTitles li.active”); // The active tab if (navParent && activeTab) { var containerWidth = navParent.clientWidth; var tabWidth = activeTab.offsetWidth; var tabPosition = activeTab.offsetLeft; // Calculate scroll position to center the active tab var scrollTo = tabPosition – (containerWidth / 2) + (tabWidth / 2); // Animate scrolling navParent.scrollTo({ left: scrollTo, behavior: “smooth” }); } } function handleTabClick() { if (window.innerWidth > 767) return; // Only run on screen widths ≤ 767px // Remove active class from all tabs document.querySelectorAll(“.xcloud\_\_pricing-tab .tabTitles li”).forEach(el => el.classList.remove(“active”)); // Add active class to clicked tab this.classList.add(“active”); // Center the clicked tab centerActiveTab(); } // Center the active tab on page load (if screen width ≤ 767px) centerActiveTab(); // Add click event to all tabs document.querySelectorAll(“.xcloud\_\_pricing-tab .tabTitles li”).forEach(function (tab) { tab.addEventListener(“click”, handleTabClick); }); // Re-check on window resize (optional, to handle dynamic screen resizing) window.addEventListener(“resize”, centerActiveTab); });
## Pricing
## Reliable Managed Codex Hosting
at a Price You’ll Love
Deploy and scale Codex-built applications on your preferred cloud server
with flexible, pay-as-you-go hosting plans.
- ###### xCloud Managed Server
- ###### Self-Managed Server
.xcloud\_\_ui-slider-wrap { width: 100%; margin: 70px 0 100px; } .xcloud\_\_ui-slider-wrap img { width: 100%; height: auto !important; } .xcloud\_\_ui-slider-outer { width: 100%; display: flex; position: relative; } .xcloud\_\_ui-slider-dragger { width: 24px; height: 24px; background: linear-gradient(97deg, #5D83FF -0.34%, #2E5DF7 99.66%); border-radius: 100px; cursor: grab; position: relative; z-index: 9999; box-sizing: border-box; order: 1; margin-bottom: -24px; } .xcloud\_\_ui-slider-dropzone { display: flex; justify-content: space-between; position: absolute; gap: 0px; width: 100%; } .xcloud\_\_ui-slider-dragger:hover { cursor: grabbing; } .dropzone { /\*flex: 1;\*/ display: flex; flex-wrap: wrap; justify-content: center; cursor: pointer; min-width: 62px; position: relative; } .dropzone:first-child { margin-left: -18px; } .dropzone:last-child { margin-right: -18px; } .dropzone-info { flex: 1 100%; text-align: center; margin-top: 36px; order: 2; pointer-event: none; } .dropzone-hor-line { height: 20px; width: 2px; background: #3D3F4F; margin: 0 auto 15px; } .dropzone.active .dropzone-hor-line { background: #3264F7; } .dropzone-title { color: #FFF; text-align: center; font-family: Sora; font-size: 12px; font-style: normal; font-weight: 600; line-height: 1; letter-spacing: 0.36px; text-transform: uppercase !important; } .dropzone-tooltip { width: 170px; background: #2B2E40; background: radial-gradient(circle at 100% 100%, #2b2e40 0, #2b2e40 11px, transparent 11px) 0% 0%/12px 12px no-repeat, radial-gradient(circle at 0 100%, #2b2e40 0, #2b2e40 11px, transparent 11px) 100% 0%/12px 12px no-repeat, radial-gradient(circle at 100% 0, #2b2e40 0, #2b2e40 11px, transparent 11px) 0% 100%/12px 12px no-repeat, radial-gradient(circle at 0 0, #2b2e40 0, #2b2e40 11px, transparent 11px) 100% 100%/12px 12px no-repeat, linear-gradient(#2b2e40, #2b2e40) 50% 50%/calc(100% – 2px) calc(100% – 24px) no-repeat, linear-gradient(#2b2e40, #2b2e40) 50% 50%/calc(100% – 24px) calc(100% – 2px) no-repeat, linear-gradient(90deg, #42465d 0%, #212435 100%); border-radius: 12px; padding: 19px; position: absolute; bottom: calc(100% + 20px); left: 50%; transform: translate(-50%, 10px) scale(0.9); opacity: 0; visibility: hidden; transition: all 0.4s; } .dropzone-tooltip::after { top: 100%; left: 50%; border: solid transparent; content: “”; height: 0; width: 0; position: absolute; pointer-events: none; border-color: rgba(136, 183, 213, 0); border-top-color: #2B2E40; border-width: 14px; margin-left: -14px; } .dropzone-tooltip p { color: #FFF; margin: 0; font-family: Sora; font-size: 12px; font-weight: 400; line-height: 1.2; letter-spacing: 0.03em; text-transform: uppercase; text-align: center; } .dropzone.active .dropzone-tooltip { transform: translate(-50%, 0) scale(1); opacity: 1; visibility: visible; } @media (max-width: 1024px) { .dropzone-tooltip { padding: 8px; bottom: calc(100% + 10px); width: 100px; } .dropzone-tooltip::after { border-width: 8px; margin-left: -8px; } .dropzone-tooltip p { font-size: 9px; } } @media (max-width: 767px) { .xcloud\_\_ui-slider-wrap { display: none; } }
### All
### 1 GB
For Personal Use
### 2 gb
For Basic Websites
### 4 gb
For Growing Websites
### 8 gb
For Busier Websites
### 16 gb
For Bigger, Busier Websites
### 32 gb
For HIGH-PERFORMANCE NEEDS
### 48 gb
For HIGH-PERFORMANCE NEEDS
### 58 gb
For HIGH-PERFORMANCE NEEDS
jQuery( document ).ready(function($) { function xCloudSnapToGrid(droppedId, target, dragger) { if( droppedId ) { dragger.style.left = 0; target.append(dragger) $(target).addClass( ‘active’ ).siblings().removeClass(‘active’); $(\`.eb-advanced-tabs-1n0aa50 \[data-title-tab-id=${droppedId}\]\`).trigger(‘click’); } } let droppedId = 1; $(“#xcloud\_dragger”).draggable({ axis: ‘x’ }); $(“.dropzone”).droppable({ accept: ‘#xcloud\_dragger’, greedy: true, drop: function (event, ui) { droppedId = event.target.dataset.id; xCloudSnapToGrid(droppedId, event.target, ui.draggable\[0\]); }, deactivate: function (event, ui) { let dropzone = document.querySelector(\`\[data-id=’${droppedId}’\]\`); if (dropzone) { xCloudSnapToGrid(droppedId, dropzone, ui.draggable\[0\]); } } }); $(document).on( ‘click’, ‘.dropzone’, function( e ){ let target = e.target; if( ! target.dataset.id ) { target = e.target.closest(‘.dropzone’); } xCloudSnapToGrid( target.dataset.id, target, document.querySelector(“#xcloud\_dragger”) ) } ) });
## Elevate your site with xCloud servers—ensuring speed and security, with no hidden charges in the future.
## Premium servers are powered by High-Frequency 3GHz+ Intel Xeon CPUs, lightning-fast memory, and NVMe storage, delivering unmatched speed and performance. General servers, on the other hand, offer a budget-friendly solution for standard workloads
- ###### All
- ###### 1 GB
- ###### 2gb
- ###### 4gb
- ###### 8GB
- ###### 16gb
- ###### 32gb
- ###### 48GB
- ###### 58GB
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
## Business Max
- ### 64 GB RAM
Ultimate plan for unparalleled power
- ### 1280 GB SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 10 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-max)
## $ **399.00** /mo
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
Monthly
Yearly
MonthlyYearly
## Black Friday Special Deal : One-time Payment – LIFETIME Access!
Bring your own server and unlock access to our cloud control panel to enjoy a seamless server and site management experience for a lifetime.
[Grab Lifetime Deal](/deal/)
## Want to explore xCloud first? Try it out for free and then decide!
[Get started](https://app.xcloud.host/register)
## FREE PLAN
- ### 1 Server
- ### 10 Site
## Start your journey without cost
## Starter
- $5/Server (/month)
- 1-5 Servers
- Unlimited Sites
## Perfect for Beginner
## Professional
- $4/Server (/month)
- 6-10 Servers
- Unlimited Sites
## Tailored for Experts
## Agency
- $3/Server (/month)
- 11+ Servers
- Unlimited Sites
## Perfect for Large Teams
## Features
## Perfect For Everything You Build with Codex
Codex is an AI software engineering agent designed to help you write, refactor, and ship production-ready code at speed. From a single prompt to a deployed application, Codex handles the heavy lifting of development so you can move from idea to production faster.
- ### AI-assisted code generation, editing, and refactoring
- ### Rapid prototyping and iteration on real codebases
- ### Full-stack application support across Node.js and modern frameworks
- ### Easy deployment and integration with your own infrastructure
## Advanced Features
## Deploy Codex Apps on Your VPS for Fast, Secure Performance
Launch your Codex-built applications on a high-performance VPS with no complicated setup. Everything comes pre-configured so you can deploy in minutes and scale with confidence.
## Fast Provisioning
Quickly provision servers and deploy sites with xCloud Managed Servers, DigitalOcean, Vultr, Linode, AWS, or Any Servers.
## Enterprise-grade security
Protect your infrastructure with a free SSL certificate, AI bot blocking, and advanced security features at no additional cost.
## One Click Deployment
Start building your server infrastructure instantly with a streamlined setup that gets you running in just a few clicks.
## Intuitive Control Panel
From Server creation to application deployment and security settings, everything can be managed with few clicks from our easy-to-use hosting control panel.
## Optimised Setup
Your server is pre-optimized with high-performance stacks like Nginx or OpenLiteSpeed and backed by ultra-fast NVMe SSD storage
## Easy DNS Management
Easily manage your DNS records through our intuitive panel. Also, verify your DNS in just 1 click using Cloudflare integration.
## AI Apps
## More AI Apps You Can Deploy on xCloud
From personal assistants to autonomous AI companies, deploy the tools your workflow needs on xCloud.
### OpenClaw Hosting
Deploy Your Personal AI Assistant With Managed OpenClaw Hosting Turn OpenClaw into a working assistant that executes tasks and manages conversations across platforms. Go live in minutes.
[Learn More](/openclaw-hosting/)
### Hermes Agent Hosting
Fully Managed Hermes Agent Hosting. Deploy Hermes Agent in five minutes with persistent memory and connections to Telegram, tools, files, APIs, and scheduled tasks. No server setup, no maintenance.
[Learn More](https://xcloud.host/hermes-hosting/)
### Paperclip Hosting
Run an Autonomous AI Company With Managed Paperclip Hosting Skip the hours of setting up and get a fully managed Paperclip instance live in under a few minutes. With xCloud, focus on building your AI workforce, not complexities.
[Learn More](/paperclip-hosting/)
### Claude Hosting
Deploy Your Personal AI Assistant With Managed OpenClaw Hosting Turn OpenClaw into a working assistant that executes tasks and manages conversations across platforms. Go live in minutes.
[Learn More](/claude-code-hosting/)
### Codex Hosting
Fully Managed Hermes Agent Hosting. Deploy Hermes Agent in five minutes with persistent memory and connections to Telegram, tools, files, APIs, and scheduled tasks. No server setup, no maintenance.
[Learn More](/codex-hosting/)
### Odysseus Hosting
Run an Autonomous AI Company With Managed Paperclip Hosting Skip the hours of setting up and get a fully managed Paperclip instance live in under a few minutes. With xCloud, focus on building your AI workforce, not complexities.
[Learn More](/odysseus-hosting/)
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
xCloud isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
#xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. Xcloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What is Codex hosting, and why does it matter for production apps?
Codex hosting means running the apps you build with Codex in a live environment your users can actually reach. It matters because production hosting gives you real uptime, managed environments, and a stable runtime, instead of leaving your project tied to your local machine.
### How is Codex hosting on xCloud different from a raw VPS?
On a raw VPS you manage the OS, runtime version, process manager, updates, and security yourself. With xCloud, that server setup and ongoing maintenance is handled for you, so you can deploy and run Codex projects without babysitting the underlying machine.
### Can I deploy a Codex project from a private GitHub repository?
Yes. Connect your GitHub account, grant access to the private repo, and deploy from the branch you choose. After that, new pushes to the connected branch can trigger automatic redeploys.
---
# Compare xCloud — Hosting, Panels, Agents & Stacks
> 25 side-by-side comparisons: xCloud against other managed hosts and control panels, plus the hosting-model, AI-agent, automation and stack decisions behind them.
Head-to-head breakdowns — xCloud against the other managed hosts and control
panels, and the platform decisions that come before picking one.
## xCloud vs the alternatives
| Comparison | What it covers |
| --- | --- |
| [xCloud vs Cloudways](/xcloud-vs-cloudways/) | How xCloud differs from Cloudways. |
| [xCloud vs RunCloud](/xcloud-vs-runcloud/) | Features, pricing and support compared. |
| [xCloud vs SiteGround](/xcloud-vs-siteground/) | A complete competitor analysis. |
| [xCloud vs SpinupWP](/xcloud-vs-spinupwp/) | Feature-by-feature differences. |
| [xCloud vs ServerAvatar](/xcloud-vs-serveravatar/) | We compared them so you don't have to. |
| [xCloud vs Rapyd Cloud](/xcloud-vs-rapyd-cloud/) | Fast, secure WordPress hosting compared. |
| [Revisiting the SpinupWP comparison](/reflecting-on-the-spinupwp-vs-xcloud-comparison/) | A more accurate view of our features and services. |
| [xCloud Free vs PRO](/xcloud-free-vs-pro/) | How the free and PRO tiers compare. |
## Switching from another host
| Comparison | What it covers |
| --- | --- |
| [7 best Cloudways alternatives](/best-cloudways-alternatives/) | Pricing, performance and features; save up to 40%. |
| [7 best RunCloud alternatives](/best-runcloud-alternatives/) | Free tiers, pricing and WordPress features. |
| [11 best WP Engine alternatives](/best-wp-engine-alternatives/) | Faster, cheaper, WordPress.org-friendly picks. |
## Managed or self-managed
| Comparison | What it covers |
| --- | --- |
| [Self-managed vs managed hosting](/self-managed-vs-managed-hosting/) | Pros and cons of each model. |
| [Managed vs self-hosting OpenClaw](/managed-vs-self-hosting-openclaw/) | Costs, security risks, performance, setup effort. |
| [Hermes Agent: Docker vs managed](/hermes-agent-docker-vs-managed-hosting/) | Setup, control, security, cost and uptime. |
| [Horizontal vs vertical scaling](/horizontal-scaling-vs-vertical-scaling/) | Which scaling approach suits you. |
## AI agents and models
| Comparison | What it covers |
| --- | --- |
| [Hermes Agent vs OpenClaw](/hermes-agent-vs-openclaw/) | Memory, skills, channels, security and cost. |
| [OpenClaw vs Paperclip vs Hermes](/openclaw-vs-paperclip-vs-hermes/) | The top three open-source agent platforms. |
| [GPT-5.5 vs Claude Opus 4.7](/openai-gpt-5-5-vs-claude-opus-4-7/) | Benchmarks, pricing and token efficiency. |
## Automation tools
| Comparison | What it covers |
| --- | --- |
| [n8n vs Make vs Zapier](/n8n-vs-make-vs-zapier-which-automation-tool-should-you-choose/) | Pricing, integrations and workflow flexibility. |
| [n8n vs Make](/n8n-vs-make-which-one-should-you-choose/) | Pricing, features, AI integration, customization. |
| [n8n vs Zapier](/n8n-vs-zapier-which-one-should-you-choose/) | In-depth comparison of features and costs. |
## Stacks and infrastructure
| Comparison | What it covers |
| --- | --- |
| [Node.js vs Laravel](/node-js-vs-laravel-key-differences/) | Performance, scalability, security, use cases. |
| [Django vs Node.js](/django-vs-nodejs-web-development-guide/) | Performance, scalability and developer experience. |
| [NGINX vs OpenLiteSpeed](/nginx-vs-openlitespeed-which-web-server-is-faster/) | Which web server is faster for your site. |
| [AWS Lightsail vs EC2](/aws-lightsail-vs-aws-ec2-instance/) | Pricing, features and use cases. |
## More
- Pricing: [/pricing/](/pricing/)
- Docs: [/docs/](/docs/)
- Full page catalogue: [/llms.txt](/llms.txt)
---
# WordPress Security Headers – A Guide to Keep Your Website Safe - xCloud
> A complete guide to WordPress security headers for strengthening your site defense. Learn & apply to make your site protected by all means.
Strengthening your site’s defenses with WordPress security headers is one of the smartest moves you can make to protect it. These hidden heroes quietly guard your website, blocking hackers, preventing data theft, and keeping online threats at bay. Often overlooked, security headers are a simple yet powerful way to ensure your site stays safe and secure. Ready to find out how they work and why they are a must-have for your WordPress site? Let us dive in!
## **What Are Security Headers in WordPress & How Do They Work?**
Security headers act as invisible shields between your website and the browsers accessing it, preventing malicious code from executing. They safeguard both your site and your users by blocking potential threats, like injected code or harmful scripts before they can do any damage.
In WordPress, security headers are delivered directly by the web server (e.g., Apache, Microsoft IIS). Imagine a scenario where a malicious iframe is injected into a page. When the server sends this page to a user’s browser, it also sends security headers. If the correct header, such as **_X-Frame-Options_**, is in place, it will stop the browser from displaying the harmful iframe, keeping your users safe.
## **Why Do We Need Security Headers in WordPress?**
HTTP security headers are an essential yet often overlooked way to enhance your WordPress site’s security and performance. They act as invisible shields, protecting your site from threats and optimizing how it interacts with browsers. Here is how they work:
- **Boost Security:** With headers like CSP (Content Security Policy) and XFO (X-Frame Options), you can guard your site against common attacks like cross-site scripting (XSS) and malicious code injections, keeping your data and users safe.
- **Prevent Risky Content Execution:** XCTO (X-Content-Type-Options) headers help browsers identify content types correctly, blocking potentially harmful files from executing.
- **Secure Data in Transit:** HSTS (HTTP Strict Transport Security) headers enforce encrypted connections between browsers and servers, ensuring sensitive data remains private.
- **Protect User Privacy:** Set headers to control how data is shared in web requests, giving you the ability to safeguard user information and maintain privacy.
By implementing HTTP security headers, you’re not just adding another layer of protection—you’re creating a safer, faster, and more reliable experience for everyone who visits your site.
## **How to Add Recommended WordPress Security Headers?**
You need to enhance your website’s security by adding recommended security headers in WordPress. These headers help protect against common threats like XSS, clickjacking and data injection.
### **Understanding X-Frame-Options Security Header**
X-Frame-Options is a security header that protects your website from clickjacking attacks. Clickjacking occurs when your site’s content is embedded into another website using an iframe, tricking users into interacting with elements they believe are safe. This becomes especially dangerous if the user is logged into restricted areas of your site.
**Key Directives of X-Frame-Options**
- DENY:
Prevents your site from being displayed in an iframe, ensuring complete protection against embedding.
_X-Frame-Options: DENY_
- ALLOW-FROM:
This is an obsolete directive. Modern browsers that encounter response headers with this directive will ignore the header completely. The [**Content-Security-Policy HTTP**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options#allow-from_origin) header has a frame-ancestors directive which you should use instead.
_Content-Security-Policy: frame-ancestors ‘self’_ [_https://www.example.com_](https://www.example.com)
- SAMEORIGIN:
Allows rendering only when the iframe is loaded from the same origin (domain) as your website.
_X-Frame-Options: SAMEORIGIN_
#### **Adding X-Frame-Options Security Header to Your WordPress Site**
You can implement the X-Frame-Options security header in WordPress by modifying the configuration files of your server: .htaccess for Apache or nginx.conf for NGINX.
**For OLS**
header add X-Frame-Options “SAMEORIGIN”
**For NGINX**
_add\_header X-Frame-Options “SAMEORIGIN” always;_
**For Apache**
__
_Header always append X-Frame-Options SAMEORIGIN_
__
These configurations ensure that your site is safeguarded against unauthorized embedding, maintaining user trust and security.
_Note: With xCloud, you can edit the X-Frame-Options from Site settings. To do so, you need to navigate to_ **_Site → Tools → Security_** _& enable the ‘_**_Edit X-Frame-Options_**_’ toggle._
### **Understanding HSTS – HTTP Strict Transport Security**
HTTP Strict Transport Security (HSTS) is a security mechanism that ensures web browsers only interact with a web server using secure HTTPS connections, completely avoiding the less secure HTTP protocol. HSTS is a standardized protocol defined by the IETF and detailed in RFC 6797, which was approved in 2012.
**Key directives in HSTS include:**
- **includeSubDomains:** Ensures the HSTS rule is applied to all subdomains of a site.
- **max-age:** Specifies the duration (in seconds) that browsers should enforce HTTPS-only access to the site.
An Example of an HSTS header
_Strict-Transport-Security: max-age=10886400; includeSubDomains_
#### **Adding HTTP Strict Transport Security Header to WordPress**
Before adding HSTS headers, you need to ensure that your site is using a proper SSL certificate and HTTPS is working properly. Then the users should add this header. Adding this header without an SSL cert is dangerous.
That being said, to implement HSTS on a WordPress site, you need to add the appropriate header to your server configuration. This can be done by editing the .htaccess file for Apache servers or the nginx.conf file for NGINX servers.
**OLS Configuration**
header add Strict-Transport-Security “max-age=10886400; includeSubDomains”
**Apache Configuration**
Add the following code to your .htaccess file:
__
_Header always set Strict-Transport-Security “max-age=10886400; includeSubDomains”_
__
**NGINX Configuration**
Add this directive to your nginx.conf file:
_add\_header Strict-Transport-Security “max-age=10886400; includeSubDomains”;_
After making these changes, restart your server to apply the new configuration.
### **Understanding Content Security Policy (CSP)**
The Content-Security-Policy (CSP) header is a security feature designed to minimize cross-site scripting (XSS) risks in modern browsers. It allows you to specify which dynamic resources are permitted to load, adding an additional layer of security.
Similar to the X-Content-Type-Options header, CSP offers a wide range of configuration options. Below, we focus on the key directives, which are particularly useful for beginners.
**Key CSP Directives**
- **default-src:** Sets the default policy for loading content, including AJAX requests, frames, images, JavaScript, CSS, fonts, and media.
- **script-src:** Specifies allowed sources for JavaScript.
- **connect-src:** Controls connections like WebSocket, XMLHttpRequest (AJAX), and EventSource. If a connection isn’t permitted, the browser simulates a 400 HTTP status code.
- **img-src:** Identifies legitimate sources for images.
- **style-src**: Defines trusted sources for stylesheets.
#### **Adding a Content-Security-Policy Header**
You can implement a Content-Security-Policy header on your WordPress site by configuring the .htaccess file (Apache) or the nginx.conf file (NGINX).
**For OLS Servers:**
header add Content-Security-Policy “default-src ‘none’; script-src ‘self’; connect-src ‘self’; img-src ‘self’; style-src ‘self’;”
For Apache Servers:
Add the following line to your .htaccess file:
Header set Content-Security-Policy “default-src ‘self’; script-src ‘self’ [https://ajax.googleapis.com](https://ajax.googleapis.com); img-src ‘self’ data:; style-src ‘self’ [https://fonts.google.com/](https://fonts.google.com/);”
For NGINX Servers:
Add this directive to your nginx.conf file:
add\_header Content-Security-Policy “default-src ‘self’; script-src ‘self’ [https://ajax.googleapis.com](https://ajax.googleapis.com); img-src ‘self’ data:; style-src ‘self’ [https://fonts.google.com/](https://fonts.googleapis.com);” always;
By setting up CSP headers correctly, you can significantly enhance your website’s security against unauthorized resource loading and malicious attacks.
### **Understanding X-Content-Type-Options**
The X-Content-Type-Options header ensures that browsers only interpret files according to the declared content type in the HTTP headers, enhancing security by preventing content type sniffing. While there are various configuration options and parameters available, the most commonly used setting is nosniff.
Example:
_X-Content-Type-Options: nosniff_
#### **Adding the X-Content-Type-Options Header in WordPress**
You can configure the X-Content-Type-Options header in your WordPress site through the .htaccess file (for Apache) or the nginx.conf file (for NGINX).
For OLS:
**header add X-Content-Type-Options “nosniff”**
For Apache:
Add the following snippet to your .htaccess file:
Header set X-Content-Type-Options nosniff
For NGINX:
Add this line to your nginx.conf file:
add\_header X-Content-Type-Options “nosniff” always;
By implementing this header, you can safeguard your site against potential security risks related to improper content type handling.
## **How to Add HTTPS Security If You Have xCloud?**
With xCloud, you can easily install the ‘**Let’s Encrypt**‘ SSL certificate on your site without any complexity. You can directly do it from the dashboard. All you have to do is enable the toggle button of ‘**HTTPS Enabled.**’
👉 To learn more: [**How To Easily Install Let’s Encrypt SSL Certificate**](/docs/install-lets-encrypt-ssl-certificate/)
## **How Can You Test Your Website’s Security Headers?**
Two ways of testing you can go with—a third-party website or terminal. With this test, you can find out which headings are missing from your website & the status of your newly added security headings, and whether it is working properly or not.
### **1\. Test Your Website Security Headers Using Third-Party App**
To test your website security headers, we recommend you use [**Security Headers by synk**](https://securityheaders.com/?q=hurayraiit.com&hide=on&followRedirects=on).The platform provides scores for security headers, A means excellent. Here we used [**wordpress.org**](http://wordpress.org) as an example & it scored ‘**D**.’ That means, there is a scope to improve more.
### **2\. Test Your Website Security Headers Using the Terminal**
Another way of testing your website security header is running this command: **_curl -I_** [**_https://yourwebsite.com_**](https://yourwebsite.com). Once you write the command in your terminal, hit the ‘Enter; button & you will get your website security headers result as shown below.
## **Strengthen Your WordPress Security with Headers to Keep Your Site Secure**
WordPress security headers are a simple yet powerful way to protect your website. They act as invisible shields, blocking threats like hackers, malicious code, and data theft. By setting up headers such as X-Frame-Options, HSTS, & CSP you can secure your site, safeguard user privacy, and boost performance.
These headers are easy to implement and provide significant protection against common vulnerabilities. Taking this small step ensures your website stays safe, fast, and trustworthy. Start adding security headers today and keep your WordPress site secure for the future.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Connect with Team xCloud
> Meet and connect with Team xCloud to learn all about our next-gen hosting solution for WordPress, Node.js, Lovable, AI projects and many more. Book a meeting today!
Meet and connect with Team **xCloud Hosting** at WordCamp Asia 2025!
Choose a topic, select an expert, and click on your preferred card below to book a time slot that fits your schedule.
### M Asif Rahman
Founder, xCloud & Startise. Get in touch to discuss high-performance hosting solutions and why xCloud is the next big thing in hosting.
### Rupok
Co-Founder, xCloud & Startise. Connect to explore innovative opportunities in hosting, product development and business growth.
### Shifat
Product Manager, xCloud. Talk with him about enhancing your hosting experience or sharing feature requests or product ideas.
### Sadman
Senior Cloud Support Engineer, xCloud. Book a call for best practices on optimizing hosting performance and seamless customer experiences.
### Charina Acuar
Technical Support Engineer, xCloud. Connect to resolve hosting issues and ensure smooth hosting experiences with expert support.
---
# Contact - xCloud
> Contact us here for any kind of assistance. Check out our Support Portal to find your tickets.
## Get In Touch
# Need Assistance? Reach Out to Us
Contact us here for any kind of assistance. Check out our [Support Portal](https://support.xcloud.host) to find your tickets.
## Get in Touch
## Address
xCloud Hosting, LLC.
124 Broadkill Rd #599
Milton, DE 19968-1008
## Email
support@xcloud.host
## Send Us A Message
---
# Cookie Policy - xCloud
> Read the Cookie Policy and learn how xCloud uses cookies to improve functionality, personalize experiences, and ensure compliance with privacy and data protection laws.
# xCloud **Cookie Policy**
Please take the time to read this agreement carefully, as it includes important information about your legal rights and protections.
- [What Are Cookies?](/cookie-policy/)
- [Use of Cookies And Tracking Technologies](/cookie-policy/)
- [Why We Use Cookies?](/cookie-policy/)
- [Types of Cookies We Use](/cookie-policy/)
- [Essential Cookies](/cookie-policy/)
- [Web Statistics Cookies](/cookie-policy/)
- [Social Media Cookies](/cookie-policy/)
- [Advertising Cookies](/cookie-policy/)
- [Using Cookies for Retargeting](/cookie-policy/)
- [Third-Party Advertising Partners](/cookie-policy/)
- [Practical Steps for Compliance](/cookie-policy/)
- [Functionality Cookies](/cookie-policy/)
- [Other Cookies](/cookie-policy/)
- [Cookies Used by Third Parties](/cookie-policy/)
- [Managing Cookies](/cookie-policy/)
- [Changes to This Cookie Policy](/cookie-policy/)
- [Contact Us](/cookie-policy/)
xCloud and its affiliated companies (collectively referred to as “xCloud,” “us,” “we,” or “our”) operate the websites, including but not limited to \[[https://xcloud.host](/)\], \[[https://support.xcloud.host/](https://support.xcloud.host/)\], and other subdomains of xcloud.host (the “Sites,” “Service,” or “Services”).
This Cookie Policy explains how xCloud uses cookies and other tracking technologies to enhance your experience, improve functionality, and understand your preferences when using our Sites. By continuing to use our Sites, you consent to our use of cookies as described in this Cookie Policy.
### What Are Cookies?Copied!
Cookies are small text files placed on your device when you interact with online services and access certain websites. These cookies do not recognize you personally but rather the device you use or capture your preferences. Cookies can be used to remember information about your visit, such as language settings, or track when you last logged in, helping improve your experience with our Sites. Other similar technologies such as pixels, web beacons, and local storage are also used for these purposes.
### Use of Cookies And Tracking TechnologiesCopied!
To enhance user experience and ensure seamless functionality, xCloud and our third-party service providers utilize cookies, pixel tags, local storage, and scripts (collectively referred to as “cookies”). These technologies help us improve performance, analyze usage, and deliver personalized content and advertisements. By continuing to use our Sites, you consent to our use of cookies as outlined in this Cookie Policy.
### Why We Use Cookies?Copied!
We use cookies for several reasons. These cookies help us understand how our Sites are used, so we can improve their performance and provide relevant content and advertisements. We use cookies to:
- Provide and maintain the operational functionality of our Services
- Improve and personalize your experience on our Website.
- Analyze user behavior to enhance our content and Website structure.
- Deliver relevant advertisements tailored to your interests.
- Provide social media integrations and improve interactions with third-party platforms.
- Enhance security and diagnostics of the website’s services.
### Types of Cookies We UseCopied!
### Essential CookiesCopied!
These cookies are crucial for the proper functioning of our Website. They are used to store your preferences, detect misuse of our Website and services, and distribute the load on our servers, ensuring that the Website remains available. Some services you request may not be available without these cookies.
### Web Statistics CookiesCopied!
These cookies help us understand which parts of our Website are of interest to our visitors. By tracking visitor behavior (such as the number of visitors, time spent on pages, and pages visited), we can make improvements to our Website’s structure, navigation, and content. Third-party software, such as Google Analytics, may be used to track web statistics. Information generated by Google Analytics may be transferred to and stored on a Google server in the United States. As IP address anonymization is enabled, Google will mask your IP address before collecting any data.
### Social Media CookiesCopied!
Our Website may integrate third-party plug-ins (such as a Facebook “like” button). Even if you do not interact with these plug-ins, they may still collect information such as your IP address and the pages you view. These plugins are governed by the privacy policies of the respective third parties.
### Advertising CookiesCopied!
We may use third-party tracking mechanisms to collect data over time and across various websites for the purpose of interest-based advertising. For instance, third-party advertisers may use your visit to our Website to show you ads for xCloud products on other websites. In addition, these advertisers may use information about your activity on our Website or apps to show you targeted advertisements based on your online behavior. We or our third-party service providers may also link your activity across different devices (such as smartphones, tablets, and computers) for targeted advertising, analytics, and reporting purposes. This means that if you log into the same online service on multiple devices, we may combine information about your activity on these devices for analysis or to serve more relevant ads.
### Using Cookies for RetargetingCopied!
Your Cookie Policy explicitly allows Advertising Cookies and third-party tracking mechanisms (AdRoll, Bing, DoubleClick, Facebook, Twitter, etc.) to collect data for interest-based advertising. Users must consent to these cookies under applicable laws (GDPR, UK DPA, etc.). Without consent, tracking for retargeting is not permitted in regions that require opt-in consent.
### Third-Party Advertising PartnersCopied!
Retargeting typically relies on platforms like Google Ads, Facebook Ads, and others. Our Cookie Policy lists these as third-party partners along with the types of cookies they use. Users are linked to the privacy policies of these partners as required.
- Obtaining user consent for tracking cookies or personal data use.
- Data minimization – only using data necessary for advertising.
- Providing clear opt-out options for users (via DAA, DAAC, EDAA links).
### Practical Steps for ComplianceCopied!
- Ensure cookie consent banners are active for users in regions like the EU or UK.
- Configure advertising platforms (Google, Facebook, etc.) to only retarget users who have consented.
- Document consent to maintain compliance if audited.
- Avoid sharing Customer Data directly with advertisers — use anonymized IDs or hashed emails when required.
### Functionality CookiesCopied!
These cookies are essential for the basic operation of our Sites. They ensure that the Services are accessible, and functionalities like language settings, user preferences, and website security are maintained.
### Other CookiesCopied!
This category includes cookies that don’t fit into the above categories. For example, cookies bundled through tools like **Google Tag Manager**, which may help manage and simplify the use of various tracking technologies.
In addition, we also use tracking parameters set by FirstPromoter to identify referrals and promotions. These include the following query parameters which may be stored or tagged as cookies for attribution and analytics purposes: fpr, fp\_ref, via, deal, ref, \_from, \_by, \_get, \_go.
### Cookies Used by Third PartiesCopied!
We may allow third-party providers, including advertising partners, to use cookies on our Sites. These third-party providers may collect information about your activity on our Sites and use it for various purposes such as online advertising and analytics. Examples of third-party advertising partners include Google, Facebook, Twitter, Bing, and others.
Please note that third-party cookies are governed by the privacy policies of the respective providers. Below is a list aof cookies used by third-party partners:
Name
Provider
Purpose
Expiry Date
\_various
AdRoll
Marketing – Measure the effectiveness of our online advertising.
Various
\_uetsid
Bing
Marketing – Measure the effectiveness of our online advertising.
4 hours
MR
Bing
Marketing – Measure the effectiveness of our online advertising.
6 months
MUID
Bing
Marketing – Measure the effectiveness of our online advertising.
1 year
IDE
DoubleClick
Marketing – Measure the effectiveness of our online advertising.
6 months
DSID
DoubleClick
Marketing – Measure the effectiveness of our online advertising.
1 year
fr
Facebook
Marketing – Measure the effectiveness of our online advertising.
3 months
\_ga
Google Analytics
Marketing – Measure the effectiveness of our online advertising.
2 years
\_gid
Google Analytics
Marketing – Measure the effectiveness of our online advertising.
24 hours
\_gat
Google Analytics
Marketing – Measure the effectiveness of our online advertising.
1 minute
drift\_aid
Drift
Marketing – Measure the effectiveness of our online advertising.
2 years
drift\_campaign\_refresh
Drift
Marketing – Measure the effectiveness of our online advertising.
30 minutes
personalization\_id
Twitter
Marketing – Measure the effectiveness of our online advertising.
2 years
### Managing CookiesCopied!
You have the ability to control and manage your cookie preferences by adjusting your browser settings. The instructions for changing your cookie settings can typically be found in the ‘options’ or ‘preferences’ menu of your browser. If you are unsure where to find these settings, the following links may be helpful:
- [Cookie settings in Firefox](https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences)
- [Cookie settings in Chrome](http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=95647)
- [Cookie settings in Safari](https://support.apple.com/en-us/HT201265)
- [Cookie settings in Microsoft Edge](https://support.microsoft.com/en-us/microsoft-edge/manage-cookies-and-site-data-in-microsoft-edge)
- [Cookie settings in Internet Explorer](https://support.microsoft.com/en-us/help/17442/windows-internet-explorer-delete-manage-cookies)
Additionally, you can opt-out of certain third-party cookies by visiting the following websites:
- DAA – Digital Advertising Alliance
- [](http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=95647)[DAAC – Digital Advertising Alliance of Canada](https://youradchoices.ca/)ookie settings in Chrome
- [](https://support.apple.com/en-us/HT201265)[EDAA – European Interactive Digital Advertising Alliance](https://www.edaa.eu/)
### Changes to This Cookie PolicyCopied!
We may update this Cookie Policy from time to time to reflect changes in technology or legal requirements. We encourage you to review this policy regularly to stay informed about our use of cookies. If we make significant changes to this policy, we will notify you by posting a prominent notice on our Sites or sending you an email notification if you are a registered user. Your continued use of the Services after any such modifications will constitute your acknowledgment of the changes and your acceptance of the modified Cookie Policy.
### Contact UsCopied!
If you have any questions about this Cookie Policy or our use of cookies, please contact us at:
Email: [support@xcloud.host](mailto:support@xcloud.host)
---
# Crawler List: A Complete Guide to Web Crawlers and Bot Management - xCloud
> Learn what web crawlers are and how they work. Check out the detailed web crawlers list to understand their impact on SEO.
Web crawlers are the invisible workers of the internet. You may not see them, but they visit your website almost every day. These digital agents, often called _spiders_, _bots_, or _indexers_, collect and organize data from websites. This data then gets stored and used by search engines like Google and Bing to create search results.
Let us learn how web crawlers function, discover the most common crawlers you should know about, understand the risks from harmful bots, and find out how to manage them efficiently.
## **What Are Web Crawlers And How Do They Work**
Web crawlers are automated scripts. They scan web pages, follow links, and gather content. This process is called **crawling**.
Search engines use crawlers to discover and index content, build searchable databases and help users find relevant results.
To understand the importance of maintaining a crawler list and managing bots effectively, you first need to know how web crawlers work. A **web crawler**, also known as a spider or bot, is an automated script or software application. Its job is to browse the internet and collect data from websites. This process is called **crawling**.
Crawlers are used by search engines like Google, Bing, and Yandex. They scan web pages, follow links, index content, and build massive searchable databases. These databases make it possible for you to get search results when you type something into Google.
## **How Crawlers Discover And Navigate Websites**
The crawling process usually starts with a list of known web pages. These could be popular sites, pages from previous crawls, or pages submitted through sitemaps. The crawler visits these pages, scans their content, and looks for hyperlinks. It then adds those links to its list of pages to crawl next. This cycle repeats continuously.
Check what happens during crawling:
1. **Start with a seed URL** (an initial page or a set of pages).
2. **Download the page content** and parse the HTML.
3. **Extract all the links** on that page.
4. **Follow the links** to discover new pages.
5. **Repeat** the process across the web.
Some crawlers use **breadth-first crawling**, which covers all the pages on one level before going deeper. Others use **depth-first crawling**, which follows one path down before backtracking.
## **Search Engine Crawlers vs Third-Party Bots**
There are two broad types of crawlers you should know about: good bots and bad bots. Good bots, also known as legitimate crawlers, are operated by search engines like Google, Bing, and DuckDuckGo to index websites and gather information for search results. Let us learn about them a more detailed
#### **Search Engine Crawlers**
Search engine crawlers include bots like Googlebot, Bingbot, Baiduspider, and others. They are responsible for indexing your content so users can find your site in search engines. These crawlers follow guidelines in your robots.txt file and usually respect crawl delays and access rules.
#### **Third-Party Bots**
Third-party bots are often built by SEO tools, AI models, content scrapers, or competitive research tools. Some are helpful, like SemrushBot or AhrefsBot, which help site owners analyze SEO performance. Others, like price scrapers or spam bots, may access your site aggressively and cause problems.
### **Crawling Policies And Architecture Essentials**
Web crawlers are designed to be polite and efficient. Most legitimate bots follow rules defined in your robots.txt file. This file tells crawlers which pages they can or cannot access. Here are some key principles for effective web crawling:
- **Politeness:** Good crawlers limit the number of requests to avoid overloading your server.
- **Prioritization:** Bots often prioritize high-quality or frequently updated content.
- **Refresh rate:** Some pages are crawled more often, especially if they change frequently or attract traffic.
- **Respect for robots.txt:** Reputable bots honor disallow rules and crawl delays. Malicious bots usually ignore them.
## **Crawler List: Most Common And Emerging Web Crawlers in 2025**
Building and maintaining a [**crawler list**](https://wpdeveloper.com/most-common-web-crawler/) helps you understand which bots are visiting your site. This list is also key to managing your server resources, securing your content, and keeping your analytics data clean. Let us learn about the most widely used crawlers and new bots that are emerging in 2025.
### **Top Search Engine Crawlers to Know**
Search Engine Crawlers come from major search engines and are responsible for indexing your site for users worldwide. They are generally safe, follow crawling rules, and are vital for your SEO.
- **Googlebot:** This is Google’s main crawler. It has several versions, including Googlebot-Desktop, Googlebot-Mobile, Googlebot-Image, and others. Googlebot checks your pages, updates the index, and helps your content appear in Google Search.
- **Bingbot:** Microsoft’s Bingbot works similarly to Googlebot and indexes pages for Bing. It also supports Microsoft’s newer AI-driven services.
- **Applebot:** Applebot crawls the web to collect content for Apple services like Siri and Spotlight. It follows robots.txt and supports Apple’s privacy standards.
- **Baiduspider:** This bot is from the Baidu search engine, which is dominant in China. If you are targeting a Chinese audience, allow this crawler access.
- **YandexBot and DuckDuckBot:** These bots come from Yandex (Russia) and DuckDuckGo, respectively. Both are known to respect robots.txt and are part of the trusted crawler community.
### **AI and Platform-Specific Crawlers**
The rise of artificial intelligence has led to new crawlers that collect web content to train language models or deliver AI-based services. These bots are newer and sometimes less transparent than traditional search engine crawlers.
- **GPTBot (OpenAI):** Used to crawl and index public web content to improve AI models like ChatGPT. It became widely known in 2023 and can be blocked using robots.txt.
- **ClaudeBot (Anthropic):** Claude is another AI chatbot, and its bot crawls pages for training and reference purposes.
- **CCBot (Common Crawl)**: This is a non-commercial crawler that provides data for AI research, search engine projects, and large datasets.
- **Bytespider (ByteDance):** Created by the parent company of TikTok, this bot is often used for content analysis and research.
### **Other Notable Bots (SEO Tools, Scrapers, Aggregators)**
These bots may help you with SEO insights or analytics, but some can be resource-heavy or invasive if left unmanaged.
- **AhrefsBot and SemrushBot:** These are used by SEO professionals to analyze backlinks, keyword rankings, and competitor data. They are useful but can create a high crawl load.
- **MJ12bot (Majestic):** A well-known crawler used for link indexing and backlink analysis.
- **PetalBot (Huawei):** Gaining attention in global markets, this crawler supports Huawei’s search engine.
- **DotBot and MojeekBot:** These are emerging bots used for smaller or independent search engines.
- **Unknown Scrapers and Bad Bots:** Many bots do not identify themselves clearly. They may pose as legitimate crawlers but are really scraping your content, probing for vulnerabilities, or draining resources.
To manage your website effectively, you need to keep your **crawler list** updated. Know which bots are beneficial, which ones are neutral, and which ones you should block or limit. Logging and monitoring traffic can help you identify new user agents and adjust your rules accordingly.
## **How Crawlers Impact SEO, Analytics And Site Performance**
Now that you know the types of bots on your crawler list, let us talk about how they affect your website. Not all bots behave the same. Some help your site grow by improving visibility in search engines. Others can drag your site down by distorting data or consuming resources.
Understanding the **impact of crawlers** is critical if you want to make smart decisions about which bots to allow, restrict, or block completely.
### **SEO Benefits from Good Crawlers**
Good bots help search engines understand and rank your website. Their presence on your crawler list is usually a good sign. These bots index your pages, discover new content, and monitor updates so your site stays relevant in search results. Here are a few SEO benefits you get from good crawlers:
- **Content Indexing:** Bots like Googlebot and Bingbot read your content and add it to their search databases. This allows your site to appear in relevant queries.
- **Freshness and Updates:** Regular crawling helps search engines know when you update a post, publish a new page, or remove outdated content.
- **Site Structure Analysis:** Crawlers follow internal links and evaluate your website’s hierarchy. This affects how search engines determine the importance of each page.
- **Sitemap and Robots.txt Compliance:** When you use XML sitemaps and proper robots.txt directives, good bots follow them and prioritize crawling the most important pages.
- **Ranking Signals Collection:** Search engines gather data on page speed, mobile responsiveness, content quality, and user engagement. Crawlers often trigger this analysis.
Without these crawlers, your site may be invisible to search engines, which means no traffic, no rankings, and no conversions.
### **Risks from Bad Bots**
Bad bots behave very differently. Instead of helping your site, they often waste your bandwidth, distort your data, or even pose security threats. Let us explore how:
- **Analytics Distortion:** Bots can inflate pageviews, bounce rates, and session counts in your analytics tools. This makes it hard to understand how real users interact with your site.
- **Server Load and Performance Issues:** Malicious or aggressive bots can overwhelm your server with too many requests. This slows down your site for real visitors and can even lead to crashes.
- **Content Scraping:** Scrapers steal your content and republish it without permission. This can hurt your rankings if Google finds the stolen version first.
- **Price and Data Theft:** eCommerce sites are often targeted by bots that scrape prices, product descriptions, or stock data. Competitors may use this data for unfair advantage.
- **Ad Fraud and Click Abuse:** Some bots are designed to click on ads to inflate traffic and costs, or to simulate user behavior and deceive ad tracking systems.
- **Security Risks:** Some bots look for vulnerabilities like open ports, outdated plugins, or misconfigured servers. These can lead to malware infections or data breaches.
## **Bot Management Strategies And Tools**
Managing bots is not just about blocking bad ones. It is about building a smart system that protects your website while allowing helpful bots to do their job. A clear **bot management strategy** is essential for your server health, SEO performance, and security. It starts with understanding how to identify bots, then using the right tools and rules to manage them effectively.
Let us look at the most important methods and tools you can use to control the traffic from your **crawler list**.
### **How to Use robots.txt And Sitemaps Effectively**
The robots.txt file is your first line of control over how bots behave on your site. It is a simple text file placed in the root directory of your domain (like yourdomain.com/robots.txt). This file gives instructions to bots on which pages they can or cannot visit. Here is how it works:
- **Allow and Disallow:** You can allow or block entire sections of your site. For example, you might disallow /private/ or /cart/ if those pages do not need to be crawled.
- **User-agent Rules:** You can write different rules for different bots. For example, one rule for Googlebot and another for SemrushBot.
- **Crawl-delay:** Some crawlers support this directive. It tells them to wait a few seconds between requests. This reduces server load.
However, keep in mind that robots.txt is only a request. Good bots follow it. Bad bots often ignore it. That is why robots.txt should not be your only protection.
**Sitemaps**, on the other hand, help good bots crawl your site more efficiently. A sitemap is an XML file that lists all the important pages on your site. It helps crawlers understand your structure and prioritize content.
When you submit a sitemap to Google Search Console or Bing Webmaster Tools, it tells search engines where your key content is located and how often it changes. This can speed up indexing and improve your visibility.
### **Identification Methods: User-Agent + IP Verification**
Every bot that visits your site sends a **user-agent** string. This is like an ID tag that tells you which software is making the request. For example: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
By analyzing user-agents, you can detect and categorize crawlers. You can allow verified ones and block suspicious ones. But it is not always simple. Some malicious bots spoof legitimate user-agents to avoid detection.
To improve accuracy, you can verify bots by checking their **IP addresses**. For instance:
- Google offers a reverse DNS check so you can confirm that a bot claiming to be Googlebot is really from Google’s network.
- Cloudflare and other services allow you to set rules that allow only verified IP ranges from trusted bots.
This extra verification is useful when you want to allow crawlers like GPTBot or ClaudeBot while keeping out impersonators.
### **Bot Detection And Behavior Monitoring**
Besides static rules, you can also monitor how bots behave in real-time. This helps you detect unusual activity, like:
- High request rates from one IP
- Crawling restricted pages
- Ignoring crawl-delay or robots.txt
- Accessing scripts or backend paths
**Behavioral analysis** can flag bots that disguise themselves as regular users. Many modern systems use **machine learning** to detect patterns in bot traffic and flag anomalies. These systems analyze timing, request headers, page paths, and session behavior. Some platforms offer dashboards where you can:
- View real-time bot activity
- See which bots consume the most bandwidth
- Detect unknown crawlers
- Set automated rules for response
## **Manage Bot with xCloud’s AI Bot Blocker**
Several tools and services help manage bots on your site. These platforms combine detection, reporting, and mitigation into one system.
To manage bots effectively, you need the right tools. Several platforms now offer complete solutions that combine bot detection, behavior tracking, and real-time protection. Popular services include Cloudflare Bot Management, DataDome, Akamai Bot Manager, HUMAN Security, Imperva, and Radware. These tools help you monitor crawler activity, control access, and defend against malicious bots that may steal content or overload your server.
To block bots effectively, you can use xCloud’s [**AI Bot Blocker**](/docs/enable-ai-bot-blocker-in-xcloud/). This tool uses advanced AI to detect bots based on behavior, not just user-agent strings. It helps you stop impersonators, scrapers, and high-frequency crawlers before they harm your site. You can allow verified bots, block unknown ones, and set crawl limits with ease.
Watch the detailed video here to see how xCloud’s AI Bot Blocker works and how it can protect your content and performance.
## **Best Practices for Managing Your Crawler List**
Once you understand which bots are accessing your site, the next step is to manage them wisely. Having a complete and up-to-date **crawler list** allows you to create a balanced strategy. You want to let useful bots in, slow down the noisy ones, and block the ones that bring harm. Here are key best practices for managing your crawler list effectively.
### **Allow Good Bots And Block or Limit Bad Bots**
The most important rule is simple: **encourage helpful crawlers, discourage harmful ones**.
Good bots follow crawling rules and bring real benefits. These include Googlebot, Bingbot, Applebot, and trusted SEO tools like AhrefsBot. You should make sure they are not unintentionally blocked.
Bad bots often ignore robots.txt, disguise their user agents, and crawl aggressively. These include scrapers, brute force tools, and some AI bots that do not respect your rules. These bots can:
- Copy your content
- Consume your bandwidth
- Distort your analytics
- Scan for vulnerabilities
To stop bad bots, use layered controls like:
- Blocking user-agents by name
- Rate-limiting access per IP
- Denying suspicious IP ranges
- Using captchas or bot challenges
This way, you reduce server load and protect your data without affecting useful crawlers.
### **Customize Per-Bot Crawl-Delay And Access**
Some bots behave well but crawl too frequently. If you allow them unrestricted access, they may overload your server or slow down your site. To manage this, you can:
- Set a **crawl-delay** in robots.txt for specific bots
- Limit access to high-impact pages
- Exclude unnecessary directories from crawling
- Allow bots only during off-peak hours (if your server supports scheduling)
For example, you might allow AhrefsBot but tell it to crawl slowly so it does not interfere with real user traffic. This way, you keep the benefits of SEO tools and data indexing without hurting site performance.
### **Regular Review and Adjustment of Policies**
Your bot management policy is not something you write once and forget. The **crawler ecosystem changes constantly**, especially with the rise of AI bots, new search platforms, and evolving scraping techniques.
Every few weeks or months, you should:
- Review server logs to identify new user-agents
- Add or remove bots from your crawler list
- Adjust crawl delays or access based on current server load
- Re-verify bot IPs to ensure they are genuine
- Monitor traffic for abnormal spikes or bot-like behavior
Keeping your crawler list updated is like tuning a machine. It improves performance, prevents breakdowns, and supports long-term stability.
### **Logging, Analytics, And Internal Link Auditing**
To manage bots effectively, you need data. Use logging tools or analytics software to track crawler behavior. These tools can tell you:
- Which bots access your site most often
- Which pages they visit
- How much bandwidth they use
- Whether they follow your rules
You can also use this data to optimize your **internal linking**. Crawlers depend on links to find new pages. If important pages are buried too deep or have no internal links pointing to them, they may be ignored. Here’s how to support crawler access:
- Make sure your important content is reachable from your homepage
- Use clean, crawlable internal links (avoid JavaScript-based navigation)
- Check your sitemap regularly and update it when you add or remove content
- Identify orphaned pages and link to them from relevant parts of your site
Internal link audits help both humans and bots discover your content. A strong internal structure improves crawl efficiency and SEO performance.
With these best practices, your **crawler list** becomes a powerful tool. You will know who is visiting your site, why they are there, and how to control the experience. You will also protect your content, speed up your pages, and keep your analytics clean.
**Frequently Asked Questions**
### **2\. What should I allow in robots.txt vs. block at the server or firewall level?**
Use robots.txt to guide good bots. It is ideal for:
- Controlling access to certain directories
- Setting crawl delays
- Directing bots to your sitemap
However, robots.txt is not secure. Bad bots often ignore it. For stronger protection, block malicious bots at:
- **Firewall or CDN level (e.g., Cloudflare)**
- **Web server rules (like Apache’s .htaccess or NGINX rules)**
- **Bot management platforms (like Cloudflare, xCloud’s AI Bot Blocker)**
Combine both methods for layered security. Use robots.txt to guide good bots and stronger tools to block the bad ones.
### **3\. How can I verify if a bot is genuine (e.g., Googlebot, GPTBot)?**
Some bots pretend to be trusted crawlers. To confirm a bot’s identity, do a reverse DNS lookup on its IP address. For example:
- If a bot claims to be Googlebot, verify its IP resolves to \*.googlebot.com.
- Google provides an official verification guide.
- OpenAI and Anthropic also publish guidelines and IP ranges for GPTBot and ClaudeBot.
Do not trust the user-agent alone. Spoofing it is easy. Always check the source IP if security is a concern.
### **4\. Should I allow AI bots that crawl my content for training purposes?**
This depends on your content strategy. Allowing AI bots may:
- Help your content show up in AI-generated answers
- Expose your content to broader audiences
- Lead to backlinks and visibility
However, it also comes with risks:
- Your content may be used without credit
- Bots may crawl aggressively
- You lose control over how your words are reused
To block AI bots like GPTBot or ClaudeBot, add this to your robots.txt:
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
Some site owners also implement **CAPTCHAs, JavaScript challenges, or paywalls** to limit access. It depends on your goals.
## **Wrapping Up: So, Why Does Your Crawler List And Bot Management Matter?**
Bots make up most of your traffic. Some bots boost your SEO and help users find your content. Others scrape, overload, or deceive. If you want control, speed, security, and clean data, you need to manage your crawler list.
Use smart rules, reliable tools like xCloud’s AI Bot Blocker, and monitor everything. With good bot management, your site will be faster, safer, and more visible to the right audience.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# How to Create a Staging Environment in xCloud [Guide for WooCommerce Included] - xCloud
> Test changes on your website without breaking your live site. Learn how to create a staging environment in xCloud for worry-free development & website updates.
Want to safeguard your website from potential risks? A staging environment is like a safety net, letting you test new features without risking your live site. With xCloud, it is simple to [**create a staging environment**](/docs/how-to-create-a-staging-environment-in-xcloud/), even if you are not a tech expert. Just follow this guide to easily set up and use your staging environment in xCloud.
## **What is a Staging Environment?**
A staging environment allows you to test new features, plugins, themes, or updates without any risk to your live site. For web developers and site administrators, this is crucial because it means you can experiment freely, knowing that your changes will not accidentally break something that is already working perfectly.
In the world of website management, where one small mistake can lead to a major crisis, having a [**staging environment**](https://essential-addons.com/wordpress-staging-site/) is not just extra work it is a smart and secure move. If you are using **xCloud hosting**, you are in for a treat. [**xCloud**](/) makes the process of creating and managing a staging environment seamless, even for those who might not be tech-savvy.
This guide will walk you through every step you need to take to create a **staging environment in xCloud**, deploy it, and manage your data efficiently between your staging and production sites.
## **Why a Staging Environment is Essential for Your Website**
Before we dive into the technical details, it is important to understand why a staging environment is crucial. Imagine you are running an online store and decide to install a new plugin to enhance the user experience. Without a staging environment, you would need to install that plugin directly on your live site.
If the plugin causes a conflict or error, your customers could encounter a broken page, or worse, they might be unable to make purchases. The result? Lost sales and frustrated customers. A staging environment allows you to test such changes safely, ensuring your live site remains unaffected by potential issues.
A staging environment acts as a buffer zone, allowing you to catch potential problems before they affect your real-world users. But the benefits do not stop there:
1. **Risk-Free Experimentation:** A staging environment lets you try out new features or changes without fear. Whether it is a new plugin, a theme, or a major update, you can see exactly how it will behave on your site without risking the live version.
2. **Performance Testing:** Before rolling out changes, you can test how they affect your site’s performance. This is crucial for maintaining a fast and smooth user experience.
3. **Bug Fixing:** Debugging on a live site can be a nightmare. A staging environment allows you to identify and fix bugs without any pressure, ensuring a smooth experience for your users once the changes go live.
4. **Security:** Sometimes updates or changes can introduce security vulnerabilities. Testing in a staging environment helps you ensure that your site remains secure before the updates go live.
5. **Backup and Recovery:** xCloud makes it easy to back up your site before making changes. This way, if something does go wrong, you can quickly revert to the previous version without any data loss.
Overall, a staging environment is essential for safely testing changes, ensuring your live site remains secure, bug-free, and performing at its best before going live.
## **How to Create a Staging Environment in xCloud?**
Now that we understand the importance of a staging environment, let us get started on creating one in xCloud. Follow these step-by-step instructions below to create a staging environment in xCloud and manage data transfers between staging and production sites.
### **Step 1: Create a Staging Environment in xCloud**
First, log into your xCloud account to access your dashboard. Select the server hosting of your live site. If you have not created a live site yet, do so first, as the staging environment requires an existing production site to clone.
**_Note:_** _Before creating your staging environment, name it clearly (e.g., ‘_**_mystore-staging_**_’), clone the latest live site data, and verify that permissions and access levels are correctly set to prevent unauthorized changes._
### **Step 2: Deploy Your Staging Environment**
Now that you have created the staging environment, the next step is to deploy it. xCloud simplifies this process, so even if you are not particularly tech-savvy, you will find it easy to follow along.
On your xCloud dashboard, you can quickly create a staging environment by expanding the drop-down found beside the site name and selecting ‘**Add Staging Environment**’ or clicking on the ‘**Deploy Staging**’ button.
A confirmation window will appear, explaining how staging works in xCloud. Simply confirm by clicking on the ‘**Deploy Staging**’ button. Within moments, xCloud will deploy your staging environment, complete with a test domain.
Once deployed, you can begin customizing your staging environment. This could involve installing new plugins, updating themes, or making any other changes you need to test. With your staging environment deployed, you now have a safe space to make and test changes without any risk to your live site.
### **Step 3: Pull and Push Site Data**
Once your staging environment is live and running, it is time to manage the data between your staging and production sites. This is where the real power of xCloud comes into play, allowing you to seamlessly transfer data between environments.
Navigate to the ‘**Staging Management**’ tab on your staging site page. Here, you will find options for pulling and pushing data, as well as access to deployment logs. These logs are incredibly useful for tracking changes and ensuring that everything is working as expected.
If you need to update your staging environment with the latest data from your live site, click on the ‘**Pull Data**’ button. You will have two options to pull: **Files** and **Database**. Plus, you can choose to overwrite all files or keep the most recent updates since the last pull with the ‘**Incremental**’ option.
You can pull the full database or select specific tables to import only the data you need. Once you are done selecting, hit the ‘**Pull Data**’ button.
**_\[Note\]_** _This is especially useful if you are only working on specific sections of your site._
Your data pull will initiate and will be completed in a few seconds. You can see the pull status and record in the ‘**Deployment Logs**’.
To push data from the staging environment to the production site, click the ‘**Push Data**’ button. A popup will appear, allowing you to select files and databases to push. You can choose to overwrite all files or apply the most recent updates using the ‘**Incremental**’ option.
**_Note:_** _if you are a **woocommerce** user creating a staging site pushing data might conflict with your live site data for products, orders, or transactional values. Create a backup and use a secure method to data._
Alternatively, you can push the entire database or select specific tables from staging to live. However, xCloud strongly recommends backing up the production site before pushing data to prevent any potential data loss in case of errors.
After selecting your preferred options, click the ‘**Push to Production**’ button to initiate the data push. The process will be completed within seconds. During the push, xCloud backs up your environments, overwrites the destination, and clears the cache. You can view the push status and records in the ‘**Deployment Logs**’.
After pushing data from staging to production, it is essential to perform some final checks on your live site. Make sure that all functionality is working as expected, and that no critical features have been disrupted. It is also a good idea to have a few other people test the site from different devices and browsers to ensure everything is working smoothly.
This is how efficiently you can create a staging environment to pull and push site data in xCloud between your production site and staging.
## **How to Avoid Data Conflict in WooCommerce Push for Product And Order?**
Whenever you push data from a staging site to a live website in xCloud, it is crucial to ensure that WooCommerce orders, customers, and products on the live site remain unaffected. Unfortunately, there is no automatic way to prevent these items from copying or merging between the staging and live sites. However, you can avoid losing your essential WooCommerce data with careful manual work.
While certain plugins promise seamless WooCommerce data merging between staging and live environments, their performance in practice often needs to improve. The potential for unintended data overwrites poses a serious threat to order and product integrity.
To safeguard your data, it is essential to adopt a manual approach when transferring WooCommerce data between staging and live sites.
### **Understanding How WooCommerce Stores Data**
**WooCommerce** and **WordPress** store their data, including orders, products, and user information, in specific database tables.
Orders and products, for instance, are stored in the **wp\_posts** and **wp\_postmeta** tables under a custom post type labeled ‘**orders**‘. User information is stored in **wp\_users** and **wp\_usermeta**, while other WooCommerce-specific data like tax rates and order items are stored in custom tables, typically prefixed with ‘**\_woocommerce**.’
**Note:** In xCloud Database table files are labeled differently on different sites
### **Three Methods to Prevent Data Overwrite**
To migrate data from your staging site to your production site while ensuring WooCommerce data on the live site remains untouched, consider the following methods:
#### **1\. Selective Table Exclusion**
In this method, you **exclude all database tables** except for the **\_options** table and select only the necessary plugins and themes to push. This prevents the loss or overwriting of any data generated on the live site after the staging site was created. However, any missing data must be recreated manually on the live site after the push.
#### **2\. Export And Import WooCommerce Data**
This method involves exporting orders, user data, and other transactional data from the live site and importing them into the staging site before pushing it live. This allows you to safely copy the entire staging site while preserving live **WooCommerce data**. For those unfamiliar with the **database structure**, this is the recommended approach.
#### **3\. Exclude Modified Tables**
Here, you exclude modified database tables like **\_posts** and **\_postmeta** from the push process. While this prevents certain data from being overwritten, it may result in missing images or layout elements on the live site, particularly if you use visual editors like **Gutenberg** or [**Elementor**](https://wpdeveloper.com/go/elementor/). Use this method only when necessary, as it can disrupt your site’s design and functionality.
To ensure data integrity and prevent conflicts when transferring WooCommerce data between staging and live sites, it is crucial to avoid automatic merging. By following the recommended methods you can safely migrate data while preserving your live site’s WooCommerce information.
## **Advanced Tips for Managing Your Staging Environment**
Creating and managing a staging environment in xCloud is straightforward, but there are a few advanced tips that can make your life even easier:
1. **Automated Backups:** Set up automated backups of your staging and production environments. This ensures that you always have a recent version to revert to in case something goes wrong.
2. **Version Control:** Use version control software like Git in conjunction with your staging environment. This allows you to track changes more effectively and collaborate with other developers.
3. **Regular Updates:** Keep your staging environment updated with the latest data from your live site. This ensures that your tests are always conducted in an environment that closely mirrors your production site.
4. **Security Testing:** Use your staging environment to test the security of your site. Run vulnerability scans and penetration tests to identify and fix potential security issues before they reach your live site.
5. **Stress Testing:** If you are planning a major update or expecting a surge in traffic, use your staging environment to conduct stress tests. This will help you identify potential bottlenecks and optimize your site’s performance before the changes go live.
6. **User Testing:** Before pushing changes live, consider running user tests in your staging environment. Gather feedback from real users to ensure that the changes improve the user experience.
7. **Documentation:** Keep detailed documentation of all the changes you make in your staging environment. This can be invaluable if you need to troubleshoot issues or revert to a previous version.
8. **Collaboration:** If you are working with a team, ensure that everyone has access to the staging environment and is on the same page regarding changes. Clear communication can prevent costly mistakes.
You can enhance the efficiency and security of your staging environment in xCloud, ensuring smooth updates and a seamless experience for both your team and users by implementing these advanced tips.
## **Securely Create & Manage Staging for a High-Performance Website**
Creating a **staging environment in xCloud** is not just about protecting your live site. It is about empowering yourself to be confident that your site visitors will always have a smooth, uninterrupted experience.
xCloud’s staging environment tools are designed to be user-friendly while offering powerful features for more advanced users. Following the steps in this blog you can create a robust staging environment in **xCloud** that keeps your site safe, secure, and performing at its best. If you found this blog helpful, [**subscribe to our blog**](/blog/) for more tutorials, guides, and tips on web hosting and server management. Join our [**Facebook Community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# A Comprehensive Guide On CSV Injection & How To Prevent It - xCloud
> A comprehensive guide on CSV injection and how to get rid of it with simple yet effective tips and tricks.
These days, many web applications let you export data into CSV files. While this is super handy, it can also lead to a risk known as CSV injection. It is important to make sure these exported files are safe and do not leave users vulnerable to attacks. In this blog post, we will take a closer look at CSV injection and how you can prevent it to **[protect your data](/docs/use-xcloud-7g-firewall-on-nginx/)**.
## **What is CSV Injection & When It Occurs?**
CSV Excel Macro Injection, also known as **Formula Injection or CSV Injection**, is an attack method used in regular penetration testing of applications. CSV injection is a vulnerability found in applications that allow users to export data as spreadsheets. These spreadsheets are generated from user inputs that have not been properly validated or filtered.
Many modern web applications let users download data in **.csv or .xls file formats**. This is convenient for spreadsheet applications like MS Excel and OpenOffice Calc, but it also means that cells in the spreadsheets can include data from untrusted sources. Consequently, users who open these exported spreadsheets may be at risk.
### **CSV Injection Attack: In Simple Terms**
✅ A CSV Injection Attack happens when malicious websites insert harmful code into CSV files.
✅ This attack is particularly dangerous because it exploits cells starting with these characters: equal sign (=), plus sign (+), minus sign (-), and the @ symbol.
✅ When the harmful code is entered as a formula in a CSV file, it can execute commands that harm the computer by manipulating, accessing, or deleting user data.
✅ Another method for this attack is through DDE (Dynamic Data Exchange), which allows the execution of arbitrary code on the computer.
## **How Does CSV/Formula Injection Attack Work?**
To learn how the CSV injection attack works, let us have a look at the below data set. The first row lists the column headers of the data set: Name, Email, and Phone.
Each following row contains a contact’s data, with values separated by commas. This data includes each person’s name, email address, and phone number.
**John Doe,john@example.com,=SUM(1,2)**
**Jane Smith,jane@example.com,555–1234**
In this example, an attacker could inject a formula like **\=SUM(1,2)** into the third column. When the CSV file is opened in a spreadsheet application, it would perform unintended calculations.
Here is how it might happen in a real-world application:
Suppose you have an app that collects user input. When the user clicks the ‘**Submit**’ button, the app sends the data to the backend and generates a CSV file. If the backend does not validate the input, it is vulnerable to this kind of attack.
Since there is no validation, any field can be targeted. The attacker chose the Phone field and injected the formula **\=SUM(1,2)**.
When the user opens the downloaded file in Excel/Google Sheets, the Phone field will display the number 3 because the formula adds 1 and 2.
You might think it is no big deal. After all, someone just added up two numbers; it can not harm you or your customers. But in reality, it actually does.
For example, hackers can sneak into a user’s computer using something called a reverse shell. The formula makes the computer download a harmful exploit.exe file from the web and run it. This gives the hacker access to the user’s system.
Sometimes, hackers trick users into clicking links that take them to malicious websites. They can even steal Google Docs. You can see how risky this is! And there are many more ways hackers can cause trouble. So, you need to know how to prevent this CSV injection to protect your data.
## **CSV Injection Prevention: The Easiest and Possible Solutions**
CSV injection can be a real threat if user input is not handled properly before adding it to a CSV file. Here is a straightforward guide to keep your CSV files safe:
### **General Tips to Prevent CSV Injection**
💡 **Avoid Direct User Input:** If possible, do not use user input directly in your CSV files.
💡 **Validate Input:** Check that the input meets the expected criteria.
💡 **Sanitize Input:** Clean the input to remove any harmful content.
### **Important Characters to Watch Out For**
There are a few things you need to be aware of while preventing CSV injection. Keep an eye on these characters:
👉 Equals sign (=)
👉 Plus sign (+)
👉 Minus sign (-)
👉 At symbol (@)
👉 Tab (0x09)
👉 Carriage return (0x0D)
### **Handling Dangerous Characters**
It is not enough to ensure that user input does not start with these characters. Be cautious of field separators (like commas or semicolons) and quotes, as these can help attackers manipulate the cell content.
### **Safe Practices**
To ensure safety, apply these methods to each CSV field:
💡 **Wrap Fields in Double Quotes:** This helps the spreadsheet editor read the content as text.
💡 **Prepend with a Single Quote:** This further ensures that the content is treated as text.
💡 **Escape Double Quotes:** Use an additional double quote to escape each double quote in the content.
By following these simple steps, you can significantly reduce the risk of CSV injection and keep your data secure.
Let us have a few examples 👇
**Before Sanitization**
**After Sanitization**
\=1+2″ ; = 1+2
” ‘=1+2″” ; = 1+2″
\=1+2′ ” ; ,= 1+2
” ‘=1+2’ “” ; ,= 1+2″
## **Sanitize Files and Prevent CSV Injection Easily**
CSV injection is a significant security risk for web applications that allow data export to CSV files. This type of attack can lead to data manipulation, unauthorized access, or even the execution of harmful commands. To protect against CSV injection, it is crucial to sanitize CSV files before they are opened.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# CyberChef Hosting - xCloud
> Managed CyberChef hosting on xCloud. Deploy the open-source, browser-based toolkit for encryption, encoding, compression and data analysis on a Docker server in one click, with free SSL, backups, and 24/7 support.
## Deploy your AI Agent in 1-Click - Managed Hermes Agent Hosting starts from $9.99
[Get Started Now](/hermes-agent-hosting/)
[](/)
Toggle Menu
Close Menu
[Menu](#)
[Solutions](#)Close SolutionsOpen Solutions
## Hosting Solutions
## Managed WordPress Hosting
Fast, secure WordPress hosting with automated updates, backups and more.
## WooCommerce Hosting
Managed hosting supporting high traffic sites, millions of checkouts per minute.
## Laravel Hosting
Laravel-optimized hosting with staging, SSL, and streamlined deployment tools.
## LLM Hosting
High-performance platform built for hosting large language models.
## n8n Hosting
Managed n8n hosting with optimized performance, a free SSL certificate, and more.
## OpenClaw Hosting
Secure AI agent hosting with Firewall, updates, backups, SSL and more
## Node.js Hosting
Easily deploy server-side or client-side app with Node.js hosting.
## Hosting Addons
Power Up Your Hosting Experience with Premium Addons
[](https://xcloud.host/deploy-openclaw)
[Pricing](/#pricing)
[Providers](#)Close ProvidersOpen Providers
## Cloud Providers
## xCloud Managed Hosting
Fully managed cloud hosting solution with full server backup & more
## DigitalOcean Hosting
Fast, easy cloud deployments on DigitalOcean with $200 credits for new user.
## Vultr Hosting
Feature-packed managed Vultr hosting with $100 free credits.
## Hostinger VPS
Bring your Hostinger VPS and manage with xCloud's advanced control panel.
## Any Provider
Connect your Ubuntu server to our platform and manage with powerful features easily.
## AWS Hosting
Optimized AWS hosting engineered for performance, security, and scalability.
## Google Cloud Hosting
Experience the power of Google Cloud with xCloud's user friendly platform
## Linode Hosting
Unleash the power of Linode servers with our feature-packed panel.
## Next Gen Hosting Built For Stability, Security & Speed
- 
### No Restrictions On Traffic & Sites.
- 
### Full Server Backup
## [Starts at **$5**/Month](#)
[Features](#)Close FeaturesOpen Features
## Features
## App Deployment
## Server Management
## Scheduled Tasks
## Monitoring & Alerts
## Security, SSL, Firewall
## Git, CLI & Dev Tools
## Staging Environments
## Team Collaboration
## Backups & Snapshots
## One Click Apps
## AI Website Builder
[See All Features](/features)
## Managed n8n Hosting:
For Smart & No-Code
Automation
[Learn More](/n8n-hosting/)
[Integrations](#)Close IntegrationsOpen Integrations
## Integrations
## WhatsApp Notifications
Get instant alerts and updates delivered straight to WhatsApp.
## Cloudflare Integration
Deliver content at top speed worldwide with built-in Cloudflare integration.
## Git Provider
Connect your repositories and automatic deployments from your Git projects.
## Google Drive Storage
Securely store automated backups in your Google Drive account for your backup.
## Slack Alerts
Connect to Slack for real-time performance and event notifications.
## Object Cache PRO
Speed Up Your WordPress Application Using Object Cache Pro.
## Mailgun
Integrate Mailgun in WordPress to send transactional emails easily.
## Connect Us :
- [](https://www.facebook.com/xCloud.host)
- [](https://x.com/xCloud_host)
- [](https://www.linkedin.com/company/xcloud.host/)
- [](https://www.youtube.com/@xCloud-Hosting)
- ### [Documentation](/docs)
- ### [Tutorials](https://www.youtube.com/@xCloud-Hosting)
## Get In Touch
Talk to our support team for any issues.
- ### [support@xcloud.host](mailto:support@xcloud.host)
[Talk To Us](/support)
## Join our global community
[](https://www.facebook.com/groups/xcloud.community)
[Resources](#)Close ResourcesOpen Resources
## Resources
## Blog
Read the latest guides, news, insights, and industry updates.
## Comparison Pages
Compare providers, features, and plans to find your perfect match.
## Support Portal
Access support tickets and live expert support 24/7 for any issues.
## Documentation
Step-by-step technical docs to help you build with confidence.
## Case Studies
See how real businesses scale and succeed with xCloud.
## Write for Us
Submit your expert articles, contribute tutorials, guides, and insights.
## Watch & Learn
## Next Gen Hosting Built For Stability, Security & Speed
[See All Videos](https://www.youtube.com/watch?v=oEE9OHo3_48)
[Join Free](https://app.xcloud.host/register)
[Login](https://app.xcloud.host/login)
[Join Free](https://app.xcloud.host/register)
[login](https://app.xcloud.host/login)
[Join Free](https://app.xcloud.host/register)
## Managed Hosting for your own data toolkit
# Fully Managed
CyberChef Toolkit Hosting
Run the Cyber Swiss Army Knife on a domain you control using managed CyberChef hosting, with consistent performance and no maintenance work.
[Choose Your Plan](#pricing)
- 
### Starts at $24.99/mo
- 
### 24/7 Expert Support
- 
### No Lock-In, Cancel Anytime
## **How It Works**
## Simple Steps To Launch Your CyberChef Instance in Minutes
Deploy and manage your CyberChef instance with a carefully designed, streamlined workflow built for consistent speed, stability, and reliability from first deployment to everyday production use.
01
## Choose Your Server
Pick an xCloud managed server or connect your own provider, then set it up as a Docker server to deploy CyberChef.
02
## Select Application
Open One Click Apps in your xCloud dashboard and choose CyberChef from the available applications to begin the guided setup.
03
## Configure Your Instance
Add your domain and deployment settings in the xCloud dashboard. We serve the CyberChef build from your server, behind your own domain and certificate.
04
## Go Live Right Away
Confirm the setup and open your domain — CyberChef loads straight into the browser. There is no login, so decide who should reach it before you share the URL.
## Pricing
## Simple Pricing for Your CyberChef Instance
Your recipes get longer, your bill does not. CyberChef is a static bundle your own browser does the work for, so the entry tier is really headroom for everything else you run beside it.
## Cloud VPS 6GB
## $24.99
Renews at $24.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=f292a3d0-fbcc-4c23-be7b-67f9cd677c69&app=cyberchef)
- ### 6 GB RAM
- ### 100 GB NVMe SSD
- ### 4 vCPU cores
- ### 30TB Bandwidth
## Popular deal
## Cloud VPS 16GB
## $59.99
Renews at $59.99/mo. Cancel anytime.
[Get started](https://app.xcloud.host/cart/product/checkout?product=33a8077d-dedc-4187-967d-b023ae20ed5c&app=cyberchef)
- ### 16 GB RAM
- ### 200 GB NVMe SSD
- ### 6 vCPU cores
- ### 30TB Bandwidth
## Cloud VPS 24GB
## $84.99
Renews at $84.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=b9bc978a-fd8e-4aea-a847-02ad127c9bfb&app=cyberchef)
- ### 24 GB RAM
- ### 300 GB NVMe SSD
- ### 8 vCPU cores
- ### 30TB Bandwidth
## Features
## One Place To Decode, Convert & Inspect Every Blob.
CyberChef chains operations into a recipe and runs them against your input inside the browser. Hundreds of operations, a live output pane, and nothing sent to a server in between.
- ### Hundreds of operations in one recipe builder
- ### Every operation runs in your browser, not on the server
- ### Your own domain and your own access rules
- ### One-click deployment, free SSL, and firewall
## Capabilities
## A Platform built for the data you already handle
CyberChef is an open-source, browser-based toolkit built and released by GCHQ. You drag operations into a recipe — encoding, encryption, compression, hashing, parsing — and it runs them against your input inside your browser. What’s different when you host it is that the app is served from a domain you chose, rather than a public website.
## Recipes & Operations
Drag the operations you need into a recipe and reorder them freely — the output of each one becomes the input of the next.
## Auto Bake & Magic
CyberChef re-runs your recipe as you change it, and the Magic operation attempts to work out which encodings your input is already under.
## Entirely Client-Side
None of your recipe configuration or input is ever sent to the web server — all processing is carried out within your own browser.
## Large Inputs
Files of around 2 GB can be dropped straight into the input box, though how far you get depends on your browser and on the operations you run.
## Breakpoints & Stepping
Set a breakpoint on any operation to pause before it runs, then step through the recipe one operation at a time to see the data at each stage.
## Privacy Controls
CyberChef ships no login and no user accounts, so the instance is readable by anyone who can reach it until you restrict it. Self-hosting is not privacy on its own — you still configure it.
## Recipes You Can Share
Save a recipe to your browser, or share it as a URL. Note that the link carries the recipe and the input with it, so treat a shared URL as the data itself.
## Apache 2.0 & Crown Copyright
CyberChef is released under the Apache 2.0 Licence and is covered by Crown Copyright. It was built and released by GCHQ; xCloud is not affiliated with GCHQ or the CyberChef project.
## Advanced Features
## Ready To Own Your Toolkit?
Whether you decode ten strings a day or ten thousand, managed CyberChef hosting delivers the reliability, flexibility, and performance your team needs to work without limits. Deploy faster. Scale smarter. Stay in control.
## Fast Provisioning
Deploy faster using an xCloud Managed Server built with optimized stacks and high-speed SSDs.
## Enterprise-grade security
Protect your infrastructure with a free SSL certificate and more advanced security features at no additional cost.
## Intuitive Control Panel
From Server creation to application deployment, everything can be managed from our intuitive control panel.
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
**xCloud** isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Paul Goulart
@freelivingsoul
I set this up locally, tried AWS and Digital Ocean with disappointing results. Setup on Xcloud was easy and it’s still working!
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. xCloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## Your Toolkit Should Live On Your Own Domain.
Deploy a production CyberChef instance in minutes. Open your domain, build your first recipe, and keep
every byte you paste inside your own browser.
[Start Deploying Now](#pricing)
[Browse One Click Apps](/one-click-apps/)
- 
### No Lock-In
- 
### Cancel anytime
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What is CyberChef?
CyberChef is an open-source, browser-based toolkit for encryption, encoding, compression and data analysis — its own tagline is “the Cyber Swiss Army Knife”. You build a recipe out of operations and it runs that recipe against whatever you paste or drop into the input box. The thing worth knowing before anything else is that it is entirely client-side: none of your recipe configuration or input is ever sent to the web server, because all processing is carried out within your browser. CyberChef was conceived, designed and built by an analyst at GCHQ, and is released under the Apache 2.0 Licence and covered by Crown Copyright. Note what it is not: it ships no login and no user accounts, so an instance is readable by anyone who can reach the URL until you put something in front of it. The hosting on this page is xCloud’s; xCloud is not affiliated with GCHQ or the CyberChef project.
### How do I deploy CyberChef on xCloud?
CyberChef is available through xCloud’s One Click Apps. Create a Docker server in your xCloud dashboard, open One Click Apps, select CyberChef, add your domain, and deploy. xCloud provisions the container, maps the domain, and issues the SSL certificate for you. You then open your domain and CyberChef loads — there is no sign-in step, because there is no account system to sign in to. That makes the next decision yours: if the instance should not be public, restrict it before you share the URL, using the firewall rules or the IP access controls in your xCloud dashboard.
### Do I need a Docker server to run CyberChef?
Yes. CyberChef is deployed as a containerised application, so it needs to be deployed on a Docker server. What that container serves is a static web application — HTML, JavaScript and CSS — with no database behind it and no server-side processing, because the work happens in the visitor’s browser. It is the lightest kind of application in the catalogue, so the entry Cloud VPS tier is really headroom for everything else you run beside it. What grows with use is bandwidth rather than memory, because every visitor downloads the application bundle once. When you create a new server in xCloud, choose Docker as the server type — you can then deploy CyberChef to it from One Click Apps.
## xCloud is the future of cloud hosting and server management for WordPress users, streamlining the way you host, deploy, manage or update your websites like never before!
## Get The Latest Updates
- [](https://www.facebook.com/xCloud.host)
- [](https://x.com/xCloud_host)
- [](https://www.linkedin.com/company/xcloud.host/)
- [](https://www.youtube.com/@xCloud-Hosting)
## Address:
xCloud Hosting, LLC. 124 Broadkill Rd #599 Milton, DE 19968-1008
## Products & Services
## Resources
## Compare xCloud
## Addons
## Quick Help
## **Company**
- #### [Privacy Policy](/privacy-policy/)
- #### [Terms and Condition](/terms-and-conditions/)
## A **[WPDeveloper](https://wpdeveloper.com/)** Creation, in Partnership with **[WPManageNinja](https://wpmanageninja.com/)**
## **xCloud Hosting LLC**. All rights reserved.
---
# Global SSD VPS Hosting | 30+ Data Centers with 99.999% Uptime
> Deploy high-performance SSD VPS servers in 30+ global locations. Enjoy low latency, enterprise-grade security, and 99.999% uptime with xCloud Managed Server.
## Data Centers
# Host Around the World with xCloud Managed Server
Build trust with your customers by using a professional business
email address that includes your business name.
- 
### 30+ Data Centers
- 
### 100+ Uptime
[See the Locations](/data-centers/)
## 30+ Data Centers Worldwide
[Explore All Locations](/docs/31-server-locations-worldwide/)
## MAP
# Enterprise-Grade Infrastructure for
Powerful Hosting
Enjoy high-performance cloud hosting with a secure, reliable global
network built for any business.
## Constant Availability
We work with trusted data center partners who operate a broad network of edge facilities. These facilities keep your server online at all times .
## Localized Peering
Our network team constantly improves routing and peering agreements in every region. This ensures your enterprise-grade VPS hosting runs on a low-latency.
## Redundant Network
Every data center is designed to prevent downtime. Critical systems such as cooling, backup generators, and processors are duplicated.
## Low Latency Near You
Deploy SSD VPS servers in 30+ data center locations worldwide. Develop locally and launch close to your audience for the best speed and low latency VPS hosting.
## Vigilant Security
Every facility follows strict security protocols, including biometric scans, video surveillance, ID verification, mantraps, and on-site guards.
## 24/7 Monitoring
Our experts monitor systems day and night. The operations team works directly with on-site staff to ensure uninterrupted cloud service.
## MAp
## Enterprise-Grade Infrastructure for
Powerful Hosting
Enjoy high-performance cloud hosting with a secure, reliable global
network built for any business.
- ###### All Regions
## Region
## Location
## xCloud Managed Server
## Toronto
## Ontario, Canada
## Mexico City
## Mexico
## Warsaw
## Poland
## Atlanta
## Georgia, United States
## Honolulu
## Hawaii, United States
## Chicago
## Illinois, United States
## Dallas
## Texas, United States
## Los Angeles
## California, United States
## Miami
## Florida, United States
## New York Area
## New York, United States
## San Francisco Bay Area
## California, United States
## Seattle
## Washington, United States
## Amsterdam
## Netherlands
## London
## United Kingdom
## Manchester
## United Kingdom
## Frankfurt
## Germany
## Paris
## France
## Madrid
## Spain
## Stockholm
## Sweden
## Tokyo
## Japan
## Osaka
## Japan
## Seoul
## South Korea
## Singapore
## Singapore
## Bangalore
## Karnataka, India
## Mumbai
## Maharashtra, India
## Delhi NCR
## India
## Sydney
## New South Wales, Australia
## Melbourne
## Victoria, Australia
## Santiago
## Chile
## Tel Aviv-Yafo
## Israel
## Johannesburg
## South Africa
## Pricing
## Pick your Preferred Plan – n8n Hosting Included with All
Every plan includes secure n8n Hosting with SSL, backups, and updates. Whether you want to experiment or
scale, you can run your self hosted n8n without limits.
- ###### xCloud Managed Server
- ###### Self-Managed Server
### All
### 1 GB
For Personal Use
### 2 gb
For Basic Websites
### 4 gb
For Growing Websites
### 8 gb
For Busier Websites
### 16 gb
For Bigger, Busier Websites
### 32 gb
For HIGH-PERFORMANCE NEEDS
### 48 gb
For HIGH-PERFORMANCE NEEDS
### 58 gb
For HIGH-PERFORMANCE NEEDS
## Elevate your site with xCloud servers—ensuring speed and security, with no hidden charges in the future.
## Premium servers are powered by High-Frequency 3GHz+ Intel Xeon CPUs, lightning-fast memory, and NVMe storage, delivering unmatched speed and performance. General servers, on the other hand, offer a budget-friendly solution for standard workloads
- ###### All
- ###### 1 GB
- ###### 2gb
- ###### 4gb
- ###### 8GB
- ###### 16gb
- ###### 32gb
- ###### 48GB
- ###### 58GB
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
## Business Max
- ### 64 GB RAM
Ultimate plan for unparalleled power
- ### 1280 GB SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 10 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-max)
## $ **399.00** /mo
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
MonthlyYearly
MonthlyYearly
## Black Friday Special Deal : One-time Payment – LIFETIME Access!
Bring your own server and unlock access to our cloud control panel to enjoy a seamless server and site management experience for a lifetime.
[Grab Lifetime Deal](/deal/)
## Want to explore xCloud first? Try it out for free and then decide!
[Get started](https://app.xcloud.host/register)
## FREE PLAN
- ### 1 Server
- ### 10 Site
## Start your journey without cost
## Starter
- $5/Server (/month)
- 1-5 Servers
- Unlimited Sites
## Perfect for Beginner
## Professional
- $4/Server (/month)
- 6-10 Servers
- Unlimited Sites
## Tailored for Experts
## Agency
- $3/Server (/month)
- 11+ Servers
- Unlimited Sites
## Perfect for Large Teams
## Support
## Global Hosting, Built
for Performance and Reliability
Deploy a high-performance cloud server with secure VPS hosting that is close to your audience for faster delivery, seamless experiences, and round-the-clock reliability with xCloud Managed Server
[Migrate for Free](/data-centers/)
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Mary Basu
@tlewisverdu
Pretty happy with my n8n thru xCloud.
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Mary Basu
@tlewisverdu
I set this up yesterday – easy build, then jumped right in. I recreated a few of my existing workflows without any issues. Thanks, xcloud!
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
xCloud #wordpress #hosting
Brian Geovanny
SaaS Space
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. xCloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
[View More Testimonials](/reviews-and-testimonials/)
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### 1\. What does global VPS hosting with xCloud mean?
xCloud lets you deploy xCloud-managed VPS servers in 30+ data center locations worldwide. You choose a location close to your audience to get faster speed, lower latency, and better reliability.
### 2\. What uptime can I expect from xCloud?
xCloud delivers up to 99.999% uptime by using redundant systems for power, cooling, and networking. If one component fails, a backup activates instantly to keep your server online.
---
# 8 Data Leakage Examples & Prevention Tips for Websites
> Learn common website data leakage examples and how to prevent them. Protect sensitive information with expert tips and smart security strategies.
Data leakage is like letting important secrets slip out. Imagine if you told someone a secret, and then they told everyone else. That is similar to what happens with data leakage. Understanding data leakage is really important because it helps us keep our information safe. Today, we will explore data leakage, look at some real examples of how it happens, learn why it happens, and find out how we can prevent it. So let us roll down.
## **What is Data Leakage?**
Data leakage is the unauthorized transmission or exposure of information from within an organization to an external destination or recipient. This data can be anything from **personal identifiable information (PII)**, financial records, intellectual property, confidential [**business or personal information**](https://wpdeveloper.com/4-easy-steps-to-optimizing-google-business-profile/). Data leakage can occur in many forms and through various channels, making it a significant concern for both individuals and organizations.
Data leakage means the escape of sensitive data from its intended secure environment. This breach can happen intentionally or accidentally. This leakage leads to potentially severe consequences such as financial losses, legal ramifications, and reputational damage. Types of Data Leakage
## **Common Causes of Data Leakage**
Data leakage can happen for many reasons, often because of small mistakes or oversights that lead to big problems. Here are some of the most common causes of data leakage and how they might occur.
### **Poor Security Measures**
One of the biggest reasons for data leakage is inadequate security. This can be due to weak passwords, lack of encryption, or outdated security software. For example, if a company’s network does not require strong passwords, it might be easy for hackers to guess them and access confidential information. Similarly, if sensitive data is not encrypted, anyone who gains access to it can read it easily.
### **Human Error**
Many instances of data leakage are due to simple human errors. This could be anything from [**sending an email**](https://wpdeveloper.com/email-marketing-social-proof/) to the wrong person to misplacing a laptop or storage device with important data. For instance, an employee might accidentally attach a file containing personal customer information to a public newsletter. Such mistakes, although unintentional, can lead to serious breaches of privacy.
### **Insufficient Employee Training**
If employees are not properly trained on data security practices, they are more likely to make mistakes that could lead to data leakage. This includes not knowing how to identify phishing emails, mishandling sensitive data, or not following proper protocols when accessing or sharing information. Companies must regularly train employees to handle data securely and be aware of the potential risks.
### **Malicious Insider Threats**
Sometimes, data leakage is caused intentionally by employees or contractors who have access to sensitive data. These insiders might leak data to harm the company or benefit someone else. For instance, a dissatisfied employee might sell customer data to a competitor or post it online to damage the company’s reputation.
### **Technical Vulnerabilities**
Software and hardware vulnerabilities can also lead to data leakage. Hackers often exploit flaws in systems to gain unauthorized access to data. For example, if a company’s software is not regularly updated, it might contain security loopholes that hackers can use to steal information. Similarly, physical vulnerabilities, like unsecured servers or computers, can be accessed by unauthorized people.
### **Inadequate Data Disposal Procedures**
When old electronic devices like computers, hard drives, or mobile phones are disposed of without properly erasing the data, they can become a source of data leakage. People might recover the data from these devices and use it for malicious purposes. It is important for companies and individuals to follow strict data disposal protocols to ensure that no data remains on the equipment they discard.
### **Third-Party Services**
Using third-party services and vendors can also lead to data leakage. Sometimes, these third parties may not have stringent security measures, or they might experience their own data breaches, which can compromise your data. For example, if a company uses a cloud service provider that suffers a breach, all the company’s data stored on the cloud could be exposed.
### **Poor Network Security**
Weak network security is a significant risk for data leakage. This includes unprotected Wi-Fi networks, lack of network monitoring, and insufficient firewalls. If a company’s network is easily accessible, it could allow hackers to intercept data being transmitted across the network. For example, if an employee accesses sensitive company data over a public Wi-Fi network, hackers could capture that data through the network.
### **Lost or Stolen Devices**
Mobile devices like laptops, smartphones, and tablets can contain vast amounts of sensitive data. If these devices are lost or stolen and are not properly secured, the information on them can easily leak.
Each of these causes represents a potential vulnerability that can lead to data leakage. Recognizing these risks is the first step in preventing them.
## **Examples of Data Leakage**
Data leakage can happen in many different settings and affect various types of information. Let us look at some common examples to understand how data leakage occurs in real-life situations and the impact it can have.
### **Example 1: Hospital Records**
In a hospital, doctors and nurses use private information to take care of patients. This information includes medical histories, treatment plans, and personal details like addresses and social security numbers. If this information leaks, it can be very harmful. For instance, if a hospital employee accidentally sends patient information to the wrong person via email, that is data leakage. This can lead to privacy violations and the patients might feel unsafe because strangers know about their health conditions.
### **Example 2: School Records**
Schools hold a lot of personal information about students, such as grades, disciplinary records, and family backgrounds. If a teacher mistakenly shares this information with unauthorized people, that is a case of data leakage. An example is when a teacher loses a USB drive containing student records, and someone else finds it. This can harm student’s reputations and their future opportunities, as private academic or behavioral details could be exposed.
### **Example 3: Online Shopping**
When you shop online, you provide your credit card information, address, and possibly even your phone number. If the website has poor security, hackers might access this information. This data leakage can lead to unauthorized charges on your credit card or someone using your personal details to make fake accounts. For example, if an online retailer’s database is hacked and customer information is stolen, this would not only lead to financial losses for customers but also damage the retailer’s reputation.
### **Example 4: Email Mishaps**
Emails are a common way for information to leak. If someone sends an email containing sensitive information to the wrong recipient, that is data leakage. For example, a company employee might accidentally send a file with all the employees salaries visible to everyone in the company instead of just the HR department. This can cause dissatisfaction and distrust among employees, as private salary information is considered confidential.
### **Example 5: Unsecured Mobile Devices**
Many people store personal and work-related information on their mobile phones. If these devices are lost or stolen without proper [**security measures**](https://wpdeveloper.com/biggest-cyber-security-mistakes/) like encryption or passwords, the information can easily leak. For instance, if a salesperson loses a phone containing confidential client details, and someone else uses that information for malicious purposes, that is data leakage. This can lead to loss of business and trust between the salesperson and their clients.
### **Example 6: Cloud Storage Errors**
Storing data in the cloud is common, but if not managed properly, it can lead to data leakage. An example is when someone configures the security settings incorrectly, allowing unauthorized access to sensitive documents. For instance, a company might store its business plans in a poorly secured cloud storage service, and competitors might access and use this information to gain a market advantage.
### **Example 7: Disposal of Old Equipment**
When companies or individuals throw away old computers and storage devices without properly deleting the data, they risk data leakage. For example, if a company disposes of old computers with the employee information still on the hard drives, and scavengers retrieve these details, the employees could become victims of identity theft.
### **Example 8: Insider Threats**
Sometimes, data leakage happens not by accident but because someone inside the company decides to leak information. This could be an unhappy employee who shares trade secrets with a competitor. For example, an engineer at a tech company might take proprietary software code and give it to a rival company, which uses it to create similar products.
## **How Does Data Leakage Affect Us?**
Data leakage can have serious consequences for both individuals and organizations. Here’s how it can impact us:
1. **Financial Loss:** For companies, data leakage can lead to significant financial damages. This includes the costs of fixing the leak, legal fees if the leakage results in litigation, and fines if the leakage violates data protection laws. For individuals, data leakage can mean financial theft, like someone using your credit card details to make unauthorized purchases.
2. **Loss of Reputation:** When companies suffer from data leakage, their reputation can be badly damaged. Customers and clients might lose trust in the company’s ability to safeguard their information, which can lead to lost business and a tarnished brand image.
3. **Identity Theft:** For individuals, one of the scariest outcomes of data leakage is [**identity theft**](https://wpdeveloper.com/free-tools-to-scan-wordpress-for-vulnerabilities/). If personal details like Social Security numbers, addresses, and birth dates are leaked, criminals can use this information to impersonate you. This can lead to unauthorized account openings, false applications for loans, and other fraudulent activities using your name.
4. **Operational Disruption:** Data leakage can disrupt the normal operations of a business. If sensitive internal information, like strategic plans or proprietary technology, is leaked, it can affect competitive advantage and day-to-day functioning.
5. **Legal and Regulatory Consequences:** There are many laws and regulations around data protection. Data leakage can lead companies to face legal penalties, regulatory fines, and mandatory audits, all of which require time and resources to address.
By understanding these impacts, it becomes clear why preventing data leakage is crucial for protecting our personal and professional lives.
## **Tips to Fight Data Leakage**
Preventing data leakage involves a combination of good practices, awareness, and the right technology. Here are some practical tips to help individuals and organizations minimize the risk of data leakage and keep their information secure.
### **Implement Strong Password Policies**
One of the simplest yet most effective ways to prevent data leakage is to use strong, unique passwords for all accounts. Passwords should be long, include a mix of characters (numbers, letters, and symbols), and be changed regularly. Additionally, implementing multi-factor authentication (MFA) provides an extra layer of security, making it harder for unauthorized users to gain access even if they know the password.
### **Educate and Train Employees**
Regular [**training on**](https://wpdeveloper.com/social-engineering-attacks-wordpress-security/) **[data](https://wpdeveloper.com/social-engineering-attacks-wordpress-security/)** [**security**](https://wpdeveloper.com/social-engineering-attacks-wordpress-security/) best practices is crucial. Employees should be aware of the risks of data leakage and how their actions can impact security. Training programs should cover topics like phishing, safe internet practices, and the importance of reporting suspicious activities. Creating a culture of security within the organization can significantly reduce the risk of data leakage due to human error.
### **Use Encryption**
Encrypting data makes it unreadable to anyone who does not have the key to decrypt it. This should be applied to data at rest (stored data) as well as data in transit (data being transmitted). Using strong encryption methods can prevent data leakage even if unauthorized individuals access the data.
### **Secure Physical and Network Access**
Physical security measures, such as securing offices and data centers with access controls, can prevent unauthorized access to physical machines and storage devices. Similarly, securing the network with firewalls, intrusion detection systems, and regular monitoring can help detect and block malicious activities before they lead to data leakage.
### **Monitor and Control Data Access**
Limiting access to sensitive data to only those who need it can minimize the risk of data leakage. Implementing access controls and keeping detailed logs of who accesses data and when can help identify potential security breaches before they cause significant damage.
### **Implement Data Loss Prevention (DLP) Tools**
Data Loss Prevention tools can automatically detect and block potential data leakage points across a network. DLP tools work by identifying sensitive data and monitoring its use, preventing unauthorized sharing or transmission outside the company.
### **Regularly Update and Patch Systems**
Keeping software and systems updated is critical to protect against known vulnerabilities. Hackers often exploit outdated systems with known security flaws. Regular updates and patches ensure that these loopholes are closed, reducing the risk of data leakage.
### **Manage Third-Party Risks**
When working with third-party vendors or service providers, it’s important to assess their security practices. Ensuring that third parties adhere to stringent security standards can prevent data leakage that might originate from less secure systems. Contracts should include clauses that hold third parties accountable for maintaining the security of any data they handle.
### **Develop a Response Plan**
Despite the best efforts, data leakage can still occur. Having a comprehensive incident response plan in place can help mitigate the damage. This plan should outline how to respond to a data breach, including notifying affected individuals, working with cybersecurity professionals to contain the breach, and communicating with the public and regulatory bodies as necessary.
### **Secure Mobile Devices**
As mobile devices become common tools for accessing and storing sensitive information, securing these devices is crucial. Implementing mobile device management (MDM) solutions that can enforce security policies, remotely wipe data on lost or stolen devices, and monitor for suspicious activities can significantly reduce the risk of data leakage from mobile sources.
### **Use Secure File Sharing Practices**
Instead of using unsecured methods to share files, such as email attachments or unencrypted file transfer protocols, use secure file-sharing services that offer end-to-end encryption. This ensures that data remains protected during transmission and only intended recipients can access it.
By implementing these tips, organizations and individuals can significantly reduce the risk of data leakage. It is essential to stay vigilant and proactive in data security practices, as the threat landscape is constantly evolving. Regular reviews and updates to security protocols can help keep sensitive information safe from unauthorized access and prevent potential data breaches.
## **Secure Your Data & Prevent Data Leakage Efficiently!**
Data leakage is a serious issue that can lead to financial loss, damaged reputations, and legal troubles. However, by understanding how data leakage happens and implementing strong security measures, we can significantly reduce the risks. It is important for everyone to be proactive about security. Protecting our data not only helps prevent data leakage but also builds trust and ensures a safer digital environment for all.
If you have found this blog helpful, feel free to [subscribe to our blogs](/blog/) for valuable tutorials, guide. You can also join our [Facebook community](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# xCloud Deals: Get Next-Gen Managed Hosting For WordPress
> Grab the xCloud Deal and step into the future of managed hosting & server management for WordPress. Click, host and deploy your websites now!
## Free Unlimited Website Migration
## Black Friday Exclusive
## xCloud Lifetime
[Unlock The Deal](/deal/)
# Next-Gen Cloud Control Redefining Performance, Security & Stability
## xCloud offers a user-friendly control panel that simplifies the setup and management of WordPress websites across various cloud or VPS servers.
#### 130+
### Powerful Features
#### 240+
### 5 Star Ratings
#### 100k+
### Sites Deployed
## Our platform automates server setup, application installation, SSL, monitoring, resizing, and plugin updates, streamlining tasks for both beginners and experienced developers.
## With xCloud, users can easily create and manage multiple sites on a single server, equipped with tools to optimize performance and scale efficiently.
## Build and manage websites faster – xCloud makes hosting as simple as saying **“Hello World.”**
### Connect Your Server
Select the server providers & connect with xCloud effortlessly.
### Setup Your Server
Set up your connected server with just a few steps & manage easily.
### Deploy Your Sites
Deploy and Monitor Sites on your servers automatically.
## Choose the hosting option that fits your needs, bring your own provider, deploy websites with just a few clicks, and manage servers and sites effortlessly.
## Manage your preferred cloud provider within xCloud, whether it’s Vultr, GCP, DO, or any other, and build lightning-fast websites.
## Migrate an unlimited number of websites to xCloud Hosting at no cost with our full server migration feature. Use our free migration plugin to transfer sites from other hosting seamlessly.
## Set up your transactional emails easily. Enjoy 100 free emails per month with xCloud’s Email Delivery, or integrate your own provider like Mailgun, SendGrid, or Elastic Email.
## Manage DNS easily with xCloud: Integrate your Cloudflare account to manage DNS automatically.
## Easy Backup Management: Integrate any S3 compatible storage provider such as Cloudflare R2, AWS or DO Space to take site backups.
## Simplify Server & Website Management With Our Future Proof Hosting Control Panel
## Server Creation
- ### Deploy self-managed easily with a few clicks.
- ### Dedicated IP Included For Your Site
- ### Complete Root Access Authorization
## Server & Site Management
- ### Unlimited Database Storage Capacity
- ### Site Backup On Remote Storage
- ### Bulk WordPress plugin, theme and core updates.
## High Performance Hosting for WordPress, Laravel & PHP Applications
## Optimized Web Stacks
- ### High-Performance Nginx & OpenLiteSpeed Web Servers
- ### Run sites on MariaDB or MySQL, both pre-configured for optimal performance.
- ### Advanced Caching Layers with Page Caching, Edge Cahing, Redis Caching etc
## Staging & Migration
- ### Advanced Git repository cloning
- ### Clone the full server & sites
- ### Advanced demo site and staging environment setup.
- ### Free full server migration
## Updates Manager for Easy Sites Management
Easily update WordPress plugins, themes, & core files in bulk from a single dashboard, simplifying the process and boosting productivity.
## Monitor Site Performance with Page Speed
Track your site’s performance with Core Web Vitals and see scores for Performance, Accessibility, Best Practices, and SEO in one place.
## Free SSL Certificates
## Full Root Access
## Launch Your Favorite
Apps in One Click
Deploy popular applications with our high-performance, fully managed hosting or advanced control panel with a single click.
## Built-in Integrations to Maximize Performances
## Oops, You Have Missed The Deal!
Sign up to get notified before the next exclusive offer
## Lifetime Deal
## Pay 1–2 Years upfront and enjoy Lifetime Access to xCloud’s Control Panel.
[GRAB THE DEAL](https://xcloud.host/buy/BFCM2025-xcloudltd-5servers)
## 14-days money-back guarantee.
- 
### Unlimited site deployments
- 
### Access to Powerful features
## xCloud WHITE LABEL
## Free Reseller Panel Included with Your xCloud LTD Plans!
Kickstart your hosting business with your own server provider . Resell under
your brand with full client and billing support.
## What We Offer
## Billing and Support
- 
### Simple Billing: Integration with Stripe for Your Convenience
- 
### Live Chat Support: Crisp Integration for Real-Time Assistance
- 
### Full Server Migration Support: Get Help When You Need It
## team
## Team Harmony In Action
- 
### Versatile User Roles: Owner, Super User, Server Admin
- 
### Control Server & site Access for Teams
- 
### Enhanced Security: Activate 2FA Protection
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
**xCloud** isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. xCloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## FAQ’s
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What’s Included In the xCloud LTD Offer?
xCloud LTD offer will give you lifetime access to our cloud control panel. After grabbing this offer, you can integrate your own cloud provider like Vultr, Digital Ocean, AWS, Hetzner and more, enabling you to manage your server and your website with xCloud easily.
### Will I Be Charged For Future Features Added To The Product?
You will get access to all current and future features on the [roadmap](/roadmap/) within our cloud control panel. However, our hosting or any add-ons like email bundles or backup storage will not be included in the xCloud LTD offer.
### Can I Get A Refund?
Yes, we have a 14-day complete refund policy, no questions asked.
### How Do I Get Support?
Our dedicated support team is here to address any queries or concerns you may have, whether it’s technical assistance, account-related issues, or general inquiries. Get instant support from our live chat or submit a support ticket.
### Do You Have Hosting In xCloud?
Yes, we have hosting for WordPress, Laravel, PHP, Node.Js and more. But The Black Friday deal is only for our control panel, not the [managed hosting servers](/managed-hosting/).
### Can I Purchase This LTD Plan Multiple Times?
This Lifetime deal is stackable. You can buy as many times as you need.
### Is Split Payment Accepted?
Split payment is accepted for most plans. However, it is not available for the first three tier 5 Servers, 10 Servers and 15 Servers LTD plans. For the remaining three tiers 25 Servers, 50 Servers, 100 Servers LTD plans, you can claim the split payment option and complete your purchase in installments. To learn more about split payment, reach out to our support team.
### Is the Reseller Panel Included in the Lifetime Plans?
Yes. the [reseller panel](/reseller-hosting/) is included in all plans.
### What is the new White Label (Reseller Program) offer for LTD users?
We are offering LTD users complimentary access to our White Label plan. The plan you receive depends on your LTD tier (server capacity). The higher your LTD tier, the bigger the free WL plan you will receive! Your free WL plan is based on the number of servers included in your LTD license:
- LTD below 5 servers → 25 WL plan
- LTD below 15 servers → 60 WL plan
- LTD below 50 servers → 150 WL plan
- LTD below 250 servers → 400 WL plan
### I don’t have a server. How can I use the panel?
If you don’t already have a server, no worries — you can purchase our special discounted manged-server for LTD users, starting at just $4.50/mo only.
## Team Behind xCloud
## Go BIG and bring your own provider to xCloud to host and manage servers. Act now, this Black Friday exclusive deal is available for a limited time only.
---
# DeepSeek Harness vs OpenClaw vs Hermes Agent: Which Agent Harness Should You Run in 2026? - xCloud
> Compare DeepSeek Harness vs OpenClaw vs Hermes Agent to find the best open-source AI agent for coding, messaging, memory, and customization in 2026.
_Updated August 2026_
Three open-source AI agents now dominate the self-hosted conversation, and they arrived in three waves. OpenClaw built the category and, [**per explainx.ai’s growth tracking**](https://explainx.ai/blog/deepseek-harness-v0-1-plugin-first-agent-stack-august-2026), took 84 days to reach 200,000 GitHub stars. [**Hermes Agent**](https://xcloud.host/what-is-hermes-agent-features-and-use-cases/) from Nous Research crossed 90,000 stars within roughly six weeks of its February 2026 launch. Then [**DeepSeek Harness**](https://xcloud.host/what-is-deepseek-harness/) arrived on August 13, 2026 and passed 141,000 stars in four days, [**according to a direct GitHub API query**](https://pasqualepillitteri.it/en/news/11573/deepseek-harness-fastest-github-stars-record).
All three are MIT licensed. All three run on a $5 to $10 server. They are also built on three genuinely different philosophies, which means the right choice depends on what you want an agent to do, and picking on star count alone lands plenty of people on the wrong one. This guide compares all three on architecture, memory, model support, interfaces, ecosystem, maturity, and cost, then gives a decision framework by use case.
## Quick Summary / TL;DR
**Too long; didn’t read?** Here is the verdict table:
If you want…
Run this
Why
A messaging-first assistant across Telegram, Discord, Slack, WhatsApp
**OpenClaw**
The most mature multi-channel gateway in the category
An agent that learns and remembers across sessions
**Hermes Agent**
Three-layer persistent memory is its core design
A composable runtime you can reshape at every layer
**DeepSeek Harness**
Everything, including the loop, is a swappable plugin
A coding agent with full session replay and forking
**DeepSeek Harness**
Append-only session log supports resume, fork, replay
Maximum stability today
**OpenClaw** or **Hermes Agent**
Both are past the breaking-changes phase; dsh is a v0.1 preview
To run any of them without touching a server
[**xCloud managed hosting**](https://app.xcloud.host/deepseek-harness)
One platform runs all three as one-click managed deployments
**The short version of the difference:** OpenClaw is a finished product for talking to an agent everywhere you already chat. Hermes Agent is a finished product for an agent that gets smarter the longer it runs. DeepSeek Harness is a chassis for building the agent you actually want. Products get you running faster; the chassis goes further.
**The hosting answer is simpler than the agent answer:** all three need the same thing, an always-on server with SSL, supervision, and backups, and [**xCloud**](https://xcloud.host/deepseek-harness/) is the one platform that runs all three as managed one-click deployments at $9.99/month each.
## Why These Three, and How We Compared Them
This comparison covers the three agents with the largest active communities in the self-hosted category as of August 2026. Each was evaluated on seven criteria: architecture and extensibility, memory and session model, model support, interfaces, ecosystem depth, maturity and stability, and total running cost. Technical claims come from each project’s official documentation and repository: the [**DeepSeek Harness repository**](https://github.com/deepseek-ai/deepseek-harness), the [**Hermes Agent documentation**](https://hermes-agent.nousresearch.com/docs/), and OpenClaw’s official docs, supplemented by third-party analyses cited inline. Resource figures come from the same operator field reports used in the [**DeepSeek Harness hosting guide**](https://xcloud.host/best-deepseek-harness-hosting-providers/).
Transparency note: xCloud operates managed hosting for all three agents, which is exactly why the hosting recommendation does not depend on which agent wins your comparison.
## Master Comparison Table: DeepSeek Harness vs OpenClaw vs Hermes Agent
**DeepSeek Harness (dsh)**
**OpenClaw**
**Hermes Agent**
**Built by**
DeepSeek AI
Open-source community
Nous Research
**Released**
August 13, 2026
2025
February 2026
**License**
MIT (full repo)
MIT
MIT
**Runtime**
Node.js (TypeScript)
Node.js
Python
**Core idea**
Everything is a plugin (Cordis kernel)
Agent in every chat app
Agent that learns and remembers
**Architecture**
Plugin kernel; model, tools, loop, UI all swappable
Monolithic product + config
Single process + portable skills
**Memory model**
Append-only session log: resume, fork, replay
Session history per channel
Three layers: MEMORY.md + SQLite (FTS5) + skills
**Model support**
DeepSeek, Anthropic, OpenAI, Bedrock, Vertex, Azure, any OpenAI-compatible
Multiple providers
Multiple providers incl. Nous Portal, OpenRouter
**Primary interface**
Local Web UI (127.0.0.1:3080), CLI, Python SDK
~15+ messaging channels
Messaging gateway (~16 channels) + CLI
**Runtime modes**
Standard, Code (PTC), Minimal, Creator
One product mode
Standard + browser automation (Camofox, v0.7+)
**Ecosystem**
1,200+ `dsh-plugin` repos in 48 hours
Largest installed base, mature plugins
Growing skill-sharing community
**Maturity**
Developer preview (0.1.0-rc.5), breaking changes promised
Stable
Stable
**Min RAM (API models)**
1–2 GB
2 GB, scales with channels
1 GB CLI; 4 GB with browser
**Managed hosting**
[xCloud](https://xcloud.host/deepseek-harness/)
[xCloud](https://xcloud.host/openclaw-hosting/)
[xCloud](https://xcloud.host/hermes-agent-hosting/)
That table answers “what is the difference.” The rest of this guide answers the harder question: which difference matters for you.
## DeepSeek Harness: The Composable Runtime
[**DeepSeek Harness**](https://xcloud.host/what-is-deepseek-harness/) (command name `dsh`) is the newest of the three and the most architecturally ambitious. It runs on the Cordis plugin kernel, and [**as AgentsPulse’s architecture review**](https://agentspulse.github.io/tutorials/deepseek-harness-and-cordis-why-everything-is-a-plugin/) puts it, models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and the UI all load as replaceable plugins with no privileged core to work around. Want a different sandbox, storage backend, or agent loop? Mount a plugin instead of forking the runtime.
Two features stand apart in this comparison. First, the append-only session log: every run is recorded as an event stream that resume, fork, search, and replay operate on, so a run that went wrong at step 40 can be forked at step 39 and retried, with full visibility into what the model saw. Neither OpenClaw nor Hermes Agent offers replay and forking at this depth. Second, the four runtime modes (Standard, Code with Programmatic Tool Calling, Minimal for benchmarking, Creator for plugin authors) make it the only entry that doubles as an evaluation harness; DeepSeek benchmarks its own V4 models with the Minimal mode.
### Strengths and Weaknesses
Strengths
Weaknesses
✅ Deepest extensibility of the three; the loop itself is swappable
❌ Developer preview: the README promises breaking changes
✅ Session replay and forking are unmatched for debugging
❌ No built-in messaging gateway; chat-app integration is a plugin job
✅ Widest first-party model support, including Bedrock, Vertex, Azure
❌ Web UI is localhost-only; secure exposure is your job when self-hosting
✅ Fastest-growing plugin ecosystem: 1,200+ tagged repos in 48 hours
❌ Youngest community; fewer answered questions when you get stuck
**Best for:** Developers and teams who treat the agent runtime as infrastructure they will shape, coding-agent workflows that benefit from replay, and anyone building plugins for an ecosystem still handing out land.
## OpenClaw: The Messaging-First Workhorse
OpenClaw is the incumbent, and its advantage is exactly what incumbency buys: the most mature multi-channel messaging gateway in the category, the largest installed base, and the deepest pool of solved problems. Connect it to Telegram, Discord, Slack, WhatsApp, and a dozen other channels, and the agent lives where you already talk. Its resource use scales with the number of channels enabled, and the configuration surface, while wide, is documented by years of community use.
What OpenClaw does not try to be is a framework. The loop, tools, and UI ship as one opinionated product. When your needs match its opinions, that is a feature: setup is fast and the failure modes are known. When they do not, you are patching someone else’s architecture, which is precisely the pain [**DeepSeek Harness was designed to remove**](https://www.digitalapplied.com/blog/deepseek-harness-open-source-agent-framework-2026).
### Strengths and Weaknesses
Strengths
Weaknesses
✅ The most mature messaging integration story of the three
❌ Monolithic: deep customization means forking
✅ Stable, documented, large community
❌ Resource use grows with every channel enabled
✅ Known failure modes and years of answered questions
❌ No session forking or replay comparable to dsh
✅ Fastest path to an agent in your team’s chat apps
❌ The category’s newer ideas (plugin kernels, layered memory) arrived elsewhere first
**Best for:** Teams and individuals who want a reliable assistant in their existing chat channels today, with minimum surprise and maximum community support.
## Hermes Agent: The One That Remembers
[**Hermes Agent**](https://xcloud.host/what-is-hermes-agent-features-and-use-cases/) from Nous Research is built around one bet: an agent is only as useful as what it retains. Its three-layer memory architecture, [**documented by Nous Research**](https://hermes-agent.nousresearch.com/docs/), keeps active memory in MEMORY.md, session history in SQLite with FTS5 full-text search, and procedural memory as portable skills that survive updates and migrate between servers. Run it continuously against real workflows and the skill library compounds; close the laptop and the compounding stops, which is why Hermes operators moved to always-on hosting faster than any other agent community.
Hermes also has a strong messaging story (roughly 16 channels through one gateway) and, since v0.7, browser automation through the Camofox anti-detection browser, which adds about 2 GB to its RAM needs. It runs on Python rather than Node.js, the only one of the three to do so, which matters if your team’s tooling and deployment muscle memory lean one way or the other.
### Strengths and Weaknesses
Strengths
Weaknesses
✅ The best persistent-memory design in the category
❌ Memory only compounds with 24/7 uptime; laptop use wastes the core feature
✅ Portable skills migrate between servers in minutes
❌ Browser automation pushes RAM needs to 4 GB
✅ Strong messaging gateway plus CLI
❌ Python stack, if your ops standardize on Node.js
✅ Stable and past its breaking-changes phase
❌ Less architectural flexibility than a plugin kernel
**Best for:** Operators who want a long-running personal or team agent whose value grows with time: research assistants, monitoring agents, and workflow automation that benefits from accumulated context.
## Head-to-Head: The Five Decisions That Actually Separate Them
### 1\. Architecture: Product vs Product vs Chassis
OpenClaw and Hermes Agent are finished products with opinions. DeepSeek Harness is a chassis. [**Floatboat’s Cordis analysis**](https://floatboat.ai/blog/cordis-plugin-framework) frames the difference well: an open license makes code inspectable, but a plugin kernel makes it transformable. If you have ever forked an agent to change one component, the chassis is what you wanted. If you never will, the products get you running faster.
### 2\. Memory: Replay vs History vs Learning
Three different answers to “what does the agent keep.” dsh keeps a forensic record (every event, replayable and forkable). OpenClaw keeps conversational history per channel. Hermes keeps learned capability (skills and searchable memory that change future behavior). Debugging-heavy coding work favors dsh. Everyday assistant work favors OpenClaw’s simplicity. Anything where week 10 should be smarter than week 1 favors Hermes.
### 3\. Interfaces: Where Do You Meet the Agent?
OpenClaw and Hermes meet you in chat apps. dsh meets you in a Web UI, a CLI, and a Python SDK, with chat-app integration left to its plugin ecosystem. As of August 2026 that ecosystem is 1,200+ repositories and four days old, [**per BibiGPT’s count**](https://bibigpt.co/en/blog/posts/deepseek-harness-skill-ai-video-summary), so messaging-first users should either wait for the gateway plugins to mature or pick OpenClaw and Hermes today.
### 4\. Maturity: Stability vs Momentum
The repository’s own version string is 0.1.0-rc.5, and DeepSeek’s README warns in capital letters about compatibility-breaking changes. OpenClaw and Hermes are both past that phase. The honest framing: dsh has the most momentum and the least stability; production dependencies belong on the other two for now, while evaluation and plugin development belong on dsh precisely because the ecosystem’s defaults are being decided this quarter.
### 5\. Cost: Nearly a Tie, With One Asterisk
All three run on the same class of server, and hosting is a wash. The asterisk is tokens: [**VentureBeat reports**](https://venturebeat.com/technology/deepseek-harness-launches-as-open-source-rival-to-claude-code-alongside-v4-pro-on-api-with-higher-prices) DeepSeek’s API moved to peak and off-peak pricing on August 16, 2026, so dsh loops scheduled into off-peak windows now cost measurably less on DeepSeek models. All three agents are model-agnostic enough that token strategy, not agent choice, drives the bill.
Monthly cost
dsh
OpenClaw
Hermes Agent
Managed hosting ([xCloud](https://app.xcloud.host/deepseek-harness))
$9.99
$9.99
$9.99
Typical tokens (moderate use)
$5–20
$5–25
$5–20
RAM you should budget
2–4 GB
2–4 GB
2–4 GB
Your ops time on managed
~0 hrs
~0 hrs
~0 hrs
## The Decision Framework: Match the Agent to the Job
Your situation
Run this
Second choice
“I want an assistant in Slack/Telegram/WhatsApp this week”
**OpenClaw**
Hermes Agent
“I want an agent that knows my projects better every month”
**Hermes Agent**
dsh + memory plugins
“I’m building agent products or internal tooling”
**DeepSeek Harness**
OpenClaw
“I need a coding agent I can debug properly”
**DeepSeek Harness**
OpenClaw
“I run agents for clients and need boring reliability”
**OpenClaw**
Hermes Agent
“I want to write plugins people will actually use”
**DeepSeek Harness**
Hermes skills
“I genuinely can’t decide”
**Run two side by side**
See below
That last row is not a dodge. All three coexist on one 4 GB server (they are separate processes with separate ports and data directories), and the community has already built bridges between them, including the HermesClaw bridge connecting Hermes and OpenClaw. The two-week bake-off, one real workflow on each candidate, settles the question faster than any comparison article, this one included.
## Whichever You Pick, the Hosting Answer Is the Same
Here is the part most three-way comparisons miss: the three agents disagree on architecture and agree completely on infrastructure. Every one of them needs 24/7 uptime, persistent disk for its memory or session data, SSL, a process supervisor, backups, and a secured public endpoint. Every one of them is a demo on a laptop and a tool on a server.
[**xCloud**](https://xcloud.host/deepseek-harness/) is the one platform in this comparison that runs all three as one-click managed deployments: [**OpenClaw hosting**](https://xcloud.host/openclaw-hosting/), [**Hermes Agent hosting**](https://xcloud.host/hermes-agent-hosting/) (as of April 2026, the only fully managed Hermes service on the market), and now [**managed DeepSeek Harness hosting**](https://app.xcloud.host/deepseek-harness), one of the first anywhere, each at $9.99/month with SSL, authentication, supervision, daily backups, and updates handled.
That has a practical consequence for the bake-off strategy: you can deploy two or all three candidates in the same panel in under fifteen minutes total, run your real workflow against each for two weeks, keep the winner, and delete the rest, all inside the 14-day money-back window. The platform’s track record running OpenClaw and Hermes fleets through 2026 is also the answer to the fair question “will they know what to do when my agent breaks”: their support has been debugging exactly these three stacks all year.
**Deploy any of the three in about five minutes:** [**start at app.xcloud.host/deepseek-harness**](https://app.xcloud.host/deepseek-harness)**.**
## Common Mistakes When Choosing Between These Three
- **Choosing on star velocity.** dsh’s four-day curve is remarkable and says nothing about whether you need a plugin kernel. Stars measure attention, not fit.
- **Putting a v0.1 release candidate under production load.** dsh’s README promises breaking changes. Evaluate it now; depend on it later.
- **Running Hermes without persistent uptime.** Its learning loop is the product. Part-time Hermes is a worse OpenClaw.
- **Expecting dsh to be a chat-app agent out of the box.** The gateway plugins are coming from the ecosystem; today that story belongs to OpenClaw and Hermes.
- **Rebuilding Docker containers without mounted volumes.** All three keep their value on disk (session logs, SQLite memory, skills). No volume, no memory, on any of them.
## Frequently Asked Questions
### What is the main difference between DeepSeek Harness, OpenClaw, and Hermes Agent?
Architecture and purpose. DeepSeek Harness is a composable runtime where every component, including the agent loop, is a swappable plugin. OpenClaw is a finished messaging-first agent that lives in your chat apps. Hermes Agent is a finished agent built around persistent, compounding memory. All three are MIT licensed and run on similar servers.
### Which agent is best for beginners in 2026?
OpenClaw or Hermes Agent, deployed on managed hosting. Both are stable products with communities that have already answered the beginner questions. DeepSeek Harness rewards users who want to configure and extend; it is a better second agent than first agent, unless you start with a [**managed deployment**](https://app.xcloud.host/deepseek-harness) that removes the infrastructure half of the learning curve.
### Is DeepSeek Harness a replacement for OpenClaw?
Not today. They overlap less than the launch commentary suggests: OpenClaw’s core strength is the multi-channel messaging gateway, which dsh does not ship first-party. dsh’s core strengths, the plugin kernel and session replay, have no OpenClaw equivalent. Over time the dsh plugin ecosystem may close the gateway gap; the projects can also coexist on one server.
### Can Hermes Agent’s memory be replicated in DeepSeek Harness?
Partially, through storage and skill plugins, and the ecosystem is moving fast. But Hermes ships the three-layer design (MEMORY.md, SQLite with FTS5 search, portable skills) as a tested, integrated whole today. If compounding memory is your primary requirement, Hermes is the proven path in 2026.
### Which of the three is the cheapest to run?
Hosting costs are effectively identical: each runs comfortably on a 2 to 4 GB server, and managed hosting for any of them is $9.99/month on xCloud. Token spend dominates the real bill, and since DeepSeek’s move to peak/off-peak API pricing on August 16, 2026, scheduling dsh loops off-peak on DeepSeek models is the single biggest cost lever among the three.
### Do all three need a GPU?
No. All three call hosted LLM APIs by default, so the server runs agent logic only, which is CPU-light. A GPU enters the picture only if you co-host a local model with Ollama or vLLM, and that decision is independent of which agent you choose.
### Can I run all three on the same server?
Yes. They are separate processes (two Node.js, one Python) with separate ports and data directories. Budget 4 GB RAM or more for two agents with active tool use, supervise each with its own systemd unit or Docker restart policy, and back up each data directory separately. Managed deployments sidestep the juggling by giving each agent its own instance.
### Which one gets the most out of DeepSeek’s V4 models?
DeepSeek Harness, by design: it is the runtime DeepSeek uses to benchmark V4, and V4-Pro shipped the same day. That said, all three are model-agnostic, and V4’s open weights and API work in any of them.
### How hard is it to switch agents later?
Easy, and this should lower the stakes of your choice. Each keeps its state in a data directory you can archive and restore in minutes. The two-week bake-off beats months of deliberation: deploy candidates, run one real workflow on each, keep the winner.
### Where should I host whichever one I pick?
The requirements are identical across all three: always-on server, persistent disk, SSL, authentication, supervision, backups. [**xCloud**](https://xcloud.host/deepseek-harness/) runs managed one-click deployments of all three at $9.99/month each with a 14-day money-back guarantee, which makes it the one hosting decision that does not depend on the agent decision. Self-hosting on a VPS works too; the full provider comparison is in the [**DeepSeek Harness hosting guide**](https://xcloud.host/best-deepseek-harness-hosting-providers/).
## Conclusion: The 2026 Verdict
The three-way race has a clean shape in 2026. OpenClaw is the reliable incumbent and the fastest path to an agent in your chat apps. Hermes Agent is the specialist, unmatched when an agent should be smarter in month three than in week one. DeepSeek Harness is the platform bet, the least stable and the most consequential, because a runtime where everything is a plugin tends to absorb the best ideas of everything around it.
### Expert Picks by Goal
Your goal
Best choice
Why
Agent in your chat apps this week
**OpenClaw**
Most mature messaging gateway
Agent that compounds knowledge
**Hermes Agent**
Three-layer persistent memory
Agent runtime you can reshape
**DeepSeek Harness**
Plugin kernel, session replay
Coding agent with real debugging
**DeepSeek Harness**
Fork and replay any session
Client work needing boring reliability
**OpenClaw**
Stable, known failure modes
Undecided
**Two-week bake-off**
Deploy 2–3 side by side, keep the winner
**What to do this week:** Stop deliberating and run the test. Pick your top two from the table, deploy both as [**managed instances on xCloud**](https://app.xcloud.host/deepseek-harness) in about ten minutes combined, and point one real workflow at each for two weeks. The 14-day money-back guarantee means the losing candidate costs you nothing, and the winning one is already deployed, secured, and backed up the moment you decide. Whichever agent wins, that is the setup that gets you an answer by the end of the month instead of another comparison tab.
For more deep-dive comparisons on hosting AI agents and the open-source stack behind them, [**subscribe to the xCloud blog**](https://xcloud.host/blog/) or join the [**xCloud Facebook community**](https://www.facebook.com/groups/xcloud.community).
---
# DeepSeek Harness vs OpenCode: Which Coding Agent Should You Run in 2026? - xCloud
> Discover DeepSeek Harness vs OpenCode, comparing their features, architecture, coding workflows, model support, and which is better for developers in 2026.
_Updated August 2026_
Two open-source coding agents, two completely different bets. [**OpenCode**](https://opencode.ai/) crossed 160,000 GitHub stars and roughly 7.5 million monthly developers by mid-2026, [**per Developers Digest’s guide**](https://www.developersdigest.tech/blog/opencode-developer-guide-2026), making it the most-used open-source coding agent in the world. [**DeepSeek Harness**](https://xcloud.host/what-is-deepseek-harness-features-architecture-use-cases/) shipped on August 13, 2026 and passed 141,000 stars in four days, [**according to a direct GitHub API query**](https://pasqualepillitteri.it/en/news/11573/deepseek-harness-fastest-github-stars-record).
Both are MIT licensed. Both are model-agnostic. Both will happily run DeepSeek V4, Claude, or GPT. And they solve the same problem from opposite ends: OpenCode perfected the terminal workflow developers already live in, while DeepSeek Harness rebuilt the runtime so every part of it can be replaced. This guide compares them on architecture, interfaces, model support, extensibility, maturity, cost, and what it takes to run either one on a server rather than a laptop.
## Quick Summary / TL;DR
**Too long; didn’t read?**
If you want…
Run this
Why
A dependable daily coding agent in your terminal
**OpenCode**
Mature TUI, IDE and desktop surfaces, 75+ providers
To reshape the agent runtime itself
**DeepSeek Harness**
Models, tools, loops, sandbox, and UI are all plugins
Widest model and provider choice
**OpenCode**
75+ providers plus local models via Ollama
Full session replay, forking, and audit trail
**DeepSeek Harness**
Append-only session event log
Stability today
**OpenCode**
dsh is a v0.1 developer preview with breaking changes promised
A browser UI instead of a terminal
**DeepSeek Harness**
Web UI is the default interface
Either one running 24/7 on a server
[**xCloud**](https://xcloud.host/deepseek-harness/)
One-click managed dsh, or Node.js hosting for headless OpenCode
**The one-line verdict:** OpenCode is the safer daily driver in 2026; DeepSeek Harness is the more consequential architecture. If you write code every day and want it to work, start with OpenCode. If you are building agent infrastructure other people will run, dsh is where the interesting problems are.
**Important caveat up front:** nobody has credible head-to-head coding benchmarks for these two yet. dsh is days old, and much of the early “DeepSeek harness” benchmarking online actually tested unrelated community wrappers with similar names. A controlled trial protocol is included below so you can measure your own workload instead of trusting a leaderboard that does not exist.
## Why These Two Get Compared
They land in the same search results because both answer “open-source alternative to Claude Code,” and both point at DeepSeek’s V4 models. But their design centers sit far apart.
OpenCode is a coding _product_: a terminal-native agent with Plan and Build modes, Language Server Protocol integration, subagents, and an IDE extension, built by the team behind SST. DeepSeek Harness is a coding _runtime_: a plugin kernel where the model adapter, tool pipeline, session store, sandbox, approval policy, and UI are all replaceable components.
One fact that trips up newcomers: OpenCode has a fork history. The original repository was maintained by Charm; after a dispute over direction the project split, with the SST/Anomaly version rewritten in TypeScript on Bun becoming the one most developers mean today, while Charm’s continuation lives on as Crush. When you read older OpenCode tutorials referencing a Go codebase and a Bubble Tea TUI, you are reading about the earlier lineage.
## Master Comparison Table: DeepSeek Harness vs OpenCode
**DeepSeek Harness (dsh)**
**OpenCode**
**Built by**
DeepSeek AI
SST / Anomaly
**Released**
August 13, 2026
2025, active fork rewritten 2026
**License**
MIT
MIT
**Runtime**
Node.js / TypeScript (pnpm)
TypeScript on Bun
**Core idea**
Everything is a plugin (Cordis kernel)
Terminal-first coding agent, bring your own model
**Primary interface**
Web UI at 127.0.0.1:3080
Terminal UI, plus desktop app and IDE extension
**Headless mode**
Headless profile and Python SDK
`opencode serve` with OpenAPI spec and JS/TS SDK
**Model providers**
DeepSeek, Anthropic, OpenAI, Bedrock, Vertex, Azure, any OpenAI-compatible
75+ providers including local models via Ollama
**Agent modes**
Standard, Code (PTC), Minimal, Creator
Plan and Build, plus General, Explore, Scout subagents
**Extensibility**
Plugin kernel: replace any core component
Plugins, hooks, custom tools, commands, MCP servers
**Code intelligence**
Tool-driven file and shell access
LSP diagnostics across most languages
**Session model**
Append-only event log: resume, fork, replay
Persistent local sessions, share links, undo and redo
**Project memory**
Skills and config plugins
`AGENTS.md` generated by `/init`
**Sub-agent delegation**
Can delegate to Claude Code and Codex binaries
General, Explore, and Scout subagents
**Maturity**
Developer preview, 0.1.0-rc.5
Established, production-used
**GitHub stars**
141,000+ in four days
160,000+
**Managed hosting**
[xCloud one-click](https://app.xcloud.host/deepseek-harness)
Self-host headless on [xCloud Node.js](https://xcloud.host/node-js-hosting/)
## DeepSeek Harness: The Runtime You Can Rebuild
[**DeepSeek Harness**](https://github.com/deepseek-ai/deepseek-harness) (command `dsh`) is built on the Cordis plugin kernel, and its README opens with the thesis: everything is a plugin. Models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and the UI all mount through the same kernel, so there is no privileged core to work around.
Two capabilities matter most for coding work. The **append-only session log** records every event, so a run that derailed at step 40 can be forked at step 39 and retried with full visibility into what the model saw. And **Code mode (PTC, Programmatic Tool Calling)** lets the model write TypeScript to express control flow instead of issuing tools one call at a time, which suits multi-step refactors with branching logic.
[**The New Stack’s coverage**](https://thenewstack.io/deepseek-harness-open-source-plugins/) surfaced a detail worth knowing: the harness ships subagent providers that delegate work directly to Anthropic’s Claude Code and OpenAI’s Codex by resolving their binaries from your PATH, both disabled by default, plus bridges that run your existing `hooks.json` from either product. That makes dsh less a rival to those tools than a layer that can sit above them.
### Strengths and Weaknesses
Strengths
Weaknesses
✅ Any component is replaceable without forking the source
❌ Developer preview: the README promises breaking changes
✅ Session replay and forking give real debugging visibility
❌ Terminal workflow is less refined than OpenCode’s TUI
✅ Can orchestrate Claude Code and Codex as subagents
❌ No LSP integration; code intelligence comes from tools
✅ Browser UI suits people who dislike terminal-only tools
❌ Web UI binds to localhost, so remote use needs proxy, SSL, and auth
✅ Plugin ecosystem growing faster than anything in the category
❌ Configuration complexity is higher by design
**Best for:** Platform teams, plugin authors, and developers who want to shape the runtime, prefer a browser interface, or need forensic replay of agent runs.
## OpenCode: The Daily Driver
OpenCode is what most developers should reach for first, because it is optimized for the loop you actually repeat: open a repo, describe a change, review, ship. Its **Plan and Build modes** are the standout design decision. Plan mode drafts what the agent intends to do before touching any files; you review, give feedback, and only then switch to Build to execute, which prevents the class of failure where an agent rewrites six files you did not want touched.
Its practical advantages stack up in ways that show years of iteration. LSP integration means the agent sees type information, function signatures, import paths, and diagnostics rather than raw text, across TypeScript, Python, Go, Rust, Java, and most languages with a language server. Multiple concurrent sessions each carry their own context window, history, and model configuration, so a research session stays separate from an implementation session. `/init` generates an `AGENTS.md` you commit to Git so the agent understands your project conventions. And `opencode serve` runs it as a headless HTTP server with an OpenAPI spec at /doc and an official `@opencode-ai/sdk` package, which is the feature most people miss and the one that makes OpenCode automatable.
The provider catalog is the other advantage: 75+ providers including Claude, GPT, Gemini, Groq, Bedrock, Azure, OpenRouter, and local models through Ollama, with an optional OpenCode Zen tier that routes tasks to benchmarked models automatically.
### Strengths and Weaknesses
Strengths
Weaknesses
✅ Plan mode prevents unwanted edits before they happen
❌ You extend around the core; you cannot replace it
✅ LSP gives the agent real code intelligence
❌ Terminal-first, which not everyone wants
✅ 75+ providers plus free local models via Ollama
❌ Desktop app is still beta
✅ Headless server mode plus official SDK for automation
❌ No session forking or replay comparable to dsh
✅ Largest user base in the category, so answers exist
❌ Fork history makes older tutorials misleading
**Best for:** Working developers who want an agent in their existing terminal and IDE today, teams standardizing on one tool, and anyone routing tasks across many model providers.
## The Four Differences That Actually Decide It
### 1\. Plugins as Convenience vs Plugins as Product Structure
OpenCode plugins are JavaScript or TypeScript modules that react to events, add tools, protect files, and adjust behavior around tool execution. They extend a fixed core. In DeepSeek Harness, plugins _are_ the core: profiles stack bundles, patches replace components, and event seams intercept requests, tools, sessions, or turns. Replacing the session store or the sandbox is a supported operation in dsh and a fork in OpenCode.
If your extension needs are hooks and custom commands, OpenCode is more direct. If you need to swap the sandbox for one inside your own network, dsh is the only one of the two that treats that as configuration.
### 2\. Where the Agent Meets You
OpenCode meets you in the terminal, the IDE, and a beta desktop app. dsh meets you in a browser UI at `127.0.0.1:3080`, with headless and SDK options behind it. This is a genuine preference split rather than a quality gap: terminal-native developers find a web UI a context switch, while people who dislike TUIs find it an unlock.
### 3\. Code Intelligence
OpenCode’s LSP integration is a real advantage for large codebases. The agent reading type information and diagnostics beats an agent reading text. dsh compensates with tool access and PTC control flow, but LSP-grade awareness is not part of the box today. Expect the plugin ecosystem to attack this gap; it has not closed yet.
### 4\. Stability vs Momentum
`0.1.0-rc.5`, and the README warns in capital letters about compatibility-breaking changes. OpenCode is production-used by millions of developers monthly. That asymmetry should decide it for anyone with deadlines. It should not decide it for anyone building the next layer of agent infrastructure, where being early is the entire point.
## Nobody Has Benchmarked These Two Yet: Run Your Own Trial
Two harnesses running the identical model can make different tool calls, resend different context, compact history at different points, and recover from errors differently, so time, token spend, and final diff quality all diverge. That means harness benchmarks published within days of a launch are close to meaningless, and much of the early “DeepSeek harness” testing circulating online measured unrelated community wrappers.
Run this instead. It takes an afternoon and answers the question for your codebase:
1. **Fix the variable.** Select the same model and inference provider in both tools, for example DeepSeek V4 Flash through the same endpoint.
2. **Clean slate each run.** Start from identical fresh clones of the same repository and grant equivalent permissions.
3. **Same scoped task, same tests.** Give both an identical, well-defined task with defined acceptance tests.
4. **Repeat three times minimum.** Single runs measure luck.
5. **Score seven things:** correctness, diff quality, tests passed, wall-clock time, tokens consumed, retries, and human cleanup required.
The last column usually decides it, and it is the one no leaderboard measures.
## Cost Breakdown: What Each Actually Costs to Run
Both tools are free. Your bill is tokens plus, if you run either beyond your laptop, hosting.
Setup
Software
Tokens/month
Hosting
Total/month
OpenCode local, DeepSeek V4 Flash
$0
$5–20
$0
**$5–20**
OpenCode local, Claude models
$0
$20–60
$0
**$20–60**
OpenCode local, Ollama local model
$0
$0
$0
**$0**
dsh local, DeepSeek V4
$0
$5–20
$0
**$5–20**
dsh always-on, managed
$0
$5–20
$9.99
**$15–30**
OpenCode headless on a server
$0
$5–25
$9.99+
**$15–35**
Either, self-hosted VPS
$0
$5–25
$5 + 1–3 hrs setup
**$40–175**
One timing detail that affects dsh specifically: [**VentureBeat reports**](https://venturebeat.com/technology/deepseek-harness-launches-as-open-source-rival-to-claude-code-alongside-v4-pro-on-api-with-higher-prices) DeepSeek moved to peak and off-peak API pricing on August 16, 2026, so scheduled or batch runs against DeepSeek models cost measurably less in off-peak windows. Interactive coding in your working hours pays the peak rate in either tool.
## Installing Both: Side by Side
**DeepSeek Harness**
1. Install Node.js 20 or newer
2. Run `npx @deepseek-ai/dsh web`
3. Open `http://127.0.0.1:3080`
4. Add your model provider API key
5. Start a session in Standard mode, or Code mode for PTC control flow
From source for plugin work: `git clone`, `pnpm install`, `pnpm run build`, `pnpm dsh web`.
**OpenCode**
1. Install via the official install script (WSL recommended on Windows)
2. Run `opencode auth login` to connect a provider
3. Navigate to your project and run `opencode`
4. Run `/init` to generate `AGENTS.md`, then commit it
5. Work in Plan mode first, switch to Build to execute
For automation, `opencode run "…"` executes non-interactively and `opencode serve` starts the HTTP server.
## Resource Requirements
Workload
vCPU
RAM
Notes
OpenCode local, API models
1
1 GB
Runs alongside your editor
dsh local, API models
1
1–2 GB
Node process plus Web UI
dsh always-on server
1–2
2 GB
Session logs on persistent disk
Either with heavy sandboxed tool use
2
4 GB
Code execution needs headroom
Either with a local model via Ollama
4+
16 GB+
The model sets the floor, not the agent
Neither tool needs a GPU unless you host the model yourself.
## Running Either One Beyond Your Laptop
Most comparisons stop at “which do I install.” The more useful question for teams is what happens when the work should continue after you close the lid: scheduled repo checks, CI-triggered reviews, long-running refactors, or an agent a teammate can reach.
Both tools support this, differently. **DeepSeek Harness** has a headless profile and a Web UI built to be a persistent workspace, though the UI binds to localhost, so remote access requires a reverse proxy, SSL, and an authentication layer. **OpenCode** exposes `opencode serve` as an HTTP server with an OpenAPI spec and an official SDK, which is exactly what you point CI at, and it needs the same protective layers in front of it.
That wiring is the actual work, and it is identical for both: a Linux box, Node or Bun, a process supervisor so the agent survives crashes, Caddy or nginx terminating SSL, authentication in front of the endpoint, a firewall, and backups of the session or workspace directory.
[**xCloud**](https://xcloud.host/deepseek-harness/) removes that step for both paths. [**Managed DeepSeek Harness hosting**](https://app.xcloud.host/deepseek-harness) deploys dsh with the proxy, SSL, authentication, supervision, and daily backups already wired, at $9.99/month, one of the first managed dsh services anywhere. For headless OpenCode, [**xCloud’s Node.js hosting**](https://xcloud.host/node-js-hosting/) gives you the same managed foundation to run `opencode serve` behind SSL. It is the same one-click playbook the platform proved with [**OpenClaw hosting**](https://xcloud.host/openclaw-hosting/) and [**Hermes Agent hosting**](https://xcloud.host/hermes-agent-hosting/), which as of April 2026 was the only fully managed Hermes service on the market.
Worth being straight about: if you only use a coding agent interactively on your own machine, you do not need hosting at all, and neither tool is worse for running locally. Hosting earns its keep the moment the agent needs to be reachable, scheduled, or shared.
**Deploy DeepSeek Harness in about five minutes:** [**start at app.xcloud.host/deepseek-harness**](https://app.xcloud.host/deepseek-harness)**.**
## Video: The Architecture Behind DeepSeek Harness
For a visual walkthrough of the plugin model that separates dsh from every other coding agent, DevsKingdom’s breakdown is the clearest primer available: [**Deepseek Harness: Everything is a Plugin (YouTube)**](https://www.youtube.com/watch?v=xe-aHJLC5UU).
## Common Mistakes When Choosing Between Them
- **Trusting early benchmarks.** Much of the “DeepSeek harness” performance testing online tested unrelated wrappers, not the official DeepSeek AI project.
- **Replacing a working setup on launch week.** If OpenCode already ships your code, run dsh beside it on a non-critical repo instead of switching.
- **Reading old OpenCode tutorials.** Guides describing a Go codebase predate the TypeScript rewrite; check what lineage a tutorial covers before following it.
- **Exposing either agent without auth.** Both can run shell commands. A publicly reachable endpoint without authentication hands a shell to the internet.
- **Comparing model quality instead of harness quality.** Same model, different harness, different result. Hold the model fixed or you are measuring the wrong thing.
## Frequently Asked Questions
### What is the difference between DeepSeek Harness and OpenCode?
OpenCode is a mature terminal-first coding agent with Plan and Build modes, LSP code intelligence, and 75+ model providers. DeepSeek Harness is a plugin-based agent runtime where the model, tools, session store, sandbox, loop, and UI are all replaceable components, accessed through a browser UI. OpenCode optimizes the daily coding workflow; dsh optimizes how much of the runtime you can rebuild.
### Which is better for daily coding work in 2026?
OpenCode, for most developers. It is production-used by millions monthly, has LSP integration and IDE surfaces, and is past the breaking-changes phase. DeepSeek Harness is a v0.1 developer preview, which makes it a strong second agent for experimentation rather than the tool you depend on for shipping deadlines.
### Can both run DeepSeek V4 models?
Yes. OpenCode includes DeepSeek in its 75+ provider catalog, and DeepSeek Harness supports DeepSeek alongside Anthropic, OpenAI, Bedrock, Vertex, Azure, and any OpenAI-compatible endpoint. Neither locks you to one vendor, so model choice should not decide your harness choice.
### Is DeepSeek Harness faster or better at coding than OpenCode?
There is no trustworthy head-to-head evidence yet, and any published this soon after launch deserves skepticism. Two harnesses using the same model differ in tool calls, context handling, and error recovery, so run the controlled trial described above on your own repository rather than trusting a leaderboard.
### Which one has better model support?
OpenCode, on breadth: 75+ documented providers plus local models through Ollama, and an optional Zen tier that routes by benchmarked performance. DeepSeek Harness covers the major clouds (Bedrock, Vertex, Azure) plus custom OpenAI-compatible endpoints, which is enough for most teams but a shorter list.
### Can I use both together?
Yes, and it is a reasonable setup. Keep OpenCode as the daily driver in your terminal and run dsh for experiments, plugin development, or work that benefits from session replay. dsh can also delegate to Claude Code and Codex binaries as subagents, so it can sit above other tools rather than replacing them.
### Does either one need a GPU?
No. Both call hosted model APIs by default, so your machine or server only runs agent logic, which is CPU-light. A GPU matters only if you serve a local model yourself through Ollama or vLLM, and that choice is independent of which agent you pick.
### Can OpenCode run on a server instead of my laptop?
Yes. `opencode serve` starts a headless HTTP server with an OpenAPI spec at `/doc`, and there is an official `@opencode-ai/sdk` for driving it programmatically. Put it behind SSL and authentication, supervise the process, and CI or teammates can reach it. [**Managed Node.js hosting**](https://xcloud.host/node-js-hosting/) handles that foundation if you would rather not wire it yourself.
### Why can’t I reach the DeepSeek Harness Web UI on my server?
It binds to `127.0.0.1:3080`, localhost only, by design. Use an SSH tunnel (`ssh -L 3080:127.0.0.1:3080 user@server`) for quick access, or put an SSL-terminated, authenticated reverse proxy in front of it. Never bind it to `0.0.0.0` on a public IP without those layers, since the agent can run shell commands.
### I followed an OpenCode tutorial and the commands do not match. Why?
Almost certainly a fork mismatch. The original project was maintained by Charm and later split; the widely used version today is the SST/Anomaly TypeScript rewrite, while Charm’s continuation is named Crush. Tutorials describing a Go codebase and Bubble Tea TUI belong to the earlier lineage.
### My agent lost its session history after a rebuild. How do I prevent that?
Both tools keep state on disk: dsh in its session-log data directory, OpenCode in its local session store and `AGENTS.md`. If you run either in Docker, mount that directory as a named volume, otherwise every rebuild wipes it. On a VPS or managed instance, keep the data directory on persistent disk and back it up.
### How do these compare to OpenClaw and Hermes Agent?
Different category. OpenCode and dsh are coding agents; OpenClaw and Hermes Agent are general-purpose assistants built around messaging channels and persistent memory. The [**DeepSeek Harness vs OpenClaw vs Hermes Agent comparison**](https://xcloud.host/deepseek-harness-vs-openclaw-vs-hermes-agent/) covers that side, and dsh appears in both because its plugin kernel spans the two use cases.
## Conclusion: Stability or Composability?
The honest 2026 answer: **OpenCode if you write code for a living, DeepSeek Harness if you build the tools that write code.**
OpenCode earned its 160,000 stars by being unglamorous and reliable. Plan mode, LSP awareness, 75+ providers, and a headless server mode add up to a tool that fits the day you already have. DeepSeek Harness earned its four-day star curve by proposing that the runtime should be yours to rebuild, and that idea will likely outlive the current release candidate even if v0.1 does not survive contact with your production repo.
### Expert Picks by Goal
Your goal
Best choice
Why
Ship code today with fewer surprises
**OpenCode**
Mature, LSP-aware, Plan mode prevents damage
Build custom agent infrastructure
**DeepSeek Harness**
Every core component is replaceable
Widest model and provider choice
**OpenCode**
75+ providers plus free local models
Debug agent runs forensically
**DeepSeek Harness**
Fork and replay any session
Avoid the terminal
**DeepSeek Harness**
Browser UI by default
Run an agent your CI can call
**Either, hosted**
`opencode serve` or the dsh headless profile
**What to do this week:** Install both, they are free, and give each the same real task from your backlog with the same model. An afternoon of controlled comparison beats a month of reading. If the winner needs to keep working after you close the laptop, [**deploy it managed on xCloud**](https://app.xcloud.host/deepseek-harness), where dsh is one click and headless OpenCode runs on managed Node.js, both with SSL, supervision, and backups handled, and a 14-day money-back guarantee if it does not earn its place.
For more comparisons on AI coding agents and the open-source stack behind them, [**subscribe to the xCloud blog**](https://xcloud.host/blog/) or join the [**xCloud Facebook community**](https://www.facebook.com/groups/xcloud.community).
---
# Defending Against the 12 Major Client Side Security Threats in 2025 - xCloud
> Learn how to defend against the 12 major client side security threats. From XSS to SQL Injection, our guide offers essential tips to protect your data and privacy.
Today, we all use the internet for work, to learn new things, and to talk to our friends. But, when we use the internet, there are dangers that can hurt our computers or steal our information. These dangers are called **major client side security threats**.
In 2025, these threats are very smart and can trick many people. We need to know about these dangers so we can keep our computers and information safe. Today, we will talk about the 12 major client side security threats and how we can protect ourselves from them. Let us start learning about how to keep our internet time safe!
## **What Are Client Side Security Threats?**
Major client side security threats are problems that happen when bad people try to attack the part of your computer or phone that you use to look at websites or use apps. These are the areas where you put in information like your names, passwords, and other details. When you interact with the internet directly, that is where these threats come in.
Think of your device like your house. If someone wanted to sneak in, they might try the windows, doors, or even the mailbox. In the world of computers and phones, major client side security threats are like these sneaky ways that hackers try to get into your device. They might trick you into opening a bad email, clicking on a harmful link, or downloading something that looks fun but is actually dangerous.
By understanding these threats, you can learn how to lock the doors and windows of your device better. This way, you can keep your personal information safe from hackers who want to steal it. So, it is very important to know about these major client side security threats and how to stop them from affecting you and your family.
## **The 12 Major Client Side Security Threats in 2025**
It is important to understand these threats because they target the part of your computer system that you interact with directly, like your web browser and applications. By learning about these issues, you can be better prepared to stop hackers before they can do any damage. So, let us discuss what these major client side security threats are and how you can defend against them to keep your digital life safe and secure.
### **Threat 1: Cross-Site Scripting (XSS)**
One of the big dangers on the internet is called Cross-Site Scripting, or XSS for short. XSS is a kind of attack where bad people put harmful scripts into websites that we trust. Imagine you are writing on a wall where everyone can write. Someone could write something bad that makes your pen stop working or messes up your drawing. That is a bit like how XSS works on websites.
When you visit a website hit by XSS, these harmful scripts run on your computer without you knowing. This can lead to bad people stealing your personal information, like your passwords or even your messages. It is scary because you can not easily see it happening. Here are some simple steps we can take to protect ourselves from XSS:
1. **Be Careful Where You Click:** Just like you would not pick up a candy from the ground and eat it, do not click on links from people or places you do not trust. Sometimes, these links can have hidden scripts that cause XSS attacks.
2. **Use Trusted Extensions:** Some browser extensions can help keep you safe. They check the websites you visit and make sure there is nothing suspicious. It is like having a guard who checks if the wall you are writing on is safe.
3. **Keep Your Browser Updated:** Make sure the internet browser you use (like Chrome, Firefox, or Edge) is always updated. When a browser is up-to-date, it has the latest protection against many types of attacks, including XSS.
4. **Watch Out for Warnings:** Sometimes, your browser will warn you if a website looks dangerous. Always pay attention to these warnings. It is like a stop sign on the road telling you to be careful.
### **Threat 2: SQL Injection**
[**SQL injection**](https://wpdeveloper.com/fortify-wordpress-site-from-sql-injection-9-ways/) is another serious major client side security threats. It happens when bad people use web forms or URLs to send bad code to a website’s database. Think of it like slipping a fake ticket into a movie theater that tricks the ticket checker into letting more people in for free.
Databases hold all the important information, like user details and passwords. When someone does an SQL injection, they can trick the database into showing or changing information that they should not see or touch. This can lead to big problems, like stealing private information or messing up the website. Here are some ways to protect ourselves from SQL injection:
1. **Be Careful with Your Information:** Be thoughtful about where and how you enter your personal information online. Only fill out forms on websites you trust, and never give more information than you need to.
2. **Use Strong Passwords:** Using strong and unique passwords for different sites is like having a good lock on your door. It makes it harder for hackers to guess and use your passwords to attack databases.
3. **Keep Software Updated:** Just like with defending against XSS, keeping your software updated helps protect against SQL injection. Updates often fix security holes that hackers use to perform these attacks.
4. **Learn to Recognize Phishing Attempts:** Often, SQL injection attacks start with a phishing attempt, where you receive a fake email asking for your information. Knowing how to spot these fake emails can stop SQL injection attacks before they start.
### **Threat 3: CSRF (Cross-Site Request Forgery)**
**Cross-Site Request Forgery**, often called **CSRF**, is another major client side security threat that we need to be careful about. CSRF tricks you into doing things you did not mean to do on a website where you are logged in. If someone secretly changed your TV channel using another remote while you thought you were using yours.
CSRF can happen when you click on a bad link or visit a harmful website while you are logged into another site, like your email or bank account. This bad site can send a request, like changing your password, without you knowing. This is dangerous because it can let bad people take over your accounts or steal your personal info. Here is how you can protect yourself from CSRF:
1. **Log Out of Websites:** Always log out from websites when you are done, especially ones where you have important information like your bank or email. It is like locking your car after you park it.
2. **Be Careful with Links:** Just like with other threats, be very careful about clicking on links, especially in emails from people you do not know. If a link looks weird or you did not expect it, do not click on it.
3. **Use Security Features:** Some websites have features that help protect against CSRF. This might include things like “same-site cookies” which make sure requests come from the same website, not a bad one. Always turn on extra security features when you can.
4. **Update Your Browser:** Keep your internet browser updated. New updates often have better security that helps protect against threats like CSRF.
### **Threat 4: Session Hijacking**
**Session hijacking** is another major client side security threat that we should all know about. This happens when a bad person takes over your online session with a website. For example, if you were playing a video game online and someone else took your controller and started playing as you. That is kind of what happens during session hijacking.
When you log in to a website, a session is started between your computer and the website. It is like a secret handshake that keeps you connected. If someone steals that handshake, they can pretend to be you. They might see your private information, buy things with your money, or change your account details. Here is how you can fight against session hijacking:
1. **Use HTTPS:** Always make sure the websites you use have HTTPS in the URL, not just HTTP. HTTPS is more secure because it encrypts, or scrambles, your information so others can not easily see it. It is like sending a letter in a locked box instead of a clear envelope.
2. **Log Out after Use:** Always log out from websites when you are finished, especially if you are using a public computer or Wi-Fi. This closes your session safely.
3. **Be Wary of Public Wi-Fi:** Public Wi-Fi can be risky because it is easier for [hackers to intercept the data](/data-leakage-examples-and-tips-to-fight/) you send and receive. If you must use public Wi-Fi, avoid logging into important accounts or use a VPN (Virtual Private Network) which makes your connection more secure.
4. **Keep Your Software Updated:** This includes your web browser and any security software you have. Updates often include fixes for security problems that could allow session hijacking.
### **Threat 5: Insecure Direct Object References**
Insecure **Direct Object References**, often abbreviated as IDOR, is a major client side security threat that can allow bad people to see or change information they should not have access to. if you could see someone else’s report card by just changing a number on a website. That is what happens with IDOR.
This threat occurs when a website uses simple references to access objects directly, like database entries or files. If these references are not protected well, someone could change them to access other users’ data, like personal details or files. Here is how we can protect ourselves from IDOR:
1. **Be Careful with Your Information:** Always think twice before you enter personal information on a website. Make sure the website is trustworthy and has good security measures in place.
2. **Check URL Changes:** Sometimes, just looking at the URL in your web browser can tell you if the website is using simple object references. Be cautious if you see a number or a name in the URL that looks like it controls what you see on the page.
3. **Use Websites with Good Security Practices:** Websites that have strong security measures are less likely to be vulnerable to IDOR. These websites use methods that hide the direct references or check that you are allowed to see what you are asking for.
4. **Keep Your Browser Updated:** Again, having the latest updates for your web browser can help protect you from many major client side security threats, including IDOR. Browser updates often include new security tools that make it harder for hackers to exploit vulnerabilities.
### **Threat 6: Security Misconfiguration**
**Security Misconfiguration** is a major client side security threat that happens when websites or online services are not set up correctly. For instance, if someone forgot to close a window in their house before leaving. If a thief walks by, it would be easy for them to get in. This is similar to what happens when an online service is not configured properly hackers find it easier to sneak in.
This threat can occur in many ways, such as when default passwords are not changed, unnecessary services are left running, or when software is not set up securely. Each of these issues can create openings that bad people can use to access private information or disrupt services. Here is how to protect against security misconfiguration:
1. **Update and Patch:** Always keep your software up-to-date. Updates fix security holes that hackers might use to get into your systems.
2. **Secure Settings:** When setting up new devices or software, change default settings, passwords, and usernames to something secure. This includes turning off or removing any software features you do not need.
3. **Regular Security Reviews:** Regularly check your security settings to make sure everything is as tight as it should be. This is like making sure all the windows and doors in your house are locked before you leave.
4. **Educate Yourself:** Learn about the best security practices for the software and devices you use. The more you know, the better you can protect yourself from hackers.
### **Threat 7: Sensitive Data Exposure**
**Sensitive Data Exposure** is a major client side security threat where our personal and important data can be stolen or seen by others who should not have access to it. Think of it like leaving your diary open on a park bench where anyone walking by could read it.
This kind of exposure can happen when websites do not protect our data well enough. It could be anything from your passwords and credit card numbers to your home address and phone number. If bad people get this information, they can steal from you or pretend to be you. Here is how to protect yourself from sensitive data exposure:
1. **Use Strong Passwords:** Make sure you use strong and different passwords for your online accounts. A strong password is like a strong lock on your diary. It makes it harder for someone to open it and read your secrets.
2. **Look for HTTPS:** Always check that the website you are using has HTTPS in its URL. This means the site is more secure. It is like making sure your diary has a lock before you write in it.
3. **Be Careful What You Share:** Think carefully about the information you put online. Ask yourself if you really need to give this information. It is like thinking twice before you write something really personal in your diary.
4. **Use Security Settings:** Many websites and apps have settings that help protect your privacy. Make sure you understand these settings and use them to keep your information safe. It is like covering your diary with something so people can not easily see it.
### **Threat 8: Missing Function Level Access Control**
**Missing Function Level Access Control** is a major client side security threat that happens when websites do not properly check if someone has the right to do something, like viewing private files or changing settings. Imagine if anyone at your school could go into the office and look at any student’s records just because the door was unlocked. That is similar to what happens with this threat.
This threat means that once someone is logged into a system, they might access things they should not be able to, just because the website does not check their permissions carefully each time. This can lead to unauthorized changes or exposure of sensitive information. Here is how we can protect ourselves from missing function level access control:
1. **Be Cautious About Where You Log In:** Only log into accounts from your own devices and from secure locations. This makes it less likely that someone else will be able to access your logged-in session.
2. **Use Websites with Good Security Practices:** Choose to use services and websites that are known for their strong security. These websites are better at managing who can see what, making sure only the right people get access to sensitive actions.
3. **Keep an Eye on Your Account Activities:** Regularly check the logs of your online accounts, if available. This means looking at what has been done with your account to see if there is anything you did not do.
4. **Educate Yourself About Security Features:** Understanding the security features and settings available on the platforms you use can help you better protect your accounts. This is like knowing all the exits and doors in your house so you can make sure they are all locked.
### **Threat 9: Using Components with Known Vulnerabilities**
Using Components with Known Vulnerabilities is a major client side security threat that happens when websites use old or unsafe software that has problems that bad people know about. It is like using an old lock on your door that everyone knows can be easily picked.
When websites or apps use these old parts (or components), it gives hackers a chance to break in because they already know what weaknesses these parts have. They can steal information, mess up the website, or even take over the website completely. Here is how you can protect yourself from this threat:
1. **Update Your Software:** Always make sure the software on your devices is up-to-date. Updates often fix old problems that could let hackers in. It is like changing an old lock for a new, stronger one.
2. **Use Reliable Software:** When you choose software, pick ones that are well-known for being safe and get regular updates. It is like choosing a lock for your door that is made by a trusted brand.
3. **Stay Informed:** Keep an eye on news about software you use. If you hear about a problem, look for updates or a way to fix it. This is like knowing that a certain type of lock has been recalled for safety issues.
4. **Secure Configuration:** Make sure your software is set up safely. Sometimes, the way software is set up can leave it open to attacks. It is like making sure your door’s lock is not just installed, but also properly working.
### **Threat 10: Unvalidated Redirects and Forwards**
Unvalidated Redirects and Forwards a major client side security threat where websites send you to other websites without checking if those destinations are safe. Think of it like being told to take a shortcut by someone you do not know, without knowing where it really goes. This can be risky because it might lead you to a dangerous place.
When websites do not properly check where they are sending you, hackers can trick the site into sending you to a bad website. This bad site might look real but can be set up to steal your information, like passwords or even install harmful software on your device. Here is how to protect yourself from unvalidated redirects and forwards:
1. **Stay Alert to URL Changes:** Watch the web address bar in your browser. If you click on a link and the URL changes weirdly, be cautious. It is like keeping an eye on road signs to make sure you are still on the right path.
2. **Avoid Clicking Suspicious Links:** Be careful with links in emails, messages, or websites, especially if they look strange or come from someone you do not know. It is like ignoring advice from a stranger who seems shady.
3. **Use Trusted Websites:** Stick to well-known and trusted websites, especially when you need to enter personal information. Trusted sites are more likely to have the right security to prevent these threats.
4. **Keep Software Updated:** Ensuring your browser and any security software are up to date can help protect against threats that exploit unvalidated redirects and forwards.
### **Threat 11: Clickjacking**
[**Clickjacking**](/clickjacking-attack-examples-and-prevention/) is a sneaky major client side security threat where bad people trick you into clicking on something you did not mean to. Imagine if someone covered a real button with a fake button that looks just like it. You think you are clicking the real button, but actually, you press the fake one.
Clickjacking can happen when hackers hide invisible layers over what looks like normal web pages. You might think you are clicking on a video play button, but you are actually giving access to your webcam or liking a page on social media without knowing it.
Here is how you can defend against clickjacking:
1. **Use Modern Browsers:** Make sure you are using a modern and updated web browser. New browsers have better protection against many types of attacks, including clickjacking. They can block those invisible layers.
2. **Enable Browser Security Features:** Many browsers have features that stop bad pages from doing sneaky things. For example, frame busting is a feature that stops other sites from putting hidden frames on the page you are viewing.
3. **Be Cautious with Links and Buttons:** Be careful where you click, especially on websites you do not visit often. If something seems off, like a button not doing what it should, it is better to close the page.
4. **Use Security Software:** Some security programs can help protect against clickjacking by warning you about suspicious websites or blocking harmful content.
### **Threat 12: Using Outdated or Unsupported Software**
Using Outdated or Unsupported Software is a significant major client side security threat. This happens when you keep using old versions of software or apps that no longer get security updates from the creators. Imagine driving a car that has not been serviced for years; it is more likely to break down and is not as safe.
When software is outdated, it may have weaknesses that hackers know about and can easily attack. These attacks can lead to them stealing your private information, taking over your computer, or using it to attack others. Here is how to protect yourself from using outdated or unsupported software:
1. **Regular Updates:** Always update your software and apps whenever a new version is available. These updates often fix security problems that could let hackers in. It is like getting your car regularly checked and serviced to make sure it stays safe.
2. **Uninstall Unused Software:** If you have old programs on your computer that you do not use anymore, it is best to uninstall them. This reduces the chances of bad people finding and using old software to get into your computer.
3. **Use Supported Software:** Make sure the software you use is still supported by the people who made it. Unsupported software does not get updates, which makes it risky. It is like using equipment that no one fixes anymore.
4. **Security Software:** Have good security software installed. This can help protect you by blocking attacks and warning you about risky software on your computer.
## **Use of Security Tools and Best Practices**
Using the right tools and following best practices can greatly help in defending against major client side security threats. These tools and strategies ensure that your online activities remain safe and your personal information is well-protected. Here are some essential security tools and best practices to consider:
1. **Antivirus And Anti-Malware Software:** These are the first line of defense against many threats. They scan your computer for known viruses and malware, and help remove any threats found. Make sure to keep this software updated to protect against the latest threats.
2. **Firewalls:** A firewall helps protect your network by blocking unauthorized access while permitting outward communication. It can be software-based or hardware-based and is crucial for preventing unauthorized access to your network.
3. **VPN (Virtual Private Network):** A VPN encrypts your internet connection, making it secure and private. This is especially important when you are using public Wi-Fi networks, as it helps protect your data from major client side security threats like Man-in-the-Middle attacks.
4. **Browser Security Settings:** Increase your browser’s security by adjusting settings to block unauthorized downloads, disable unwanted plugins, and control site permissions. Regularly clear your cookies and cache to remove personal data stored by websites.
5. **Strong Passwords And Password Managers:** Use complex passwords that are hard to guess. A password manager can help you generate and store these passwords securely. Never reuse passwords across different sites.
6. **Two-Factor Authentication (2FA):** Always enable 2FA where possible. This adds an additional layer of security by requiring not only your password but also a second factor, like a code sent to your phone, to access your accounts.
7. **Regular Updates:** Keep all software, including your operating system, browser, and any installed applications, up to date. Developers regularly release updates to fix security vulnerabilities that could be exploited by attackers.
8. **Educate Yourself And Others:** Stay informed about the latest security threats and how to protect against them. Educate your family, friends, and colleagues about safe online practices to help them avoid common pitfalls.
By integrating these security tools and best practices into your daily online activities, you can enhance your defenses against major client side security threats. Maintaining a proactive approach to cybersecurity can significantly reduce the risk of falling victim to cyber attacks.
## **Fight Against Client Side Security Threats & Keep Your Online Platform Safe**
We have learned about the 12 major client side security threats that are especially important in 2025. By understanding these threats, we can take better steps to protect ourselves online. It involves being aware of the dangers, using the right tools to protect yourself, and always staying alert. We can fight off these major client side security threats and keep our digital space secure.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and engage in discussions.
---
# Discourage Search Engines from Indexing This Site: When & Why to Use This Option - xCloud
> Learn how to discourage search engines from indexing this site & why you need to do things that you're not supposed to do.
If you have explored the WordPress backend, you might have seen an option called **_‘Discourage search engines from indexing this site_**’ and wondered what it does. Is it a way to hide your site from search engines or keep your content private from unwanted visitors? While this option might seem like a quick fix, it is important to understand how it works and its limitations. In this blog, we will explain what this option does, its limitations & how you can do this using xCloud. Let us get started.
## **What Does “Discourage Search Engines from Indexing This Site” Mean?**
Ever wondered how search engines discover and rank your website? The answer lies in an automated program known as a spider—sometimes referred to as a robot or crawler. These digital scouts traverse the internet, visiting websites and logging content to build a vast index of information.
### **What Do Spiders Do?**
Spiders play a crucial role in how Google and other search engines interact with your site. Here is what they do:
- **Rank Your Website:** Spiders gather data to determine how your site should rank in search engine results.
- **Grab Snippets:** They extract content snippets from your articles to display on search results pages.
- **Pull Images:** Spiders collect images from your site for indexing in platforms like Google Images.
### **How WordPress Handles Crawling Instructions**
In WordPress, you have the option to control whether search engines can index your site. For example, if you enable the **‘Discourage search engines from indexing this site’** setting, here is what happens:
- **Robots.txt File Update:** WordPress modifies the robots.txt file, which provides guidelines to spiders about which parts of your site to crawl or ignore.
- **Meta Tag Addition:** It can also add a meta tag in your site’s header, instructing search engines like Google not to index any of your content.
This feature is helpful if your site is still under construction or if you prefer to keep it private. However, remember that discouraging search engines from indexing your site means it will not appear in search results, impacting your site’s visibility.
By understanding how spiders work and how to guide them effectively, you can better manage your website’s SEO and ensure it is optimized for search engines.
## **Why Would You Hide Your Website From Search Engines?**
[**Websites are built**](/guide-how-to-create-a-website/) to connect with audiences — to inform, engage, and encourage action. Whether you are sharing insightful articles, selling products, or creating captivating content, visibility is crucial. So, why would anyone intentionally block search engines from accessing their site?
Surprisingly, there are valid scenarios where deindexing part or all of your website makes sense. Let us explore the reasons and alternatives you might consider. Here are a few common reasons to hide your website (or parts of it).
- **Your Site is Under Development:** If your website is not ready for the public eye, you may not want search engines indexing incomplete pages or test content.
- **You Want Private Content Management:** WordPress can double as a private content management system, perfect for internal resources or personal projects you do not want to share publicly.
- **Protecting Sensitive Information:** Sometimes, websites house sensitive data you would rather keep away from prying eyes.
- **Restricting Access to Specific Groups:** If your content is designed for a niche audience — accessible via invitation or link only — keeping it off search engines makes sense.
- **Gated or Exclusive Content:** For paywalled articles or exclusive newsletters, deindexing ensures that only paying members or subscribers can access the content.
- **Archiving Old Content:** To improve user experience and maintain relevance, you may want to hide outdated or irrelevant articles from search engines.
- **Avoiding SEO Penalties:** Duplicate content, test pages, or unnecessary subdomains can hurt your site’s SEO ranking. Blocking search engines from these areas helps protect your main site.
### **Are There Better Alternatives?**
For some of these scenarios, alternative solutions can be more effective than deindexing:
- **Use a Local Development Server:** When building a new site, consider testing it on a private server or [**staging environment**](/create-a-staging-environment-in-xcloud/) rather than exposing it online.
- **Set Articles to Private:** WordPress allows you to mark pages or posts as private, keeping them hidden from public view and search engines.
- **Add Password Protection:** For sensitive or gated content, protect access using a secure password.
However, there are cases where deindexing remains the right choice. Whether it is protecting private resources or fine-tuning your SEO strategy, selectively blocking search engines is a legitimate tool in your website management toolkit.
Remember, striking the right balance between visibility and [**privacy ensures**](/defend-against-12-major-client-side-security-threats/) your website serves its purpose effectively. Speaking of it, xCloud is the platform that allows you to keep that right balance easily.
## **How to Discourage Search Engines from Indexing Your Site Using xCloud?**
Managing search engine visibility in [**xCloud**](/) is straightforward and versatile, allowing you to control whether search engines index your WordPress site. This feature is available in multiple locations within the xCloud dashboard, ensuring convenience and flexibility.
### **Search Engine Visibility in xCloud**
For live websites, it is recommended not to discourage search engines from indexing your site. When adding a new site, you will find the Search Engine Visibility option under “**More Advanced Settings**”, as shown below:
Remember, for the Staging & Demo site, this option is being discouraged by default. What if you do not check this option while adding a site? No worries. You can do it later; as we mentioned, we can use this option in multiple places on xCloud.
Once you log into your xCloud dashboard, click on ‘Sites’ and from the list of multiple sites (if you have) enter the sites for which you want to discourage search engine indexing.
On the resulting page, click on ‘Site Settings’ from the left side panel. Scroll down a bit to find the option ‘Search Engine Visibility’, click to turn on the toggle button, & hit the ‘Save Settings’ option to complete the configuration. Well, you’ve done your part, now it’s up to search engines to honor this request.
Once configured, your site’s visibility settings will request search engines not to index the site. However, it is ultimately up to the search engines to honor this directive.
_**Note:** Do not forget to uncheck the box while going back to live again._
With this simple process, you can effortlessly manage search engine visibility for your WordPress site directly from the xCloud dashboard, keeping your staging or demo environments private and ensuring best practices for live sites.
## **Make the Most of Search Engine Visibility Options with xCloud**
Deciding when to discourage search engines from indexing your site is essential for effective website management. Whether protecting sensitive content, staging a demo, or optimizing SEO, this option helps you control what gets indexed online.
xCloud simplifies the process with easy-to-use tools for managing search engine visibility, ensuring you can balance privacy and exposure effortlessly. Use this feature wisely to safeguard your content, streamline development, and keep your live sites optimized for search engines.
If you want to read more blogs like this one to learn about updates from xCloud, [**subscribe to our blogs**](/blog/). And join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to connect people with common interests.
---
# Django vs Node.js: Which Is Better for Web Development? - xCloud
> Learn Django vs Node.js for web development. Compare performance, scalability, security and developer experience to pick the right backend framework.
When new developers look for a suitable backend technology, they often find themselves comparing Django vs Node.js. Both languages are widely used for web development and each has strong features that fit different project needs. Choosing the right technology stack is one of the most critical decisions in web development.
Both technologies are important in web development. However, they have different purposes and work best in different situations. This blog explains Django and Node.js by looking at their design, strengths, limits and best uses. It will help you decide which one fits your project. Whether you are building a content system, a busy real‑time app or complex APIs, knowing these differences will guide you to the right choice
## **Introduction to Django And Node.js**
Modern web development relies on powerful frameworks and runtimes that handle the complex work of serving content to users. Django and Node.js have become two of the most popular choices for building web applications, yet they operate in very different ways.
### **What Is Django?**
**[Django](https://www.djangoproject.com/)** is a high-level web framework built with Python to help developers create web applications faster and in a cleaner way. It started as an internal tool for building dynamic news websites and later evolved into a full-featured framework trusted by developers around the world. Django focuses on clear structure, speed and security, which makes it a popular choice for modern web projects.
### **What Makes Django Special**
Discover what makes Django special, a secure, scalable Python framework built for rapid development. Check out how it helps developers build powerful web applications faster and with less effort:
- **Clean project structure:** Django follows the Model View Template pattern. Models manage data, views handle logic and templates control design. This keeps code organized and easy to maintain.
- **Built for rapid development:** Common features come ready to use so developers spend more time building features and less time on setup.
- **Batteries included framework
**Django includes an ORM, an authentication system, form handling and an admin dashboard by default.
- **Strong focus on security:** Built-in protection against CSRF, SQL injection and XSS helps keep applications safe.
- **Developer-friendly workflow:** Clear conventions reduce confusion and help teams work faster together.
- **Backed by a large community:** Django has strong documentation and community support, which makes learning and troubleshooting easier.
Django helps developers build reliable, secure and scalable web applications without unnecessary complexity.
### **What Is Node.js?**
[**Node.js**](/what-is-node-js-beginners-guide/) is a runtime environment that lets developers run JavaScript outside the browser. It was introduced in 2009 and is powered by the V8 engine used in Google Chrome. Node.js is known for its speed and ability to handle many tasks at the same time, which makes it a strong choice for modern web applications.
### **Why Developers Choose Node.js**
Discover why developers choose Node.js, a fast, scalable runtime that brings JavaScript across the stack to build modern, real‑time applications:
- **Runs JavaScript on the server:** Node.js allows the same language to be used on both frontend and backend, which simplifies full-stack development.
- **Event-driven** and non-blocking**:** It processes multiple requests at once without waiting for each task to finish. This makes it ideal for real-time features.
- **Great for real-time applications:** Common use cases include chat apps, live streaming platforms and collaboration tools.
- **Works well with popular frameworks:** Node.js is often paired with Express.js, Koa, or Nest.js to manage routing and middleware more easily.
- **Huge npm ecosystem:** npm provides access to thousands of open source packages that help developers build applications faster.
- **Flexible and lightweight:** Developers can combine small modules to create custom setups that fit their project needs.
Node.js helps teams build fast, scalable applications using a single language across the entire stack.
## **Django vs Node.js: What Is the Difference?**
Django and Node.js are two popular choices for building modern web applications, yet they follow very different approaches. Choosing the right backend technology can shape how fast your product grows and how easily your team can maintain it. One offers a structured framework with built in tools while the other focuses on speed, flexibility and real time performance. Understanding how Django and Node.js differ helps developers and businesses decide which option fits their project goals best.
**Aspect**
**Django**
**Node.js**
**Type**
Event-driven and non blocking
JavaScript runtime environment
**Primary Language**
Python
JavaScript
**Release Year**
2005
2009
**Architecture**
Model View Template pattern
High performance and real-time handling
**Core Purpose**
**Built-in Features**
Rapid development with a clean structure
The framework itself includes most tools
ORM, authentication, admin panel, security tools
Minimal core, relies on external libraries
**Framework Dependency**
Real-time apps, APIs, streaming services
Requires frameworks like Express or Nest
**Performance Model**
Synchronous by default with async support
Asynchronous and concurrent by design
**Best Use Cases**
Content-driven sites, dashboards, data-heavy apps
Easier for JavaScript-focused developers
**Learning Curve**
Easier for structured backend development
Strong built-in security protections
**Scalability**
Scales well with proper setup
Scales naturally for concurrent requests
**Security Focus**
Ready-to-use admin panel included
Security depends on selected packages
**Package Ecosystem**
Python ecosystem via pip
Massive npm package ecosystem
**Admin Interface**
No built-in admin solution
Faster for custom real-time systems
**Development Speed**
Faster for standard web apps
Faster for custom real time systems
## **Which Backend Technology Should You Choose?**
When it comes to building web applications, Django and Node.js are two of the most popular backend technologies. Each follows a different philosophy, offers unique strengths, and is suited for specific project requirements. Understanding their architecture, performance, ecosystem and security will help you make an informed choice.
### **Architecture And Framework Philosophy**
Django follows a monolithic **[Model View Template (MVT)](https://www.tutorialspoint.com/django/django_mvt.htm)** pattern, providing a structured environment where models manage data, views handle logic and templates control presentation. It comes with built in tools like an ORM, an admin panel and authentication, allowing developers to focus on building features rather than wiring components together.
🐍
view-example.py
\# Django view example
from django.shortcuts import render
from .models import Article
def home(request):
articles = Article.objects.all()
return render(request, 'home.html', {'articles': articles})
In contrast, Node.js uses an event-driven, non-blocking I/O model. It is modular and often paired with frameworks such as Express.js or Nest.js, giving teams flexibility to choose only the libraries they need.
📄
Express-example.js
// Node.js Express example
const express = require('express');
const app = express();
app.get('/', (req, res) => {
res.send('Hello World from Node.js!');
});
app.listen(3000, () => console.log('Server running on port 3000'));
### **Language And Ecosystem**
Django runs on Python, a language known for readability and a vast library ecosystem. Python excels in data processing, machine learning, and scientific computing, making Django particularly suitable for projects that integrate with these domains.
Node.js, on the other hand, uses JavaScript, a language already familiar to many web developers. Running the same language on the frontend and backend simplifies full-stack development. Its npm registry hosts hundreds of thousands of packages, enabling developers to assemble lightweight, customized solutions for almost any requirement.
**Feature**
**Django (Python)**
**Node.js (JavaScript)**
Language Focus
Backend & data-heavy apps
Real time and web apps
Libraries
Data analysis, ML, web tools
Web, APIs, streaming
Community
Mature and stable
Large and fast evolving
### **Performance And Concurrency**
Django operates on a synchronous request-response cycle, which makes it well-suited for CPU-bound tasks and data-heavy applications. Handling high concurrency requires additional tools or multiple servers.
Node.js’s event-driven and asynchronous design allows a single thread to manage thousands of connections simultaneously. This makes Node.js ideal for chat apps, streaming platforms and other real-time applications where speed and scalability under load are critical.
📄
handling-multiple-requests.js
// Node.js example of handling multiple requests asynchronously
const http = require('http');
http.createServer((req, res) => {
setTimeout(() => { // simulate async operation
res.write('Response handled asynchronously');
res.end();
}, 1000);
}).listen(3000);
### **Scalability And Reliability**
Scalability and reliability are key factors when building applications that need to handle growth in traffic or data. **Django** is designed to scale **horizontally**, meaning you can run multiple instances of your application on different servers behind a load balancer. This allows the system to handle more users by distributing the workload across several machines.
For applications that require **real-time features** like chat or notifications, Django can use **Django Channels**, which adds support for WebSockets and asynchronous tasks. However, because Django operates with a synchronous request-response model by default, handling extremely high numbers of concurrent users may require **extra servers, worker processes or caching strategies** to maintain performance.
[**Node.js**](/node-js-hosting/) is designed for handling many connections at the same time and scaling easily across multiple servers. Its **event-driven, non-blocking** model allows a single Node process to manage thousands of users at once. Developers can use **clustering tools** to run multiple instances on different CPU cores, and **process managers like PM2** help distribute traffic and keep the system running even if one process fails. This makes Node.js ideal for applications that need to handle **rapid growth or sudden spikes**, such as streaming services, online games or real-time collaboration tools.
### **Security And Safety**
Security is one of Django’s strongest features. It comes with **built-in protections** against common web threats such as [**XSS (Cross-Site Scripting)**](https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/XSS), [**CSRF (Cross-Site Request Forgery)**](https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/CSRF) and [**SQL injection**](https://www.w3schools.com/sql/sql_injection.asp). Django also **hashes passwords securely**, manages user sessions safely, and includes tools to prevent clickjacking. The best part is that **many of these protections are enabled by default**, so even developers who are new to web development can build applications that follow security best practices without extra effort.
Node.js, on the other hand, is more **modular and flexible**, but that means it doesn’t include as many security features out of the box. Developers need to **configure protections manually** or rely on third-party packages to secure their applications. While Node.js supports **SSL and TLS** for secure data transmission, setting them up requires additional steps. Because of this, building a secure Node.js application often demands more attention and experience, especially when handling user data or sensitive information.
## **Which Framework Offers Better Learning And Community Support?**
Developer experience and community support are important when choosing a backend framework. Django and Node.js work differently and knowing their strengths can help your team build projects faster, avoid problems and achieve better results.
### **Development Experience And Learning Curve**
Django provides **rapid development** with its built-in ORM, admin panel and templating system. These tools reduce boilerplate code, enforce best practices and speed up delivery. Python developers often find it easy to use, though the structured approach may feel restrictive for those who prefer full flexibility.
Node.js offers **flexibility and modularity** but it requires more initial setup. Developers choose frameworks like Express.js or Nest.js and assemble the stack they need. This freedom suits experienced developers, but beginners may find it overwhelming. Knowledge of **asynchronous programming**, including callbacks, promises, and async/await, is essential to use Node effectively.
### **Community Support**
The Django community is **mature and stable**, active since 2005. Long-term support (LTS) releases guarantee updates and security patches over extended periods. Developers benefit from extensive documentation, tutorials, third-party packages and forums. While smaller than Node’s community, it is known for **reliability and thorough guidance**.
Node.js has a **fast-growing and vibrant community**. A large pool of developers, active discussions on forums, and abundant learning resources make it easy to get help. The sheer size of the ecosystem requires careful evaluation of resources and packages to ensure quality and security.
## **Django And Node.js Side-by-Side Coding Comparison**
Code examples help illustrate how Django and Node.js differ in real projects. The examples below show **basic routing and response handling**, highlighting differences in syntax and workflow. These snippets are simple and meant for learning; they are not production-ready.
A basic route is one of the simplest ways to see how Django and Node.js handle requests and responses. In this example, we create a small endpoint that returns a greeting message.
### **Django Hello Endpoint**
In Django, a **view function** handles an incoming request and returns a response. The URL configuration maps a path to that function.
🐍
django-hello-endpoint.py
\# views.py
from django.http import HttpResponse
def hello\_view(request):
return HttpResponse("Hello world from Django!")
\# urls.py
from django.urls import path
from .views import hello\_view
urlpatterns = \[
path('hello/', hello\_view),
\]
**Output:**
Here, hello\_view receives a request object and returns a simple text response. When a user visits /hello/, Django calls the view and returns the greeting.
### **Node.js Hello Endpoint**
In Node.js, developers often use **Express.js** to handle routing. The following example creates a similar endpoint:
📄
app.js
// app.js
const express = require('express');
const app = express();
app.get('/hello', (req, res) => {
res.send('Hello world from Node!');
});
app.listen(3000, () => {
console.log('Server running on port 3000');
});
**Output:**
Here, app.get registers a handler for GET requests to /hello and uses a callback to send a response. The app.listen function starts the server on port 3000. Node.js uses **JavaScript syntax** and asynchronous callbacks, while Django uses **Python syntax** and declarative URL mapping.
## **Django vs Node.js: Pros, Cons And Key Differences**
A clear understanding of Django and Node.js strengths and limitations ensures projects succeed. Both frameworks have unique features that suit different scenarios, and the right choice depends on project requirements, team skills and goals. The table below highlights key advantages and disadvantages of each framework.
**Framework**
**Advantages**
**Disadvantages**
**Django**
🟢 Rapid development with built-in tools like ORM and admin panel
🟢 Strong security out of the box (XSS, CSRF, SQL injection)Structured and stable architecture
🟢 Extensive Python ecosystem for data, ML, and scientific computing
🟢 Scales well with multiple instances and Django Channels
🔴 Less suitable for high-concurrency real-time apps
🔴 Prescribed structure limits flexibility
🔴 Overhead may feel heavy for small projects
**Node.js**
🟢 High concurrency and fast I/O with event-driven architecture
Uses JavaScript across frontend and backend
Flexible, modular ecosystem via npm
🟢 Ideal for real-time apps, microservices and streaming platforms
🟢 Lightweight and easy for small projects
🔴 Security features require manual setup and careful configuration
🔴 Learning asynchronous programming can be challenging
🔴 Inconsistent quality of some npm packages
🔴 Less efficient for CPU-heavy or data-intensive tasks
## **When to Choose Django Or Node.js?**
The right backend technology determines how efficiently a project runs and how easily a team can maintain it. Django and Node.js are both powerful, yet they excel in different areas. Django handles **data-heavy tasks and administrative workflows** with built-in tools and a structured approach, while Node.js performs best in **real-time applications** that require high concurrency and fast responses.
A **hybrid setup** combining both technologies allows teams to leverage the strengths of each, using tools like **Redis or message queues** to pass data between services efficiently. This guide explains when to use Django, Node.js, or a combination of both.
### **Use Django When**
Django is ideal for projects that require structured data handling, security and rapid development. **It works best if you are:**
- Building a **content management system, an enterprise application, or a platform with complex data**. Django’s ORM and admin panel make it easier to manage schemas and business rules.
- Focusing on **security and compliance**. Built-in protections against XSS, CSRF, SQL injection and secure password handling help safeguard user data.
- Using **Python or having a team experienced in Python**. The language’s readability and libraries for data analysis or machine learning can accelerate development.
- Prioritizing **speed to market**. Django’s batteries-included approach reduces setup time and lets you release applications faster.
### **Use Node.js When**
Node.js shines in projects that require real-time features, flexibility and high concurrency. **It is a good choice if you are:**
- Developing a **real-time application** like chat apps, online games, or collaborative tools. Node’s event-driven, non-blocking model handles thousands of simultaneous connections efficiently.
- Looking to **use one language across the stack**. JavaScript on both frontend and backend allows code sharing and simplifies hiring and team training.
- Building **customized architectures**. Node lets you choose only the modules you need and easily create microservices or serverless solutions.
- Working on **I/O bound applications** where fast responses are critical. Node performs well when requests spend time waiting on databases or external services.
## **Django vs Node.js: Cost And Resource Considerations for Web Projects**
Project budgets and infrastructure requirements play a crucial role in selecting the right backend technology. Evaluating the costs and resource needs of Django and Node.js helps teams plan effectively, reduce surprises and allocate budgets wisely.
### **Resource Usage And Hosting Costs**
Django applications generally consume more memory and CPU per instance due to Python’s memory overhead and the synchronous request model. This means servers often need higher specifications. Recent Python improvements have narrowed this gap but hosting costs can still be higher compared to Node.js.
[**Node.js**](/node-js-hosting/) is highly efficient in resource usage. A single Node.js instance can handle thousands of simultaneous connections with minimal memory, making it ideal for high-concurrency applications. This efficiency can reduce hosting expenses, particularly for apps serving many users or running in cloud environments.
### **Development And Staffing Costs**
Development costs usually outweigh hosting costs. Django’s comprehensive tools, built-in features, and structured approach often allow faster development, lowering overall project costs despite higher hosting requirements.
Staffing expenses vary. Python developers with Django expertise often command competitive salaries, while JavaScript developers are more abundant due to the language’s popularity. Skilled Node.js backend developers are in demand, particularly for high-performance or real-time applications.
### **Maintenance And Long-Term Costs**
Django emphasizes **stability and backward compatibility**, reducing long-term maintenance. Applications typically require fewer updates and major refactoring. Long-term support (LTS) releases allow organizations to delay upgrades without compromising security.
Node.js projects need **frequent dependency updates** to maintain security and compatibility. The fast-paced JavaScript ecosystem means packages evolve rapidly, which requires ongoing attention and investment to avoid breaking changes.
### **Infrastructure And DevOps Considerations**
Django often uses traditional deployment setups, such as Gunicorn or uWSGI behind reverse proxies. These models are well-documented and widely supported, making infrastructure management predictable.
Node.js excels in **modern cloud-native architectures**, including containerized or serverless deployments. Its lightweight runtime and fast startup times make it highly scalable, but implementing these solutions requires **DevOps expertise** and infrastructure investment.
## **Get Started with the Right Backend Today**
Django and Node.js both offer powerful features but the key is matching the technology to your project’s needs. Django delivers a structured, secure and feature-rich environment perfect for data-heavy or enterprise applications, while Node.js provides flexibility, high concurrency and real-time capabilities ideal for chat apps, streaming platforms and microservices.
Now that you understand their differences in architecture, performance, security and scalability, it is time to take action. Define your project goals, evaluate your team’s expertise and decide whether Django, Node.js or a hybrid approach best fits your requirements.
If you have found this blog helpful, feel free to [**subscribe to our blogs**](/blog/) for valuable tutorials, guides, knowledge and tips on web hosting and server management. You can also join our [**Facebook community**](https://www.facebook.com/groups/xcloud.community) to share insights and take part in discussions. Do not wait, turn your ideas into reality today. And do not forget to share what you have built. We would love to see your work.
## **Frequently Asked Questions (FAQs) on Django vs Node.js**
**The decision between Django and Node.js** can be challenging due to the many opinions online. This FAQ provides the most common questions developers ask about these two popular backend technologies. It also includes questions often raised in AI and LLM contexts, helping readers make informed choices for 2026 and beyond.
### **1\. Which one is better for 2026, Node.js or Django?**
There is no one-size-fits-all answer. Django is ideal for projects that require **robust data handling, security, and rapid development**, while Node.js excels at **real-time applications, high concurrency, and modern cloud architectures**. The “better” framework depends on your project type, team skills and long-term goals.
### **2\. Should I learn Node.js if I already know Django?**
Yes, learning Node.js can expand your options. Django provides strong **Python-based full-stack development**, while Node.js allows **JavaScript across the frontend and backend**, which is useful for real-time apps and microservices. Knowing both increases your versatility as a developer.
### **3\. Which framework should I learn first: Django or Node.js?**
If you are new to web development and prefer **structured, beginner-friendly frameworks**, Django is a great starting point. If you enjoy **flexible, event-driven architectures** and plan to work with real-time apps, Node.js is a better choice. Your choice also depends on the language you prefer: Python (Django) or JavaScript (Node.js).
### **4\. Is Node.js faster than Django?**
Node.js handles **many concurrent requests efficiently** thanks to its event-driven, non-blocking I/O model. Django, being synchronous by default, may handle fewer simultaneous connections but performs well for **CPU-bound tasks** and data-heavy applications. Speed depends on the type of workload.
### **5\. Which is better for web development: Node.js or Django?**
Django is better for **data-driven websites, enterprise apps, and projects requiring strong security**. Node.js is better for **real-time apps, streaming services, and APIs** that need **high concurrency**. Both frameworks are widely used for web development; the choice depends on your project goals.
### **6\. What Node.js framework is most similar to Django?**
Express.js or Nest.js are commonly compared to Django. **Express.js** is minimal and flexible, while **Nest.js** is more structured and uses decorators and modules similar to Django’s approach, making it easier to implement large-scale applications.
### **7\. Is Django underrated and Node.js overrated?**
Both frameworks have strong use cases. Django may feel less trendy because it is Python-based but it excels in **security, maintainability and rapid development**. Node.js is popular for **real-time and high-concurrency apps** but it requires careful dependency management. Neither is overrated or underrated, they fit different project needs.
### **8\. Should I quit Django and move to Node.js?**
Switching frameworks depends on your goals. If your projects require **real-time applications or microservices**, Node.js might be worth learning. If you are building **data-heavy applications, CMS or enterprise apps**, Django remains a strong choice. Learning Node.js does not mean quitting Django; many developers use both in different projects.
### **9\. Django vs Flask or Node.js: Which should I pick?**
Flask is lightweight and flexible, perfect for small applications or microservices. Django provides a full-stack solution with batteries included, ideal for larger projects. Node.js is suited for real-time apps and high-concurrency workloads. Choose based on **project** size, complexity and preferred language.
### **10\. How do Django and Node.js compare for modern development trends?**
Django remains strong for **enterprise, data-driven and secure applications**. Node.js dominates **real-time applications, microservices, serverless architectures and modern cloud development**. Understanding the differences helps you pick a framework aligned with 2026 trends.
---
# Docker Hosting - xCloud
> Deploy and manage unlimited Docker applications with fully managed Docker Hosting, free SSL, and 24/7 expert support on high-performance VPS infrastructure.
## Docker Hosting
# Simple Docker Hosting Solution To Deploy Any Projects Easily
Run microservices, CI/CD pipelines, and cloud-native apps using Docker Hosting to package applications and dependencies into portable containers with consistent performance across environments.
- 
### 24/7/365 Global Customer Support
## Free SSL Certificate
## **Setup Process**
## Simple Steps To Launch Your Docker Application in Minutes
Deploy and manage Docker projects with a carefully designed, streamlined workflow built for consistent speed, stability, and reliability from development to live production deployment.
### Choose Deployment Method
Select Docker Compose to deploy and manage your Docker projects with a fast and simple setup.
### Configure App Settings
Add your Dockerfile URL or paste the file into the xCloud dashboard with other required settings
### Go Live Right Away
Review your configuration, confirm the setup, and deploy your site to production in just a few clicks.
## Pricing
## Reliable & Secure Docker Hosting at a Price You’ll Love
Get started for free and host unlimited Docker applications on your preferred platform
plans and boost growth with powerful features.
- ###### xCloud Managed Server
- ###### Self-Managed Server
### All
### 1 GB
For Personal Use
### 2 gb
For Basic Websites
### 4 gb
For Growing Websites
### 8 gb
For Busier Websites
### 16 gb
For Bigger, Busier Websites
### 32 gb
For HIGH-PERFORMANCE NEEDS
### 48 gb
For HIGH-PERFORMANCE NEEDS
### 58 gb
For HIGH-PERFORMANCE NEEDS
## Elevate your site with xCloud servers—ensuring speed and security, with no hidden charges in the future.
## Premium servers are powered by High-Frequency 3GHz+ Intel Xeon CPUs, lightning-fast memory, and NVMe storage, delivering unmatched speed and performance. General servers, on the other hand, offer a budget-friendly solution for standard workloads
- ###### All
- ###### 1 GB
- ###### 2gb
- ###### 4gb
- ###### 8GB
- ###### 16gb
- ###### 32gb
- ###### 48GB
- ###### 58GB
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
## Business Max
- ### 64 GB RAM
Ultimate plan for unparalleled power
- ### 1280 GB SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 10 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-max)
## $ **399.00** /mo
## Newcomer
- ### 1 GB RAM
Entry-level plan for new websites
- ### 25 GB SSD
- ### 1 vCPU
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-newcomer)
## $ **5.00** /mo
## Lite
Premium
- ### 1 GB RAM
Lightweight plan for small projects
- ### 32 GB NVMe SSD
- ### 1 vCPU
3GHz+ Intel Xeon CPUs
- ### 1 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-lite)
## $ **7.5** /mo
## Basic
- ### 2 GB RAM
Fundamental plan for growing sites
- ### 55 GB SSD
- ### 1 vCPU
- ### 2 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-basic)
## $ **12.00** /mo
## Personal
Premium
- ### 2 GB RAM
Personalized plan for individual needs
- ### 80 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-personal)
## $ **20.00** /mo
## Standard
- ### 4 GB RAM
Standard plan for business essentials
- ### 80 GB SSD
- ### 2 vCPU
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-standard)
## $ **24.00** /mo
## Growing
Premium
- ### 4 GB RAM
Scalable plan for expanding websites
- ### 128 GB NVMe SSD
- ### 2 vCPU
3GHz+ Intel Xeon CPUs
- ### 3 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-growing)
## $ **30.00** /mo
## Professional
- ### 8 GB RAM
Professional-grade plan for advanced needs
- ### 160 GB SSD
- ### 4 vCPU
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-professional)
## $ **45.00** /mo
## Elite
Premium
- ### 8 GB RAM
Elite plan for high-performance requirements
- ### 256 GB NVMe SSD
- ### 3 vCPU
3GHz+ Intel Xeon CPUs
- ### 4 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-elite)
## $ **50.00** /mo
## Business
- ### 16 GB RAM
Business-focused plan for corporate sites
- ### 320 GB SSD
- ### 6 vCPU
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business)
## $ **88.00** /mo
## Titanium
Premium
- ### 16 GB RAM
Titanium plan for robust enterprise solutions
- ### 384 GB NVMe SSD
- ### 4 vCPU
3GHz+ Intel Xeon CPUs
- ### 5 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-titanium)
## $ **100.00** /mo
## Ultimate
Premium
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 512 GB NVMe SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### 7 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-ultimate)
## $ **200.00** /mo
## Business Plus
- ### 32 GB RAM
Ultimate plan for unparalleled power
- ### 640 GB SSD
- ### 8 vCPU
3GHz+ Intel Xeon CPUs
- ### Bandwidth: 6 TB
- ### Unlimited Sites
[Buy Now](https://xcloud.host/buy/xcloud-business-plus)
## $ **196.00** /mo
## Ultimate PLUS
Premium
- ### 48 GB RAM
Ultimate plan for unparalleled power
- ### 768 GB NVMe SSD
- ### 12 vCPU
3GHz+ Intel Xeon CPUs
- ### 8 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=581)
## $ **310.00** /mo
## Quantum
Premium
- ### 58 GB RAM
Ultimate plan for unparalleled power
- ### 1024 GB NVMe SSD
- ### 16 vCPU
3GHz+ Intel Xeon CPUs
- ### 9 TB Bandwidth
- ### Unlimited Sites
[Buy Now](https://app.xcloud.host/cart/product/checkout?product=583)
## $ **395.00** /mo
## Cloud VPS 6GB
## $24.99
Renews at $24.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=f292a3d0-fbcc-4c23-be7b-67f9cd677c69&stack=docker_nginx)
- ### 6 GB RAM
- ### 100 GB NVMe SSD
- ### 4 vCPU cores
- ### 30TB Bandwidth
## Popular deal
## Cloud VPS 16GB
## $59.99
Renews at $59.99/mo. Cancel anytime.
[Get started](https://app.xcloud.host/cart/product/checkout?product=33a8077d-dedc-4187-967d-b023ae20ed5c&stack=docker_nginx)
- ### 16 GB RAM
- ### 200 GB NVMe SSD
- ### 6 vCPU cores
- ### 30TB Bandwidth
## Cloud VPS 24GB
## $84.99
Renews at $84.99/mo. Cancel anytime.
[Get Started](https://app.xcloud.host/cart/product/checkout?product=b9bc978a-fd8e-4aea-a847-02ad127c9bfb&stack=docker_nginx)
- ### 24 GB RAM
- ### 300 GB NVMe SSD
- ### 8 vCPU cores
- ### 30TB Bandwidth
Monthly
Yearly
MonthlyYearly
## Black Friday Special Deal : One-time Payment – LIFETIME Access!
Bring your own server and unlock access to our cloud control panel to enjoy a seamless server and site management experience for a lifetime.
[Grab Lifetime Deal](/deal/)
## Want to explore xCloud first? Try it out for free and then decide!
[Get started](https://app.xcloud.host/register)
## FREE PLAN
- ### 1 Server
- ### 10 Site
## Start your journey without cost
## Starter
- $5/Server (/month)
- 1-5 Servers
- Unlimited Sites
## Perfect for Beginner
## Professional
- $4/Server (/month)
- 6-10 Servers
- Unlimited Sites
## Tailored for Experts
## Agency
- $3/Server (/month)
- 11+ Servers
- Unlimited Sites
## Perfect for Large Teams
## Features
## Build, Ship, & Scale Any Application with Docker
Docker helps developers build and run applications using containers. Containers bundle everything an application needs into a single, portable package.
- ### Microservices and APIs
- ### SaaS applications
- ### AI & ML workloads
- ### Databases and caching services
- ### Background workers and cron jobs
## Advanced Features
## Deploy Docker on Your VPS for Fast & Secure Performance
Launch Docker on a high-performance VPS with no complicated setup. Everything comes pre-configured so you can deploy in minutes and scale with confidence.
## Fast Provisioning
Quickly provision servers and deploy sites with xCloud Managed Servers, DigitalOcean, Vultr, Linode, AWS, or Any Servers.
## Enterprise-grade security
Protect your infrastructure with a free SSL certificate, AI bot blocking, and advanced security features at no additional cost.
## One Click Deployment
Start building your server infrastructure instantly with a streamlined setup that gets you running in just a few clicks.
## Intuitive Control Panel
From Server creation to application deployment and security settings, everything can be managed with few clicks from our easy-to-use hosting control panel.
## Optimised Setup
Your server is pre-optimized with high-performance stacks like Nginx or OpenLiteSpeed and backed by ultra-fast NVMe SSD storage
## Easy DNS Management
Easily manage your DNS records through our intuitive panel. Also, verify your DNS in just 1 click using Cloudflare integration.
## Testimonials
## Hear What The Users Have To Say
We are delighted with the enthusiastic response from our users. Read some of the great feedback we have received so far!
Massimo Villa
@tlewisverdu
So far my experience has been smooth like silk. I didn’t imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included).
For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation.
I’m sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Waqar Ahmed
@tlewisverdu
**xCloud** isn’t just a solution. It’s like one of that friend who got your back when you screw things up pretty bad.
Tony Lewis
@tlewisverdu
I’ve recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud.
I have to say, I’m really impressed with xCloud so far! The interface is definitely the standout feature for me.
Brian Geovanny
@braingigio
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising.
Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Leo Koo
@leowrites
I’m moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud!
xCloud #wordpress #hosting
Rahul Singh
@tlewisverdu
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahil Maknojia
@rahilmaknojia
Dear xCloud Team,
I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It’s a fantastic service, and my experience so far has been very positive.
Successful migrated 5 sites on a single server. xCloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Dan Spinoza
@tlewisverdu
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
[View More Testimonials](/reviews-and-testimonials/)
## FAQs
## Frequently Asked Questions
Feel free to contact us with any questions or concerns you may have
### What is Docker VPS hosting?
Docker VPS hosting combines the flexibility of Docker containers with the performance of a virtual private server (VPS). It allows developers to deploy and manage multiple isolated applications, with each application running in its own container on a single VPS.
### Can I migrate my existing apps to a Docker VPS?
Yes. Docker lets you package your applications and their dependencies into containers, making it easier to move them between hosting environments, including Docker VPSs. Some configuration may be required to ensure full compatibility.
---
# Docs - xCloud
> Docs Archive - xCloud
## Documentation
# Welcome to xCloud Knowledge Base 👋
## Quick Start
7
- [Quick Start Guide: Setup Your First Server & Site With xCloud Managed Servers](/docs/setup-your-first-server-site-with-xcloud/)
- [How To Setup DNS Record In xCloud?](/docs/how-to-setup-dns-record-in-xcloud-server/)
- [Quick Start Guide: How To Create A Site With xCloud](/docs/how-to-create-a-site-with-xcloud/)
- [How to Create a Demo Site in xCloud?](/docs/create-a-demo-site-in-xcloud/)
- [Simplified Navigation For Your Servers And Sites In xCloud Dashboard](/docs/simplified-navigation-for-servers-and-sites/)
- [Complete Guide to WordPress Site Migration on xCloud](/docs/guide-to-wordpress-site-migration-on-xcloud/)
[Explore More](https://xcloud.host/docs-category/quick-start/)
## Servers
63
- [How To Upgrade Your Server in xCloud?](/docs/how-to-upgrade-your-server-in-xcloud/)
- [How To Setup A Vultr Server in xCloud and Get Free Hosting For 6 Months?](/docs/how-to-get-free-hosting-with-vultr/)
- [How to Setup a Digital Ocean Server in xCloud?](/docs/how-to-setup-your-server-with-digital-ocean/)
- [How To Setup a GCP(Google Cloud Platform) Server in xCloud?](/docs/first-server-with-google-cloud-platform/)
- [How To Connect Existing Fresh Ubuntu Server On xCloud From Any Provider?](/docs/how-to-set-up-server-with-other-providers/)
- [How To Manage Your Server Utilities With xCloud?](/docs/how-to-manage-your-server-utilities-with-xcloud/)
[Explore More](https://xcloud.host/docs-category/servers/)
## Sites
78
- [Setting Up Site Emails With Any SMTP Provider For WordPress On xCloud](/docs/setting-up-site-emails-for-wordpress-on-xcloud/)
- [Integrate Cloudflare for DNS Management with xCloud](/docs/using-xcloud-with-cloudflare-for-dns-management/)
- [How To Go Live From Staging Domain?](/docs/how-to-go-live-from-staging-domain/)
- [How To Easily Install Let’s Encrypt SSL Certificate](/docs/install-lets-encrypt-ssl-certificate/)
- [How To Configure SFTP Access For Your Site](/docs/how-to-configure-sftp-access/)
- [How To Manage And Update WordPress Core, Themes, & Plugins In xCloud?](/docs/manage-and-update-wordpress-core-themes-in-xcloud/)
[Explore More](https://xcloud.host/docs-category/sites/)
## Accounts
11
- [How Pricing Plans And Billing Works In xCloud](/docs/how-billing-works-in-xcloud/)
- [Team Roles & Permissions in xCloud](/docs/team-roles-permissions-in-xcloud/)
- [How To Generate Custom Invoices in xCloud?](/docs/how-to-generate-custom-invoices/)
- [Protecting Our System With Security and Vulnerability Disclosure Protocols](/docs/security-and-vulnerability-disclosure-protocols/)
- [How to Change the Language for xCloud Hosting Panel?](/docs/change-the-language-for-xcloud-hosting-panel/)
- [How to Change Language for Reseller xCloud Hosting Panel?](/docs/change-language-for-reseller-xcloud-hosting/)
[Explore More](https://xcloud.host/docs-category/accounts/)
## FAQ
41
- [How Many Sites Can Be Hosted Efficiently On A Single Server?](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
- [Do You Provide Root Access To My Servers?](/docs/provide-root-access/)
- [How long is the trial period supposed to be?](/docs/how-long-is-the-trial-period-supposed-to-be/)
- [When will I be charged?](/docs/when-will-i-be-charged/)
- [Do you offer backups in xCloud?](/docs/backups-in-xcloud/)
- [An Overview of xCloud White-label Feature](/docs/overview-xcloud-white-label-feature/)
[Explore More](https://xcloud.host/docs-category/faq/)
## Migration
12
- [How To Perform A Full Server Migration With xCloud?(WordPress Sites)](/docs/perform-a-full-server-migration-with-xcloud/)
- [How To Migrate An Existing WordPress Website In xCloud?](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
- [How To Manually Upload WordPress Websites On xCloud](/docs/how-to-manually-upload-wordpress-websites/)
- [How To Clone A Website From Git Repository With xCloud](/docs/clone-a-website-from-git-repository-with-xcloud/)
- [How To Easily Migrate A Website With Migrate Guru Plugin In xCloud?](/docs/migrate-a-website-with-migrate-guru-plugin/)
- [How To Perform Full Server Migration Between xCloud Servers Effortlessly?](/docs/full-server-migration-between-xcloud-servers/)
[Explore More](https://xcloud.host/docs-category/migration/)
## Troubleshooting
22
- [How To Solve The ‘WordPress Memory Limit Exhausted’ Error?](/docs/wordpress-memory-limit-exhausted-error/)
- [How To Solve Automatic Site Backup Failures?](/docs/how-to-solve-automatic-site-backup-failures/)
- [How to Troubleshoot Server Installation Failed (xCloud & Self-managed)](/docs/how-to-troubleshoot-server-installation-failed-xcloud-self-managed/)
- [How To Fix Failed Free SSL Issue in xCloud](/docs/how-to-fix-a-failed-free-ssl-issue/)
- [How To Fix WordPress Updates Not Working Issue](/docs/how-to-fix-wordpress-updates-not-working-issue/)
- [Server Gets Disconnected](/docs/server-gets-disconnected/)
[Explore More](https://xcloud.host/docs-category/troubleshooting/)
## Cache
5
- [How to Integrate Object Cache Pro with xCloud? \[Easy Guide\]](/docs/integrate-object-cache-pro-with-xcloud/)
- [How to Enable the Edge Full Page Cache in xCloud](/docs/enable-the-edge-full-page-cache/)
- [How to Control OPcache With xCloud](/docs/control-opcache-with-xcloud/)
- [How to Enable Redis Object Cache Plugin With OpenLiteSpeed](/docs/enable-redis-object-cache-plugin-with-ols/)
- [How To Allow Caching Of A URL With A Query String](/docs/how-to-allow-caching-of-a-url-with-a-query-string/)
## Integrations
6
- [How to Configure Slack Integration in xCloud Hosting?](/docs/configure-slack-integration-in-xcloud/)
- [How to Configure Integration with WhatsApp In xCloud Hosting?](/docs/how-to-configure-integration-with-whatsapp/)
- [How to Configure Integration with Telegram in xCloud Hosting?](/docs/configure-integration-with-telegram-in-xcloud/)
- [How to Integrate Google Drive for Site Backup in xCloud?](/docs/google-drive-for-site-backup-xcloud/)
- [How to Integrate Wasabi Storage Provider for Site Backup with xCloud?](/docs/integrate-wasabi-storage-provider-with-xcloud/)
- [How to Set Up Hide My WP plugin in xCloud?](/docs/how-to-set-up-hide-my-wp-plugin-on-xcloud/)
## Security
22
- [Enhancing Server and Website Security with xCloud](/docs/server-and-website-security-with-xcloud/)
- [Protecting Our System With Security and Vulnerability Disclosure Protocols](/docs/security-and-vulnerability-disclosure-protocols/)
- [How To Use xCloud 7G Firewall On Nginx](/docs/use-xcloud-7g-firewall-on-nginx/)
- [How To Easily Configure Firewall Management With xCloud Hosting](/docs/how-to-configure-firewall-management-in-xcloud/)
- [Fail2Ban in xCloud: Enhancing Server Security With Ease](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
- [How to Detect & Fix Security Bugs with Vulnerability Checker in xCloud?](/docs/vulnerability-checker-in-xcloud/)
[Explore More](https://xcloud.host/docs-category/security/)
## Backup
13
- [Site Backups In xCloud](/docs/site-backups-in-xcloud/)
- [How To Solve Automatic Site Backup Failures?](/docs/how-to-solve-automatic-site-backup-failures/)
- [How To Configure Server Backup Management In xCloud?](/docs/configure-server-backup-management/)
- [Optimal Backup Practices For xCloud Hosting Users](/docs/optimal-backup-practices-xcloud/)
- [How to Use Cloudflare R2 Storage for Site Backup in xCloud?](/docs/cloudflare-r2-storage-for-site-backup/)
- [How To Take Incremental Backup In xCloud?](/docs/incremental-backup-in-xcloud/)
[Explore More](https://xcloud.host/docs-category/backup/)
## White Label
11
- [How to Setup Your Reseller Account with xCloud White Label](/docs/setup-reseller-account-with-xcloud-white-label/)
- [How to Customize Reseller Landing Page in xCloud](/docs/customize-reseller-landing-page-in-xcloud/)
- [How to Collect Stripe Publishable Key for 3D Secure Card Payments?](/docs/collect-stripe-publishable-key/)
- [How Billing Works in xCloud White Label Program or Reseller Hosting Program](/docs/how-billing-works-in-xcloud-white-label-program/)
- [How to Set Up Custom SMTP for Branded Emails in xCloud White Label](/docs/custom-smtp-provider-with-xcloud-white-label/)
- [How to Create a Custom Sales Landing Page for xCloud White Label](/docs/how-to-create-a-custom-sales-landing-page-for-xcloud-white-label/)
[Explore More](https://xcloud.host/docs-category/white-label/)
## Laravel
6
- [How to Deploy Laravel Applications with xCloud?](/docs/deploy-laravel-applications/)
- [How to Set Up a Queue Worker for Laravel Applications](/docs/set-up-queue-worker-for-laravel-applications/)
- [How to Set Up Laravel Horizon with xCloud](/docs/set-up-laravel-horizon/)
- [How to Use Supervisor for Process Management With xCloud](/docs/supervisor-for-process-management/)
- [How to Set Up Laravel on DigitalOcean Server with xCloud?](/docs/how-to-set-up-laravel-on-digitalocean-server/)
- [How to Clone a Laravel App with xCloud](/docs/how-to-clone-a-laravel-app-with-xcloud/)
## One Click Apps & Node.js
17
- [How to Deploy phpMyAdmin with xCloud One Click Apps](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
- [How to Deploy Uptime Kuma with xCloud One Click Apps](/docs/deploy-uptime-kuma-with-xcloud/)
- [How to Change Node Version with xCloud](/docs/how-to-change-node-version-with-xcloud/)
- [How to Deploy n8n with xCloud with One Click Apps](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
- [How to Reset Uptime Kuma Password via CLI with xCloud](/docs/how-to-reset-uptime-kuma-password/)
- [How to Set Up SMTP for n8n with Environment in xCloud](/docs/how-to-set-up-smtp-for-n8n-with-environment/)
[Explore More](https://xcloud.host/docs-category/one-click-apps/)
## MailBox Addon
11
- [How to Set up Site Security PRO with xCloud](/docs/set-up-site-security-pro/)
- [How to Set Up xCloud MailBox Addon](/docs/how-to-set-up-xcloud-mailbox-addon/)
- [How to Configure Your Email Client with xCloud Mailbox Addon](/docs/configure-email-client-with-mailbox-addon-xcloud/)
- [How to Configure a Business Mail account on Phone Using Gmail](/docs/how-to-configure-a-business-mail-account-on-phone-using-gmail/)
- [How to Configure a Business Mail account on Apple Mail](/docs/configure-a-business-mail-account-on-apple-mail/)
- [How to Configure a Business Mail account on Gmail](/docs/configure-a-business-mail-account-on-gmail/)
[Explore More](https://xcloud.host/docs-category/mailbox-addon/)
## Addons
4
- [How to Set Up xCloud Mail Delivery Addon For Your Site](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
- [How to Set up Site Security PRO with xCloud](/docs/set-up-site-security-pro/)
- [How to Set Up xCloud MailBox Addon](/docs/how-to-set-up-xcloud-mailbox-addon/)
- [How to Activate the Cloudflare Enterprise Addon on Your Domain](/docs/how-to-activate-the-cloudflare-enterprise-addon/)
## API Documentations
2
- [How to Access the xCloud API](/docs/how-to-access-the-xcloud-api/)
- [xCloud API Documentations](/docs/xcloud-api/)
---
# 31 Server Locations WorldWide - xCloud
> Server Location Table ContinentLocationCountryNorth AmericaTorontoCanadaNorth AmericaMexico CityMexicoNorth AmericaAtlantaUnited StatesNorth
### Server Location Table [#](/docs/31-server-locations-worldwide/)
Continent
Location
Country
North America
Toronto
Canada
North America
Mexico City
Mexico
North America
Atlanta
United States
North America
Honolulu
United States
North America
Chicago
United States
North America
Dallas
United States
North America
Los Angeles
United States
North America
Miami
United States
North America
New York Area
United States
North America
San Francisco Bay Area
United States
North America
Seattle
United States
Africa
Johannesburg
South Africa
South America
Santiago
Chile
Europe
Warsaw
Poland
Europe
Amsterdam
Netherlands
Europe
London
United Kingdom
Europe
Frankfurt
Germany
Europe
Paris
France
Europe
Madrid
Spain
Europe
Stockholm
Sweden
Europe
Manchester
United Kingdom
Asia
Tokyo
Japan
Asia
Seoul
Republic of Korea
Asia
Singapore
Singapore
Asia
Bangalore
India
Asia
Mumbai
India
Asia
Delhi NCR
India
Asia
Tel Aviv-Yafo
Israel
Asia
Osaka
Japan
Australia
Sydney
Australia
Australia
Melbourne
Australia
---
# How to Access Built-in Support Portal in xCloud - xCloud
> Learn how to use the new Support Portal in xCloud to create tickets, track issues, and manage communication with the support team in one place.
xCloud’s new Support Portal makes it easier for you to manage and track your technical issues. Unlike the previous portal, the new system gives you a single dashboard to view tickets, create new ones, and communicate directly with the support team.
This new Support Portal helps you save time, reduce confusion, and manage your support activity in one central place. Let’s learn how to use the new xCloud support portal, follow updates, and keep all your support activity organized in one place.
## **How to Access Previous Support Tickets** [#](/docs/access-built-in-support-portal-in-xcloud/)
We have moved to our new, built-in [**xCloud Support Portal**](https://app.xcloud.host/support/all-tickets) to make the process faster and easier for you. In the old portal, you can no longer create any new support tickets. You can still reply to your existing tickets and view them.
To access your old tickets, click on the [**Support Portal**](https://app.xcloud.host/support/all-tickets) link. Once there, you will be able to see your previous tickets and continue conversations if needed. For all new issues, you must now use the new dashboard to create support tickets.
## **Step 1: Accessing the Support Portal** [#](/docs/access-built-in-support-portal-in-xcloud/)
To access the support portal, go to the top menu and select the **‘Support’** option. Once you click it, you will be redirected to the **‘All Tickets’** page.
On this page, you will see an overview of your tickets, including **‘Total Tickets’**, **‘Open Tickets’**, and **‘Closed Tickets’**. This section gives you a quick view of your overall ticket activity.
## **Step 2: Viewing Ticket Details** [#](/docs/access-built-in-support-portal-in-xcloud/)
To make navigation easier, you can filter tickets using different options such as **‘Shows’**, **‘Status’**, **‘All Status’**, **‘Sort By’**, and **‘Sort Type’** which allows you to organize tickets in either ascending or descending order. There is also a **‘Search’** field that allows you to quickly find tickets based on your preferences.
In the **‘Total Tickets’** section, you can view the important information about each ticket. This includes the **‘Ticket Details’**, the **‘User’** who created it, the current **‘Status’**, the related **‘Server’**, the **‘Sites’**, and the available **‘Action’** options. From here, you can check any tickets by clicking on the **‘View’** button.
## **Step 3: Creating a Ticket** [#](/docs/access-built-in-support-portal-in-xcloud/)
If you want to create a new ticket, you can click on the **‘Create Ticket’** button located at the top of the dashboard or use the same option from the sidebar. Once there, you need to select the **‘Team’** from the dropdown list and provide the **‘Subject’** of your ticket in the designated field.
After that, choose the most suitable **‘Topic’, ‘Category’** for the issue and set its **‘Priority’** level. You should then provide a brief but clear explanation in the **‘Descriptions’** field so the support team understands the problem.
In addition to text, you can upload supporting files in the **‘Attachments’** section. These can include screenshots, GIFs, or documents that make the issue clearer. In the **‘Additional Information’** section, you can specify the related **‘Server’** or **‘Site’** that is connected to the issue. Give related permission to the support team by checking the boxes in. Once all the required fields are completed, click on the **‘Create Ticket’** button to submit it.
## **Step 5: After Ticket Creation** [#](/docs/access-built-in-support-portal-in-xcloud/)
Once your ticket is created, it will appear instantly in the system. You will be able to see replies from the xCloud support team whenever they respond. You can also continue the conversation by replying to the ticket, making it easy to track the progress of your request.
## **Give Role Permission to Team Member** [#](/docs/access-built-in-support-portal-in-xcloud/)
If you want to give one of your team members access to the xCloud Support portal and allow them to manage tickets, go to the team settings. Change the role, scroll to the end of the role permissions dashboard, and find the Support option. Then, assign the permissions according to your preference.
The xCloud Support Portal is designed to make support easier and more efficient for you. By using the options to view, filter, and create tickets, you can clearly present your issues and get timely assistance.
Once your ticket is created, you can follow up and respond just like a conversation, ensuring smooth communication until your issue is resolved.
## **Frequently Asked Questions** [#](/docs/access-built-in-support-portal-in-xcloud/)
**1\. How can I view my old tickets?**You can view your old tickets by visiting the previous support portal. In the old portal, you cannot create new tickets, but you can still open existing ones and continue conversations with the support team.
**2\. Where can I create new tickets?**You can create new tickets only in the new xCloud Support Portal. Use the ‘Create Ticket’ button on the dashboard or sidebar to submit a new issue.
**3\. Can I migrate old tickets to the new portal?**Yes, you can. To migrate old tickets to the new support portal, contact the support team. They will help you move your old tickets into the new system.
**4\. Can I provide access to my team members to see my tickets and manage them?
**Yes, you can provide access to your team members so they can view and manage your tickets.
Still stuck? Contact our [**support team**](https://app.xcloud.host/support/all-tickets) for any of your queries.
---
# How to Access OpenLiteSpeed Webadmin in xCloud - xCloud
> Learn how to enable and access OpenLiteSpeed webadmin in xCloud for secure server monitoring.
By default, the OpenLiteSpeed webadmin console is disabled in xCloud. This is done to improve security. However, you can enable it if you need to monitor your server or view its configurations.
To do this, you need to follow a few steps. These steps involve using the command line, updating your firewall settings, and restarting the web server. You will also need some basic access and permissions before you begin.
## **Prerequisites** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
To proceed, you must have sudo or root access to your server. This is necessary to run certain commands. You also need access to the xCloud dashboard. This allows you to manage firewall settings and restart services on your server.
## **Steps to Enable the OpenLiteSpeed Webadmin** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
To enable the webadmin console, follow these four steps.
### **Step 1: Enable the Web Console via Command Line** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
To start, connect to your server using SSH. After logging in, run a command to remove a specific file. This file is what disables the web admin by default. You can delete it by typing the following command:
**sudo rm /usr/local/lsws/conf/disablewebconsole**
When you remove this file, the web console will become active.
### **Step 2: Open Port 7080 in the Firewall** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
The OLS webadmin operates on port 7080. Make sure this port is open. Go to your server dashboard, choose **‘Security’ → ‘Firewall Management’**. Here you can find **‘Add new rule’** to button to create a new rule to allow incoming traffic on TCP port 7080.
If you are using another cloud provider like AWS, Google Cloud, Azure, or DigitalOcean, you will also need to open port 7080 in their security groups or external firewalls.
### **Step 3: Restart OpenLiteSpeed** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
After opening the port, restart the OpenLiteSpeed service to apply the changes. To do this, go to your xCloud dashboard. Click on **‘Server Management’** and then choose **‘Settings.’** Look for the section where you can manage services. Find OpenLiteSpeed in the list and click the **‘Reboot’** button.
### **Step 4: Access the Webadmin Console** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
Once the service restarts, you can access the OpenLiteSpeed webadmin in your browser. Enter the following URL:
[**http://your\_server\_ip:7080**](http://your_server_ip:7080)
Replace your\_server\_ip with the actual IP address of your server. You should now see the OpenLiteSpeed login page in your browser.
## **Important Note: Read-Only Mode** [#](/docs/access-openlitespeed-webadmin-in-xcloud/)
The OpenLiteSpeed webadmin in xCloud only works in read-only mode. This means you can use it to view server configurations, monitor the system, and check statistics. However, you cannot make or save any changes using the webadmin console.
If you want to update configurations or apply changes, you must use the xCloud dashboard. All configuration management should be handled through that panel.
This guide helps you enable and use the OpenLiteSpeed webadmin in xCloud. Use it when you need to monitor your server without making changes directly through the web interface.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Access Site Database Using Adminer In xCloud - xCloud
> Access site database using Adminer in xCloud effortlessly. Enable, launch, and manage your WordPress database securely with our step-by-step guide
Your website’s database is stored on a server. If you want to access and manage the database manually with enhanced security, you need a third-party database management tool such as **[TablePlus](https://tableplus.com/)** using an SSH connection. However, **[xCloud](/)** offers a simpler method to access site databases using Adminer without a manual database connection. Although an SSH connection guarantees more security, we suggest enabling Adminer only when you find it necessary.
## **Understanding Adminer For Database Management In xCloud** [#](/docs/access-site-database-using-adminer-xcloud/)
**Adminer** is a PHP-based lightweight database administration tool. It provides users with a web-based interface for managing databases, running SQL queries, and doing other database-related operations. With a single file deployment, Adminer offers a simple alternative to more complicated database administration systems such as phpMyAdmin.
Follow the guide below to learn how to access site database using Adminer in xCloud.
## **Enable Adminer In xCloud** [#](/docs/access-site-database-using-adminer-xcloud/)
Log in to your xCloud dashboard and navigate to **Access Details → Database**. The Adminer is disabled by default.
Toggle the ‘Enable Adminer’ button to enable it, and hit the ‘Launch Adminer’ button to open the Adminer dashboard.
## **Manage Database In Adminer** [#](/docs/access-site-database-using-adminer-xcloud/)
After enabling and launching the Adminer from your xCloud dashboard, you can now easily manage your database, including running SQL commands, importing or exporting data, creating tables, and more.
### **Run SQL Command** [#](/docs/access-site-database-using-adminer-xcloud/)
From the Adminer dashboard, you can easily run **CRUD** commands.
### **Import/Export SQL Files** [#](/docs/access-site-database-using-adminer-xcloud/)
You can quickly import your existing database with a single click.
You can also export your database and select output options, format, database type, and choose tables and data, and more in a few clicks.
That’s how easy it is to manage databases using Adminer in xCloud.
## **Access Site Database Using Adminer In xCloud** [#](/docs/access-site-database-using-adminer-xcloud/)
You must ensure you have access to your website’s site management database as a team member. If you do not have that, please ask your team’s administrator to enable access in the ‘**Team Management**’ section from your dashboard. However, if you are the Team Admin, you have this access by default.
Still stuck? Contact our support team for any of your queries.
---
# How to Access the Web Terminal from xCloud Dashboard - xCloud
> Access and manage your servers directly from the xCloud dashboard with the built-in Web Terminal. Open secure root, sudo or site-level terminal sessions instantly from your browser.
[**xCloud**](/) helps you open a fully functional command-line web terminal for your servers and sites directly inside the dashboard, right from your web browser. Instead of configuring an SSH client, copying key files and connecting manually, you can launch a secure terminal session with a single click and start running commands straight away.
## **Why Use the Built-in Terminal?** [#](/docs/access-web-terminal-in-xcloud/)
Traditionally, accessing a server through the command line means setting up an SSH connection, managing private keys, and remembering host details, a process that can be slow and error-prone, especially for teams. xCloud removes that friction by bringing the terminal into the dashboard itself.
**With the built-in terminal you can:**
- **Connect Instantly:** Open a live terminal in your browser without any local SSH setup or key management.
- **Choose the Right Access Level:** Open a Server terminal as the root user, as a specific Sudo user or scope a terminal to an individual Site.
- **Control Access with Permissions:** Decide exactly which team members can use each type of terminal through role-based permissions.
- **Work Faster And Safer:** Run scripts, check logs and troubleshoot in real time from anywhere, on any device.
Follow the guide below to enable the necessary permissions and access each type of terminal through a step-by-step process.
### **Step 01: Set the Required Role Permissions** [#](/docs/access-web-terminal-in-xcloud/)
Before anyone can open a terminal, the correct permissions must be enabled for their role. From your xCloud dashboard, open the team member’s Role Permission page and make sure the relevant terminal permissions are switched on under the Server and Site sections.
From the left sidebar, click **‘All Team’**. Navigate to the team member you want to manage, then click **‘Change Role’** to access the role permission settings and make the necessary changes. In the Server and Site sections, enable the permissions that match the access each user needs:
**Navigate:** Dashboard → All Team → Change Role → Role Permission
**Enable the permissions that match the access each user needs:**
- **Server:terminal-root** → Allows opening the Server terminal as the root user.
- **Server:terminal-sudo** → Allows opening the Server terminal as a Sudo user.
- **Site:terminal** → Allows opening a terminal scoped to a specific Site.
**Note:** If a user does not see the **‘Open Terminal’** option, it usually means the matching permission above has not been enabled for their role.
### **Step 02: Open the Web Terminal as Root** [#](/docs/access-web-terminal-in-xcloud/)
Root access gives you full administrative control over the entire server. From the left menu, go to Servers and select the server you want to manage. On the server overview screen, click the **‘Open Terminal’** button in the top-right corner.
From the left sidebar, click **‘Servers’**. Select the server you want to manage to open its overview screen. In the top-right corner, click **‘Open Terminal’**.
**Navigate:** Dashboard → Servers → Select Your Server → Open Terminal
A secure terminal session opens in your browser, connected to the server as the root user. **Use this when you need to:**
- Perform server-wide configuration or maintenance tasks.
- Install software or manage services that require root privileges.
- Inspect system-level logs and processes across the whole server.
**Note:** Because root has unrestricted access, reserve it for tasks that genuinely require it and rely on Sudo users for routine work.
### **Step 03: Open the Web Terminal as a Sudo User** [#](/docs/access-web-terminal-in-xcloud/)
A Sudo user has elevated server access for administrative tasks while maintaining controlled permissions.
To view Sudo users, select your server, open **‘Management’** from the left menu and click **‘Sudo Users’**. You will see a list of all Sudo users available on that server.
**Navigate:** Servers → Select Your Server → Management → Sudo Users → Terminal Icon
Find the user you want to use, then in the Actions column click the terminal icon to launch a session as that Sudo user.
- Each terminal runs with the permissions of the chosen Sudo user.
- Ideal for delegating server access to team members without sharing root.
- You can manage these accounts any time using **‘+ Add Sudo User’** on the same page.
### **Step 04: Open the Site Web Terminal** [#](/docs/access-web-terminal-in-xcloud/)
A site web terminal is scoped to a single website, so you can work within that site’s environment without affecting the rest of the server.
From the left menu, go to **‘Sites’** and select the site you want to manage. On the Site Overview screen, click the **‘Open Terminal’** button in the top-right corner.
**Navigate:** Dashboard → Sites → Select Your Site → Open Terminal
The terminal opens in the context of that specific site, **which is perfect for:**
- Running WP-CLI or site-specific commands.
- Managing files and folders inside the site directory.
- Debugging or maintaining one site without touching others on the server.
### **Step 5: Start Working in Your Terminal** [#](/docs/access-web-terminal-in-xcloud/)
Whichever option you choose, xCloud opens a live, secure terminal session in your browser. A welcome banner confirms the connection for example, _Terminal root @ DevSquad_ with a **Connected** status in the top-right and shows your server’s system information before handing you the command prompt.
**From here you’re ready to work just as you would over SSH:**
- Confirm the session details at the top, including the user you’re connected as (such as **root**) and the server name.
- Review the system summary, such as: operating system, system load, disk and memory usage, IP address, and pending updates to get a quick health check at a glance.
- Type your commands at the prompt to manage your server or site in real time.
- When you’re finished, type **exit** to close the session. Note the idle timeout (15 minutes) automatically ends inactive sessions to keep your server secure.
**Note:** You can copy the terminal’s URL and open the session in a separate browser tab. The terminal stays accessible from that link until you exit the session, handy for keeping a terminal open alongside the rest of your dashboard. Once you type exit, the link is closed and a new session must be opened from the dashboard.
That’s It! You can now open a terminal for your servers and sites directly from the xCloud dashboard as root, as a Sudo user or scoped to a single site without ever leaving your browser. Choose the access level that fits the task and you are ready to manage everything in real time.
Still need a hand? Our support team is always happy to help. If you have any questions, feel free to reach out to our [**Support Team**](/support/) or explore more guides in the [**xCloud Documentation**](https://xcloud.host/docs/).
---
# How to Access WordPress Files in xCloud By Tiny File Manager? - xCloud
> Learn how to access WordPress files in xCloud using Tiny File Manager with this step-by-step guide.
With Tiny File Manager in **[xCloud](/)**, you can manage app files right from the dashboard. It lets you do things like creating new files and folders, compressing, extracting, deleting, moving, copying, editing, and renaming files, just like any other file manager.
If you want to access your site’s files we recommend doing it manually by [**sFTP connection**](/docs/how-to-configure-sftp-access/) and using tools like FileZilla. We suggest enabling Tiny File Manager only when you find it necessary.
Let’s see how to access WordPress files through Tiny File Manager in xCloud & perform your file manager tasks.
## **Access WordPress Files in xCloud by** **Enabling Tiny File Manager in xCloud** [#](/docs/access-wordpress-files-in-xcloud/)
Log in to your xCloud dashboard and navigate to **Access Details → File Manager** under Sites. The Tiny File Manager is disabled by default.
Toggle the **‘Enable File Manager’** button to enable it, and hit the **‘Launch File Manager’** button. This will open the File Manager on a new tab.
That’s how easy it is to access and manage WordPress files directly from the xCloud dashboard using Tiny File Manager.
_**Note:**_ You must ensure you have access to your website’s **‘manage-file- manager’** as a team member. If you do not have that, please ask your team’s administrator to enable access in the **‘Team Management’** section from your dashboard. However, if you are the Team Admin, you have this access by default.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# Accessing All Site Files via SFTP with Root User in xCloud - xCloud
> In xCloud, each site runs under a separate system user (called a site user) for improved security and separation. However, to access all site files across the
In xCloud, each site runs under a separate system user (called a **site user**) for improved security and separation. However, to access all site files across the server via SFTP (e.g. using FileZilla, Transmit, or Cyberduck), you can use the **root user with sudo privileges**. Follow the steps below:
### Step 1: Collect the Sudo Password for the Root User [#](/docs/accessing-all-site-files-via-sftp-with-root-user-in-xcloud/)
When your server is first created in xCloud, you’ll receive a welcome email with the root user’s sudo credentials.
📩 Look for:
- **User**: `root`
- **Sudo Password**: (available in the email)
Example:
```
User: root
Sudo Password: CSehTu5E1ab9ZXRn...
```
Copy to Clipboard
📌 **Keep this safe** – it’s needed for both SSH and SFTP access.
* * *
### Step 2: Confirm or Add `root` as a Sudo User (if needed) [#](/docs/accessing-all-site-files-via-sftp-with-root-user-in-xcloud/)
To verify or add `root` as a sudo user:
1. Go to your server dashboard in xCloud.
2. Navigate to `Management` → `Sudo Users`.
3. If not already present, add a new sudo user:
- **Username**: `root`
- **Password**: (use the one from the welcome email or set a new one)
- Attach your SSH key
📘 Detailed Doc: [Using Sudo and Site Users in xCloud](/docs/usudo-users-and-site-users-in-xcloud/)
* * *
### Step 3: Connect via SFTP [#](/docs/accessing-all-site-files-via-sftp-with-root-user-in-xcloud/)
Use any SFTP client such as FileZilla, Cyberduck, or Transmit.
**Connection Details:**
- **Protocol**: `SFTP`
- **Address**: Your server’s IP
- **Username**: `root`
- **Authentication**: SSH Key or Password (from email)
- **Remote Path**: `/var/www/`
(This is where all your site directories are located)
🔎 Example in Transmit:
```
Protocol: SFTP
Address: 192.168.0.1
User Name: root
Key: id_rsa (or enter password manually)
Remote Path: /var/www/
```
Copy to Clipboard
* * *
### Syncing the Password (Optional) [#](/docs/accessing-all-site-files-via-sftp-with-root-user-in-xcloud/)
You can use the same **sudo password** as the one provided in the setup email for consistency, or set a different password when creating the sudo user in xCloud’s panel.
### Important Notes [#](/docs/accessing-all-site-files-via-sftp-with-root-user-in-xcloud/)
- Avoid using the root user for regular uploads unless necessary.
- For site-specific access, always use the **site user** auto-created by xCloud.
- Misuse of the root user can impact all sites – use carefully.
Let us know via support if you need help connecting or setting it up!
---
# How To Add A Custom Cron Job In xCloud? - xCloud
> Add a custom cron job in xCloud by following the step-by-step guide & execute specific tasks at predefined intervals.
Custom cron jobs are like personal assistants for your website, executing specific tasks at predefined intervals. Whether it’s updating content, sending out emails, or performing maintenance, custom cronjobs tailor automation to your unique needs, saving time and ensuring efficiency in your online operations.
In [**xCloud**](/), adding a custom cron job is a straightforward process that can be done directly from the xCloud dashboard. Let’s see the complete guide on how to add a custom cron job in xCloud.
## **Add A Custom Cron Job In xCloud: Step-By-Step Guide** [#](/docs/add-a-custom-cron-job-in-xcloud/)
Simply follow the below steps to add a custom cron job in xCloud to manage & execute specific tasks at a predefined timeframe.
### **Step 1: Login To Your Hosting Panel** [#](/docs/add-a-custom-cron-job-in-xcloud/)
With the right credentials, log in to your xCloud dashboard.
### **Step 2: Locate The Cron Job Settings** [#](/docs/add-a-custom-cron-job-in-xcloud/)
From your xCloud dashboard, navigate to **‘All Servers’**, click on any server (if you have many), & get the Cron Jobs on the left sidebar of your server dashboard.
### **Step 3: Create a New Cron Job** [#](/docs/add-a-custom-cron-job-in-xcloud/)
To create a new cron job, click on the **‘Add Cron Job’** on the following page. It will redirect you to the next of adding a custom cron job in xCloud.
### **Step 4: Specify The Schedule** [#](/docs/add-a-custom-cron-job-in-xcloud/)
On the resulting page, execute the command, set the user, & determine the frequency of the cron job using the provided drop-down menu with predefined values.
In the ‘**User**‘ field, you can set both the root user & non root (site user, sudo user) user.
**Note:** If you want to execute WP-CLI command, you need to make it with site users.
After choosing the type of script to run (PHP, curl, or wget) and specifying the command to execute. Once all this is done, click on **‘Save’** to save your configuration.
Moreover, you can set a custom schedule too. To do so, click on the **‘Custom’** option as shown below & set the **‘Custom Schedule.’** With the below syntax in **‘Custom Schedule’,** you can create any scheduling need.
**1\* \* \* \* \* /path/to/script.sh 2\* \* \* \* \* command**
In the above command, the 5 asterisk signs allow you to control minutes, hours, days, months, and days of weeks. The range includes:
- Minute (Range: 0 to 59)
- Hour (Range: 0 to 23)
- Day of month (Range: 1 to 31)
- Month (Range: 1 to 12)
- Day of week (Range: 0 to 6, Sunday will count as 0)
### **Step 5: Save The Cron Job & See The Output** [#](/docs/add-a-custom-cron-job-in-xcloud/)
Once everything is configured, your cron job will be listed under the Basic tab in xCloud.
## Add A Custom Cron Job For Your Site: Step-By-Step Guide [#](/docs/add-a-custom-cron-job-in-xcloud/)
Follow the steps below to add a custom cron job in xCloud and run specific tasks at a scheduled time on your site.
From the xCloud dashboard, open your site dashboard and navigate to Tools → Cron Jobs from the sidebar. Click Add New Cron Job to create a new cron job. This will take you to the configuration page where you can set it up.
In the Command field, enter the command you want to run.
Common examples:
```
# Run Laravel task scheduler
php artisan schedule:run
# Run a WP-CLI command (must specify the site path)
cd /var/www/yoursite && wp cron event run --due-now
# Fetch a URL (useful for WordPress cron via wget)
wget -q -O - https://yourdomain.com/wp-cron.php?doing_wp_cron
# Run a custom PHP script
php /var/www/yoursite/scripts/cleanup.php
```
Copy to Clipboard
Next, select how often the cron job should run using the Frequency radio buttons:
Frequency
Cron Expression
Description
Every Minute
\* \* \* \* \*
Runs once per minute
Hourly
0 \* \* \* \*
Runs at the start of every hour
Daily
0 0 \* \* \*
Runs once per day at midnight
Weekly
0 0 \* \* 0
Runs every Sunday at midnight
Monthly
0 0 1 \* \*
Runs on the 1st of every month
Custom
(your expression)
Enter your own cron expression
If you select Custom, an additional Custom Schedule field appears where you can enter any valid cron expression (e.g., \*/15 \* \* \* \* for every 15 minutes).
## Managing Existing Cron Jobs [#](/docs/add-a-custom-cron-job-in-xcloud/)
You can easily manage your cron jobs. From the Cron Jobs list, ‘Run Now’, ‘View Output’, ‘Edit’, ‘Delete’ for each of the cron jobs.
This is how you can easily add a custom cron job in xCloud.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
## **Where Cron Jobs Can Help You?** [#](/docs/add-a-custom-cron-job-in-xcloud/)
Cron jobs are super handy for server admins, but they’re also pretty useful for web developers like you. Here’s how they can make your life easier:
**Membership Management:** Got a website with memberships? Set up cron jobs to handle account expirations. You can automatically deactivate or delete accounts based on their expiration dates.
**Newsletter Automation**: If you’re running a blog, cron jobs are great for sending out newsletter emails without you having to lift a finger.
**Tracking Website Traffic:** Keep tabs on your website traffic by saving every page visit in a database table. Cron jobs can help you store daily traffic summaries for easy analysis.
**Managing Cached Data:** Need to clear out old cached data files? Cron jobs can handle that task for you, keeping your website running smoothly.
**Checking for Broken Links:** Worried about broken links on your massive website? Cron jobs can automatically check for broken links and send you a report every day.
**Handling Big Tasks:** Sending tons of emails or encoding videos can take a while. Cron jobs can run command line scripts to handle these tasks efficiently in the background.
**Social Media Updates:** Social media marketers can use cron jobs to fetch recent tweets and cache them in a text file, making it easy to keep your website’s social content up to date.
---
# Additional Domain Feature www And Non www Redirect With xCloud - xCloud
> Follow this simple guide to add additional domain with xCloud.
With [**xCloud**](http://hidden-hamlet-226309.wp1.sh) you will have the option to add an additional domain so that your users can automatically send people who visit one web address to another. It’s handy for things like managing multiple domains into one, changing domain names without losing customer traffic, fixing URL typos, and ensuring users find content that has been moved.
## **Add Additional Domain While Creating Site** [#](/docs/additional-domain-feature-with-xcloud/)
When building your website through the site creation panel, you’ll have the option to set additional domain names. This feature is incredibly helpful as it helps users to find you.
Let’s say your primary domain is **_clickfordiscount.com_**, but you’ve also got an additional domain called **_www.clickfordiscount.com_**. With domain redirect, typing **_www.clickfordiscount.com_** takes your users straight to clickfordiscount.com. It’s like a shortcut that always leads to the same place
## **Redirect Your Domain To The Primary Domain** [#](/docs/additional-domain-feature-with-xcloud/)
Once you’ve added your extra domain, it’s time to redirect it to your main one. This step ensures that whenever someone types in the extra domain, they’re automatically sent to your main website. It’s like giving clear directions so everyone ends up at the right place without any confusion. You have to click the “**Redirect this domain to the primary domain**” button for redirection
With xCloud, you can easily add multiple extra domains. Just click the ‘+’ button and add them one by one.
You can also take advantage of this additional domain feature for your current website setup.
If you are still stuck, feel free to reach out to our [**support**](/support/) for assistance.
---
# Adjusting Time Zone Settings In xCloud Servers - xCloud
> Follow this guide to adjust time zone settings in xCloud.
We’ll walk you through the straightforward process of aligning your time zone settings with **[xCloud](http://hidden-hamlet-226309.wp1.sh)**. With this simple guide, you’ll navigate the dashboard settings with ease. Just click on the **Time Zone** dropdown menu and select your desired time zone. Let’s ensure your xCloud servers are set to the correct time zone hassle-free!
---
# How to Auto-Deploy a Static Website From GitHub on xCloud
> Connect GitHub to xCloud and auto deploy a static website from Github every push using branch selection, deployment scripts, webhooks, logs, and rollback backups.
This guide explains how to **auto deploy static website GitHub** projects on xCloud. After setup, every push to your selected branch can trigger xCloud to pull the latest code, run your deployment script, and update the live site.
## Before you start [#](/docs/auto-deploy-static-website-github-xcloud/)
- An xCloud account with a server ready for the site.
- A GitHub repository containing the static website source or final files.
- Permission to authorize the repository for xCloud.
- A known build command and output folder if the repository requires a build step.
Connect GitHub so xCloud can access the repository for deployment.
## **Step-by-step Auto-Deploy Setup Of A Static Website From GitHub On xCloud** [#](/docs/auto-deploy-static-website-github-xcloud/)
### **Step 1: Connect GitHub to xCloud** [#](/docs/auto-deploy-static-website-github-xcloud/)
Open your xCloud settings or site creation flow and connect your GitHub account. Give the connection a clear label if you manage multiple GitHub accounts. Authorize GitHub so repositories can be selected from xCloud.
### **Step 2: Create a site from the repository** [#](/docs/auto-deploy-static-website-github-xcloud/)
Open the target server, create a new site, and choose the Git repository option. Select the repository and branch xCloud should deploy. Choose the repository and production branch for the static site.
### **Step 3: Enable push-to-deploy** [#](/docs/auto-deploy-static-website-github-xcloud/)
Turn on push-to-deploy so GitHub sends a webhook event to xCloud after pushes to the configured branch. Only pushes to that branch should trigger the deployment. Enable push-to-deploy for automatic deployments from GitHub.
### **Step 4: Add the deployment script** [#](/docs/auto-deploy-static-website-github-xcloud/)
If the repository already contains final static files, the deployment script may be minimal. If it needs a build, install dependencies, build, and copy the output folder into the web root.
```
cd /var/www/your-site
npm ci
npm run build
rsync -a --delete dist/ ./
```
Copy to Clipboard
Set the commands xCloud should run on each deployment.
### **Step 5: Add domain, SSL, and backups** [#](/docs/auto-deploy-static-website-github-xcloud/)
Attach the domain, enable HTTPS, and configure backups before relying on automatic deployments. A backup gives you a rollback point if a bad commit ships to production. Finish the setup with domain, SSL, and backups.
## Verify auto-deploy [#](/docs/auto-deploy-static-website-github-xcloud/)
1. Make a small visible change in the repository.
2. Push to the configured branch.
3. Open xCloud deployment logs and confirm the webhook triggered a new deployment.
4. Visit the site and verify the change appears.
5. Use deployment logs to verify every push-to-deploy run.
## Rollback or pause deployments [#](/docs/auto-deploy-static-website-github-xcloud/)
If a deployment ships the wrong version, revert the commit and push again, or restore the site from a known-good xCloud backup. To pause automatic deployments while investigating, disable push-to-deploy in the site Git settings.
## Troubleshooting [#](/docs/auto-deploy-static-website-github-xcloud/)
- If Git pushes do not trigger deployment, confirm push-to-deploy is enabled and the push went to the configured branch.
- If GitHub webhooks were removed or changed, re-save the Git settings in xCloud so the webhook can be recreated where supported.
- If the build succeeds but old content remains, verify the script copies the correct output directory into the web root.
- If environment variable changes do not appear, run a new deployment after saving them.
- If SSL fails after deploy, debug DNS/SSL separately; deployment and DNS propagation are different parts of the launch.
## **Frequently Asked Questions** [#](/docs/auto-deploy-static-website-github-xcloud/)
### Can I switch the deployed branch later? [#](/docs/auto-deploy-static-website-github-xcloud/)
Yes. Change the configured branch in the xCloud Git settings, save, and run the next deployment from that branch.
### Can I manually redeploy without a Git push? [#](/docs/auto-deploy-static-website-github-xcloud/)
Yes. Use the manual deployment option in xCloud when you want to rerun the deployment script without changing the repository.
### Does auto-deploy replace backups? [#](/docs/auto-deploy-static-website-github-xcloud/)
No. Auto-deploy updates the site, while backups give you rollback protection. Use both for safer releases.
## Related docs and resources [#](/docs/auto-deploy-static-website-github-xcloud/)
- [xCloud documentation](https://xcloud.host/docs/)
- [xCloud Dashboard](https://app.xcloud.host/)
- [GitHub webhooks documentation](https://docs.github.com/en/webhooks) for push-to-deploy workflows
## How the auto-deploy loop works [#](/docs/auto-deploy-static-website-github-xcloud/)
1. You push a commit to the selected GitHub branch.
2. GitHub sends a webhook event to xCloud.
3. xCloud pulls the latest code from the repository.
4. xCloud runs the configured deployment script.
5. The script copies the final output to the web root.
6. The next browser request loads the updated version after cache clears.
## Deployment script patterns [#](/docs/auto-deploy-static-website-github-xcloud/)
The deployment script should be repeatable. A good script can run many times without leaving old build files, nested folders, or partial output behind.
```
# Static repository with files already in the root
cd /var/www/your-site
echo "No build step required"
# Static project with a build output folder
cd /var/www/your-site
npm ci
npm run build
rsync -a --delete dist/ ./
```
Copy to Clipboard
## Release safety tips [#](/docs/auto-deploy-static-website-github-xcloud/)
- Use a production branch for live deployments.
- Review changes before merging into the deployment branch.
- Create backups before major redesigns or build-system changes.
- Keep deployment logs available when asking for support.
- Pause push-to-deploy if a bad commit is repeatedly deploying while you investigate.
## What to send to xCloud Support [#](/docs/auto-deploy-static-website-github-xcloud/)
- The xCloud site name and public domain.
- The GitHub repository/branch label, without private tokens.
- The time of the last push and whether GitHub shows webhook delivery.
- The deployment log output from xCloud.
- Whether manual Deploy Now works while GitHub push-to-deploy does not.
Still stuck? Feel free to contact our [**support team.**](https://support.xcloud.host/)
---
# An Overview Of Auto Healing Feature In xCloud - xCloud
> xCloud Auto Healing Feature automatically detect, fix, and start the server utilities again if you have issues. Take a look at xCloud Auto Healing Feature.
xCloud server utilities help you to manage your server and the server database. If they get turned off, with our monitoring feature we detect this, resolve the issue, and restart the server utilities automatically.
Let’s have a quick look at the auto-healing-enabled server utilities below.
- MySQL
- NGINX
- Redis
- PHP
If you have any questions or are facing any difficulties feel free to contact our [**support team**](/support/) anytime.
---
# How to Auto-Tune MySQL/MariaDB Configurations on Your Server - xCloud
> Learn how to automatically optimize MySQL/MariaDB settings on your server using the built-in Auto-Tune feature.
Optimizing MySQL or MariaDB is essential for maintaining high performance, stability, and efficient resource usage on your server. Manual tuning can be complex, especially if you’re unfamiliar with various database parameters.
To simplify this process, the system includes an **Auto-Tune** feature that automatically adjusts key MySQL/MariaDB settings based on your server’s resources and workload.
Follow the guide to auto-tune MySQL/MariaDB configurations on your server in one click.
## **Step 1: Go to Your Server** [#](/docs/auto-tune-mysql-mariadb-configurations/)
To begin, go to your server dashboard and navigate to the settings area. From the sidebar menu, open **‘Management’** and then choose **‘MariaDB Configuration’**.
After accessing the MariaDB Configuration section, locate the **‘Auto-Tune’** button on the dashboard. Clicking this button will trigger the system to automatically analyze your server’s resources and adjust several important MySQL/MariaDB settings.
The Auto-Tune tool focuses on optimizing key parameters, including **‘Max Connections’**, **‘Max Allowed Packet’**, and the **‘InnoDB Buffer Pool Size’**.
These adjustments help ensure your database operates efficiently by improving connection handling, supporting larger data packets, and optimizing memory usage for InnoDB tables. The updated configuration is applied automatically after the tuning is complete.
_Note: We will bring more MySQL and MariaDB configurations very soon._
And that’s it this is how easily you can Auto Tune MySQL and MariaDB in one click. By automatically configuring essential settings, the tool helps your server run more smoothly and handle greater workloads with ease.
Still stuck? Feel free to contact to our [support team](/support/).
---
# How to Integrate AWS S3 Bucket Using Any Storage Provider with xCloud? - xCloud
> Learn how to configure and use AWS S3 bucket for site backup in xCloud - an easy step by step guide to follow.
Backing up your website is essential to ensure data security and disaster recovery. With [**xCloud hosting**](/), you can leverage AWS S3 (Simple Storage Service) to store backups of your website efficiently. This guide will walk you through the process of setting up an AWS S3 bucket and configuring it for site backups in xCloud.
**Prerequisites**
Before proceeding, ensure you have:
- An AWS account with S3 access.
- An xCloud account with site backup features enabled.
- Basic knowledge of AWS IAM (Identity and Access Management).
**_Note:_** _To use AWS S3 bucket for site backup in xCloud, you need a few things in your hand while creating a bucket:_ **_Bucket Name, Access Key ID, Secret Key, Endpoint & Region_**_. Let’s collect all these following the guide below._
## **How to Create an S3 Bucket – Step By Step Guide** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
Setting up an AWS S3 bucket is easier than you think! This guide walks you through the process step by step.
### **Create & Collect Access Key & Secret Access Key** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
Start with logging into your AWS account. Once you’re in, click on your profile placed in the top right corner & navigate to ‘**Security Credentials**’ from the dropdown options.
On the resulting page, click on ‘**Create Access Key**’ & select ‘**Other**’ before clicking on **‘Next.’**
Now, describe the purpose of your access key & where it’ll be used further. A good description will help you rotate this access key confidently later. Click on the ‘**Create access key**’ to go to the next step.
On the resulting page, you’ll find your ‘**Access key**’ & ‘**Secret access key.**’ Copy these keys and save them somewhere else. You’ll require these keys while configuring AWS S3 in xCloud. Finally, click on ‘**Continue.**’
Now, follow the instructions as shown below. Initially, you may not find the S3 option the way it has been displayed below. All you have to do is type ‘**S3**’ on the top search bar.
### **Create an S3 Bucket** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
The next step is creating the S3 Bucket. To do so, click on the ‘**Create bucket**’ & you’ll get a new page. Now, name your bucket, scroll down & click on ‘**Create bucket**.’ While naming the bucket, make sure your bucket name is globally unique.
Up to this point, we have everything in our hands except the endpoint & region. To get these according to your region, follow this [**documentation**](https://docs.aws.amazon.com/general/latest/gr/s3.html). For this tutorial, the region was Asia Pacific (Sydney) & here’s the endpoint & region below.
Now, let’s move on to the process of how you need to configure your bucket in xCloud.
## **How to Configure AWS S3 Bucket for Site Backup in xCloud** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
Backing up your xCloud site has never been easier. Set up an AWS S3 bucket to store your data securely with this quick and easy guide.
### **Step 1: Login to Your xCloud Dashboard** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
Start with logging into your xCloud dashboard. Navigate to your profile settings on the top right corner & click on ‘**Team Settings.**’
### **Step 2: Add New Provider** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
From the resulting page, navigate to **‘Integrations’** → **‘Storage Provider**’ & click on **‘Add New Provider’** to add the AWS S3 provider to your xCloud.
Now select **‘Other’** & place all the things (Bucket Name, Access Key ID, Secret Key, Endpoint & Region) that you’ve collected so far in the respective fields. Hit the **‘Submit’** button to finalize the configuration of the AWS S3 bucket for site backup in xCloud.
_Note: Before the endpoint, make sure to add ‘_**_https://_**_’; otherwise, it’ll not work._
## **Connect Any S3-Compatible Storage Provider** [#](/docs/aws-s3-bucket-for-site-backup-in-xcloud/)
In addition, **xCloud supports integration with more S3-compatible storage service**s. Easily connect:
- **MinIO**
- **Wasabi**
- **Backblaze B2**
- **Any other S3-compatible object storage**
This is how you can easily configure and use an AWS S3 bucket for site backup in xCloud.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# Do you offer backups in xCloud? - xCloud
> Yes, xCloud provides two types of backups: Server Backup and Site Backup.
Yes, xCloud provides two types of backups: **Server Backup** and **Site Backup**.
### Server Backup [#](/docs/backups-in-xcloud/)
Server Backup is available only for **xCloud Managed Servers** and Vultr Server. This feature lets you back up your entire server environment.
- Costs an additional **20% of the server price**
👉 Read this [**documentation**](/docs/configure-server-backup-management/) to learn more.
### Site Backup [#](/docs/backups-in-xcloud/)
Site Backup allows you to back up individual websites with flexible storage options.
- Supports multiple storage integrations
- Compatible with **S3-based storage providers**
- Lets you connect your own storage and manage backups easily
👉 Read this [**documentation**](/docs/site-backups-in-xcloud/) to learn more.
---
# How To Enable Brotli Compression on xCloud And Configuring For Your Site - xCloud
> Learn how to enable Brotli compression on your site and verify it works using simple tools and commands. Boost your site’s speed today.
Brotli is a modern compression algorithm developed by Google, designed to compress web content more efficiently. Introduced in 2015, Brotli is now supported by all major browsers and is widely adopted across modern web infrastructure.
Compression plays a critical role in web performance by reducing file sizes before they are transmitted to users. Smaller files mean faster downloads, lower bandwidth usage, and improved page load times. Brotli is particularly effective at compressing **static assets** such as CSS, JavaScript, fonts, and images, where its higher compression ratio can provide significant savings.
Brotli supports both **static compression** (where files are pre-compressed at build time) and **dynamic compression** (where files are compressed on-the-fly by the server). Static compression is recommended for production environments, while dynamic compression is used when static files are not pre-compressed.
In xCloud environments, Brotli is automatically enabled on NGINX servers, ensuring all eligible files benefit from this advanced compression algorithm without requiring manual intervention. However, if you’re using **Cloudflare**, you can use Brotli compression on both **NGINX** and **OpenLiteSpeed (OLS)** servers. This provides flexibility for Cloudflare users to take advantage of Brotli’s benefits, regardless of the server platform.
_**Note**: Brotli is automatically installed on the new servers. However, it is not installed on the old servers for now._
## **Configuring Brotli For Your Site** [#](/docs/brotli-compression-on-xcloud/)
If you want to access Brotli, you’ll need to make sure your site is using HTTPS (SSL). Brotli only works with secure connections, so be sure to get your SSL certificate set up first. Once enabled, these are the default settings for Brotli you will get :
brotli on;
brotli\_static on;
brotli\_comp\_level 4;
brotli\_types application/atom+xml
application/javascript
application/json
application/ld+json
application/manifest+json
application/vnd.geo+json
application/vnd.ms-fontobject
application/x-font-opentype
application/x-font-truetype
application/x-font-ttf
application/x-javascript
application/x-web-app-manifest+json
application/xhtml+xml
application/xml
application/xml+rss
image/bmp
font/eot
font/opentype
font/otf
image/svg+xml
image/vnd.microsoft.icon
image/x-win-bitmap
image/x-icon
text/cache-manifest
text/css
text/javascript
text/plain
text/vcard
text/vnd.rim.location.xloc
text/vtt
text/x-component
text/x-cross-domain-policy
text/xml;
## **Verifying if Brotli is Working on Your Website** [#](/docs/brotli-compression-on-xcloud/)
To ensure Brotli is working on your site, you can use various online tools to test your website’s compression. One of the simplest ways to verify is by using the **Gift of Speed** Gzip test tool, which also checks Brotli compression.
Here’s how you can verify if Brotli is enabled:
1. Go to [Gift of Speed Gzip Test](https://www.giftofspeed.com/gzip-test/).
2. Enter your website URL and click “Test Your Site.”
3. Once the test is complete, look at the **Content-Encoding** header in the response.
If Brotli is working correctly, you should see br listed as the encoding method. For example: Content-Encoding: br
If you see gzip or deflate, it means Brotli is not enabled or being used. If br is present, you know that Brotli is successfully compressing your assets.
### **Verifying Brotli Using Command Line** [#](/docs/brotli-compression-on-xcloud/)
Alternatively, you can verify if Brotli is working using the command line with curl. Here are some commands to help you check for Brotli or Gzip compression:
1. **Check for Gzip Compression**Run the following command to see if Gzip is enabled:
```
curl -s -I -H "Accept-Encoding: gzip" https://example.com | grep -i "content-encoding"
```
Copy to Clipboard
If Gzip is enabled, you will see:
```
Content-Encoding: gzip
```
Copy to Clipboard
2. **Check for Brotli Compression**Run the following command to see if Brotli is enabled:
```
curl -s -I -H "Accept-Encoding: br" https://example.com | grep -i "content-encoding"
```
Copy to Clipboard
If Brotli is enabled, you will see:
- Content-Encoding: br
3. **Check for Both (Gzip and Brotli) at Once**If you want to check for both compression types, run:
```
curl -s -I -H "Accept-Encoding: gzip, br" https://example.com | grep -i "content-encoding"
```
Copy to Clipboard
If both are supported, the response might be:
```
Content-Encoding: br
```
Copy to Clipboard
or
```
Content-Encoding: gzip
```
Copy to Clipboard
The server typically chooses the best compression method, and **Brotli** is preferred if both are available.
4. **Check for Compression with Full Request**If you want to view the full response headers, use this command:
```
curl -s -H "Accept-Encoding: gzip, br" -D - https://example.com -o /dev/null
```
Copy to Clipboard
Brotli compression is a powerful tool to enhance your performance by reducing file sizes and improving page speed. With automatic configuration and smart optimization with xCloud, your applications benefit from Brotli’s efficiency without requiring manual setup.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Build a WordPress Site with Templately AI - xCloud
> Learn how to quickly build and customize a WordPress site on xCloud using Templately AI, complete with automated templates, content generation, and easy deployment.
Building a new website becomes much easier when you have the right tools and a clear process to follow. xCloud makes it simple to deploy a WordPress site using [**Templately AI**](https://templately.com/). If you want to create a site with ready-made templates and AI-generated content, xCloud enables you to launch your website quickly and efficiently.
Follow the steps to **[create a WordPress site](/hosting-for-wordpress/)** using Build With Templately AI right from the xCloud dashboard.
## ✅ **Free Access for All xCloud Free and PRO Users** [#](/docs/build-a-wordpress-site-with-templately-ai/)
Enjoy exclusive AI-powered website-building capabilities at no extra cost:
- **100 AI Credits**
- **3 Full Site Imports**
- **1 Month Templately Pro Access**
_(includes 3,836 Premium Templates!)_
## **Step 1: Access the Dashboard** [#](/docs/build-a-wordpress-site-with-templately-ai/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
## **Step 2: Choose Your Server** [#](/docs/build-a-wordpress-site-with-templately-ai/)
Once your server is connected, you can create a site from the dashboard or Site List by clicking the ‘Create New Site’ button. Then choose your server from the dropdown menu. Next, click on the ‘Next’ button to proceed.
## **Step 3: Choose Your Site & Add Information** [#](/docs/build-a-wordpress-site-with-templately-ai/)
As we will be creating a fresh WordPress site, choose the **‘Install New WordPress Website’** option.
[](https://xcloud.host/docs/build-a-wordpress-site-with-templately-ai/image-1374/)
## **Step 4: Select Site Creation Method** [#](/docs/build-a-wordpress-site-with-templately-ai/)
Next, you need to choose a deployment method: **‘Default’** or **‘Build With Templately AI’**.
To create a site manually, choose the **‘Default’** method. If you want to create a site using AI, choose the **‘Build With Templately AI’** method.
## **Step 5: Set Up Your Site** [#](/docs/build-a-wordpress-site-with-templately-ai/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes:
- **Go Live** – for a production-ready deployment.
- **Demo Site** – for deploying the site instantly with a demo domain from xCloud.
Selecting **Go Live** will immediately create a live environment, while **Demo Site** allows you to create a site using a temporary demo domain.
### **Step 6: Configure Domain Settings** [#](/docs/build-a-wordpress-site-with-templately-ai/)
If you select the **Demo Site** option, xCloud will assign a temporary subdomain for your WordPress application. Next, enter your application’s domain.
You will also get multiple configuration options, including**‘WordPress Multisite’, ‘Turn Off Indexing’, ‘Full Page Caching’, ‘Redis Page Caching’.** Toggle them on according to your preferences.
**📌 Note for WordPress Multisite Users:** _When using Multisite, xCloud will only build the Primary Site during deployment. Additional network sites will not be automatically generated and must be created manually within the WordPress Network Admin after deployment._
Copy to Clipboard
### Get 100 Free Emails With xCloud Email Delivery For Your Sites [#](/docs/build-a-wordpress-site-with-templately-ai/)
Next, toggle on the ‘**Email Provider Configuration’** for your site. xCloud provides **100 free emails per site**.
📌 Follow this **_[documentation](https://xcloud.host/docs/add-xcloud-managed-email-service/)_** to learn more.
## **Step 6: Configure Additional Settings** [#](/docs/build-a-wordpress-site-with-templately-ai/)
By default, the WordPress admin credentials are auto-generated to speed up the site creation process. Once your site is deployed, you will receive your admin credentials via email. You can later update your password if needed.
From **More Advanced Settings**, you can update ‘Admin Username’, ‘Admin Password’, ‘Admin Email Address’ additional configuration details.
You can also configure Search Engine Visibility, Deploy Script, and Database Management settings according to your preferences.
## **Step 7: Review Your WordPress Settings** [#](/docs/build-a-wordpress-site-with-templately-ai/)
After completing the previous steps, click the **‘Next’** button. It usually takes 1–2 minutes to create your site.
🔔 Note: After your site is created, **Templately will automatically send an email containing your WordPress admin login credentials**.
Copy to Clipboard
## **Step 8: Insert Full Site with AI** [#](/docs/build-a-wordpress-site-with-templately-ai/)
Click on the ‘Build with Templately AI’ button. This will automatically redirect you to the Templately dashboard.
If the redirect does not happen automatically, simply click the ‘Build with Templately AI’ button again to proceed manually.
Here, the AI will ask some questions to generate content based on the answers you provide. Here are the questions that you need to answer.
- Business Name: The chatbot will ask, ‘What is Your Business Name?’. Here, in the answer, type your business name. If you are creating a portfolio website, you can add your name here, too.
- Industry: Then, you have to define which industry your business belongs to. You will find the suggested industry name in the conversation. You can either pick an industry from the options or add yours.
- Business Details: In the next part, give a detailed description of your business. Here, you can add what specifically your business does. For example, if it’s an agency, then whether it is a digital marketing agency or a study abroad agency, you can specify the information.
Email Address: Add specific email addresses for your website contact section. Through this email address, your visitors can contact you.
- Contact Number: Next, you will be asked whether you want your contact number or not. If you want to, then you can add it, or else you can click on the ‘Skip’ button.
- Business Address: In the next part, add your business address if you have one. OtherwiseOther wise you can click on the ‘Skip’ button here too.
- Opening Hours: If your business has a specific business hour, then add the opening hours in detail. You can click on the ‘Skip’ button if you do not have any specific hours.
- If you want to replace the images from the template and want to add customized images, you can do that. With Templately AI, you can also replace images. To change images, click on the ‘Yes’ button to agree to replace images.
After answering the questions, you will receive a confirmation text to generate content on the website based on the information you provided. If you are still confused, you can click on the ‘How should I pick?’ to get a demo sample.
After that, you will find an option to change images. From the options, select the image you want to replace. Then, you can choose from stock photos or upload them from your files. Select the images you want to replace.
Finally, click ‘Save Changes’, and after importing the full site, you will see that the images will be replaced with the ones you have chosen. Finally, click on ‘Generate and Proceed’ to generate full content and replace images on your website with AI.
Finally, after completing the process you will see your website will be createdwill created instantly. Here enter your ‘Site Title’, ‘Site Description’ & ‘Logo’ and then click on the ‘Style Website’.
Next, adjust the color and ‘Typography’ according to your preferences and click on the ‘Confirm Setup’ button.
### Final Outcome of Generating Content & Image Replacement [#](/docs/build-a-wordpress-site-with-templately-ai/)
And your site creation will be completed instantly. You will get two options: ‘Viewoptions ‘View Dashboard’, and ‘Visit Site’. Click on the visitvisti site option to check out your newly created site.
And that’s it. This is how easily you can effortlessly create and customize a fully functional WordPress website on xCloud. With xCloud and Templately AI, building a professional website has never been faster or more intuitive.
## **Frequently Asked Questions** [#](/docs/build-a-wordpress-site-with-templately-ai/)
### **What happens to Templately Pro access and my website after the 1-month free period ends?** [#](/docs/build-a-wordpress-site-with-templately-ai/)
After the complimentary one-month Templately Pro access ends, you will no longer have access to Pro templates or advanced Pro-only features, and you won’t be able to connect more than three websites. However, your website will remain live and fully functional, and all content and designs you created will stay exactly as they are. You can continue using Templately’s free features, and if you wish to regain Pro access, you can **[upgrade](https://templately.com/)** to PRO at any time.
### **What if I already have a Templately Pro (or Templately Lifetime Deal) account?** [#](/docs/build-a-wordpress-site-with-templately-ai/)
If you already have a **[Templately Pro](https://templately.com/) (Or Lifetime Deal)** account, xCloud will automatically connect to your existing account; no new account will be created. Any website built through xCloud will not count toward your active site limit under your Templately subscription. In addition, the 100 AI credits provided by xCloud will be added directly to your existing account, even if you’re an LTD user. For example, if you currently have 50 AI credits, your total will become 150.
### **How do AI credits work, and are they separate from my existing account with Templately?** [#](/docs/build-a-wordpress-site-with-templately-ai/)
The 100 AI credits included with xCloud are added directly to your current Templately account, whether you’re on a Free, Pro, or LTD plan. These credits are not part of a separate product or dashboard. Once your credits are used up, you won’t be able to generate new AI content, but all previously generated content will remain on your website without any interruption.
Still stuck? Feel free to reach out to our **[support team](http://hidden-hamlet-226309.wp1.sh/support).**
---
# Can I use Debian, Fedora, or other Linux distributions with xCloud? - xCloud
> Currently, xCloud supports Ubuntu-based servers for managed server provisioning and site deployment.
Currently, xCloud supports Ubuntu-based servers for managed server provisioning and site deployment.
We use Ubuntu because it gives the best compatibility with xCloud’s automation, WordPress stack, security updates, server management tools, and supported services.
At this time, Debian, Fedora, AlmaLinux, Rocky Linux, and other Linux distributions are not officially supported for xCloud-managed servers.
If you want to connect your own server to xCloud, we recommend using a supported Ubuntu version to ensure provisioning, updates, backups, SSL, and site management work properly.
---
# How to Change Language for Reseller xCloud Hosting Panel? - xCloud
> Learn how to change language for reseller hosting panel in xCloud white label to ensure a localized, user-friendly experience.
[**xCloud**](/) allows you to set your preferred language for your xCloud White Label reseller hosting panel, ensuring a localized and user-friendly experience for both you and your users.
## ****Change Language for Reseller xCloud White Label**** [#](/docs/change-language-for-reseller-xcloud-hosting/)
Change language for reseller hosting panels is quick and easy. Follow the below steps to update your brand language settings.
### **Step 1: Log in Navigate to Brand Settings** [#](/docs/change-language-for-reseller-xcloud-hosting/)
After logging into your xCloud dashboard, navigate to the ‘**White Label’** section. Then, go to ‘**Settings’** and select ‘**Brand’** to open the **Brand Setup** settings.
### **Step 2: Change Language for Reseller** [#](/docs/change-language-for-reseller-xcloud-hosting/)
In the ‘**Language Settings’** section, click the down arrow icon to open the dropdown menu and select your preferred language. Then, hit the ‘**Save**‘ button to successfully update your White Label brand language for reseller client end users.
**_Note:_** _Reseller clients can change their own hosting panel language from their profile settings._
This is how easily you can change brand language in xCloud White Label with your preferred choice. Still stuck? Contact our [**support team**](https://support.xcloud.host/) for further assistance.
---
# How to Change the Language for xCloud Hosting Panel? - xCloud
> Learn how to change the language in xCloud hosting panel for profile & notifications. Enjoy a personalized, multilingual experience easily.
[**xCloud**](/) lets you change the language for your profile and notifications in the xCloud hosting panel with multi-language support. This feature ensures a more personalized and user-friendly experience. It caters to your preferred language, making navigation and communication easier.
## **Change Language for xCloud Hosting Panel** [#](/docs/change-the-language-for-xcloud-hosting-panel/)
Changing the language in xCloud hosting panels is quick and straightforward. Follow the below steps to update your profile language or adjust notification settings.
### **Step 1: Log in to xCloud Dashboard** [#](/docs/change-the-language-for-xcloud-hosting-panel/)
First, Log In to your xCloud hosting panel dashboard. Add your email and password, then hit the ‘**Log In’** button.
### **Step 2: Change Language** [#](/docs/change-the-language-for-xcloud-hosting-panel/)
In your xCloud Dashboard, click on the top right corner ‘**^**‘ (up) the arrow icon beside your profile name. From the dropdown option ‘**Select**‘ the language you want to set for your xCloud profile. It will automatically save and implement your saved language.
There is another way to change the language in xCloud. Click on the top right corner **‘^’** (up) the arrow icon beside your profile name and click on ‘**My Profile**‘. Choose a language from the dropdown option and your saved language will be implemented.
#### **Notification Language Settings** [#](/docs/change-the-language-for-xcloud-hosting-panel/)
To receive your xCloud team’s activities in notifications in your preferred language, change it. Click on the top right corner ‘**^**‘ (up) the arrow icon and select ‘**Team Settings,**‘ click on the three-dot options of your team and select ‘**Edit**‘.
From the dropdown options, change the language to your preferred one in the notification language settings. Hit the ‘**Save Changes’** button to update.
After saving your notification language settings, you can get notifications in Email, Slack, WhatsApp & Telegram in your preferred language. Here, you can see an email notification in German we set to receive notification.
This is how easily you can change language in xCloud with your preferred choice. Still Stuck! Contact our [**support team**](https://support.xcloud.host/) for further assistance.
---
# How to Check Cron Job List of All Sites in Your Server? - xCloud
> xCloud now allows you to check cron job list of all the sites in your server in an organized manner. Find out more from this documentation.
[**xCloud**](/) now lets you **check cron job list** of all sites in your server. With this functionality, you can easily find all the system cron jobs of your server organized in one place. Also, you will be able to monitor the cron job list to ensure server security. In this step-by-step documentation, we will show you how it works.
## **How to Check Cron Job List of Your Server’s Sites in xCloud?** [#](/docs/check-cron-job-list-of-all-sites-in-your-server/)
We will now show you the steps that you need to follow to check cron job list of your servers list in xCloud. Let’s get started.
### **Step 1: Sign Up or Login with xCloud** [#](/docs/check-cron-job-list-of-all-sites-in-your-server/)
First, login with xCloud using your credentials. If you do not have an active account, create one by signing up.
**_Note:_** [**_Read this documentation_**](/docs/setup-your-first-server-site-with-xcloud/) _to learn how to set up your first server & site with xCloud._
### **Step 2: Navigate to Your Desired Server** [#](/docs/check-cron-job-list-of-all-sites-in-your-server/)
From the dashboard, click on the ‘**Server**’ tab at the top. Then, hit your desired server in the list to select it.
### **Step 3: Check Cron Job List of the Server** [#](/docs/check-cron-job-list-of-all-sites-in-your-server/)
Now, go to the ‘**Management’** tab in the left side panel. Under this tab, select the ‘**Cron Jobs**’ option.
In the ‘**Cron Jobs**’ screen, you will find the list of your custom and system cron jobs. As shown in the image below, the custom cron jobs are listed in the upper section of the screen. These cron jobs are organized in columns for ‘**ID**’, ‘**Command**’, ‘**User**’, ‘**Frequency**’ and ‘**Actions**’.
Under the ‘**Server Cron Jobs**’ section, you will get the system cron job list of all the sites on your server. These cron jobs will be organized according to columns for ‘**ID**’, ‘**User**’, ‘**Frequency**’ and ‘**Command**’. Also, you can click on any command to copy it instantly.
This is how easily you can check cron job list of all sites in our server using xCloud.
Still have questions? [**Contact our support team**](https://support.xcloud.host/) for quick assistance.
---
# How To Clone A Website From Git Repository With xCloud - xCloud
> Effortlessly clone a website from Git Repository with xCloud, simplifying the process without introducing any unnecessary complexity or challenges.
With [**xCloud**](/), you can easily clone a website from Git Repository with xCloud without any complexity at all. The migration process is exceptionally fast, ensuring a rapid transition without introducing any alterations to the code within your Git repository. With the below steps, you can easily migrate an existing WordPress from Git Repository. Let’s follow this guide to get started.
## **How To Migrate A Site From Git** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
Migrating a website from a Git repository with xCloud involves several easy steps. The below guide can help you to understand how you can perform this migration. Follow the steps below to migrate a site from a Git Repository.
### **Step 1: Select Option To Clone A Website** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
First, log into your xCloud account. From the dashboard, click on ‘**+New Site**’ button. Now, choose a server to add a site and click ‘**Next**’. Go to ‘**Clone a Git Repository**’ option.
**Note:** _Cloning is currently supported only for WordPress sites. It will not work for other types of websites at this time._
### **Step 2: Select Destination Server** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
From the ‘**Destination**’ tab, select the destination server to migrate your site. You can keep the server that is already selected, or you can change it from the dropdown. Then, click on ‘**Next**’.
### **Step 3: Set Up Domains** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
From the ‘**Domains**’ tab, you will get two options, either you can create your site in a staging domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
**Migrate Into A New Domain**
To create a site with your live domain, you need to select ‘**Migrate into a New Domain**’ option. Then you have to put ‘**New Site Title**’ and ‘**Domain Name**’.
Here, you need to enable HTTPS to make your website more secure. From the DNS Setup section, toggle on the ‘Do You Want To Enable HTTPS?’ option. After enabling it, you will get two options to select. Either choose to use a free SSL certificate issued & managed by xCloud, or, you can provide the certificate and manage it yourself. Select according to your choice.
**Staging Environment**
Instead of migrating into a new domain, you can select the ‘**Staging Environment**’ option. xCloud offers a temporary staging domain to make your site live which helps promptly showcase your site’s progress and collect feedback from teammates or clients. Subsequently, you can integrate your custom domain to make the site accessible to your users or visitors. Now, click on ‘**Next**’.
**Note:** For this documentation, we are going with the ‘**Staging Environment**’ option.
### **Step 4: Settings To Manage Database** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
In the ‘**Settings**’ tab, you will see the ‘**PHP Version**’ and ‘**Site Users**’. You can change these according to your choice. Also, you will see two caching options: ‘**Full Page Caching**’ and ‘**Redis Object Caching**’. You can enable both of these options.
Now, it is time for database management. You will get two options. Either you can create a new database on the server, or, you can add your existing database that is hosted on another server.
**Create Database In Server**
If you select this option, you need to get a ‘**Database Name**’, ‘**Database Username**’ and ‘**Database Password**’. You can keep these auto-generated credentials, or you can modify them according to your choice.
**Add Your Existing Database**
If you select this option, you need to put in a few information and credentials such as ‘**Database Host**’, ‘**Database Port**’, ‘**Database User**’, ‘**Database Name**’, and ‘**Database Password**’. Please make sure that the database connection configuration is correct.
After selecting any one option and providing all essential information and credentials, click on ‘**Next**’.
**Note:** For this documentation, we are going with ‘**Create Database In Server**’ option.
### **Step 5: Insert Git Repository Credentials** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
In the ‘**Git Repo**’ Tab, add your ‘**Git Repository**’ and ‘**Git Branch**’. Also, toggle on ‘**Enable push to deploy**’ option.
Once you enable the ‘**Push To Deploy**’, it will generate a ‘**Deployment URL**’. ‘**Push To Deploy**’ is a way to automatically deploy your site live once you push code to a Git repo. We need to insert this URL into GitHub. Let’s copy the ‘**Deployment URL**’
### **Step 6: Add Deployment URL In Git Repository** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
Now, go to your Git Repository. From the ‘**Code**‘ tab, go to the ‘**Settings**’ tab and click on ‘**Webhooks**’ page from the ‘**Code and automation**’ section of the left navigation. Insert the Deployment URL into the ‘**Payload URL**’ field. Select the ‘**Application/json**’ from the ‘**Content type**’ dropdown.
### **Step 7: Add Public Key In Git Repository** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
From the xCloud dashboard, copy the ‘**Public Key**’ to add it to your Git repository as a deploy key. Git migration uses the ‘**Public Key**’ for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the ‘**Code**‘ tab, go to the ‘**Settings**’ tab and click on ‘**Deploy Keys**’ in the security section of the left navigation. Click on the ‘**Add Deploy Key**’ button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on ‘**Next**’ on your xCloud settings of the ‘**Git Repo**’ tab.
### **Step 8: Confirm Migrating The Website** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
Now, to start the migration process, click on the ‘**Start**’ button.
After clicking on the ‘**Start**’ button, the migration process will start. And, you will see the progress of migrating.
The Git Repository must contain a **wp-config-sample.php**. xCloud generates a wp-config.php file from wp-config-sample.php file with the database information.
**Note:** You can choose whether you want to import your old database or not. So, here is an optional step below. You need to follow this after the migration process is complete.
### **How To Import Your Database In SQL Format** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
To import the database from your old site, you need to connect your **Database client** such as **TablePlus**. From your xCloud dashboard, take the ‘**Database Connection URL**’ from the SSH/sFTP page of your site.
Now, go to **TablePlus** dashboard. Click on the ‘**+**’ icon, then click on ‘**Import from URL**’. Paste the Connection URL and hit the ‘**Import**; button. Then click on ‘**Save**’.
Now you can delete the tables that were automatically generated by xCloud and import your desired database.
## **Setup The Site After Completing Git Migration** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
When the migration process is complete, you can visit the site. You need to choose the language and provide necessary information such as ‘**Site Title**’, ‘**Username**’, ‘**Email**’, etc. Now, you can access the site by logging in.
## **After Migration Deployment Settings** [#](/docs/clone-a-website-from-git-repository-with-xcloud/)
After the migration process is complete, you can change the Git Branch, turn on or off the ‘**Push To Deploy**’ feature, run Deploy Scripts by inserting the scripts, etc. Go to GitHub page from the site dashboard, update things you want to change, and hit the ‘**Save**’ button.
That’s it! You have successfully cloned a website from the **Git repository with xCloud**.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# Clone Site Under Same/Different Server In xCloud - xCloud
> Clone site effortlessly with xCloud—same/different server options. Back up, test updates, or migrate hassle-free. Step-by-step tutorial inside!
In this tutorial, we will explore how to efficiently clone a site under the same or a different server using [xCloud](/). Cloning your website can serve various purposes, such as creating backups, testing updates safely, or smoothly migrating to a new server.
With xCloud’s intuitive interface and robust features, you’ll learn the precise steps to duplicate your site hassle-free. So, let’s begin the process of cloning your site with xCloud.
Note: Cloning is currently supported only for WordPress sites. It will not work for other types of websites at this time.
## Step 1: Clone Site From Dashboard [#](/docs/clone-site-under-same-different-server-in-xcloud/)
First, go to your site and click on the three-dot icon from the dashboard. From the action menu, click on the **‘Clone Site’** option. Then choose where you want to clone your server. And click on the **‘Next’** button.
## Step 2: Choose a Demo or Custom Domain [#](/docs/clone-site-under-same-different-server-in-xcloud/)
You will have two options available. You can choose a **‘Demo site’** or **‘Migrate to a New Domain’** for your cloned site. Here we are creating a demo site. After choosing click on the ‘Next’ button to proceed.
Then create a new database or add your own database for this website and click on the ‘Next’ button.
## **Step 2: Adjust the Settings** [#](/docs/clone-site-under-same-different-server-in-xcloud/)
Next, choose the ‘PHP version for this site. Also, you can **‘Clone Your Source Site Settings’** like **‘Backup’** and some **‘Security Settings’**. Here you will be able to see the options that are enabled in your source site.
For Backup Settings:
- Remote Backup
- Local Backup
For Security Settings:
- XML-RPC
- X-Frame-Options
- 8G Firewall
- AI Bot Blocker
- WP Fail2Ban
Choose your preferences and click on the ‘Next’ button.
And finally review the information and click on the ‘Start’ button to start the site cloning process
Once the process is completed, the site will be live instantly. Now you can customize it as your prefernces
This is how you can clone a WordPress site under the same or a different server in xCloud.
Still stuck? [**Contact our support**](/contact/) team for any queries.
---
# How to Fix Cloudflare 522 Errors When Ports 80 and 443 Are Closed With xCloud
> Cloudflare 522 troubleshooting guide for xCloud servers when ports 80 and 443 are closed by UFW or firewall rules. Check SSH, allow HTTP/HTTPS, and bring the site back online.
A Cloudflare 522 error usually means Cloudflare reached your domain but could not connect to the origin server in time. In xCloud, one common cause is that the server is online and SSH works, but the web ports **80** and **443** are blocked in UFW or another firewall layer.
This guide explains how to troubleshoot **Cloudflare 522 ports 80 443 closed** issues, confirm the firewall status, allow HTTP and HTTPS traffic, and verify that your site is live again. It is written for symptoms such as Cloudflare 522, origin timeout, connection timed out, server disconnected, HTTPS port closed, HTTP port closed, UFW firewall issue, and xCloud firewall troubleshooting.
## When to use this guide [#](/docs/cloudflare-522-ports-80-443-closed/)
- Your site shows **Error 522** in Cloudflare.
- The xCloud server still appears connected or reachable.
- SSH works, but the website does not load.
- External checks show port **80** or **443** is closed, filtered, or timing out.
- Cloudflare says it cannot connect to the origin server.
- Recent firewall, bot protection, fail2ban, iptables, nftables, or UFW changes were made.
## What the Cloudflare 522 error means [#](/docs/cloudflare-522-ports-80-443-closed/)
Cloudflare Error 522 means the connection from Cloudflare to the origin server timed out. The server may still be running, but Cloudflare cannot complete a web connection to the origin over HTTP or HTTPS.
For most WordPress and web applications, the required web ports are:
- **Port 80** for HTTP traffic
- **Port 443** for HTTPS traffic
- **Port 22** for SSH access
If only port 22 is allowed, SSH can still work, but visitors and Cloudflare cannot reach the website. This creates a situation where the server may look available from SSH, but the public site remains down.
## Before you start [#](/docs/cloudflare-522-ports-80-443-closed/)
- Confirm that you have SSH or sudo user access to the server.
- Make sure you understand the impact of firewall changes before running commands.
- If you recently added custom firewall rules, keep a note of what was changed.
- Do not disable the firewall completely unless you know why and have a rollback plan.
You can also review the xCloud server disconnected troubleshooting guide: [Troubleshooting Guide: xCloud Server Disconnected](/docs/troubleshooting-guide-xcloud-server-disconnected/).
## Step 1: Confirm the site error [#](/docs/cloudflare-522-ports-80-443-closed/)
Open the affected domain in your browser and confirm the exact error. If Cloudflare shows **Error 522**, the issue is usually between Cloudflare and the origin server, not between the visitor and Cloudflare.
(Screenshot: Browser showing a Cloudflare 522 timeout for the affected domain)
## Step 2: Check whether SSH still works [#](/docs/cloudflare-522-ports-80-443-closed/)
Try to connect to the server with SSH. You can use your normal SSH user, root access if available, or the xCloud sudo user feature.
```
ssh username@your-server-ip
```
Copy to Clipboard
If SSH connects but the website does not load, the server may be online while the web ports are blocked.
(Screenshot: xCloud server overview showing the server is connected while the public site is not loading)
## Step 3: Check the UFW firewall status [#](/docs/cloudflare-522-ports-80-443-closed/)
After you connect with SSH, run the following command:
```
sudo ufw status
```
Copy to Clipboard
If the output only shows SSH rules, the web ports are not allowed. For example:
```
Status: active
To Action From
-- ------ ----
22/tcp ALLOW Anywhere
22 ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
22 (v6) ALLOW Anywhere (v6)
```
Copy to Clipboard
This output means SSH is allowed, but HTTP and HTTPS are not allowed through UFW. In this state, Cloudflare can show a 522 error because it cannot reach the origin server on port 80 or 443.
(Screenshot: SSH terminal showing UFW status with only SSH/port 22 allowed)
## Step 4: Allow ports 80 and 443 [#](/docs/cloudflare-522-ports-80-443-closed/)
Run these commands to allow standard web traffic:
```
sudo ufw allow 80
sudo ufw allow 443
```
Copy to Clipboard
Port 80 is required for HTTP. Port 443 is required for HTTPS. Even if your site redirects all visitors to HTTPS, port 80 is still commonly needed for redirects, certificate checks, and normal web routing.
## Step 5: Confirm the firewall rules were added [#](/docs/cloudflare-522-ports-80-443-closed/)
Run the UFW status command again:
```
sudo ufw status
```
Copy to Clipboard
The output should now include port 80 and port 443 for both IPv4 and IPv6:
```
Status: active
To Action From
-- ------ ----
22/tcp ALLOW Anywhere
22 ALLOW Anywhere
443 ALLOW Anywhere
80 ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
22 (v6) ALLOW Anywhere (v6)
443 (v6) ALLOW Anywhere (v6)
80 (v6) ALLOW Anywhere (v6)
```
Copy to Clipboard
(Screenshot: SSH terminal showing UFW status with ports 22, 80, and 443 allowed)
## Step 6: Verify the site loads again [#](/docs/cloudflare-522-ports-80-443-closed/)
Open the site in your browser and refresh Cloudflare if needed. You can also test both the HTTP and HTTPS versions:
- `http://your-domain.com`
- `https://your-domain.com`
The expected result is that the site loads normally and Cloudflare no longer shows the 522 timeout page.
(Screenshot: Website loading successfully after ports 80 and 443 are allowed)
## Step 7: Check xCloud firewall settings [#](/docs/cloudflare-522-ports-80-443-closed/)
After fixing the immediate issue through SSH, review the firewall configuration in xCloud.
1. Log in to your xCloud dashboard.
2. Open the affected server.
3. Go to **Security** → **Firewall Management**.
4. Confirm that **HTTP** on port **80** is allowed.
5. Confirm that **HTTPS** on port **443** is allowed.
6. Review any custom deny rules that may have been added recently.
For more details, see [How To Easily Configure Firewall Management With xCloud Hosting](/docs/how-to-configure-firewall-management-in-xcloud/).
(Screenshot: xCloud Firewall Management page showing HTTP and HTTPS allowed)
## If ports are allowed but the site still shows 522 [#](/docs/cloudflare-522-ports-80-443-closed/)
If UFW shows ports 80 and 443 as allowed but the site still does not load, check whether the web server is listening on those ports.
```
sudo ss -ltnp | grep -E ':80|:443'
```
Copy to Clipboard
You should see a web server process listening on port 80 and/or 443. If nothing is listening, check the web server status. For OpenLiteSpeed, you can use:
```
sudo systemctl status lsws
```
Copy to Clipboard
If the service is stopped or failed, review the service logs before restarting it. Restarting services on a production server can affect active visitors, so confirm the impact first.
## Common causes [#](/docs/cloudflare-522-ports-80-443-closed/)
- A custom firewall command removed existing allow rules.
- UFW was enabled without adding HTTP and HTTPS rules.
- An anti-bot or emergency firewall change blocked web traffic.
- A deny rule was added before the allow rules.
- A server cleanup or hardening command modified iptables, nftables, or UFW rules.
- The web server service stopped responding after configuration changes.
## Prevention tips [#](/docs/cloudflare-522-ports-80-443-closed/)
- Before enabling UFW, allow SSH, HTTP, and HTTPS.
- Keep SSH open so you do not lock yourself out.
- Avoid running copied firewall cleanup commands without reviewing them.
- Document any custom firewall rules added for bot protection.
- After changing firewall rules, test the website from an external network.
- Use xCloud Firewall Management for standard port rules when possible.
## Useful commands [#](/docs/cloudflare-522-ports-80-443-closed/)
```
# Check UFW status
sudo ufw status
# Allow HTTP
sudo ufw allow 80
# Allow HTTPS
sudo ufw allow 443
# Check listening web ports
sudo ss -ltnp | grep -E ':80|:443'
# Check OpenLiteSpeed status
sudo systemctl status lsws
```
Copy to Clipboard
For additional UFW reference, see the [Ubuntu UFW community documentation](https://help.ubuntu.com/community/UFW).
## Expected result [#](/docs/cloudflare-522-ports-80-443-closed/)
After ports 80 and 443 are allowed, Cloudflare should be able to connect to the origin server again. The site should load normally over HTTPS, and visitors should no longer see the Cloudflare 522 error.
## FAQ [#](/docs/cloudflare-522-ports-80-443-closed/)
### Why did SSH work when the website was down? [#](/docs/cloudflare-522-ports-80-443-closed/)
SSH uses port 22. Your website uses ports 80 and 443. If only port 22 is allowed, you can still connect to the server through SSH while Cloudflare and visitors cannot access the website.
### Do I need both port 80 and port 443? [#](/docs/cloudflare-522-ports-80-443-closed/)
Yes. Port 443 is required for HTTPS traffic. Port 80 is commonly used for HTTP redirects, certificate validation, and normal web handling. Allow both unless you have a specific advanced firewall design.
### Does Cloudflare 522 always mean the server is down? [#](/docs/cloudflare-522-ports-80-443-closed/)
No. A 522 can happen when the server is online but Cloudflare cannot connect to the origin web ports. That is why checking SSH, UFW rules, and web server status is important.
### Should I disable UFW to fix this? [#](/docs/cloudflare-522-ports-80-443-closed/)
No. In most cases, you should keep the firewall active and allow the required ports. Disabling the firewall can expose more services than needed.
## Still need help? [#](/docs/cloudflare-522-ports-80-443-closed/)
If the site still shows a Cloudflare 522 error after allowing ports 80 and 443, contact xCloud Support with the domain, server name, recent firewall changes, UFW status output, and any web server error shown in the xCloud logs or events.
---
# How to Use Cloudflare R2 Storage for Site Backup in xCloud? - xCloud
> Learn how to easily configure and use Cloudflare R2 storage for site backup in xCloud. It is a reliable and secure option that integrates seamlessly with xCloud.
In [**xCloud**](/), you can easily use **Cloudflare R2 storage for site backup**. It is a reliable and secure option that integrates seamlessly with xCloud. Plus, it’s budget-friendly, costing at least 10% less than S3 Standard. You even get 10GB of free storage with each account, which can be shared across different buckets. After the free 10GB, you’ll only be charged for the extra storage you use.
Ready to set up Cloudflare R2 Storage in xCloud? Let’s dive into the step-by-step guide.
## **Step 1: Create A Cloudflare Account** [#](/docs/cloudflare-r2-storage-for-site-backup/)
If you don’t have a Cloudflare account already, you need to create one. Creating a Cloudflare account is so easy – all you need to do is **[visit Cloudflare’s website](https://www.cloudflare.com/)**, click on the ‘**Sign Up**’ button & fill up all the necessary information.
## **Step 2: Create an R2 Storage Bucket** [#](/docs/cloudflare-r2-storage-for-site-backup/)
Once you’re signed in Cloudflare account, navigate to **‘R2’ → ‘Overview’** from the left panel of the dashboard. Now, click on the **‘Create Bucket’** as you need to create an R2 storage bucket for your site backup in xCloud.
Name your bucket and remember it for later recognition. Though it is optional (because R2 automatically places your bucket in the closest available region based on your location) can set your location hint. Complete this by clicking on **‘Create bucket.’**
Your bucket will be completed. Now go **‘Settings’** option & see your bucket details. If you want copy your bucket name & S3 API somewhere else for further use.
## **Step 3: Get Your R2 Credentials (Access Key ID, Secret Access Key)** [#](/docs/cloudflare-r2-storage-for-site-backup/)
The next step is to get the Cloudflare R2 credentials (Access ID, Access Key) to use in xCloud.
To do so, again navigate to **‘R2’ → ‘Overview’** from the left menu, and click on **‘Manage R2 API Tokens’** from the right corner.
Now click on the ‘**Create API token**’ button from the right of your screen. On the resulting page, choose your Token name, select the ‘Admin Read & Write’ under the Permissions, and leave the TTL as it is **‘Forever**.’ Once you set all things up, click on the ‘**Create API token**’ button from the bottom of the page.
Here comes the most important part. You’ll only be able to access the below screen once. Be sure to copy the below details, and keep them somewhere safe for further use.
- Token value
- Access Key ID
- Secret Access Key
- Use jurisdiction-specific endpoints for S3 clients
\*\*\*_**Note:**_ When using the S3 API with an R2 bucket, the region is automatically set. Specifying an empty value or “**us-east-1**” will also default to the correct region. Plus, they don’t provide any region name or code when creating the API.
## **Step 4: Configure Cloudflare R2 Storage for Site Backup in xCloud** [#](/docs/cloudflare-r2-storage-for-site-backup/)
Since you have collected everything that you need from Cloudflare end, now let’s see how you can configure Claoudflare R2 storage for site backup in xCloud.
### **1\. Login & Access New Provider** [#](/docs/cloudflare-r2-storage-for-site-backup/)
Login to your xCloud dashboard, and navigate to ‘**Team Settings’ → ‘Integrations’ → ‘Storage Provider’** & click on ‘**Add New Provider.’**
### **2\. Select Cloudflare As Storage Provider** [#](/docs/cloudflare-r2-storage-for-site-backup/)
On the resulting page, click on ‘**Select Provider**‘ to expand the dropdown option. And select ‘**Cloudflare R2**‘ as your storage provider.
### **3\. Fill Up All the Necessary Information** [#](/docs/cloudflare-r2-storage-for-site-backup/)
Now, fill in your ‘**Bucket Name’**, ‘**Access Key ID’, ‘Secret Key’**, and ‘**Endpoint’** that you are supposed to save anywhere. Once everything is done, click on **‘Submit.**’
If everything is okay, your Cloudflare R2 storage will be added to xCloud, you can use it for site backup. Here’s how it looks in your dashboard once it gets connected successfully.
### **4. Configure Site Backups Settings in xCloud** [#](/docs/cloudflare-r2-storage-for-site-backup/)
Once the integration process is done, you can move on to backup your site. As you can integrate more than one storage provider, choose one if you have multiple. For the Remote Backup Settings, choose your Bucket.
After that, you can exclude paths if required. You will find the box below the ‘**File Backup**’ field as shown below.
You can also choose to schedule ‘**Automatic Backup**’ and ‘**Automatic Delete**’. For automatic backup, you need to select backup frequency and backup time. On the other hand, you can set a value for how many days after a backup will be deleted automatically.
This is how you can easily configure and use Cloudflare R2 storage for site backup in xCloud.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Collect Stripe Publishable Key for 3D Secure Card Payments? - xCloud
> Follow the guidelines to collect stripe publishable key for 3D secure payments & implement on xCloud via onboarding flow or dashboard end.
Keeping online payments safe is essential for any business & [**xCloud**](/) always ensures its fullness. When you use Stripe, your **Stripe Publishable Key** is the way to connect your website or app to Stripe’s payment system. Combined with 3D Secure, this key helps you process payments safely and boosts customer confidence.
**Why do we need the Publishable Key from your (Reseller) account?** 3D Secure adds an extra layer of protection to your credit card transactions, helping to prevent fraud and build trust. To enable it, you will need to get your Stripe publishable key and set it up correctly.
In this guide, we’ll show you the simple steps to access your Stripe publishable key so you can start accepting 3D Secure payments from your clients.
**_Note:_** _Before heading to the process, make sure that you_ [**_connect your Stripe account with xCloud_**](/docs/setup-reseller-account-with-xcloud-white-label/).
## **Collecting Stripe Publishable Key** [#](/docs/collect-stripe-publishable-key/)
To collect the publishable key, log in to your **[Stripe](https://stripe.com/)** account & head towards the Developers option on top in the dashboard. Under the ‘**Developers**’ section, you’ll get two options—API Keys & Apps. Click on ‘**API Keys**’ & copy your Stripe ‘**Publishable Key.**’
## **Implementing Stripe Publishable Key for Allowing 3D Secure Card Payments in xCloud White Label \[Onboarding Flow\]** [#](/docs/collect-stripe-publishable-key/)
While setting up your reseller account with xCloud White Label, you’ll go through an onboarding flow. After setting up your ‘Brand’, when you reach to **‘Payment Setup’** section, you’ll get an option named **‘3D Secure Card Compatibility for Your Clients.’** Now paste your Stripe ‘**Publishable Key**’ before heading to the next step of the onboarding flow.
**_Note:_** _By any chance, if you skip this part while getting onboard, you can do it later from the dashboard end as well._
Now, let’s see how you can apply your Stripe Publishable Key in xCloud White Label from the dashboard.
## **Implementing Stripe Publishable Key for Allowing 3D Secure Card Payments in xCloud White Label \[Dashboard End\]** [#](/docs/collect-stripe-publishable-key/)
Follow the below step-by-step guide to save your Stripe Publishable Key to allow your clients to make payments safely and boost their confidence.
### **Step 1: Access xCloud White Label** [#](/docs/collect-stripe-publishable-key/)
Login to your xCloud dashboard with the right credentials, & head over to the **‘White Label’** on top and click on it. And you’ll be redirected to your White Label dashboard as shown below.
### **Step 2: Setup Stripe 3DS Card** [#](/docs/collect-stripe-publishable-key/)
Once you’re in, navigate to the **‘Settings’** → **‘Payment’** option. On the resulting page, you’ll get your Stripe Account details & an option named **‘Stripe 3DS Card Setup.**’ Now paste your Publishable Key to the respective box and click on **‘Add.’**
This is how you can easily access your Stripe Publishable Key for 3D Secure Card Payments and apply in xCloud White Label following any of the above-mentioned methods.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Configure a Business Mail account on Apple Mail - xCloud
> Learn how to configure business Mail account on Apple Mail with xCloud MailBox Addon in just a few steps.
If you want to manage emails from another account within MacOS/Apple Mail App, you can do so by setting up IMAP. This allows Apple Mail to receive and send emails using an external email provider.
Follow this guide to learn how to configure a business mail account on Apple Mail with xCloud MailBox.
## **Step 1: Gather your IMAP Info** [#](/docs/configure-a-business-mail-account-on-apple-mail/)
First, go to your MailBox, choose your mail, and head over to the ‘IMAP’ tab from the menu. Here you will find the credentials to set up the email client with Apple Mail.
> **Email:** hi@yoursite.com
>
> **Password**: \*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Incoming Server Hostname:** imap.eu.appsuite.cloud
>
> **Incoming Server Username**: hi@yoursite.com
>
> **Incoming Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Outgoing Mail Server Hostname:** pop.eu.appsuite.cloud
>
> **Outgoing Server Username:** hi@yoursite.com
>
> **Outgoing Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Port:** 993
>
> **Encryption:** TLS
### **Step 2: Go to Your Apple Mail Account** [#](/docs/configure-a-business-mail-account-on-apple-mail/)
Open Mail and **‘Add account**’ from the main menu. Select **‘Other Mail Account** and click Continue.
Then enter your Login credentials ‘**Email Address’**, enter your email account’s ‘password’ and click the Sign In button.
Next, choose ‘Account Type’ as ’IMAP’ and fill in the ‘ Incoming Mail Server’, and ‘Outgoing Mail Server’ credentials in their dedicated fields and click on the ‘Sign in’.
Specify what things you wish to sync with the server, in this example, it is ‘Notes’ and ‘Mail’. Choose and click on the ‘Done’ button.
Once the setup process is done, you can see that your MailBox is set up with Apple Mail.
And that’s it, you have successfully located your other server and verified your credentials. Just a verification email has been sent to your MailBox. Go to your MailBox and verify the email client setup with Apple Mail.
Still stuck? Contact our [dedicated support team](https://support.xcloud.host/) for any of your queries.
---
# How to Configure a Business Mail account on Gmail - xCloud
> Learn how to configure a business Mail account on Gmail with xCloud MailBox Addon in just a few steps.
If you want to manage emails from another account within Gmail, you can do so by setting up POP and SMTP access. This allows Gmail to receive and send emails using an external email provider.
Follow this guide to learn how to configure a business mail account on Gmail with wxCloud MailBox to send and receive mail easily:
## **Step 1: Gather your POP Info** [#](/docs/configure-a-business-mail-account-on-gmail/)
First, go to your MailBox, choose your mail, and head over to the ‘POP’ tab from the menu. Here you will find the credentials to set up the email client with Gmail.
> **Email:** hi@yoursite.com
>
> **Password**: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Incoming Server Hostname:** pop.eu.appsuite.cloud
>
> **Incoming Server Username:** hi@yoursite.com
>
> **Incoming Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Outgoing Mail Server Hostname:** pop.eu.appsuite.cloud
>
> **Outgoing Server Username:** hi@yoursite.com
>
> **Outgoing Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Port:** 995
>
> **Encryption:** TLS
## **Step 2: Go to Your Gmail Account** [#](/docs/configure-a-business-mail-account-on-gmail/)
Start by logging into your Gmail account and navigating to ‘**Settings’**. From there, click on ‘**See All Settings.’**
Then go to the ‘Forwarding and POP/IMAP’ tab and find the ‘POP Download’ option. Next enable the POP for all mail option and click ont he ‘Save’ button.
## **Step 3: Add a Mail Account** [#](/docs/configure-a-business-mail-account-on-gmail/)
Then, go to the to ‘**Settings’**. From there, click on ‘**See All Settings’** → ‘**Accounts’** tab. Click ‘**Add a mail account’**, which opens a new window.
Then enter your **‘POP Mail’** in the **‘Email address’** field and click on the ‘**Next’** step button.
Next, enter the ‘Username’, ‘Password’, ‘POP Server’, ‘Port’ accordingly that you have copied from the xCloud MailBox dashboard and click on the ‘Add Account’ button.
And your mail account has been added to receive emails. Now if you want to send emails form the Gmail account as well choose the option ‘Yes’ and click on the ‘Next’ button.
Next, you will see that an option ‘Import emails from my other account’ is selected, keep it selected and go to the ‘Next’.
Next, add a ‘Name’ and click on the ‘Next Step’ button to proceed.
Then go to your MailBox dashboard again and switch over to the ‘SMTP tab from the dashboard and collect the credentials:’Username’, ‘SMTP Server Name’, ‘Password‘, ‘Port for STARTTLS’ and go to the email client setup process.
Now, enter the ‘Username’ ‘SMTP Server Name’, ‘Password‘, ‘Port for STARTTLS’ into the dedicated fields and click on the ‘Add Account’ button.
And you have successfully located your other server and verified your credentials. Next, just a verification email has been sent to your MailBox. Go to your MailBox and verify the email client setup with Gmail.
And that’s it, this is how easily you can connect your email clients account with Gmail.
Still stuck? Contact our [dedicated support team](https://support.xcloud.host/) for any of your queries.
---
# How To Configure Custom NGINX In xCloud? - xCloud
> Ready to enhance NGINX? Dive into xCloud's custom config options. Configure custom NGINX for ultimate performance tweaking.
[**NGINX**](https://www.nginx.com/) is a top choice for web servers for its adaptability and strength. Many online services and applications use NGINX and customize it to boost their system’s efficiency, secure their data, and add new features. However, you might find it challenging to **configure custom NGINX** settings, as it often requires manual edits in the Linux terminal.
But, with [**xCloud**](/), you can simplify this process. If you add a custom NGINX in xCloud, it lets you easily modify NGINX settings right from the xCloud dashboard, without using any extra command lines.
## **Understanding The NGINX Config** [#](/docs/configure-custom-nginx-xcloud/)
NGINX is an **open-source web server** that provides reverse proxy, load balancing, and caching capabilities. It has HTTPS server capabilities and is primarily intended for optimal performance and stability.
In xCloud, the NGINX server settings are customizable through configuration files in the **_/etc/NGINX/_** folder. The main configuration file can be located at **_/etc/NGINX/xcloud-conf_**.
## **Configure Custom NGINX In xCloud: A Step-By-Step Guide** [#](/docs/configure-custom-nginx-xcloud/)
With xCloud’s **Custom NGINX Config** feature, you can add a new configuration directly from the xCloud dashboard. Here, you can add custom configurations for before, after, and inside server blocks. Follow the guide to learn how you can configure custom NGINX in xCloud.
### **Step 1: Navigate To The NGINX Tab In xCloud** [#](/docs/configure-custom-nginx-xcloud/)
Log in to your [**xCloud dashboard**](https://app.xcloud.host/) and choose the website for which you want to add a custom NGINX. From the left navigation menu, click on the NGINX option.
### **Step 2: Add A Custom NGINX** [#](/docs/configure-custom-nginx-xcloud/)
From this tab, you need to tap the ‘**Add a New Config**’ button to configure a custom NGINX. You can run and debug a custom config or save this for later use purposes.
You can choose one from **4 NGINX types**: Before Server Block, Inside Server Block, and After Server Block. You can then choose a file name, ‘**Run & Debug**’ a custom NGINX, or ‘**Save Config**’.
1. If you choose the ‘Before Server Block’ and set a Config File Name, the Config will be generated as **_/etc/NGINX/xcloud-conf/(sitename)/before/(Config File Name)._**
2. For ‘Inside Server Block’ and a Config File Name, the Config will be generated as **_/etc/NGINX/xcloud-conf/(sitename)/server/(Config File Name)._**
3. For ‘After Server Block’ and a Config File Name, the Config will be generated as **_/etc/NGINX/xcloud-conf/(sitename)/after/(Config File Name)._**
4. If you choose Inside PHP Location Block, it will be placed inside the PHP location block in the relevant server configuration.
5. If you choose ‘Inside Proxy Location Block’**,** it will be placed inside the location block used for proxying non-PHP applications.
For example, if you choose the ‘**Inside Server Block**’ and set the Config File Name as ‘**rankmath**’ for the site ‘**summer-star-195.xcloud.name**’, the config will be generated as **/etc/NGINX/xcloud-conf/summer-star-195.xcloud.name/server/rankmath.conf.**
Now, using the Config Content below for example:
\# START NGINX Rewrites for Rank Math Sitemaps
rewrite ^/sitemap\_index.xml$ /index.php?sitemap=1 last;
rewrite ^/(\[^/\]+?)-sitemap(\[0-9\]+)?.xml$ /index.php?sitemap=$1&sitemap\_n=$2 last;
rewrite ^/(\[a-z\]+)?-sitemap\\.xsl$ /index.php?xsl=$1 last;
\# END NGINX Rewrites for Rank Math Sitemaps
You can then choose to ‘**Run & Debug**’ or ‘**Save Config**’.
If you are using Custom NGINX for HideMyWP, make sure to change your settings in the plugin like this, as shown below.
If your custom NGINX command and configurations are okay, you will see a green message upon clicking the ‘Run & Debug’.
However, if there are some issues with your configuration and command, you will see a red message.
Once you add a custom NGINX config successfully, it will be listed on the ‘**Custom NGINX Config**’ tab. From here, you can edit or delete a config. Additionally, you can preview your configuration.
## **Custom NGINX Templates** [#](/docs/configure-custom-nginx-xcloud/)
For now, we are offering built-in custom NGINX support for Rankmath and Hide My WP on the xCloud dashboard. That means, If your website has the [**Rankmath**](https://wordpress.org/plugins/seo-by-rank-math/) or [**Hide My WP**](https://wordpress.org/plugins/hide-my-wp/) plugins installed, you can choose from the ‘**Select Template**’ list and you’re all good to go. Or else, you can choose ‘**Use My Own Config**’ to run your config manually. However, we will be gradually adding more plugins.
That is how easily you can configure custom NGINX in xCloud.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Configure Your Email Client with xCloud Mailbox Addon - xCloud
> Learn how to configure your email client with the xCloud Mailbox Addon using IMAP or POP for secure, seamless email access on any device.
The **xCloud Mailbox Addon** allows you to integrate your email account with popular email clients like Gmail, Microsoft Outlook, Thunderbird, Windows Mail, and iOS Mail. By configuring an email client, you can send and receive emails directly from your desktop or mobile device, providing a seamless and efficient communication experience without relying solely on webmail.
This guide walks you through the complete process of configuring your preferred email client using **IMAP/POP protocols**, ensuring secure and reliable access to your xCloud mailbox.
## **Step 1: Create Your Email Account** [#](/docs/configure-email-client-with-mailbox-addon-xcloud/)
To proceed, you need to create a MailBox first. If you have not created any MailBox yet, read this detailed documentation:
[**_How to Set Up xCloud MailBox Addon_**](/docs/how-to-set-up-xcloud-mailbox-addon/)
## **Step 2: Gather your IMAP/POP Info** [#](/docs/configure-email-client-with-mailbox-addon-xcloud/)
After accessing the **IMAP and POP tab** in your xCloud Mailbox dashboard, you will find all the necessary credentials to configure your email account. Before proceeding, it’s important to understand the difference between **IMAP** and **POP** as each serves a different purpose.
**IMAP (Internet Message Access Protocol)** is the recommended option for most users. It allows for two-way synchronization between your email client and the server, meaning any changes you make—such as reading, deleting, or moving messages—will reflect across all your devices. This makes IMAP ideal if you plan to access your email from multiple devices like your smartphone, tablet, or computer.
On the other hand, **POP3 (Post Office Protocol v3)** is designed for downloading emails to a single device. Once downloaded, emails are typically removed from the server, and any changes made on one device won’t sync to others. POP3 is best suited for users who only check their email on one device and prefer to store their emails locally.
Choose the email setup that works best for you: IMAP for syncing your email on multiple devices or POP for accessing your email on just one device. Then, gather the setup details from your dashboard to continue configuring your email client.
### **For IMAP:** [#](/docs/configure-email-client-with-mailbox-addon-xcloud/)
> **Email:** hi@yoursite.com
>
> **Password**: \*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Incoming Server Hostname:** imap.eu.appsuite.cloud
>
> **Incoming Server Username**: hi@yoursite.com
>
> **Incoming Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Outgoing Mail Server Hostname:** pop.eu.appsuite.cloud
>
> **Outgoing Server Username:** hi@yoursite.com
>
> **Outgoing Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Port:** 993
>
> **Encryption:** TLS
### **POP** [#](/docs/configure-email-client-with-mailbox-addon-xcloud/)
> **Email:** hi@yoursite.com
>
> **Password**: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Incoming Server Hostname:** pop.eu.appsuite.cloud
>
> **Incoming Server Username:** hi@yoursite.com
>
> **Incoming Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Outgoing Mail Server Hostname:** pop.eu.appsuite.cloud
>
> **Outgoing Server Username:** hi@yoursite.com
>
> **Outgoing Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Port:** 995
>
> **Encryption:** TLS
### **Step 3 – Configure your email client** [#](/docs/configure-email-client-with-mailbox-addon-xcloud/)
Although various email clients and devices have distinct configurations, they all have fundamental setup requirements in common. For more information, select your device from the list below:
- [Smartphones and tablets](/docs/how-to-configure-a-business-mail-account-on-phone-using-gmail/)
- [Mac devices](/docs/configure-a-business-mail-account-on-apple-mail/)
- [Gmail](/docs/configure-a-business-mail-account-on-gmail/)
- Windows
- Other Email clients
If your device or email application is not included in the list, consult a similar guide or look online for the official documentation.
Still stuck? Contact our **[support team](https://support.xcloud.host/)** for any of your queries.
---
# How to Configure Integration with Telegram in xCloud Hosting? - xCloud
> Learn how integration with Telegram in xCloud hosting for real-time site notifications to enhance your team's coordination effortlessly.
[**xCloud**](/) offers a feature called ‘**Integration with Telegram**’ to receive site notifications in the Telegram app. With just a few clicks, you can seamlessly integrate Telegram into xCloud hosting to enhance your notification management. By integrating with [**Telegram**](https://telegram.org/), you can receive real-time server and site notifications, along with team activity updates, directly within your Telegram app, ensuring you stay connected and informed at all times.
Follow the step-by-step guide to learn how to integrate Telegram in xCloud hosting to enhance team coordination and efficiency.
## **Step 1: Add New Notification** [#](/docs/configure-integration-with-telegram-in-xcloud/)
Once you login to your **xCloud account**, go to **Integrations → Notification** on the dashboard. Then, click on ‘**Add New Notification**’ to connect Telegram to your xCloud hosting.
## **Step 2: Integration with Telegram in xCloud** [#](/docs/configure-integration-with-telegram-in-xcloud/)
After clicking on ‘**Add New Notification**’ choose ‘**Telegram**’. Now copy the authentication command by clicking on the ‘**Copy**’ button & go to Telegram @**xCloudhostingbot** to start your chat to integrate Telegram in xCloud.
In the Telegram app start your chat with the xCloud Notification bot and send the copied authentication command token. The notification bot will confirm that you are ready to authorize notifications with xCloud.
Now, click on the ‘**Authorize on Telegram**’ button and a notification will appear to confirm Telegram is connected with xCloud.
Now, in the ‘**List of Notifications,**‘ you can see your connected Telegram title along with its Type, Status, and Action. To disconnect your Telegram from xCloud, just click on ‘**Disconnect**‘ under Action then ‘**Ok**’ to confirm.
## **Step 3: Choose the Notifications You Want to Get** [#](/docs/configure-integration-with-telegram-in-xcloud/)
To choose which notifications you want to receive in your Telegram, go to **Team Settings → Notifications**. Then, check the Telegram options for ‘**Server**,’ ‘**Site**,’ or ‘**Other**‘ that you want to receive notifications for, and click on ‘**Save Changes**.’
This is how you can easily configure Telegram with xCloud hosting & get your server, site notifications along with team accounts and actions directly into your Telegram.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# Configure Mailgun For Site Emails - xCloud
> Minimize spam risks and optimize email delivery on xCloud with Mailgun. Learn how to configure Mailgun, authenticate domains, and integrate with SMTP or API.
[**xCloud hosting**](/) recognizes the importance of well-integrated email systems like Mailgun to minimize the risk of emails being marked as spam or failing to reach their intended recipients. So, it has streamlined the way to configure Mailgun into its environment for site emails.
**[Mailgun](https://www.mailgun.com/)** is one of the most popular email delivery services that combines powerful features and compatibility to ensure a more innovative mailing experience. Plus, it’s one of the cheapest options available. You can send **up to 5000 emails** per month on the Free plan. On the other hand, it will cost you **$0.001 per email** on the Flex plan.
Follow the step-by-step guide below to learn how to configure Mailgun for your site emails.
## **Step 1: Domain Authentication With Mailgun** [#](/docs/configure-mailgun-for-site-emails/)
Before getting started with the Mailgun integration into your xCloud team, you need to authenticate your domain with the email service. Please follow their detailed documentation on how you can do that: [**Mailgun Domain Verification Walkthrough**](https://help.mailgun.com/hc/en-us/articles/32884702360603-Domain-Verification-Setup-Guide)**.**
## **Step 2: Integrate Mailgun into xCloud** [#](/docs/configure-mailgun-for-site-emails/)
Once you authenticate your domains with Mailgun, you can integrate the email service into the xCloud environment by following these two methods:
- **Integrate Mailgun With SMTP Credentials**
- **Integrate Mailgun With API**
### **Integrate Mailgun With SMTP Credentials** [#](/docs/configure-mailgun-for-site-emails/)
[**Log in**](https://login.mailgun.com/login/) to your Mailgun account and navigate to **Sending → Domains** from the dashboard. Then navigate to the **Domain Settings → SMTP Credentials.** Add a new domain by tapping the ‘**Add new domain**’ button. Once you add the domain, save your login credentials (username and password) for using it in the xCloud mail integration.
Once you are done collecting your SMTP credentials for Mailgun, it’s time to add Mailgun as the email provider in xCloud. From your xCloud dashboard, navigate to **My Profile → Integrations → Email Provider**. You need to integrate your Mailgun account domain with the credentials by clicking the ‘**Add New Provider’** button.
Once you hit the ‘**Add New Provider**’ button, you will see a pop-up asking you to select the email provider, SMTP username, and SMTP password.
Select Mailgun as the provider, and input your credentials in the **SMTP username** and **SMTP password** fields. The email provider will be added instantly.
### **Integrate Mailgun With API** [#](/docs/configure-mailgun-for-site-emails/)
Alongside using the Mailgun SMTP credentials, you can integrate Mailgun with the API keys. For that, log in to your Mailgun account and navigate to **API Security** page. Add a new key by clicking the ‘**Add new key**’ button and setting a description. Save your API key for future use.
From your xCloud dashboard, navigate to **My Profile → Integrations → Email Provider**. You need to integrate your Mailgun account domain with the credentials by clicking the ‘**Add New Provider’** button.
Once you hit the ‘**Add New Provider**’ button, you will see a pop-up asking you to select the email provider name. Select **Mailgun API** as the provider, and input your collected API from the **Mailgun API Security** page. Then, provide your authenticated domain name and hit the ‘**Add Email Provider**’ button.
That’s how easily you can integrate Mailgun into your xCloud team with API keys.
## **Step 3: Testing Your Email Integration** [#](/docs/configure-mailgun-for-site-emails/)
After adding Mailgun successfully, you can test your email service by sending a test email straight from the **Email Provider** section.
## **Step 4: Add Mailgun Service To Site** [#](/docs/configure-mailgun-for-site-emails/)
After integrating Mailgun into your xCloud environment, you need just to add the provider to the site. Go to **All Sites** and choose your website to add the email provider. Select your site and navigate to **Email Provider** tab.
Now select your domain from the ‘**Email Provider**’ options, set the sender’s name in the ‘**From Name**’ field, and input your email sender’s address in the ‘**From Email**’ field. Once done, hit the ‘**Add This Provider To Site**’ button.
If you don’t find it convenient to configure your site emails with Mailgun using the SMTP credentials or API, you can check the process of configuring with the Mailgun plugin below.
## **Configure Site Emails With Mailgun Plugin** [#](/docs/configure-mailgun-for-site-emails/)
Get started by signing up for an [**account.**](https://signup.mailgun.com/new/signup) Follow the [**Quickstart Guide**](https://documentation.mailgun.com/docs/mailgun/quickstart) to verify your domain, and once it’s confirmed, your API key will be revealed and ready for use!
Click on your profile, and from the dropdown menu, select **API Keys**. Collect your **private key** and copy it for using it on your WordPress dashboard.
Now, you need to install the Mailgun plugin on your WordPress site. Follow these simple steps below:
- Log in to your WordPress site.
- Visit the Add Plugins page.
- Search for “[**Mailgun for WordPress**](https://wordpress.org/plugins/mailgun/)” and install the plugin.
- Access the Mailgun screen from the Settings menu.
- Enable Use HTTP API to **Yes**.
- Enter your Mailgaun domain in the **Domain Name** field.
- Copy and paste your Private API key into the **API Key** field.
- Save the changes and click Test Configuration to send a test email.
After saving all the changes:
- Save the settings after configuration.
- Send a test email to ensure proper setup.
- If errors occur, check if DNS settings are still propagating or if settings are misconfigured.
- Ensure the Mailgun domain status shows as “Active.”
- Upon successful sending, you’ll receive a confirmation email with the following text:
- If you have received this message, as shown in the image, the requested test has succeeded.
That’s how easily you can **configure Mailgun for site emails** for xCloud environment as an **[SMTP provider](/docs/setting-up-site-emails-for-wordpress-on-xcloud/)** to streamline the email delivery process of transactional emails.
Still stuck? Contact our **[support team](/support/)** for any of your queries.
---
# How to Configure MySQL and MariaDB with xCloud - xCloud
> Learn how to configure MySQL and MariaDB using xCloud for better performance and stability.
Managing your database server the right way is essential for performance, stability, and data protection. Whether you use MySQL or MariaDB, configuring your settings based on your server’s needs will help you get the most out of your setup. Follow the guide to configure MySQL and MariaDB using xCloud and explain the key configuration options in simple terms.
## **How to Configure MySQL for Your Server** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
You can [**manage MySQL**](https://www.mysql.com/) settings directly from the xCloud control panel. Follow the steps below to modify key database parameters of MySQL that affect performance and stability.
### **Step 1: Go to the Server** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
Go to your server. From the sidebar, go to ‘**Management’** and then click on ‘**MySQL Configuration’**.
### **Step 2: Adjust the Configuration options** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
Here you will find all the configuration options **‘Max Connections’, ‘Max Allowed Packet’, ‘InnoDB Buffer Pool Size’, ‘InnoDB Buffer Pool Instances’, ‘InnoDB Flush Log at Transaction Commit’, ‘Slow Query Log’, ‘Long Query Time’, ‘Sort Buffer Size’, ‘Binary Log Expire Time’, ‘InnoDB Flush Method’**.
You can change these settings based on your server’s workload and resource availability.
### **Step 3: Apply Changes** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
After you adjust the settings based on your server’s needs, review the values and click on the **Save Changes** button. The new configuration will be applied immediately.
## **How to Configure MariaDB for Your Server** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
Just like MySQL, you can adjust MariaDB configuration from the xCloud control panel. Follow the steps below to modify key database parameters of MariaDB and apply changes based on your server’s needs.
### **Step 1: Go to the Server** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
Go to your server. From the sidebar, go to ‘**Management’** and then click on ‘**MariaDB Configuration’**.
### **Step 2: Adjust the Configuration options** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
Here you will find all the configuration options **‘Max Connections’, ‘Max Allowed Packet’, ‘InnoDB Buffer Pool Size’, ‘InnoDB Buffer Pool Instances’, ‘InnoDB Flush Log at Transaction Commit’, ‘Slow Query Log’, ‘Long Query Time’, ‘Sort Buffer Size’, ‘Binary Log Expire Time’, ‘InnoDB Flush Method’**.
You can change these settings based on your server’s workload and resource availability.
### **Step 3: Apply Changes** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
After you adjust the settings based on your server’s needs, review the values and click on the **Save Changes** button. The new configuration will be applied immediately.
## **Configuration Options for MySQL and MariaDB** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
When you configure MySQL or MariaDB, you will deal with several important settings. These settings affect how well your server performs, how stable it stays under pressure, and how safe your data is. Here is a simple explanation of each option so you can make informed decisions.
### **Max Connections** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This setting controls the maximum number of client connections that your database can handle at the same time. If your application has many users, increase this value based on your server’s CPU and RAM. Too many connections without enough resources will cause connection errors.
### **Max Allowed Packet** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This sets the maximum size of a packet that your server can handle in a single transaction. If your application sends large data chunks, such as files or long queries, you may need to raise this value. Use values like 64M or 128M, depending on your needs.
### **InnoDB Buffer Pool Size** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This defines how much RAM is used to cache data and indexes. It is a major factor in overall performance. A good rule is to allocate 70 to 80 percent of available memory for this setting. Use 128M for smaller systems, or 1G and higher for large workloads.
### **InnoDB Buffer Pool Instances** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This option breaks the buffer pool into multiple parts. Doing so helps performance, especially if your server has multiple CPU cores. It reduces contention and allows smoother handling of concurrent queries. In MariaDB, this feature is maintained by MariaDB, ensuring optimized performance tailored for its database environment.
### **InnoDB Flush Log at Transaction Commit** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This controls how often transaction logs are written to disk. There are three settings:
- 0 gives the best speed but risks losing recent data if the server crashes.
- 1 is the default and ensures the highest data safety.
- 2 is a balance between performance and durability.
Pick the one that fits your data safety needs.
### **Slow Query Log** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
Turn this ON if you want to track slow queries. It helps you detect performance issues. The log file is usually stored at /var/log/mysql/mysql-slow.log. You can disable it when you do not need it.
### **Long Query Time** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This works with the slow query log. It sets the time (in seconds) that a query must run before being labeled as “slow.” Adjust it to match your idea of slow performance.
### **Sort Buffer Size** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This controls how much memory is used for sorting operations like ORDER BY or GROUP BY. If your application performs a lot of sorting, increasing this value can help. Use values between 256K and 2M, depending on your server memory.
### **Binary Log Expire Time** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This setting defines how long binary logs are kept before deletion. These logs help with replication and recovery but can use up disk space. Setting a shorter expiry time will free up space automatically.
### **InnoDB Flush Method** [#](/docs/configure-mysql-and-mariadb-with-xcloud/)
This setting controls how data is written to disk. Your choice depends on your storage device.
- fsync is standard and works well for most setups.
- O\_DIRECT is good for SSDs and helps reduce memory use by skipping the OS cache.
- Other options like O\_DSYNC, littlesync, nosync, and O\_DIRECT\_NO\_FSYNC offer different performance trade-offs.
If you are using SSD storage, O\_DIRECT is usually the best option.
Make sure you adjust these settings based on your actual server usage and the hardware resources available. With proper configuration, both MySQL and MariaDB can deliver strong performance and high reliability.
And that’s it, this is how easily you can configure MySQL and MariaDB for your server in just a few clicks.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How To Configure Server Backup Management In xCloud? - xCloud
> Secure your website! Learn how to easily configure server backup management in your xCloud dashboard to recover from crashes or disasters.
Server backups on your hosting platform are lifesavers for your website. It ensures a copy of everything, including files, databases, and images is stored securely off-site. These backups are essential for bouncing back from disasters like crashes, cyberattacks, or even accidental deletions. With [**xCloud**](/), you can easily configure **server backup management** straight from your dashboard.
The Server Backup Management feature at xCloud is now available for:
- xCloud server
- Vultr server
_**Important:** Server backup is an **optional add-on for xCloud Managed Servers with an additional 20% cost**._
We will be adding more providers for this feature soon. However, the billing of the providers (other than xCloud) will be handled by their end.
Follow this step-by-step guide to learn how to configure server backup management in xCloud.
## **Step 1: Create A Server & Enable Backup** [#](/docs/configure-server-backup-management/)
Log in to your [**xCloud dashboard**](https://app.xcloud.host/) and create a new server by tapping on the ‘**\+ New Server**’ button. Choose all the resources and set all the details. Drop down and you will find the option to enable the backup. Toggle the button to turn on server backup while adding a new server.
If you are an xCloud LTD user, you will find the option to bring the xCloud-managed provider’s server. Once done, hit the next screen, and your server will automatically finish setting up.
## **Step 2: Configure Server Backup Management** [#](/docs/configure-server-backup-management/)
Once you are on the server overview page, tap on the ‘**Backup**’ tab. Here, you will find the button to enable backup. It will add backups on the cloud provider, and you will see a list of backups here. Once done, hit the ‘**Save Settings**’ button.
If you have brought your own server or use another service like [**Vultr**](https://www.vultr.com/)**,** the billing, and cost of server backup and management will be handled on that provider’s end.
After you toggle the button to enable backup, you will have the option to choose the ‘Provider Backup Schedule’. Select one of the backup frequency options (Daily, Weekly, Monthly, Every Even Day, or Every Odd Day). If you choose monthly, you will also see another option to select the day of the month.
Additionally, you can choose a backup time. Once choosing your preferences, hit the ‘**Update Scheule**‘ button.
However, for xCloud managed or Vultr providers, you might not find the Server Backup option if it’s not enabled from the ‘**team management**‘ page. In that case, you need to ask your team admin to enable the ‘**servermanage-provider-backup**‘ option, as shown below:
If you are choosing another provider other than xCloud, you might need to select the backup volume or interval on the provider’s end. Typically, Vultr offers backups once a week by default. But, you can change the interval to daily or even monthly.
## **Special Notes To Keep In Mind** [#](/docs/configure-server-backup-management/)
- Be careful before you delete a server. If you delete a server, all the server’s backup will be removed too.
- Your server backups are performed once a week by default. You can have two backups on the backup list at a time. If there are two backups already available and a new backup is created, xCloud will automatically delete the older version of the previous two backups. Also, if you restore a backup, your most recent data or progress will be lost as you are restoring the files and data from the backup file.
- We do not allow anyone to repeatedly turn on or off the automatic backup option to prevent system abuse. If you disable the feature after turning it on for a server, you cannot enable it again. However, if you disable backups for a server by mistake, please contact support to re-enable it.
That is how easily you can configure server backup management in xCloud.
Still, feeling stuck? Contact our [**support team**](https://support.xcloud.host/) for assistance.
---
# How to Configure Slack Integration in xCloud Hosting? - xCloud
> Follow the guide to learn how to configure Slack integration in xCloud hosting & easily collaborate, communicate with your team.
Effective communication is vital for seamless collaboration and productivity. With that in mind, [**xCloud**](/) Hosting brings an innovative solution through Slack integration, empowering users to streamline communication effortlessly within their team hosting environment. With this integration, you can get server notifications, site notifications, and more on your Slack.
Follow the step-by-step guide to learn how to **configure Slack integration in xCloud** hosting to enhance team coordination and efficiency.
_**Note:** Before getting started, you will need to visit the xCloud website and you have to sign up or log in to xCloud with your credentials._
## **Step 1: Add New Slack Notification** [#](/docs/configure-slack-integration-in-xcloud/)
After logging in to your xCloud account, navigate to **Team Settings** → **Integrations** → **Notification.** Once you’re in, click on **‘Add New Notification’,** select your provider as **‘Slack’** from the dropdown, and click on ‘**Authorize on Slack.**’
## **Step 2: Give Permission Access & Select Slack Channel** [#](/docs/configure-slack-integration-in-xcloud/)
On the resulting page, xCloud requires a channel to post to as an app. Since xCloud is requesting permission to access here, you need to select a channel from the dropdown **“Share for a Channel”**, and click on **‘Allow’** for the further step.
Wait for a few seconds & your Slack channel will be connected with your xCloud hosting. This is how easy it is to configure Slack integration in xCloud hosting.
## **Step 3: Select Notifications You Want in Your Prefered Slack Channel** [#](/docs/configure-slack-integration-in-xcloud/)
After connecting your Slack channel to xCloud hosting, you’ll get options to choose which notifications (e.g., **Server Notifications, Site Notifications, Other Notifications**) you want to get in your selected Slack channel as shown below. To do so, navigate to **Team Settings** → **Notifications**.
Just click the **‘Slack’** option beside each notification to enable and disable the option. Once you’re done with the selection, don’t forget to click the ‘**Save Changes**’ to save all the changes you made.
**Note:** _The role permission of integrations & notifications can only be managed by the Team Admin role user in xCloud._
This is how you can easily configure Slack integration in xCloud hosting & communicate with your team with the Slack conversations that you choose.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Control OPcache With xCloud - xCloud
> Learn how to quickly enable PHP OPcache on your server using xCloud for improved application performance.
OPcache is a PHP extension that enhances performance by storing precompiled script bytecode in memory. This allows PHP scripts to execute more quickly by avoiding the overhead of parsing and compiling code on each request. Enabling OPcache can significantly improve the efficiency of your PHP applications.
Follow the steps to learn how to enable OPcache on your server with xCloud.
**_Note:_** _OPcache is compatible with PHP versions 5.6 through 8.4. Ensure your server is running a supported PHP version before proceeding._
## **Step 1: Access the PHP Configuration** [#](/docs/control-opcache-with-xcloud/)
To begin, log in to your xCloud server management dashboard. From the main interface, navigate to the **Management** section and select **PHP Configuration**. This will take you to the configuration settings where you can manage various PHP extensions and options.
## **Step 2: Enable OPCache** [#](/docs/control-opcache-with-xcloud/)
Once you are on the PHP Configuration page, scroll down to access the ‘**PHP OPcache’** option. To enable OPcache, simply toggle the corresponding switch. This action activates OPcache on your server, and no further configuration is needed.
And that’s it. This is how easily you can enable OPCache with xCloud and ensure faster script execution and enhanced overall application efficiency.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Create a Database for Your Site with xCloud? - xCloud
> Learn how to create a database for your site or web application in xCloud with easy step by step process.
xCloud makes it easy to create a database and manage it for your site or web application, whether you are using MySQL or MariaDB. This guide will walk you through the steps to set up a new database and a new database user. You will be able to handle everything from choosing the server to setting access permissions, all from within the xCloud dashboard. Follow these simple steps, and you will have your database and user up and running in no time!
## **Step 1: Choose the Server** [#](/docs/create-a-database-for-your-site-web-application/)
To begin, select the server where you want to create a database. Navigate to the left sidebar and find the Management section. From the dropdown, select Database.
## **Step 2: Create the Database** [#](/docs/create-a-database-for-your-site-web-application/)
Once you have selected your server, proceed to create the database. Click the **‘Add Database’** button. A pop-up window will appear.
Enter a **Database Name** and **Username** for the database. A password will be automatically generated for the database, but you can change it if needed. After entering the necessary details, click the **‘Add Database’** button to create the new database.
## **Step 3: Create a Database User** [#](/docs/create-a-database-for-your-site-web-application/)
After you create the database, you can add new users and assign them the necessary access permissions. On the dashboard, locate and click the **‘Add Database User’** button. A pop-up window will appear.
Enter a **Username** for the new user. A password will be automatically generated for the user, though you can change it to one of your preference. Set the user’s access permissions. Choose the database the user should have access to. Finally, click **‘Add New User’** to save the user.
## **Step 4: Access New Database and User** [#](/docs/create-a-database-for-your-site-web-application/)
After you have created the new database and user, both will appear in your xCloud dashboard. You can now manage your databases and users directly from here.
With these simple steps, you can efficiently create a database and manage users effortlessly in xCloud!
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Create a Demo Site in xCloud? - xCloud
> Need a test site? xCloud lets you create a demo site in just a few clicks. Follow our step-by-step guide to configure, test, and launch seamlessly!
With [**xCloud**](/), you can easily **create a demo site** in a few clicks and test everything before going live. A demo site serves as a test website where you can migrate sites, run experiments, use all necessary plugins and themes, and more with a temporary domain before going live.
On the other hand, [**a staging environment**](/docs/how-to-create-a-staging-environment-in-xcloud/) lets you push and pull site data between staging and production sites. Follow this step-by-step guideline below to learn how to create a demo site in xCloud.
## **Step 1: Add New Site & Add Information** [#](/docs/create-a-demo-site-in-xcloud/)
Log in to your [**xCloud dashboard**](https://app.xcloud.host/) and click the ‘**+New Site**’ to add a new site. Then, choose a server from the list and go ‘**Next**’.
We will be creating a fresh WordPress site here. So choose the ‘**Install New WordPress Website**’ option as shown below.
## **Step 2: Configure & Install Your Demo Site** [#](/docs/create-a-demo-site-in-xcloud/)
Now, instead of going live, you need to choose ‘**Demo Site**’ in this section as shown below. Your new WordPress site will be a demo site, so you can run some tests and experiments before sending it live.
Before continuing, please note that xCloud provides demo domains as **‘.wp1.site’** and **‘.wp1.sh**’. The demo domains are subdomains of wp1.site and wp1.sh and team xCloud uses Cloudflare to manage these domains. You can choose between any of these. Once you go from **Demo to Live**, you cannot go back to the Demo domain again.
Set a name for your demo site and add relevant tags. Your staging domain will be generated automatically. Now, scroll down to configure more settings, such as Multisite, Caching, Email Provider, and Blueprints as you need.
At the bottom, you will see another option for ‘**More Advanced Settings**’, where you can set and choose admin details, WordPress Version, PHP Version, manage database, and more.
Once you are done with all the configurations and adjustments, hit the ‘**Next**’ button. Within a few minutes, your demo site will be ready & you will be able to manage everything on your site from the xCloud dashboard.
## **Final Outcome** [#](/docs/create-a-demo-site-in-xcloud/)
Here is the outcome of your demo site’s environment below. xCloud provides this demo site to do all the development to your site with a temporary domain. When you are ready with everything on your site, simply select the ‘**GO LIVE**’ option and add your own domain to make the site available to your user/visitor.
This is how easily you **can create a demo site** in xCloud.
Still feeling stuck? Contact our [**dedicated support team**](/support/) for further assistance.
---
# How to Create a New Product in xCloud White Label - xCloud
> Learn how to create a new product or a custom package for reseller in xCloud White Label easily.
xCloud provides an efficient way to create custom hosting packages, enabling you to resell hosting services under your own brand through the xCloud White Label program.
By setting up your server within the xCloud white label dashboard, you can start offering customized hosting plans to your customers. This guide will walk you through the step-by-step guide on how to create a new product or a custom package in xCloud.
## **Step 1: Log In to Your xCloud Dashboard** [#](/docs/create-a-new-product-in-xcloud-white-label/)
First, log in to your xCloud dashboard using your credentials. Once you are logged in, navigate to the ‘**White Label’** tab on the dashboard. Clicking on this tab will redirect you to the xCloud White Label landing page, where you can manage your white label settings and create custom hosting packages.
## **Step 2: Create Custom Hosting Packages** [#](/docs/create-a-new-product-in-xcloud-white-label/)
On the dashboard of White Label, click on the **‘Add Product’** button to begin creating your custom hosting package. A popup window will appear with server configuration options.
Here, you can choose your server plan by selecting between ‘**General’** and ‘**Premium’** plans based on your needs.
Next, select your desired server size from the available options. As you select different plans and server sizes, you will be able to see the corresponding prices. Once you have made your selections, click on the ‘**Next’** button to proceed.
## **Step 3: Customize Your Hosting Plan** [#](/docs/create-a-new-product-in-xcloud-white-label/)
In this step, you will customize the details of your hosting package. Enter a unique **‘Plan Name’** for your package or keep it blank and it will take the original product you have choosen. In the **‘Custom Price/Month’** field, set the monthly price you wish to charge your customers and then provide a ‘**SKU’** (Stock Keeping Unit). You can also deactivate any package by clicking on the ‘Active Package’ button. Once all the details are filled out, you can make it immediately available for purchase by clicking on the **‘Save and Publish’** button.
**_Note:_** _Remember, your custom price needs to be higher than the server cost to ensure you make a profit. Also, the Stripe fees will be handled by the Reseller._
## **Final Outcome** [#](/docs/create-a-new-product-in-xcloud-white-label/)
After completing these steps, you will be able to see your newly created product in the dashboard under your list of plans. Your custom hosting package is now ready to be offered to your customers under your own branding.
That is it! You have successfully created a customized package in xCloud White Label. You can now continue to add more packages or manage your existing ones to grow your hosting business.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Create a Paperless-ngx Superuser With xCloud - xCloud
> Create a Paperless-ngx superuser from the xCloud dashboard using the Commands interface. Follow this step-by-step guide to identify the container, run the Docker command, and access the admin panel quickly.
Some users install **Paperless-ngx** on their server but cannot access the admin panel because no superuser account exists. Paperless-ngx requires an administrative user to log in and manage documents, users, and system settings. Normally, the platform creates this account through an interactive terminal command.
The issue appears when the user works from the **xCloud dashboard**. The Commands interface in xCloud runs commands in a **non-interactive environment**, which means the standard createsuperuser command cannot prompt for a username and password.
This guide explains how to solve that problem by creating a **Paperless-ngx superuser directly from the xCloud Commands interface**. The process uses Docker commands and environment variables to bypass the interactive prompt and create the admin account successfully.
The steps below will help you:
- Identify the correct Paperless-ngx Docker container
- Run the command required to generate a superuser
- Verify that the account was created successfully
Follow the steps to log in to the Paperless-ngx dashboard and manage your installation normally.
## **Step 1: Identify the Docker Container Name** [#](/docs/create-a-paperless-ngx-superuser-with-xcloud/)
Since container names in xCloud are dynamically generated (e.g., containing unique strings like g27hx), you must first identify the exact name of your webserver container.
1\. Log in to your xCloud Dashboard.
2\. Navigate to Servers > Select your Server.
3\. Go to Management > Commands.
4\. Run the following command:
```
docker ps
```
Copy to Clipboard
5\. Look for the image associated with paperlessngx. You are looking for a name similar to:
paperlessngx-g27hx-cloudapp-web
6\. server-1
### Step 2: Execute the Superuser Creation Command [#](/docs/create-a-paperless-ngx-superuser-with-xcloud/)
Once you have the container name, you can trigger the creation of the superadmin account. Because the xCloud Command tool is non-interactive, we pass the password as an environment variable and use the –noinput flag.
1. In the same Commands interface, clear the previous input.
2. Paste the following command (replace \[YOUR\_CONTAINER\_NAME\] with the name found in Step 1):
```
docker exec -e DJANGO_SUPERUSER_PASSWORD='Pass@#123' [YOUR_CONTAINER_NAME] python3 manage.py createsuperuser --noinput --username superadmin --email superadmin@example.com
```
Copy to Clipboard
_Security Note: It is highly recommended to log in to the Paperless-ngx web interface immediately after this step to change the password from the default password._
### Step 3: Verification [#](/docs/create-a-paperless-ngx-superuser-with-xcloud/)
After running the command, the output log in xCloud should indicate:
Superuser created successfully.
You can now navigate to your Paperless-ngx URL and log in with:
- Username: superadmin
- Password: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
## **Alternative Method: SSH (Recommended)** [#](/docs/create-a-paperless-ngx-superuser-with-xcloud/)
**While the xCloud dashboard is convenient, using SSH is the most robust method for managing Docker containers. If you have SSH access configured:**
1\. Connect to your server via terminal: ssh user@your-server-ip.
Run the standard interactive command:
sudo docker exec -it \[YOUR\_CONTAINER\_NAME\] python3 manage.py createsuperuser
2\. Follow the prompts to manually enter your desired credentials.
A missing superuser can prevent access to the Paperless-ngx admin panel. The method above solves the issue through the xCloud Commands interface by running the required Docker command with environment variables.
This process creates the admin account without an interactive terminal. Log in to the Paperless-ngx dashboard after the command finishes and change the default password immediately for security. SSH remains a good alternative if you prefer an interactive setup.
Still stuck? Feel free to contact our [support team.](/support/)
---
# How to Create A Site Snapshot With xCloud - xCloud
> xCloud allows to create a snapshot of your existing WordPress site. Learn how to create a snapshot and deploy a WordPress site easily with xCloud
When managing multiple websites or frequently deploying similar site setups, repeating the same configuration steps can be time-consuming and inefficient. The Site Snapshot feature in xCloud addresses this issue by enabling you to capture a complete version of an existing site and reuse it to create new sites instantly.
This ensures consistency across deployments, reduces manual effort, and speeds up the site creation process. Follow the steps to create a snapshot and use it to launch a new WordPress site in xCloud.
## **Step 1: Create a Snapshot** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
To begin, log in to your xCloud account and go to the source site where you want to create a snapshot. From the site dashboard, navigate to the ‘**Actions’** menu and select ‘**Take Snapshot’** from the dropdown list.
A popup window will appear where you need to enter a name for the snapshot so you can easily identify it later. Once the name is added, click the **Take Snapshot** button. After the process is complete, go to the **Site Snapshots** section from the xCloud dashboard to confirm that your snapshot has been successfully created.
After you have created the snapshot, go to the ‘Site Snapshots’ option from the xCloud dashboard.
## **Create a Site Using Snapshots** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
After creating a snapshot, you can use it to deploy a new site without starting from scratch. The snapshot preserves your site’s configuration, structure, and settings, allowing you to replicate the same setup in just a few steps. This makes it easy to launch multiple sites, create demo environments, or test changes while maintaining consistency and saving valuable time.
### **Step 1: Access the Dashboard** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
### **Step 2: Choose Your Server** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
Once your server is connected, you can create a site from the dashboard or Site List by clicking the **‘Create New Site’** button. Then choose your server from the dropdown menu. Next, click on the ‘Next’ button to proceed.
### **Step 3: Choose Your Site & Add Information** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
As we will be creating a fresh WordPress site, choose the **‘Install New WordPress Website’** option.
### **Step 4: Select Site Creation Method** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
Next, you need to choose a deployment method: **‘Default’, ‘Build With Templately AI’** or **‘Site Snapshots**’.
To create a site manually, choose the**‘Default’** method. If you want to create a site using AI, choose the **‘Build With Templately AI’** method, or if you want to proceed with site creation with your preset templates, choose ‘ Snapshots’.
### **Step 5: Choose the Snapshots** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
Next, in the pop-up, you will get the list of snapshots you have created. Choose your preferred one to proceed.
### **Step 6: Set Up Your Site** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes:
- **Go Live** – for a production-ready deployment.
- **Demo Site** – for deploying the site instantly with a demo domain from xCloud.
Selecting **Go Live** will immediately create a live environment, while **Demo Site** allows you to create a site using a temporary demo domain.
### **Step 7: Configure Domain Settings** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
If you select the **Demo Site** option, xCloud will assign a temporary subdomain for your WordPress application. Next, enter your application’s domain.
You will also get a few configuration options, including **‘Turn Off Indexing’, ‘Site Backup Settings’.** Configure them according to your preferences and click on the **‘Next’** button.
## **Manage Site Snapshots** [#](/docs/create-a-snapshot-to-deploy-a-wordpress-site/)
To manage the snapshots you have created under this site, go to the **‘Site Snapshots’** Option from the sidebar menu.
Here, you can view all your created snapshots in one place. You can select any specific snapshot to **‘Edit’** or **‘Delete’** it.
Now, you can manage all snapshots across your team. Go to Settings and navigate to Site Snapshots from the sidebar menu.
Here, you can view all snapshots from every site in the team in one place. You can select any snapshot to **‘Edit’** or **‘Delete’** it.
And that’s it. This is how easily you can create a site using the Site Snapshot feature in xCloud. It enables you to create new WordPress sites quickly and consistently, eliminating the need to repeat the same setup steps. By creating a snapshot once and reusing it whenever needed, you can deploy demo or live sites with minimal effort and maximum efficiency.
---
# Telegram Bot Token Setup: 7 Easy Steps to Connect Hermes on xCloud
> Create a Telegram bot token with BotFather, find your Telegram user ID, and connect Hermes Agent on xCloud in 7 easy steps.
Hermes Agent runs on your xCloud server, but you do not always have the dashboard open when you need it. Connecting Hermes to Telegram gives you a faster way in. You can send prompts, get replies, and run Hermes from your phone wherever you are, without logging into the server.
Follow this guide to create a Telegram bot token with BotFather and connect it to Hermes Agent during deployment on xCloud. You will create the bot, copy the bot token, find your Telegram user ID, and enter both values in the Hermes Agent deployment flow. Most of the setup takes place while you create or configure the Hermes server in xCloud.
Add the Telegram bot token while deploying Hermes Agent on xCloud.
## Prerequisites [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
- An active xCloud account.
- Access to the Hermes Agent deployment flow in xCloud.
- A Telegram account.
- The Telegram app is installed on your phone or desktop.
## Step 1: Open BotFather in Telegram [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
Open Telegram and search for **@BotFather**. BotFather is Telegram’s official bot for creating and managing bots. You can also review Telegram’s official BotFather information in the [**Telegram BotFather**](https://core.telegram.org/bots/features#botfather) [](https://core.telegram.org/bots/features#botfather)documentation.
1. Open Telegram.
2. Search for **@BotFather**.
3. Open the verified BotFather chat.
4. Click **Start** if you have not used BotFather before.
## Step 2: Create a new Telegram bot [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
In the BotFather chat, send the following command:
```
/newbot
```
Copy to Clipboard
BotFather will ask for two values:
- **Bot name:** This is the display name users see in Telegram. Example: **xCloud Hermes Assistant**.
- **Bot username:** This must be unique and must end with `bot`. Example: `xcloud_hermes_assistant_bot`.
If the username is already taken, choose a different username and send it again. When Telegram accepts the username, BotFather creates the bot and returns a token.
Send /newbot in BotFather, then enter the bot display name and bot username.
## Step 3: Copy the Telegram bot token [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
After the bot is created, BotFather shows a **Telegram bot token**. The token usually looks similar to this example:
```
1234567890:AAExampleTokenValueForYourTelegramBot
```
Copy to Clipboard
Copy the full token and keep it private. Anyone with this token may be able to control your Telegram bot. Do not share it publicly, do not add it to screenshots, and do not paste it into public support threads.
Copy the Telegram bot token from BotFather and keep it secure.
## Step 4: Find your Telegram user ID [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
Hermes can restrict Telegram access to allowed users. If the xCloud setup form asks for a Telegram user ID, add the Telegram numeric ID for the person who should be allowed to control Hermes.
1. Open Telegram.
2. Search for **@userinfobot** or another trusted Telegram user ID bot.
3. Start the bot.
4. Copy your numeric Telegram user ID.
If multiple team members need access, collect each person’s Telegram user ID and add them where the Hermes setup form supports multiple IDs.
Send /start to the bot to confirm the Telegram user ID or pairing details.
## Step 5: Add the Telegram bot token while setting up Hermes on xCloud [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
Go back to xCloud and continue the Hermes deployment flow. During setup, choose **Agentic**, select **Hermes Agent**, and open the optional Telegram messaging section.
1. Open your xCloud dashboard.
2. Start the agent deployment flow.
3. Select **Agentic**.
4. Select **Hermes Agent**.
5. Go to the optional **Telegram** or messaging section.
6. Paste the **Telegram Bot Token** you copied from BotFather.
7. Add your **Telegram User ID** if the field is available or required.
Make sure there are no extra spaces before or after the token. A small typo in the token can prevent Hermes from connecting to Telegram.
## Step 6: Complete the Hermes deployment [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
After adding the Telegram bot token, continue the remaining Hermes setup steps in xCloud. Review the selected server, plan, domain, and required environment values. Then click **Next** and click **Create** to start the deployment.
xCloud will provision the server and install Hermes Agent. Wait until the setup finishes before testing Telegram. If the deployment is still running, Telegram may not reply yet.
## Step 7: Start and test the Telegram bot [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
After the Hermes deployment is complete, open your new Telegram bot and send:
```
/start
```
Copy to Clipboard
Then send a short test message, such as:
```
Hello Hermes
```
Copy to Clipboard
If the connection is working, Hermes should respond in Telegram. You can now use Telegram as a messaging channel for your Hermes Agent.
Send /start and a short test message to confirm the Hermes Telegram connection is working.
And that’s it this is how you can create a Telegram Bot and connect It with Hermes on xCloud. If you want the full deployment walkthrough to deploy your AI Agent with Hermes Agent, read [**this documentation**](/docs/how-to-deploy-hermes-agent-with-xcloud/)**.**
## Manage the Telegram connection after deployment [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
The setup-time Telegram fields are the recommended way to connect Hermes during deployment. After Hermes is deployed, you can manage messaging configuration from the Hermes dashboard or available channel settings if your deployment exposes them.
Use the post-deployment settings only for maintenance tasks such as replacing a bot token, adjusting allowed Telegram users, or reconnecting the channel after changing the bot in Telegram.
## Troubleshooting [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
### BotFather says the username is unavailable [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
Choose a different bot username. Telegram bot usernames must be unique and must end with `bot`.
### Hermes does not reply in Telegram [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
- Confirm the Hermes deployment has finished.
- Send `/start` to the bot first.
- Check that the Telegram bot token was copied correctly.
- Confirm your Telegram user ID is allowed if access restrictions are enabled.
- Restart or reconnect the Telegram channel from the Hermes settings if available.
### The Telegram bot token was exposed [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
If the token was shared publicly or added to a screenshot, open **@BotFather**, revoke the old token, generate a new token, and update the Hermes Telegram configuration in xCloud.
## FAQ [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
### Do I need a Telegram bot to use Hermes on xCloud? [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
No. Hermes can still run without Telegram if you use another supported interface. You only need a Telegram bot token if you want to control Hermes from Telegram.
### Can I add the Telegram bot token after Hermes is deployed? [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
Yes, where post-deployment channel settings are available. However, adding the Telegram bot token during setup is the recommended flow because Hermes can be configured with Telegram from the start.
### Can more than one Telegram user access the same Hermes bot? [#](/docs/create-a-telegram-bot-and-connect-it-with-hermes/)
Yes, if your Hermes setup supports multiple allowed Telegram user IDs. Add each trusted user’s Telegram ID and avoid sharing the bot token itself.
---
# How to Create Server with the Preferred Ubuntu Version - xCloud
> Learn how to create a server in xCloud with your preferred Ubuntu version. Follow a simple process to select Ubuntu version with ease.
Keeping your server OS updated is essential for performance, security, and compatibility. In xCloud, you can create server and choose your preferred Ubuntu version for your server.
**First,** head to your xCloud dashboard and click **‘Create Server’.** You can **select your desired Ubuntu version** (e.g., Ubuntu 22.04, 24.04) during the server creation process.
**_Note:_** You **cannot upgrade** the Ubuntu version **on an existing server** in xCloud.
Instead, you must:
1. **Create a new server** with the upgraded Ubuntu version.
2. **Clone your existing sites** to the newly created server.
Read the step-by-step guide to learn how to clone your sites:
_👉 [**How To Clone A Website From Git Repository With xCloud**](/docs/clone-a-website-from-git-repository-with-xcloud/)_
And that’s it. This is how easily you can create your new server with the upgraded Ubuntu version.
---
# How to Set Up Custom SMTP for Branded Emails in xCloud White Label - xCloud
> Setting up your custom SMTP allows you to send branded emails from your domain to clients, enhancing your professionalism and brand identity. Follow these
Setting up your custom SMTP allows you to send branded emails from your domain to clients, enhancing your professionalism and brand identity. Follow these steps to configure custom SMTP in your xCloud White Label dashboard.
#### **Step 1: Access the White Label Dashboard** [#](/docs/custom-smtp-provider-with-xcloud-white-label/)
1. Log in to your xCloud account.
2. Navigate to the **White Label Dashboard** from your main account menu.
#### **Step 2: Open White Label Settings** [#](/docs/custom-smtp-provider-with-xcloud-white-label/)
1. Inside the White Label Dashboard, locate and click on **Settings** in the sidebar.
2. Look for the **SMTP** section in the settings menu.
#### **Step 3: Configure Custom SMTP** [#](/docs/custom-smtp-provider-with-xcloud-white-label/)
1. In the SMTP section, click **Add SMTP Credentials**.
2. Fill in the fields with your SMTP provider’s details:
- **SMTP Host**: (e.g., `smtp.yourdomain.com`)
- **SMTP Port**: (e.g., `465` for SSL or `587` for TLS)
- **Encryption Type**: Select **SSL**, **TLS**, or **None** depending on your provider’s settings.
- **SMTP Username**: Enter the username for your email account.
- **SMTP Password**: Enter the password for your email account.
#### **Step 4: Test the Configuration** [#](/docs/custom-smtp-provider-with-xcloud-white-label/)
1. After entering the credentials **Test SMTP** setup.
2. Try a forget password method from your own dashboard as one of your own registered clients.
#### **Step 5: Save and Apply Settings** [#](/docs/custom-smtp-provider-with-xcloud-white-label/)
1. Once tested successfully, click **Save Changes** to finalize your setup.
2. Your custom SMTP is now ready to send branded emails to your clients.
### **Best Practices for Custom SMTP** [#](/docs/custom-smtp-provider-with-xcloud-white-label/)
- Ensure your email domain has valid DNS records like **SPF**, **DKIM**, and **DMARC** to prevent emails from being marked as spam.
- Use a reliable SMTP provider to ensure email deliverability.
- Follow your specific SMTP provider’s guidelines.
Still stuck? Contact **our** [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Customize Reseller Landing Page in xCloud - xCloud
> Learn how to customize reseller landing page with xCloud White Label.
With xCloud White Label, you receive a built-in landing page to showcase your hosting plans and start selling immediately. You can easily customize reseller landing page with custom content and add your social media profiles.
## **Step 1: Enable or Disable the Landing Page** [#](/docs/customize-reseller-landing-page-in-xcloud/)
By default, xCloud White Label provides a ready-made landing page. From the dashboard, go to **‘Settings**.’ Now, select ‘Landing Page.’ This is where you will find all the available options to customize different aspects of your landing page.
Toggle it on to enable the landing page. However, if you prefer not to use this built-in feature, you have the option to keep it disabled. Disabling the page allows you to use your own custom landing page or website if you choose to do so.
## **Step 3: Add a Logo to the Navbar** [#](/docs/customize-reseller-landing-page-in-xcloud/)
In the **‘Landing Page Settings’** option, find the **‘Navbar Logo’** section. Click on the **‘Upload Logo’** button and upload your custom logo.
**_Note:_** _Ensure that the logo is_ _a minimum size of 212×40 pixels in PNG, JPEG, or JPG format (max 5MB)_ _to fit well within the navbar_
## **Step 4: Customize the Hero Section** [#](/docs/customize-reseller-landing-page-in-xcloud/)
You can customize the Hero section to highlight your services or a key message about your reseller hosting plans. Locate the **‘Hero Section’** in the **‘Landing Page Settings’**. Under **‘Heading’**, write a strong headline that clearly conveys what you offer. This could be your main value proposition or a catchy phrase to capture attention. Next, in the **‘Subheading’** field, provide additional information or context about your services. This can be a short description that complements the main heading.
## **Step 5: Customize the CTA (Call to Action) Section** [#](/docs/customize-reseller-landing-page-in-xcloud/)
To personalize the CTA section, locate the **‘Heading’** field and input your text. Then, add your desired subheading content in the **‘Subheading’** field. Then add a ‘button text’ and ‘button UR’ where this ‘CTA’ will redirect the user.
## **Step 6: Add Your Social Media Profiles** [#](/docs/customize-reseller-landing-page-in-xcloud/)
Add links to your social media profiles by filling in the **‘Social Profile Links’** for Facebook, Twitter, LinkedIn, YouTube, and Instagram. Once you’ve set everything up, click the **‘Save and Preview’** button.
By following these steps, you can quickly and easily customize your reseller’s landing page using xCloud White Label. This personalized page will help you promote your hosting plans, strengthen your brand presence, and connect with your audience across social platforms.
Still stuck? Contact our [**support**](/support/) team for any of your queries.
---
# How to Choose Dedicated CPU Instance Types With xCloud
> Learn when to choose a Dedicated CPU instance in xCloud, compare Dedicated 4GB to 96GB plans, and select the right plan for production workloads.
If you’re comparing hosting, you’ve probably seen “shared hosting,” “VPS,” “shared CPU,” and “dedicated CPU” used loosely, sometimes as if they mean the same thing. They don’t, and the difference directly affects how fast and how reliably your site runs under real traffic.
This guide explains all three levels in plain language, helps you decide which fits your site, and shows you exactly how to choose a Dedicated CPU plan inside xCloud, including the plans available and what each one is best for.
## Quick summary (TL;DR) [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
There are three distinct levels of hosting, not two names for one thing:
Level
What’s yours
What’s shared
Best for
Shared hosting
A slice of a control panel
The whole server (OS, RAM, CPU)
Small, low-traffic sites
Shared-CPU VPS
Your own server, RAM, storage
The physical CPU cores
Most sites and apps
Dedicated-CPU VPS
Your own server, RAM, storage, and CPU
Nothing
High-traffic, business-critical sites
The biggest jump is from shared hosting to any VPS, that’s where you gain a real isolated server and full control. The jump from shared-CPU to dedicated-CPU is narrower but important: it’s what keeps performance consistent when your site is under sustained, heavy load.
If your site is hitting CPU limits, slowing down during traffic spikes, or running a heavy stack (large WooCommerce, Laravel, Node.js), a dedicated-CPU server is the upgrade that fixes it. xCloud Managed Dedicated runs on reserved vCPUs with full root access and OpenLiteSpeed, and costs up to 28% less than Cloudways at comparable specs.
## Part 1: Understanding the three hosting levels [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
### Shared hosting (e.g. Namecheap) [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
With shared hosting, your website lives on a single server alongside many other accounts, sometimes hundreds. Everyone shares the same operating system, memory, and CPU, and you typically manage your site through a control panel like cPanel rather than the server itself.
What this means for you:
- No isolated server environment, you’re sharing the machine itself
- No root access, and limited ability to install custom software or choose your stack
- Resources are pooled, so a traffic spike or heavy script on someone else’s site can slow yours down
- Lowest cost of any option
Best for: small, low-traffic websites, personal blogs, and simple brochure sites where budget matters most and control doesn’t.
### Shared-CPU VPS (e.g. Vultr Cloud Compute) [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
A VPS (Virtual Private Server) is a big step up. You get your own virtual server with your own operating system, full root access, and RAM and storage reserved exclusively for you. You’re free to install whatever software and stack you like.
On a shared-CPU VPS, the one resource still shared is the physical CPU. Your server is given CPU time on cores that other VPSs on the same physical host also use. Most of the time this is perfectly smooth, but when several VPSs on the same host demand CPU at once, your available CPU can fluctuate. This is the “noisy neighbor” effect.
What this means for you:
- Your own isolated server with root access and a custom stack
- Dedicated RAM and storage
- Shared CPU cores, performance is usually strong but can dip under contention
- Excellent price-to-performance
Best for: the majority of sites and applications, growing WordPress sites, small-to-mid WooCommerce stores, staging environments, and most web apps.
### Dedicated-CPU VPS (e.g. Vultr Optimized Cloud Compute, used by xCloud Dedicated) [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
A dedicated-CPU VPS gives you everything a VPS offers, your own OS, root access, reserved RAM and NVMe storage, plus one crucial upgrade: your vCPUs are reserved exclusively for you. No other customer shares your CPU cores.
Because there’s no competition for CPU, performance stays consistent even under sustained, heavy load. There’s no noisy-neighbor variability, which is exactly what high-traffic and transactional sites need.
What this means for you:
- Full server isolation and control, same as any VPS
- Dedicated RAM, NVMe storage, and CPU
- Consistent, predictable performance under load
- The right tier when stable performance is business-critical
Best for: high-traffic WordPress sites, large WooCommerce stores, Laravel and Node.js applications, agency workloads, and any business-critical site where a slowdown costs you money.
### Side-by-side comparison [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Shared hosting
Shared-CPU VPS
Dedicated-CPU VPS
Your own server environment
No
Yes
Yes
Root access / custom stack
No
Yes
Yes
RAM & storage
Shared
Reserved for you
Reserved for you
CPU cores
Shared
Shared (can fluctuate)
Reserved for you
Performance under load
Least predictable
Usually good, can dip
Consistent
Typical cost
Lowest
Mid
Higher
Best for
Small, low-traffic sites
Most sites & apps
High-traffic, business-critical
### **Is Namecheap shared hosting the same as a Vultr shared-CPU VPS?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
This is one of the most common points of confusion, so it’s worth answering directly: no, they are not the same.
Even an entry-level shared-CPU VPS (like Vultr Cloud Compute) gives you a genuinely isolated server, your own operating system, root access, and reserved RAM and storage. Shared hosting (like Namecheap) gives you none of those, you’re sharing the entire machine and managing your site through a restricted control panel.
So the gap between Namecheap shared hosting and a Vultr VPS is large: it’s the difference between renting a slice of a shared machine and having your own server. The narrower question, “is a shared-CPU VPS the same as a dedicated-CPU VPS?”, comes down to one thing: whether your CPU is guaranteed, or can flex when neighbors get busy.
## What is a Dedicated CPU instance type in xCloud? [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
A Dedicated CPU instance type gives your xCloud Managed server access to a stronger, more predictable compute profile than standard shared or general-purpose plans. It’s a good fit when your site or application is important enough that CPU consistency matters for page speed, admin performance, background jobs, checkouts, API requests, or deployment workloads.
In xCloud, the Dedicated option appears beside the existing General and Premium server plan types during xCloud Managed server creation. The first Dedicated release uses Vultr Optimized Cloud Compute General Purpose plans only. This keeps the plan family consistent and helps maintain a safe upgrade path as your server grows.
### When should you choose a Dedicated CPU instance? [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Choose a Dedicated CPU instance when your workload needs more predictable resources than a normal starter server. Common use cases include:
- High-traffic WordPress sites that need stable frontend and wp-admin performance
- WooCommerce stores where checkout, cart, product search, and admin tasks must stay responsive
- Laravel, PHP, or Node.js applications with steady production traffic
- Agency servers that host important client sites and need more predictable headroom
- Business-critical applications where CPU spikes can affect revenue, operations, or customer experience
If you’re launching a small test site, a staging site, or a low-traffic project, a General or Premium plan may be enough. If the server already handles real users, transactions, heavy plugins, recurring jobs, or multiple production apps, Dedicated is the safer starting point.
## Available Dedicated CPU plans in xCloud [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
The Dedicated plan set includes ten RAM-based plans, from 4 GB up to 256 GB. Each plan uses the same Vultr Optimized General Purpose family, so upgrades can stay within the same category.
xCloud plan
CPU
RAM
Storage
Bandwidth
Monthly price
Best for
Dedicated 4GB
1 vCPU
4 GB
30 GB NVMe
4 TB
$40/mo
Small production sites, lightweight apps, or first Dedicated deployments
Dedicated 8GB
2 vCPU
8 GB
50 GB NVMe
5 TB
$90/mo
Growing WordPress sites, moderate WooCommerce stores, and agency workloads
Dedicated 16GB
4 vCPU
16 GB
80 GB NVMe
6 TB
$185/mo
Recommended middle option for serious production workloads
Dedicated 32GB
8 vCPU
32 GB
160 GB NVMe
7 TB
$335/mo
Busy stores, multiple client sites, or heavier application workloads
Dedicated 64GB
16 vCPU
64 GB
320 GB NVMe
8 TB
$590/mo
Large production environments with sustained traffic and resource needs
Dedicated 96GB
24 vCPU
96 GB
480 GB NVMe
9 TB
$900/mo
High-capacity production servers
Dedicated 128GB
32 vCPU
128 GB
640 GB NVMe
9 TB
$1,110/mo
Heavy multi-site or multi-app production environments
Dedicated 160GB
40 vCPU
160 GB
768 GB NVMe
10 TB
$1,500/mo
Large-scale hosting and resource-intensive applications
Dedicated 192GB
64 vCPU
192 GB
960 GB NVMe
11 TB
$2,400/mo
Enterprise workloads with sustained high demand
Dedicated 256GB
96 vCPU
256 GB
1280 GB NVMe
12 TB
$4,800/mo
The largest Dedicated option for the most demanding deployments
Note: xCloud does not include a Dedicated 2GB option because the selected Vultr Optimized General Purpose plan family starts at 4 GB. Keeping Dedicated plans inside one provider plan family helps avoid upgrade issues later.
## How to choose a Dedicated CPU instance type in xCloud [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Follow these steps when creating a new xCloud Managed server.
### 1\. Open the xCloud Managed server creation page [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Log in to your xCloud Dashboard and start creating a new xCloud Managed server. Continue until you reach the server plan selection step.
### 2\. Select the Dedicated plan type [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
In the plan type selector, choose Dedicated. You should see Dedicated plans listed separately from General and Premium.
### 3\. Pick the Dedicated size that matches your workload [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Select the plan based on your expected traffic, number of sites, application type, and resource usage. For many production workloads, Dedicated 16GB is the recommended balanced starting point because it gives 4 vCPU, 16 GB RAM, and 80 GB NVMe storage without starting too high.
### 4\. Choose a supported region [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Choose a region where the selected Dedicated plan is available. If a plan is not available in a specific region, choose another region or select a different Dedicated size that is available there.
### 5\. Review billing and create the server [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Review the selected plan, monthly price, region, and server details before creating the server. After provisioning finishes, check the server details page to confirm the CPU, RAM, and storage match the Dedicated plan you selected.
## How xCloud Dedicated compares to Cloudways [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
A dedicated-CPU server normally comes with a tradeoff: you get raw power, but you’re expected to manage the server yourself, setup, security, updates, and maintenance. xCloud removes that tradeoff. xCloud Managed Dedicated runs on reserved-CPU infrastructure but is fully managed, so you get guaranteed performance and full control without the system-administration burden.
Compared to Cloudways, the difference comes down to what you’re actually allowed to do with your server, and how it performs under pressure:
xCloud Managed Dedicated
Cloudways
Reserved (dedicated) vCPUs
Yes
Yes (Dedicated line)
Full root / SSH access
Yes
No
OpenLiteSpeed option
Yes
No
NVMe storage at each tier
More
Less
Built-in WAF (7G/8G firewall)
Yes
Limited
Full server-level backups
Yes
Site-level
Price at comparable tiers
Up to 28% lower
Higher
The takeaway: xCloud Dedicated gives you things Cloudways structurally cannot, root access, OpenLiteSpeed, more storage per tier, and full server backups, while keeping the consistent performance a reserved-CPU server is built for. Costing up to 28% less at comparable specs is the bonus, not the whole story.
If you want the absolute lowest infrastructure cost and you’re comfortable choosing your own provider, xCloud also lets you bring your own server (Vultr, DigitalOcean, Hetzner, AWS, and more) and pay near-zero markup. Managed Dedicated is for teams who’d rather have it all handled, with performance guaranteed.
## Dedicated vs General and Premium plans [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
General and Premium plans are still useful for many websites and applications. Dedicated is not required for every server. The main difference is that Dedicated plans are intended for workloads where consistent compute performance is more important.
- Use General for smaller projects, staging sites, development servers, or budget-friendly hosting.
- Use Premium when you want stronger performance than General but don’t need the Dedicated plan family.
- Use Dedicated for production workloads that need stronger and more consistent CPU performance.
If you’re unsure which option to choose, start by reviewing your current server CPU, RAM, disk usage, traffic pattern, and application type. You can also contact xCloud Support with your workload details for guidance.
## Upgrade path for Dedicated servers [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Dedicated plans are designed to upgrade inside the same Vultr Optimized General Purpose plan family. For example, a server on Dedicated 4GB can move to a larger Dedicated plan such as Dedicated 8GB, Dedicated 16GB, or higher when more resources are needed.
This same-family approach is important because providers may not allow direct upgrades between different optimized plan families. xCloud keeps the first Dedicated release focused on one balanced family so the upgrade path stays clear.
## Verification after creating a Dedicated server [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
After your server is created, verify the setup before moving important workloads to it:
- Open the server details page in xCloud
- Confirm the selected Dedicated plan name is shown correctly
- Confirm the CPU, RAM, and storage match your selected plan
- Create or move your site/application only after provisioning is complete
- Monitor CPU, memory, disk, and traffic after launch to confirm the size is suitable
## Troubleshooting [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
I do not see the Dedicated option Make sure you are creating an xCloud Managed server and that the feature is available for your account. If you still do not see it, refresh the dashboard or contact xCloud Support.
A Dedicated plan is not available in my preferred region Plan availability can depend on the provider region. Choose another supported region or select a different Dedicated size that is available.
I am not sure which Dedicated size to choose For many production workloads, Dedicated 16GB is a balanced starting point. Smaller sites can start with Dedicated 4GB or 8GB, while busy stores, agencies, and heavier applications may need 32GB or higher.
## **Frequently asked questions** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
### **Is Namecheap shared hosting the same as a shared-CPU VPS?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
No. Shared hosting puts you on a server shared with many other accounts, with no root access and no isolated environment. A shared-CPU VPS gives you your own server, your own OS, root access, and reserved RAM and storage, only the physical CPU cores are shared. They’re different categories of hosting.
### **What’s the difference between shared CPU and dedicated CPU?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
On shared CPU, your server shares physical processor cores with other customers, so your available CPU can fluctuate when neighbors get busy. On dedicated CPU, your vCPUs are reserved only for you, giving consistent performance even under sustained load. Isolation and control are the same; the difference is performance consistency.
### **Can I use Dedicated CPU instances for WordPress?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Yes. Dedicated CPU instances are a strong option for high-traffic WordPress sites, WooCommerce stores, membership sites, LMS sites, and other production WordPress workloads.
### **Can I use Dedicated CPU instances for Laravel or Node.js apps?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Yes. Dedicated plans are suitable for Laravel, PHP, Node.js, and similar application workloads when you need more predictable compute performance.
### **Which Dedicated CPU plan does xCloud recommend?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Dedicated 16GB is the recommended middle option for serious production workloads. It includes 4 vCPU, 16 GB RAM, and 80 GB NVMe storage.
### **Can I move from shared hosting to a VPS without downtime?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
In most cases, yes. The typical approach is to set up your site on the new server, test it fully, and only switch your domain over once everything is confirmed working. Done this way, visitors experience little to no interruption. xCloud offers free migration assistance if you’d like help planning the move.
### **Do I have to manage the server myself on a VPS?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Not with xCloud. A raw VPS normally means handling server setup, security, and maintenance yourself, but xCloud is managed, so we handle the server-level work (provisioning, the stack, updates, and security hardening) while you focus on your sites. You get the power and isolation of a VPS without the system-administration burden.
### **What does “noisy neighbor” actually mean?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
It’s when another customer sharing the same physical hardware suddenly uses a lot of CPU, temporarily reducing what’s available to you. It only affects shared-CPU setups. On a dedicated-CPU server your cores are reserved for you, so other customers’ activity can’t impact your performance.
### **Is more RAM or dedicated CPU more important for my site?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
It depends on your bottleneck. If your site is running out of memory (large databases, many concurrent processes, memory-heavy plugins), more RAM helps most. If your site slows down under traffic or runs CPU-intensive work, dedicated CPU is what keeps performance steady. If you’re unsure which you’re hitting, tell us your symptoms and we’ll help you diagnose it.
### **How is xCloud Dedicated different from Cloudways?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Both offer dedicated-CPU servers, but xCloud adds full root access, an OpenLiteSpeed option, more NVMe storage per tier, a built-in firewall, and full server-level backups, none of which Cloudways provides. xCloud Dedicated is also priced up to 28% lower at comparable specs.
### **Can I upgrade later if I outgrow my plan?** [#](/docs/dedicated-cpu-instance-types-with-xcloud/)
Yes. You can scale up to a larger Dedicated plan within the same provider family as your traffic and resource needs grow, so it’s fine to start with what you need today and move up when the time comes.
Still not sure which fits? For many production workloads, Dedicated 16GB is the balanced starting point. Tell our team your current setup and traffic levels and we’ll recommend the right size, or start with xCloud’s free tier to test the platform risk-free.
---
# How to Deploy AI Agents Platforms With xCloud White Label/ Reseller Hosting Program - xCloud
> Learn how to offer fully managed AI agent hosting under your brand with xCloud. Deploy OpenClaw, Hermes and Paperclip in minutes.
If you run a hosting business or reseller platform, your clients likely want to deploy AI agents without dealing with infrastructure headaches. xCloud’s white-label reseller hosting program makes that possible. Through your own branded panel, clients can spin up fully managed AI agent instances – OpenClaw, Hermes Agent, or Paperclip – in just a few clicks.
If you want to build a company allowing your users to deploy their preferred AI agents such as OpenClaw, Paperclip, and Hermes, then with the [**xCloud white-label reseller hosting program**](/reseller-hosting/). You can allow your users to deploy agents easily.
When deployed using the xCloud Reseller Hosting panel, AI Agents run on a dedicated xCloud managed server with a pre-configured stack. This setup removes the complexity of self-hosting, manual configuration, updates, and infrastructure maintenance.
### **Supported AI Agent Platforms** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
- OpenClaw
- Hermes Agent
- Paperclip
**Note:** This feature is available only for products created with the xCloud Managed Server.
Follow these steps to create a server and deploy your preferred AI agent.
## **Prerequisite To Deploy An AI Agent** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
- **xCloud Managed Server required.** AI agents can only be deployed on products created with an xCloud Managed Server. Existing or external servers are not supported.
- **Minimum 4 GB RAM.** The server must have at least 4 GB of RAM to run any AI agent.
## **Step 1: Create a New Server** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
First, users need to visit your dashboard. From there, click on the **“Create a Server”** button. Go to the **“Server Name”** field and enter a name for your server. You can also add a tag for the server. This step is optional.
## **Step 2: Choose a Server Size** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
Select your preferred server size from the available options. Make sure the server has at least **4 GB of RAM** – this is the minimum required for all AI agent deployments.
Note: The Agentic stack will be shown for the products you have created with xCloud Managed Server.
## **Step 3: Select Your Region** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
Choose your preferred **continent** from the dropdown menu to determine where your server will be hosted.
### **Step 4: Configure Backups** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
You will see the option to enable or disable automated backups for your deployment. Toggle this based on your preference.
### **Step 5: Select the Agentic Stack and Choose Your Agent** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
The platform provides a dedicated stack for AI agent applications. Select the **Agentic** stack, and you will see three agent options:
- **OpenClaw**
- **Hermes Agent**
- **Paperclip**
Choose the agent you want to deploy.
### **Step 6: Complete the Agent Setup** [#](/docs/deploy-ai-agents-platforms-with-xcloud-reseller-hosting-program/)
After selecting your agent, follow the corresponding guide below to finish the deployment:
- [How to Deploy OpenClaw with xCloud](/docs/how-to-deploy-openclaw-with-xcloud/)
- [How to Deploy Hermes Agent with xCloud](/docs/how-to-deploy-hermes-agent-with-xcloud/)
- [How to Deploy Paperclip with xCloud](/docs/how-to-deploy-paperclip-with-xcloud/)
Each guide covers the remaining configuration steps specific to your chosen agent.
That is it. This is how easily your clients can deploy AI agents on your own branded platform. No terminal access needed, no manual configuration, no ongoing maintenance. Connect your preferred AI provider, link a messaging channel, and your agent is ready to work.
If you run into any issues during the deployment process, feel free to reach out to our [support](https://support.xcloud.host/) team.
---
# How To Deploy Custom PHP Applications With xCloud? - xCloud
> Learn how to quickly install or manually upload your custom PHP applications to xCloud with this easy-to-follow tutorial.
Creating a website using custom [**PHP applications**](/php-hosting/) on xCloud can be a powerful way to build a tailored online presence. Unlike traditional WordPress-based sites, xCloud allows you to go beyond WordPress and develop fully customized PHP applications to meet your unique requirements. Whether you’re building a dynamic web app, an interactive platform, or a simple portfolio, xCloud provides a flexible hosting environment to support your PHP-based projects.
If you are migrating a custom PHP website from a Git repository or manually uploading your files, xCloud makes deployment seamless. In just a few easy steps, you can have your custom PHP application live. Follow this step-by-step guide to configure and deploy your fully functional website with ease—without the limitations of WordPress.
## **Step 1: Choose Your Server** [#](/docs/deploy-custom-php-applications-with-xcloud/)
Log in to your [**xCloud dashboard**](https://app.xcloud.host/) and click the **‘+New Site’** to add a new site. Then, choose a server from the list and go to **‘Next’**.
## **Step 2: Select Custom PHP** [#](/docs/deploy-custom-php-applications-with-xcloud/)
Here you will find **‘WordPress’** and **‘Custom PHP’** options. Go to **‘Custom PHP’** to upload your custom PHP scripts.
Then choose your preferred way from **‘Clone a Git Repository’** and **‘Manually Upload a Website’** options**.**
## **How To Install Custom PHP Applications From Your Git Repository** [#](/docs/deploy-custom-php-applications-with-xcloud/)
Migrating a website from a Git repository with xCloud involves several easy steps. The below guide can help you to understand how you can perform this migration. Follow the steps below to migrate a custom php site from a Git Repository.
### **Step 1: Select Option To Clone A Git Repository Option** [#](/docs/deploy-custom-php-applications-with-xcloud/)
First, click on ‘New Site’ from the xCloud dashboard. Click on the **‘Custom PHP’** field. Now, choose **‘Clone A Git Repository’** to import your custom php site.
### **Step 2: Select Destination Server** [#](/docs/deploy-custom-php-applications-with-xcloud/)
From the **‘Destination’** tab, select the destination server to migrate your site. You can keep the server that is already selected, or you can change it from the dropdown. Then, click on **‘Next’**.
### **Step 3: Set Up Domains** [#](/docs/deploy-custom-php-applications-with-xcloud/)
From the **‘Domains’** tab, you will get two options, either you can create your site in a staging domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain. To create a site with your live domain, you need to select the **‘Migrate into a New Domain’** option. Then you have to put **‘New Site Title’** and **‘Domain Name’**.
Here, you need to enable HTTPS to make your website more secure. From the DNS Setup section, toggle on the **‘Do You Want To Enable HTTPS?’** option. After enabling it, you will get two options to select. Either choose to use a free SSL certificate issued & managed by xCloud, or, you can provide the certificate and manage it yourself. Select according to your choice.
Instead of migrating into a new domain, you can select the **‘Demo Site’** option. xCloud offers a temporary staging domain to make your site live which helps promptly showcase your site’s progress and collect feedback from teammates or clients. Subsequently, you can integrate your custom domain to make the site accessible to your users or visitors. Now, click on **‘Next’**.
### **Step 4: Settings To Manage Database** [#](/docs/deploy-custom-php-applications-with-xcloud/)
In the **‘Settings’** tab, you will see the **‘PHP Version’** and **‘Site Users’**. You can change these according to your choice.
Now, it is time for database management. You will get two options. Either you can create a new database on the server, or, you can add your existing database that is hosted on another server. If you select this option, you need to get a **‘Database Name’**, **‘Database Username’** and **‘Database Password’**. You can keep these auto-generated credentials, or you can modify them according to your choice.
If you select this option, you need to put in a few information and credentials such as **‘Database Host’**, **‘Database Port’**, **‘Database User’**, **‘Database Name’**, and **‘Database Password’**. Please make sure that the database connection configuration is correct.
After selecting any one option and providing all essential information and credentials, click on **‘Next’**.
_Note: For this documentation, we are going with the **‘Create Database In Server’** option._
### **Step 5: Insert Git Repository Credentials** [#](/docs/deploy-custom-php-applications-with-xcloud/)
In the **‘Git Repo’** Tab, add your **‘Git Repository’** and **‘Git Branch’**. Also, toggle on the **‘Enable push to deploy’** option. Once you enable the **‘Push To Deploy’**, it will generate a **‘Deployment URL’**. We need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
### **Step 6: Add Deployment URL In Git Repository** [#](/docs/deploy-custom-php-applications-with-xcloud/)
Now, go to your Git Repository. From the **‘Code‘** tab, go to the **‘Settings’** tab and click on **‘Webhooks’** page from the **‘Code and automation’** section of the left navigation. Insert the Deployment URL into the **‘Payload URL’** field. Select the **‘Application/json’** from the **‘Content type’** dropdown.
### **Step 7: Add Public Key In Git Repository** [#](/docs/deploy-custom-php-applications-with-xcloud/)
From the xCloud dashboard, copy the **‘Public Key’** to add it to your Git repository as a deploy key. Git migration uses the **‘Public Key’** for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the **‘Code‘** tab, go to the **‘Settings’** tab and click on **‘Deploy Keys’** in the security section of the left navigation. Click on the ‘Add Deploy Key’ button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on **‘Next’** on your xCloud settings of the ‘Git Repo’ tab.
### **Step 8: Confirm Migrating The Website** [#](/docs/deploy-custom-php-applications-with-xcloud/)
Now, to start the migration process, click on the **‘Start’** button. After clicking on the **‘Start’** button, the migration process will start. And, you will see the progress of migrating.
**_Note:_** _The Git Repository must contain a wp-config-sample.php. xCloud generates a wp-config.php file from wp-config-sample.php file with the database information._
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
## **How To Manually Upload PHP Site On xCloud** [#](/docs/deploy-custom-php-applications-with-xcloud/)
If you’re migrating an existing PHP site or starting from scratch, xCloud makes it easy to upload and configure your website. Follow the steps below to successfully upload your site, set up your database, and get your site live on a custom domain or a staging environment.
### **Step 1: Create A New Site** [#](/docs/deploy-custom-php-applications-with-xcloud/)
First, click on ‘New Site’ from the xCloud dashboard. Click on the **‘Custom PHP’** field. Now, you choose **‘Manually Upload Website’** to import your custom php site.
### **Step 2: Add Information To Manually Upload Website** [#](/docs/deploy-custom-php-applications-with-xcloud/)
Now, select the destination server to migrate your site. Afterward, click on the **‘Next’** button.
In the next step, you need to add your source site URL. And if you choose to migrate to a new domain you can include your custom domain. xCloud offers a staging environment and with it, you can upload your site and visit it live with a temporary domain. After successfully uploading your site, you may update the site with your custom domain later.
In this tutorial, we will be working on a staging site. Select ‘**Demo Site’** and then click on the **‘Next’** button.
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your **‘PHP Version’**, **‘Site Users’**, **‘Web root’** and other details before clicking the **‘Next’** button.
_Note: The directory where your website’s main files, including index.php, are stored. The Web root defines the base folder from which your website is served, and it must be set correctly to ensure proper functionality_
Additionally, ensure that your index.php file is correctly placed for the system to function automatically. The **index.php** file should be located in the root directory. However, if it is placed in a subdirectory, you must update the Web Root Settings accordingly.
Users may upload their entire website directory instead of just the necessary files. For example, if the website files are inside a folder named **public\_html**, then the root directory does not contain index.php directly.
To resolve this, the you need to update the Web root settings. For this, navigate to Web Root Settings from the ‘**Site Settings’**. Then enter the name of the folder that contains the index.php file (e.g., public\_html) and click on the **‘Update’**.
Once updated, our system will correctly detect and load the index.php file from the specified folder.
### **Step 3: Upload The Exported Zip File & SQL File** [#](/docs/deploy-custom-php-applications-with-xcloud/)
You will be now directed to the **‘Settings’** step. Just upload your exported custom php file as shown and click on the **‘Next’** button.
Now from the **‘Files’** step, upload your SQL file similarly. Afterward, click on the **‘Next’** button.
### **Step 4: Complete Database Settings & Finalize** [#](/docs/deploy-custom-php-applications-with-xcloud/)
In the **‘Database’** tab you can configure your preferred database setup. If you are good to go for uploading an existing custom PHP website with xCloud, click on the **‘Start’** button.
Within a few moments, your PHP website will be uploaded on xCloud automatically. You will see the following screen while uploading.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
## Final Outcome [#](/docs/deploy-custom-php-applications-with-xcloud/)
After the migration is completed, if you visit the site, you can see the newly custom PHP site that you have uploaded with xCloud.
This is how easily you can create a site with custom PHP applications in xCloud. With simple steps, you can quickly deploy your site, configure your database, and choose your preferred domain settings. If you’re using a Git repository or uploading files directly, xCloud provides easy ways to get your website live and running smoothly.
Still, feeling stuck? Contact our [**dedicated support team**](/support/) for further assistance.
---
# How to Deploy Git Projects in One Click with xCloud - xCloud
> Learn how to deploy Git projects with xCloud on a single screen — automatic app detection, domain setup, DNS verification, and free SSL, no manual config needed.
Deploying a project from a Git repository usually means wiring up the server, the domain, the SSL certificate, and a build script before anything goes live. With [**xCloud**](/), all of that happens on a single screen.
xCloud reads your repository, detects the site type on its own, and handles the domain, DNS, and SSL for you, so your project goes from repo to live in one click.
This feature supports application detection for:
- WordPress
- PHP
- Laravel
- Node.js
- Lovable
- Docker Compose applications from Git
Follow the guide to deploy your Git project easily with xCloud:
## Step 1: Create a New Site [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
To begin deployment, click on the **‘Add New Site’** button from your xCloud dashboard. You will then be asked to choose the **server** where you want to deploy your Git project.
## Step 2: Go to the Deploy Via Git Tab [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Next, head over to the **‘Deploy Via Git’** tab. This is where you can deploy your Git projects in just a click.
## **Step 3: Enter Your Project URL** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Enter your project URL in the **‘URL’** field. You will see xCloud automatically detecting the site type, whether it is ‘WordPress’, ‘Laravel’, ‘[Node.js](http://node.js)’ or others from your repository, so there is nothing to select manually here.
## **Step 4: Set Up Your Domain** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Next, you can proceed with a **staging domain** from xCloud, or proceed with **your own custom domain.**
If you are using your own domain, enter the domain and verify the DNS.
### **– Verify DNS with Cloudflare** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
If you have Cloudflare integrated with xCloud and your domain is on Cloudflare, you can verify the DNS with a single toggle. Just enable the **‘Manage DNS with Cloudflare’** toggle button.
### **– Verify DNS Manually** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Alternatively, you can add the DNS records manually at your own DNS provider and verify from there.
Then, enable HTTPS. Just toggle on the button beside the **‘HTTPS’** section. You can use xCloud’s **free SSL certificate** or use your own **custom SSL certificate.**
## **Step 5: Select the Branch** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Then, enter the **branch** of the project that you want to deploy.
### **Step 6: Configure Advanced Settings (Optional)** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Next, go to the **‘Advanced Settings’** section. This step is optional, but it lets you fine-tune the deployment:
**→ PHP Version:**Choose the PHP version your project needs from the dropdown.
**→ Database:**Configure the database settings for your project.
Next, enter the contents of your environment file in the ‘.env File’ field. This is where you define the environment variables your project needs at runtime, such as API keys, database credentials, or app-specific configuration values.
You can also add a deploy script for this project. Any commands you enter here will run after the deployment completes, which is useful for tasks like installing dependencies, running migrations, or building assets.
### **Step 7: Deploy Your Project** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
Once everything is configured, click on the **‘Deploy’** button to proceed. Once the deployment is complete, your project will be live.
Deploying Git projects with xCloud removes the manual work of server configuration, DNS verification, and SSL setup. With site-type detection built in, you point xCloud at your repository and it takes care of the rest.
### **Deploying Specific Projects** [#](/docs/deploy-git-projects-in-one-click-with-xcloud/)
The one-click Git deployment flow works for most project types. If you’re deploying a specific framework or application, you can follow the dedicated guide instead:
- **WordPress:** To deploy your WordPress projects from Git, follow [**How To Clone A Website From Git Repository With xCloud**](/docs/clone-a-website-from-git-repository-with-xcloud/).
- **Node.js:** To deploy your Node.js projects, follow [**How to Deploy a Node.js Application with xCloud**](/docs/how-to-deploy-a-node-js-application/).
- **Laravel:** To deploy your Laravel projects, follow [**How to Deploy Laravel Applications with xCloud**](/docs/deploy-laravel-applications/).
Once your project is live, you can update it by pushing changes to your Git repository and redeploying from the xCloud dashboard.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How To Deploy Github Project From A Specific Branch - xCloud
> Learn how to prevent unintended deployments by configuring GitHub Actions to trigger only from specific branches and protect your production environment.
A deployment issue occurs when a webhook triggers a redeploy even if changes are pushed to a branch other than the selected production branch (e.g., main). This behavior causes unintended redeployments and may overwrite production with outdated or unrelated code.
To avoid this, you can control deployments directly from GitHub Actions by restricting execution to specific branches.
## Step 1: Open Your GitHub Repository [#](/docs/deploy-github-project-from-a-specific-branch/)
First, go to your GitHub repository. If you have already set the webhook, you need to remove the Webhooks from the dashboard. To remove, go to the ‘Settings’ from the menu. Then click on the ‘Delete’ webhooks that you have set for this repository with xCloud.
## Step 1: Go To The Actions Menu [#](/docs/deploy-github-project-from-a-specific-branch/)
Then go to the **Actions** tab in the top navigation bar. This section contains all automation workflows related to your project.
## Step 3. Create a New Workflow [#](/docs/deploy-github-project-from-a-specific-branch/)
Inside the **Actions** tab, look for an option labeled **Set up a workflow yourself**. Click on it to create a custom workflow from scratch. GitHub will open an editor where you can define your deployment logic using a YAML configuration file.
## Step 4: Paste the Workflow Code [#](/docs/deploy-github-project-from-a-specific-branch/)
In the editor, replace any default content with the following code:
name: Deployment
on:
push:
branches:
- main
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: Deploy
run: |
curl https://app.xcloud.host/deploy?token=xxxxx
Update the branch name under “branches:” to match the branch you want to trigger deployments from. For example:
**Branch**
**YAML Value**
main
– main
dev
– dev
Replace the placeholder URL in the curl command with your actual xCloud deployment webhook URL:
curl https://app.xcloud.host/deploy?token=YOUR\_ACTUAL\_TOKEN
Click the green “Commit changes” button to save the workflow file to your repository.
And that’s it, this is how you can activate the workflow immediately. From this point forward, any push to the specified branch will automatically trigger the deployment process. This ensures that only intentional pushes to your production branch will trigger a deployment, preventing the accidental redeployments caused by the previous webhook setup.
Still stuck? Feel free to reach out to our [support team](https://support.xcloud.host/).
---
# How to Deploy Laravel Applications with xCloud? - xCloud
> Deploy Laravel applications effortlessly on xCloud. Follow our step-by-step guide to launch, configure Git, manage DB, and go live—all in one place.
Deploying [**Laravel applications**](/laravel-hosting/) can often involve multiple steps and intricate configurations. xCloud simplifies this process by providing a streamlined platform tailored for deploying modern PHP applications, including Laravel, with minimal complexity. This tutorial provides a comprehensive, step-by-step guide to help you deploy your Laravel application using xCloud. If you are launching a new project or migrating an existing one, you’ll learn how to set up your server, configure your Git repository, manage your database, and finalize your deployment—all within the xCloud environment.
Follow this step-by-step guide to configure and deploy your fully functional Laravel website with ease.
## **Step 1: Choose Your Server** [#](/docs/deploy-laravel-applications/)
Log in to your [**xCloud dashboard**](https://app.xcloud.host/) and click the **‘+New Site’** to add a new site. Then, choose a server from the list and go to ‘**Next’**.
## **Step 2: Go to The Laravel Tab** [#](/docs/deploy-laravel-applications/)
From here go to the **‘Laravel’ tab** to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
## **Step 3: Set Up Domains** [#](/docs/deploy-laravel-applications/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the **‘Migrate into a New Domain’** option. Then you have to pu**t ‘New Site Title’** and **‘Domain Name’**. Here we are choosing **the ‘Demo Site’** domain. Then click on **‘Next’**.
## **Step 4: Settings To Manage Database** [#](/docs/deploy-laravel-applications/)
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your **‘PHP Version’**, **‘Site User’**, **‘Web root’**.
Now, it is time for database management. You will get three options. You can either create a new database on the server, you can add your existing database that is hosted on another server.
You can also proceed without any database. For this tutorial, we are going with the **‘Create Database In Server’** option.
If you select this option, enter your **‘Database Name’**, **‘Database Username’ and ‘Database Password’.** You can keep these auto-generated credentials, or you can modify them according to your choice.
After selecting any one option and providing all essential information and credentials, click on **‘Next’.**
## **Step 5: Insert Git Repository Credentials** [#](/docs/deploy-laravel-applications/)
In the **‘Git Repo’** tab, add your **‘Git Repository’** and ‘**Git Branch’**. Also, toggle on the **‘Enable push to deploy’** option. Once you enable the **‘Push To Deploy’**, it will generate a **‘Deployment**
**URL’**. We can use this URL to CICD pipeline and copy the **‘Deployment URL’** from here.
## **Step 6: Add the Deployment URL to the Git Repository** [#](/docs/deploy-laravel-applications/)
Now, go to your Git repository. From the **‘Code‘** tab, go to the **‘Settings’** tab and click on the **‘Webhooks’** page from the ‘**Code and automation’** section of the left navigation. Insert the deployment URL into the **‘Payload URL’** field. Select **‘application/json’** from the **‘Content type’** dropdown.
_Note: This step is optional. Adding a webhook enables automatic deployments when you push changes to the repository, but it’s not required if you prefer to deploy manually._
## **Step 7: Add Public Key to Git Repository** [#](/docs/deploy-laravel-applications/)
Next in the ‘Deploy Script’ field any script that needs to be executed after the site is deployed. For example, you can use it to install dependencies or run database migrations.
**Next, in the ‘Deploy Script’ field, specify any commands that need to be executed after the site is deployed.**If your project uses **PHP**, you can specify the version (e.g., php8.1) and run Composer along with Laravel-specific commands like this:
```
php8.1 $(which composer) install --no-interaction --prefer-dist --optimize-autoloader --no-dev
```
Copy to Clipboard
```
php8.1 artisan migrate --force
```
Copy to Clipboard
```
php8.1 artisan optimize:clear
```
Copy to Clipboard
If your project also involves **Node.js**, you can include additional commands as well. These scripts ensure that your backend and frontend are fully prepared after deployment.
From the xCloud dashboard, copy the **‘Public Key’** to add it to your Git repository as a deploy key. Git migration uses the **‘Public Key’** for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the **‘Code‘** tab, go to the **‘Settings’** tab and click on **‘Deploy keys’** in the security section of the left navigation. Click on the **‘Add key’** button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on **‘Next’** on your xCloud settings of the **‘Git Repo’** tab.
## **Step 8: Confirm Migrating The Website** [#](/docs/deploy-laravel-applications/)
Now, to start the migration process, click on the **‘Start’** button. After clicking on the **‘Start’** button, the migration process will start and you will see the progress of migration.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there. Go to the **‘Laravel’** Option from the menu and customize the **‘Application’** and **‘Environment’** as your preferences.
Check out the other features of Laravel:
[_**How to Use Supervisor for Process Management With xCloud**_](/docs/supervisor-for-process-management/)
[_**How to Set Up Laravel Horizon with xCloud**_](/docs/set-up-laravel-horizon/)
[**_How to Set Up a Queue Worker for Laravel Applications_**](/docs/set-up-queue-worker-for-laravel-applications/)
Configure Laravel Scheduler with cron job for your Laravel projects with ease. Check out this documentation for more details:
[_**How To Configure xCloud Cron Job?**_](/docs/how-to-configure-xcloud-cron-job/)
And that’s it. This is how easily you can successfully deploy your Laravel application on xCloud. Now you can go to your site dashboard from xCloud and customize according to your preferences.
If you are still stuck, feel free to contact our **[support team](/support/).**
---
# How to Deploy Lovable Applications with xCloud? - xCloud
> Learn how to deploy Lovable applications with xCloud using Git integration, domain setup, backups, and push-to-deploy - all from a simple dashboard.
[**Lovable**](/lovable-hosting/) is a modern AI-powered application-building platform designed to help anyone create user-friendly, scalable, and production-ready applications and websites through chatting.
xCloud allows you to deploy Lovable applications easily from your Git repositories. You can install and set up Lovable and get your application live in just a few clicks.
Follow the steps below to set up Lovable with xCloud and deploy AI-powered projects easily:
## **Step 1: Create a New Site** [#](/docs/deploy-lovable-applications-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
## **Step 2: Choose Your Server** [#](/docs/deploy-lovable-applications-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Lovable applications.
## **Step 3: Go to The Lovable Tab** [#](/docs/deploy-lovable-applications-with-xcloud/)
From here, go to the **‘Lovable’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
📝 Before you proceed, make sure your Lovable projects are properly synced with Git repositories.
## **Step 4: Set Up Domains** [#](/docs/deploy-lovable-applications-with-xcloud/)
From the ‘Domains’ tab, you will get two options: either you can create a ‘Demo Site’ with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the ‘Migrate into a New Domain’ option.
## **Step 5: Configure Site Settings** [#](/docs/deploy-lovable-applications-with-xcloud/)
Next, under the **‘Settings’** tab, you will get the **‘[Node.js](http://node.js) Version’** and ‘**Site User’** for this application. After that, click on the **‘Next’** button.
## **Step 6: Insert Git Repository Credentials** [#](/docs/deploy-lovable-applications-with-xcloud/)
In the ‘**Git Repo’** tab, you will get three repository options: **‘Private Repository (Manual SSH URL)’, ‘Public Repository (Manual HTTPS URL)’,** and **‘Connected Git Provider’.**
We are going to deploy Git projects using the **‘Git Provider’** option here. Choose the **‘Connected Git Provider’** option from the dropdown menu.
From the **‘Select Git Provider’** dropdown, choose the connected account you want to use. Once selected, navigate through the list of repositories, pick the one you want to deploy, and then select the specific **‘Branch’** of that project.
You can also deploy Lovable projects from your Public or Private Git repositories as well. For more details read this documentation:
_**👉 [How to Insert Your Git Repositories with xCloud](/docs/how-to-integrate-a-git-provider-with-xcloud/)**_
## **Step 7: Enable Push to Deploy** [#](/docs/deploy-lovable-applications-with-xcloud/)
The next step is to enable automated deployment. Toggle on the ‘Enable push to deploy’ option. You need to insert this URL into GitHub. Copy the ‘Deployment URL’ from here.
_**Note: If you want to learn more about the process, follow the steps in this [document](/docs/deploy-custom-php-applications-with-xcloud/).**_
Finally, review all the details and click on the **‘Start’** button to create the Lovable application.
## **Step 8: Visit the Application** [#](/docs/deploy-lovable-applications-with-xcloud/)
After completing the setup, you will be able to visit your Lovable site. From the dashboard, click on the **‘Visit Site’** app.
That’s it! This is how easily you can deploy Lovable with xCloud and launch your web apps in just a few clicks.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How to Deploy n8n with xCloud with One Click Apps - xCloud
> Deploy n8n with xCloud easily using One-Click Apps. Set up powerful workflow automation in minutes with minimal configuration.
[**n8n**](/n8n-hosting/) is an open-source workflow automation platform that allows users to connect different services and build complex workflows with minimal effort. With support for hundreds of integrations and a visual interface, n8n is ideal for teams looking to increase productivity without writing extensive custom code.
With **xCloud’s One Click Apps** feature, you can deploy n8n with ease. Follow the steps below to quickly set up n8n in a demo or production environment with xCloud.
## **🔖Recommendations** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
### **📌Web Server for Deployment** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
Though you can deploy the n8n application from both NGINX and OLS servers, we recommend deploying n8n on an NGINX server for the best performance and stability. While you can use an **OLS** server, Nginx generally provides a more reliable experience.
### **📌CPU Requirements** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
_To deploy n8n, you need a server with at least 4 GB of RAM and 2 CPU cores._
_**Note**: n8n is available in our plans, including the free plan. But you have to upgrade to our PRO plans to access the Environment feature._
## **Step 1: Access the One Click Apps Dashboard** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
This will take you to the site creation interface. From here, choose the **‘Server’,** then go to the **‘One Click Apps’** section. Select **‘n8n’** from the available applications to initiate the deployment process.
This will take you to the site creation interface. From here, go to the **‘One Click Apps’** section. Select **“n8n”** from the available applications to initiate the deployment process.
Ensure your server is already connected to xCloud. If not, follow the instructions on the dashboard to establish a server connection. Once connected, you can create a new site either from the main dashboard or the site list by selecting the **‘Create New Site**‘ option.
## **Step 2: Set Up the n8n Application** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘**Site Title’** and add relevant ‘**Tags’** to help organize your deployment. At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
## **Step 3: Configure Domain Settings** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
If you select the ‘**Demo Site’** option, xCloud will assign a temporary subdomain for your n8n application.
**_Note:_** _Note that once a demo site is promoted to a live environment, you cannot revert to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding._
## **Step 4: Configure and Install the Site** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
Then, a default **‘Port’, ‘Site User’** will be selected automatically. Then choose a ‘Timezone’ for this site. Once all settings have been configured, click the **‘Next’** button to proceed.
_Note: We recommend leaving the port and site user as the default._
## **Step 5: Visit the n8n Site** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
With n8n set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** app.
This will open the n8n dialog window for registration, which should look something like the example below. Simply enter your details and create a password according to the specs indicated. Hit the Next button, then click through any additional popups, leaving them empty for now.
This should bring you to the n8n Overview page. Now that your n8n instance is up and running, let’s fine-tune its settings for security and customization. From here, go to the ‘**Create workflow**’ , set according to your preferences.
## **Add Your Custom Domain** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
You can add your own **‘Domain’** to host the site by going to the Domain section. Also, you can add an **‘Additional Domain’** with your custom domain.
## **Environment Editor for n8n** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
The Environment section in xCloud allows you to customize configuration settings for your n8n instance. Just go to the **‘Environment’** option from the sidebar and adjust as you need, then click on the **‘Save’** button.
## **Update N8N Version** [#](/docs/deploy-n8n-with-xcloud-with-one-click-apps/)
To update n8n to the latest version, simply go to **‘Updates’** from the sidebar of the dashboard. Then simply search for the **‘Check for Updates’** button. Click the **‘Update n8n’** button, and this will install the latest n8n version on your server.
And that’s it, this is how easily you can quickly and efficiently deploy an n8n instance using xCloud’s One Click Apps feature. You can create your own n8n application and automate with workflows seamlessly.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Deploy Uptime Kuma with xCloud One Click Apps - xCloud
> Learn how to easily set up Uptime Kuma with xCloud one click apps deployment for reliable website and service monitoring in just minutes.
[**Uptime Kuma**](https://uptimekuma.org/) is a self-hosted monitoring tool that allows users to monitor websites, services, and applications with ease. It offers powerful uptime tracking, notifications, and intuitive dashboards.
If you are a developer, systems administrator, or hobbyist, you can deploy Uptime Kuma with xCloud to get a reliable, automated monitoring system. Follow the steps below to quickly set up Uptime Kuma with xCloud in a demo or production environment.
## **Step 1: Access the One Click Apps Dashboard** [#](/docs/deploy-uptime-kuma-with-xcloud/)
Begin by logging into your xCloud account. Once authenticated, navigate to your dashboard and click on the **‘New Site’** button.
This will take you to the site creation interface. From here, choose the **‘Server’,** then go to the **‘One Click Apps’** section. Select **‘****Uptime Kuma’** from the available applications to initiate the deployment process.
Ensure your server is already connected to xCloud. If not, follow the instructions on the dashboard to establish a server connection. Once connected, you can create a new site either from the main Dashboard or the Site List by selecting the **‘****Create New Site’** option.
## **Step 2: Set Up the Uptime Kuma Application** [#](/docs/deploy-uptime-kuma-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘**Site Title’** and add relevant ‘**Tags’** to help organize your deployment. At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
## **Step 3: Configure Domain Settings** [#](/docs/deploy-uptime-kuma-with-xcloud/)
If you select the ‘**Demo Site’** option, xCloud will assign a temporary subdomain for your Uptime Kuma instance. Available subdomain extensions include .wp1.site and .wp1.sh, both managed through Cloudflare. These demo domains are intended for temporary use and should be used for testing and development purposes only.
Note that once a demo site is promoted to a live environment, you cannot revert back to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding.
## **Step 4: Configure and Install the Site** [#](/docs/deploy-uptime-kuma-with-xcloud/)
Then, a default **‘Port’** and **‘Site User’** will be selected automatically. Also, you can create a new database to **‘Create Database to a Server**’ or ‘**Add Your Existing Database**’. Once all settings have been reviewed and configured, click the **‘****Next’** button to proceed.
_Note: We recommend leaving the database settings as default xCloud will automatically create a ‘Database Name’, Database Username’ for you, if you are creating a new database._
## **Step 5: Visit the Uptime Kuma Site** [#](/docs/deploy-uptime-kuma-with-xcloud/)
With Uptime Kuma set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** app.
## **Step 6: Go Live (optional)** [#](/docs/deploy-uptime-kuma-with-xcloud/)
You can add your own domain to host the site by going to the **Domain** section. Also, you can add an **Additional Domain** to host the status page of Uptime Kuma with your custom domain.
## **Step 7: Creating a Public Status Page With a Custom Domain** [#](/docs/deploy-uptime-kuma-with-xcloud/)
Once you’ve set up your monitoring and notification systems, the next step is to build a **public-facing status page**. This page provides real-time visibility into the status of your services for end users, helping you communicate uptime and issues transparently.
### **Create a New Status Page** [#](/docs/deploy-uptime-kuma-with-xcloud/)
In the Uptime Kuma dashboard, locate the **“Status Page”** option in the navigation menu and click on it to get started. Click the **“Create New Status Page”** button.
You’ll be taken to a form where you can configure basic settings. Give your page a ‘**Name’**. Define a custom ‘**slug’** that will be used in the page URL. Then click **Next** once you’ve entered these initial details.
### **Assign Monitors & Customize the Page Information** [#](/docs/deploy-uptime-kuma-with-xcloud/)
To display service statuses, click **“Add Monitor”** and choose which services or sites you want this page to track. These will appear on the public page as live status indicators.
You’ll now be able to add optional content to enhance the status page, such as a short **‘Description’**. A ‘**Footer Text’** that might include support contact info or disclaimers
### **Add Custom Domain** [#](/docs/deploy-uptime-kuma-with-xcloud/)
Then go to the **‘Domain Name’** and add your custom domain in the blank field. Add your custom domain here and click **Save** to finalize and publish the page. The status page becomes instantly accessible at the URL defined by your slug.
## **Step 8: Add Status Page Custom URL as an Additional Domain with xCloud** [#](/docs/deploy-uptime-kuma-with-xcloud/)
Next, go back to your Uptime Kuma site dashboard in xCloud. You can add your status page’s URL as an additional domain here. Just go to the **‘Domain’** and add the URL into the **‘Additional Domain’** and click on the save button.
## **Final Outcome** [#](/docs/deploy-uptime-kuma-with-xcloud/)
This will open the Uptime Kuma dialog window for registration, which should look something like the example below. Enter the registration details and hit the Next button. This should bring you to the Uptime Kuma Overview page. Now that your Uptime Kuma instance is up and running, let’s fine-tune its settings and other customizations. From here, go to the **‘Create workflow’**, set according to your preferences.
And that’s it, this is how easily, within minutes, your Uptime Kuma instance will be live and accessible via the xCloud dashboard. With just a few configuration steps, you can launch a robust uptime monitoring service suited for both demo and production use.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Disable Site in xCloud Hosting? - xCloud
> Step-by-step guide to learn how to disable site in xCloud hosting to disable complete access to a site over the web.
[**xCloud Hosting**](/) – the cloud-based server management tool brings a new feature to the table **‘Disable Site’** which allows you to disable complete access to a site over the web. Plus, your SFTP/SSH access will also be removed along with any cron jobs (scheduled tasks) for that site will be paused by disabling this feature.
There are several use cases for this feature. For example, if you ever need to pause or stop a client’s website, you can easily do it on xCloud using this feature. This might be because they have not paid their bills, or you need to do some quick maintenance.
Follow the below guidelines & learn how to disable site in xCloud hosting.
## **Step 1: Access Disable Site Option from Dashboard** [#](/docs/disable-site-in-xcloud-hosting/)
First, log in to your xCloud dashboard with the right credentials. Click on **‘All Sites’** and select the running site that you wish to disable. Now, find the **‘Settings’** from the left on the resulting page. Click on it, & scroll down to locate the **‘Disable Site’** option.
## **Step 2: Disable Site in xCloud Hosting** [#](/docs/disable-site-in-xcloud-hosting/)
Now, toggle the ‘**Disable Site’** on & click on **‘Save Settings.’** And you’re done with disabling the site in xCloud hosting.
Moreover, you can customize your disable site markup if you wish directly from the dashboard. After changing your markup simply click on ‘**Save Settings.’**
Once you disable your site in xCloud hosting, it will look like as shown below. Moreover, you can enable your anytime by clicking on mentioned **‘Click here.’**
This is how you can easily suspend site, manage cron jobs & customize markup in xCloud hosting.
Still stuck? Contact our [**support team**](/contact/) for any of your queries.
---
# How to Disable WordPress Automatic Updates With xCloud
> Learn how to disable WordPress automatic updates for WordPress core, plugins, and themes on xCloud using dashboard settings, update plugins, or safe custom code.
**Disable WordPress automatic updates** when you want to review WordPress core, plugin, or theme changes before they reach your live site. This guide explains how WordPress automatic updates work on an xCloud-hosted site and how to manage them safely from inside WordPress.
**Important:** xCloud does not currently provide a dashboard setting to disable WordPress automatic updates. WordPress handles its own update system, and update behavior can also be changed by plugins, themes, custom code, or WordPress configuration. If you want to disable WordPress automatic updates, manage the setting inside WordPress.
## Before you disable WordPress automatic updates [#](/docs/disable-wordpress-automatic-updates/)
Automatic updates help keep WordPress secure and maintained. Disabling them gives you more control, but it also means you are responsible for reviewing and installing important security, maintenance, plugin, and theme updates on time.
- Create a fresh backup before changing update settings.
- Use a staging site to test major updates when possible.
- Keep security and maintenance updates enabled unless you have a manual update process.
- Review plugin and theme changelogs before updating business-critical sites.
- Keep a rollback plan ready before changing WordPress core update behavior.
## What this guide covers [#](/docs/disable-wordpress-automatic-updates/)
- How WordPress automatic updates work
- How to disable plugin auto updates from the WordPress dashboard
- How to disable theme auto updates from the WordPress dashboard
- How to disable WordPress automatic updates with a plugin
- How to disable WordPress core automatic updates with custom code
- How to verify that automatic updates are disabled
- What to do if updates still happen after changing the setting
## How WordPress automatic updates work [#](/docs/disable-wordpress-automatic-updates/)
WordPress can update different parts of your site automatically, including WordPress core, plugins, themes, and translation files. Minor WordPress core security and maintenance releases may run automatically in the background. Plugins and themes can also be configured to auto update from the WordPress admin area.
Automatic updates reduce maintenance work, but they can occasionally cause compatibility issues with a plugin, theme, custom code, checkout flow, form, membership system, or third-party integration. For this reason, some site owners prefer to disable WordPress automatic updates and review changes manually.
If your site is hosted on xCloud, the update control still comes from WordPress itself. xCloud can help with hosting-side workflows such as backups, staging, logs, restore options, and server checks, but WordPress core update behavior is controlled inside the WordPress installation.
## Option 1: Disable plugin auto updates from WordPress [#](/docs/disable-wordpress-automatic-updates/)
Use this option if you want to disable WordPress automatic updates for one or more plugins while keeping other update types unchanged.
1. Log in to your WordPress admin dashboard.
2. Go to **Plugins** → **Installed Plugins**.
3. Find the plugin you want to manage manually.
4. Click **Disable auto-updates** next to that plugin.
5. Repeat the same step for any other plugin you want to manage manually.
After this, WordPress will not automatically update that plugin. You can still install the update manually after checking compatibility.
## Option 2: Disable theme auto updates from WordPress [#](/docs/disable-wordpress-automatic-updates/)
Use this option if your active theme, child theme, or parent theme should not update automatically.
1. Log in to your WordPress admin dashboard.
2. Go to **Appearance** → **Themes**.
3. Click the theme you want to manage.
4. Click **Disable auto-updates**.
5. Check the parent theme as well if your site uses a child theme.
Theme updates can affect layout, templates, custom styling, and block patterns. Test theme updates on staging first if your production site depends on custom design work.
## Option 3: Use a plugin to disable WordPress automatic updates [#](/docs/disable-wordpress-automatic-updates/)
If you want more control without editing files, use a trusted WordPress update management plugin. These plugins usually let you manage WordPress core, plugin, theme, and translation updates from one settings screen.
1. Create a backup of your site.
2. Log in to your WordPress admin dashboard.
3. Go to **Plugins** → **Add New**.
4. Search for a trusted update management plugin, such as **Easy Updates Manager**.
5. Install and activate the plugin.
6. Open the plugin settings page.
7. Choose which update types you want to disable or manage manually.
8. Save your changes.
This is the best option for most users because it avoids direct code changes. Review the plugin settings carefully so you do not disable more update types than intended.
## Option 4: Disable WordPress automatic updates with custom code [#](/docs/disable-wordpress-automatic-updates/)
Use custom code only if you are comfortable managing WordPress configuration. A code snippets plugin or a small custom plugin is usually safer than editing your active theme’s `functions.php` file, because theme updates can overwrite theme file changes.
### Disable all WordPress automatic updates [#](/docs/disable-wordpress-automatic-updates/)
To disable all WordPress background automatic updates, add this line to your site’s `wp-config.php` file before the line that says `/* That's all, stop editing! Happy publishing. */`:
```
define( 'AUTOMATIC_UPDATER_DISABLED', true );
```
Copy to Clipboard
This disables the automatic updater. Use it carefully because it can stop important background updates.
### Disable WordPress core automatic updates [#](/docs/disable-wordpress-automatic-updates/)
To disable WordPress core automatic updates, add this line to `wp-config.php`:
```
define( 'WP_AUTO_UPDATE_CORE', false );
```
Copy to Clipboard
This gives you manual control over WordPress core updates. Check for new WordPress releases regularly and apply security updates as soon as possible.
### Disable plugin automatic updates with a code snippet [#](/docs/disable-wordpress-automatic-updates/)
Add this snippet using a code snippets plugin or a small custom plugin:
```
add_filter( 'auto_update_plugin', '__return_false' );
```
Copy to Clipboard
### Disable theme automatic updates with a code snippet [#](/docs/disable-wordpress-automatic-updates/)
Add this snippet using a code snippets plugin or a small custom plugin:
```
add_filter( 'auto_update_theme', '__return_false' );
```
Copy to Clipboard
### Disable translation automatic updates [#](/docs/disable-wordpress-automatic-updates/)
If you also want to disable automatic translation updates, add this snippet:
```
add_filter( 'auto_update_translation', '__return_false' );
```
Copy to Clipboard
## Recommended method for xCloud users [#](/docs/disable-wordpress-automatic-updates/)
For most xCloud users, we recommend this order when you need to disable WordPress automatic updates:
1. Use the WordPress dashboard to disable auto updates for selected plugins or themes.
2. Use a trusted update management plugin if you need broader control.
3. Use custom code only when you understand the impact and have a rollback plan.
Do not disable WordPress automatic updates and then ignore maintenance. Plan a regular update schedule so your site continues receiving security fixes.
## How to verify automatic updates are disabled [#](/docs/disable-wordpress-automatic-updates/)
1. Open your WordPress admin dashboard.
2. Go to **Dashboard** → **Updates**.
3. Review available WordPress core, plugin, and theme updates.
4. Go to **Plugins** → **Installed Plugins** and confirm the auto update action shows the expected state.
5. Go to **Appearance** → **Themes** and confirm the theme auto update setting is correct.
6. Check any update management plugin settings if one is installed.
(Screenshot: WordPress Updates screen showing available updates to review manually)
## Related xCloud docs [#](/docs/disable-wordpress-automatic-updates/)
- [How to Create a Staging Environment in xCloud](/docs/how-to-create-a-staging-environment-in-xcloud/)
- [How to Disable WordPress Update Email Notifications With xCloud](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
You can also review the official WordPress update configuration documentation for advanced update constants and filters: [WordPress upgrade documentation](https://developer.wordpress.org/advanced-administration/upgrade/upgrading/).
## Troubleshooting [#](/docs/disable-wordpress-automatic-updates/)
### I disabled auto updates, but updates still appear in WordPress [#](/docs/disable-wordpress-automatic-updates/)
Disabling automatic updates does not hide available updates. WordPress will still show updates in the dashboard so you can review and install them manually.
### A plugin or theme updated after I changed the setting [#](/docs/disable-wordpress-automatic-updates/)
Check whether another update management plugin, custom code snippet, hosting maintenance service, or WordPress configuration rule is controlling updates. Also confirm the setting was changed for the correct site, plugin, or theme.
### My site broke after a manual update [#](/docs/disable-wordpress-automatic-updates/)
Restore from a recent backup if needed, then test the update on staging before applying it again. If the issue is caused by plugin, theme, or custom code compatibility, contact the plugin/theme developer or your site developer for help.
### xCloud settings did not stop WordPress auto updates [#](/docs/disable-wordpress-automatic-updates/)
xCloud notification settings do not control WordPress core, plugin, or theme automatic updates. WordPress automatic updates must be managed inside each WordPress site.
## FAQ [#](/docs/disable-wordpress-automatic-updates/)
### Does xCloud disable WordPress automatic updates? [#](/docs/disable-wordpress-automatic-updates/)
No. xCloud does not currently provide a dashboard-level control to disable WordPress automatic updates. WordPress handles automatic updates inside each WordPress installation.
### How do I disable WordPress automatic updates? [#](/docs/disable-wordpress-automatic-updates/)
You can disable WordPress automatic updates from the WordPress dashboard for plugins and themes, with an update management plugin, or with safe custom code in `wp-config.php` or a custom plugin.
### Should I disable all WordPress automatic updates? [#](/docs/disable-wordpress-automatic-updates/)
Only disable the update types you plan to manage manually. Keeping security and maintenance updates enabled is usually safer unless you have a regular update review process.
### Can xCloud Support disable WordPress auto updates for me? [#](/docs/disable-wordpress-automatic-updates/)
xCloud Support can guide you on backups, staging, restore options, logs, and hosting-side checks. Custom WordPress code changes, plugin configuration, theme compatibility, and update strategy are usually handled by your site developer or WordPress administrator.
### What should I do after disabling automatic updates? [#](/docs/disable-wordpress-automatic-updates/)
Set a regular maintenance schedule. Review updates, create backups, test important changes on staging, and apply security updates as soon as possible.
---
# How to Disable WordPress Update Email Notifications With xCloud - xCloud
> Learn how to disable WordPress update email notifications using xCloud without turning off automatic updates. Reduce inbox clutter while keeping your site secure and updated.
WordPress can send email notifications after automatic core, plugin, or theme updates. If you manage many WordPress sites, these emails can fill your inbox even when the updates completed successfully.
Use this guide to disable WordPress update email notifications while keeping automatic updates enabled.
## Prerequisites [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
- Access to your xCloud account
- WordPress administrator access for the site
- Permission to add a code snippet or edit site files
- A recent backup before changing site code
## Before you start [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
WordPress update emails are different from xCloud notifications.
- **xCloud notifications** are controlled from `https://app.xcloud.host/user/notifications`.
- **WordPress update emails** are generated by WordPress inside each site.
If you want to stop xCloud notification emails, use the xCloud notification settings page. If you want to stop emails such as “Some plugins were automatically updated” or WordPress core update emails, use the steps below.
## Recommended method [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Use a code snippet manager or a small custom plugin when possible. This keeps the code separate from your active theme.
Avoid editing the active theme’s `functions.php` file unless you are comfortable with PHP. A syntax error in `functions.php` can break the WordPress dashboard, and theme updates can overwrite custom changes.
## Step-by-step Guide To Disable WordPress Update Email Notifications [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
### 1\. Open the WordPress site in xCloud [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Log in to xCloud, open **Sites**, and select the WordPress site where you want to disable update emails.
### 2\. Create a backup [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Before adding custom PHP code, create a current backup of the site or confirm that a recent backup is available.
### 3\. Choose where to add the snippet [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Choose one safe place for the code:
- A code snippet plugin inside WordPress
- A small custom plugin
- A child theme’s `functions.php` file
For most users, a code snippet plugin is the safest option because it reduces the risk of losing the code during a theme update.
### 4\. Add the snippet to disable successful update emails [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Add this snippet if you want to stop successful automatic update emails for WordPress core, plugins, and themes.
/\*\*
\* Disable successful WordPress automatic update email notifications.
\* Updates still run. Only the email notifications are disabled.
\*/
add\_filter( 'auto\_core\_update\_send\_email', function ( $send, $type, $core\_update, $result ) {
if ( 'success' === $type ) {
return false;
}
return $send;
}, 10, 4 );
add\_filter( 'auto\_plugin\_update\_send\_email', '\_\_return\_false' );
add\_filter( 'auto\_theme\_update\_send\_email', '\_\_return\_false' );
This keeps WordPress updates active. It only stops the automatic update notification emails.
### 5\. Save and activate the snippet [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Save the snippet and activate it. If your snippet plugin supports execution location, run the snippet on the site frontend and admin area, or use the default site-wide option.
### 6\. Confirm updates are still enabled [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Open **Dashboard** → **Updates** in WordPress and confirm your core, plugin, and theme update settings still match your preferred workflow.
(Screenshot: WordPress Dashboard Updates page)
### 7\. Monitor the next automatic update [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
After the next automatic update runs, confirm that the site updates normally and that WordPress no longer sends the update notification email you disabled.
(Screenshot: WordPress plugins page showing updated plugin version)
## Disable only one type of WordPress update email [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
If you do not want to disable all WordPress update emails, use one of these smaller snippets instead.
### Disable only WordPress core update emails [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
add\_filter( 'auto\_core\_update\_send\_email', '\_\_return\_false' );
### Disable only plugin update emails [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
add\_filter( 'auto\_plugin\_update\_send\_email', '\_\_return\_false' );
### Disable only theme update emails [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
📄
filename.js
add\_filter( 'auto\_theme\_update\_send\_email', '\_\_return\_false' );
You can combine these snippets based on the emails you want to stop.
## Safer option: keep failure emails for WordPress core [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
If you want to stop successful core update emails but keep failure emails, use this version for core updates:
add\_filter( 'auto\_core\_update\_send\_email', function ( $send, $type, $core\_update, $result ) {
if ( 'success' === $type ) {
return false;
}
return $send;
}, 10, 4 );
This can be useful when you want fewer routine emails but still want to know if a WordPress core update fails.
## Expected result [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
After the snippet is active:
- WordPress can continue installing automatic updates.
- Successful update notification emails are no longer sent for the selected update types.
- xCloud notifications are unchanged unless you also update your xCloud notification settings.
- You can still check update history and plugin versions inside WordPress or xCloud.
## Troubleshooting [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
### I still receive xCloud notification emails [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
WordPress snippets only control emails generated by WordPress. To disable xCloud notifications, visit [this page](https://app.xcloud.host/user/notifications)
Then turn off **Email** in the notification sections you do not want.
### I still receive WordPress update emails [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Confirm the snippet is active on the correct WordPress site. If you manage multiple websites, add the snippet to each site where you want WordPress update emails disabled.
### My site shows an error after adding the snippet [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
Disable the snippet from your code snippet plugin if possible. If you edited a file directly, restore the file from backup or remove the snippet through File Manager or SSH.
### I use a child theme [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
You can add the snippet to the child theme’s `functions.php` file, but a code snippet plugin or small custom plugin is safer for most users.
## FAQ [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
### Does this disable WordPress updates? [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
No. The snippets only disable update notification emails. They do not disable the update process.
### Can I apply this to all websites from one xCloud setting? [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
No. These emails are generated inside WordPress, so the snippet must be added to each WordPress site where you want to disable the emails.
### Can xCloud disable these WordPress emails for me automatically? [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
xCloud notification settings control xCloud notifications. WordPress update emails are controlled inside each WordPress site. You can use the snippet in this guide to control them per site.
### Should I disable all update emails? [#](/docs/disable-wordpress-update-email-notifications-with-xcloud/)
If you manage many sites and monitor updates from a dashboard or maintenance workflow, disabling routine success emails can reduce noise. Keep failure or security alerts enabled if your team depends on email for issue detection.
---
# Does xCloud Support ARM servers? - xCloud
> Learn how to setup ARM servers with xCloud and how you can get ARM servers with Hetzner.
xCloud supports ARM servers across multiple cloud providers, like Hetzner. Now, xCloud provides built-in support for the Hetzner cloud server. Moreover, you can connect any provider that is based on ARM server and set up with xCloud. This compatibility ensures you get a cost-effective solution with seamless performance and efficiency.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Enable 8G Firewall in xCloud? - xCloud
> Learn how to enable 8G firewall in xCloud and enhance your website's security from the step-by-step guide.
The **8G Firewall** is a robust security solution for OLS servers, protecting a variety of threats, including SQL injections, cross-site scripting (XSS), remote code execution, and malicious bots. With xCloud, you can easily enable 8G Firewall in xCloud with a few clicks.
## **What Is An 8G Firewall?** [#](/docs/enable-8g-firewall-in-xcloud/)
The [**8G Firewall**](https://perishablepress.com/8g-firewall/), an enhanced web application firewall (WAF), is a set of web-server rules that filter out common malicious traffic before it hits your website. This lightweight firewall is an advanced iteration of the earlier 7G Firewall developed by Perishable Press. The 8G Firewall aims to reduce the cost of traffic requesting PHP/WordPress resources and enhance overall site security.
## **8G Firewall: Top Features & Goals** [#](/docs/enable-8g-firewall-in-xcloud/)
- Security via simplicity
- Extensive firewall protection
- Fine-tuned to minimize false positives
- Lightweight (only 14 KB!), modular, flexible, and fast
- Completely plug-&-play with no configuration required
- Improves security, reduces server load, and conserves resources
- Git/SVN friendly (does not block svn/git files et al)
- Open source, easy to use, and completely free
- 100% compatible with WordPress
- Enhanced bad bot detection
- Built-in logging
## **Types Of Attacks & Threats 8G Protects Against** [#](/docs/enable-8g-firewall-in-xcloud/)
- Directory Traversal
- HTTP Response Splitting
- (XSS) Cross-Site Scripting
- Cache Poisoning
- Dual-Header Exploits
- SQL/PHP/Code Injection
- File Injection/Inclusion
- Null Byte Injection
- WordPress exploits such as revslider, timthumb, fckeditor, et al
- Exploits such as c99shell, phpshell, remoteview, site copier, et al
- PHP information leakage
📚 Read more on the 8G Firewall [**here**](https://perishablepress.com/8g-firewall/).
## **How To Enable 8G Firewall On Website With OLS** [#](/docs/enable-8g-firewall-in-xcloud/)
With a few clicks, you can enable the 8G Firewall on your website from your xCloud end. Follow the steps below to enable it.
### **Step1: Log in to xCloud Dashboard** [#](/docs/enable-8g-firewall-in-xcloud/)
First, login to your xCloud dashboard and go to your website. From there move to the **‘Tools’** tab and click on the **‘Security’** tab.
### **Step 2: Enable 8G Firewall Option** [#](/docs/enable-8g-firewall-in-xcloud/)
Now, From the **‘Security’** section, you will find an option to enable the **8G Firewall.** Simply, toggle on the 8G Firewall option and click on the **‘Save Settings’** button.
This is how you can easily enable the 8G Firewall from the xCloud dashboard.
## **8G Firewall Location on Server** [#](/docs/enable-8g-firewall-in-xcloud/)
You can view the 8G Firewall configuration location With the below file path:
/var/www/yourdomain.com/.htaccess
The conditional rules for each site can be found in the .htaccess file
## **Check 8G Logs** [#](/docs/enable-8g-firewall-in-xcloud/)
You can find the 8G logs from the ‘**Site Monitoring’** tab**.** Move to the ‘**Site Monitoring’ →‘Logs’** tab and select ‘**OpenLitepeed Log’** from the dropdown arrow.
## **How To Enable 8G Firewall on Website With NGINX** [#](/docs/enable-8g-firewall-in-xcloud/)
You can also enable the NGINX on your NGINX servers.
## **Issues And Troubleshoots** [#](/docs/enable-8g-firewall-in-xcloud/)
With this type of firewall, you may face some issues or troubleshoots. One of the drawbacks is that certain legitimate activities may get blocked. The 8G Firewall is highly effective at blocking a wide range of malicious activities, but it can also inadvertently block legitimate actions and plugins due to its stringent security rules. Here are some specific issues that may arise:
- **Elementor Editing**: The 8G Firewall has been known to block the editing capabilities of the Elementor plugin, resulting in 403 Access Denied errors when trying to preview, edit, or access Elementor pages ([WordPress.org](https://wordpress.org/support/topic/8g-firewall-preventing-elementor-editing/)).
- **SEO Tools**: Certain rules in the 8G Firewall can interfere with SEO plugins, such as blocking requests from tools like Ahrefs and preventing the loading of CSS and JavaScript files necessary for plugins like Rank Math SEO ([Perishable Press](https://perishablepress.com/8g-firewall/)).
- **Admin Access**: Some rules may block access to various admin functions and pages, causing issues with wp-admin and other administrative scripts. This can lead to errors when trying to access plugin settings or perform administrative tasks. ([WordPress.org](https://wordpress.org/support/topic/8g-firewall-preventing-elementor-editing/)).
Due to these potential conflicts, users may need to deactivate the 8G Firewall temporarily adjust its configuration to allow specific actions, or whitelist certain plugins and services.
**Note:** We are continually focused on enhancing security and will bring more advanced features soon.
Still stuck? Contact our dedicated [**support team**](https://support.xcloud.host/?_gl=1*1pcf7m6*_ga*NTcyNTk2ODAwLjE3MjAzNDE5MzM.*_ga_GS7G4T8PYV*MTcyMzQ0NzY1Ni4zMS4wLjE3MjM0NDc2NTYuMC4wLjA.) for any of your queries.
**Related docs**:
[How To Easily Configure Firewall Management With xCloud Hosting](/docs/how-to-configure-firewall-management-in-xcloud/)
[How To Use xCloud 7G Firewall On Nginx](/docs/use-xcloud-7g-firewall-on-nginx/)
---
# How to Enable AI Bot Blocker for Your Website in xCloud? - xCloud
> Protect your site from AI bots in seconds! Follow this easy guide to enable xCloud's AI Bot Blocker and safeguard your content & analytics.
AI crawlers and automated scrapers now account for a growing share of web traffic, and most of it does nothing for your site, it copies your content without permission, inflates your server load, and skews your analytics with visits that were never real people. The AI Bot Blocker in xCloud gives you a simple way to shut that traffic out.
Built right into your site settings as a single on/off toggle, the feature lets you control automated traffic without touching a line of code. By blocking unwanted AI bots, you protect your content from unauthorized scraping, lighten the load on your server, and keep your analytics clean so your data reflects genuine visitor engagement. The result is a site that stays faster, with more secure management, all from one place.
Follow the step-by-step guide below to enable the AI Bot Blocker for your website in xCloud.
## Step 1: Access Site Settings in xCloud [#](/docs/enable-ai-bot-blocker-in-xcloud/)
Log in to your **[xCloud dashboard](http://app.xcloud.host/?fbclid=IwY2xjawSqNrBleHRuA2FlbQIxMABicmlkETFyWlJrdjRXNTgyRERjUU1lc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHqvcpIMNgDG3QVQRfY110uaxeRsO71Yu90ofc0-DVvFCJT-1p_0HMgh2GqWv_aem_kNYuYV2V4OvXzj2Tf0e9WQ&utm_source=docs&utm_medium=organic&utm_campaign=docs)** and go to ‘Sites’. Click on the site where you want to enable the bot blocker.
## Step 2: Enable the AI Bot Blocker [#](/docs/enable-ai-bot-blocker-in-xcloud/)
You will find the ‘AI Bot Blocker’ feature available for both Nginx and OpenLiteSpeed servers. If you are using the Nginx server, navigate to ‘Tools → Nginx and Security’ from the navigation menu. Then find the ‘AI Bot Blocker’ listed along with other Nginx Options. Now, to enable this, just toggle it on.
However, if you are using the OpenLiteSpeed server, similarly navigate to ‘Tools → Security’ from the navigation menu and you will find the ‘AI Bot Blocker’ listed along with other OpenLiteSpeed Options.
## Step 3: Allow/ Block AI Bots [#](/docs/enable-ai-bot-blocker-in-xcloud/)
Once enabled, the AI Bot Blocker automatically blocks 180+ known AI-related bots, including but not limited to:
- Hugging Face
- Hypotenuse AI
- iaskspider
- ICC-Crawler
- ImagesiftBot
- img2dataset
- INK Editor
- INKforall
- IntelliSeek.ai
- Inferkit
- ISSCyberRiskCrawler
- JasperAI
- Kafkai
- Kangaroo
- Keyword Density AI
- LeftWingGPT
- LLaMA
- magpie-crawler
- MarketMuse
- Meltwater
- Meta AI
- Meta Llama
- Meta.AI
- Meta-AI
- Meta-ExternalAgent
- Meta-ExternalFetcher
- MetaAI
- MetaTagBot
- Mistral
- Narrative Device
- Neural Text
- NeuralSEO
- OAI-SearchBot
- OAI SearchBot
- omgili
- OmniGPT
- Open AI
- OpenAI
- OpenText AI
- Outwrite
- Page Analyzer AI
- PanguBot
- Paraphraser.io
- peer39\_crawler
- PerplexityBot
- PetalBot
- ProWritingAid
- QuillBot
- RightWingGPT
- RobotSpider
- Rytr
- SaplingAI
- Scalenut
- Scrapy
- ScriptBook
- SearchGPT
- SemrushBot
- SEO Content Machine
- SEO Robot
- Sidetrade
- Simplified AI
- SlickWrite
- Spin Rewriter
- Spinbot
- Stability
- Sudowrite
- Surfer AI
- Text Blaze
- TextCortex
- The Knowledge AI
- Timpibot
- VelenPublicWebCrawler
- Vidnami AI
- WebChatGPT
- Webzio
- Whisper
- WordAI
- Wordtune
- Writecream
- WriterZen
- Writescope
- Writesonic
- x.AI
- xAI
- YouBot
- Zero GTP
- ZimmWriter
- Claude-User
- Claude-SearchBot
- Perplexity-User
- PhindBot
- Andibot
- SBIntuitionsBot
- Poseidon Research Crawler
- Cotoyogi
- Factset\_spyderbot
- TikTokSpider
- YandexAdditional
- Devin
To manage individual bots, simply choose your preferred bot from the dropdown, select **Allow** or **Block** according to your preference, and then click the **Add** button.
## Step 4: Exclude Any Specific Bot From Allowed/ Blocked List [#](/docs/enable-ai-bot-blocker-in-xcloud/)
If you want to remove a specific bot from your allowed or blocked list, just click the cross (×) icon beside that bot. It will instantly remove that bot from the list.
This is how you can easily enable the AI Bot Blocker for your site in xCloud.
The AI Bot Blocker is one of the quickest ways to take back control of your website’s traffic in xCloud. With a single toggle, you can shut out unwanted AI crawlers, protect your original content from scraping, ease the strain on your server, and keep your analytics honest — all without any technical setup. Whether you’re running Nginx or OpenLiteSpeed, the feature fits right into your existing workflow and gives you the flexibility to allow or block specific bots whenever you need to. Turn it on once, fine-tune it to your preferences, and let xCloud handle the rest while you focus on delivering a fast, secure experience to your real visitors.
This is how easily you can enable AI Bot Blocker for your site in xCloud. Thanks to [**Perishable Press**](https://perishablepress.com/) for their research and [**article about this**](https://perishablepress.com/ultimate-ai-block-list/).
Still feeling stuck? Contact the [**support team**](/support/) for further assistance.
---
# How To Enable HTTPS For WordPress Site In xCloud & Configure SSL Certificates? - xCloud
> In xCloud, you can enable/disable HTTPS for WordPress sites and configure SSL Certificates in a few clicks to ensure site secure and build trust with visitors.
Enabling HTTPS for a WordPress site and configuring SSL certificates is crucial for ensuring secure data transmission, safeguarding sensitive information, and building trust with visitors. In xCloud, you can easily enable or disable HTTPS for WordPress sites.
## How To Enable HTTPS For WordPress Site In xCloud & Configure SSL Certificates [#](/docs/enable-https-in-xcloud-configure-ssl-certificates/)
In xCloud, you can enable or disable HTTPS for WordPress sites in a few clicks. To enable HTTPS on your website, go to the **SSL/HTTPS tab** from the xCloud site dashboard and Toggle on the HTTPS button. You can configure SSL certificates in three ways.
1. Use free SSL certificate issued & managed by xCloud
2. Provide your own certificate & manage it yourself
3. Use Cloudflare managed SSL Certificate
### #1 Use Free SSL Certificate Issued & Managed By xCloud [#](/docs/enable-https-in-xcloud-configure-ssl-certificates/)
With xCloud, you can easily use free SSL certificates issued and managed by xCloud on your site without any complexity. xCloud will handle SSL automatically. To enable HTTPS on your website, go to the SSL/HTTPS tab from the xCloud site dashboard. Click on the ‘**Use free SSL certificate issued & managed by xCloud**’ option. For more details, [**read this documentation**](/docs/install-lets-encrypt-ssl-certificate/).
### #2 Provide Your Own Certificate & Manage It Yourself [#](/docs/enable-https-in-xcloud-configure-ssl-certificates/)
In xCloud, you can provide your own certificate and manage SSL/HTTPS by yourself. You can use the custom certificate from any 3rd party web application for security providers. From the xCloud site dashboard, go to the SSL/HTTPS tab. Click on the ‘**Provide your own certificate & manage it yourself**’ option. Now provide the Certificate. For more details, **[read this documentation](http://use-custom-certificate-of-cloudflare-with-xcloud)**.
### #3 Use Cloudflare managed SSL Certificate [#](/docs/enable-https-in-xcloud-configure-ssl-certificates/)
If you manage your domain with Cloudflare, the SSL will be managed by xCloud automatically. You have to integrate your Cloudflare account with xCloud and add your own certificates. For this, go to the xCloud site dashboard and click on the SSL/HTTPS tab. Click on the ‘**Use Cloudflare managed SSL Certificate**’ option. For more details, [**read this documentation**](/docs/using-xcloud-with-cloudflare-for-dns-management/).
Thus you can easily enable/disable HTTPS for the WordPress website in xCloud and configure SSL Certificates.
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How to Enable Redis Object Cache Plugin With OpenLiteSpeed - xCloud
> Learn how to enable Redis Object Cache plugin with OpenLiteSpeed for WordPress on xCloud with easy step by step guide.
**[Redis Object Cache](/docs/how-to-find-the-redis-credentials/)** is a powerful caching solution that helps improve the performance and scalability of WordPress websites. By integrating Redis with your xCloud server running OpenLiteSpeed, you can reduce database queries, speed up page loads, and provide a smoother experience for your visitors.
The LiteSpeed Cache plugin already includes Redis integration, so you do not need to install any additional plugin if you do not want it. However, this guide is for those who prefer to use the Redis Object Cache plugin separately instead of LiteSpeed’s built-in Redis option.
Let us follow the step-by-step process to enable [**Redis Object Cache plugin**](https://wordpress.org/plugins/redis-cache/) with OpenLiteSpeed servers correctly and without conflicts.
## **Step 1. Enable LiteSpeed Cache Plugin** [#](/docs/enable-redis-object-cache-plugin-with-ols/)
First, go to your site from the dashboard. Then, find the **‘WordPress’** option from the side navigation bar and toggle on the ‘LiteSpeed Cache’ button to enable the plugin from the xCloud dashboard.
Once you toggle on the **‘LiteSpeed Cache’,** you will get the **‘Redis User’,** **‘Redis Password’** and **‘Redis Object Cache Key’** or Redis Prefix. Collect the credentials.
## **Step 2: Access the wp-config.php file** [#](/docs/enable-redis-object-cache-plugin-with-ols/)
Next, go to **‘WordPress’ → ‘WP Config’** from the sidebar to customize the wp-config file directly from the xCloud dashboard.
Once you are in the wp-config.php editor panel. Add the following code into the editor and update the username, password, and prefix with the Redis credentials you collected earlier from the LiteSpeed Cache page. After updating the values, click on the Update Config button to save the changes.
Copy to clipboard
1
2
3
define( 'WP\_REDIS\_PASSWORD', \["user", "password"\] );
define( 'WP\_REDIS\_DISABLE\_BANNERS', 'true' );
define( 'WP\_REDIS\_PREFIX', 'prefix' );
## **Step 3: Turn OFF or Uninstall the Object Cache Plugin** [#](/docs/enable-redis-object-cache-plugin-with-ols/)
To use the Redis Object Cache in OpenLiteSpeed servers, you need to prevent conflicts between caching systems. LiteSpeed Cache plugin handles both Full Page Cache and Object Cache, and Redis is already configured inside it.
- If you want to use the Redis Object Cache plugin separately, you must either disable the Object Cache option in LiteSpeed Cache or uninstall the plugin entirely.
- If you want to continue using LiteSpeed Cache for full page caching only, then just disable the Object Cache option.
Go to **LiteSpeed Cache → Cache**, turn off the **Object Cache** button, and click **Save Changes** to proceed.
You can also uninstall and deactivate the LiteSpeed Cache plugin. Just go to **Plugins → Installed Plugins** and locate ‘**LiteSpeed Cache (LS Cache)’**. Deactivate and uninstall the LS Cache plugin to prevent conflicts between caching systems.
## **Step 4. Install And Activate Redis Cache Plugin** [#](/docs/enable-redis-object-cache-plugin-with-ols/)
Next, you will configure WordPress to use the Redis cache plugin. Log in to your WordPress admin dashboard. Navigate to ‘**Plugins’ → ‘Add New’**. In the search bar, type **‘Redis Object Cache**‘. Click ‘**Install Now**‘ and then ‘**Activate’**.
After installing and activating the plugin go to the **‘Settings’ → ‘Redis**‘ from the sidebar and just click on the ‘Enable Object Cache’ button from the dashboard.
If configured correctly, you will see a success message indicating that Redis is connected. Look for the Overview tab. It should show:
> Status: Connected
>
> Filesystem: Writeable
>
> Redis: Reacable
If you see these values, your Redis cache is active and working.
And that’s it, this is how easily you can enable Redis Object Cache on OLS server with xCloud. With Redis successfully connected, your WordPress website will run faster, handle more traffic efficiently, and deliver a seamless experience to your users.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Enable the Edge Full Page Cache in xCloud - xCloud
> Learn how to easily enable Edge Full Page Cache in xCloud to boost your site’s speed by up to 40% with powerful, network-level caching via Cloudflare.
**[Caching](/docs/how-caching-works-in-xcloud/)** plays a crucial role in boosting website performance and delivering a faster, smoother browsing experience for users. At xCloud, we know that speed and performance are critical for a great user experience. That’s why we offer powerful Edge Caching, which saves your site’s page cache to a global network of data centers, delivering content from the location closest to each visitor. This can boost your website speed and performance.
Along with edge caching, we implement heavy caching layers both at the server level and through Page Caching and Object Caching, ensuring lightning-fast load times. By default, our edge cache refreshes every 24 hours, but you have full control — you can adjust cache expiration times or manually clear caches as needed. Whether you’re deploying updates, copying your site, or simply editing a post, purging the right cache ensures your changes appear instantly.
At xCloud, edge caching is included with all plans at no extra cost — no plugins required. If your site is integrated with Cloudflare, you will be able to access this feature with a click.
_**Note:** To use this feature, you must integrate Cloudflare with xCloud and configure your site accordingly. It is also recommended to maintain a full-page cache alongside the Edge Cache for optimal performance. You can continue using your existing full-page caching solutions, such as **FastCGI (NGINX Cache)**, **LiteSpeed Cache (LSCache)**, or **WP Rocket**, together with the Edge Cache._
## **Edge Full Page Cache** [#](/docs/enable-the-edge-full-page-cache/)
Edge Full Page Cache is an optional layer of caching at the network level that improves your website’s performance. This feature caches the website’s HTML and stores it on Cloudflare’s CDN network, enhancing the Time to First Byte (TTFB) and latency for most websites.
If your domain is currently configured using Advanced Network or Global Edge Security (GES), most of your static assets are already cached through Cloudflare’s CDN. However, HTML files by default are served directly from the servers. With Edge Full Page Cache enabled, HTML pages are also cached at Cloudflare’s edge, making assets geographically closer to your visitors and improving overall page performance.
## **How Does Edge Caching Work?** [#](/docs/enable-the-edge-full-page-cache/)
Edge caching operates by strategically distributing cached copies of website content across multiple servers at the edge of a content delivery network (CDN), closer to end-users. Here’s a detailed breakdown of how it works:
**Request** **Routing:** When a user/visitor requests content from a website, such as HTML files, images, videos, or other resources, their request is initially routed to the CDN’s edge servers, which are distributed worldwide.
**Edge Server Selection:** The CDN intelligently selects the edge server nearest to the user requesting the content. This selection is based on factors such as the user’s geographical location, network conditions, and server availability.
With **over 200 edge server locations worldwide powered by Cloudflare**, your content is delivered from the edge server nearest to the visitor. This reduces the need for requests to travel across continents to your origin server, minimizing latency and improving page load times significantly.
## **Steps to Enable the Edge Full Page Cache in xCloud** [#](/docs/enable-the-edge-full-page-cache/)
Caching content at the network edge significantly improves website performance by reducing latency and load times for visitors. xCloud makes it easy to enable full-page caching using their Edge Caching feature, allowing for a faster and more responsive experience for your users. This guide will walk you through the process of enabling Edge Full Page Cache in xCloud step-by-step.
### **Step 1: Access the Site Dashboard** [#](/docs/enable-the-edge-full-page-cache/)
First, navigate to the dashboard of the site where you want to enable Edge Caching. Once logged in, locate and click on the **‘Caching’** option from the main menu.
### **Step 2: Enable Edge Caching** [#](/docs/enable-the-edge-full-page-cache/)
Within the Caching section, click on the **‘Edge Caching’** button to activate the feature.Next, click on **‘Advanced Settings’** to access additional configuration options.
### **Step 3: Configure Cache Exclusion Rules** [#](/docs/enable-the-edge-full-page-cache/)
In the Advanced Settings menu, you will find options to customize caching behavior:
- **Cache Exclusion HTTP URL Rules**: Specify URL patterns you want to exclude from being cached.
- **Cache Exclusion Cookie Rules**: Define cookie-based rules to prevent caching for certain sessions or users.
Set these rules according to your specific preferences or requirements.
### **Step 4: Purge Cache** [#](/docs/enable-the-edge-full-page-cache/)
After configuring the caching settings, click on the **‘Purge Cache’** button. This action will clear all previously cached content from Cloudflare’s edge network, ensuring the updated rules are applied immediately. After all the configurations, click on the **‘Save Settings’** button.
Afte that, if you go to your xCloud dashboard, you will see the plugin **‘xCloud Cloudflare Edge Cache’** has been installed on your site. From here, if you go to the header menu, you will see the **‘Purge Cache’** button from the dashboard which you can click to purge your site caches easily.
And that’s it. This is how easily you can enable Edge Full Page Cache in xCloud and enhance your site’s performance and user experience. By carefully setting exclusion rules and purging outdated cache, you ensure that your visitors receive the most up-to-date and optimized content.
## **Things to Know Before Enabling Edge Caching** [#](/docs/enable-the-edge-full-page-cache/)
Here are some important considerations to keep in mind when using Edge Caching with xCloud.
#### **Geolocation Variations** [#](/docs/enable-the-edge-full-page-cache/)
Edge Caching does not support narrow-scope geolocation variations, such as caching based on city, state, or border proximity. Sites relying heavily on localized content variations may need to consider alternative caching strategies.
#### **Geo-blocking and IP Blocking** [#](/docs/enable-the-edge-full-page-cache/)
Geo-blocking and IP Deny rules are enforced at the server level (Nginx). Since Edge Caching happens on Cloudflare’s network, visitors from blocked IPs or regions could still access cached versions of your site. Additionally, visits from these blocked IPs will still appear in your site’s analytics data.
#### **Set-Cookie Header Conflicts** [#](/docs/enable-the-edge-full-page-cache/)
Pages that send a **Set-Cookie** header by default are not cached at the edge. To prevent caching visitor-specific data, Cloudflare automatically removes the Set-Cookie header from cached responses for all new sites. This ensures the cache remains consistent and secure.
#### **Cloudflare APO** [#](/docs/enable-the-edge-full-page-cache/)
If you are using your own Cloudflare account, you can utilize Edge Caching only if Cloudflare’s Automatic Platform Optimization (APO) feature is disabled. Edge Caching and APO cannot be active simultaneously, so you will need to choose one or the other.
#### **General Behavior and Compatibility** [#](/docs/enable-the-edge-full-page-cache/)
It’s important to note that after clearing the Edge Cache, you should allow 2 to 5 minutes for the purge to fully propagate across all Cloudflare data centers, as the process isn’t instantaneous.
### **Where Edge Caching Can Be Used** [#](/docs/enable-the-edge-full-page-cache/)
Edge Caching is supported on both Live Sites, Staging Environments and demo site. However, it is not available for Standard Staging Environments. If you are working within a Standard Staging Environment, Edge Caching will not be an option.
### **Content Served by Edge Caching** [#](/docs/enable-the-edge-full-page-cache/)
Edge Caching only caches and serves the page cache of your site, which refers to the HTML output, static assets such as images, JavaScript files, or CSS files.
### **WordPress Compatibility** [#](/docs/enable-the-edge-full-page-cache/)
Edge Caching is fully compatible with standard WordPress setups as well as popular plugins and frameworks like BuddyPress, WooCommerce, and Easy Digital Downloads. Pages that need to bypass caching, such as the WordPress Admin, Cart, Checkout, and My Account pages, are automatically excluded from Edge Caching.
For highly customized WordPress installations, additional custom caching rules may be necessary. The xCloud Support team is available to assist with creating these custom configurations if needed.
### **Cache Clearing Automation** [#](/docs/enable-the-edge-full-page-cache/)
Whenever you update pages or make changes within WordPress, both the Site Cache and Edge Cache are automatically purged. In most cases, manual cache clearing is unnecessary unless you have a specific reason to do so.
### **Custom Cache Exclusions** [#](/docs/enable-the-edge-full-page-cache/)
If your site uses Advanced Site Cache custom exclusions — such as specific combinations of custom cookies and URIs — these are not yet honored by edge caching.
### **Custom Cache Rules** [#](/docs/enable-the-edge-full-page-cache/)
You can safely enable edge caching as long as our Support team has not set up special cache rules for your site involving custom cookies or geolocation-based logic.
### **Cloudflare Edge Cache File Size Limit** [#](/docs/enable-the-edge-full-page-cache/)
When using Cloudflare with xCloud, it’s important to understand that there are limitations on how large a file can be cached at the network edge. According to [Cloudflare’s official guidelines](https://developers.cloudflare.com/pages/platform/limits/), the **maximum size for any single file** cached on the edge is **512 MB** for users on Free, Pro, and Business plans. This limit increases to **5 GB** for Enterprise customers.
And files that exceed this size threshold won’t be cached at Cloudflare’s edge. Instead, those requests will bypass the edge and be delivered straight from your origin server — potentially resulting in slower performance for large files such as video content or software downloads.
**If your site serves large files, consider these alternatives:**
- **Cloudflare R2**: An object storage solution that lets you deliver large files efficiently without incurring egress costs.
- **Disabling Cloudflare Proxy Temporarily**: You can set the DNS proxy (orange cloud icon) to “off” to allow large files to be delivered directly from your server without passing through Cloudflare.
Also note that changing TTL (time-to-live) settings for caching does **not** bypass these file size limits — they are enforced regardless of your cache duration configuration.
Edge Full Page Cache respects the cache-control headers configured by your page caching solution. For example, xCloud installs the FastCGI Cache plugin for NGINX servers, the LiteSpeed Cache plugin for OpenLiteSpeed (OLS) servers, or popular caching plugins like WP Rocket, depending on your server environment.
## **Troubleshooting Edge Caching** [#](/docs/enable-the-edge-full-page-cache/)
If Edge Caching doesn’t seem to be working properly on your xCloud site, there are a few steps you can take to diagnose and fix the issue.
### **Check for Excluded URL Patterns or Cookies** [#](/docs/enable-the-edge-full-page-cache/)
Another potential cause is exclusion based on URL patterns or cookies. Specific sections of your site, like **/cart** or **/checkout**, might be configured to bypass caching automatically. Similarly, pages that depend on custom cookies, such as login sessions or shopping carts, might also be excluded. If you expect a page to be cached but notice that it isn’t, it’s a good idea to contact xCloud Support. They can help verify whether certain pages or cookies have been intentionally excluded from caching or whether any additional custom caching rules are influencing this behavior.
### **Password Protection and Edge Caching** [#](/docs/enable-the-edge-full-page-cache/)
If your site has Password Protection enabled, Edge Caching cannot function. Password protection must be disabled for Edge Caching to work successfully. Make sure to check this setting if Edge Caching appears inactive after other troubleshooting steps.
### **Conflict with Cloudflare APO** [#](/docs/enable-the-edge-full-page-cache/)
If you are using Cloudflare’s Automatic Platform Optimization (APO) service through your own Cloudflare account, it will conflict with Edge Caching. In order for Edge Caching to operate correctly, you must disable APO. It’s important to ensure that only one optimization service is managing cache behavior to avoid conflicts.
### **Geo-blocking and IP Blocking Considerations** [#](/docs/enable-the-edge-full-page-cache/)
Since Edge Caching operates at Cloudflare’s network level, it does not respect geo-blocking rules that are configured at the server (Nginx) level. This means visitors from regions that you intended to block might still receive cached content. Similarly, IP addresses that have been blocked via xCloud’s IP Deny tool may still be able to access cached pages through Cloudflare’s edge network. If maintaining strict geo- or IP-based access control is critical for your site, you may want to reconsider enabling Edge Caching.
Still stuck? Contact our **[support team](/support/)** for any of your queries.
---
# How To Easily Enable WP Debug Tool From xCloud Dashboard - xCloud
> Follow this guide to enable WP Debug tool from xCloud site dashboard.
[**WP Debug**](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/) is a tool in WordPress that helps developers find and fix errors on their website by displaying detailed information about PHP errors, notices, and warnings.
**[xCloud](http://hidden-hamlet-226309.wp1.sh)** now offers an easy way to enable WP Debug directly from your site dashboard, without any manual coding. Just toggle on the **WP Debug** option, and it starts working right away, helping you troubleshoot issues on your WordPress site effortlessly.
We’re introducing the WP debug option to prevent error messages from appearing on your site, which can create a negative experience for your customers. By enabling WP debug from the dashboard, xCloud ensures that these error messages or other unwanted messages are suppressed, maintaining a clean and professional appearance for your site.
Once you’ve turned on the WP Debug option, head over to the **WP Config** tab. You’ll see the updated debug condition code added automatically.
Now, go to the Logs tab, where you’ll find your debug logs along with detailed information.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Export Servers and Sites Data with xCloud - xCloud
> Learn how to easily export server and site data in CSV or Excel format using xCloud with our step-by-step guide.
Exporting server and site data is essential for analysis. With xCloud, you can export your server and site data with just a few clicks. Whether you need your data in CSV or Excel (XLSX) format, xCloud makes the process seamless and user-friendly. Follow the steps below to export both site and server data using xCloud.
**_Note:_** _This feature is available for the team owner only._
## **Step 1: Access the Export Option** [#](/docs/export-servers-and-sites-data-with-xcloud/)
To begin, log in to your xCloud account and ensure you are the **team owner**. Then, navigate to the ‘**Team Settings**’ section from the main dashboard. Once there, click on the ‘**Export’** option under the **‘Team’** menu from the sidebar. This will open the page where you can export your server or site datas.
## **Step 2: Export Site Data** [#](/docs/export-servers-and-sites-data-with-xcloud/)
On the Export page, locate the **‘Select** **Export Type’** dropdown and choose **‘Sites’** as your preferred data category. Next, under the ‘**Export Format’** option, select your desired file format, either ‘**CSV’** or **‘Excel (XLSX)’**.
You can further refine the data by selecting the specific **columns** you want to include in the export. Once all your options are set, simply click the **Export** button to download the sites data to your device.
## **Step 3: Export Server Data** [#](/docs/export-servers-and-sites-data-with-xcloud/)
To export server data, change the **‘Select Export Type’** to **Servers** from the dropdown menu of the same page**.** Just as with site data, you’ll need to choose your preferred **‘Export Format’**, selecting either **‘CSV’** or **Excel (XLSX)’**.
You can further customize the export by choosing the specific **‘Columns’** relevant to your needs. Finally, click the ‘**Export’** button to download the server data.
And that’s it. This is how easily you can export servers and sites data with xCloud. xCloud simplifies the process of exporting both servers and sites data, offering flexibility in format and content selection.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# Fail2Ban in xCloud: Enhancing Server Security With Ease - xCloud
> Follow this simple guide on Fail2Ban management with xCloud, where you can ban & unban IP addresses effortlessly to maintain sheer security.
[**Fail2Ban**](https://en.wikipedia.org/wiki/Fail2ban) is a powerful feature integrated with [**xCloud**](/), that protects your server from unauthorized access attempts and brute-force attacks. It automatically blocks harmful IP addresses from accessing essential services such as SSH, minimizing the risk of security breaches. This proactive method helps stop brute force attacks, spamming, port scanning, and other unauthorized attempts to get into your server.
xCloud has always had Fail2Ban integrated for server security. Now, with our latest update, managing security is simpler than ever. You can easily ban and unban IP addresses directly from your xCloud dashboard as well as ban new IP addresses with just a few clicks, giving you greater control over your server’s protection.
## **How Fail2Ban Works In xCloud** [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
- Automatic Blocking: Fail2Ban quickly stops harmful IP addresses from trying to break into your server.
- SSH Hardening: xCloud secures SSH logins during server setup to stop unauthorized access.
- View Banned IP Addresses: Easily see the list of banned IP addresses that tried to force their way into your server.
- Ban IP: Block an IP address.
- Unban IP: Allow a banned IP address to connect by removing it from the block list.
## **How To Easily Ban IP Addresses With Fail2Ban in xCloud** [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
After successfully logging in/signing up in xCloud, go to the server page dashboard. Under the **Settings** tab, you will find the **Security** option. Click on it and then you will find the Fail2Ban management options.
From here you can see the already Banned IP Addresses. You will have the option to **Unban** the IP addresses if the situation demands.
To ban a new IP address click on **Ban New IP Address, and** a popup will appear. Simply write the address you want to ban and click on **Ban IP,** and it will be banned instantly.
## Whitelisting Trusted IP Addresses in Fail2Ban [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
While Fail2Ban is excellent for blocking malicious actors, you want to ensure you don’t accidentally lock yourself out of your own server. If you have a static IP address or a fixed corporate network range, you can **whitelist** these addresses.
Once an IP is whitelisted (added to the `ignoreip` list), Fail2Ban will never block it, regardless of how many failed login attempts occur.
> **Security Note:** Only whitelist IP addresses that you fully trust. Misconfiguring this step by adding broad ranges can create a security loophole.
### 1\. Open the Jail Configuration File [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
To add a whitelist, first SSH into your server using a sudo user. Then, you need to edit the jail.local file. Use the following command to open it with the Nano editor:
Copy to clipboard
1
sudo nano -l /etc/fail2ban/jail.local
### 2\. Add Your IP to the `ignoreip` Line [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
Locate the line starting with `ignoreip`. By default, Fail2Ban whitelists your local machine (`127.0.0.1/8`).
To add your specific IP (e.g., `192.168.1.100`), append it to the end of the line, separated by a space:
Copy to clipboard
1
ignoreip = 127.0.0.1/8 ::1 192.168.1.100
### 3\. Save and Reload Fail2Ban [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
After adding your IP, save the file by pressing **Ctrl + O**, then **Enter**, and exit with **Ctrl + X**.
To apply the changes, reload the Fail2Ban service. Reloading is preferred over restarting because it refreshes the configuration without interrupting the service:
Copy to clipboard
1
sudo systemctl reload fail2ban
### 4\. Verify the Service Status [#](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/)
It is a best practice to verify that the configuration change didn’t cause any errors. Check the service status with this command:
Copy to clipboard
1
systemctl status fail2ban
If the output shows **active (running)**, your configuration is successful, and your IP is now protected from being banned.
With Fail2Ban seamlessly integrated into xCloud, you can be confident that your server is shielded from unauthorized access attempts and brute-force attacks. By utilizing this advanced security tool, you can solidify the overall security of your server and reduce the likelihood of security breaches.
Still stuck? Contact our [**support team**](http://support@xcloud.host/) for any of your queries.
---
# How to find Default Paths for PHP, Nginx, and MySQL Configurations in xCloud server - xCloud
> Discover the ways to find default paths for PHP, NGINX, and MySQL configuration in xCloud
When managing a server on a platform like xCloud, knowing where to find configuration files is crucial.
## **How To Find Default Paths in xCloud** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
This guide provides detailed information on how to find default paths for PHP, Nginx, MySQL, and other related configurations on an xCloud server.
### **1\. Site Path** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
The site path is where the files for each of your websites are stored. This directory typically contains the website’s HTML, PHP scripts, images, and other assets needed to display and run the site. Keeping your site files organized and accessible in this directory makes it easier to manage and update your site. For most setups on xCloud, the standard site path is:
- **Site Path:**
```
/var/www/{site-name}
```
Copy to Clipboard
Replace {site-name} with the actual name of your website. For example, if your site is named “example.com” the path would be **/var/www/example.com**
This location is commonly used because it keeps site files separate and organized under the /var/www directory, which is a conventional location for web files on Linux servers.
### **2\. NGINX Configuration Path** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
Nginx is a powerful and popular web server used to serve websites and applications. Each website that Nginx serves typically has its own configuration file, which contains settings such as server names, root directories, and proxy configurations. These configuration files are stored in the following path:
- **Nginx Config Path:**
```
/etc/nginx/sites-available/{site-name}
```
Copy to Clipboard
Here, {site-name} should be replaced with the name of your specific site. For example, a website named “example.com” would have its configuration file at **/etc/nginx/sites-available/example.com**
After creating or modifying a configuration file in this directory, you usually create a symbolic link in the /etc/nginx/sites-enabled/ directory to activate the site.
### **3\. PHP FPM Pool Configuration** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
PHP FastCGI Process Manager (FPM) is a PHP handler that allows for faster processing and better performance by managing pools of PHP workers. Each site or application can have its own FPM pool configuration, which specifies settings like the number of child processes, memory limits, and execution timeouts. These pool configuration files are located in:
- **PHP FPM Pool:**
```
/etc/php/{php-version}/fpm/pool.d/
```
Copy to Clipboard
Substitute {php-version} with the version of PHP that your site is using, such as 7.4 or 8.0. For example, if you are using PHP version 8.0, the path would be /etc/php/8.0/fpm/pool.d. Within this directory, you will find files named after your site or application, which contain pool-specific settings with the **www.site-username.conf** format.
### **4\. Find Default Paths for PHP INI Configuration** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
The php.ini file is the main configuration file for PHP. It sets important options such as memory limits, file upload sizes, and execution time. There are separate php.ini files for different execution contexts: one for PHP-FPM (used by web servers like Nginx) and another for the CLI (Command Line Interface). The paths for these files are:
**For NGINX**
- **FPM Configuration:**
```
/etc/php/{php-version}/fpm/php.ini
```
Copy to Clipboard
- **CLI Configuration:**
```
/etc/php/{php-version}/cli/php.ini
```
Copy to Clipboard
**For OLS**
```
/usr/local/lsws/lsphp83/bin/{php-version}
```
Copy to Clipboard
Replace {php-version} with the specific PHP version you are using. For instance, if using PHP 8.0, the FPM configuration path would be /etc/php/8.0/fpm/php.ini, and the CLI path would be /etc/php/8.0/cli/php.ini. These files control the PHP environment for web and command-line scripts, respectively.
### **5\. Find Default Paths for SSL Certificate**s [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
[**SSL certificates**](/docs/install-lets-encrypt-ssl-certificate/) are essential for securing the connection between a user’s browser and your server. Certificates can come from different sources, such as Let’s Encrypt, which provides free SSL certificates, or custom providers like Cloudflare. The paths to these certificates vary depending on the source:
- **Let’s Encrypt Certificates:**
```
/etc/letsencrypt/live/{site-name}/fullchain.pem
```
Copy to Clipboard
- **Custom, Cloudflare, or Other Certificates:**
```
/etc/nginx/ssl/{site-name}/fullchain.pem
```
Copy to Clipboard
Replace {site-name} with your actual site name. For example, the path for a site named “example.com” using Let’s Encrypt would be **/etc/letsencrypt/live/example.com/fullchain.pem**. For custom certificates, ensure that the files are placed in the /etc/nginx/ssl/{site-name}/ directory and referenced correctly in your Nginx configuration.
### **6\. Log File Paths** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
Log files are vital for monitoring and troubleshooting server operations. They record information about server access, errors, and other events, providing insights into server performance and identifying issues. Common log file paths include:
- `**Debug Log:**`
```
/var/www/{site-name}/wp-content/debug.log
```
Copy to Clipboard
This file logs PHP-related debugging messages for sites using WordPress or custom PHP scripts.
- `**Nginx Log:**`
```
/var/log/nginx/{site-name}*.log
```
Copy to Clipboard
This directory contains general log files related to Nginx, capturing various server events.
- `**Nginx Access Log:**`
```
/var/log/nginx/{site-name}-access.log
```
Copy to Clipboard
This file logs all access requests to your site, providing details about visitor IPs, request types, and response statuses.
- `**Nginx Error Log:**`
```
/var/log/nginx/{site-name}-error.log
```
Copy to Clipboard
This file logs any errors encountered by Nginx, including configuration issues, server errors, and script errors.
- `**MySQL Log:**`
```
/var/log/mysql/
```
Copy to Clipboard
This directory contains logs related to MySQL database activities, which can be useful for monitoring queries, replication issues, and server performance.
### **7\. 7G Firewall Configuration** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
The [**7G Firewall**](/docs/use-xcloud-7g-firewall-on-nginx/) is a set of rules designed to protect web servers from common threats like spam, SQL injection, and other malicious attacks. Configuration files for the 7G Firewall on an xCloud server can be found here:
- `**General 7G Configuration:**`
```
/etc/nginx/conf.d/7g-firewall.conf
```
Copy to Clipboard
This file contains the main rules that apply to the entire server.
- `**Site-Specific 7G Configuration:**`
```
/etc/nginx/xcloud-conf/7g.conf
```
Copy to Clipboard
This file includes conditional rules tailored for individual sites.
These files are critical for securing your server and should be reviewed and updated regularly to adapt to new threats.
### **8\. Site Backup Path** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
Backing up your site is crucial to prevent data loss. On xCloud servers, backups are typically stored in a hidden directory under the root user’s home directory:
- `**Backup Path:**`
```
/root/.backup/
```
Copy to Clipboard
This directory contains backup archives of your site files and databases. Regularly check this directory to ensure backups are being created and consider copying backups to an off-site location for added security.
### **9\. Redis User File Location** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
Redis is a popular in-memory data structure store used as a database, cache, and message broker. On xCloud servers, user access control for Redis is managed using the users.acl file:
- `**Redis User File:**`
```
/etc/redis/users.acl
```
Copy to Clipboard
This file defines user permissions and access control lists (ACLs) for Redis. Make sure to configure this file to restrict access appropriately and secure your Redis installation.
### **10\. Cron job List Path** [#](/docs/find-default-paths-for-php-nginx-and-mysql/)
**[Cron jobs](/docs/how-to-configure-xcloud-cron-job/)** are scheduled tasks that run automatically at specified intervals. They are useful for automating repetitive tasks such as backups, updates, and maintenance. The list of cron jobs is typically stored in:
- `**Cronjob List Path:**`
```
/etc/cron.d/
```
Copy to Clipboard
This directory contains files that define scheduled tasks for various applications and scripts. You can add or modify cron jobs here to schedule tasks like database backups, system updates, and routine maintenance scripts.
These paths are common default locations on xCloud servers, but they can vary based on your specific configuration or server setup. It is always a good practice to double-check these paths, especially after custom configurations or installations, to ensure your server operates securely and efficiently.
---
# How to Find MySQL Root Password in xCloud - xCloud
> Learn how to quickly find your MySQL root password in xCloud through a few simple steps in the dashboard.
Managing your server credentials securely and efficiently is crucial for database administration. If you’re using xCloud to manage your hosting environment, retrieving the MySQL root password is a simple and straightforward process through the xCloud dashboard.
Follow the steps below to find MySQL root password in xCloud with just a few clicks:
## **Step 1: Log In and Access Your Server** [#](/docs/find-mysql-root-password-in-xcloud/)
To begin, log in to your xCloud dashboard. Once you are in, navigate to the **‘Servers’** section, where all your server instances are listed. From there, select the server for which you need the MySQL root password.
## **Step 2: Locate the MySQL Root Password** [#](/docs/find-mysql-root-password-in-xcloud/)
After selecting the server, look at the left-hand side navigation bar and click on the **‘Others’** option. This will take you to a section that includes various server-related settings. Scroll down until you find the **‘Database’** section. In this section, you’ll see the MySQL root password displayed. You can then click the copy icon to securely copy the password for use in your MySQL client or wherever it is needed.
_Note: The password is also sent to the users through mail after any new server creation process is completed_.
That’s it. This is how easily you can get MySQL root password with xCoud. Retrieving your MySQL root password in xCloud is quick and user-friendly, thanks to the intuitive dashboard layout. By following the steps above, you can securely access and manage your MySQL root credentials whenever needed. Always make sure to store your passwords safely and avoid sharing them with unauthorized users.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Setup a GCP(Google Cloud Platform) Server in xCloud? - xCloud
> Complete beginner's guide to launching your first Google Cloud web server. No technical experience needed - follow our step-by-step instructions.
With [**xCloud**](/)**,** you can easily set up the first server with Google Cloud Platform without any coding at all. xCloud aims to simplify the process of hosting and managing WordPress sites, allowing developers and agencies to focus on building great websites without worrying about the underlying infrastructure. Now let’s follow these steps to get you started.
### Step 1: Sign Up/Login With xCloud [#](/docs/first-server-with-google-cloud-platform/)
First, you will need to visit the xCloud website and you have to sign up for xCloud with your credentials. If you have already an account please visit our [**app URL**](/) below:
### Step 2: Create Your New Google Cloud Platform Server [#](/docs/first-server-with-google-cloud-platform/)
After logging in to your xCloud account, start by adding a new server by clicking on the “**Create New Server**” button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a **Google Cloud Platform** server and for that select the **Google Cloud Platform** option. The billing of the server will be handled on your **Google Cloud Platform** account.
All You have to do is upload the json file and create GCP servers instantly from xCloud.
Now the question is where & how to get the json file to upload it in the below-resulting image.
### Step 3: Get The JSON File From Google Platform [#](/docs/first-server-with-google-cloud-platform/)
To get the JSON file you need to follow a few simple steps.
1. Sign in to your Google Cloud Platform with the correct credentials. Once you signed in, switch to your project where you want to create your server and navigate to ‘IAM & Admin’ and click on it.
On the resulting page, navigate to ‘**Service Accounts’ → ‘Create Service Account**‘ to go to the next step.
Fill up your service account name, and account ID & click on **‘Create & Continue.’**
Now, select the role as **‘Owner’** & click on **‘Done’** from below.
Now, locate your account service from the below-resulting page & click on it.
In this step, navigate to **‘Keys’ → ‘Add Key.’**
And here you are finally! Click on JSON as the Key type as shown below & press the Create button from below right. And you will have your JSON file downloaded on your device.
### **Step 4: Enable Google API** [#](/docs/first-server-with-google-cloud-platform/)
To enable Google API, you will find a search bar at the top, search for “**Compute Engine API**” there.
Click **ENABLE** as shown below:
### **Step 5: Create Firewall Policies** [#](/docs/first-server-with-google-cloud-platform/)
You need to configure “default-allow-http” & “default-allow-https” firewall on your GCP account.
**Visit Firewall Policies**
**Create the rules: “default-allow-https” rule.**
Create the rules: “default-allow-http” rule.
**Make sure to Enable both**
### **Step 6: Create a VPC Network** [#](/docs/first-server-with-google-cloud-platform/)
If the project does not show any default VPC network, then you can create a new VPC network by yourself. To create a new VPC network, look for the **‘Create VPC Network’** and click on it. Now a form will pop up on the screen. Here, you need to fill up the form, give it a name set the **‘Subnet creation mode’** to automatic and forward with the **‘Create’** button so that you can create a new VPC network.
Once the VPC network is created, you can manage all firewall rules on the Firewall rules page. Select any firewall rules below that you would like to apply to this VPC network from the below menu. Then roll down to the next section where you will set the Dynamic routing mode to **‘Regional’** and press on the **‘Create’ button.**
### **Step 7: Add Necessary Information** [#](/docs/first-server-with-google-cloud-platform/)
After uploading the correct json file now you need to provide the **Server name**, your preferred **Server Specifications** (CPU, RAM, storage), and the **Region** nearest to you and your visitors.
Then submit the form and this might take up to 12-15 minutes to make the server live and ready to install a lightning-fast WordPress Site.
## **How To Create A Site With xCloud** [#](/docs/first-server-with-google-cloud-platform/)
After you have completed the previous steps, you are now ready to create your site. Simply follow our step-by-step guide below.
### **Step 1: Create A Site From The Dashboard** [#](/docs/first-server-with-google-cloud-platform/)
Once your server is connected, you can create a site from the Dashboard or Site List by clicking on the button “**Create New Site**”
Then you will need to select the server on which you want to install your WordPress website.
### **Step 2: Choose Your Site & Add Information** [#](/docs/first-server-with-google-cloud-platform/)
As we will be creating a fresh WordPress site choose the “I**nstall New WordPress Website**” options as shown below.
Now all you have to do is install and Go Live with your WordPress Site. You can do the next process with 3 simple and easy steps.
1. Add a **Site Title**
2. Add **Tags** if you want
3. Choose to **Go Live**
4. Add your own **Domain**. Make sure to add the A record as shown above in your DNS panel.
To use a **Free SSL certificate** by **Let’s Encrypt** simply turn on the HTTPS enable button and xCloud will automatically set everything for you.
You can then simply hit the Next Button to create your site and **Go Live** instantly.
### **Step 3: Go For The Staging Environment** [#](/docs/first-server-with-google-cloud-platform/)
Also, If you do not want to point your domain yet then xCloud offers temporary domains to make your site live with every Site creation method available in xCloud. For that select the **Staging Environment** option.
### **Step 4: Configure Advanced Settings** [#](/docs/first-server-with-google-cloud-platform/)
By default, the WordPress admin credentials are autogenerated to speed up the site creation process. As soon as your site is deployed you will receive your Site credentials on your email address. Later on, you can update your password if needed. From “**More Advanced Settings**” you can update the default **Admin Username**, **Admin Password, Admin Email Address,** etc along with other additional settings from here.
### **Step 5: Review Your WordPress Settings** [#](/docs/first-server-with-google-cloud-platform/)
After all the information, you can review your settings. Here you will get an overall report of your **Domain Name**, **HTTPS Settings**, **WordPress Version**, **PHP Version,** and much more.
After the previous step, click on the ‘**Next**’ button. It might take only 1-2 minutes to create your WordPress site. You are done with your creation of the first server with Google Cloud Platform.
That’s it! You’ve successfully setup the first server with Google Cloud Platform in xCloud. Now you can start working on your website, customize it, install themes/plugins (if applicable), and take advantage of xCloud’s optimized server environment for seamless site management.
_Don’t have_ **_xCloud Pro_** _access? You can integrate any server provider in xCloud to provision a server and install a site in it. Check out this documentation to find out how to provision a server with DO_
[**How To Set Up Server With Other Providers?**](https://docs.google.com/document/d/17_kNb_y9Qq3rSoYmMIKdtDhqIQzBI_pvQreVGR13TQs/edit#heading=h.u3e1dvqbe2h5)
Still stuck? Contact our **support team** for any of your queries.
---
# How to Fix 503 Bad Gateway Errors for n8n Application - xCloud
> Learn how to troubleshoot and fix 503 bad gateway errors for your n8n application with step by step process.
A 503 Bad Gateway error occurs when a server (typically a reverse proxy like NGINX) tries to forward a request to your app server and receives an invalid or no response. When hosting n8n and facing a 503 Bad Gateway error.
Follow the steps below to fix 503 Bad Gateway errors for your [n8n application](/n8n-hosting/) easily:
### **Step 1: Check Node.js Version Verification** [#](/docs/fix-503-bad-gateway-errors-for-n8n-application/)
Apps like n8n require Node.js version 20 or later. To check your current version, go to your n8n site dashboard and check for the current version that your site is using.
### **Step 2: Upgrade the Node.js Version** [#](/docs/fix-503-bad-gateway-errors-for-n8n-application/)
Now click on the **Node version to go to** that will take you to the ‘Node Configuration’ dashboard of your server. Now choose your preferred version and click on the ‘Save’ button.
### **Step 3: Check PM2 Logs from the Monitoring Log** [#](/docs/fix-503-bad-gateway-errors-for-n8n-application/)
Navigate to the ‘Monitoring’ section of your n8n site dashboard. Look for the PM2 log associated with your application. This log provides valuable information about any crashes, errors, or service restarts that may be causing the 503 error. Review the log entries to identify and address any issues in your application’s runtime behavior.
###  [#](/docs/fix-503-bad-gateway-errors-for-n8n-application/)
### **Step 4: Reset the Permissions** [#](/docs/fix-503-bad-gateway-errors-for-n8n-application/)
Now, to reset the file and folder permissions, go back to your n8n site dashboard and head over to the **‘settings’** option from the left navigation bar. Then enable all the options and click on the **‘Run Now ’** button to reset the commands. It will check all directory and file permissions and ensure they are in the right place.
And that’s it. This is how easily you can fix the 503 bad gateway error for your n8n application in just a few clicks.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Fix Plugin or Theme Upload/Update 500 Errors on OpenLiteSpeed Servers With xCloud - xCloud
> When a WordPress site on an OpenLiteSpeed (OLS) server fails while uploading or updating a plugin/theme, the issue may be related to incorrect ownership of
When a WordPress site on an OpenLiteSpeed (OLS) server fails while uploading or updating a plugin/theme, the issue may be related to incorrect ownership of OpenLiteSpeed temporary files.
This guide explains how to identify the issue and apply the known fix.
### **Symptoms** [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
A customer may report one or more of the following:
- Plugin upload fails
- Plugin update fails
- Theme upload fails
- Theme update fails
- WordPress shows a 500 Internal Server Error
- The issue happens during upload/update actions only
- The site is hosted on an OpenLiteSpeed / OLS stack server
### Example customer message: [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
I cannot update the theme. It is showing a 500 error on your server
### Affected Stack [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
This issue is related to servers using the OpenLiteSpeed (OLS) stack.
It does not usually happen on NGINX stack servers.
In customer-friendly language:
Your server is using the OpenLiteSpeed stack. This issue is related to OpenLiteSpeed temporary file handling and is not related to Redis or cache settings.
### Error to Look For [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
Open the server logs in xCloud:
### Server → Logs [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
Or use the direct server logs URL:
https://app.xcloud.host/server/{server\_id}/logs
Look for this error:
> Failed to obtain or reinitialize VMemBuf.
### Example: [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
> 2026-05-13 06:27:02.750619 \[ERROR\] \[269567\] \[192.128.217.123:13925:H2-1\]
>
> Failed to obtain or reinitialize VMemBuf.
If this error appears while the customer is uploading or updating a plugin/theme, apply the fix below.
### Likely Cause [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
OpenLiteSpeed uses temporary swap/report files under:
> /tmp/lshttpd/
In some cases, these files or folders may have incorrect ownership. When OpenLiteSpeed cannot write to or reinitialize these temporary buffers properly, WordPress actions such as plugin/theme upload or update can fail with a 500 error.
The fix is to restore ownership to the correct server user:
> xcloud:xcloud
### **Fix** [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
SSH into the server or use the xCloud **Command Runner**.
### Run: [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
📄
filename.js
chown -R xcloud:xcloud /tmp/lshttpd/swap
chown -R xcloud:xcloud /tmp/lshttpd/.rtreport\*
### Using xCloud Command Runner [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
If you are using the xCloud dashboard:
1\. Open the xCloud dashboard.
2\. Go to Servers.
3\. Select the affected server.
4\. Open Command Runner.
5\. Run the following commands:
chown -R xcloud:xcloud /tmp/lshttpd/swap
chown -R xcloud:xcloud /tmp/lshttpd/.rtreport\*
6\. Wait for the command to finish.
7\. Ask the customer to test the plugin/theme upload or update again.
### Verification [#](/docs/fix-plugin-or-theme-upload-update-500-errors-on-openlitespeed-servers-with-xcloud/)
After applying the fix, ask the customer to retry the same action:
– Upload the plugin again
If successful, the issue is resolved.
Also, check the server logs again and confirm that the same error is no longer appearing during the upload/update attempt:
> Failed to obtain or reinitialize VMemBuf.
---
# Why my fresh xCloud server is showing 7.5GB used? - xCloud
> The operating system and essential stacks consume approximately 7.5GB for fresh xCloud server primarily. You can manage it by your own later on.
It’s normal for a fresh xCloud server to show approximately 7.5GB of disk usage. This usage primarily accounts for the operating system and essential stacks required for server functionality.
The essential stacks and software packages typically include:
- Nginx (with HTTP/2 enabled) 1.24
- PHP-FPM 8.2
- MySQL 8.0
- Redis 7.2
- Git
- Composer
- WP-CLI
- Certbot (for Let’s Encrypt TLS/SSL certificates)
- UFW (firewall)
- Fail2ban
While the initial disk usage is essential for server functionality, you can manage and optimize the disk space based on your specific needs. Consider removing unnecessary packages or optimizing configurations to free up disk space if required. However, ensure that essential components remain intact for proper server operation.
---
# How To Perform Full Server Migration Between xCloud Servers Effortlessly? - xCloud
> Learn how to perform full server migration between xCloud servers by following this step-by-step guide.
With [**xCloud**](/), you can effortlessly migrate all your websites from one xCloud server to another without any hassle. This includes moving multiple WordPress sites in bulk on the same xCloud server. It’s a speedy process that won’t harm your original servers or sites, unlike basic plugin migrations. Let’s see the step-by-step process below to learn how to do the full server migration between xCloud servers easily.
## **Prerequisite To Perform A Full Server Migration Between xCloud Servers:** [#](/docs/full-server-migration-between-xcloud-servers/)
- Add a Sudo User to your source server.
- Disable Wordfence or any other security plugins.
To learn how to add Sudo User in your source server, the below doc is for your help.
- [**Add Sudo User**](/docs/usudo-users-and-site-users-in-xcloud/)
### **Step 1: Pick Your Source and Destination Server** [#](/docs/full-server-migration-between-xcloud-servers/)
Before jumping into the process of how to achieve it successfully, choose your **Source Server** (from where you’re migrating) & **Destination Serve**r (where you want to migrate). To do so, go to your xCloud dashboard & locate ‘**All Servers**.’
For this guide, we’ve picked Vultr Server as the Source Server & xCloud Provider as the Destination Server.
### **Step 2: Enter Into Your Destination Server** [#](/docs/full-server-migration-between-xcloud-servers/)
After choosing the destination server ‘**xCloud Provider**,’ click on it & hover over to the top right, and click on ‘**New Site.**’
### **Step 3: Migrate Your Site To Your Destination Server** [#](/docs/full-server-migration-between-xcloud-servers/)
On the resulting page, click on **‘Migrate Full Server Option’** to proceed with the whole migration with the process.
### **Step 4: Connect Your Source Server with All the Information** [#](/docs/full-server-migration-between-xcloud-servers/)
On this page, select your hosting provider as **‘Others**,’ put the source server’s ‘**IP Address**,’ & click on **‘Next**.’
But if your server relies on public key authentication, you will need to add the xCloud’s provided public key by accessing your server via root user using the terminal. This process ensures that only authorized individuals with the corresponding private key can gain access to the server and this is more secured than the Password approach.
Therefore, to add the public key to your source server you need to follow these steps:
- Copy the public key from xCloud’s FSM dashboard.
- Access your source server as a root user via SSH.
- Paste the public key.
After adding the Public key in your source server switch back to xCloud and click next.
### **Step 5: Select The Site/Sites You Want To Migrate** [#](/docs/full-server-migration-between-xcloud-servers/)
After you have connected your public key, you will get access to your sites for migration. Select which server to migrate, click **‘Next’**, and push your site to the live site.
### **Step 6: Go Live Or Create Staging Sites** [#](/docs/full-server-migration-between-xcloud-servers/)
In this step, you can either choose a staging site or you can opt for going live. Simply, toggle on your favorable option.
_**Note:** Please make sure to check out the storage of your destination server. We recommend keeping your destination server with at least 1 GB free always._
Now your full server migration will start shortly.
**_Note:_** If you’ve selected the GO LIVE option, you need to point your domain to the new server. If you’re not clear, dive into the below documentation for more details.
- [How To Setup DNS Record In xCloud Server?](/docs/how-to-setup-dns-record-in-xcloud-server/)
- [With xCloud, Integrate Cloudflare For DNS Management](/docs/using-xcloud-with-cloudflare-for-dns-management/)
Our development team will help you to perform full server migration. Please contact our [**support team**](/support/) for any assistance.
---
# How to Access Global Backup Settings with xCloud - xCloud
> Follow the steps to access your global backup settings, configurations, and manage backups efficiently through the xCloud dashboard.
Managing reliable backups is essential for ensuring the safety and continuity of your websites. The xCloud platform provides a centralized system that makes it easy to configure, monitor, and maintain both remote and local backups across all your sites.
Follow the steps to access your global backup settings, configurations, and manage backups efficiently through the xCloud dashboard.
## **Step 1: Go to Global Settings Option** [#](/docs/global-backup-settings-with-xcloud/)
First, from your xCloud dashboard, go to your ‘Team Settings’ from the top menu. Then head over to your ‘Global Settings’ → ‘Site Backup’ option from the menu.
## **Step 2: Get Backup Overview** [#](/docs/global-backup-settings-with-xcloud/)
Here you will get an overview of your site backups like ‘Total Sites’, ‘Sites With Backup Configured’, ‘Sites Without Backup’.
## **Step 3: Check Backup Settings** [#](/docs/global-backup-settings-with-xcloud/)
Here, you will get your both ‘Remote Backup’ and ‘Local Backup settings’ . Just go to the ‘Remote Backup’ tab to access adjust the settings as your preferences ‘Backup Type’ , ‘Bucket’, ‘Automatic Backup’, ‘Automatic Delete’, ‘Database Backup’, ‘File Backup .
Next, you can go to your ‘Local Backup’ tab. Just go to the ‘Remote Backup’ tab to adjust the settings according to your preferences: ‘Backup Type’, ‘Bucket’, ‘Automatic Backup’, ‘Automatic Delete’, ‘Database Backup’, ‘File Backup’.
## **Step 4: Backup Overview Settings** [#](/docs/global-backup-settings-with-xcloud/)
Next, go to the ‘Backup Overview’ section, and head over to the ‘All Sites’ ‘Remote Backup’, ‘Local Backup’, ‘No Backup’ options. Here you can manage all your site backups in bulk easily.
---
# How to Configure Global Settings for File Manager and Adminer in xCloud - xCloud
> Learn how to customize global settings for File Manager and Adminer in xCloud and manage features for seamless performance.
Managing global settings for your features ensures that your xCloud account operates according to your preferences. Whether you want to customize accessibility options for the File Manager or adjust Adminer settings, xCloud provides an easy way to make these changes.
Follow the step-by-step process below to access and configure your feature settings efficiently.
## **Step 1: Go to Your Profile Settings** [#](/docs/global-settings-for-file-manager-and-adminer/)
To begin, log in to your [**xCloud account**](https://app.xcloud.host/dashboard) and navigate to the top-right corner of your dashboard. Click on the **‘Profile Settings’** option to access your account settings.
## **Step 2: Access Features Customization Option** [#](/docs/global-settings-for-file-manager-and-adminer/)
From there, go to the left navigation menu and select **‘Team’** → **‘Customization’**, to access the global settings for your File Manager and Adminer customizations.
## **Step 3: Customize File Manager Settings** [#](/docs/global-settings-for-file-manager-and-adminer/)
If you wish to customize the File Manager settings, locate the **‘Access File Manager’** option from the dashboard to adjust settings as you prefer. To keep the File Manager always accessible, select the **‘Always Enabled’** option.
Alternatively, if you prefer to disable the File Manager after a specific duration, choose the **‘Disable File Manager’** option. A dropdown menu will appear, allowing you to select the duration after which the File Manager will be disabled. Once you’ve made your selection, click **‘Save’** to apply the changes.
## **Step 4: Customize File Manager Settings** [#](/docs/global-settings-for-file-manager-and-adminer/)
For customizing Adminer settings, locate the **‘Access Adminer’** option from the dashboard. To keep Adminer always accessible, select the **‘Always Enabled’** option.
If you want to disable Adminer after a specific duration, choose the **‘Disable Adminer’** option. A dropdown menu will appear, enabling you to select the duration after which Adminer will be disabled. After selecting your preferred duration, click **‘Save’** to confirm your settings.
And that’s it. This is how easily you can configure the global settings for your File Manager and Adminer in xCloud.
Still stuck or have any questions? Contact our [**support team**](/support/) for any of your queries.
---
# How to Integrate Google Drive for Site Backup in xCloud? - xCloud
> Simplify your data protection by using Google Drive for Site Backup with xCloud. Set up auto-backups and secure your website effortlessly.
Ensuring the safety and reliability of your website data is crucial, and integrating **Google Drive for site backup** is a smart way to achieve it. [**Google Drive**](https://workspace.google.com/products/drive/) is a trusted cloud storage platform, offering a user-friendly interface, robust security and scalable storage solutions. These features make it an ideal choice for protecting your site backups and ensuring easy accessibility whenever needed.
In this guide, we will show you how to seamlessly integrate **Google Drive for site backup** with [**xCloud**](/), enabling a smooth and efficient backup process. Ready to secure your data with Google Drive? Let us dive into the step-by-step instructions!
## **Steps to Integrate Google Drive for Site Backups with xCloud & Back up Site** [#](/docs/google-drive-for-site-backup-xcloud/)
Follow the steps below to integrate Google Drive for site backups with xCloud and back up your websites effortlessly.
### **Step 1: Integrate Google Drive to Your Account** [#](/docs/google-drive-for-site-backup-xcloud/)
Before getting started to back up your websites with Google Drive, you need to integrate the storage provider into xCloud. For that, [**log in to your xCloud account**](https://app.xcloud.host/) and navigate to **My Profile → Integrations → Storage Provider.**
Now, click the **‘Add New Provider’** button and choose Google Drive as your provider. Next, set a label/name for which a folder will be created in your Google Drive.
You will be taken to the **‘Sign in with Google’** page where Google will ask you to choose an account for accessing with xCloud Hosting. Choose an account or create a new one and continue.
Once integrated, you will see the Google Account **integrated and listed** on the Storage Provider page in xCloud, as shown below.
### **Step 2: Configure Backup Settings for Google Drive** [#](/docs/google-drive-for-site-backup-xcloud/)
Once you are done integrating Google Drive as a storage provider into xCloud, you can now configure ‘**Backup Settings**’ for taking backups with Google Drive. Now, go to sites, choose the one you want to take backup and navigate to the **Site Backup → Backup Settings.**
Now, in the **‘Remote Backup’** section, choose Backup Type as **‘Full’** and select the bucket you have just created for Google Drive. You can then choose to exclude paths if necessary (for the paths you do not want to take backup).
Then, you can also enable **‘Automatic Backup’** and choose the backup frequency. Plus, you have the option to use the **‘Automatic Delete’** option with which you can set days after when your backup will be deleted automatically**.** Once done, hit the **‘Save’** button.
\[**Note:** Google Drive currently does not support Incremental backup option. Also, since this is a remote backup provider, you only need to choose the remote backup option with Google Drive.\]
### **Step 3: Take a Backup of Your Site** [#](/docs/google-drive-for-site-backup-xcloud/)
Once you are done configuring the site backups, you can now take backups of your websites using this provider. Now, go to the **Previous Backups** of your site settings and you will see all the available remote backups and local backups.
You can take a backup of your site from here by simply clicking on the **‘Backup Now’** button. Your backup process will be initiated and the backup files will be shown here once done.
You can also check your [**Google Drive**](https://drive.google.com/drive/my-drive). A folder will be created with the name of your backup label and your backups will be saved inside the folder there.
This is how easily you can integrate Google Drive for Site Backup with xCloud and take backups of your websites.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# Complete Guide to WordPress Site Migration on xCloud - xCloud
> Learn how xCloud's free WordPress migration works - from submitting your site details and queue-based scheduling to testing on a demo domain and going live with DNS and SSL.
Migrating your WordPress site to a new hosting platform can feel daunting, but xCloud’s managed migration service is designed to make the entire process seamless and stress-free. This comprehensive guide walks you through every stage of xCloud’s free WordPress migration from submitting your site details and understanding the queue-based scheduling system, to testing your migrated site on a temporary domain and finally taking it live with updated DNS and SSL.
Whether you’re moving a single site or coordinating a batch of migrations, this document provides the clarity and detail you need to ensure a smooth transition with zero downtime.
**⚠️ Important:** Please read this entire guide carefully before submitting a migration request. Having a clear understanding of each step will help you prepare properly and avoid unnecessary delays.
## **Supported Migrations** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
xCloud’s free migration service is exclusively available for WordPress-powered websites. If your site runs on a different CMS or platform, this migration pathway will not apply.
All migration requests are handled through a queue-based system. Rather than processing all requests simultaneously, xCloud completes migrations in small daily batches. This deliberate approach serves two important purposes: it gives you adequate time to thoroughly test each migrated site before making it live, and it minimizes the risk of errors or service disruptions — particularly when you’re migrating multiple sites at once.
## **Step 1: Submit Your Migration Details** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
The migration process begins once xCloud receives your request. You’ll be provided with a shared Google Sheet where you can enter all the necessary details for each site you want to migrate. Completing this form accurately and thoroughly is the single most important thing you can do to prevent delays.
### **Information Required for Each Site** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
For every WordPress site included in your migration request, please provide the following details:
1. Full WordPress admin login URL (e.g., yourdomain.com/wp-admin)
2. WordPress admin username with full administrative privileges
3. The email address associated with the admin account
4. The admin account password (shared securely via the Google Sheet)
5. The destination server IP address where the site should be migrated
6. The PHP version your site requires (e.g., PHP 8.1, 8.2)
7. Any additional notes, special configurations, or custom requirements
**💡 Tip:** Double-check all credentials before submitting. Incorrect login details are the most common cause of migration delays.
### **How to Share Admin Access Securely** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
If you’re uncomfortable sharing your primary WordPress admin credentials, xCloud recommends creating a temporary admin user specifically for the migration. This approach keeps your main account secure while still giving the migration team the access they need.
To set this up:
1. Log in to your WordPress dashboard and navigate to **Users → Add New**
2. Create a new user with the **Administrator** role
3. Use **support@xcloud.host** as the email address for this temporary account
4. After the migration is fully complete and verified, delete this temporary user
## **Step 2: Migration Queue & Scheduling** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
Once your site details have been submitted, your migration request is added to xCloud’s processing queue. Migrations are completed in controlled daily batches rather than all at once.
This structured scheduling ensures:
- No unnecessary downtime for your live site during the migration window
- Sufficient time to test and verify each migrated site before proceeding to the next
- A smoother, more predictable experience — especially valuable when migrating multiple sites in succession
You can monitor the real-time status of your migration directly within the same Google Sheet where you submitted your site details. Each entry will be updated as it moves through the queue.
## **Step 3: Migration in Progress** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
When your site reaches the front of the queue and migration begins, the process is handled entirely by xCloud’s team. Here’s what you should know about what happens during this stage.
### **What Happens During Migration** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
- **Zero downtime:** Your live site continues to operate normally throughout the entire migration. Visitors will not experience any interruptions.
- **Temporary demo domain:** Your site is migrated to a temporary demo domain provided by xCloud, not directly to your live domain. This allows thorough testing before any DNS changes are made.
- **Live domain stays untouched:** Your original domain and hosting remain completely unaffected until you explicitly decide to switch over.
### **What to Avoid While Migration Is Underway** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
To ensure the migration produces an accurate copy of your site, please observe the following during this stage:
- **Do not make any content changes,** plugin updates, or configuration adjustments on the source site. Changes made during migration may not be captured in the migrated copy.
- **Expect temporary plugin deactivation:** xCloud may temporarily disable certain security plugins (such as Wordfence or Sucuri) and caching plugins (such as WP Super Cache or W3 Total Cache) on the source site to facilitate a clean migration. These will be re-enabled once migration is complete.
## **Step 4: Migration Complete — Review & Testing** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
Once the migration is finished, xCloud will notify you and provide access to the migrated site on the temporary demo domain. This is your opportunity to conduct a thorough review before anything goes live.
### **Your Post-Migration Testing Checklist** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
Take your time with this review. Carefully check the following areas:
- Browse all pages, posts, and custom content types to verify that everything displays correctly
- Test all forms (contact forms, signup forms, checkout flows) to confirm they function properly
- Log in to the WordPress admin dashboard and review your settings, menus, and widget configurations
- Reactivate any premium or licensed plugins that were deactivated during migration, and verify their license keys are active
- Check media files (images, videos, PDFs) to ensure they loaded correctly and are not broken
### **⚠️ Critical Reminder:** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
- **Do NOT delete your source site immediately after migration.** Keep it fully intact for at least two weeks as a safety net.
- Make sure you have verified backups of the original site before removing it from your previous host.
- If you discover any issues during testing, contact xCloud support immediately so the team can investigate and resolve them quickly.
## **Step 5: Going Live on xCloud** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
After you’ve completed your testing and confirmed that everything on the migrated site is functioning correctly, xCloud will assist you with the final steps to make your site live on its new home.
### **The Go-Live Process Includes** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
1. **DNS update:** Updating your domain’s DNS records to point to the new xCloud server. This redirects all traffic to the migrated site.
2. **SSL installation and verification:** Ensuring your site is served over a secure HTTPS connection with a valid SSL certificate.
3. **Basic performance checks:** Running initial diagnostics to confirm the site loads efficiently on the new server.
4. **Backup activation:** Setting up automated backups on xCloud to protect your site going forward.
Once DNS propagation is complete and SSL is active, your site will be fully live and operational on xCloud.
## **Alternative Migration Methods** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
In some situations, the standard migration approach may not work as expected — for example, if your current host has non-standard configurations, restricted access, or particularly large databases.
When this occurs, xCloud may need to use an alternative migration method. This typically involves creating a full backup archive directly on your source server and transferring it to xCloud. Before proceeding with this approach:
- xCloud will explain why the standard method was not viable and request your explicit permission before using the alternative approach.
- You’ll need to confirm that your source server has sufficient disk space available to generate the backup archive (typically 2–3x the size of your site).
- xCloud will keep you informed at every stage of the alternative process, so you’re never left guessing.
## **When Migration Cannot Be Completed** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
In rare cases, a migration may not succeed despite the team’s best efforts. If this happens, xCloud will:
1. Provide a clear, detailed explanation of why the migration failed and what technical obstacles were encountered.
2. Present all available alternative options, including manual migration approaches or third-party tools that may help.
3. Outline any additional access, credentials, or server-side changes that might be required to attempt the migration again.
xCloud’s support team will work closely with you to determine the best path forward and won’t leave you without a resolution.
## **Best Practices for a Smooth Migration** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
Following these recommendations will significantly reduce the likelihood of complications and help ensure your migration goes as smoothly as possible.
**Best Practice**
**Why It Matters**
**Take a full backup before migration**
Provides a reliable fallback if anything unexpected happens during the transfer process
**Freeze all site changes during migration**
Ensures the migrated copy is an exact replica of your current site, with no missing updates
**Verify all credentials before submitting**
Incorrect or expired login details are the leading cause of migration delays
**Keep the source site for at least 14 days**
Acts as a safety net in case any issues are discovered after going live on xCloud
**Test thoroughly on the demo domain**
Catches problems early, before they affect your live visitors and search rankings
**Communicate special requirements upfront**
Helps xCloud’s team prepare for custom configurations, large databases, or unusual setups
### **Need Help? We’re Here for You.** [#](/docs/guide-to-wordpress-site-migration-on-xcloud/)
If you have any questions after reading this guide, or if something isn’t clear, don’t hesitate to reach out. Contact **our [support team](https://support.xcloud.host/), we’re here to help.**
---
# Can I host Multiple Websites on One xCloud Account? - xCloud
> You can host multiple websites on single xCloud account.
YES, xCloud’s hosting plans let you manage multiple websites under one account. So, whether you’re running blogs, business sites, or eCommerce stores, you can do it all without additional cost.
To get more ideas about xCloud and its plans with unlimited websites, contact our dedicated **[support team](https://support.xcloud.host/)**.
---
# How to Host PewDiePie’s Odysseus AI on a VPS With xCloud
> Learn how to host PewDiePie’s Odysseus AI on a VPS with xCloud using Docker, Custom Docker from Git, port 7000, domain, SSL, and safe setup steps.
**[Odysseus AI](/odysseus-hosting/)** is PewDiePie’s open-source, self-hosted AI workspace for chat, agents, local models, tools, memory, documents, email, calendar, and research workflows. If you want to run PewDiePie’s Odysseus on your own VPS instead of only using a hosted AI app, xCloud can help you deploy it with Docker, map it to a domain, and serve it over HTTPS.
This guide shows how to host **PewDiePie’s Odysseus AI on a VPS with xCloud** using the **Docker + NGINX** server type, **Custom Docker**, and the **[official public GitHub repository](https://github.com/pewdiepie-archdaemon/odysseus.git)**.
> This is an xCloud deployment guide for Odysseus. Odysseus itself is maintained by the PewDiePie Archdaemon project, so check the official repository for the latest app-specific setup notes and environment variables.
## What is PewDiePie’s Odysseus AI? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Odysseus is a self-hosted AI workspace designed to feel closer to a ChatGPT or Claude-style interface, but with more control over where the app runs, where data is stored, and which models or API providers you connect. The official project describes it as a local-first and privacy-first workspace for talking to language models and running agent workflows.
- **Chat and agents:** run multi-turn conversations and agent workflows with tools.
- **Model connections:** connect local or remote model runtimes such as Ollama, vLLM, llama.cpp, OpenAI, OpenRouter, or other supported endpoints.
- **Research and tools:** use web, files, memory, MCP tools, and deep research-style workflows where supported by the app.
- **Persistent workspace:** keep app data, logs, model cache, and configuration on your own server instead of depending only on a third-party hosted UI.
If you are new to Odysseus, start by understanding the app first, then move into the hosting steps. This guide focuses on the practical deployment path: how to get Odysseus AI running on a VPS with Docker and a secure URL.
## **Why host Odysseus AI on a VPS?** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Odysseus is built for people who want more control over their AI workspace. Instead of relying only on a hosted SaaS interface, you can run the app on your own VPS, keep persistent data on your server, connect your preferred AI providers, and expose the dashboard through your own domain with HTTPS.
- You can use API providers such as OpenAI, OpenRouter, or other compatible services where supported by Odysseus.
- You can connect local or remote model runtimes such as Ollama, vLLM, or llama.cpp when your server resources are suitable.
- You can keep Odysseus data, logs, SSH keys, and model cache mounted as persistent Docker volumes.
- You can manage the public domain and SSL through xCloud while the app runs inside Docker containers.
## What this guide covers [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
If you want to try PewDiePie’s Odysseus AI platform on your own VPS, this guide walks you through the full xCloud deployment flow: creating a Docker + NGINX server, deploying the public GitHub repository with Custom Docker, mapping the Odysseus port, connecting a domain, and serving the app through a secure HTTPS URL.
## Prerequisites [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
- An xCloud account with access to create or connect a server.
- A VPS that can run Docker workloads. For local model serving, choose a plan with enough CPU, RAM, disk, and GPU/VRAM if needed. Smaller servers can still run the web UI and connect to external API providers.
- A domain or subdomain you can point to xCloud.
- The public [**Odysseus Git repository URL**](https://github.com/pewdiepie-archdaemon/odysseus.git).
- Basic knowledge of environment variables for API keys and model endpoints.
## Step 1: Create a Docker+ NGINX Server [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Before you can deploy Odysseus, you need a server to host it. First, you need to create a Docker server to deploy Custom Docker. Click the **‘Add New Server’** button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Custom Docker either on your [**own server**](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy Custom Docker with xCloud. You can either use an [xCloud Managed Server](/managed-hosting/) or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the ‘Server Name’, set the ‘App Type’ to Custom Docker(it is optional to select), and add any relevant ‘Tags’ to help identify your server later.
Next, you can see the ‘Docker + NGINX’ stack is already selected, which is mandatory for deploying the Custom Docker application. Then click on the ‘Pay & Deploy’ button to proceed.
📌 For more details about the supported stack, see **[Web Servers Compatibility For Different Applications](/docs/web-server-compatibility-for-different-applications/).**
Next, choose your server size according to your preferences. xCloud offers an exclusive discount for the first month. Moreover, you can save up to more discounts if you proceed to an annual or 24-month plan.
Once the server is created, you will be able to deploy your Custom Docker Application on this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## **Step 2: Start a Custom Docker site** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the ‘New Site’ button.
## **Step 3: Choose Your Server** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Custom Docker applications.
## **Step 4: Go to The Custom Docker Tab** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
From here, go to the **‘Custom Docker’** tab and click on the **‘Docker Compose’** to deploy your Custom Docker applications.
## **Step 5: Set Up the Docker Compose Application** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment
## **Step 6: Set Up Domains** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain. Just proceed with the **‘Go Live’** option.
For the **‘Demo Site’,** you will get a free demo domain for xCloud. Under the **‘Domain Setup’** section, choose your preferred domain. Then you will get a **‘Site User’** of xCloud and click on the **‘Next’** button to proceed.
## **Step 7: Use the HTTPS GitHub repository URL** [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Next, choose the ‘Public Repository (HTTPS)’ option from the dropdown and enter the **[Git repository URL](https://github.com/pewdiepie-archdaemon/odysseus.git)**. Then select the default branch, usually ‘main’. Next, set the Docker Compose file name to docker-compose.yml unless the repository changes its file structure later. Afterwards, continue to the next step.
The repository already includes a Dockerfile and Docker Compose configuration. Odysseus exposes the web app on container port 7000.
## Step 8: Detect and map the Odysseus port [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
After xCloud reads the Docker Compose file, use port detection to map the app to NGINX. Odysseus uses port `7000` inside the container.
1. Go to **Port Detection**.
2. Click **Auto-Detect Ports**.
3. Choose `7000` as the primary service port if xCloud detects multiple services.
4. Map the selected port to your Odysseus domain or subdomain.
5. Continue the deployment.
The Odysseus Compose file also includes supporting services such as ChromaDB and SearXNG. Those services should normally remain internal unless you intentionally map them for a specific reason.
## Step 9: Add environment variables [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Odysseus can start with defaults, but a VPS deployment should define the important deployment-level settings clearly. In xCloud, enable the **Environment File** option when you need to add environment variables for the Docker Compose services.
Useful variables may include:
```
APP_BIND=0.0.0.0
APP_PORT=7000
AUTH_ENABLED=true
ODYSSEUS_ADMIN_USER=admin
ODYSSEUS_ADMIN_PASSWORD=use-a-strong-password
ALLOWED_ORIGINS=https://odysseus.example.com
SECURE_COOKIES=true
OPENAI_API_KEY=your-openai-api-key
OPENROUTER_API_KEY=your-openrouter-api-key
OLLAMA_BASE_URL=http://host.docker.internal:11434
```
Copy to Clipboard
Replace `https://odysseus.example.com` with your real HTTPS URL. Keep API keys private and do not paste production secrets into screenshots, public issues, or shared chat messages.
## Step 10: Deploy Odysseus [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
1. Review the repository URL, branch, Compose file name, domain, port, and environment variables.
2. Click the deployment button in xCloud.
3. Wait for xCloud to clone the repository, build the Docker image, start the containers, and configure NGINX routing.
4. Open the site from the xCloud dashboard when deployment finishes.
On first setup, Odysseus creates an admin account and prints a temporary password in the container logs if you did not pre-seed an admin password. For Docker installs, check the Odysseus container logs from the xCloud site logs or server terminal if needed.
## Step 11: Log in and complete Odysseus setup [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Open your HTTPS Odysseus URL in a browser and log in with the admin username and password. If a temporary password was generated, change it from the Odysseus settings, then add your AI provider keys or local model endpoints there as well. Before enabling heavier agent or research workflows, test a simple chat request to confirm everything is connected.
## Recommended VPS size [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
The Odysseus web app itself is lightweight, but model serving can be heavy. If you plan to connect only to external API providers, a smaller Docker VPS may be enough. If you want to run local models, choose resources based on the model size, runtime, and GPU/VRAM requirements.
- **API-only use:** start with a moderate CPU/RAM plan and scale after testing.
- **Local small models:** use more RAM and disk for model cache and embeddings.
- **GPU model serving:** choose a GPU-capable environment and confirm the runtime requirements before production use.
- **Deep research or agent workflows:** allow extra CPU, memory, and disk because background tasks can run longer.
## Mobile access for Odysseus AI [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Many people want to use Odysseus from a phone or another device. Hosting Odysseus on a VPS with a domain makes that easier: once the app is deployed and SSL is active, you can open the same HTTPS URL from desktop or mobile.
- Use HTTPS before logging in from mobile browsers.
- Set allowed origins and cookie settings to match your real domain.
- Avoid exposing internal service ports directly to the public internet.
- Use a strong admin password and rotate credentials if you shared temporary setup details anywhere.
## Troubleshooting Odysseus AI deployment [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
### The site does not load after deployment [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
- Confirm the Docker containers are running.
- Confirm the primary service port is `7000`.
- Check whether DNS points to the correct xCloud server.
- Enable or retry SSL after DNS verification passes.
- Review container logs for Python, dependency, or startup errors.
### Login does not work or cookies fail [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
- Use the HTTPS version of the site URL.
- Set `ALLOWED_ORIGINS` to your real HTTPS URL.
- Set `SECURE_COOKIES=true` for production HTTPS usage.
- Clear old browser cookies after changing domain or cookie settings.
### AI providers or local models do not respond [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
- Check that the API key is correct and active.
- Confirm the model provider endpoint is reachable from the container.
- For host-based Ollama, use `host.docker.internal` if supported by your Docker network setup.
- Check Odysseus logs for provider-specific errors.
## FAQ about hosting Odysseus AI on xCloud [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
### Is Odysseus AI made by PewDiePie? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Odysseus is published under the PewDiePie Archdaemon GitHub organization. This xCloud guide explains how to deploy that public project on a VPS with xCloud; it is not the official Odysseus documentation.
### Can I access Odysseus AI from my phone? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Yes. After you deploy Odysseus on a VPS, connect a domain, and enable SSL, you can open the same secure URL from a mobile browser. Keep authentication enabled and do not expose internal Docker services publicly.
### Can I host Odysseus AI with Custom Docker on xCloud? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Yes. Odysseus includes Docker and Docker Compose files, so you can deploy it through xCloud’s Docker + NGINX server type and Custom Docker workflow.
### Should I use the HTTPS Git URL or SSH Git URL? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
For the public **[Odysseus repository](https://github.com/pewdiepie-archdaemon/odysseus.git)**, use the HTTPS Git URL. SSH is mainly useful for private repositories.
### Does Odysseus need a GPU? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Not always. You can run the Odysseus web workspace on a normal VPS and connect to API providers. A GPU is only needed when you plan to serve local models that require GPU acceleration.
### Can I use my own domain with SSL? [#](/docs/host-odysseus-on-a-vps-with-xcloud/)
Yes. Use the domain step in xCloud, point the required DNS record, verify the domain, and enable SSL so Odysseus runs on a secure HTTPS URL.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How Billing Works in xCloud White Label Program or Reseller Hosting Program - xCloud
> Discover how xCloud White Label billing works so you get to learn how our billing works to maximize your revenue
xCloud White Label is a service provided by xCloud that allows you to launch your own hosting business under your brand. As a reseller, you have full control over pricing, branding, and client management. xCloud provides the infrastructure through its **xCloud Managed Server** or **Self Managed Provider/ Own Server Provider,** where you will create your products and resell to your clients. You focus on running your business while xCloud takes care of the technical management of our reseller platform.
Read the complete guide to know how the xCloud White Label/ Reseller Hosting panel’s billing works, including costs, payment processes, and your responsibilities as a reseller.
### **Pricing Breakdown** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
As a reseller using xCloud White Label, your revenue is determined by the pricing you set for your hosting services, minus the fees associated with the xCloud Managed Server or self-managed sever/own server provider and other fees. Here’s how the billing structure works:
1. **Reseller Panel Subscription Fees:** Resellers will be charged a monthly subscription fee, which provides you with the tools to manage your customers, automate billing, and handle your hosting packages. This panel is essential for maintaining the smooth operation of your hosting business.
2. **xCloud Managed Server Fees**: You are responsible for creating and managing the servers your clients use. Each server comes with a base fee charged by xCloud, depending on the resources (such as storage, bandwidth, and computing power) required to meet the needs of your clients.
3. **Self Managed Server Provider/ Own Server Provider:** For your own or self-managed server that you connect to resell with xCloud, you will be responsible for the payment and management of those servers.
4. **Your Custom Pricing**: As a reseller, you have complete freedom to set your own pricing for the hosting packages you offer to your clients. After covering the xCloud Managed Server and control panel fees, the remaining amount from the prices you set is your profit.
5. **Platform Fee:** If you integrate your own or self-managed server with the xCloud White Label or Reseller Hosting Panel, a platform fee will apply to each server sale.
6. **Stripe Fees**: For payment processing, Stripe may charge up to 10% transaction fees, which will be automatically deducted from each payment you receive.
> 📌 To use any Reseller Plan – either “xCloud Managed Server” or “Self Managed Provider Server” — you, as a reseller, must subscribe to a plan.
### **Example Billing Breakdown for Reseller Hosting with xCloud Managed Server** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
- **xCloud Managed Server Fee**: $24 per month.
- **Customer Payment (Your Product Price): $70**
- **Stripe Fee:** Up to 3% Stripe fees
- **Your Profit:** $43.50
### **Example Billing Breakdown for Reseller Hosting with Self Managed Provider:** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
- Reseller’s Customer Payment (Your Product Price): $30
- Server Provider Cost: $5
- Platform Fee (Advanced Plan / Startup example): Based on your reseller panel subscription plan. For example, if you choose the Startup plan, you will be charged 25% or a minimum of $3 per sale, whichever is higher.
- Stripe Fee: Up to 3% (approx.)
- Your Profit: $16.60
_**Payment Calculation:** $30 – $5 – $7.50 – $0.90 = 16.60_
### **Payment Processing with Stripe Connect** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
All payments for hosting services provided through your white-label business are processed via Stripe Connect, ensuring smooth and secure transactions for both you and your clients.
Here is how the payment process works:
1. Your customers make payments for their hosting packages via your branded platform.
2. Stripe Connect processes the payments.
3. You need to pay us the monthly White Label subscription fees.
4. When your client create any server based on your created ‘Products’ then Stripe will automatically deducts the xCloud Managed Server fees and the remaining amount, which is your profit, will be transferred to your Stripe account.
Stripe Connect simplifies the payment process and allows you to manage recurring payments and billing, leaving you more time to focus on growing your business.
### **Responsibility for Unpaid Fees** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
As a reseller, you are ultimately responsible for ensuring that your clients pay for their hosting services. If a customer fails to make their payment, you are still required to cover the associated xCloud Managed Server and subscription fees for our panel that client’s account.
#### **What Happens if Fees are Unpaid?** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
- If your customer does not pay their hosting fees, xCloud will notify you about the outstanding balance.
- You are responsible for covering the unpaid amount to maintain service for that customer.
- If the unpaid fees are not settled, **xCloud reserves the right to lock the services** for that particular account. This means your customer’s hosting service will be suspended until the payment is made, and you will be unable to provide further service to that customer.
This policy ensures that server resources are always paid for, and services remain uninterrupted for other clients. To avoid service disruption, it’s essential to manage your client billing effectively and ensure that all payments are made on time.
## **Refund Policy** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
### **Refund Policy for xCloud Managed Servers** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
xCloud White Label offers a very transparent refund policy which includes a 14-day refund policy which including the subscription fees and the unused amount of the xCloud Managed server fees will be refunded for the month if a server is removed.
xCloud uses **Stripe** as a third-party payment processor to handle all transactions. All transactions are subject to Stripe’s terms and conditions. If you decide to delete your xCloud Managed Server, the following refund policy will apply:
- You will be charged for the total usage of the server up to the point of deletion, along with a **Stripe fee of up to 3%** of the used amount.
- You will be billed for **a minimum of one day**, even if you delete the server within an hour or less of provisioning. The Stripe fee will still apply.
- The remaining unused amount, after deducting the server usage and Stripe fees, will be refunded to your account.
This ensures that you are only charged for what you use, but keep in mind the associated fees when managing your servers.
### **Refund Policy for Self Managed Servers** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
If you’re reselling hosting using your own server or a Self-Managed Server, xCloud offers a 14-day refund policy that includes the subscription fees for our Reseller Panel.
### **Refunds and Payment Obligations** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
Refunds for your customers are managed by you as the reseller since you set the prices and manage the customer relationship. xCloud does not offer refunds for the Managed Server or hosting control panel fees once they are charged. You will need to establish your own refund policies and communicate them clearly to your clients.
It is important to note that xCloud does not provide refunds for services that have been locked due to unpaid fees. Therefore, to prevent issues with non-payment, make sure that you are collecting payments from your customers on time and resolving any issues as quickly as possible.
### **Late Payments** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
The billing cycle for xCloud charges accounts on the **first day of each month**. If your account becomes overdue, xCloud may **temporarily suspend** your services until the balance is cleared. If you require additional time to settle your account, please reach out to our support team within the first week of the month to discuss possible arrangements.
We are committed to providing reliable cloud services, and our support team is here to help with any billing-related questions or issues.
### **Pricing Plans** [#](/docs/how-billing-works-in-xcloud-white-label-program/)
To explore our pricing options for creating and managing servers under xCloud White Label, please **check out this page** for the latest pricing details. This allows you to select the most suitable option for your business needs, maximizing your profitability while maintaining control over your hosting services.
xCloud White Label offers you the opportunity to build a fully branded hosting business with complete control over your services, pricing, and customer relationships. As a reseller, you are responsible for covering the costs of the xCloud Managed Server and xCloud White Label subscription fees, while keeping the profits from the custom pricing you set for your clients.
Still stuck? Contact our **[support team](http://hidden-hamlet-226309.wp1.sh/support)** for any of your queries.
---
# How Pricing Plans And Billing Works In xCloud - xCloud
> Follow this billing guideline while purchasing your xCloud package.
When a user creates a server in **[xCloud](http://hidden-hamlet-226309.wp1.sh)**, the system employs a prepaid billing model. We automatically generate invoices and charge your account’s primary payment method on the first day of each month for all existing servers.
## **Account Activation and Free Tier Access** [#](/docs/how-billing-works-in-xcloud/)
New users can start using xCloud with the **Free Plan**, which allows the creation of **one server and up to 10 sites** by integrating their preferred cloud providers, such as DigitalOcean (DO), Vultr, or Google Cloud Platform (GCP).
Although the Free Plan does not charge for the xCloud platform itself, **a valid credit card must still be added to the account** to activate and use the Free Plan server. This ensures billing readiness if the account upgrades to a paid plan or uses paid services.
Some services, such as **xCloud Managed Servers and additional premium features**, are not accessible under the Free Plan and require an active payment method and paid billing structure.
If your account is already using **any paid plan or paid server**, you will **no longer be eligible to use the Free Plan**.
Users can also upgrade their Free Plan server manually at any time.
### **Billing Workflow** [#](/docs/how-billing-works-in-xcloud/)
The cost of the server is immediately deducted from the user’s primary payment method upon creation. Unused hours for the server of the first month will be adjusted in the following month, ensuring you pay what you use in the first month only.
### **Server Billing Workflow Example** [#](/docs/how-billing-works-in-xcloud/)
If a user purchases a Growing server on January 15th for $50, they will be charged $25 in the next month for the same server. However, removing that particular server will not result in adjustments for other servers.
### **Server Resize Or Upgrade Billing Example** [#](/docs/how-billing-works-in-xcloud/)
The billing for resizing a server is pretty straightforward. Suppose, you have a server on the Growing plan which costs $30. After 7 days, you decide to upgrade to the Titanium plan, priced at $100. Since you have already used a portion of the Growing plan, we will deduct that and adjust the unused amount.
In the above scenario, you have $23 unused amount as you have used $7 with the Growing plan in the 7 days. Since you upgrade to the Titanium plan which costs $100, you only pay the rest of the amount. In this case, that would be $100 – $23 = $77.
### **Server Backup Billing Example** [#](/docs/how-billing-works-in-xcloud/)
Server Backup pricing will be adjusted accordingly with server resizing or upgrading.
For example, if a user purchases a server on January 15th for $5, they will be charged $2.5 in the next month for the same server. However, removal of that particular server will not result in adjustments for other servers.
### **Pricing Plans** [#](/docs/how-billing-works-in-xcloud/)
xCloud offers multiple pricing plans so that users can easily pay for what they need. Here you can check all the [**pricing plans**](/). For a more detailed understanding, let us have a look below.
Currently, xCloud provides **2 types of services** under multiple pricing plans. One is xCloud Managed Hosting and the other is Self-Managed Hosting.
### **xCloud Managed Hosting** [#](/docs/how-billing-works-in-xcloud/)
This service offers to elevate your site with xCloud servers. It ensures speed and security, with no hidden charges in the future. This service has different packages where you will be charged monthly based on configuration. Have a look at the plans below to select your needs. Also, you can check the pricing page.
_Note: If you have any questions or queries related to the services, please reach out to our [support team](https://support.xcloud.host). We are always here for your help._
## Self-Managed Hosting [#](/docs/how-billing-works-in-xcloud/)
This service allows you to bring your own server from providers such as Vultr, DigitalOcean, GCP, Linode, Hetzner, Contabo, or other cloud providers and manage it through xCloud.
This service uses **tier-based pricing** with four available plans:
- **Free:** No cost for 1 server and up to 10 sites (limited features)
- **Starter:** $5/server/month for 1–5 servers (all features)
- **Professional:** $4/server/month for 6–10 servers (all features)
- **Agency:** $3/server/month for 10+ servers (all features)
Users can initially start with the **Free Plan**, but a **credit card must still be added to the account** to activate the server and maintain billing readiness.
Once a payment is made for any server under the account, the **Free Plan automatically expires**, and the account moves permanently to the paid pricing structure.
If an account is already operating under any **paid plan**, it cannot switch back to or access the Free Plan.
At first, you can start using xCloud for free, with limited features. To unlock more features, when you add a card payment method, then the Free Plan server will be charged $5 according to Starter plan tier-based pricing.
For 1st 5 servers, you have to pay $5 for each. After adding the 6th server, it will be charged $4 according to the Professional plan tier-based pricing. And, if you add 10+ servers, then it will be charged $3 according to the Agency plan tier-based pricing. Have a look at the pricing plans for this service.
_Note: If you have any questions or queries related to the services, please reach out to our [support team](https://support.xcloud.host). We are always here for your help._
For more details, visit this [page](/self-managed-hosting/).
## **Refund Policy** [#](/docs/how-billing-works-in-xcloud/)
xCloud offers a very transparent refund policy, which includes:
- **For LTD & [Self Managed Hosting](/self-managed-hosting/)**: 14-day refund policy, no questions asked.
- **For xCloud Provider & [xCloud Managed Servers](/managed-hosting/):** the unused amount will be refunded after deducting the Stripe fee.
### **Refund Policy for xCloud Managed Servers** [#](/docs/how-billing-works-in-xcloud/)
We use the third-party payment processor **‘Stripe’** to process payments. All transactions are subject to the terms and conditions of the payment processor. If you delete your xCloud Managed Server, you will be charged for the total usage of the server, along with up to **10%** **Stripe** fee based on the used amount. You will be billed for a minimum of one day, regardless of whether you delete the server within an hour or a day of provisioning, including the associated Stripe fee. The remaining unused amount, after deducting the used amount and Stripe fees, will be refunded to your account.
### **Hosting Addons Refund Policy** [#](/docs/how-billing-works-in-xcloud/)
Refunds are **not available** for any **[hosting addons](/hosting-addons/)** after the subscription has been completed.
Once you activate or purchase an addon, the payment is final. No refunds will be processed under any condition for addon services.
Please make sure to review your choices before subscribing to any hosting addon.
## **How to Request a Refund** [#](/docs/how-billing-works-in-xcloud/)
To request a refund, reach out to our support team with your account email and share the details. Our team will review your case and respond promptly.
Approved refunds are processed within 5–10 business days and returned to your original payment method. All refund amounts are calculated in USD.
### **Late Payments** [#](/docs/how-billing-works-in-xcloud/)
Our billing cycle charges accounts on the first day of each month. If your account remains past due, it may be temporarily suspended. If you require additional time to settle your bill, please reach out to our support team for further assistance within the first week of the month.
We’re here to provide you with reliable cloud services, and our support team is ready to assist you with any billing-related inquiries or concerns you may have.
### **Pricing Plans** [#](/docs/how-billing-works-in-xcloud/)
From our [**official sale page**](http://hidden-hamlet-226309.wp1.sh/#pricing) please check our pricing plans of **Bring Your Own Servers**.
## **Frequently Asked Questions** [#](/docs/how-billing-works-in-xcloud/)
### **What happens to the Free Plan after I add a payment method?** [#](/docs/how-billing-works-in-xcloud/)
Once a payment method is added and a payment is made for any server under the account, the Free Plan automatically expires.
### **Can the Free Plan be reactivated after it expires?** [#](/docs/how-billing-works-in-xcloud/)
No. After a payment method is used and a paid server is created, the Free Plan **cannot be reactivated** for that account.
### **Does adding a payment method immediately remove the Free Plan?** [#](/docs/how-billing-works-in-xcloud/)
No. Adding a payment method alone does not remove the Free Plan. The Free Plan expires only **after a payment is made for any server under the account**. At that point, the account permanently transitions to the paid billing structure.
### **What happens to the Free Plan after I add a payment method?** [#](/docs/how-billing-works-in-xcloud/)
Adding a payment method alone does not remove the Free Plan. However, once a payment is made for any server under the account, the Free Plan automatically expires.
### **Can the Free Plan be reactivated after it expires?** [#](/docs/how-billing-works-in-xcloud/)
No. After a payment method is used and a paid server is created, the Free Plan cannot be reactivated for that account.
### **Does adding a payment method immediately remove the Free Plan?** [#](/docs/how-billing-works-in-xcloud/)
No. The Free Plan remains active after adding a payment method. It expires only when a payment is made for any server under the account.
### **Do I need a credit card to use the Free Plan?** [#](/docs/how-billing-works-in-xcloud/)
Yes. Even though the Free Plan does not charge for the platform itself, a **valid credit card must be added to the account** to activate and use the Free Plan server.
### **Can I use the Free Plan if I already have a paid plan?** [#](/docs/how-billing-works-in-xcloud/)
No. If your account is already using **any paid plan or paid server**, the Free Plan cannot be activated or used.
---
# How Caching Works In xCloud - xCloud
> Follow this guide to learn how xCloud caching works.
In [**xCloud**](/), caching is a technique used to make websites load faster. There are two main types: page caching and object caching.
Page caching involves saving entire web pages so that when someone visits the site again, the page loads much faster because it doesn’t need to be recreated from scratch. xCloud uses FASTCGI NGINX to implement this type of caching.
Object caching, on the other hand, focuses on saving specific pieces of information from the website’s database, like menus, post details, or other dynamic content. By saving this information, the website doesn’t have to repeatedly search the database for the same data, which speeds up loading times. xCloud uses Redis Object caching for this purpose.
So, with both page caching and object caching working together, xCloud helps websites perform better and provide a smoother experience for visitors.
## FastCGI Nginx Caching [#](/docs/how-caching-works-in-xcloud/)
[**FastCGI**](https://www.nginx.com/resources/wiki/start/topics/examples/fastcgiexample/) is great for busy websites with lots of visitors, especially those that update their content often, like popular blogs or news sites with active comments. It keeps everything running smoothly even when lots of people are accessing the site at the same time.
For these busy sites, micro-caching is super helpful. It quietly updates the cache in the background every time someone views a page, making sure that everyone sees the latest content.
But if your website doesn’t have tons of visitors all at once and your content doesn’t change much, Redis Nginx Page Caching is usually a better choice. It’s a simpler option that works well for most websites.
## How To Use FastCGI NGINX Page Caching in xCloud? [#](/docs/how-caching-works-in-xcloud/)
Turning on Nginx FastCGI caching is perfect for WordPress websites. It’s great for sites that are live and getting lots of traffic. But if your site is still in testing or you’re not worried about speed, you can turn it off. You don’t need any extra plugins for caching to work, but if you want to use one, it’s better to disable FastCGI caching in xCloud and use the plugin instead.
## Redis Object Caching [#](/docs/how-caching-works-in-xcloud/)
[**Redis Object Caching**](https://docs.wp-rocket.me/article/1359-redis-object-caching) boosts WordPress performance by storing data in memory using Redis. This means fewer requests to the main database, making your site faster and more scalable.
Here’s how it works: When someone visits a page, Redis saves the data from the database. Next time someone wants the same info, Redis serves it directly, skipping the database query.
With Redis Object Caching, your site can handle more visitors without slowing down. You can set it up easily with the Redis Object Caching plugin and clear the cache directly from xCloud.
## Using A Third-party Page Cache Plugin? [#](/docs/how-caching-works-in-xcloud/)
If you’re already using plugins like WPRocket, WP Super Cache, or W3 Total Cache, you can choose the appropriate caching option in the xCloud Cache section to match. This ensures that your caching settings across different tools are aligned and optimized for your website’s performance.
### Automatic Rocket Nginx Configuration With WPRocket [#](/docs/how-caching-works-in-xcloud/)
The major benefit of using Rocket-Nginx with WP-Rocket is that it makes your WordPress website faster. When someone visits your website, WP-Rocket caches (stores) certain parts of your website, like images, CSS files, and JavaScript files. With Rocket-Nginx, these cached files are served directly by the web server (Nginx) without needing to involve WordPress or PHP. Rocket-Nginx is a powerful Nginx configuration that enhances the performance of your WordPress website by serving cached files directly from the server. By automating the Rocket-Nginx configuration process with xCloud, you can enjoy the following benefits:
Faster Website Load Times: Rocket-Nginx eliminates the need for executing PHP code and querying the database, resulting in significantly faster load times for your website.
Reduced Server Load: By serving pre-cached files directly from the server, Rocket-Nginx decreases the load on your server, enabling it to handle more concurrent visitors without slowing down.
Improved User Experience: Quicker page loading enhances the browsing experience for your visitors, reducing bounce rates and increasing engagement.
If you turn on this option then xCloud will automatically enable NGINX with a single click to directly serve previously cached files without calling WordPress or any PHP. It also adds headers to cached CSS, JS, and images via the browser cache. As a result, your website will be much faster.
### Standard WordPress-Nginx Configuration With WP Super Cache & W3 Total Cache [#](/docs/how-caching-works-in-xcloud/)
The Standard WordPress-Nginx configuration with WP Super cache & W3 Total Cache is designed to enhance the performance and speed of a WordPress website by implementing caching mechanisms.
It leverages WP Super cache & W3 Total Cache to generate static HTML files, reducing server load and improving response times. If you are using WP Super cache & W3 Total Cache and want to configure Standard WordPress-Nginx configuration automatically, all you need to do is just enable this option. And with a single click, xCloud automates the whole steps and configures everything on behalf of users.
As a result, users can effortlessly optimize the performance and speed of their WordPress websites without manually configuring the server.
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How Can I Get Support In xCloud? - xCloud
> Learn where will you get support in xCloud, if you face any difficulties while using this server and site management solution.
At xCloud, we care about users and provide support for all. Our dedicated support team is ready to solve any issues you may face while using xCloud. Additionally, we have [**step-by-step documentation**](https://xcloud.host/docs/) so you can independently troubleshoot and resolve issues without relying on support. Take a look at our support details here.
## **Where Should I Ask For Support?** [#](/docs/how-can-i-get-support-in-xcloud/)
We have a ticketing system and live chat support to help you as early as possible. We also have a [**Facebook community**](https://www.facebook.com/groups/xcloud.community) where you can ask for help. Check out the options available for reaching out when you require assistance below.
### **Live Chat Support** [#](/docs/how-can-i-get-support-in-xcloud/)
We have live chat that you will find on the bottom left corner of our website or the app dashboard. We will try to respond instantly, however, if we have too much support pressure you can expect us to get back to you within 30 to 1 hours max. Learn here when you should knock on our live chat below.
- **Presale Queries:** If you have any presale queries you should knock our live support. Our support representatives will get back to you as soon as possible.
- **General Help:** If you have any questions regarding any features, or are stuck in any step, you can drop us a line in the live chat.
- **Urgent Help:** If you have a serious issue, or you need urgent help just reach out to live chat. It will be transferred to our relevant department, and we will solve your issue as soon as possible.
### **Submit Support Ticket** [#](/docs/how-can-i-get-support-in-xcloud/)
We have a ticketing system that you can use to get technical support from us. We will try to resolve your issues within 12-24 hours max if this can be done via SSH or platform level issues. While submitting your tickets you should add relevant screenshots, screen recordings, or URLs to help us understand your issue faster. You should [**create a ticket**](https://app.xcloud.host/support/all-tickets) if you need support for the following things:
- **Free Migration Request:** We will help you if you need any help with migration.
- **Accounts & Billing:** If you have any questions requiring accounts or billing, you can submit a support request. Besides, if you need a refund, you should submit a support ticket. Please, share your invoice ID while submitting this type of ticket.
- **Bug Report:** If you find a bug, you should submit a ticket to help us track the issue and solve it as soon as possible.
- **Suggestions:** If you have suggestions or feedback for us, or any enhancement request for our existing features, you can submit a support ticket as well.
- **Feature Request:** We would like to hear what you want us to bring next. Please submit a ticket if you have any feature requests.
### **Facebook Community** [#](/docs/how-can-i-get-support-in-xcloud/)
We have an active [**Facebook community**](https://www.facebook.com/groups/xcloud.community) where you can ask questions, and get help from the xCloud community. Though submitting a support ticket is the best option for technical queries, you can explore our community to see if others have encountered similar issues and find solutions. Keep an eye out for important announcements, news, and the latest updates in the Facebook community.
Engage in discussions with the founder, co-founders, community team, and marketing team members who actively participate in the community. You can share your feature suggestions and ideas with detailed explanations, and request a vote to have them added to our roadmap. Additionally, if you create tutorials or guides related to xCloud, we encourage you to share them with the community for everyone’s benefit.
## **Our Support Schedule In Eastern Daylight Time (EDT)** [#](/docs/how-can-i-get-support-in-xcloud/)
Take a look at the weekly xCloud support team schedule and see when we will be able to solve your issues if you face any.
**Days**
**Active Hours**
**Total Coverage Time**
Monday
12:00 AM – 11:59 PM
24 hours
Tuesday
12:00 AM – 11:59 PM
24 hours
Wednesday
12:00 AM – 11:59 PM
24 hours
Thursday
12:00 AM – 11:59 PM
24 hours
Friday
12:00 AM – 6:00 PM &
10:00 PM – 11:59 PM
24 hours
Saturday
12:00 AM – 8:00 PM &
10:00 PM – 11:59 PM
22 hours
Sunday
12:00 AM – 8:00 PM &
10:00 PM – 11:59 PM
22 hours
---
# How Clients Can Set Up a Server with Reseller Hosting Program - xCloud
> Learn how clients can set up a server with Reseller hosting program from the landing page or dashboard.
The xCloud Reseller Hosting Program simplifies the process of creating and managing servers for your clients. With xCloud , reseller’s clients can set up a server easily.
Clients n create your server from the dashboard and create it from the landing page. Follow these steps to create a server easily that meets your needs.
## **Create a New Server from the Landing Page/Sales Page** [#](/docs/how-clients-set-up-a-server-with-reseller-hosting-program/)
Suppose the client visits your reseller’s landing page. Then choose your preferred pricing plan and click on the **‘Select Plan’** button to start the process.
Then, at first, enter your account sign-up credentials: **‘Account Name’, ‘Account Email’** and **‘Password’.**
Then, you can see your chosen **‘Server Size’** and the cost of that plan. If everything is alright, click on the Pay now button.
You will now be taken to the checkout page. Enter the details and click on the **‘Save Card’** to proceed.
Once the payment has been successfully completed, you will be redirected to your **dashboard**. From here, you will see an option to ‘**Set Up Now’**. You can click on this to start creating your server.
_Note: But you do not need to set up the server immediately. You can choose to create your server later through Team Products or when you try to provision a server. If you have already purchased a product, you will get a notification that your server is available. You can then decide whether you want to proceed with the setup or wait._
When you click on the ‘Set Up Now’ option, it will take you to the server setup page.
You will see a notice that says your server setup is pending.
Next, you can give your **‘Server name’** and ‘**Tags’**. Then you can see that the **‘Server Type’** and the **‘Server Size’** are already selected. Keep them as it is, as you have already paid for them.
Then, scroll a bit and go to the ‘Region’ and choose the continent you want to deploy your server on. Next, select any one database from **MySQL** and **MariaDB.**
Now you can enable the ‘Backup’ option, which will add an additional charge to your plan. Next, choose from any one web server from **‘NGINX’** or **‘OpenLiteSpeed’** and click on the **‘Next’** button.
Once you hit the on next button, the server creation process will start. After the server creation process is completed, you will be redirected to the server dashboard.
## **Create New Server From the Dashboard** [#](/docs/how-clients-set-up-a-server-with-reseller-hosting-program/)
Now, if you want to create another server from the dashboard, click on the **‘New Server**’ button.
Next, you can give your **‘Server name’**, ‘**Tags’** according to your preferences.
Then you can see that the **Server Type ‘General and ‘Premium’** and the **‘Server Size’** according to the plans. Choose the server type and size based on your needs. Then select the **‘Region’** on the server.
Next, choose any one database from **MySQL** and **MariaDB.** Now you can enable the **‘Backup’** option, which will add a charge to your plan. Next, choose from any one web server from **‘NGINX’** or **‘OpenLiteSpeed’** and click on the **‘Next’** button.
Once you hit the next button, the server creation process will start. After the server creation process is completed, you will be redirected to the server dashboard. And that’s it this is how easily you can create your server.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How Does xCloud Manage High Concurrency for BuddyBoss-Powered Community Sites? - xCloud
> Discover the xCloud infrastructure manages high concurrency for BuddyBoss sites with NGINX, OLS, fast CPUs, and NVMe storage for peak performance.
xCloud’s infrastructure is designed to **manage high concurrency**, which is essential for community sites powered by BuddyBoss. Our stack includes **NGINX**, **OpenLiteSpeed** (OLS), **MySQL**, and **MariaDB**, allowing us to efficiently handle multiple simultaneous user interactions without slowing down your site. With powerful multi-core CPUs, fast memory, and **NVMe** storage, our servers can support thousands of concurrent users, ensuring stability and speed even during peak traffic times.
Still stuck? Contact our [**support team**](/contact/) for any of your queries.
---
# How long is the trial period supposed to be? - xCloud
> With the xCloud trial period, you can manage 10 sites with limited features on one VPS server. However, your account will be automatically upgraded to the
With the xCloud trial period, you can manage 10 sites with limited features on one VPS server. However, your account will be automatically upgraded to the next tier when you add more servers.
During the trial of xCloud’s control panel, you get limited features. To use it, you need your own server, and you’ll have to cover the server costs. The trial is free for life until you add a payment method. You can also explore xCloud through the Playground during the trial.
---
# How Many Sites Can Be Hosted Efficiently On A Single Server? - xCloud
> Selecting an appropriate server size is essential for optimal performance in single server.
Efficiently hosting multiple websites on a single server demands a strategic approach to balance performance, resource allocation, and user experience. This guide offers insights and guidelines for informed decision-making, considering factors like website type, traffic patterns, caching, resource availability, and more. Factors to Take into Account:
### Website Type and Characteristics [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Different websites exhibit varying resource demands. Static sites with full-page caching require fewer resources compared to dynamic e-commerce or membership sites with intensive database functions.
### Traffic Patterns For Single Server [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
The volume of website traffic significantly impacts server load. High-traffic sites may require more server resources to handle user visits effectively.
### Caching Capabilities [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Efficient caching reduces server load by delivering cached content. Websites with effective caching can manage higher traffic with fewer resources.
### Resource Availability [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Server specifications, including CPU power, RAM, and storage, determine hosting capacity. More robust servers can handle a greater number of sites.
### Codebase and Plugins [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Resource-heavy plugins or themes can strain server performance. Evaluate codebase and plugin resource requirements when determining hosting density.
### User Experience and Performance [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Prioritizing user satisfaction and site performance is crucial to avoid slow loading times and subpar experiences.
# Best Practices [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
**We strongly recommend distributing sites across multiple servers and this is the best practice. If something goes otherwise in your server then your all sites are not down.** **It is recommended not to host more than 15 sites in** **an instance.**
### Hosting Fully Cached Brochure Websites [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
These are static sites with fully cached pages.
\*\*Recommended Configuration:\*\*
– Host up to 10 simple websites on a 2GB RAM / 1 shared CPU server.
– Alternatively, consider hosting 10-15 simple websites on a 2 CPU 4GB RAM server for improved performance.
– Distribute sites across multiple servers to mitigate risks during server downtime.
### Hosting Dynamic Websites [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
These are sites with varying resource demands due to traffic and codebase.
\*\*Guidelines:\*\*
– Allocate dedicated resources for optimal performance.
– For low-traffic dynamic sites with similar demands, consider sharing 2-4 CPU servers.
Dynamic sites with cache bypassing traffic may require dedicated resources. Low-traffic dynamic sites can share 2-4 CPU servers.
### Choosing the Right Server Size [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Selecting an appropriate server size is essential for optimal performance. Consider these factors:
– Amount of traffic served from the page cache.
– Peak traffic levels.
– Usage of external databases.
– Database and media library sizes.
To ensure scalability, opt for a slightly larger server with extra capacity. For example, choose a 2GB RAM server for a WordPress site.
– Smaller sites can share a single server if using page caching (around 10 sites on a 2GB RAM / 1 shared CPU server).
– For complex sites, especially high-traffic or dynamic ones, a dedicated, larger server is advisable.
– Page caching can efficiently handle significant traffic with minimal resources.
### Shared CPU vs. Dedicated CPU [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Consider the server type based on your needs:
– Shared CPU: Suitable for staging/testing sites and low-consequence production sites. Minor delays during CPU sharing may occur.
– Dedicated CPU: Ideal for critical production sites with limited page caching, especially those using heavy plugins like WooCommerce.
While shared CPU servers are cost-effective, dedicated CPU servers offer enhanced performance, particularly for response times.
### Monitoring and Server Upgrades [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Regularly monitor server resources using provided tools or SSH if needed. Maintain memory usage below 60% to accommodate traffic spikes. Consistent high CPU or memory usage may signal the need for an upgrade.
### Server Snapshots and Backups [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
Leverage server provider snapshots for data backups, providing essential insurance for your business. Typically, this adds around 20% to the base price.
## Recommendations [#](/docs/how-many-sites-can-be-hosted-on-a-single-server/)
To sum up, These are the minimum configurations **[xCloud](http://hidden-hamlet-226309.wp1.sh)** suggest you begin with. Later you can always upgrade your server plan as you grow.
**Scenario**
**Site Type**
**Server Configuration**
**Recommended Sites**
Low Traffic + Fully Cached
Brochure Sites
2GB RAM / 1 shared CPU
10 sites
High Traffic + Fully Cached
Brochure Sites (Fully Cached)
4GB RAM / 2 CPU
10-15 sites
Low Traffic + No cache
Dynamic Sites (e.g., WooCommerce, LMS)
2GB RAM / 1 shared CPU
1 Site
Moderate Traffic + No cache
Dynamic Sites (e.g., WooCommerce, LMS)
4GB RAM / 2 CPU
1 Site
\*\*Recommended Server Configuration:\*\*
1\. It is advised to allocate a minimum of 2GB of RAM to ensure optimal performance for hosting a WordPress website on xCloud’s technology infrastructure.
2\. Consider selecting a plan priced between $40 to $48 per month, offering around 4 virtual CPUs and 8GB of RAM.
3\. It is recommended not to host more than 15 sites on a single instance.
---
# How Scalable Is xCloud & What Are Your Future Plans? - xCloud
> How scalable is xCloud? We offer seamless plan upgrades, ensuring your website can grow effortlessly as we enhance your WordPress hosting experience.
If you ask how scalable is xCloud, it has **unparalleled scalability**, allowing users to upgrade their hosting plans as their websites grow. Whether you are beginning a small or running a large website, you can quickly upgrade to **more powerful servers** with no downtime. In addition, we are continuously working on upgrading our technology and improving our services to ensure you enjoy the best WordPress-managed hosting experience.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Access Page Speed Insights for Website Performance Reports on xCloud - xCloud
> Learn how to access Page Speed Insights on xCloud to monitor performance, review Core Web Vitals, and improve SEO and user experience.
Website performance plays a key role in user experience and search engine ranking. A slow site can push visitors away, while a fast site helps you keep them engaged. [**Page Speed Insights**](https://pagespeed.web.dev/) on xCloud gives you a clear view of how your website performs and highlights issues that need fixing.
By using it, you can improve speed, accessibility, best practices, and SEO, which are all important for growth. To ensure you fully leverage this tool, it is essential to learn how to access Page Speed Insights effectively.
Follow the steps below to access Page Speed Insights on xCloud and optimize your website for better performance in just a few clicks:
## **Step 1: Access Page Speed Insights** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
First, go to your site dashboard, then navigate to the **‘Monitoring’** option from the sidebar menu, and then click on the **‘Page Speed’** from the menu.
## **Step 2: Review Site Performance Graphs** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
In this section, you will see the **‘Site Performance’** area displayed as a graph. This graph shows your site’s overall scores for **‘Performance’**, **‘Accessibility’**, **‘Best Practices’**, and **‘SEO’**. These scores help you quickly understand how well your site is functioning in terms of speed, usability, coding quality, and search optimization.
- **Performance:** Measures how fast and responsive your website is.
- **Accessibility:** Checks if your site is easy to use for everyone, including people with disabilities.
- **Best Practices:** Reviews whether your site follows safe and modern coding standards.
- **SEO:** Look at how well your site is prepared to rank in search engines.
## **Step 3: Switch Between Mobile and Desktop Views** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
At the top right corner of the performance section, you will find buttons labeled **‘Mobile’** and **‘Desktop’**. By switching between these options, you can view how your site performs on different devices.
## **Step 4: Explore Page Speed History** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
When you scroll down, you will come across the **‘Page Speed History’** section. This area stores the historical data of your site’s performance. By reviewing it, you can track whether the improvements you made in the past have had a positive effect on your site’s health over time. Also, click on the **‘Analyze Now’** button to get the latest results instantly.
## **Step 5: Check Detailed Reports** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
For deeper analysis, click on the **‘View Details’** link. Here, you will find a detailed breakdown of your site’s scores in **‘Performance’**, **‘Accessibility’**, **‘Best Practices’**, and **‘SEO’**. These results give you a clear view of which areas are strong and which need more attention.
## **Step 6: Review Core Web Vitals** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
You can also review the **‘Core Web Vitals Assessment’**, which highlights vital elements that reflect real-world user experience. These include **‘Speed Index’**, **‘Time To Interactive’**, **‘Total Blocking Time’**, **‘First Contentful Paint’**, **‘Cumulative Layout Shift’**, and **‘Largest Contentful Paint’**. These metrics show you exactly how users experience your website in terms of speed, responsiveness, and stability while it loads.
- **Speed Index**: Tells how fast the visible content on your page appears while it loads. A lower value means the page looks ready sooner.
- **Time To Interactive**: Shows how long it takes before users can fully interact with the page without delays.
- **Total Blocking Time**: Measures the time when the page cannot respond because scripts are blocking it.
- **First Contentful Paint**: Marks the moment when the first text or image appears on the screen.
- **Cumulative Layout Shift**: Tracks how much the page layout moves around as it loads. Less shifting means a smoother experience.
- **Largest Contentful Paint**: Records how long it takes for the main piece of content, like a large image or text block, to appear.
## **Step 7: Use Insights and Diagnostics** [#](/docs/how-to-access-page-speed-insights-on-xcloud/)
Finally, at the bottom of the report, you will find **‘Insights’** and **‘Diagnostics’**. Insights identify the major issues that may be slowing down your website, while diagnostics provide clear recommendations to fix those problems.
For example, you might be advised to reduce unused CSS or JavaScript, compress large images, improve server response times, or enable caching. By following these suggestions, you can significantly improve the overall performance of your site.
And that is it, this is how easily you can monitor your site regularly, create a website that is fast, user-friendly, and search engine optimized. This not only enhances the experience for your visitors but also increases your chances of ranking higher and staying competitive online.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Access the xCloud API - xCloud
> Learn how to access the xCloud API. Create an API token, set permissions, and manage your servers and sites through code.
The xCloud API gives you programmatic access to the xCloud Platform. Developers, e-commerce store owners, and development agencies can use it to integrate server operations, run application tasks, and automate the workflows behind their servers.
Instead of checking server stats or managing your VPS by hand, you can perform these tasks with a few simple commands, then build the dashboards, alerts, and integrations that fit how you already work.
## **Key benefits of using the xCloud API:** [#](/docs/how-to-access-the-xcloud-api/)
- **Full Platform Access:** Run the same server and site operations available on the dashboard.
- **Seamless Integration:** Connect xCloud to your existing tools and pipelines.
- **Automation:** Run restarts, deployments, and routine tasks without manual effort.
- **Real-Time Insights:** Monitor CPU, RAM, disk space, and network traffic on demand.
- **Custom Dashboards:** Build your own views on top of live server data.
- **Scoped Permissions:** Control access with read and write tokens for servers and sites.
- **Bulk Management:** Manage multiple servers and sites in one workflow.
### **Step 1: Navigate to API Settings** [#](/docs/how-to-access-the-xcloud-api/)
First, go to your xCloud dashboard. Navigate to the left-hand sidebar menu, select Settings, and then click on the ‘Developers’ option from the left side menu and click on the ‘API Tokens’ option. Within the API tokens interface, click the Create New Token button.
### Step 2: Configure Token Name and Permissions [#](/docs/how-to-access-the-xcloud-api/)
A pop-up will appear. Enter a descriptive name for your token and select the appropriate permissions:
1. Full Access (all permissions)
2. read:servers
3. write:servers
4. read:sites
5. write:sites
Once configured, click Create Token.
### **Step 3: Copy and Store Your API Token** [#](/docs/how-to-access-the-xcloud-api/)
After creation, your token will be displayed. Copy and store it in a secure location immediately, as you will need it for future authentication.
### **Step 4: Deleting an API Token** [#](/docs/how-to-access-the-xcloud-api/)
If you no longer require a specific token, locate it in the dashboard and click the **Delete** icon to remove it.
You now have everything you need to access the xCloud Public API. Create a token, set its permissions, and store it safely to start managing your servers programmatically.
### 📑 Explore the API Documentation [#](/docs/how-to-access-the-xcloud-api/)
With your token ready, visit the [**API documentation**](https://app.xcloud.host/api/v1/docs#description/introduction) to learn about the available endpoints and start building.
If you face any issues, please do not hesitate to contact our [**support team.**](https://support.xcloud.host/)
---
# How to Activate the Cloudflare Enterprise Addon on Your Domain - xCloud
> Cloudflare Enterprise normally means a direct contract with Cloudflare, negotiated at volume and priced for large organizations. xCloud already holds that
Cloudflare Enterprise normally means a direct contract with Cloudflare, negotiated at volume and priced for large organizations. xCloud already holds that contract. The addon lets you put a single domain behind it for $5 a month, with none of the negotiation and no minimum commitment.
It runs on Cloudflare for SaaS. Your domain joins xCloud’s Cloudflare account as a custom hostname, so you keep your current DNS provider, leave your nameservers where they are, and add one CNAME record. Everything after that happens in your xCloud dashboard: cache rules, WAF toggles, purge, analytics, security events. You will never need to log into Cloudflare.
Below is the whole process, from buying the addon to reading your first security report.
## **What Cloudflare Enterprise does for your site** [#](#what-cloudflare-enterprise-does-for-your-site)
Once a domain is verified, its traffic stops going straight to your server and starts coming through Cloudflare’s edge network. That changes a few things:
- Static files like images, CSS, and JavaScript are served from whichever Cloudflare location is nearest your visitor.
- Dynamic pages can be cached at the edge too, which cuts the wait before the first byte arrives. xCloud turns off local page caching when you enable this so the two do not fight each other.
- Cloudflare’s managed WAF rulesets sit in front of the site and catch emerging threats, including zero-days.
- Layer 7 DDoS attacks can be met with Under Attack Mode, which makes every visitor pass an extra check before reaching the site.
- Noisy traffic gets filtered: rate limiting on IPs that exceed the threshold, browser integrity checks on malformed requests, and a switch to block known AI crawlers.
- Images are compressed at the edge, Early Hints let browsers start fetching assets sooner, and ScrapeShield scrambles email addresses so bots cannot harvest them.
- Request counts, data transfer, and security events are reported back into your dashboard.
Activation is per domain rather than per site, per server, or per plan, so you can cover the domains that need it and leave the rest alone.
## **Pricing** [#](#pricing)
$5 per month, per domain. Each subscription covers one domain. Every domain and subdomain will count as separate domain. If you want several domains protected, subscribe to each one and manage them together from the Addons page.
> _Note: We are not providing support additional domains yet, but will be available very soon._
## **Prerequisites / required permissions** [#](#prerequisites--required-permissions)
- The team must be billing-enabled and eligible to purchase addons.
- The site must already exist under a server.
- The domain must be available to configure at its DNS provider.
- For manual DNS setup, the user needs DNS access for the domain.
- Production/staging must have the Cloudflare Enterprise configuration in place before domains can activate successfully.
## Step 1: Activate the Cloudflare Enterprise Addon [#](#step-1-activate-the-cloudflare-enterprise-addon)
From your dashboard, first click on the ‘Addons’ button and then find the ‘Cloudflare Enterprise’ Addons and click on the Enable button.
## Step 2: Enable Cloudflare Enterprise on your site [#](#step-2-enable-cloudflare-enterprise-on-your-site)
Next click on the enable button and proceed. You can activate Cloudflare Enterprise on any domains for just $5/month.
Next, choose the domain from the dropdown of the popup and click on the Pay button to pay proceed with enabling Cloudflare for this site.
You can also open the feature from a specific site at **Site → Cloudflare Enterprise**. Before any domains are added, the site page shows an empty state and an **Enable Cloudflare Enterprise** button.
## **Step 5. Configure the DNS Setup** [#](#step-5-configure-the-dns-setup)
Once you are done with the payment you will see that the Cloudflare Enterprise is activated on your domain and added to the dashboard. If you have Cloudflare integrated, you will see the domain is activated instantly. If the domain is not added with Cloudflare, you will see a status showing ‘Pending Verification’.
Next, click on the three dot icon and click on the ‘Manage’ option from the menu to complete the DNS verification and configure the Cloudflare Enterprise Addon.
Next under the Domain tab you can click on the ‘CNAME Records’ option from the dashboard. xCloud opens a DNS instructions modal showing the exact records the customer should add at their DNS provider.
Once you click on the ‘CNAME Records’, you will be able to get the records that you need to configure with your domain provider.
Once, you add the records on your domain provider, go to the Domain status tab and click on the refresh button.
It will show you the domain as active. Now you can proceed to configure other Cloudflare enterprise settings.
### **Step 6: Configure Cloudflare settings** [#](#step-6-configure-cloudflare-settings)
Now visit domain where you have activated the Cloudflare enterprise, and click on the ‘Cloudflare Enterprise’ option from the dashboard. Here you will see the domain you have activated for listed under the Domains tab
Next, go to the ‘Overview’ tab, here you will get the option of ‘Purge Cahce’. You can clear all cached content from Cloudflare and forces content to be fetched directly from your server right from your xCloud dashboard.
### **7\. Configure optimization settings** [#](#7-configure-optimization-settings)
Next, open **Settings** tab. Here you will get **Optimization options for your site.** These settings apply to all Cloudflare Enterprise domains on the current site.
Optimization options:
**Setting**
**What it controls**
**Early Hints**
Sends 103 Early Hints so browsers can preload linked assets before the final response arrives.
**ScrapeShield**
Obfuscates email addresses on the website to reduce harvesting by bots/spammers.
**Caching**
Caches static content such as images, CSS, and JavaScript on Cloudflare’s global CDN.
**Edge Page Caching**
Caches dynamic pages at the edge for faster TTFB; local page caching is bypassed automatically to avoid conflicts.
**Image Optimization**
Uses Cloudflare Polish-style image optimization.
**SSL Cipher**
Controls the SSL/TLS cipher profile used between visitors and the Cloudflare edge.
### **8\. Configure security settings** [#](#8-configure-security-settings)
Next, under the **Security** section below the optimization settings comes with many security options. These cover WAF and abuse-protection behavior for the site’s Cloudflare Enterprise domains.
Security options:
**Setting**
**What it controls**
**Web Application Firewall**
Blocks emerging threats, including zero-days, using Cloudflare managed WAF rulesets.
**Rate Limiting**
Applies managed challenges to IPs exceeding the managed request threshold.
**Browser Integrity Check**
Blocks requests with suspicious or missing HTTP headers commonly used by abusive bots.
**Under Attack Mode**
Last-resort Layer 7 DDoS protection; visitors must pass additional validation before accessing the site.
**AI Crawler Blocking**
Blocks known AI crawlers from scanning or collecting site content.
You can toggle on or off each of the option according to your preferences. Click **Save Changes** after changing any toggle or select. xCloud persists the settings for the site.
### **Step 10: Review Analytics: request summary** [#](#step-10-review-analytics-request-summary)
Next Open **Analytics**. The default view is **Request Summary**.
Analytics includes:
- Range selector: **Last 30 minutes**, **Last 6 hours**, **Last 12 hours**, **Last 24 hours**, **Last 7 days**, and **Last 30 days**.
- Request summary cards: **Total Requests**, **Served by Cloudflare**, and **Served by Origin**.
- Time-series chart area.
- Cache status section.
- Top tables for request sources such as content types, paths, hosts, device types, countries, and edge status codes.
### **Step 11: Review Analytics: data transfer summary** [#](#step-11-review-analytics-data-transfer-summary)
Under the ‘Analytics tab you will Use the toggle in the Analytics header to switch from **Request Summary** to **Data Transfer Summary**.
### **Step 12: Review Security events** [#](#step-12-review-security-events)
Next, go to the Open the ‘**Security’** tab to view Cloudflare security-event reporting. Security event reporting includes:
- Range selector using the same time windows as Analytics.
- **Total Events** card.
- **Events By Services** summary.
- Time-series security-event chart area.
- Top event tables: IP addresses, user agents, paths, countries, hosts, and HTTP methods.
### **Step 13: Manage all Cloudflare Enterprise domains from the global addon page** [#](#step-13-manage-all-cloudflare-enterprise-domains-from-the-global-addon-page)
You can manage all your domains from one place under the ‘Addons’ page. You can just click on the three dot icon of each of the domain and Also you can delete any domain from the subscription as well from here.
## **FAQ** [#](#faq)
### Do I need my own Cloudflare account? [#](#do-i-need-my-own-cloudflare-account)
No. Your domain joins xCloud’s Cloudflare account as a custom hostname. Everything is managed from your xCloud dashboard, and you never log into Cloudflare.
### Do I have to change my nameservers? [#](#do-i-have-to-change-my-nameservers)
No. Keep your domain at its current DNS provider. You only add the CNAME records xCloud shows you in the DNS instructions modal.
### How much does it cost? [#](#how-much-does-it-cost)
$5 per month, per hostname. Each subscription covers a single domain. Subdomains are counted separately, if you want to use Cloudflare Enterprise for each domain
### Is it per site, per server, or per domain? [#](#is-it-per-site-per-server-or-per-domain)
Per domain, and that includes subdomains. Every hostname you want behind Cloudflare Enterprise needs its own $5/month subscription, so `example.com`, `www.example.com`, and `shop.example.com` would each be a separate purchase.
### Why does my domain say “Pending Verification”? [#](#why-does-my-domain-say-pending-verification)
It means the CNAME records aren’t visible yet at your DNS provider. Add the records shown under Domain → CNAME Records, then open the Domain Status tab and hit refresh. If your Cloudflare account is already integrated with xCloud, the domain activates instantly and you can skip this.
### Will this conflict with xCloud’s page caching? [#](#will-this-conflict-with-xclouds-page-caching)
No. When you turn on Edge Page Caching, xCloud automatically bypasses local page caching so the two layers don’t fight each other.
### Do the settings apply to one domain or all of them? [#](#do-the-settings-apply-to-one-domain-or-all-of-them)
The Optimization and Security toggles apply to every Cloudflare Enterprise domain on the current site. Remember to click Save Changes after any toggle or dropdown change.
### How do I clear the Cloudflare cache? [#](#how-do-i-clear-the-cloudflare-cache)
Open the Cloudflare Enterprise section for the domain, go to the Overview tab, and use Purge Cache. It clears all cached content and forces the next request to fetch from your server.
### Can I remove a domain later? [#](#can-i-remove-a-domain-later)
Yes. On the Addons page, click the three-dot icon next to the domain and delete it from the subscription.
### What happens if I delete the CNAME records? [#](#what-happens-if-i-delete-the-cname-records)
Traffic stops routing through Cloudflare’s edge and the domain drops out of verification. Add the records back and refresh the Domain Status tab to bring it live again.
### How long does activation take? [#](#how-long-does-activation-take)
After DNS is pointed correctly, xCloud tries to activate the domain immediatly, if the Cloudflare account integrated with xCloud. But if you are using a domain with a different domain provider, you need to configure the DNS with your provider then refresh the status on xCloud.
### Can a domain be removed? [#](#can-a-domain-be-removed)
Yes. Use **Remove** from the domain row. xCloud warns that traffic may become unreachable if DNS is still pointed to Cloudflare Enterprise after removal.
### Is the Cloudflare Enterprise addon refundable? [#](#is-the-cloudflare-enterprise-addon-refundable)
No. Like all xCloud addons, the Cloudflare Enterprise addon is non-refundable once the subscription is activated. Addon purchases are final, so please review the domain, pricing, and billing details before you subscribe. You can read the full policy in the [xCloud Refund Policy.](https://xcloud.host/docs/refund-policy/)
---
# How To Add Custom Security Headers in xCloud - xCloud
> Learn how to safely add custom security headers in xCloud for OLS and NGINX servers without risking config overrides. Step-by-step guide included.
Security headers are essential for protecting your websites from common web vulnerabilities by controlling how browsers behave. This guide will walk you through the correct way to add custom security headers in xCloud, covering both OpenLiteSpeed (OLS) and NGINX web servers.
In xCloud, directly editing the main server configuration files (like vhconf.conf) is not recommended, as these files are managed by the control panel and can be overwritten automatically when changes are made via the UI.
## **Add Custom Security Headers on OLS Servers in xCloud** [#](/docs/how-to-add-custom-security-headers-in-xcloud/)
### **Step 1: SSH Into Your Server** [#](/docs/how-to-add-custom-security-headers-in-xcloud/)
Before making any changes, you must SSH into your OLS server:
### **Step 2: Use the vhconf.server.conf Config File** [#](/docs/how-to-add-custom-security-headers-in-xcloud/)
Use the following file to define your custom HTTP security headers:
```
/usr/local/lsws/conf/vhosts/tstr.io/vhconf.server.conf
```
Copy to Clipboard
This file is not overwritten by the xCloud panel and is ideal for persisting manual changes such as custom headers.
### **Step 3: Add Security Headers** [#](/docs/how-to-add-custom-security-headers-in-xcloud/)
To add custom security headers, update vhconf.server.conf with the following block:
```
context / {
extraHeaders << Need to add external database for your xCloud website? This guide shows how to add & configure one during site creation. Includes troubleshooting tips!
[**xCloud**](/) provides a convenient way to manage your website without needing separate database administration. However, if you have specific requirements or prefer an external database solution, In that case, xCloud offers an option to add external database while creating a new site.
## **Steps: How to Add External Database On xCloud** [#](/docs/how-to-add-external-database-on-xcloud/)
You can follow the steps shown below to learn how to Add an External Database in xCloud.
### **Step 1: Create A New Site from xCloud Dashboard** [#](/docs/how-to-add-external-database-on-xcloud/)
From your xCloud dashboard, click on ‘**\+ New Site**,’ choose a server from the dropdown, click on ‘**Next**,’ then select ‘**Install a New Website**.’ Now, add all the details about your new sites.
### **Step 2: Add External Database** [#](/docs/how-to-add-external-database-on-xcloud/)
Scroll down and expand ‘**More Advanced Settings.’** In the Database Management section, choose the option ‘**Add Your Existing Database**’ and add your external database details to establish a database connection.
### **Step 3: Finalize Configuration** [#](/docs/how-to-add-external-database-on-xcloud/)
Click on ‘**Next**’ to configure the external database with your newly created site.
Following these steps and considering the additional factors will enable you to successfully integrate and maintain an external database with your xCloud website.
If you encounter any issues or need further assistance, reach out to [**xCloud support**](https://support.xcloud.host/). Our team is available to help you with any challenges you face while integrating and managing your external database.
---
# How to Adjust PHP Workers in xCloud? - xCloud
> Optimize your website's performance with xCloud. Learn how to adjust PHP workers for better speed, reliability, and user experience following our these steps.
**PHP workers** are processes that execute PHP code concurrently, improving the performance and scalability of web applications. When creating your server in **xCloud** or updating a new PHP version, [**xCloud**](/) adjusts PHP workers count automatically based on the RAM and CPU core available on your server specification.
xCloud provides you the flexibility to set the number of PHP workers to your exact needs from your dashboard. You can find the recommended number of workers count later in this documentation. Optimizing workers can significantly impact your website’s performance, speed, and reliability.
## **How Do You Adjust PHP Workers in xCloud?** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
Following the steps below, you can effectively manage PHP workers to meet your website’s specific requirements.
**_Note:_** _Incorrectly configuring workers count in PHP can affect your website’s performance. It is essential to carefully consider your server’s resources and workload before adjusting._
### **Step 1: Access Your Site in xCloud** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
To adjust the PHP workers of your site, first, log in to your xCloud dashboard. Then, head over to the **‘Sites**’, and choose the website to navigate to the selected site’s ‘**Overview’** page where you want to make the changes.
### **Step 2: Access PHP Settings** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
From the website’s ‘**Overview**’ page, click on the ‘**Settings**‘ tab from the left panel.
### **Step 3: Adjust the Number of PHP Workers** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
In the PHP Settings, set the maximum workers limit in the ‘**Max PHP Workers**’ section considering your site traffic, server’s RAM and CPU resources and click on ‘**Save Settings**’.
**_Note:_** _We recommend allocating max 1 worker per 256MB of RAM and 4 workers per CPU core to avoid overflow and underflow. When adjusting automatically xCloud follows this calculation._
That is how you adjust PHP workers in xCloud to enhance your website’s speed, reliability, and user experience.
## **Determining the Optimal Number of Workers in xCloud** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
While the exact number of PHP workers needed varies for each website, understanding your website’s specific requirements can help you find the optimal configuration. Here is how:
### **Consider Website Type And Workload** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
Different website types have varying demands on workers. Here are some general recommendations to get you started (remember, testing and customization are crucial)
- **Low-Traffic Websites (Blogs, Portfolios):** Begin with a conservative number, like 2 to 3 static workers per CPU core.
- **Medium-Traffic Websites (E-commerce Stores):** For moderate traffic, consider starting with 3 to 4 static workers per CPU core. Websites with complex product catalogs or high user interaction might require further adjustments.
- **High-Traffic Websites (Forums, Social Networks):** These resource-intensive websites might benefit from a wider range (4 to 8+ workers) depending on the complexity of user interactions and database operations.
Before changing the PHP worker count, a thorough assessment of your server’s capacity and workload is recommended.
### **Emphasize Testing And Monitoring** [#](/docs/how-to-adjust-php-workers-in-xcloud/)
A data-driven approach is key. Here are some valuable strategies:
- **Test incrementally:** Increase workers gradually (e.g., +1 per core) and monitor website performance after each change. Use tools like Google PageSpeed Insights or Load Impact to evaluate website speed and identify bottlenecks.
- **Analyze Resource Utilization:** Keep an eye on server resources like CPU and RAM usage within the xCloud dashboard. Too many workers can lead to resource exhaustion, negatively impacting performance.
Note: PHP worker adjustment is only available NGINX servers. Because OpenLiteSpeed uses a different approach to handling PHP requests compared to NGINX. While NGINX typically relies on PHP-FPM (FastCGI Process Manager), which allows for the adjustment of PHP worker processes (or pools), OpenLiteSpeed integrates PHP directly using its own PHP process management mechanism.
Still stuck! Contact our [**dedicated support team**](https://support.xcloud.host/) for assistance with your queries.
---
# How To Allow Caching Of A URL With A Query String - xCloud
> Learn how to enable caching of a URL with a query string in xCloud by ignoring tracking parameters to improve performance and reduce server load.
By default, pages that include query string parameters (anything after “?” in a URL) were excluded from caching. This behavior ensured safety but caused performance issues, especially for marketing traffic.
URLs containing tracking parameters such as utm\_campaign, gclid, or fbclid were always treated as unique pages. As a result:
- **Cache was bypassed every time**
- **Page load times increased**
- **Server resources were used unnecessarily**
To address this, you can now define which query parameters should be ignored, allowing those URLs to be cached and served efficiently.
Previously, any URL with query string parameters automatically bypassed the page cache. As a result, traffic from marketing campaigns using tracking parameters such as **utm\_source, gclid, or fbclid** consistently caused cache misses, leading to slower response times and increased server load.
You can now configure which query string parameters should be ignored when serving cached pages directly from the dashboard. While HTTP rules and cookie rule exclusions were already manageable through the dashboard, fine-grained control over which cookies triggered cache bypasses previously required manual configuration.
## **Step 1: Go to Your Site** [#](/docs/how-to-allow-caching-of-a-url-with-a-query-string/)
To begin, log in to your dashboard and select the site you want to configure. From the site menu, navigate to **WordPress → Caching**. This will take you to the caching settings for the selected WordPress installation.
## **Step 2: Allow Caching of URLs With a Query String** [#](/docs/how-to-allow-caching-of-a-url-with-a-query-string/)
Within the Caching section, click on More Advanced Settings to access additional configuration options. Here, locate the Ignore Query String Parameter setting. This section contains a list of query string parameters that xCloud already ignores by default when serving cached pages.
You can customize this list based on your needs. Remove any parameters that you no longer want to ignore, or add new ones, such as marketing or analytics tracking parameters, that do not affect page content. After saving your changes, URLs containing only these specified query string parameters will be cached normally, helping improve page load times and reduce server load.
And that’s it, this is how easily you can enable caching for URLs with query string parameters. By configuring which parameters should be ignored, you allow your site to serve cached pages more efficiently, improving performance and reducing unnecessary server load.
With just a few simple adjustments and mindful parameter selection, you can ensure faster page delivery while maintaining a stable and reliable site.
---
# How to Apply Bulk NGINX Customization Across Multiple Sites in xCloud? - xCloud
> Learn how to use bulk NGINX customization in xCloud to push configs to multiple sites at once and simplify server management.
Managing NGINX configurations across multiple sites can be time-consuming, especially when you need to apply the same custom config to dozens of sites on a single server. Normally, you’d have to visit each site’s settings individually, paste the same snippet, and repeat the process over and over.
xCloud’s Bulk NGINX Customization feature eliminates that repetitive work. It lets you select a configuration – whether from a ready-made template or your own custom snippet and push it to multiple sites in a single operation.
Follow this to apply bulk NGINX customization for your sites easily with xCloud.
## **Prerequisites** [#](/docs/how-to-apply-bulk-nginx-customization/)
- Your server must be running the NGINX stack (not OpenLiteSpeed). The Bulk NGINX Customization option is not available on OLS servers.
- Your server must have at least one provisioned site.
- You must be the server owner or have the appropriate team role to manage server settings.
⚠️ Bulk NGINX Customization processes sites in the background. For servers with many sites, changes may take a few minutes to apply across all selected sites.
## **Step 1: Open Bulk NGINX Customization** [#](/docs/how-to-apply-bulk-nginx-customization/)
From your xCloud dashboard, navigate to your server. In the left sidebar, go to **‘Management → Nginx Customization**.
Next, click on the ‘Add Bulk Config’ option to create a new NGINX config.
## **Step 2: Choose a Configuration Type** [#](/docs/how-to-apply-bulk-nginx-customization/)
Next, a pop-up will appear. Here, you need to configure a Custom NGINX. If you are not sure how to create a custom NGINX config, then read this documentation:
👉 [**How To Configure Custom NGINX In xCloud?**](/docs/configure-custom-nginx-xcloud/)
Once you select a type or template, the config snippet appears in the code editor below the dropdowns. You can review it as-is or make custom edits directly in the editor before applying.
## **Step 3: Select the Sites to Apply To** [#](/docs/how-to-apply-bulk-nginx-customization/)
The site selection table lists all sites on the server. Use the search bar to filter by site name or domain, or use the Select All checkbox to select every site at once.
For WordPress-only templates, the list automatically filters to show only WordPress sites.
💡 Sites that already have a custom NGINX config will show an “Overwrite” indicator. Applying a new config to these sites will replace their existing configuration.
## **Step 4: Apply the Configuration** [#](/docs/how-to-apply-bulk-nginx-customization/)
Before applying to all sites, it’s strongly recommended to test your config. Click **‘Run & Debug,’** then click **‘Apply’** to Selected Sites, and the NGINX configuration will start working on the selected sites. Afterward, your newly created Custom NGINX config will be displayed under **‘Site Name,’ ‘Type,’ and ‘Custom Configs’** in the dashboard.
Bulk NGINX Customization saves you from the tedious task of configuring each site individually. By applying a single config across all the sites that need it, you reduce both the time spent and the risk of inconsistent configurations between sites.
Just remember to use the Run & Debug option before applying to catch any issues early, and keep an eye on the overwrite indicators so you don’t accidentally replace a site’s existing config. If anything goes wrong after applying, you can always roll back by editing the config at the individual site level and reloading NGINX.
Still stuck? Contact our **[Support team](https://support.xcloud.host/).**
---
# How to Cancel xCloud Subscription? - xCloud
> Cancel xCloud subscription easily by deleting your server. Keep your data safe with a backup before deletion.
Want to cancel **[xCloud](/)** subscription? Just delete your server to cancel your xCloud subscription. If you would like to keep your data for future use, we recommend having a backup before deleting your server.
_**Note**: If you have multiple servers, deleting one server will only cancel billing related to that server in your subscription. Also once deleted, your server and its data will be permanently removed._
Need further assistance? Our [**support team**](https://support.xcloud.host/) is here to help with any questions or concerns.
---
# How to Change MySQL Max Connection via xCloud? - xCloud
> Learn how to change MySQL max connections on your xCloud server. Follow simple steps to optimize performance and handle heavy traffic.
[**xCloud**](/) lets you optimize your server’s performance and handle increased traffic by adjusting the max connection parameter in the **[MySQL](https://dev.mysql.com/doc/refman/8.4/en/option-files.html)** configuration file.
## **Steps to Change MySQL Max Connection via xCloud** [#](/docs/how-to-change-mysql-max-connection-via-xcloud/)
We will be using the command line to change MySQL Max Connection. Follow the steps below to increase the maximum connections MySQL allows on your xCloud server using the terminal.
### **Step 1: Access MySQL Configuration File** [#](/docs/how-to-change-mysql-max-connection-via-xcloud/)
Open the command terminal and run this command to edit MySQL config file:
**sudo nano /etc/mysql/mysql.conf.d/mysqld.cnf**
### **Step 2: Modify Max Connection Parameter** [#](/docs/how-to-change-mysql-max-connection-via-xcloud/)
In the MySQL configuration file in the nano text editor add these two lines at the end of the file as shown below if not exist (Values are based on preference):
**max\_allowed\_packet = 64M**
**max\_connections = 200**
### **Step 3: Restart MySQL** [#](/docs/how-to-change-mysql-max-connection-via-xcloud/)
Restart MySQL by running this: **sudo systemctl restart mysql** to ensure that the MySQL server is operating correctly with the new max\_connection value.
Following the steps you will have successfully increased the maximum connections allowed by MySQL on your xCloud server. This adjustment can significantly enhance your server’s performance and capacity to handle demanding workloads.
This is how you can easily change MySQL max connection via xCloud.
Still stuck! Contact our [**support team**](https://support.xcloud.host/) for assistance in detail with your queries.
---
# How to Change Node Version with xCloud - xCloud
> Learn how to switch Node versions on xCloud for smooth app deployment and development. Quick and simple guide.
Maintaining the appropriate Node.js version is crucial when deploying and developing applications on xCloud. Different projects may rely on specific Node versions, and ensuring alignment can prevent bugs, build errors, and runtime issues.
To change the Node version with xCloud, go to your server, then **‘Manage’ → ‘Node Configuration’**. From here, choose your preferred node version and click on the **‘Save’** button.
And that’s it. This is how easily you can change the node version with xCloud for your server.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How To Change The Primary Domain Of A Site? - xCloud
> Here is a simple guide to change your primary domain easily with xCloud.
The primary domain is the main and most important web address for a website. It’s like the home address for your site on the internet. When people want to visit your website, they use this domain to find and access it. Think of it as your website’s main location on the web.
With **[xCloud](/)**, you can change the main domain of your site if needed. All you need to do is to follow the simple steps below.
## **Steps To Change The Primary Domain Of Your Site?** [#](/docs/how-to-change-the-primary-domain-of-a-site/)
Go through the simple step-by-step guide below to easily change your domain of a site in xCloud.
### **Step 1: Log In To Your xCloud Dashboard** [#](/docs/how-to-change-the-primary-domain-of-a-site/)
From your xCloud dashboard select the site you want to change the primary domain for or go to the ‘**All Sites’** tab and click on the site to change the domain name.
### **Step 2: Change The Domain** [#](/docs/how-to-change-the-primary-domain-of-a-site/)
Go to the **‘Domain’** tab now. To change the primary domain, click on the **‘Change’** button.
### **Step 3: Verify Your New Domain** [#](/docs/how-to-change-the-primary-domain-of-a-site/)
Now enter your new domain name in the **‘Primary Domain’** field and hit the **‘Save’** button. After that, click on **‘Verify My DNS’** to verify your new domain.
Thus, you can easily change the domain of a site. Getting stuck? Feel free to **[contact our support team](/contact/)** for further assistance.
---
# How To Claim Your Free MailBox On xCloud - xCloud
> Learn how to claim and configure your free xCloud Mailbox add-on. Create a custom business email address on your domain in minutes directly from the xCloud dashboard.
Setting up a professional email mailbox for your website doesn’t have to be complicated or expensive. With xCloud Managed servers, every user gets access to a free mailbox add-on that can be configured in just a few simple steps.
Follow the process of claiming and setting up your free mailbox directly from your xCloud dashboard.
## Step 1: Go To Your Site [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Log in to the xCloud dashboard and go to Sites. Open the site that is hosted on an xCloud Managed server. From the dashboard, click Email Config → Mailbox. Then, click the Get Mailbox Add-on button.
You can also click the Get It Free button from the banner displayed on your xCloud Managed Server site.
Enter the Email address and Password you want to use for the new mailbox in the designated fields.
Then select the free Mailbox plan and click the Pay button.
That’s all it takes — once you’ve selected the free plan and clicked Pay, your new mailbox will be ready to use. If you run into any issues during setup, reach out to the xCloud support team for assistance.
## xCloud Mailbox Add-on – Frequently Asked Questions (FAQs) [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
### How is xCloud Mailbox Addon billed? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
The billing is monthly, based on your chosen plan.You only pay for the plan you subscribe to. There are no hidden charges for aliases or forwarding.
### Can I create multiple mailboxes under one domain? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes, you can create multiple mailboxes as long as they’re within the same xCloud team.
You cannot use the same domain across different teams.
Example: If user@domain.com is in Team A, then admin@domain.com can’t be in Team B.
### Are aliases free to use? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. Creating and using email aliases is completely free and included with your Mailbox plan.
### Is there a limit on how many aliases I can have? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No, there is no limit to how many aliases you can create under a domain. An alias cannot have the same name as an existing mailbox, and aliases cannot forward to other aliases.
### What is email forwarding, and is it free? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Email forwarding automatically sends a copy of incoming mail from one address to another. Email forwarding is included for free. Each mailbox supports an unlimited number of email forwarding addresses.
### What if my domain verification fails? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Try the following:
- Double-check all DNS records
- If using Cloudflare, toggle ‘Auto Manage DNS’ OFF and then ON again
- Wait a few minutes and try verifying again.
### After logging in, if you see the white page, what do you do? [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Once you log in to your webmail page, if you encounter a blank white screen, it may be due to your ad blocker. Please ensure that you turn off your ad blocker, clear your cache, and then refresh the page.
### **Can I use xCloud Mailbox for transactional emails?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes, it is possible. SMTP is included with the mailbox and comes with a sending limit of 250 emails per day. However, for SMTP or transactional emails such as subscriber notifications, order confirmations, and marketing messages, we recommend using the xCloud Email Delivery Add-on for better reliability and performance.
### **What is a business email?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
A business email uses your own domain name as the address, like you@yourdomain.com. You use it for professional communication, and it makes your brand look more credible. You get your business name in the address, more control over security, and the ability to add more accounts as your team grows.
### **How is business email different from personal email?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
You use personal email to talk with friends and family, sign up for services, and manage social media. Business email handles professional communication and contacts. It comes with email aliases, group aliases, more storage, and features like migration support, an admin control panel, and team-level integrations.
### **What is email hosting?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Email hosting lets you send and receive emails using your own domain name. You get a professional address, more storage, and strong security and privacy controls. If you want full control over your business email without relying on free providers, email hosting gives you that.
### **How do I create a business email address with xCloud Mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
If you own a domain, connect it to xCloud Mailbox and set up your email in minutes. If you don’t have a domain, you can buy one, and create a Mailbox using that domain.
### **How much storage do I get with xCloud Mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
xCloud Mailbox has 5 plans, including a free tier. Storage ranges from 100 MB free plan to 80 GB and each plan includes different features. If you need more space later, you can add storage to your account at any time.
### **Can I create aliases and forwarding rules?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. You can create unlimited aliases and forwarding addresses per mailbox at no extra cost.
### **Which email protocols are supported?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
xCloud supports IMAP, POP3, and SMTP. You can set it up on Outlook, Thunderbird, Apple Mail, Gmail, iPhone, Android, and most other email clients.
### **Where is the email hosted? On my server or somewhere else?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Your email does not run on your server. xCloud partners with a mailbox provider who runs email on their own infrastructure with dedicated IP addresses. Your web server handles your sites. Your email runs on infrastructure built for reliable delivery.
### **Can I buy one large mailbox and put all my clients’ email accounts inside it?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No. Each email account has its own storage. If you need three addresses like support@yourdomain.com, sales@yourdomain.com, and contact@yourdomain.com, you buy three separate mailboxes. Each one gets its own plan and storage. This works the same way as Google Workspace and other email platforms. Plans go up to 80 GB per mailbox. If you need more, reach out to the team.
### **Can self-managed server users use xCloud Mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. Self Managed server users get the same plans, pricing, and features as everyone else on xCloud. The free mailbox plan is the only exception. It is limited to xCloud-managed server users. Self-managed server users can buy any paid plan with no feature restrictions.
### **Can I disable the AI features for my team or clients?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. You can turn AI features off at the domain level. If you manage mailboxes for clients or staff and don’t want them using AI suggestions, you control that setting.
### **Will the existing mailbox provider be removed? What happens if I don’t migrate?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
The existing provider is not going away right now. You can keep using it with no disruption. Migrating to the new provider gives you more features at the same price. xCloud built a migration tool to make the switch easy, and support can help if you need it. There is no deadline to migrate.
### **How do I claim my free mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Deploy your site on an xCloud managed server (xCloud or xCloud Provider). A “Claim Free Mailbox” banner shows up on your dashboard. Click it, follow the steps, and your free 100 MB mailbox is ready. Each domain on an xCloud managed server gets one free mailbox.
### **I am paying for email on my xCloud managed server. Will my existing mailbox become free?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No. The free mailbox applies to new mailboxes created on xCloud managed servers. Existing mailboxes are not eligible. You can migrate your existing mailboxes to the new provider using the built-in migration tool and keep paying the same price, with access to all the upgraded features.
### **I don’t see the “Claim Free Mailbox” banner. What should I check?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
A few things could be going on. Your site must run on an xCloud managed server. Hetzner, AWS, DigitalOcean, and other non-managed providers don’t qualify. The site needs to be in production, not staging. Your team may have used all its free mailbox slots (default cap is 10 per team). The domain may have a free mailbox assigned to it. Legacy mailboxes on the domain that haven’t been migrated will block the banner until migration is done. You or someone on your team may have dismissed the banner (dismissal is per domain). White-label tenants don’t see the mailbox addon.
### **I have legacy mailboxes on my domain. Can I still get a free mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes, after you finish migration. Use the migration wizard to move all your legacy mailboxes to the new provider. Once that is done, the free mailbox banner shows up on every site that shares that base domain. You don’t need to contact support. It happens on its own.
### **If I create a new site on my xCloud managed server, does it qualify for a free mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. Any site on an xCloud managed server qualifies, including new ones. The domain can’t have claimed a free mailbox before.
### **Is the free mailbox available on xCloud reseller managed servers?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No. The mailbox addon is not available on the xCloud reseller program right now. It works on standard xCloud managed servers.
### **I have a lifetime deal (LTD). Am I eligible for a free mailbox?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Free Mailbox is available for both xCloud Managed Servers and xCloud Provider Servers.
If you are using an xCloud Provider Server, you are eligible to claim the free Mailbox offer.
However, this offer is not available for self-managed servers. In other words, if you are managing your own server instead of using an xCloud Provider Server, you will not be able to claim the free Mailbox.
### 20\. **What happens to my free mailbox if I move my site off xCloud?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Your free mailbox keeps working. It won’t shut down right away. An ineligibility period starts, and you get notification emails on Day 0, 7, 14, and 30. An in-app banner gives you two options: move your site back to xCloud, or upgrade to a paid mailbox plan. Auto-suspension is not active in the current version.
### 21\. **I brought my site back to xCloud. Will the ineligibility warning go away?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. The system picks up the change within seconds, closes the ineligibility episode, and removes the warning banner on the next page load.
### 22\. I deleted my free mailbox but my counter still shows it is at the limit. [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
The counter should update right when you delete a mailbox. Refresh the mailbox addons page. If the count is still wrong after refreshing, contact our support team so the team can look into it.
### 23\. **Can I have more than 10 free mailboxes on my team?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. The default cap is 10 per team. Contact support to request a higher limit.
### 24\. **I am getting a “Free plan limit reached” error but I only have a couple of free mailboxes.** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Your team may have a custom limit set lower than the default. A recently deleted mailbox might still be processing. Contact our support team so they can check your team’s settings and fix the issue.
### 25\. **I have a paid mailbox on my domain. Can I add a free one too?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
Yes. Paid and free mailboxes can exist on the same domain as long as everything runs on the default provider. There is no restriction on combining both plan types.
### 26\. **Can I claim a free mailbox through the API?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No. Free mailbox claims go through the dashboard with a valid site context. API-based claims are not available in this version.
### 27\. **The migration wizard won’t let me cancel. Is this a bug?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No. Once any mailbox in the migration reaches the DNS-verified stage, email is flowing to the new system. Canceling at that point would lose the received mail. You need to finish the migration to keep everything intact.
### **28\. Is it possible to downgrade my mailbox plan?** [#](/docs/how-to-claim-your-free-mailbox-on-xcloud/)
No, downgrading your mailbox plan is not possible. Once you have selected and activated a plan, it cannot be changed to a lower tier. If you have specific concerns about your current plan, we recommend reaching out to the xCloud support team for guidance.
It’s important to note that the MailBox Addon is not suitable for handling mass-volume transactional emails. For such needs, we recommend using our SMTP Email Delivery Addon.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How to Clone a Laravel App with xCloud - xCloud
> Learn how to clone a Laravel app with xCloud in a few easy steps, from selecting a destination server to configuring SSL, database, and your deploy script.
With [**xCloud**](/), you can quickly clone a Laravel app into a new, ready-to-use copy.
Whether you need a staging environment for testing, want to move an app to another server or create a safe copy before making changes, the Clone Site feature makes the process simple.
It copies your application files and database automatically. It also configures SSL, Nginx, and deployment settings for the new site. Follow this guide to get started.
## **Prerequisites** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Before you begin cloning your Laravel app, make sure you have the following in place:
- An active **xCloud** account with access to the [**xCloud dashboard**](https://app.xcloud.host/)**.**
- An existing Laravel app already deployed and running on xCloud (this is the site you will clone).
- A destination server available in your account where the cloned app will live. You can clone onto the same server or a different one.
## **How to Clone A Laravel App in xCloud** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Cloning a Laravel app with xCloud involves a few easy steps. The guide below walks you through the complete flow, from locating your site to watching the clone build in real time. Follow the steps below to clone your Laravel app.
### **Step 1: Open Your Laravel App** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
First, log into your xCloud account. From the left navigation menu, click on ‘**Sites**‘ to open the ‘**All Sites**‘ page. Locate the Laravel app you want to clone, then click on its name to open it.
### **Step 2: Initiate the Clone Site Action** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Once the ‘**Site Overview**‘ page loads, look at the top-right corner of the screen. Click on the ‘**Actions**‘ dropdown button to reveal the available site operations.
From the dropdown menu that appears, click on the ‘**Clone Site**‘ option. This launches the five-step cloning wizard.
### **Step 3: Select Destination Server** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
You are now on the ‘**Destination**‘ tab of the wizard, which is **Step 1 of 5**. Here, you choose the server where your cloned Laravel app will be created.
You can keep the server that is already selected, or pick a different one from the list to clone onto another server. After selecting your destination server, click on ‘**Next**‘ to continue.
### **Step 4: Set Up Domains, DNS & SSL** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
On the ‘**Domains**‘ tab (**Step 2 of 5**), titled ‘**DNS & SSL For (xCloud Managed)**‘, you decide how the cloned app will be accessed. You will get two options:
#### **Demo Site** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Choose ‘**Demo Site**‘ to create a clone using a temporary xCloud test domain. This is ideal when you simply want to test or refine the cloned app before taking it live.
#### **Migrate into a New Domain** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Choose ‘**Migrate into a New Domain**‘ to point a live domain at your cloned app right away. After selecting this option, enter your ‘**Domain Name**‘ in the field provided. If you need to serve the app on more than one domain, enter an ‘**Additional Domain (Optional)**‘ and click ‘**Add Domain**‘. You may also tick the ‘**Add DNS and SSL Certificate on Cloudflare (Optional)**‘ checkbox if you manage your DNS through Cloudflare.
Next, scroll down to point your domain to the server. xCloud displays the DNS record you need to add, including the ‘**Record**‘ type (**A**) and the target value, each with a convenient ‘**Copy**‘ button. After adding the record at your DNS provider, click ‘**Verify My DNS**‘ to confirm the connection.
To keep your Laravel app secure, make sure the ‘**HTTPS Is Enabled**‘ toggle is switched on. Once enabled, you will get two SSL options to choose from:
- ‘**Use free SSL certificate issued & managed by xCloud**‘, the recommended option, where xCloud issues and auto-renews the certificate for you.
- ‘**I will provide the certificate and manage it myself**‘, choose this if you prefer to upload and maintain your own certificate.
Select the option that suits your needs, then click ‘**Next**‘.
### **Step 5: Configure the Database Connection** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
On the ‘**Database**‘ tab (**Step 3 of 5**), titled ‘**Configuration & Database Connection**‘, you set up the database for your cloned Laravel app. Under ‘**Database Management**‘, you will get two options:
#### **Create Database In Server** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Select ‘**Create Database In Server**‘ to let xCloud automatically provision a new database on the destination server. xCloud auto-fills the ‘**Database Name**‘, ‘**Database Username**‘, and ‘**Database Password**‘ for you. You can keep these auto-generated credentials or modify them according to your choice.
#### **Add Your Own Database** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
Select ‘**Add Your Own Database**‘ if you would rather connect an existing database that is hosted elsewhere. In that case, provide the required connection details and make sure the configuration is correct.
After choosing an option and confirming the credentials, click ‘**Next**‘.
### **Step 6: Adjust Settings & Deploy Script** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
On the ‘**Settings**‘ tab (**Step 4 of 5**), titled ‘**Settings & Configurations**‘, you fine-tune how your cloned Laravel app runs.
- **PHP Version**: Choose the PHP version for the cloned app from the dropdown (set to **8.3** in this example). Matching the PHP version of your original app is recommended for compatibility.
- **Site User**: The system user that will own the cloned app’s files, shown here for reference.
- **Deploy Script (Optional)**: The commands xCloud runs automatically after the clone is created. For a Laravel app, the default script installs dependencies, runs database migrations and clears cached configuration:
You can keep the default deploy script or edit it to match your app’s specific build steps. When you are satisfied with the settings, click ‘**Next**‘.
### **Step 7: Confirm the Clone Details** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
On the ‘**Confirm**‘ tab (**Step 5 of 5**), titled ‘**Confirm Details**‘, xCloud presents a complete summary of your selections so you can review everything before the clone begins. The summary includes:
- **Staging Url**: The address where the cloned app will be available.
- **Old Domain**: The source app you are cloning from.
- **Server**: The destination server (and whether it is the same server).
- **HTTPS**: Confirms SSL is enabled.
- **PHP Version**: The PHP version applied to the clone.
- **Database Type**, **Database Name**, **Database User** and **Site User**: The database and ownership details.
If anything needs changing, click the ‘**Edit**‘ link beside the relevant row to jump back to that step. Once every detail is correct, click the ‘**Start**‘ button to begin cloning.
### **Step 8: Start the Cloning Process** [#](/docs/how-to-clone-a-laravel-app-with-xcloud/)
After you click ‘**Start**‘, the cloning process begins immediately, and a live progress screen appears. You can watch the overall completion percentage at the top while xCloud works through each stage of the clone in real time.
The process moves through three phases, broken into individual tasks such as:
- **Checking and Verifying**: Verifying server storage and connection.
- **Installing Apps**: installing PHP 8.3, syncing PHP settings, installing the database, installing required services, and cloning the site.
- **Configuring**: Configuring SSL and HTTPS, cloning backup and security settings, configuring Nginx, running the deploy script, and installing monitoring.
There is no need to refresh or interact with the page; xCloud completes each task automatically. Once the progress screen reaches 100%, your cloned app is ready to use.
**Note:** _Cloning time depends on the size of your app and database. Larger Laravel apps with bigger databases will take longer to finish._
That’s it! You have successfully cloned a Laravel app with **xCloud**. You can visit it at the staging or live URL you configured, then continue refining it, point a custom domain to it or push it live whenever you are ready.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Clone Full Server With xCloud? - xCloud
> Learn how to clone full sever with xCLoud and migrate your websites including configurations to the new or any existing server easily.
Full Server cloning allows you to create an exact copy of your existing server setup, including all applications and configurations. It is useful when you need to switch to a different cloud provider, move to a new server region, or test a different server type. You can also use it to downsize to a smaller server or perform load testing.
With xCloud, you can easily clone full server and modify certain configurations, such as switching the database(MySQL to MariaDB) or server type (NGINX to OpenLiteSpeed). Follow the step-by-step process to clone full server and migrate to another server.
## **Step 1: Access to Your Servers** [#](/docs/how-to-clone-full-server-with-xcloud/)
First, you need to **[create a second server](/docs/how-to-create-a-site-with-xcloud/)** to clone your existing server. Once you are done with it, go to your source server (The server that you want to clone) and click the clone server option from the action menu.
## **Step 2: Choose Your Destination Server** [#](/docs/how-to-clone-full-server-with-xcloud/)
Now choose your destination server to clone from the existing server and click on the **‘Next’** button.
## **Step 3: Select and Migrate Website** [#](/docs/how-to-clone-full-server-with-xcloud/)
Here you need to select websites you want to migrate from the available sites. Once your websites are fetched, you can pick from the list of available sites. Select as per your preference. it could be one or all of them.
**Note:** _Cloning is currently supported only for WordPress sites. It will not work for other types of websites at this time._
## **Step 4: Set Domain for Migration** [#](/docs/how-to-clone-full-server-with-xcloud/)
At this stage of cloning your server, you can set the status of the site whether it would be a ‘**Demo Site or Live Site**‘ scan through the list, and click on, ‘**Next**‘
**Note:** You can select the Live Site option, and for that, you need to point your domain to the new server. For further insights dive into the below documentation for more details.
- [**How To Setup DNS Record In xCloud Server?**](/docs/how-to-setup-dns-record-in-xcloud-server/)
- [**With xCloud, Integrate Cloudflare For DNS Management**](/docs/using-xcloud-with-cloudflare-for-dns-management/)
## **Step 5: Confirm Migration** [#](/docs/how-to-clone-full-server-with-xcloud/)
Now carefully check out all the migration details you have been working on. Once you are done and all the information is accurate, click on the ‘**Start**‘ button to start the migration procedure and wait for the procedure to complete.
## **Step 6: Final Overview** [#](/docs/how-to-clone-full-server-with-xcloud/)
Once your server is up and done cloning, you will get to see the status, **‘View Site**’ on the screen. Click on it and get the cloned server ready.
That is how you can **clone the server** from the existing source server in xCloud very easily and do the whole process a in few clicks.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Configure a Business Mail account on Phone Using Gmail - xCloud
> Learn how to quickly configure your business email on your phone using Gmail for seamless communication.
Accessing your email on a mobile device has become a standard necessity for both personal and professional communication. Whether you’re managing a business or staying connected on the move, configuring your email account using a reliable client like Gmail ensures smooth and secure communication.
Follow this guide to learn how to configure a business mail account on Phone using Gmail:
## **Step 1: Gather Your IMAP Information** [#](/docs/how-to-configure-a-business-mail-account-on-phone-using-gmail/)
First, go to your MailBox, choose your email, and navigate to the **‘IMAP’** tab from the menu. Here, you will find the credentials needed to set up your email client with Apple Mail.
> **Email:** hi@yoursite.com
>
> **Password**: \*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Incoming Server Hostname:** imap.eu.appsuite.cloud
>
> **Incoming Server Username**: hi@yoursite.com
>
> **Incoming Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Outgoing Mail Server Hostname:** pop.eu.appsuite.cloud
>
> **Outgoing Server Username:** hi@yoursite.com
>
> **Outgoing Server Password:** \*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> **Port:** 993
>
> **Encryption:** TLS
### **Step 2: Choose Gmail (IMAP) from the Accounts** [#](/docs/how-to-configure-a-business-mail-account-on-phone-using-gmail/)
On your phone, go to **Accounts** and select **Gmail (IMAP)**.
Next, enter the **email address** and **password** of the account you want to connect.
Then, enter the **IMAP server information** you collected from the xCloud dashboard and click the **‘Next’** button.
Enter the ‘**Delivery email server hostname** in the designated field and click **‘Next’** again.
Review the account options and click **‘Next’** to proceed.
Once completed, your business email will be successfully connected to Gmail.
And that’s it, this is how easily, you can integrate your xCloud MailBox business email with Gmail and enjoy seamless access to your inbox.
---
# How To Easily Configure Firewall Management With xCloud Hosting - xCloud
> With xCloud, it's easy now to configure firewall management to maintain sheer security for your site.
If your virtual private server (VPS) isn’t set up right, it can be open to cyber attacks. Even with strong security from your hosting provider, it’s important to take extra steps to keep it safe. That’s where the firewall management comes in.
With xCloud hosting you can activate [**UFW (Uncomplicated Firewall)**](https://wiki.ubuntu.com/UncomplicatedFirewall) to regulate incoming and outgoing traffic with just a single click. Our easy dashboard allows you to configure firewall settings with ease, putting you in full control of your server’s security. This new feature helps block any harmful traffic trying to get into or out of your server. You can disable, delete, and create new firewall management rules with xCloud. xCloud utilizes UFW for WordPress-specific Firewall rules, enhancing security against unauthorized access and malicious attacks.
## **Step 1: Configure Firewall Management From Server Dashboard** [#](/docs/how-to-configure-firewall-management-in-xcloud/)
Now navigate to your All Server dashboard. From here, go to the **‘Security’** section from the sidebar menu. Under this menu, you’ll see an option labelled **‘Firewall Management’.** Click on that.
Here, you’ll see all your current Firewall rules. From this section, you can create new rules, delete existing ones, or disable rules as needed.
By default, we set up three rules to open specific ports:
- Port 22 for SSH.
- Port 80 for HTTP, and
- Port 443 for HTTPS
For security reasons, all other ports are automatically closed.
Add New Rule: To add a new rule, just click on **‘Add New Rule‘**. This will open up a form where you can fill in the details: **‘Rule Name’, ‘Port’, ‘IP Address’, ‘Protocol’,** and **‘Traffic options’**. Fill out these fields according to your needs, then click **‘Add Rule‘** to apply the new rule.
### **Disable & Enable Firewall Rule** [#](/docs/how-to-configure-firewall-management-in-xcloud/)
By clicking this option, you’ll temporarily disable the rule. You can easily enable it again whenever you need to.
## **Delete Firewall Rule** [#](/docs/how-to-configure-firewall-management-in-xcloud/)
Choosing this option will permanently delete your firewall rule. Be sure to take the necessary precautions before proceeding with this action.
## **Firewall Rule Risk Warnings** [#](/docs/how-to-configure-firewall-management-in-xcloud/)
You won’t get locked out by accident anymore! xCloud now warns you before you add risky firewall rules, like blocking port 22 (SSH) or all IP addresses. You will see a clear warning and must confirm before saving any rule that might prevent you from accessing your server or the xCloud panel.
## **SSH Rule Deletion Warning** [#](/docs/how-to-configure-firewall-management-in-xcloud/)
If you try to delete the **SSH (Port 22)** rule, xCloud will show you a warning first. Deleting this rule can lock you out of your server and stop SSH access. You need to confirm before xCloud allows the deletion. This step helps prevent accidental disconnection from your server.
## **Give Permission To Configure Firewall Management** [#](/docs/how-to-configure-firewall-management-in-xcloud/)
If you want your team members to be able to set up firewall rules, just go to the team page and enable it there. To get started, log in or sign up for your **xCloud** account using your username and password. Once logged in, click on your account dropdown and select the ‘**Team**‘ page. There, you’ll see an option to tick the box for ‘**server:manage-firewall**‘. Don’t forget to save your settings after ticking the box.
[](https://xcloud.host/docs/how-to-configure-firewall-management-in-xcloud/image-66-2/)
This is how you can easily configure firewall management with xCloud.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Configure Integration with WhatsApp In xCloud Hosting? - xCloud
> Following easy steps you can configure integration with WhatsApp in xCloud hosting & never miss a notifications of your server, site activities, more.
[**xCloud**](/) brings another handy integration **“Integration with WhatsApp”** to its feature basket. With a few clicks, you can now integrate WhatsApp into xCloud hosting to streamline your notification strategy. By integrating with WhatsApp, you can easily get your server, site notifications along with team accounts and actions directly into your WhatsApp.
Follow the step-by-step guide to learn how to integrate WhatsApp in xCloud hosting to enhance team coordination and efficiency.
## **Step 1: Add New Notification** [#](/docs/how-to-configure-integration-with-whatsapp/)
After logging in to your xCloud account, navigate to **Integrations → Notification** from the dashboard. Now click on ‘**Add New Notification** to integrate WhatsApp into xCloud hosting.
## **Step 2: Integration With WhatsApp In xCloud** [#](/docs/how-to-configure-integration-with-whatsapp/)
Now, choose **‘WhatsApp’** from the lists of integrations that xCloud offers. Once you click, the phone number field will pop up – make sure to put your number with the country code. The moment you’re done with filling up the number, click on **‘Authorize on WhatsApp.**’
Now, under the **‘List of Notifications’**, you can see your integrated WhatsApp number with its Type, Status, and Action. Under Action, you can easily disconnect your WhatsApp from xCloud – all you need to do is click **‘Disconnect.’**
## **Step 3: Choose The Notifications You Want To Get** [#](/docs/how-to-configure-integration-with-whatsapp/)
To set which notification you would like to get in your WhatsApp, navigate to **Team Settings → Notifications**. Now mark the WhatsApp option for which you want to get notifications **‘Server’**, **‘Site’**, **‘Other’** & click on ‘**Save Changes**.’’
This is how you can easily configure WhatsApp with xCloud hosting & get your server, site notifications along with team accounts and actions directly into your WhatsApp.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Configure PHP Settings of Your Site - xCloud
> Configure PHP settings in xCloud with site-level PHP controls. Improve performance and stability without editing server config files.
PHP settings control how your site runs and handles requests. The right configuration helps improve performance, stability, and compatibility with themes, plugins, or custom code. With xCloud, you can manage PHP and PHP-FPM settings for each site separately, without touching the server or editing config files.
Follow the guide to find these settings and how to update them safely:
## Step 1: Go to Your Site [#](/docs/how-to-configure-php-settings/)
With xCloud, you can also manage your site’s PHP settings separately. Just go to your site, navigate to the ‘Site Settings’ option from the sidebar.
## Step 2: Go To PHP Configuration [#](/docs/how-to-configure-php-settings/)
You can manage your PHP settings for these sites easily. Next, go to the ‘PHP Configurations’ option and set the ‘PHP Version’ from the dropdown menu according to your preferences.
_Note: If you change the PHP version for a site, xCloud automatically resets the PHP and PHP-FPM configuration values to their default settings for that PHP version._
Here you will get an option ‘Manage’, click on it to access ‘PHP Configuration’, ‘FPM Configuration’ and ‘OPcache Configurations’ options.
## Step 3: Manage PHP Configurations [#](/docs/how-to-configure-php-settings/)
First, choose ‘PHP Configuration’, in the pop-up menu, you will get a few options to get the following options that can be modified:
1. Max Execution Time: The maximum time a PHP script can run before it stops.
2. Max Input Time: Maximum time PHP waits to receive input data.
3. Memory Limit: Maximum amount of memory a PHP script can use.
4. Max File Upload Size: Maximum size allowed for uploaded files.
5. Max Input Vars: Maximum number of input variables PHP can accept in one request.
6. Post Max Size: Maximum size of data allowed in POST requests.
7. Session GC Maxlifetime: Time PHP keeps session data before deleting inactive sessions.
If you are not sure about the values, you can use the ‘Auto Tune’ option. Click on the button, and configuration values have been automatically calculated based on your server’s available RAM. Please review the suggested values below and click Save Settings to apply them.
Now, if you want to customise the options, go to each option and enter your preferred values in the dedicated field and click on the ‘Save Changes’ button.
## Step 3: Manage FPM Configurations [#](/docs/how-to-configure-php-settings/)
First, choose ‘Manage FPM Configurations’, and on the pop-up menu, you will get a few options.to get the following options that can be modified:
1. PHP Version: PHP version used to run the site.
2. Process Manager Type: Process manager mode used by PHP-FPM to handle requests.
3. PM Start Servers: Number of PHP worker processes started when PHP-FPM launches.
4. PM Min Spare Servers: Minimum number of idle PHP worker processes kept ready.
5. PM Max Spare Servers: Maximum number of idle PHP worker processes allowed.
6. PM Max Children: Maximum number of PHP worker processes that can run at the same time.
7. PM Max Requests: Number of requests a PHP worker handles before restarting.
_Note: PHP-FPM is only available in NGINX right now._
If you are not sure about the values, you can use the ‘Auto Tune’ option. Click on the button, and configuration values have been automatically calculated based on your server’s available RAM. Please review the suggested values below and click **Save Settings** to apply them.
Now, if you want to customise the options, go to each option and enter your preferred values in the dedicated field and click on the ‘Save Changes’ button.
## Step 3: Manage OPCache Configurations [#](/docs/how-to-configure-php-settings/)
First, choose ‘OPcache Configurations’, in the pop-up menu, you will get a few options to get the following options that can be modified:
1. Memory Consumption
2. Interned Strings Buffer
3. Revalidate Frequency
4. Max Accelerated Files
If you are not sure about the values, you can use the ‘Auto Tune’ option. Click on the button, and configuration values have been automatically calculated based on your server’s available RAM. Please review the suggested values below and click **Save Settings** to apply them.
Now, if you want to customise the options, go to each option and enter your preferred values in the dedicated field and click on the ‘Save Changes’ button.
And that’s it this is how easily you can configure PHP settings to help your site run faster and more reliably. xCloud makes these changes simple by offering site-level controls without server access or manual configuration. Always apply changes gradually and test your site after updates to avoid performance or stability issues.
Still stuck? Feel free to reach out to our [**support team**](http://support.xcloud.host/).
---
# How To Configure SFTP Access For Your Site - xCloud
> Follow this guide to configure SFTP access in xCloud with some simple steps.
Using SFTP for secure file management on your [**xCloud**](/) servers is crucial for keeping your data safe. It encrypts your files during transfer, unlike standard FTP, which leaves them vulnerable.
To connect via SFTP using SFTP clients like Filezilla or Transmit, use the site user with SSH and SFTP access. You can authenticate with SSH keys or a password, but SSH keys are recommended for better security.
To set up SSH key authentication for your xCloud site user, create an SSH key pair on your local machine and link it to your site user. Make sure to follow the documentation for detailed instructions and add the SSH key specifically to the site user.
1. [How to Generate & Add SSH Keys in xCloud](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
2. [Understanding Sudo Users & Site Users In xCloud](/docs/usudo-users-and-site-users-in-xcloud/)
Once your SSH key is added to the site user, you’re all set to configure your FTP application for secure file management. You can also select the password method.
## **Step 1: Collect SFTP Credentials from Site Dashboard** [#](/docs/how-to-configure-sftp-access/)
Go to xCloud dashboard, and click on your site to collect your SFTP credentials. Then, navigate to **Access Details → SSH/SFTP** from the site dashboard to collect SFTP access.
## **Step 2: Configure SFTP Access By Choosing A Live Server & Cloud Storage Browser** [#](/docs/how-to-configure-sftp-access/)
Now you can use **Transmit** as your file transfer application. Transmit provides a graphical interface that allows you to securely transfer files between your local computer and remote servers using the SFTP protocol.
Transmit provides a reliable and secure way to transfer files over the SFTP protocol, ensuring the data’s confidentiality and integrity.
Now you have to fill up your necessary credentials and click on the connect to access your server. After connecting just find the **‘Files’** shortcut from the menu and you will be able to retrieve your server files and configure SFTP access.
## **Secure File Transfer Protocol(SFTP) With FileZilla** [#](/docs/how-to-configure-sftp-access/)
**[FileZilla](https://filezilla-project.org/)** is a user-friendly software that allows you to use SFTP for secure file transfers. With FileZilla, you can easily connect to remote servers, navigate directories, and transfer files securely, ensuring that your data remains protected during the transfer process. It provides a simple and reliable solution for securely managing file transfers over SFTP.
You will get your host key. Click on ‘Ok’ and you are good to go.
Copy the site path from xCloud to access your site files.
And paste it to Filezilla to manage your files.
## **How to Do SSH Authentication With Public Key** [#](/docs/how-to-configure-sftp-access/)
You can even use **‘Public Key’** to authenticate the SSH Authentication from xCloud dashboard.
### **Step 1: Add SSH Key Using Public key** [#](/docs/how-to-configure-sftp-access/)
To add the Public SSH Key, click on the **‘Public Key’** button and press on the **‘Add SSH Key’**, a popup will appear on the screen.
### **Step 2: Access Using an SSH key** [#](/docs/how-to-configure-sftp-access/)
Go to the FileZilla dashboard and **‘Add a New Site’** and select the Protocol from the **‘SFTP- SSH File Transfer Protocol’** from the menu. Enter the **Host** and **Port** under the Protocol menu. Change the Logon Type to **‘Key File’**, **‘Add User’** and **‘Key File’** and click on the connect button.
This way you will be able to configure and connect the SFTP with your xCloud server.
## **Secure File Transfer Protocol(SFTP) With Cyberduck** [#](/docs/how-to-configure-sftp-access/)
Cyberduck is a user-friendly software that facilitates SFTP connections. With Cyberduck, you can easily connect to remote servers, browse directories, and transfer files securely. Its intuitive interface and robust security measures ensure that your files are safely transferred over SFTP, providing a seamless and secure file transfer experience.
After adding the necessary credentials you will easily configure SFTP with Cyberduck.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Configure SSH Lockdown And restrict SSH Access Only To Trusted IPs - xCloud
> Learn how to secure your server by SSH lockdown and whitelisting trusted IPs using xCloud’s firewall management system.
Securing SSH access is a critical step in protecting your server from unauthorized access. By default, SSH is often accessible from any IP address, which can expose the server to brute-force attacks and other security risks.
The SSH Lockdown & Firewall IP Whitelisting System is a security feature designed to significantly reduce unauthorized access to servers by restricting SSH (port 22) access to a predefined set of trusted IP addresses only.
This SSH lockdown approach removes the commonly used but insecure “SSH (22) – Any” firewall rule and replaces it with a strict IP-based access control model. Only xCloud infrastructure and user-approved IP addresses are allowed to initiate SSH connections.
Follow the process below to enable SSH lockdown safely, remove the default SSH firewall rule, and restrict access to approved IP addresses without losing access to your server.
## **Step 1: Navigate to Your Server** [#](/docs/how-to-configure-ssh-lockdown/)
Begin by logging in to your server dashboard and selecting the server you want to secure. Once inside the server panel, navigate to **‘Security’**, then open **‘Firewall Management’**.
Here you will see all active firewall rules applied to your server, including the default SSH rule that permits access from any IP address.
## **Step 2: Delete the SSH Firewall Rule** [#](/docs/how-to-configure-ssh-lockdown/)
In the **Firewall Management** page, locate the firewall rule labeled **SSH**, which allows inbound traffic on port 22 from all IP addresses. Click the **Delete** icon next to this rule to begin the SSH lockdown process.
At this stage, the system will show a confirmation popup containing several critical warnings to ensure you understand the impact of enabling SSH lockdown.
At this stage, the system will show a confirmation popup containing several critical warnings. These warnings are designed to ensure that you fully understand the impact of deleting the SSH rule.
## **Step 3: Review and Confirm Safety Warnings** [#](/docs/how-to-configure-ssh-lockdown/)
When attempting to delete the SSH firewall rule, you will be presented with important system warnings explaining that removing this rule will immediately revoke SSH access for all IP addresses.
To prevent accidental lockouts, the platform requires explicit confirmation of safety measures before allowing the SSH rule to be deleted. As part of this process:
- Infrastructure IP addresses will be automatically whitelisted to ensure that monitoring, backups, and emergency recovery services remain functional.
- xCloud infrastructure IP addresses will be automatically whitelisted, as they are mandatory to ensure that monitoring, backups, and emergency recovery services remain functional.
- You can optionally whitelist your current public IP address to retain SSH access after enabling SSH lockdown. This option is user-controlled and can be enabled or disabled based on your preference. If selected, your public IP will be added to the whitelist so you retain SSH access after the rule is removed. If not selected, SSH access from your current IP will also be revoked.
You must carefully read the warnings and acknowledge them by checking the required confirmation boxes.
The SSH firewall rule cannot be deleted until all required safety confirmations have been acknowledged. Once confirmed, the system will automatically apply SSH lockdown by whitelisting required infrastructure IPs along with your selected IPs.
After reviewing all warnings and confirming the safeguards, proceed by selecting **“I Understand and Delete Anyway.”** The system will then remove the insecure SSH (port 22 – Any) firewall rule and immediately apply the new IP-based access restrictions.
> Note: To access the whitelisted IP addresses, you can also visit this [**_link_**](https://app.xcloud.host/ips).
Once the process is complete, SSH access to your server will be fully restricted. Only approved IP addresses will be able to initiate SSH connections.
## **Re-Enabling SSH Access (If Needed)** [#](/docs/how-to-configure-ssh-lockdown/)
To re-enable SSH access, navigate to the firewall dashboard and click **Add New Rule**. A popup window will appear where you need to enter **SSH** in the **Name** field and **22** in the **[SSH Port](/docs/how-to-update-ssh-port-in-xcloud/)** field.
In the ‘**IP Address**‘ field, you can specify a particular IP address to whitelist it, or leave the field blank to allow SSH access from all IP addresses. Next, set the ‘**Protocol’** to **‘TCP’** and configure ‘**Traffic**‘ as **‘Allow’**. Once all details are entered, click **‘Add Rule’** to apply the changes and restore SSH access to your server.
And that’s it. With these steps, you can easily restrict SSH access to approved IP addresses only or later re-enable, improving server security while maintaining uninterrupted access.
Still stuck? Feel free to reach out to our [**support team**](http://hidden-hamlet-226309.wp1.sh/support).
---
# What Is A Cron Job And How To Configure xCloud Cron Job? - xCloud
> xCloud cron job allows publishing scheduled content and assures scheduled tasks like content publishing occur reliably at specified intervals.
With **[xCloud](/)**, you can easily manage scheduled tasks with Cron Job. xCloud aims to simplify the process of hosting and managing WordPress sites. It allows users to focus on building great websites without worrying about the missed publishing content. Now let’s have a look below to learn more about Cron Job.
## **What Is A Cron Job And Why Is It Important?** [#](/docs/how-to-configure-xcloud-cron-job/)
A cron job is a scheduled task on Unix-like operating systems. It allows you to automate repetitive tasks by specifying when and how often certain commands or scripts should be executed. WordPress has a feature that simulates a cron job functionality within the WordPress environment. It handles scheduled tasks like publishing posts, checking for updates, and other time-based actions.
However, it relies on website visits to trigger these tasks, which might not be ideal for high-traffic or infrequently visited sites. In that case, users can choose to replace it with a server-based cron job for more reliable scheduling. And here comes the xCloud cron job feature.
There is a difference between WP-Cron and xCloud Cron. WP-Cron manages time-based tasks in WordPress relying on site visitors. xCloud Cron does the same thing at the server level. Besides, it ensures scheduled tasks like post publishing, page living, etc occur reliably at specified intervals.
## **How To Configure xCloud Cron Job?** [#](/docs/how-to-configure-xcloud-cron-job/)
xCloud cron job does not depend on high traffic, it allows publishing scheduled content if there is no site visitor. Follow the below step to enable the xCloud cron job feature.
### **Select xCloud Cron Job** [#](/docs/how-to-configure-xcloud-cron-job/)
Go to xCloud Dashboard. From the dashboard, click on the ‘Settings’ tab. Here, you will find the WP-Cron and xCloud Cron. From here, select the xCloud Cron.
### **Set Cron Interval For Server** [#](/docs/how-to-configure-xcloud-cron-job/)
After selecting the xCloud Cron, you will get an option to set the cron interval for the server. From the dropdown, select the preferred interval.
That is how you can easily configure xCloud Cron Job.
What if you want to add custom cron jobs? In xCloud, that is possible too. To learn how to add a custom cron job in xCloud, the below documentation is for you.
- **[How To Add A Custom Cron Job In xCloud?](https://xcloud.host/docs/how-to-add-a-custom-cron-job-in-xcloud/)**
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How to Configure Zoho Mail With WordPress for Custom Domain Email - xCloud
> Learn how to integrate Zoho Mail with WordPress using FluentSMTP to send emails from your custom domain.
Integrating Zoho Mail with WordPress allows you to send and receive emails using your custom domain, improving professionalism and email deliverability. This setup ensures authenticated and reliable communication, reducing the risk of emails being marked as spam. By using Zoho Mail with WordPress, you can efficiently manage website email correspondence through Zoho’s secure infrastructure.
Follow the step-by-step process to set up Zoho Mail and configure it with the FluentSMTP plugin in WordPress for seamless email communication.
**_Note:_** _Before we continue, login to your_ [_Zoho mail website_](https://www.zoho.com/mail/)_. Or, If you haven’t sign up yet, make sure to sign up and choose a plan according to your needs._
## **Step 2: Add and Verify Your Domain** [#](/docs/how-to-configure-zoho-mail-with-wordpress-for-custom-domain-email/)
In the [**Zoho Mail Admin Console**](https://www.zoho.com/mail/help/adminconsole/overview.html), navigate to the ‘**Domains’** section and select **‘+Add’** button. Enter your domain name and proceed.
Zoho will provide DNS records (MX, TXT, CNAME) that you need to add to your domain’s DNS settings. Access your domain registrar’s DNS management panel and add the provided records. After adding the records, return to Zoho Mail and click **Verify** to confirm domain ownership.
**_Note:_** _DNS changes may take some time to propagate. It’s recommened to complete this step in advance to avoid delays._
## **Step 3: Create User Accounts and Custom Email Addresses** [#](/docs/how-to-configure-zoho-mail-with-wordpress-for-custom-domain-email/)
Once your domain is verified, go to the **User Details** section in the Zoho Mail Admin Console. Add users by assigning them custom email addresses under your domain (e.g., info@yourdomain.com).
## **Step 4: Generate an Application-Specific Password in Zoho Mail** [#](/docs/how-to-configure-zoho-mail-with-wordpress-for-custom-domain-email/)
Log in to your Zoho Mail account. Navigate to **My Account** → **Security** → **App Passwords**. Generate a new application-specific password for use with external applications like FluentSMTP.
### **Step 5: Install and Configure FluentSMTP in WordPress** [#](/docs/how-to-configure-zoho-mail-with-wordpress-for-custom-domain-email/)
Log in to your WordPress Admin Dashboard. Navigate to **Plugins**→ **Add New**. Search for **FluentSMTP**, install, and activate the plugin. After activation, go to **Settings** → **FluentSMTP**.
Click on **Add New Connection** and select **Zoho** as the mailer. Then fill in the required fields:
- **From Email Address**: Your Zoho Mail email address (e.g., info@yourdomain.com).
- **From Name**: The name you want your emails to display.
- **SMTP Host**: smtp.zoho.com
- **SMTP Port**: 465 (for SSL) or 587 (for TLS)
- **Encryption**: Choose SSL or TLS based on the port selected.
- **SMTP Username**: Your full Zoho Mail email address.
- **SMTP Password**: The application-specific password generated earlier.
And save the settings and send a test email to ensure everything is configured correctly.
And that’s it. This is how easily following these steps, you can easily integrate Zoho Mail to your WordPress website, ensuring seamless email communication using your custom domain.
Still stuck? Feel free to reach out to our [**support team**](https://support.xcloud.host/) for assistance.
---
# How to Connect OpenAI Codex To OpenClaw With xCloud? - xCloud
> Connect OpenAI Codex to your xCloud OpenClaw server using ChatGPT OAuth. Use your ChatGPT Plus or Pro subscription without API keys in a simple step-by-step setup.
OpenAI Codex lets you use your existing ChatGPT Plus or Pro subscription as the AI provider for your OpenClaw agent — no separate API key or billing required. xCloud includes a built-in Codex OAuth token generator that handles the authentication flow securely inside the dashboard.
Follow the steps below to connect OpenAI Codex to xCloud easily.
## Step 1: Open the OpenClaw Provider Settings [#](/docs/how-to-connect-openai-codex-to-openclaw/)
Log in to your xCloud OpenClaw dashboard. Navigate to your Site → OpenClaw → Providers. In the OpenClaw Configuration panel, look for the AI provider selector.
If you are creating the new OpenClaw instance, just choose the **‘OpenAI Codex – CHATGPT OAuth’ from the ‘**AI Provider dropdown menu.
## **Step 2: Set up Your OAuth Token** [#](/docs/how-to-connect-openai-codex-to-openclaw/)
Next, you can to set up OpenAI Codex in just a few clicks. Click on the **‘Generate Token’** link to proceed.
## Step 3: Set up OpenAI Account [#](/docs/how-to-connect-openai-codex-to-openclaw/)
You will be redirected to the integration page of OpenAI Codex page.
Read the ‘How It Works’ information’ carefully. And click on the ‘Connect with OpenAI’ button.
Next, you will be redirected to the OpenAI login page. Here, sign in to your OpenAI account (ChatGPT Plus or Pro required) using your credentials.
Then, you will see an error page after the login process has been completed. Copy the URL from the browser’s Address bar from that page.
Next, go back to the OpenAI Codex setup page and paste that URL in the box below and click on the ‘Exchange Code and Show Token’.
Then you will get a token. Click on the ‘Copy Token’ button to proceed.
## Step 4: Paste the Callback URL and Get Your Token [#](/docs/how-to-connect-openai-codex-to-openclaw/)
Return to the xCloud tab with the OpenClaw configuration. Paste the full callback URL into the input field provided. Click Submit. xCloud will process the OAuth exchange and display your generated token
The generated token will be automatically populated into the Codex provider field. Confirm your provider configuration looks correct. Click Create (or Save) to apply the configuration to your OpenClaw server
Your OpenClaw agent will now use OpenAI Codex (backed by your ChatGPT Plus/Pro subscription) as its AI provider.
## Troubleshooting [#](/docs/how-to-connect-openai-codex-to-openclaw/)
- The redirect URL doesn’t start with http://localhost:1455/auth/callback Make sure you clicked Connect with OpenAI from inside the xCloud dashboard — do not navigate to the OAuth URL manually. If the URL looks different, try the process again from the beginning.
- “ChatGPT Plus or Pro required” error OpenAI Codex OAuth requires an active paid ChatGPT subscription. Free accounts do not have access to the Codex API. Upgrade your OpenAI plan or use a different provider (e.g., Anthropic Claude, Gemini).
- Signed in with the wrong OpenAI account Log out of your OpenAI account in the browser tab that opened, then sign in with the correct account. Restart from Step 3.
- Token was generated but agent isn’t responding Check that the token was saved correctly by revisiting Site → OpenClaw → Providers. If the field is empty, repeat Steps 3–5. Also verify your OpenClaw server is running and connected.
- Browser blocks the localhost redirect Some strict browser configurations block localhost redirects. Switch to a standard Chrome, Firefox, or Edge browser without strict security extensions, or temporarily disable HTTPS-only mode.
---
# How to Connect Supabase to Lovable - xCloud
> Learn how to connect Supabase to Lovable in minutes with this step-by-step guide for setting up a secure and scalable backend.
[**Supabase**](/supabase-hosting/) is an open-source backend platform that provides everything you need to build modern applications, including a **PostgreSQL database**, user authentication, real-time subscriptions, file storage, and built-in security features. It removes the complexity of managing your own backend infrastructure while still giving you full control over your data and APIs.
When paired with Lovable, Supabase becomes a powerful foundation for building scalable, secure, and interactive apps quickly. Lovable handles the frontend and app logic, while Supabase manages your backend services seamlessly behind the scenes.
Follow the steps to connect Supabase to the [**Lovable**](/lovable-hosting/) project easily in just a few clicks:
## **Step 1: Go to** **Your Supabase Project** [#](/docs/how-to-connect-supabase-to-lovable/)
Begin by navigating to your Supabase dashboard and opening the project you want to connect. From the top menu, click the **‘Connect’** button.
A pop-up window will appear, select the **‘App Frameworks’** tab and choose your app language. From this section, copy the credentials provided in the .env configuration. These credentials are required to link your Supabase backend to your Lovable project.
## **Step 2: Configure Supabase Credentials in Lovable** [#](/docs/how-to-connect-supabase-to-lovable/)
Next, open your Lovable project and paste the Supabase credentials you copied earlier by entering them directly through chat to update the .env file with your Supabase credentials.
Once the credentials are added, go to the **Code Editor** within Lovable. From the dashboard, copy the complete SQL code we’ve prepared for database setup. This SQL script defines the database structure that Supabase will use.
## **Step 3: Execute SQL in Supabase** [#](/docs/how-to-connect-supabase-to-lovable/)
Return to your Supabase dashboard and open the SQL Editor from the sidebar menu. Paste the SQL code you copied from the Lovable dashboard into the editor, then click the “Run” button.
After the query executes successfully, the required tables will be created in your Supabase database, completing the connection between Supabase and Lovable.
And that’s it, this is how easily you can connect Supabase to Lovable. It is a simple process that allows you to build full-stack applications with minimal effort.
By combining Supabase’s powerful backend capabilities with Lovable’s intuitive frontend and logic handling, you can launch scalable and secure applications faster without managing complex infrastructure.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How to Connect xCloud MCP to Your AI Agent - xCloud
> Learn how to connect xCloud MCP to Claude Desktop and manage your servers and sites by talking to your AI agent instead of using the dashboard.
Managing servers usually means opening the dashboard, finding the right site, clicking through a few screens, and repeating that every time you need something. xCloud MCP removes that step.
MCP (Model Context Protocol) is an open standard that lets AI agents connect to external tools and act on your behalf. With xCloud MCP connected, you can simply ask your AI agent to check a server’s health, run a backup, update plugins, purge a cache, or pull the latest vulnerability scan, and it will do it through your xCloud account. No dashboard, no tab switching.
Follow the guide walks you through connecting xCloud MCP to AI Agents.
## **Step 1: Open the MCP page in your xCloud dashboard** [#](#step-1-open-the-mcp-page-in-your-xcloud-dashboard)
From your xCloud dashboard, go to Settings. In the left sidebar, choose Developers → MCP.
This opens the MCP documentation, where you will find setup instructions for each supported AI agent.
## **Step 2: Copy the MCP URL** [#](#step-2-copy-the-mcp-url)
We are using Claude Desktop for this walkthrough. Open the Claude Desktop section in the documentation and copy the MCP URL shown there.
## **Step 3: Add the connector in Claude Desktop** [#](#step-3-add-the-connector-in-claude-desktop)
Then Login to your Claude Desktop account and find profile and click Settings option from the menu.
In the popup, go to Connectors. Click Add, then choose Add Custom Connector from the dropdown.
Next, enter a name for the connector and paste the MCP URL you copied. Click Add.
Claude Desktop will then show a screen asking you to connect xCloud MCP. Click on it.
## **Step 4: Authorize the connection** [#](#step-4-authorize-the-connection)
The xCloud authorization page opens. Here you can:
- Verify the account email shown.
- Check which team the MCP is connecting to. If it is not the right one, click Switch to change it.
- Choose the access level: Full Access (read and write) or Read Only.
If you are only trying this out, Read Only is a safe place to start. You can reconnect with wider access later. Now, click Authorize to finish.
## **Step 5: Set tool permissions** [#](#step-5-set-tool-permissions)
Once the connection is live, open the Permissions section. Every xCloud tool can be set individually to:
- Always Allow: the agent runs it without asking.
- Needs Approval: the agent asks you before each run.
- Blocked: the agent cannot use it at all.
You can also configure custom permissions per tool. A good default is Always Allow for read actions like listing sites or checking monitoring stats, and Needs Approval for anything that changes your infrastructure, such as deleting a site or restarting a service.
## You are connected [#](#you-are-connected)
That is it. xCloud MCP is now connected to Claude Desktop, and your agent can work directly with your servers and sites. Try starting with something simple to confirm it is working:
- “List all my xCloud servers.”
- “Which of my sites have pending WordPress updates?”
- “Take a backup of my staging site.”
From here, you can connect the same MCP to other agents you use, adjust permissions as you get comfortable, and let your agent handle the routine infrastructure work while you focus on everything else.
Connecting xCloud MCP takes a couple of minutes, and it changes how you work with your infrastructure. Start small to build confidence, ask it to list your servers, check which sites have pending updates, or take a backup of a staging site, then widen the permissions as you get a feel for it.
---
# How to Create a Blank PHP Site with xCloud - xCloud
> Learn how to create, configure, and create a blank PHP site on xCloud with simple step-by-step instructions.
If you want to build and launch a PHP website quickly, xCloud gives you a simple way to get started. By creating a blank PHP site, you gain full control over your project while using the flexibility and tools provided by xCloud. This guide will walk you through the entire process, from creating a new site to setting up your database and domain preferences.
Follow the steps below to create a blank PHP site on xCloud with ease, so you can focus on developing and running your application instead of worrying about setup complexities.
### **Step 1: Create A New Site** [#](/docs/how-to-create-a-blank-php-site-with-xcloud/)
First, click on **‘New Site’** from the xCloud dashboard. Then choose your server and click on the ‘Custom PHP’ tab from the menu. Next, choose the **‘Blank PHP Site’** to import your custom PHP site.
### **Step 2: Configure Blank PHP Site Information** [#](/docs/how-to-create-a-blank-php-site-with-xcloud/)
And if you choose to migrate to a new domain, you can include your custom And if you choose to migrate to a new domain, you can include your custom domain. You can upload your site and visit it live with a demo domain. After successfully creating your site, you may update the site with your custom domain later. In this tutorial, we will be working on a staging site. Select ‘Demo Site’ and then click on the ‘Next’ button.
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your **‘PHP Version’**, **‘Site Users’,** and ‘Web root’.
Then go to the ‘Database Management’ Section and proceed with ‘Create Database Server’ or **‘Add Your Existing Database’.** Also, you can create a site without any database as well, choose the **‘No Database’** option for that and click on the **‘Next’** button.
### Step 3: Complete Database Settings & Finalize [#](/docs/how-to-create-a-blank-php-site-with-xcloud/)
In the ‘Database’ tab you can configure your preferred database setup. If you are good to go for uploading an existing custom PHP website with xCloud, click on the ‘Start’ button.
Within a few moments, your PHP website will be uploaded on xCloud automatically. You will see the following screen while uploading.
Once the deployment is successfully completed will see the following screen. You go to the site dashboard from there. If you visit the site, you can see the newly Blank PHP site that you have uploaded with xCloud.
This is how easily you can create a site with Blank PHP applications in xCloud. With simple steps, you can quickly deploy your site, configure your database, and choose your preferred domain settings.
Still feeling stuck? Contact our [**support team**](/support/) for further assistance.
---
# How to Create a Custom Blueprint with xCloud - xCloud
> Learn how to create a custom blueprint in xCloud to speed up your project setup with your own plugins and themes.
Creating custom blueprints helps you organise and simplify your workflows. This is especially useful when working with teams or setting up projects repeatedly. With xCloud, you can easily design blueprints that include specific plugins and themes to fit your needs.
Follow the steps to create your own custom blueprint in xCloud, which will allow you to deploy your preferred configurations faster and more efficiently.
## **Step 1: Go to Team Settings** [#](/docs/how-to-create-a-custom-blueprint/)
First, log in to your xCloud account and navigate to the upper right menu on the dashboard. Then, click on the **‘Team Settings’** option from the menu.
## **Step 2: Go to Blueprint** [#](/docs/how-to-create-a-custom-blueprint/)
Next, locate the **‘My Blueprints’** option and select it. Then, click on **‘Create New Blueprint’** to set up your custom blueprint.
## **Step 3: Create a Custom Blueprint** [#](/docs/how-to-create-a-custom-blueprint/)
Here, you will find a menu tab. Choose the **‘Custom Items’** option from the tab.
Give your custom blueprint a name first. Then enter a name for the item in the **‘Item Name’** field and choose the **‘Item Type’** as either **‘Plugin’** or **‘Theme’** from the dropdown.
## **Step 3:Create a New Item** [#](/docs/how-to-create-a-custom-blueprint/)
Then choose a source method from the ‘Download URL’ and ‘Upload ZIP File’ options
**Method 1: Download URL**
If you choose the **‘Download URL’** option, enter the **‘Download URL’**, **‘Version’,** and **‘Description’** into the designated fields and click on the **‘Create Item’** Button.
**Method 1: Upload ZIP file**
To upload a ZIP file, first select your storage provider from the dropdown menu. Remember, you need to connect an S3 storage provider to upload a plugin or theme.
**_Note:_** _pCloud and Google Drive storage integrations will not work for Custom Bluprint_
Next, go to the ‘Upload ZIP File’ section and upload your plugin’s or theme’s ZIP file. Then enter the version and a ‘Description’ of your file and click on the ‘Create Item’ button.
## **Step 5: Add a Plugin or Theme in the Blueprint** [#](/docs/how-to-create-a-custom-blueprint/)
If you have uploaded a plugin, you need to choose at least one theme to create this blueprint. Alternatively, if you uploaded a theme, you need to choose at least one plugin to create this blueprint. From here, go to the **‘Available Custom Items’** section and choose a theme or plugin that you have already uploaded. Then click on the ‘Create’ button.
Once this is completed, you will see the item in the blueprints list.
## **Step 6: Add a Post Deployment CLI Script** [#](/docs/how-to-create-a-custom-blueprint/)
You can add a script that runs automatically after all items in the blueprint have been installed. This helps you perform extra setup tasks. Go to the ‘CLI Script’ tab and enter the scripts or commands into the dedicated field. Then click on the ‘Create’ button.
And that’s it! You’ve successfully created a custom blueprint in xCloud. By following these steps, you can build reusable configurations that save time and maintain consistency across your projects.
### 💡Why Google Drive and pCloud Are Not Compatible with Custom Blueprints in xCloud [#](/docs/how-to-create-a-custom-blueprint/)
When creating a custom blueprint in xCloud, you need to upload plugins or themes either by providing a direct download URL or by uploading a ZIP file from a connected storage provider.
Google Drive and pCloud are not supported for this feature because they do not offer **direct public download URLs** that xCloud can reliably access.
In contrast, **S3 compatible storage providers** offer **stable and secure URLs** that xCloud can use to fetch your plugin or theme files during deployment. This makes them the preferred option for working with Custom Blueprints.
If you want a simple and reliable solution, you can use Backblaze. It is S3 compatible and even offers free storage that works great with the Blueprint feature in xCloud.
So, if you want to use ZIP uploads in your blueprints, make sure you connect an S3-compatible storage account. This way, everything will run smoothly.
Still stuck? Contact our **[support team](/support/)** for any of your queries.
---
# How to Create a Custom Sales Landing Page for xCloud White Label - xCloud
> Create a custom sales landing page with xCloud White Label — link products, set pricing, and streamline the checkout process to boost conversions.
With xCloud, you can create a custom sales landing page tailored to your business needs. This landing page allows you to showcase your products and link them with pricing as per your preferences. By following a few simple steps, you can seamlessly integrate your products with a user-friendly checkout process, enhancing customer experience and increasing conversions.
To get started, you will need one domain for the landing page and one subdomain for the dashboard — for example, hosting.com for the landing page and app.hosting.com for the dashboard.
Follow the steps to setuup the process of setting up your custom sales landing page, and linking with your custom products.
## **Step 1: Insert the Custom Landing Page** [#](/docs/how-to-create-a-custom-sales-landing-page-for-xcloud-white-label/)
To begin, log in to your xCloud dashboard and navigate to the **‘White Label’** tab. From there, go to **‘Access Dashboard & Website’** and select **‘Domain Settings’**. This will redirect you to the **‘Custom Domain Name’** setup page, where you need to enter your dashboard link. This link will be the access point for your clients to manage their servers and sites.
After entering your link, you will need to add the provided DNS records to your DNS provider. Wait for the DNS records to propagate globally, then click on Verify and Save to complete the setup.
## **Step 2: Access the xCloud White Label Dashboard** [#](/docs/how-to-create-a-custom-sales-landing-page-for-xcloud-white-label/)
Next, access the xCloud White Label dashboard and go to the **‘Products’** section in the side navigation menu. Here, you will find a list of your created products. Select the product you wish to link to your custom sales landing page.
## **Step 3: Go to Your Custom Sales Landing Page’s Dashboard** [#](/docs/how-to-create-a-custom-sales-landing-page-for-xcloud-white-label/)
After selecting your product, go to your site hosting.com and add the products directly to your custom sales landing page. Then, access your site’s dashboard and navigate to **‘Pages’**. Locate the page you are using as your landing page and find its pricing section.
## **Step 4: Add Your Product Link to the Custom Landing Page** [#](/docs/how-to-create-a-custom-sales-landing-page-for-xcloud-white-label/)
Once you find the pricing section, go to the pricing option where you want to add the product link. Paste the checkout link of the selected product from the xCloud White Label dashboard and paste it into the appropriate pricing section.
Once done, click on the **‘Save’** button to confirm your changes. To ensure that everything is working correctly, visit your custom sales landing page and verify that the checkout links redirect users properly to the checkout page.
And that’s it. This is how easily you can set up a custom sales landing page with xCloud is quick and easy. Just connect your domain, link your products, and add the checkout links. In a few steps, you’ll have a branded custom page ready to drive sales and boost conversions.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# Quick Start Guide: How To Create A Site With xCloud - xCloud
> Follow this simple guide to create a site with xCloud.
Whether you have your own server or using a xCloud managed server, you can easily create a site without any coding with [**xCloud**](/). This platform aims to simplify the process of hosting and managing WordPress sites, allowing developers and agencies to focus on building fully functional websites without worrying about the underlying infrastructure. Now let us follow these steps to get you started.
## **How To Create A Site With xCloud** [#](/docs/how-to-create-a-site-with-xcloud/)
After you have completed [setting up your servers](/docs/setup-your-first-server-site-with-xcloud/), you are now ready to create your site. Simply follow our step-by-step guide below.
### **Step 1: Create A Site From The Dashboard** [#](/docs/how-to-create-a-site-with-xcloud/)
Once your server is connected, you can create a site from the Dashboard or Site List by clicking on the button “**Add New Site**”.
Then you will need to select the server on which you want to install your WordPress website.
### **Step 2: Choose Your Site & Add Information** [#](/docs/how-to-create-a-site-with-xcloud/)
As we will be creating a fresh WordPress site choose the “I**nstall New WordPress Website**” options as shown below.
Now all you have to do is install and ‘**Go Live’** with your WordPress Site. You can do the next process in a few simple and easy steps.
\[_Note: You can also create a demo site, which you can make live later._\]
1. Add a **Site Title**
2. Add **Tags** if you want
3. Choose to **Go Live**
4. Add your domain name in the ‘**Domain Setup**‘ option.
5. Below you will find an option to enable ‘**Multisite**‘. It comes with **[subdomain](/docs/wordpress-multisite-with-subdomain/)** and **[subdirectory](/docs/how-to-install-wordpress-multisite-with-xcloud/)** options.
6. **DNS Configuration:** If you add the domain and want to visit the live site you need to [**configure your DNS**](/docs/how-to-setup-dns-record-in-xcloud-server/). xCloud does not handle your DNS but all you need to do is remove any existing A records and add the A record as shown above. For example, if your domain is on Cloudflare then all you need to do is add an A record with the domain name, and your server IP address. **Domain**. Make sure to add the A record as shown above in your DNS panel.
To use a **Free SSL certificate** by **Let’s Encrypt** simply turn on the HTTPS enable button and xCloud will automatically set everything for you. However, if you are using **[Cloudflare](https://www.cloudflare.com/)** then while adding the A record please ensure you have disabled the Proxy to prevent redirect errors.
7\. Now, you can enable ‘**Full Page Caching**‘ and ‘**Redis Object Caching**‘ to make your site work faster and give your visitors a better experience.
8\. Next, you can enable ‘**xCloud Managed Email Service**‘ to get free 100 emails/month to kickstart your business. You can also purchase more as you need, starting from $1 for 1000 emails.
9\. Now, at last, you can enable **[xCloud Blueprints](/docs/how-to-use-blueprints-in-xcloud/)** for pre-saved website settings like theme and plugins. Once you create blueprints in xCloud, you do not have to install certain sets of plugins or themes each time you create a website. While creating a website in xCloud, all you need to do is select a blueprint, and then your plugins and theme will be automatically installed.
You can then simply hit the Next Button to create your site and **Go Live** instantly.
### **Configure Additional Settings** [#](/docs/how-to-create-a-site-with-xcloud/)
By default, the WordPress admin credentials are autogenerated to speed up the site creation process. As soon as your site is deployed you will receive your Site credentials on your email address. Later on, you can update your password if needed. From “**More Advanced Settings**” you can update the default **Admin Username**, **Admin Password, Admin Email Address,** etc along with other additional settings from here.
### **Step 3: Review Your WordPress Settings** [#](/docs/how-to-create-a-site-with-xcloud/)
After all the information, you can review your settings. Here you will get an overall report of your **Domain Name**, **HTTPS Settings**, **WordPress Version**, **PHP Version,** and much more.
After the previous step, click on the ‘**Next**’ button. It might take only 1-2 minutes to create your WordPress site.
### **Not Ready Yet? Try Demo Site** [#](/docs/how-to-create-a-site-with-xcloud/)
Also, If you do not want to point your domain yet then xCloud offers temporary domains to make a demo site with every Site creation method available in xCloud. For that select the **Demo Site** option.
### **Start Your Business Journey with 100 Free Emails Monthly** [#](/docs/how-to-create-a-site-with-xcloud/)
Get a sweet deal with xCloud—enjoy **100** free emails per month for each team. If you need more, grab additional xCloud email services. And for those who like it personalized, seamlessly integrate your email provider.
For 1000 emails xCloud will charge you **$1/month**, and for more additional emails we will charge you only $8/m for 8000 emails.
That is how easily you can create a site in xCloud. Now you can start working on your website, customize it, install themes/plugins (if applicable), and take advantage of xCloud’s optimized server environment for seamless site management.
Still stuck? Contact our **[support team](/support/)** for any of your queries.
---
# How to Create A Staging Environment In xCloud? - xCloud
> Simply put, a staging environment serves as an intermediary phase between the development environment and the live production environment.
With [**xCloud**](/), you can easily create a staging environment to push and pull site data between staging and production sites. This lets you test plugins, themes, or any site changes in a new environment and apply them as necessary to your production sites without the risk of breaking them.
Follow the step-by-step guidelines to learn how to create a staging environment to pull and push data between staging and production sites in xCloud.
## **Step 1: Create a Staging Site With xCloud** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Log in to your [**xCloud dashboard**](https://app.xcloud.host/), and go to your production site to deploy a staging site under that site. Once you are here, you can quickly create a staging environment from the drop-down found beside the site name or by clicking on the **‘Deploy Staging’** button.
## **Step 2: Choose The Domain Options** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Once you click the **‘Deploy Staging’ button**, here you will get two options **‘Test Domain’** & **‘Custom Domain’** for creating a staging environment.
### **Test Domain** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Now choose the **‘Test Domain’** option to create a staging site with our test domains. Next, in the **‘Domain Name’** field, enter your preferred **‘Domain Name’** and click on the **‘Deploy Staging Site’** to create a site.
### **Custom Domain** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Choose the **‘Custom Domain’** option to deploy your staging site with your domain. Then, at the **‘Domain Name’** field and enter your preferred domain and hit on the **‘Deploy Staging Site’** option.
_Note: If you have Cloudflare integrated with xCloud, simply check the box below and verify your DNS and SSL settings with Cloudflare._
Once you deploy your staging site under your production site, it will be created instantly. The site will also appear under the production site in the header menu.
## **Step 3: Pull And Push Site Data** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Once you are done creating a staging environment for your production site, it is time to pull and push site data between them. On your staging site page, go to the ‘**Staging Management**’ tab from the left menu to find the pull and push data options. You will also find the deployment logs to know when your changes have been made.
Now, if you need to pull any production site changes to the staging, press the ‘**Pull Data**’ button. You will have **two options** to pull: Files and Database. Plus, you can choose to overwrite all files or keep the most recent updates since the last pull with the ‘**Incremental**’ option.
You can also select to pull the full database or select tables to pull specific data. Once you are done selecting, hit the ‘**Pull Data**’ button.
## **Staging Hook Scripts in xCloud** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Scroll down past the Push / Pull card to find the **‘Hook Scripts’** card. The Hook Scripts card has two sections side by side:
Script
When it runs
Where it runs
**Post-Pull Hook Script**
After every Pull from Production completes
On the **staging site**
**Post-Push Hook Script**
After every Push to Production completes
On the **production site**
Click into the relevant textarea and write your bash script. Each script runs as the site’s system user inside the site’s document root (`/var/www/{site}`), so WP-CLI commands work without full paths.
Click **‘Save Post-Pull Script’** or **‘Save Post-Push Script’** depending on which script you wrote. A success message will confirm the script has been saved.
Your data pull will initiate and will be completed in a few seconds. You can see the pull status and record in the ‘**Deployment Logs**’.
You can also push data from the staging to the production site by clicking on the ‘**Push Data**’ button. Like pulling, you will also be shown a popup with the option to push files and databases. You can choose to overwrite all files or keep the most recent updates since the last push with the ‘**Incremental**’ option.
On the other hand, you can push the full database or select specific tables to push data from staging to live. However, xCloud highly recommends you take a backup of the production site before pushing the data from the staging environment to restore your production website to prevent any data loss if any accident or error occurs.
Once you select your preferred options, hit the ‘**Push to Production**’ button. Your data push will initiate and will be completed in a few seconds. Once the push process starts, xCloud backs up your environments, the destination is overwritten, and the cache is cleared on the destination. You can see the push status with the option and push record in the ‘**Deployment Logs**’.
**_NOTE: If you delete a production site then all staging sites attached to it will be removed as they become orphan. To keep the staging site you can clone them and create a new site separately._**
This is how easily you can create a staging environment to pull and push site data in xCloud between your production site and staging.
## **Frequently Asked Questions** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
### **Does xCloud control indexing on production sites?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
No. xCloud does not manage, inject, modify, or override indexing settings on production sites when using the staging feature. All production indexing behavior remains under the control of WordPress, themes, plugins, or custom configurations.
### **Does xCloud set environment flags such as WP\_ENV or WP\_STAGING?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
No. xCloud does not define, set, or alter any WordPress environment constants or flags that could force a site into a noindex state.
### **Does xCloud add noindex via MU-plugins or server-level rules?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
No. xCloud does not deploy MU-plugins, server rules, or platform-level configurations that apply noindex directives to production websites.
### **Why is indexing disabled on staging sites?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
Indexing is disabled by default on staging sites to prevent staging URLs from being indexed by search engines. This is intentional and expected behavior, designed to protect SEO and avoid duplicate content issues.
### **Does pulling or pushing data affect production indexing?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
No. During pull (production → staging) and push (staging → production) operations, xCloud transfers –
- Only files and database content are transferred
- Indexing settings are not synced or copied
- Production indexing remains unchanged
### **Can staging noindex settings be applied to production?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
No. A staging site’s indexing configuration is never applied to production by xCloud under any circumstances.
### **If a production site shows noindex, where does it come from?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
In most cases, noindex on production originates from one or more of the following:
- WordPress database options
- SEO plugin settings (such as Rank Math or similar)
- Theme logic or custom code that detects environment conditions
This behavior is not enforced or introduced by xCloud.
### **Does xCloud ever treat a production site as staging?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
No. Based on platform architecture, internal testing, and system logs, xCloud does not misidentify production environments as staging environments.
### **What should I check if production indexing issues occur after staging operations?** [#](/docs/how-to-create-a-staging-environment-in-xcloud/)
If indexing issues appear on production, review the following:
- SEO-related database options after staging pushes
- SEO plugin settings, especially environment-based or advanced configurations
- Any custom deployment scripts, environment checks, or conditional logic in themes or plugins
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Create a Telegram Bot and Connect It with OpenClaw - xCloud
> To chat with OpenClaw through Telegram, you first need to create a Telegram bot and generate a bot token. Telegram provides an official bot called @BotFather
To chat with OpenClaw through Telegram, you first need to create a Telegram bot and generate a bot token. Telegram provides an official bot called **@BotFather** that helps you do this in minutes.
Follow the steps below to create your bot, collect the required credentials, and connect it with OpenClaw using the xCloud dashboard
## **Create a Telegram Bot & Collect Telegram Bot Token** [#](/docs/how-to-create-a-telegram-bot-and-connect-it-with-openclaw/)
To chat with our bot, we’ll use Telegram. Select the Telegram option and follow the following steps: Open Telegram. Search for @BotFather and start the chat.
Run the below command in the chat field and send.
```
/newbot
```
Copy to Clipboard
Then pick a display name (anything). Pick a unique username that ends with \`bot\` (for example: \`my\_openclaw\_bot\`). BotFather will give you a bot token like \`123456789:ABCdef…\`.
Save or copy this token – you’ll be required to use this token later to connect with OpenClaw.
👉 Read this [document](/docs/how-to-deploy-openclaw-with-xcloud/) for the full OpenClaw deployment process.
## **Configure Telegram Bot Access** [#](/docs/how-to-create-a-telegram-bot-and-connect-it-with-openclaw/)
After adding your Telegram bot token with OpenClaw on xCloud, go to your Telegram Bot again and run the following command:
```
/start
```
Copy to Clipboard
After that, you will get a User ID. Copy the ID from here and copy the text “openclaw pairing approve telegram ”. Replace the code with the code to enter the user id.
Then go to the xCloud dashboard to add the Telegram Channels from the xCloud dashboard. Now Go to ‘Channels’ from the left side panel to add or update your ‘Telegram Bot Token’ and ‘Telegram User ID’ easily. Click on the ‘Save Changes’ button when you are done. xCloud will automatically connect OpenClaw with your Telegram Bot.
Now, if you go to your Telegram bot interface, you will be able to converse with the bot.
And that’s it, this is how easily you can create a bot token, connect and connect with Clawbot easily.
---
# How To Create And Manage Site Rules With xCloud? - xCloud
> Learn how to Create and Manage Site Rules in xCloud to control HTTP headers and redirects without editing nginx.
Site Rules lets you create and manage HTTP header rules and redirect rules for your WordPress site directly from the xCloud dashboard — no manual nginx config editing required. These web rules are validated against your live nginx config before being applied, and automatically rolled back if validation fails, so a bad rule can never break your site.
_📢 With this feature, xCloud has moved the Redirection feature under the new Site Rules system. You can no longer create or manage redirects using the previous method. Existing redirects will continue to work without interruption. We recommend configuring all new redirection rules through Site Insights._
_Note: This feature is available for both NGINX and OLS servers._
## What Are Site Rules? [#](/docs/how-to-create-and-manage-site-rules/)
Site Rules give you two types of control over how your site responds to HTTP requests:
- **Header Rules:** Add, modify, or remove HTTP response headers (e.g., security headers like X-Content-Type-Options, Strict-Transport-Security, custom headers for caching or CDN behavior)
- **Redirect Rules:** Create 301/302 redirects with optional conditions based on hostname, URI, query string, or device type — without touching .htaccess or nginx config files directly
Rules are processed in priority order, which you control with drag-and-drop sorting.
**➡️ To ensure optimal performance and prevent misconfiguration, Site Rules enforces limits: you can create up to 10 Header Rules and 25 Redirect Rules per site.**
## Prerequisites [#](/docs/how-to-create-and-manage-site-rules/)
- A paid xCloud plan (Site Rules is not available on the free plan)
- The site must be a production site (not a staging site)
_⚠️ It is also not available for non-WordPress applications (**Laravel, custom PHP, Node.js, etc.**)._
## **Step 1: Open Site Rules** [#](/docs/how-to-create-and-manage-site-rules/)
First, go to your site dashboard. From your site dashboard, go to **Tools → Site Rules** in the left sidebar.
## **Step 2: Choose a Rule Type** [#](/docs/how-to-create-and-manage-site-rules/)
Next, you will find the two tabs:
- **Header Rules** — for managing HTTP response headers
- **Redirect Rules** — for managing URL redirects
Click the tab for the type of rule you want to create.
## Step 3: Create a Header Rule [#](/docs/how-to-create-and-manage-site-rules/)
Click on the ‘Add Rule’ button from the top right of the dashboard to open the rule creation modal.
Fill in the following:
Field
Description
**Header Name**
The HTTP header name (e.g., X-Content-Type-Options, Cache-Control). Only letters, numbers, and hyphens allowed.
**Header Value**
The value to set for the header (e.g., nosniff, no-store). Leave blank to remove the header.
Click **‘Save Rule’.** xCloud writes the rule to your nginx config, runs nginx -t to validate, and reloads nginx. If validation fails, the change is rolled back automatically and an error message is shown.
## **Step 4: Create a Redirect Rule** [#](/docs/how-to-create-and-manage-site-rules/)
Next, switch to the ‘**Redirect Rules**’ tab, then click on ‘Add Redirect’ rule.
Fill in the following:
- **From (Source URL):** The path to redirect from (e.g., /old-page)
- **To (Destination URL):** The full URL or path to redirect to (e.g., /new-page or https://example.com/new)
- **Redirect Type: 301** (permanent) or 302 (temporary)
Click the ‘Save Rule’ button, and proceed to add the redirect rule
You can also check how a rule will behave without actually applying it to your site by using the **‘Test Rule’** button
You can also add conditions that let you create conditional redirects. For example, redirecting mobile users to a different URL, or only redirecting when a specific query parameter is present.
Click on the ‘Attach Condition’ button to access the Conditions options. Restrict when the redirect applies based on hostname, URI pattern, query string, or device type
## **Step 7: Edit or Delete a Rule** [#](/docs/how-to-create-and-manage-site-rules/)
To edit a rule, click the edit icon on the rule’s row. The same modal opens with the existing values pre-filled. Make your changes and click Save Rule.
To delete a rule, click the delete icon and confirm. The rule is removed from your nginx config immediately.
## **Troubleshooting** [#](/docs/how-to-create-and-manage-site-rules/)
- **Web Rules does not appear in the sidebar.** → Web Rules is only available for WordPress sites on nginx servers with a paid plan. Verify your site is WordPress (not Laravel or custom PHP), your server uses the LEMP/nginx stack (not OpenLiteSpeed), and your team is on a paid plan.
- **Saving a rule returns a config validation error.** → Your rule contains a syntax issue that failed nginx -t. The change was automatically rolled back — your site is unaffected. Review the error message shown in the modal, correct the header value or redirect pattern, and try again.
- **A header rule is saved but the header does not appear in the browser.** → Also, verify the rule is not being overridden by another rule higher in the priority order. Header rules apply to PHP responses — static files served by nginx directly (images, CSS, JS) may not receive headers from header rules.
- **A redirect isn’t triggering.** → If you added conditions, verify the condition values are correct (exact hostname, correct query param name). Redirect rules are evaluated before PHP processing — if another nginx rule handles the request first, the redirect may not fire.
- **I hit the rule limit but need more rules.** → Contact [our Support Team](https://support.xcloud.host/) to discuss options. Consider consolidating rules where possible — multiple header values can sometimes be combined into a single rule.
- **Test Rule shows success but the live rule isn’t working.** → The test validates nginx syntax, not rule logic. A syntactically valid rule can still produce unexpected behavior. Test your redirect in a browser using the Network tab in DevTools (look for the 301/302 response) or test headers using curl -I https://yoursite.com.
---
# How to Customize Magic Login with xCloud - xCloud
> Learn how to customize Magic Login with xCloud to seamlessly access your WordPress dashboard with easy steps.
Magic Login allows you to access your website effortlessly with a single click, without requiring a password or email address. With xCloud, you can seamlessly log in to your WordPress dashboard using your existing xCloud account or by configuring your own email address.
Follow the step-by-step process below to customize Magic Login with the xCloud.
## **Step 1: Access Magic Login Settings** [#](/docs/how-to-customize-magic-login/)
To get started, log in to your xCloud account and navigate to the site you want to customize. Once there, find the **arrow icon right beside the ‘Magic Login’ option** in the dashboard and click on it.
## **Step 2: Customize Magic Login Settings** [#](/docs/how-to-customize-magic-login/)
Next, a pop-up window will appear, presenting different login preferences. Select the **‘Default’** option if you want to log in with your xCloud email account email or the first admin account, then click on **‘Magic Login’** to access your site.
Alternatively, if you prefer to log in with a different email address or username, select the **Custom** option. Enter your preferred email address in the designated field. If you want to log in using this custom method always, click on ‘**Remember me’** to access your site dashboard using this direct magic login button. Then click **Save** to apply your changes.
_**Note:** To use the Custom option, you must have the necessary permissions. If you do not have access, request your Team Admin to grant you the required permissions._
That’s it! You have successfully cutomize Magic Login according to your preference and get seamless secure access to your WordPress dashboard with xCloud.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Delete Your Account and Data With xCloud - xCloud
> If you no longer need xCloud, download anything you need, remove active services, check provider resources, then request account and data deletion.
If you no longer need xCloud, download anything you need, remove active services, check provider resources, then request account and data deletion.
## Prerequisites [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
- Access to xCloud
- Owner or billing access
- Downloaded backups/invoices you need
- Access to cloud provider account for self-managed servers
## Step-by-step [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
### 1\. Download backups and invoices [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Save website/database backups, invoices, and records before deleting services.
### 2\. Delete sites and servers [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Remove sites and servers you no longer need. Related server subscriptions are cancelled when all related servers are removed.
### 3\. Remove provider resources [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
For self-managed servers, check the cloud provider for active servers, volumes, snapshots, firewalls, IPs, or backups.
### 4\. Review billing and cards [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Confirm no unexpected active subscriptions remain and download final invoices.
### 5\. Submit deletion request [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Contact support with account email, confirmation, downloaded-data acknowledgement, and whether billing info should be removed where possible.
### 6\. Confirm completion [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Wait for team review and keep the confirmation message for your records.
## Troubleshooting [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
### Deleted servers but still charged [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Check whether charge is from xCloud or provider; provider-side resources must be removed in provider dashboard.
### Need invoices after deletion [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Download before deletion, or contact support with billing email if already deleted.
### Want to cancel billing only [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Delete active servers; if subscription remains, contact support.
## FAQ [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
### Can I keep backups? [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Yes, download them before deletion.
### Does deleting all servers cancel subscriptions? [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Related server subscriptions should stop after servers are removed.
### Why does support ask for a reason? [#](/docs/how-to-delete-your-account-and-data-with-xcloud/)
Feedback helps improve xCloud; you can keep it brief.
---
# How to Deploy a Node.js Application with xCloud - xCloud
> Easily deploy and manage your Node.js applications using xCloud with a seamless, automated, and Git-integrated workflow.
Deploying an application can often involve complex configurations and server management tasks. With [**xCloud**](/), this process becomes simple, automated, and developer-friendly.
xCloud provides an intuitive interface that allows you to easily deploy, manage, and scale your [**Node.js**](/node-js-hosting/) applications directly from your Git repository without worrying about manual setup or infrastructure maintenance.
Follow the guide to deploy your Node.js application easily with xCloud:
## Step 1: Create a New Site [#](/docs/how-to-deploy-a-node-js-application/)
To begin deployment, click on the **‘Add New Site’** button from your xCloud dashboard. You will then be asked to choose the **server** where you want to deploy your Git project.
## Step 2: Go to the Deploy Via Git Tab [#](/docs/how-to-deploy-a-node-js-application/)
Next, head over to the **‘Deploy Via Git’** tab. This is where you can deploy your Git projects in just a click.
### **Step 3: Enter Your Project URL** [#](/docs/how-to-deploy-a-node-js-application/)
You will find **‘Public Repository (Manual HTTPS URL)’ and ‘Connected Git Provider’.** If you choose **Public Repository (Manual HTTPS URL)**, enter your **GitHub Repository URL** and specify the **Git Branch.**
If you choose **Connected Provider**, enter your **GitHub Repository SSH URL** and specify the **Git Branch.**
In this document, we’ll deploy the project using the **“Connected Git Provider”** option.
Enter your project URL in the ‘URL’ field. You will see xCloud automatically detecting the site type and setting the site type as ‘Node.js’ or others from your repository, so there is nothing to select manually here.
## **Step 2: Set Up Domains** [#](/docs/how-to-deploy-a-node-js-application/)
Then go to the **‘Staging Domain’** tab. xCloud provides a free demo domain to make your site public. Or if you want to proceed with your custom domain, just click on ‘Use a demo domain instead’. For this documentation, we’ll proceed with the **‘Demo Site’** option and click **‘Next’** to continue.
## **Step 3: Configure Node.Js Application** [#](/docs/how-to-deploy-a-node-js-application/)
In the **‘Settings’** tab, you will find options to configure the **Node.js version** and manage **site users.** Adjust them according to your preferences.
Next, you will see the ‘Build & Serving’ section and you will see that the type is already selected. Here you will get 3 options:
– Static build
- SSR (Node process)
- Hybrid (Static + API)
**You can adjust and choose your preferred one from the dropdown.**
Next, go to the ‘Web Root’ section and add the web root of your project. You can check in the click on the ‘Auto Deploy on Push’
Once the repository integration is complete, you can configure post-deployment actions.
In the **‘Deployment Script’** field, enter any custom commands you want to execute after deployment. You can also select one of the example scripts provided. After configuring this, click **‘Next’** to continue.
### **Step 7: Configure Advanced Settings (Optional)** [#](/docs/how-to-deploy-a-node-js-application/)
Next, go to the **‘Advanced Settings’** section. This step is optional, but it lets you fine-tune the deployment:
**→ Node.js Version:**Choose the Node.js version your project needs from the dropdown.
**→ Database:**Configure the database settings for your project.
Next, enter the contents of your environment file in the ‘.env File’ field. This is where you define the environment variables your project needs at runtime, such as API keys, database credentials, or app-specific configuration values.
You can also add a deploy script for this project. Any commands you enter here will run after the deployment completes, which is useful for tasks like installing dependencies, running migrations, or building assets.
## **Step 9: Confirm Deployment** [#](/docs/how-to-deploy-a-node-js-application/)
The final step is to confirm and start the deployment. Click the **‘Start’** button to begin the process. You can monitor the deployment progress in real time.
Once the deployment is complete, a success message will appear. From there, you can access your site dashboard.
After deployment, visit your site to confirm that your **Node.js application** has been successfully deployed with **xCloud.**
## **Environment Editor for Node.Js Application** [#](/docs/how-to-deploy-a-node-js-application/)
The Environment section in xCloud allows you to customize configuration settings for your Node.js instance. Just go to the **‘Environment’** option from the sidebar and adjust as you need then click on the ‘Save’ button.
## **SSR Configuration for Node.js application** [#](/docs/how-to-deploy-a-node-js-application/)
If you are deploying an SSR application, you can update the ‘**Application Port’, ‘Start Command’** later as well. Just go to the ‘SSR Configuration’ from the **‘Node.js’** Menu under the site dashboard and click on the **‘Update Configuration’** button.
Deploying a Node.js application with xCloud is a streamlined and efficient process that eliminates the complexity of manual configuration and server management. Once your deployment is complete, you can easily manage your application, update configurations, and push new changes directly from your Git repository.
With xCloud, developers can focus on building and improving their Node.js applications while xCloud takes care of the infrastructure behind the scenes.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Deploy a Custom Docker Application from a Git Repository with xCloud - xCloud
> Learn how to deploy Custom Docker projects from a Git repository using xCloud. This step-by-step guide covers server setup, port detection, and going live.
Deploying custom Docker projects doesn’t have to be complicated. With xCloud, you can pull your Docker Compose setup directly from a Git repository and have your application running in minutes.
Follow this guide to walk you through the entire process, from creating a Docker + NGINX server to deploying your application and going live.
## Step 1: Create a Docker+ NGINX Server [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
First, you need to create a Docker server to deploy Custom Docker. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Custom Docker either on your [own server](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy Custom Docker with xCloud. You can either use an [xCloud Managed Server](/managed-hosting/) or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the ‘Server Name’, set the ‘App Type’ to Custom Docker(it is optional to select), and add any relevant ‘Tags’ to help identify your server later.
Next, you can see the ‘Docker + NGINX’ stack is already selected, which is mandatory for deploying the Custom Docker application. Then click on the ‘Create’ button to proceed.
Next, choose your server size according to your preferences. xCloud offers an exclusive discount for the first month. Moreover, you can save up to more discounts if you proceed to an annual or 24-month plan.
Once the server is created, you will be able to deploy your Custom Docker Application on this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## Step 2: Create a New Site [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the ‘New Site’ button.
## Step 3: Choose Your Server [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
Then choose your server from the dropdown menu. Next, click on the ‘Next’ button to proceed to start creating Custom Docker applications.
## Step 4: Go to The Custom Docker Tab [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
From here, go to the ‘Custom Docker’ tab and click on the ‘Docker Compose From Git’ to deploy your Custom Docker applications.
## Step 5: Set Up the Docker Compose Application [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘Site Title’ and add relevant ‘Tags’ to help organize your deployment.
## Step 6: Set Up Domains [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
From the ‘Domains’ tab, you will get two options: either you can create a ‘Demo Site’ with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain. Just proceed with the ‘Go Live’ option.
It is recommended to proceed with your own domain. Top begin, click choothe ‘Go Live’ and enter your preferred domain name. Then complete the DNS verification process.
Then you will get a ‘Site User’ of xCloud and click on the ‘Next’ button to proceed.
## Step 6: Insert Git Repository Credentials [#](/docs/how-to-deploy-custom-docker-application-from-git-repository/)
In the Git Repo tab, you will see three options: Private Repository (SSH), Public Repository (HTTPS), and Connected Git Provider. For a Public Repository, enter the GitHub HTTPS URL and select the branch. For a Private Repository, enter the GitHub SSH URL and select the branch. In this guide, use Connected Git Provider. Choose your linked account, select the repository, and then pick the branch to deploy.
Next enter the name of your Docker Compose file in the repository root ‘Composer File Name’ in the dedicated field.
Next, go to the ‘Port Detection’ section and click on the ‘Auto-Detect Ports’ button. It will
Scan docker-compose.yml to discover exposed ports for your Nginx reverse proxy.
Next you will get few ports that detected from your docker file. You can select the ‘Primary Service Port’ from the dropdown menu.
Next under the ‘Additional services, you can map for additional ports to different domains or subdomains. Enter the ‘Domain/Subdomain’ and ‘Port’ in the dedicated fields.
Then toggle on the ‘Environment File’ to enable if you want to enter environment variables for your Docker Compose services.
Then, go to the ‘Deployment script section,. In the ‘Deployment Script’ field, enter any custom commands you want to run after deployment. here you can add custom commands to run after deployment (e.g., restart containers, rebuild images).
Once the deployment process is complete, your Custom Docker application will be live. From the site dashboard, click **Visit Site** to access your application in the browser.
You’ve successfully deployed a Custom Docker project from a Git repository using xCloud. With your application now live, you can manage updates by pushing changes to your Git repository and redeploying through the xCloud dashboard. If you run into any issues, review your Docker Compose file, port configuration, and environment variables to ensure everything is set up correctly.
---
# How to Deploy Custom Docker with xCloud - xCloud
> Learn how to deploy a custom Docker Compose application on xCloud with step-by-step guidance for servers, domains, and environment setup.
Docker makes it easier to package and run application processes inside containers. Although containers share some similarities with virtual machines, they are far more lightweight and efficient in their use of system resources. This efficiency enables developers to divide an application into multiple independent, isolated services.
When an application relies on several interconnected services, managing how all the containers start, interact, and stop together can quickly become complex.
[**Docker Compose**](https://docs.docker.com/compose/) addresses this challenge by providing a straightforward way to define and manage applications made up of multiple containers. It helps coordinate shared networks, storage, and communication between individual components, allowing the entire application stack to be deployed, updated, and monitored as a single unit.
Using a YAML configuration file, Docker Compose lets you describe a complete multi-container environment. Each service is defined clearly, making it possible to create flexible setups where containers share networks and data volumes as needed.
In this guide, we’ll explore how to deploy a Docker Compose–based application on xCloud.
> _Note: To access the ‘Custom Docker’ feature, you must have a Docker server._
## Step 1: Create a Docker+ NGINX Server [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
First, you need to create a Docker server to deploy Custom Docker. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Custom Docker either on your [own server](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy Custom Docker with xCloud. You can either use an [xCloud Managed Server](/managed-hosting/) or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the ‘Server Name’, set the ‘App Type’ to Custom Docker(it is optional to select), and add any relevant ‘Tags’ to help identify your server later.
Next, you can see the ‘Docker + NGINX’ stack is already selected, which is mandatory for deploying the Custom Docker application. Then click on the ‘Create’ button to proceed.
Next, choose your server size according to your preferences. xCloud offers an exclusive discount for the first month. Moreover, you can save up to more discounts if you proceed to an annual or 24-month plan.
Once the server is created, you will be able to deploy your Custom Docker Application on this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## Step 2: Create a New Site [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the ‘New Site’ button.
## Step 3: Choose Your Server [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Custom Docker applications.
## Step 4: Go to The Custom Docker Tab [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
From here, go to the **‘Custom Docker’** tab and click on the **‘Docker Compose’** to deploy your Custom Docker applications.
## **Step 5: Set Up the Docker Compose Application** [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
## **Step 6: Set Up Domains** [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain. Just proceed with the **‘Go Live’** option.
For the **‘Demo Site’,** you will get a free demo domain for xCloud. Under the **‘Domain Setup’** section, choose your preferred domain.
Then you will get a **‘Site User’** of xCloud and click on the **‘Next’** button to proceed.
## **Step 7: Set Up Docker Compose Source** [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
Next, configure the source of your Docker Compose file. You can either deploy using a **Public URL to docker-compose.yml** or by directly pasting the **docker-compose.yml content**.
### **Public URL to docker-compose.yml** [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
If you choose the public URL option, enter the URL where the docker-compose.yml file is hosted in the ‘**Docker Compose URL**’ field.
### **Paste docker-compose.yml content** [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
If you choose to paste the content directly, ensure the YAML syntax is valid and properly formatted before proceeding. Enter the Docker compose content and click ‘**Next**‘.
## **Step 8: Set Up Environment (Optional)** [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
In the ‘**Environment Variables’** section, you may optionally enable environment configuration by toggling the option on. This allows you to define environment variables required by your Docker Compose services. Once configured, proceed to finalize the deployment.
When you click Next, xCloud automatically parses the Docker Compose YAML file. If only a single port is exposed, the deployment will begin immediately. However, if multiple ports are detected, you’ll be asked to choose which port should be exposed publicly before the deployment continues.
## Step 9: Visit the Application [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
After the deployment process is complete, your Custom Docker application will be live. From the site dashboard, click ‘**Visit Site’** to access your application in the browser.
### Environment Editor for Custom Docker [#](/docs/how-to-deploy-custom-docker-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your Umami app. Just go to the **‘Environment’** option from the sidebar and adjust as you need, then click on the **‘Update Environment’** button.
And that’s it, this is how easily you can deploy a Docker Compose-based application on xCloud.
By pairing Docker Compose with xCloud’s managed infrastructure, the process of running multi-container applications becomes far more straightforward. You can define your entire application stack in a single YAML file, while xCloud handles the underlying server setup, networking, and routing for you.
This workflow reduces operational overhead and keeps deployments consistent, allowing you to focus on building and maintaining your services rather than managing infrastructure. Whether you are testing an application on a demo domain or deploying it to production, xCloud provides a simple and reliable way to run Docker Compose applications with confidence.
Still stuck? Feel free to reach out to our [**support team.**](/support/)
---
# How to Deploy Hermes Agent with xCloud (Fully Managed Hosting) - xCloud
> Learn how to deploy Hermes Agent with xCloud step by step. Use managed hosting, connect LLM providers, and launch faster with zero hassle.
[**Hermes** **Agent**](/hermes-agent-hosting/) is an AI-powered coding agent that helps you automate tasks, write code, and interact with AI models directly through your preferred messaging platform. Instead of juggling multiple tools and manual workflows, Hermes brings your AI provider and messaging channels together in one place, so you can build and ship faster.
Deploying Hermes Agent traditionally means setting up servers, managing dependencies, and configuring environments yourself. xCloud eliminates all of that with fully managed hosting, handling the infrastructure so you can focus on what actually matters.
Follow this guide to deploy Hermes Agent on xCloud in minutes, connect your preferred AI provider, and optionally set up Telegram for messaging.
## Built-In Support For AI Providers [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
- Anthropic – API Key
- OpenAI API Key
- OpenRouter – API Key
- OpenAI – API Key
- Gemini – API Key
### Built-in support for messaging channels from xCloud [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
- Telegram
### Step 1: Create an xCloud Managed Server [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
First, visit this [**link**](https://app.xcloud.host/hermes) to start creating an xCloud managed server. Go to the ‘Server Name’ field and enter your server name. Then add a tag for the server. This step is optional and not mandatory.
Note: If you haven’t signed up yet, you will be prompted to create an account, choose a plan based on your preferences, and then proceed to payment.
Note: If you create an xCloud Managed Server using the standard server creation flow, choose “**Agentic”** as the web server, then select **“Hermes Agent.”** xCloud will then display the configuration options for deploying Hermes Agent.
Next, go to the ‘Server Type’ option. Here, xCloud provides two types of servers. One is ‘General’, and the other one is ‘Premium’.
- General servers are cost-effective servers powered by Intel CPUs and regular SSDs.
- On the other hand, premium servers are blazing fast with quicker 3 GHz+ Intel Xeon CPUs, faster memory, and NVMe storage.
After that, go to the ‘Server Size’ option and choose your preferred server size. Please note that deploying a Hermes Agent instance requires a minimum 4 GB RAM server.
Next, choose your preferred continent from the dropdown menu. Then select the server location within that region.
After that, choose your ‘Ubuntu version’ from the dropdown menu under the ‘Ubuntu Operating System’. You can also enable or disable backups for this application.
xCloud provides a separate stack for this application. You will see the ‘Hermes’ stack already selected.
Next, go to the security warning section, read the information carefully, and click on the checkbox to confirm that you have read and understood it.
## Enter Your LLM Provider Credentials [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
After that, go to the ‘AI provider’ section. Select your preferred AI model from the dropdown list under ‘AI Provider’, such as ‘OpenAI Codex’ or ‘OpenAI API’. Then enter the API token for the selected AI model.
### OpenAI Codex – API Key: [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
To use your OpenAI account, choose ‘OpenAI Codex – ChatGPT 0Auth)’ from the ‘AI Provider’ menu, connect your account and enter the OAuth Token into the blank field. Also, you can set your ‘Default Model’ from the dropdown menu.
👉Read the [step-by-step guide](/docs/how-to-connect-openai-codex-to-openclaw/) to connect OpenAI Codex with Hermes on xCloud
### OpenAI – API Key: [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
To use OpenAI, choose ‘OpenAI – API KEY’ from the ‘AI Provider‘ menu and enter the OpenAI API key into the blank field. Then set your ‘Default Model’ from the dropdown menu.
### Anthropic – API Key: [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
To use Anthropic, choose ‘Anthropic’ from the ‘AI Provider‘ menu and enter the Ahtropic API key into the blank field. Then set your ‘Default Model’ from the dropdown menu.
### Google Gemini – API Key: [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
To use Gemini, choose ‘Google Gemini’ from the ‘AI Provider‘ menu and enter the Google Gemini API key into the blank field. Then set your ‘Default Model’ from the dropdown menu.
Likewise, xCloud provides Z AI, OpenRouter LLM provider as well. Set up your preferred LLM provider according to your preferences.
## Set up Your Messaging Platform (Optional) [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
Right now, xCloud allows you to connect to one built-in messaging platform: ‘Telegram’. Go to the section, add the ‘Bot token’ in the ‘Telegram Bot Token Field and ‘Telegram User ID’ in the respective fields, and click on the ‘Next’ button.
When you provide your Telegram User ID during setup, your account is automatically allowed to be listed with smarter auto-pairing. No need to run commands to pair your account!
Finally, click on the ‘Create’ button to proceed. This action will start creating the xCloud managed server and deploying the Hermes Agent application.
## Manage the Configurations from the xCloud Dashboard [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
Once the server is created, you will be redirected to the xCloud Hermes Agent dashboard. Here you will get options for ‘Status’, ‘Providers’, ‘Channels’, ‘Domain & SSL’, ‘Basic Auth’, ‘Monitoring’, Logs’, ‘SSH Access’, and ‘Settings’.
### **Log in to the Hermes Agent Dashboard** [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
To log in to your Hermes Agent account, go to the ‘Status from the dashboard. Collect the credentials ‘URL’ from the dashboard. Here you will also get a ‘Webhook Base’ URL as well.
Then go to the ‘Basic Auth Credentials’ Section and collect the ‘Basic Auth User’ and ‘Basic Auth Password’.
After collecting all the credentials, log in to the Hermeas agent’s dashboard the ‘Control UI URL’, ‘Basic Auth User’ and ‘Basic Auth Password’.
Hermes does not provide a chat box in its UI. You need to use the terminal, or you can connect your AI provider to chat with the Hermes Agent.
### How To Update Default LLM Provider Settings [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
In xCloud, you can also update the default LLM provider settings in the dashboard. Go to ‘Providers’ from the left side panel and navigate to the ‘Change Provider’ section. Add your ‘AI Provider’ and the ‘API Key’ and click on the ‘Save Changes’ button.
### How to Add or Update Messaging Channels [#](/docs/how-to-deploy-hermes-agent-with-xcloud/)
Similarly, you can add or update your messaging channels. If you haven’t connected your messaging channels with the Hermes Agent or want to update your existing channel, go to ‘Channels’ from the left side panel to add or update your ‘Telegram Bot Token’ and ‘Telegram User ID’ easily. Click on the ‘Save Changes’ button when you are done.
And that’s it. This is how easily you can deploy Hermes Agent on xCloud. Hermes Agent deployment on xCloud removes the complexity of self-managed hosting and lets you focus on what matters most.
If you run into any issues during the deployment process, feel free to reach out to our [support](https://support.xcloud.host/) team.
---
# How to Deploy LibreChat with xCloud(One Click Apps) - xCloud
> Deploy LibreChat with xCloud in minutes with this step-by-step guide using One-Click Apps, Docker, and NGINX.
LibreChat is an open-source chat application that allows users to interact with AI models in a flexible and customizable environment. It provides a platform to deploy, manage, and run AI-powered chat interfaces, making it suitable for both experimentation and production use.
Follow the steps below so you can quickly get LibreChat running on a cloud server with full functionality, whether for testing purposes or a live application.
## **Step 1: Create a Docker+ NGINX Server** [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
First, you need to create a Docker server to deploy LibreChat. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy LibreChat either on your own server or on an xCloud server.
Next, choose your server provider to deploy LibreChat with xCloud. You can either use an xCloud Managed Server or select your preferred provider. In this guide, we’ll use the [**xCloud Managed Server**](/managed-hosting/).
Afterward, enter the ‘**Server Name’**, set the **‘App Type’** to LibreChat, and add any relevant **‘Tags’** to help identify your server later.
Next, choose between the **‘General’** and **‘Premium’** options based on your requirements. Then, select a plan that best fits your needs.
Next, choose the ‘Region’ and ‘Ubuntu Version for your server. You can also enable or disable the Backup option as needed.
Next, you can see the ‘Docker + NGINX’ stack is already selected, which is mandatory for deploying the LibreChat application. Then click on the ‘Create’ button to proceed.
Once the server is created, you will be able to deploy your LibreChat Application in this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## How to Install LibreChat on a Cloud Server [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
Learn how to install LibreChat on a cloud server. It walks you through creating a server, configuring the environment, and launching your LibreChat application easily.
### Step 2: Access the One Click Apps Dashboard [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
Then choose your **‘Server’** from your dropdown and click on the **‘Next’** button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One-Click Apps section. You will see **‘LibreChat’**, click on it to proceed with the deployment of this application
### Step 3: Set Up the LibreChat Application [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant ‘**Tags**’ to help organize your deployment.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or ‘Demo Site’ for testing purposes. Selecting ‘Go Live’ will immediately create a live environment, while choosing ‘Demo Site’ allows you to experiment in a staging environment before promoting it to production.
### Step 4: Configure Domain Settings [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your LibreChat application. You can adjust the **‘Site User’** according to your preferences, or leave it as the default.
Next, click the toggle on the ‘Enable Ollama’ button, then choose the AI models and click ‘Next’ to proceed. Enabling this option is not mandatory. If you do not enable it, we will display three default AI models. You can also add your preferred models later within the application environment.
However, if you enable Ollama, you will be able to access all available models from here, choose them, and install them at the same time.
## Step 4: Visit the LibreChat Application [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
With LibreChat set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the ‘Visit Site’ app.
### Environment Editor for LibreChat [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
The Environment section in xCloud allows you to customize configuration settings for your LibreChat instance. Just go to the ‘Environment’ option from the sidebar and adjust as you need, then click on the **‘Save’** button.
### Manage LibreChat Models [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
Later, you can manage your LibreChat application. Go to the **‘LibreChat’ → ‘Management’.** Next, click on the **‘Add New Model’** to install more AI models. Also, you can click on the ‘Delete Icon’ to delete the AI models of this application.
_Note: You will get access to management only if you enable Ollama_
This is how you can deploy LibreChat with xCloud and set up a fully functional AI chat environment. By following the steps in this guide, you can create a Docker + NGINX server, configure your site using One-Click Apps, choose between a live or demo environment, and manage your AI models efficiently. You also have full control over domain settings, environment configurations, and user access.
Once deployed, LibreChat can be customized, scaled, and maintained to meet your specific requirements, providing a reliable platform for AI-powered chat applications. If you encounter any issues, xCloud support is available to assist you in keeping your LibreChat instance running smoothly.
## **Want to Deploy Different Self-Hosted AI Models?** [#](/docs/how-to-deploy-librechat-with-xcloudone-click-apps/)
If you are looking to deploy other self-hosted AI applications, check out the following documentation:
**✔️[Deploy OLLAMA application](/docs/how-to-self-host-llms-with-xcloud/)**
**✔️[Deploy OpenWebUI application](/docs/how-to-self-host-llms-with-xcloud/)**
If you encounter any issues or have questions during deployment, please contact our support team for assistance.
---
# How to Deploy OpenClaw with xCloud (Fully Managed Hosting) - xCloud
> Deploy OpenClaw with xCloud using xCloud's fully managed hosting. Easy setup, secure APIs, Telegram support, and scalable servers.
OpenClaw, also known as Clawdbot, is a self-hosted AI agent built to perform real actions instead of only replying to messages. It operates as an autonomous assistant that executes tasks, manages workflows, and interacts with external systems using secure APIs and predefined rules.
Unlike traditional chatbots, OpenClaw connects AI models with system-level access. This design allows it to automate processes, manage files, run scripts, and handle ongoing operations reliably. Users interact with OpenClaw through chat platforms, which keeps control simple while the agent handles the work in the background.
When deployed on xCloud, OpenClaw runs on a dedicated **[xCloud managed server](/managed-hosting/)** with a preconfigured stack. This setup removes the complexity of self-hosting, manual configuration, updates, and infrastructure maintenance.
### **What OpenClaw can do** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
It can handle complex and real-world actions, such as:
- Managing your calendar, inbox, messages and reminders.
- Sending emails, clearing spam or organizing files.
- Running scripts, controlling your browser, automating workflows and more.
- Execute real tasks such as running scripts, managing files, and calling APIs.
- Maintain persistent context across conversations and workflows.
- Automate multi-step workflows without manual intervention.
- Respond to events and triggers in real time.
- Operate continuously based on defined rules and permissions.
- Integrate with messaging platforms like Telegram
- .
- Allow full control through simple chat commands.
## Built-In Support For AI Providers [#](/docs/how-to-deploy-openclaw-with-xcloud/)
- Anthropic – API Key
- Anthropic – Claude Code CLI Token
- OpenAI API Key
- OpenRouter – API Key
- Moonshot Al (Kimi) – API Key
- OpenAI – API Key
- Gemini – API Key
_More AI providers, such as Grok, xAI, Mistral, and more are coming soon_.
### **Supported Messaging Channels from xCloud** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
- Telegram
### **Important Details:** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
✔️ OpenClaw Hosting is available only on xCloud Managed Servers and requires more than 4GB RAM.
✔️ You cannot install OpenClaw on existing or external servers.
✔️ After installation, the server runs only OpenClaw. You cannot host other sites or applications on the same server.
✔️ Support for this beta feature is limited. If you face any issues, please reinstall OpenClaw.
Follow the guide to deploy OpenClaw or Clawdbot on xCloud using One Click Apps and get started in just a few minutes.
Follow the guide to deploy OpenClaw on xCloud and get started in just a few minutes.
### **Step 1: Create an xCloud Managed Server** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
First, **[visit this link](https://app.xcloud.host/openclaw/cart/product/checkout?app=openclaw)** to start creating an xCloud managed server. After that, click on the ‘Start Now’ button from the dashboard.
Go to the ‘Server Name’ field and enter your server name. Then add a tag for the server. This step is optional and not mandatory.
Note: If you create an xCloud Managed Server using the standard server creation flow, choose “Agentic” as the web server, then select “OpenClaw.” xCloud will then display the configuration options for deploying Hermes Agent.
Next, go to the ‘Server Type’ option. Here, xCloud provides two types of servers. One is ‘General’, and the other one is ‘Premium’.
- General servers are cost-effective servers powered by Intel CPUs and regular SSDs.
- On the other hand, Premium servers are blazing fast with quicker 3GHz+ Intel Xeon CPUs, faster memory, and NVMe storage.
After that, go to the ‘Server Size’ option and choose your preferred server size. Please note that deploying an OpenClaw instance requires a minimum 4GB RAM server.
Next, choose your preferred continent from the dropdown menu. Then select the server location within that region.
After that, choose your ‘Ubuntu version’ from the dropdown menu under the ‘Ubuntu Operating System’. You can also enable or disable backups for this application.
xCloud provides a separate stack for this application. You will see the ‘OpenClaw’ stack already selected.
Next, go to the security warning section, read the information carefully, and click on the checkbox to confirm that you have read and understood it.
## **Enter Your AI Provider Credentials** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
After that, go to the ‘AI provider’ section. Select your preferred AI model from the dropdown list under ‘AI Provider’, such as ‘OpenAI’, Anthropic, Claude Code, and Google Gemini. Then enter the API token for the selected AI model.
### **Anthropic:** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
To use Anthropic, choose ‘Anthropic- API KEY’ from the ‘AI Provider’ menu and enter the API Key into the blank field.
### **Claude Code :** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
To use Claude Code, choose ‘Anthropic- Claude Code CLI Token’ from the ‘AI Provider’ menu and enter the Token into the blank field.
**Browser-based token generation**: With xCloud, there is no need to install the Claude Code CLI manually. Generate your token directly from your browser. First, select the Claude Code CLI option and then click on Generate Token.
### **OpenAI:** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
To use OpenAI, choose ‘OpenAI – API KEY’ from the ‘AI Proider menu and enter the API Key into the blank field.
### **Google Gemini :** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
To use Google Gemini, choose ‘Google Gemini- API Key’ from the ‘AI Provider’ menu and enter the API key into the blank field.
## **Set up Your Messaging Platform (Optional)** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
Right now, xCloud allows you to connect to one built-in messaging platform: ‘Telegram’. Go to the section, add the ‘Bot token’ in the ‘Telegram Bot Token Field and ‘Telegram User ID’ in the respective fields, and click on the ‘Next’ button.
When you provide your Telegram User ID during setup, your account is automatically allowed to be listed with smarter auto-pairing. No need to run commands to pair your account!
## **Set up Your Messaging Platform (Optional)** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
You can control the UI of OpenClaw right from the xCloud dashboard. If you want to make it more secure and do not want to make OpenClaw UI accessible for anyone, then click on the checkbox beside ‘OpenClaw Control UI Dashboard.
Finally, click on the ‘Create’ button to proceed. This action will start creating the xCloud managed server and deploying the OpenClaw application.
To log in to your OpenClaw account, go to the ‘Status from the dashboard. collect the credentials ‘URL’ and ‘Basic Auth Password’ from the dashboard.
Now if you log in toyour OpenClaw account using the credentials, you will be able to start chatting with OpenClaw.
## **Step 2: Manage the Configurations from the xCloud Dashboard** [#](/docs/how-to-deploy-openclaw-with-xcloud/)
Now, in the ‘Status’ option from the left side menu, you will get the UI credentials and the Auth credentials. Collect the credentials when necessary. From the ‘Control UI Mode’, you can toggle ON/OFF the ‘Dashboard UI’ option according to your preferences. If you toggle off, no one will be able to access the UI of the OpenClaw dashboard.
Next, go to the ‘Config’ option from the menu and adjust the credentials when needed and click on the update button right from the xCloud dashboard.
The Environment section in xCloud allows you to customize configuration settings for your OpenClaw instance. Just go to the ‘Environment’ option from the sidebar and adjust as you needed then click on the ‘Save’ button.
Update the OpenClaw version from the xCloud dashboard. Just go to the ‘Updates’ from the left menu and click on the ‘Check for Updates’ button to see if there are any updates available.
Next go to the ‘Logs’ option from the left menu. Here you can all the logs of the app.
### How To Update Default LLM Provider Settings [#](/docs/how-to-deploy-openclaw-with-xcloud/)
In xCloud, you can also update the default LLM provider settings in the dashboard. Go to ‘Providers’ from the left side panel and navigate to the ‘Change Provider’ section. Add your ‘AI Provider’ and the ‘API Key’ and click on the ‘Save Changes’ button.
### How to Add or Update Telegram Channels [#](/docs/how-to-deploy-openclaw-with-xcloud/)
Similarly, you can add or update Telegram Channels in the dashboard. Go to ‘Channels’ from the left side panel to add or update your ‘Telegram Bot Token’ and ‘Telegram User ID’ easily. Click on the ‘Save Changes’ button when you are done.
## Reset OpenClaw [#](/docs/how-to-deploy-openclaw-with-xcloud/)
OpenClaw Reset (No new server needed): You can now reinstall OpenClaw from scratch on the same server using OpenClaw Reset. With one click, it creates a backup, reinstalls a clean setup, and generates fresh credentials.
And that’s it. This is how easily you can deploy OpenClaw on xCloud. OpenClaw deployment on xCloud removes the complexity of **[self managed hosting](/self-managed-hosting/)** and lets you focus on what matters most.
## Few More Details of OpenClaw(Beta) Hosting [#](/docs/how-to-deploy-openclaw-with-xcloud/)
✅ OpenClaw Hosting is available only on xCloud Managed Servers and requires more than 4GB RAM
✅ You cannot install OpenClaw on any existing or external servers
✅ After installation, the server runs only OpenClaw. You cannot host other sites or applications on the same server
✅ Support for this OpenClaw feature is limited. If you encounter any issues, please reinstall OpenClaw
## ⚠️ Security + Support Boundaries (Read This Carefully) [#](/docs/how-to-deploy-openclaw-with-xcloud/)
AI agents are powerful tools, and careless use can introduce serious risks. Many users already run agents on personal laptops or unmanaged servers without isolation or a clear understanding of the consequences. xCloud provides a safer deployment path, but risk still exists.
### What xCloud Will Do [#](/docs/how-to-deploy-openclaw-with-xcloud/)
✅ Provision a managed server
✅ Install OpenClaw
✅ Provide basic server-level controls such as restart, reinstall, and environment configuration
### What xCloud Will NOT Do [#](/docs/how-to-deploy-openclaw-with-xcloud/)
❌ Provide support for how you run or configure your agent
❌ Troubleshoot workflows, integrations, prompts, or tool access
❌ Take responsibility for third-party API behavior or failures
❌ Debug issues caused by custom configurations
If OpenClaw becomes unstable or breaks after you start configuring it, reinstall OpenClaw.
Everything beyond server provisioning and installation remains your responsibility.
## 🚨 Mandatory Safety Guidelines [#](/docs/how-to-deploy-openclaw-with-xcloud/)
❌ Do not use your primary OpenAI, Anthropic, Gemini, or similar accounts
❌ Do not connect your main GitHub account
❌ Do not connect personal Gmail or identity systems
✅ Use separate, dedicated accounts for testing
✅ Treat OpenClaw as an isolated sandbox
✅ Avoid connecting anything tied to your real identity or critical systems
You get a fully managed server, a dedicated OpenClaw stack, and seamless integration with Telegram, all without manual configuration or infrastructure headaches.
With One Click Apps, secure API-based connections, and scalable resources, xCloud makes running OpenClaw simple, stable, and efficient. Follow the steps in this guide, complete the setup, and start managing your trading strategies with speed, consistency, and confidence.
## Frequently Asked Questions [#](/docs/how-to-deploy-openclaw-with-xcloud/)
### Q1. Do I need my own LLM provider, or is it included with OpenClaw hosting on xCloud? [#](/docs/how-to-deploy-openclaw-with-xcloud/)
Answer: Yes, you need to bring your own AI provider API key such as OpenAI, Anthropic, Claude Code, OpenAI, or others.
---
# How to Deploy Paperclip with xCloud (Fully Managed Hosting) - xCloud
> Learn how to deploy Paperclip on xCloud with fully managed hosting. Set up servers, configure AI providers, and launch your app in minutes.
[**Paperclip**](/paperclip-hosting/) is a powerful AI-powered application that you can easily deploy using xCloud’s fully managed hosting platform. With xCloud, you don’t need to worry about complex server configurations or manual setup processes. Whether you’re a developer or a non-technical user, xCloud simplifies the entire deployment by handling server provisioning, application installation, and configuration in just a few steps.
In this guide, we will walk you through the complete process of deploying Paperclip on xCloud, from creating a managed server to configuring your AI provider credentials and managing your application through the xCloud dashboard.
### Step 1: Create an xCloud Managed Server [#](/docs/how-to-deploy-paperclip-with-xcloud/)
First, visit this [**link**](https://app.xcloud.host/paperclip/) to start creating an xCloud managed server. Go to the **‘Server Name’** field and enter your server name. Then add a tag for the server. This step is optional and not mandatory.
_**Note:** If you haven’t signed up yet, you will be prompted to create an account, choose a plan based on your preferences, and then proceed to payment._
Note: If you create an xCloud Managed Server using the standard server creation flow, choose “Agentic” as the web server, then select “Paperclip.” xCloud will then display the configuration options for deploying Hermes Agent.
Next, go to the ‘Server Type’ option. Here, xCloud provides two types of servers. One is ‘General’, and the other one is ‘Premium’.
- General servers are cost-effective servers powered by Intel CPUs and regular SSDs.
- On the other hand, premium servers are blazing fast with quicker 3 GHz+ Intel Xeon CPUs, faster memory, and NVMe storage.
After that, go to the **‘Server Size’** option and choose your preferred server size. Please note that deploying a Paperclip instance requires a minimum 4 GB RAM server.
Next, choose your preferred continent from the dropdown menu. Then select the server location within that region.
After that, choose your **‘Ubuntu version’** from the dropdown menu under the **‘Ubuntu Operating System’.** You can also enable or disable backups for this application.
xCloud provides a separate stack for this application. You will see the **‘Paperclip’** stack already selected.
Next, go to the security warning section, read the information carefully, and click on the checkbox to confirm that you have read and understood it.
## Enter Your AI Provider Credentials [#](/docs/how-to-deploy-paperclip-with-xcloud/)
After that, go to the **‘AI provider’** section. Select your preferred AI model from the dropdown list under **‘AI Provider’,** such as **‘OpenAI Codex’** or **‘OpenAI API’.** Then enter the API token for the selected AI model.
### OpenAI Codex – API Key: [#](/docs/how-to-deploy-paperclip-with-xcloud/)
To use Anthropic, choose **‘Anthropic – API KEY’** from the **‘AI Provider’** menu and enter the API Key into the blank field.
### OpenAI – API Key: [#](/docs/how-to-deploy-paperclip-with-xcloud/)
To use OpenAI, choose **‘OpenAI – API KEY’** from the **‘AI Provider**‘ menu and enter the API key into the blank field.
## Set up Your Dashboard Credentials [#](/docs/how-to-deploy-paperclip-with-xcloud/)
Next, configure your Paperclip dashboard credentials. Enter your preferred **‘Dashboard Username’,** and set your preferred **‘Dashboard Basic Auth Password’** in the dedicated fields. Finally, click on the **‘Create’** button to proceed. This action will start creating the xCloud managed server and deploying the Paperclip application.
## Step 2: Manage the Configurations from the xCloud Dashboard [#](/docs/how-to-deploy-paperclip-with-xcloud/)
Once the server is created, you will be redirected to the xCloud Paperclip dashboard. Here you will get options for ‘**Status’, ‘Settings,’ ‘Domain & SSL’, ‘Providers’, ‘Environment’, ‘Logs’,** and **‘SSH Access.’**
To log in to your Paperclip account, go to the ‘**Status**‘ option from the dashboard. Collect the ‘**URL**‘ of your Paperclip dashboard. From here, you can also access ‘**Admin**‘ and ‘**Dashboard Basic Auth**‘ from this page.
Next, go to the ‘**Providers**‘ option from the left menu of the Paperclip dashboard. Here you can see the ‘**Current Provider**‘ that you configured for your Paperclip. If you want to change your AI provider, then go to the ‘**AI Provider**‘ section, set a provider from the dropdown list, and complete the setup process of the AI provider, and click on the save button.
Now go to the ‘**Logs**‘ option and get different types of logs: ‘**Nginx Access Log**‘, ‘**NGINX Error Log**‘, ‘**Fail2ban log**‘, ‘**auth.log’**.
And that’s it. This is how easily you can deploy Paperclip on xCloud. Paperclip deployment on xCloud removes the complexity of self-managed hosting and lets you focus on what matters most.
If you run into any issues during the deployment process, feel free to reach out to the [**xCloud support team**](https://support.xcloud.host/) for assistance.
---
# How to Deploy phpMyAdmin with xCloud One Click Apps - xCloud
> Deploy PHPMyAdmin with xCloud One-Click Apps in minutes. Easily set up, configure, and manage databases with a few clicks.
[phpMyAdmi**n**](https://www.phpmyadmin.net/) is a popular web-based interface used to manage MySQL and MariaDB databases. xCloud simplifies the deployment process through its intuitive dashboard, allowing users to launch and configure PHPMyAdmin instances with minimal effort.
Follow the steps below to quickly set up phpMyAdmin in a demo or production environment using xCloud.
_Note: To access the phpMyAdmin feature, disable the 7G or 8G firewall._
## **Install phpMyAdmin from the Server Dashboard** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
You can also manage phpMyAdmin from your xCloud server dashboard. Just go to **‘Server’ → ‘Database’** to access the phpMyAdmin options. From there, click **‘Open My phpMyAdmin’** to open the phpMyAdmin dashboard.
You can also disable it by clicking **‘Disable phpMyAdmin’**. Additionally, you can create a new database or database user for that server directly from the dashboard.
In this way, the application will be created as a demo site with a test domain. Later, you can update the domain and use a custom domain. Read the documentation for more details:
[_**How To Go Live From Staging Domain?**_](/docs/how-to-go-live-from-staging-domain/)
## **How To Deploy phpMyAdmin in 1 Click** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
You can also deploy your phpMyAdmin application by creating a new site. To create a new site follow the steps below:
## **Step 1: Access the One** **Click Apps Dashboard** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
Begin by logging into your xCloud account. Once authenticated, navigate to your dashboard and click on the **‘New Site’** button.
This will take you to the site creation interface. From here, go to the **‘One Click Apps’** section. Select **‘phpMyAdmin**‘ from the available applications to initiate the deployment process.
Ensure your server is already connected to xCloud. If not, follow the instructions on the dashboard to establish a server connection. Once connected, you can create a new site either from the main dashboard or the site list by selecting the **‘Create New Site**‘ option.
## **Step 2: Set Up the phpMyAdmin Application** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘**Site Title’** and add relevant ‘**Tags’** to help organize your deployment. At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
## **Step 3: Configure Domain Settings** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
If you select the ‘**Demo Site’** option, xCloud will assign a temporary subdomain for your phpMyAdmin instance. Available subdomain extensions include .wp1.site and .wp1.sh, both managed through Cloudflare. These demo domains are intended for temporary use and should be used for testing and development purposes only.
Note that once a demo site is promoted to a live environment, you cannot revert back to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding.
## **Step 4: Configure and Install the Site** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
At the bottom of the configuration screen, select the appropriate ‘**PHP Version** for your application. Also, ‘Site user’ will be created for this application. Keep it as it is. Once all settings have been reviewed and configured, click the **‘Next**‘ button to proceed.
xCloud will begin provisioning the environment, and within a few minutes, your phpMyAdmin instance will be deployed and accessible from your dashboard.
## **Step 5: Visit the phpMyAdmin Site** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
With phpMyAdmin set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Magic Login’** app. Once you click on the magic login button, you will be redirected to the phpMyAdmin dashboard. Here, you can check out the **‘Database’** of your site from the phpMyAdmin dashboard.
This will open the PHPMyAdmin dialog window for registration, which should look something like the example below. Simply enter your details and create a password according to the specs indicated. Hit the Next button, then click through any additional popups, leaving them empty for now.
## **Managing phpMyAdmin from the xCloud Server Dashboard** [#](/docs/how-to-deploy-phpmyadmin-with-xcloud/)
You can also manage phpMyAdmin from your xCloud server dashboard. Just go to **‘Server’ → ‘Database’** to access the phpMyAdmin options. From there, click **‘Open My phpMyAdmin’** to open the phpMyAdmin dashboard. You can also disable it by clicking **‘Disable phpMyAdmin’**. Additionally, you can create a new database or database user for that server directly from the dashboard.
And that’s it, this is how easily you can quickly and reliably deploy a phpMyAdmin instance using xCloud One Click Apps feature. If you are working in a staging environment or setting up a live application, xCloud provides a streamlined interface for configuring and managing your deployment.
Still, feeling stuck? Contact our [**dedicated support team**](/support/) for further assistance.
---
# How To Easily Disable Email Notifications For Credentials In xCloud Hosting - xCloud
> Go through this simple guide to disable email notifications with xCloud hosting.
Solidify your security measures with [**xCloud**](/) Hosting as we introduce a fresh approach to safeguarding your credentials: **Disable Email Notifications.**
Explore the “**Notification**” section within your settings and opt to disable it if you prefer not to receive server and site credentials. It’s important to note that we do not show any credentials within our system.
**Note: Please make sure to save your credentials somewhere else during site or server creation **as we do not show any credentials in xCloud** for security best practices.
**
If you are stuck, contact our [**support team**](/contact/) for any queries.
---
# How to Disable Notifications With xCloud - xCloud
> xCloud lets you control which notifications you receive and which channels xCloud can use to send them. If you manage many websites or servers, you can reduce
xCloud lets you control which notifications you receive and which channels xCloud can use to send them. If you manage many websites or servers, you can reduce unnecessary alerts by updating your notification settings.
Use this guide to turn off xCloud notifications, disable email alerts, or keep only the notification channels your team needs.
> ⚠️ **Important:** Disabling notifications does not disable the action that created the notification. For example, if you turn off update notification emails, xCloud will stop sending those emails, but your sites and servers can still be updated or managed based on your normal settings.
## What This Setting Controls [#](/docs/how-to-disable-notifications-with-xcloud/)
The xCloud notification page controls notification delivery from xCloud. Depending on your account and integrations, you may see channels such as:
- **Email**
- **Slack**
- **Telegram**
- **WhatsApp**
- **xCloud dashboard notifications**
You can disable one channel and keep another channel enabled. For example, you can turn off Email while keeping Slack or dashboard notifications active.
## Prerequisites [#](/docs/how-to-disable-notifications-with-xcloud/)
- Access to your xCloud account
- Permission to manage your profile settings
- Access to the team or account where the notifications are generated
## Step 1: Open Notification Settings [#](/docs/how-to-disable-notifications-with-xcloud/)
First, log in to your xCloud Dashboard and visit the **Settings → Notifications** from the dashboard or directly visit the [**link**](https://app.xcloud.host/user/notifications). You can also open your user profile menu and select **Notifications**.
## Step 2: Review Each Notification Section [#](/docs/how-to-disable-notifications-with-xcloud/)
On the notification page, review the available sections. You may see sections such as:
- **Site Notifications**
- **Server Notifications**
- **Other Notifications**
- **Vulnerability Notifications**
Each section controls a different group of xCloud alerts.
## Step 3: Disable The Notification Channels You Do Not Want [#](/docs/how-to-disable-notifications-with-xcloud/)
Uncheck the channel you want to disable in each section.
For example:
- Uncheck **Email** to stop email notifications.
- Uncheck **Slack** to stop Slack notifications.
- Uncheck **Telegram** to stop Telegram notifications.
- Uncheck **WhatsApp** to stop WhatsApp notifications.
If you only want fewer emails, turn off **Email** and leave your preferred channel enabled.
## Step 4: Disable Site Notifications If Needed [#](/docs/how-to-disable-notifications-with-xcloud/)
Use **Site Notifications** to control alerts related to your websites. These can include site upgrades, SSL certificate issues, deployment errors, and similar site-level events.
Turn off the channels you do not want under **Site Notifications**.
## Step 5: Disable Server Notifications If Needed [#](/docs/how-to-disable-notifications-with-xcloud/)
Use **Server Notifications** to control server-level alerts. These can include server reboots, unavailable servers, available upgrades, and similar server events.
Turn off the channels you do not want under **Server Notifications**.
## Step 6: Review Other And Vulnerability Notifications [#](/docs/how-to-disable-notifications-with-xcloud/)
If you want to stop all xCloud notifications through a specific channel, review **Other Notifications** and **Vulnerability Notifications** as well.
➡️ For security-related alerts, keep at least one channel enabled if your team depends on xCloud to notify you about important issues.
## Step 7: Save Your Changes [#](/docs/how-to-disable-notifications-with-xcloud/)
Click **Save Changes**.
After saving, xCloud will update your notification preferences.
### Expected Result [#](/docs/how-to-disable-notifications-with-xcloud/)
After saving your settings:
- xCloud stops sending notifications through the channels you disabled.
- xCloud keeps sending notifications through any channels that remain enabled.
- Site and server workflows continue normally.
- Updates are not disabled by changing notification settings.
## Recommended Setup [#](/docs/how-to-disable-notifications-with-xcloud/)
If you manage many websites and want fewer messages, use one of these setups.
### Reduce Email Noise [#](/docs/how-to-disable-notifications-with-xcloud/)
- Turn off **Email** under Site Notifications.
- Turn off **Email** under Server Notifications if you do not want server alert emails.
- Keep one preferred channel enabled for important alerts.
### Stop All xCloud Emails [#](/docs/how-to-disable-notifications-with-xcloud/)
- Turn off **Email** in every notification section where it appears.
- Click **Save Changes**.
- Keep another channel enabled if your team still needs operational alerts.
### Keep Only Important Security Alerts [#](/docs/how-to-disable-notifications-with-xcloud/)
- Turn off nonessential channels under Site Notifications and Server Notifications.
- Keep **Vulnerability Notifications** enabled in your preferred channel.
- Click **Save Changes**.
## Troubleshooting [#](/docs/how-to-disable-notifications-with-xcloud/)
**I still receive emails after turning off Site Notifications**
Check **Server Notifications**, **Other Notifications**, and **Vulnerability Notifications**. Some emails may come from a different notification group.
**I want no xCloud emails at all**
Open the notification page and turn off **Email** everywhere it appears. Then click **Save Changes**.
**I do not see the Notifications page**
Your role may not allow you to manage notification preferences. Ask the team owner or an admin to review your access.
**My team still needs important alerts**
Keep one shared channel enabled, such as Slack or dashboard notifications, while disabling personal email alerts.
## FAQ [#](/docs/how-to-disable-notifications-with-xcloud/)
**Can I disable notifications for all my websites from one place?**
Yes. The notification page controls your xCloud notification delivery preferences, so you can reduce notification emails without opening each website individually.
**Can I disable only Email and keep Slack enabled?**
Yes. Notification channels are controlled separately. Turn off Email and keep Slack enabled if that is your preferred workflow.
**Does this stop WordPress update emails sent directly by WordPress?**
No. This only controls xCloud notifications. WordPress can also send its own automatic update emails from inside each WordPress site. To disable those emails, follow the WordPress update email notification guide.
---
# How To Enable Basic Authentication On Your Site? - xCloud
> In xCloud you can easily configure the basic authentication for your site.
xCloud allows you to add basic authentication to your site. This can be useful for restricting access to a site for security reasons or if you’re simply running a site that needs to restrict access before you even get to WordPress.
Follow the steps below to learn how to enable authentication on your website.
### **Step 1:** Login To Your xCloud Dashboard [#](/docs/how-to-enable-basic-authentication-on-your-site/)
First, from the dashboard, click on the site you want to enable the authentication for, or go to the **“All Sites”** tab and select the site.
### **Step 2:** Enable Basic Authentication Button [#](/docs/how-to-enable-basic-authentication-on-your-site/)
Next, go to the **‘Authentication’** tab and toggle the **authentication** button.
### **Step 3:** Add Required Details [#](/docs/how-to-enable-basic-authentication-on-your-site/)
Now, enter the Username and Password as needed. Click on the **‘Save’** button and you are all set.
Thus, you can easily enable authentication on your site. Getting stuck? Feel free to contact our support team for further assistance.
---
# How to Enable Cloudflare WAF Rules for Site Security in xCloud? - xCloud
> Learn how to enable Cloudflare WAF rules in xCloud to block sensitive file access, prevent author enumeration, and strengthen WordPress security in minutes.
Keeping your WordPress site secure takes more than just strong passwords and regular updates. Many common attacks target areas like XML-RPC, sensitive files, wp-config.php, and author enumeration. If these are left unprotected, your site can become more vulnerable to unauthorized access, spam, and other security threats.
xCloud’s Cloudflare WAF integration lets you activate Web Application Firewall rules directly from your site’s security dashboard — no Cloudflare dashboard required. When you toggle a security option in xCloud, the corresponding WAF rule is automatically created, updated, or deleted in your Cloudflare zone. Rules are stored per-site, so each site on your server can have its own security configuration.
## **What Is Cloudflare WAF?** [#](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/)
Cloudflare’s Web Application Firewall (WAF) filters malicious HTTP traffic before it reaches your server. Custom rules let you block specific attack vectors – such as requests targeting sensitive config files, XML-RPC abuse, or author enumeration scans – at the CDN edge, before the request ever hits your origin. xCloud integrates with Cloudflare WAF via API, so you can manage these rules without leaving the xCloud dashboard.
## **Prerequisites** [#](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/)
- An active xCloud site on a production server
- Cloudflare DNS integration enabled and active for the site (the security card will not appear for sites without active Cloudflare DNS records)
- A valid Cloudflare API token configured in xCloud with WAF rule read/write permissions
- For WordPress-specific options: the site must be running WordPress (these options are hidden for Laravel, custom PHP, and other app types)
That is why Cloudflare Security Settings in xCloud are so important. Instead of manually creating and managing Cloudflare rules, you can quickly enable essential protections directly from your xCloud dashboard. This makes it easier to strengthen your site’s security without going through a complicated setup process.
_
Note: This feature is available for both NGINX and OLS servers._
## **Step 1: Go to Your Site** [#](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/)
First, open the site you want to configure. From your site dashboard, look at the left sidebar menu and navigate to ‘**Tools**, then open **NGINX and Security**. This section contains the settings related to performance and security, including the Cloudflare protections available for your site.
## **Step 2: Open Cloudflare Security Settings** [#](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/)
Once you are inside the **NGINX and Security** section, locate the **Cloudflare Security Settings** area on the dashboard. In this section, you will find several security options that help protect your WordPress site from common vulnerabilities and unwanted access attempts. These options includes:
- **Allow Good Bots + ACME/Let’s Encrypt Validation:** Allows trusted bots and SSL validation requests.
- **Block Sensitive File Access:** Blocks access to private or sensitive files.
- **Block Direct Access to** **wp-config.php:** Protects the main WordPress config file from direct access.
- **Block XML-RPC:** Disables XML-RPC to reduce abuse and attacks.
- **Block Author Enumeration:** Prevents attackers from discovering WordPress usernames.
You can simply use the toggle buttons to enable or disable each setting based on your needs and preferences. After that, click on the ‘Save Settings’ button.
## **Troubleshooting** [#](/docs/how-to-enable-cloudflare-waf-rules-in-xcloud/)
- **The Cloudflare Security Settings card is not showing on the NGINX Security page. →** The card only appears for production sites with an active Cloudflare DNS integration. Verify that Cloudflare DNS is enabled for this site under Site → DNS → Cloudflare. Staging sites do not display this card.
- **WordPress-specific options (wp-config.php, XML-RPC, Author Enumeration) are not visible. →** These options only appear for WordPress sites. If your site runs Laravel, custom PHP, or another stack, these options will not be shown.
- **Saving settings returns an error. →** Check that your Cloudflare API token has WAF custom rules read and write permissions. Tokens with zone-level read-only access will fail. You may also be hitting Cloudflare’s API rate limits — wait a moment and try again.
- **A rule was enabled but does not appear in the Cloudflare WAF dashboard.** → xCloud applies changes only to settings that differ from the current state. If a rule already exists in Cloudflare from a previous session, it may not be recreated. Check Cloudflare’s WAF Custom Rules list directly. If the rule is missing, toggle the option off, save, then toggle it on again and save.
- **I disabled a rule but it still appears in Cloudflare.** → Cloudflare may take a few seconds to propagate rule deletions. Refresh the Cloudflare WAF page after ~30 seconds. If the rule persists, check xCloud logs for API errors related to the delete operation.
And that’s it this is how easily you can configure Cloudflare security settings in xCloud. Cloudflare Security Settings in xCloud give you a simple way to add important protection to your WordPress site without manually configuring security rules in Cloudflare. With just a few clicks, you can block common attack vectors, protect sensitive files, and improve your site’s overall security posture.
---
# How to Enable HTTP/3 in xCloud for Enhanced Website Performance - xCloud
> Learn how to enable HTTP/3 in xCloud to boost website speed, security, and user experience with simple steps for both new and existing sites.
HTTP/3, the latest version of the Hypertext Transfer Protocol, brings significant improvements over earlier versions.
xCloud has already supported HTTP/3 on OLS (OpenLiteSpeed) servers. Now, this support is also available for NGINX servers. This means you can create and run websites on the HTTP/3 protocol whether you are using OLS or NGINX. In this guide, we will show you how to enable HTTP/3 for both new and existing sites on NGINX servers.
## **What Is HTTP/3 and Why Is It Important?** [#](/docs/how-to-enable-http-3-in-xcloud/)
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on top of QUIC, a transport layer protocol developed by Google. Unlike HTTP/2, which relies on TCP, HTTP/3 operates over UDP. This enables faster connection establishment, elimination of head-of-line blocking, improved performance on unreliable networks, and enhanced security.
### **Reduced Latency** [#](/docs/how-to-enable-http-3-in-xcloud/)
QUIC combines the transport handshake and encryption handshake into a single process. This reduces the number of round trips required to establish a secure connection and leads to faster page loads for visitors.
### **Elimination of Head-of-Line Blocking** [#](/docs/how-to-enable-http-3-in-xcloud/)
In HTTP/2, the loss of a single data packet can delay all other data streams. HTTP/3 processes each stream independently, ensuring that only the affected stream is delayed. For example, if you are chatting with an AI tool like ChatGPT and one response segment is delayed, HTTP/3 ensures that other parts of the chat, such as text already loaded or supporting images, continue to display without interruption. This independent processing improves the loading speed of site assets such as images, CSS, and JavaScript files.
### **Improved Performance on Unreliable Networks** [#](/docs/how-to-enable-http-3-in-xcloud/)
HTTP/3 supports connection migration, allowing users to maintain uninterrupted connections even when switching networks, such as from Wi-Fi to mobile data. This ensures a seamless browsing experience for visitors using mobile devices or unstable networks.
### **Enhanced Security** [#](/docs/how-to-enable-http-3-in-xcloud/)
QUIC is encrypted by default. HTTP/3 leverages this encryption to provide a more secure connection without additional configuration, protecting user data and communications.
## **How to Enable HTTP/3 in xCloud for New Sites**? [#](/docs/how-to-enable-http-3-in-xcloud/)
For all new websites deployed on xCloud, HTTP/3 support is enabled automatically if the server runs NGINX version 1.25.0 or higher. Site owners do not need to take any additional steps. New sites are provisioned with all necessary server configurations and SSL/TLS settings to ensure full compatibility with HTTP/3 for supported browsers and clients.
## **How to Enable HTTP/3 on Previously Deployed Sites** **on NGINX Servers** [#](/docs/how-to-enable-http-3-in-xcloud/)
For sites deployed before HTTP/3 support was deployed from xCloud, you need to regenerate NGINX to enable HTTP/3. Here are the steps to regenerate the permissions of the rescue site associated with each domain.
👉 Note: xCloud already supports HTTP/3 on OLS (OpenLiteSpeed) servers by default. For NGINX servers, follow the steps below to enable HTTP/3.
### **Step 1: Login and Select the Site** [#](/docs/how-to-enable-http-3-in-xcloud/)
To reset the file and folder permissions of your site. First, log in to your xCloud dashboard,go to your website where you want to activate HTTP/3. Now, go to the ‘Site settings’ option from the left navigation bar.
### **Step 2: Reset the Permissions** [#](/docs/how-to-enable-http-3-in-xcloud/)
Then roll down a little and toggle on the **‘Regenerate NGINX Configurations’** option to enable and then enable the **‘Restart NGINX’** option as well and click on the **‘Run Now’** button.
This is how easily you can reset the files and folder permissions and enable HTTP3 for your sites.
## **How to Verify HTTP/3 Activation for Your Site** [#](/docs/how-to-enable-http-3-in-xcloud/)
After regenerating permissions, verify that HTTP/3 is active by opening an online tool such as [**HTTP3 Check**](https://http3check.net/) to confirm that the site serves content over HTTP/3.
Enabling HTTP/3 in xCloud improves website performance, security, and user experience. New sites automatically benefit from HTTP/3, while existing sites can enable it by regenerating the rescue site permissions. Advanced users may also configure HTTP/3 manually if desired. This upgrade ensures faster, more reliable connections for all visitors, including those on mobile or unstable networks.
---
# How to Enable WebP For NGINX Server With xCloud - xCloud
> Read how to enable WebP for NGINX server with xCloud and discover a simple way to boost site speed with smarter image delivery.
WebP is a modern image format developed by Google that offers superior compression for images on the web, helping improve site load times without compromising quality. Enabling WebP support on your server ensures that browsers capable of displaying WebP images will automatically receive them, while others continue to receive standard PNG or JPEG formats.
Learn how to enable and configure WebP for NGINX server with xCloud to serve WebP images efficiently.
## **Step 1: Go to The NGINX Customization** [#](/docs/how-to-enable-webp-for-nginx-servers/)
To begin, log into your **xCloud dashboard** and navigate to the site where you want to enable WebP support. From the left-hand menu, click on **‘Tools’** and then select **“NGINX Customization.”** This section allows you to safely modify server configurations.
## **Step 2: Add the Config Content for Before Server Block** [#](/docs/how-to-enable-webp-for-nginx-servers/)
The first step is to add a custom configuration **before the server block**. Click the **“Add a New Config”** button, and when the popup appears, set the **Config Type** to _Before Server Block_. Name the configuration something descriptive. Then, in the **Config Content** field, paste the following code:
before:
Copy to clipboard
1
2
3
4
5
6
7
8
map $http\_accept $webp\_suffix {
default "";
"~\*webp" ".webp";
}
After pasting the code, click the **“Save Config”** button to apply the changes.
## **Step 2: Add the Config Content for Inside Server Block** [#](/docs/how-to-enable-webp-for-nginx-servers/)
Next, you’ll need to handle how NGINX serves WebP images by modifying the configuration **‘Inside the Server Block’**. Again, click **“Add a New Config”**, and this time select _Inside Server Block_ for the **Config Type**. Give this a configuration file name then paste the following into the **Config Content** field:
Inside:
Copy to clipboard
1
2
3
4
5
6
7
8
location ~\* ^.+\\.(png|jpe?g)$ {
add\_header Vary Accept;
try\_files $uri$webp\_suffix $uri =404;
}
Then, click the **“Save Config”** button to apply the changes. Once this second configuration is saved, your server is ready to start serving WebP images automatically when possible.
And that’s it. This is how easily you can enable WebP for NGINX server with xCloud. With this, your xCloud server is now optimized to serve WebP images to supported browsers, improving site performance and efficiency.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How to Find The Redis Credentials? - xCloud
> Learn how to find the redis credentials for your website in NGINX and OLS server.
Redis credentials are essential for accessing and managing your Redis database. To find the Redis credentials, you need to access specific configuration files either via a File Manager for individual sites or through SSH for broader access.
## **Find Redis Credentials in NGINX and OLS For Individual Sites** [#](/docs/how-to-find-the-redis-credentials/)
You can access the Redis credentials for NGINX servers directly from the xCloud dashboard as well. By following the steps, you can efficiently locate and utilise your Redis credentials for NGINX and OLS servers and manage your Redis database easily.
### **Step 1: Select Your Site** [#](/docs/how-to-find-the-redis-credentials/)
To find the Redis credentials, go to the **‘Site’** and head over to the [**Caching option**](/docs/how-caching-works-in-xcloud/) from the left navigation bar. For the NGINX servers, go to the ‘**WordPress’ → ‘Caching’** option.
### **Step 2: Access Your Redis Credentials** [#](/docs/how-to-find-the-redis-credentials/)
Here, can see the Redis credentials such as **‘Redis User’**, **‘Redis Password’** and **‘Redis Object Cache Key**’ options.
And from the OLS servers, go to the **‘WordPress’ → ‘Caching’ option and find the credentials under the LiteSpeed Cache.**
## **Using SSH to Find All Redis Credentials** [#](/docs/how-to-find-the-redis-credentials/)
You can also find the Redis credentials through the terminal as well. Open the terminal (on macOS or Linux) or command prompt (on Windows) to use SSH. Enter the following command to navigate to the directory where the Redis ACL file is located: /etc/redis/users.acl Here you will get the user and password of the Redis credentials
This is how easily you can find Redis credentials using the xCloud dashboard easily or using the command line of your device
Still stuck? Feel free to reach out to our [**support team**](/contact/) for further assistance.
---
# How To Fix Failed Free SSL Issue in xCloud - xCloud
> Here is the step-by-step guideline on how to fix a filed Free SSL issue if it appears while using xCloud.
With xCloud you will get a Free Let’s Encrypt Certificate. After adding a website, subdomain, or parked domain to your xCloud server, an SSL will be installed automatically. This process can require 1-2 hours to complete and for the SSL to appear as active. If you see a Failed SSL/HTTPS status on the SSL on your xCloud dashboard, a failed status will appear:
If more than two hours have passed and the SSL failed status still appears, there are a few things you can check in order to solve this issue.
## **DNS Problem** [#](/docs/how-to-fix-a-failed-free-ssl-issue/)
Use the DNS Checker tool to confirm that your domain is pointing correctly and that the records are fully propagated. Visit your DNS provider and check if you have added the correct IP addresses for your DNS records.
## **Reinstall SSL Certificate** [#](/docs/how-to-fix-a-failed-free-ssl-issue/)
If you are using our xCloud Free SSL, uninstall it and install a new SSL again. You can easily reinstall it by disabling and enabling the toggle button from SSL settings under SITE.
## **Not Secure or Not Private Connection Error** [#](/docs/how-to-fix-a-failed-free-ssl-issue/)
You may also face ‘**ERR\_SSL\_PROTOCOL\_ERROR**’ or ‘**NET::ERR\_CERT\_AUTHORITY\_INVALID**’ issues. To solve this issue, clear your browser history and cache, or check the website using incognito mode.
Afterward, if the issue stays check your SSL certificate validity with the SSL Checker tool.
That is how easily you can fix failed free SSL issue in xCloud**.**
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How to Fix openclaw.json - xCloud
> The openclaw.json file controls how OpenClaw operates within your environment. If the file contains invalid syntax, missing fields, or incorrect configuration
The openclaw.json file controls how OpenClaw operates within your environment. If the file contains invalid syntax, missing fields, or incorrect configuration values, OpenClaw may fail to initialize or execute workflows properly.
Follow the guide to identify and fix issues in the configuration file using secure access and proper validation.
## **1\. Locate the openclaw.json File** [#](/docs/how-to-fix-openclaw-json/)
Start by identifying where the openclaw.json file exists in your project or server. Check the root directory of your application or the specific configuration folder used by your deployment setup.
Confirm which environment you are working in, such as local, staging, or production, and ensure that the system actually references that specific file. If multiple environments exist, verify that you are editing the correct version to avoid unintended configuration conflicts.
## **2\. Provide SSH Access to the Agent** [#](/docs/how-to-fix-openclaw-json/)
Grant SSH access using your organization’s secure internal method. The agent must be able to read and edit the openclaw.json file directly on the server. In addition to file access, ensure the agent can run basic validation commands and any necessary project-level checks.
SSH access enables the agent to inspect the live configuration, test changes in context, and resolve issues without requiring manual file transfers.
## **3\. Share the Official OpenClaw Documentation** [#](/docs/how-to-fix-openclaw-json/)
Provide the agent with the official OpenClaw documentation link that defines the required fields, optional fields, allowed values, and schema rules. Clear documentation ensures that the agent matches your configuration precisely to the expected structure.
This step prevents assumptions and ensures that every field aligns with the platform’s current configuration standards.
## **4\. Ask the Agent to Validate and Repair** [#](/docs/how-to-fix-openclaw-json/)
Once access and documentation are available, instruct the agent to validate the JSON file and repair any errors. The agent should check for syntax issues, missing fields, incorrect values, and structural mismatches.
After applying corrections, it should revalidate the file to confirm that the configuration meets the required schema. This structured validation process ensures the file works correctly without guesswork or repeated manual edits.
Fixing openclaw.json becomes straightforward when you follow a structured approach. Confirm the correct file location, provide secure SSH access, share the official documentation, and request full validation and repair.
This method allows you to resolve configuration issues efficiently and restore proper OpenClaw functionality without rebuilding your environment.
---
# How To Fix WordPress Updates Not Working Issue - xCloud
> Here is the documentation on how to fix WordPress updates not working issues if it appears while using xCloud.
With xCloud you can easily update your WordPress plugins. However, if you face WordPress updates not working, there might be a few issues you are having. Let’s go below and see how to fix them.
## **WP-CLI Not Working** [#](/docs/how-to-fix-wordpress-updates-not-working-issue/)
Some plugins may cause issues with WP-CLI. If that is the reason your WordPress updates not working you can see this on the ‘**Sites**’ → ‘**Event**’ tab. Identify the plugin and disable it to fix the WP-CL issue. Please reach out to [**our** **support team**](/contact/) if you face any other issues.
## **PHP Version Not Supported** [#](/docs/how-to-fix-wordpress-updates-not-working-issue/)
If your WordPress updates are not working, see that the WordPress installation, theme, plugins, etc. that you are using all are compatible with the most recent version of PHP supported by your hosting account. You can determine the support and end-of-life status of your version as well as other versions by consulting the table labeled PHP Supported Versions.
_**NOTE:** It is possible that your installation will not support the most recent version of PHP if the various components of your installation do not support it. You can restore PHP to its most recent or older version through the xCloud Settings page under Site. You can roll it back to the most recent version._
## **Low Disk Storage** [#](/docs/how-to-fix-wordpress-updates-not-working-issue/)
If you don’t have sufficient disk storage on your server, WordPress updates might not work. Make sure that your server has sufficient free space to allow you to download, unpack, and then replace the plugin files.
## **Plugin Compatibility** [#](/docs/how-to-fix-wordpress-updates-not-working-issue/)
WordPress updates might not work when the plugin you are updating is not ready for the WordPress version that you are using. Make sure that the plugins being updated are compatible with the WordPress version you are using. Some plugins may not be ready for the latest version of WordPress.
## **Cache & Caching Plugins** [#](/docs/how-to-fix-wordpress-updates-not-working-issue/)
Cache and caching plugins may interfere with the WordPress update process. You need to clear any caching mechanisms on your server, including caching plugins to fix the issue.
That is how easily you can fix WordPress updates not working issue in xCloud.
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How To Generate and Add SSH Keys In xCloud? - xCloud
> Learn how to generate and add SSH keys in xCloud following easy and simple steps.
Adding an SSH (Secure Shell) key to your server is a security measure and a method of authentication. SSH keys are used for secure, encrypted communication between your local computer (or client) and a remote server. With [**xCloud**](/), you can easily generate and add SSH keys to your server to keep the server secure from unauthorized access.
## **How To Add SSH Keys To Your xCloud Account** [#](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
Follow the step-by-step instructions below to generate and add SSH keys, and delete them as well from your xCloud server.
### **Step 1: Access Your xCloud Settings** [#](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
Log in to your xCloud account and visit the **‘SSH key’**option under your account settings.
### **Step 2: Add Your Public SSH Key To The xCloud SSH Keys Settings** [#](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
To add a public SSH key to your xCloud click on the **“Create New SSH Key”** button, and paste your Public SSH Key.
What if you do not have an SSH key yet? Let’s learn how you can generate an SSH Key from scratch.
## **How To Generate An SSH Key?** [#](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
To create a new SSH key, open a terminal and execute the given command:
**ssh-keygen -t rsa -b 4096 -C “your\_email@example.com**
Replace **“your\_email@example.com”** with a unique identifier to distinguish this SSH key (it doesn’t have to be an email address).
When prompted to select a file to store the key, press Enter to accept the default location **(~/.ssh/id\_rsa)**.
When asked to set a passphrase, you can leave it empty by pressing Enter. Alternatively, for an additional layer of security, you have the option to assign a passphrase to the SSH key.
However, keep in mind that using a passphrase will require you to enter it each time the SSH key is used.
If you are a Mac user then you can easily open your Terminal and paste the following command to copy the public SSH key in your clipboard.
**pbcopy < ~/.ssh/id\_rsa.pub**
Still unable to generate an SSH key? Please refer to the following guides:
- [**Generate SSH Key on Mac**](https://www.digitalocean.com/community/tutorials/how-to-create-ssh-keys-with-openssh-on-macos-or-linux)
- [**Generate SSH Key on Windows with Putty**](https://docs.digitalocean.com/products/droplets/how-to/add-ssh-keys/create-with-putty/)
Or contact our support for further help. After successfully adding the SSH key, it will be displayed in the **“SSH Key”** section in your xCloud dashboard.
## **Let’s Add The SSH Key To xCloud Servers** [#](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
While adding the SSH key, you may also assign it to a server by creating a Sudo User with it as shown below. Make sure, you click on ‘Save’ after setting your default sudo user & password.
**Want to assign an SSH key always to new provision servers?**
While adding an SSH Key you can check the marked option shown below in xCloud to add an SSH key automatically to newly provisioned servers instead of doing it manually every time.
## **How To Delete SSH Key From The xCloud** **Dashboard** [#](/docs/how-to-generate-and-add-ssh-keys-in-xcloud/)
To delete an SSH key from the xCloud dashboard, go to ‘**Settings**‘ and select ‘**SSH Key**‘ from the sidebar or use the direct link **[visit this link](https://app.xcloud.host/user/ssh-key)** to access the page quickly. Then, click the ‘**Delete**‘ icon under the **‘Actions**‘ column next to the key you want to remove.
This is how you can easily generate and add SSH keys & to your xCloud server. Plus, you can delete your keys if you don’t need them.
Still confused or if you need any help with anything? Contact our **support team** right away.
---
# How To Generate Custom Invoices in xCloud? - xCloud
> Learn how to generate custom invoices for all payments in xCloud and download from this documentation.
In [**xCloud**](/) you can easily generate custom invoices for all payments. If you require the inclusion of specific contact or tax details on your receipts, such as your VAT identification number, or registered address on the invoice you can add any of this information on your invoice with ease, Follow the step-by-step guideline below to generate custom invoices.
## Step 1: Add Extra Billing Information [#](/docs/how-to-generate-custom-invoices/)
First of all, from your dashboard click on the ‘**Profile**’ button. Then add ‘**Name on Invoice**’ and ‘**Extra Billing Information**’ as you need. Add your contact, and tax details like VAT identification number, or registered address there.
## Step 2: Download Your Invoice [#](/docs/how-to-generate-custom-invoices/)
Now, go to the ‘**Invoices**’ tab and click on the ‘**Download**’ button on the invoice that you need. Your invoice will be downloaded with the added extra billing information.
That’s it. This is how you can generate customer invoices in xCloud.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How To Setup A Vultr Server in xCloud and Get Free Hosting For 6 Months? - xCloud
> With xCloud, we are giving free hosting with Vultr for 6 months.
**[xCloud](/)** is your all-in-one hosting solution where you will get a seamless, automated service with advanced server and site management. Our [**Vultr**](https://www.vultr.com/?ref=9536083) and xCloud partnership offers Free hosting for **Six months** for Vultr servers. By simply signing up for **Vultr** using the code “XCLOUD25”, you’ll receive **$100** in free credits. Also, new signups in xCloud allow users to create **1 server and 10 site for free** using the **Bring Your Own Server** service.
Now let’s follow some simple steps on how you can avail of the free hosting and management offer to start your xCloud journey without any cost.
## **Step 1: Sign Up For xCloud With Credentials** [#](/docs/how-to-get-free-hosting-with-vultr/)
To get started, first, you have to sign up for xCloud. Simply, put your credentials and get started.
## **Step 2: Integrate your Vultr Account in xCloud** For Free Hosting [#](/docs/how-to-get-free-hosting-with-vultr/)
After logging in to your xCloud account, start by adding a new server by clicking on the “**Create New Server**” button from your dashboard.
The next screen will provide the list of our available services. For this tutorial, we will create a **Vultr** server and for that select the **Vultr** option under “Bring your own server service”. The billing of the server will be handled on your Vultr account and in xCloud we won’t charge for this first server.
_Note:_ _Check out the documentation below to find out how to provision a server with other major providers:_
- [**How To Set Up a Server with Digital Ocean in xCloud?**](/docs/how-to-setup-your-server-with-digital-ocean/)
- [**How To Setup a Server With Google Cloud Platform in xCloud?**](/docs/first-server-with-google-cloud-platform/)
- [**How To Connect a Server From Any Provider in xCloud?**](/)
### **Signup in Vultr with xCloud Promo** [#](/docs/how-to-get-free-hosting-with-vultr/)
To get started with the free hosting offer, head over to [Vultr.com](https://www.vultr.com) and sign up for a new account. During the registration process, you’ll need to link a **valid credit card** or a **verified PayPal account** to activate your account and be eligible for the $100 promotional credit. As part of the validation, Vultr will place a **small temporary authorization** on your credit card—approximately **$2.50 USD**—to verify your payment method. This charge is not permanent and will be automatically reversed by your bank, although depending on your bank’s policy, it might take up to **30 days** for the funds to be released.
If you choose to verify using **PayPal**, note that Vultr requires a **minimum payment of $5.00 USD** for validation. Additionally, PayPal must be linked to a **valid credit card or bank account** to complete this verification process. Once your payment method is verified and your account is deemed eligible, the **$100 in free credits** will be automatically applied to your account. Make sure to use the **promo code “XCLOUD25”** during the sign-up to claim this offer.
_Note: If you already have a Vultr account then please skip this step and check how to collect API from Vultr._
### **Collect API key from Vultr** [#](/docs/how-to-get-free-hosting-with-vultr/)
After you have successfully completed setting up your billing method, you will need to get the Vultr API key to add it to xCloud to create and manage 1 server and 10 sites for free. Navigate to the **Account → API** tab from your Vultr dashboard. After that click on the ‘**Enable API**’ button.
Now, your ‘**Personal Access Token**’ will be auto-generated. Copy the API Key/Token.
Please make sure you have added Any IPv4 and Any IPv6 both under Access Control
Now, you need to go back to the xCloud dashboard and add your Vultr Label & API Key.
### **Add Team Members In Vultr** [#](/docs/how-to-get-free-hosting-with-vultr/)
If you want your team members to use xCloud with Vultr, then make sure these permissions are given.
### **Add Vultr API key in xCloud** [#](/docs/how-to-get-free-hosting-with-vultr/)
Thanks to xCloud, you can create your first server without spending any money. Now, click on ‘**Add New Server’** from the xCloud dashboard, and you will be redirected to the server selection screen. Then click on ‘**Vultr**’ to proceed further.
After selecting ‘**Vultr**’, set your ‘**Key**’, ‘**Vultr Label**’, and ‘**Vultr API Key**’. Then click on ‘**Verify**’.
## **Step 3: Create a Vultr Server in xCloud** [#](/docs/how-to-get-free-hosting-with-vultr/)
Now you have successfully verified your Vultr account, you will need to add other details to create a server in Vultr using xCloud. Choose your **Region**, **Database Server**, **Server Size,** and much more from one easy dashboard.
After putting all the information, click on **‘Next’** and xCloud will automatically install and set up everything for you in a few minutes.
## **Step 4: Create A New Free Site** [#](/docs/how-to-get-free-hosting-with-vultr/)
Once your server is connected, you can create a site from the Dashboard or Site List by clicking on the button “**Create New Site**”. Then you will need to select the server on which you want to install your WordPress website.
As we will be creating a fresh WordPress site choose the “I**nstall New WordPress Website**” options as shown below.
Now all you have to do is install and Go Live with your WordPress Site. You can do the next process with 3 simple and easy steps.
1. Add a **Site Title**
2. Add **Tags** if you want
3. Choose to **Go Live**
4. **DNS Configuration:** If you add the domain and want to visit the live site you need to configure your DNS. xCloud does not handle your DNS but all you need to do is remove any existing A records and add the A record as shown above. For example, if your domain is on Cloudflare then all you need to do is add an A record with the domain name, and your server IP address.
To use a **Free SSL certificate** by **Let’s Encrypt** simply turn on the HTTPS enable button and xCloud will automatically set everything for you.
_Note: Make sure you have pointed your domain to the server with A record and turn off the proxy of Cloudflare._
You can then simply hit the Next Button to create your site and **Go Live** instantly.
### **Configure Advanced Settings** [#](/docs/how-to-get-free-hosting-with-vultr/)
By default, the WordPress admin credentials are autogenerated to speed up the site creation process. As soon as your site is deployed you will receive your Site credentials on your email address. Later on, you can update your password if needed. From “**More Advanced Settings**” you can update the default **Admin Username**, **Admin Password, Admin Email Address,** etc. along with other additional settings from here.
After the previous step, click on the ‘**Next**’ button. It might take only 1-2 minutes to create your WordPress site.
### **Not Ready Yet? Try Staging Environment** [#](/docs/how-to-get-free-hosting-with-vultr/)
Also, If you do not want to point your domain yet then xCloud offers temporary domains to make your site live with every Site creation method available in xCloud. For that select the **Staging Environment** option.
## **Step 5: Configure Email Address for your WP Site** [#](/docs/how-to-get-free-hosting-with-vultr/)
For users on managed hosting services like WPEngine, Runcloud, and Cloudways, email providers like Office 365, GSuite, and MXroute are commonly used. If you are migrating from cPanel/Plesk, new email hosting is needed. xCloud doesn’t automatically include email setup for your sites. WordPress often requires reliable transactional email delivery, but default systems can fail, causing spam or delivery issues. Using services like Mailgun for efficient email delivery is recommended. The process of setting up and configuring Mailgun for WordPress can be found below.
👉 [**Setting Up Site Emails For WordPress ON xCloud**](/docs/setting-up-site-emails-for-wordpress-on-xcloud/)
That’s it! You’ve successfully created a site in xCloud with free hosting with Vultr. Now you can start working on your website, customize it, install themes/plugins (if applicable), and take advantage of xCloud’s optimized server environment for seamless site management.
Still stuck? Contact our **support team** for any of your queries.
---
# How to Go Live From Demo Site With Custom Domain? - xCloud
> Learn how to go Live from demo site with your custom domain on xCloud easily in just a few clicks.
With xCloud, you can easily create a demo site in a few clicks and test everything before going live. A demo site serves as a test website where you can migrate sites, run experiments, use all necessary plugins and themes, and also go Live with a custom domain. But ever wondered how you can go live from a demo site with custom domain using xCloud?
Follow the steps below to go live from the demo site with a custom domain on xCloud
First, click on the **‘Domain’** → **‘Go Live’** option from the dashboard. Then go to the **‘Domain Setup’** section. Enter your **‘Domain name’** in the field.
Then go to the ‘**DNS Setup’** section from the dashboard and add the records to your domain provider and verify the DNS.
If you are using Cloudflare for DNS management, you can [follow this guide](/docs/using-xcloud-with-cloudflare-for-dns-management/) for DNS Management with Cloudflare.
After that, click on the **‘Save’** button to complete the process. From the xCloud dashboard, you can easily go live from the demo site with a single click.
* * *
Want to learn about how to set up your DNS records?
[**_Read the documentation_**](/docs/how-to-setup-dns-record-in-xcloud-server/)
Still stuck? Contact our [support team](https://support.xcloud.host/) for any of your queries.
---
# How To Go Live From Staging Domain? - xCloud
> We can easily go live from staging site with a single click with the help of xCloud.
Testing changes before making them live is crucial for your website’s stability. It avoids errors and saves time and effort in resolving issues that may arise otherwise.
First, click on the **Staging** option. Here you will get a brief overview of your entire **Staging Management** system.
From the **[xCloud](/)** dashboard, you can easily go live from staging domain with a single click.
Now, simply click on the **Go Live** option. After clicking, you need to add your necessary information like **Domain Name, Additional Domain.** You can also, enable HTTPS for more security.
Still stuck? Contact our **[support team](https://support.xcloud.host/)** for any of your queries.
---
# How to Deploy Buzz Workspace with xCloud (One Click Apps) - xCloud
> Learn how to install the Buzz app and deploy your Buzz relay server on xCloud with One Click Apps. No manual Docker or NGINX setup needed.
Buzz is an open-source workspace where you and your AI agents share the same room. Instead of jumping between a chat app, a terminal, and half a dozen tabs, you get one place where people and agents talk, hand off work, and keep the context in view.
To run a Buzz community, you need two things: the desktop app on your machine, and a relay server that your community connects through. The app takes a couple of minutes. The relay is the part that usually means picking a provider, spinning up a Docker host, wiring NGINX, and handling SSL yourself.
That is what xCloud’s removes with fully managed [**Buzz Hosting**](/buzz-hosting/). You create a Docker + NGINX server, pick Buzz from the One Click Apps list, paste in your public key, and xCloud handles the rest. No manual container setup, no config files, no waiting on a DNS record if you just want to test things first, a free demo domain works fine.
Follow this guide to install the Buzz app and setting up your identity, then deploying your Buzz relay on xCloud from start to finish.
## Create A Docker+ Nginx Server With xCloud [#](#create-a-docker-nginx-server-with-xcloud)
### Step 1: Create a Docker+ NGINX Server [#](#step-1-create-a-docker-nginx-server)
First, create a Docker server to deploy Buzz. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Buzz either on your [own server](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy the server with xCloud. You can either use an [xCloud Managed Server](/managed-hosting/) or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the ‘Server Name’, set the ‘App Type’ to Buzz(it is optional to select), and add any relevant ‘Tags’ to help identify your server later.
Next, you can see the ‘Docker + NGINX’ stack is already selected, which is mandatory for deploying the Buzz application.
Next, choose the server options based on your requirements. Then, select a plan that best fits your needs, then click the ‘Create’ button to proceed.
Once the server is created, you will be able to deploy your Buzz Application on this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## Create The Buzz Application on xCloud [#](#create-the-buzz-application-on-xcloud)
### Step 2: Go to One Click Apps & Choose Buzz [#](#step-2-go-to-one-click-apps--choose-buzz)
Next, from your dashboard, click the ‘One Click Apps’ button and choose ‘Buzz’.
### Step 3: Set Up the Buzz Application [#](#step-3-set-up-the-buzz-application)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘Site Title’ and add relevant ‘Tags’ to help organize your deployment.
Here, you will see site deployment options. From here, proceed with the ‘Go Live’ option or the ‘Demo Site’ option. For Go Live you need to have a custom domain. For this tutorial we are going with the demo domain that is free from xCloud.
Once you choose the Demo site, you will see that xCloud assigns you a free demo domain.
### Step 4: Collect the Relay Owner Public Key [#](#step-4-collect-the-relay-owner-public-key)
Next, you need to collect the Public key (hex) in the Relay Owner Key field and click on the ‘Next’ button.
> To collect the Relay Owner Public Key, you first need to install the Buzz app and follow the instructions starting from Step 6. Do not close this tab or stop the setup process. Once you have collected the key, return to this page and paste it into the Relay Owner field.
After you collect the key, enter it and click on the ‘Next’ button to start deploying the application.
### Step 5: Visit the Application [#](#step-5-visit-the-application)
After completing the setup, you will be able to visit your Buzz app. From the dashboard, click the ‘Visit Site’ button to access your Buzz Community Link.
## Install The Buzz App In Your Device [#](#install-the-buzz-app-in-your-device)
### Step 6: Download & Install the Buzz App [#](#step-6-download--install-the-buzz-app)
First visit the official [website](https://buzz.xyz/) of Buzz and click on the ‘Get the App’ to download and install the app on your Mac device.
After completing download, install the app on your device. Drag and drop the App on your Application folder and it will instantly start installing on your device.
### Step 7: Open Your Buzz App In Your Device [#](#step-7-open-your-buzz-app-in-your-device)
Open the ‘Buzz’ from your device. It will ask whether you want to create a new identity or want to use an existing key. Here we are choosing the ‘Create a new identity key’ option.
Next you will get an unique identity key. Copy the key and store it somewhere safely.
### Step 8: Setup Your AI Agents [#](#step-8-setup-your-ai-agents)
Then it will ask you to install the Claude Code or OpenAI Codex, whichever you prefer. Click on the Install button of your preferred AI Agent button, complete the authorization process. Then hit on the next button.
### Step 9: Join A Community [#](#step-9-join-a-community)
Then, you will get three options. From here choose ‘Join a community’ as you will create your community server with xCloud .
Here you well get a public ID. Copy the ID and visit this site [NostrTool](https://nostrtool.com/).
### Step 10: Go to The NostrTool Site [#](#step-10-go-to-the-nostrtool-site)
Next visit the NostrTool and choose the “Load a pubkey from npub/hex” option. Then enter the key you had copied from the Buzz app and click on the ‘Load Button. Then You will find a ‘Nostr public key (hex)”. Copy it and store somewhere safe.
You need to add this key as ‘Relay Owner Public Key’ inside the xCloud dashboard that is mentioned in [Step 5](https://xcloud.host/docs/how-to-install-buzz-with-xcloud-one-click-apps/#step-9-enter-the-relay-owner-public-key).
Once you collect the key, go back to the xCloud dashboard and enter the key and complete the application setup process.
## Step 12: Complete the Community Setup [#](#step-12-complete-the-community-setup)
Next come back to the Buzz app and enter the site URL where your are deploying the community in xCloud with a “wss” prefix. Remember you need to enter “wss” instead of “https” or “http” before the URL. After that click on the Next button
You will be asked to enter a username and a profile picture for your Buzz profile.
Once done, you will see that Buzz is almost ready, asking you to talk to the agents. Click the ‘Talk me to Buzz’ button. It will take you to the interface.
Once done, you will be in the Buzz app, where you can create agents as you prefer.
That’s it. Your Buzz relay is live on xCloud, your app is connected to it, and your community is ready for people and agents to start working in.
[**Deploy Buzz Now**](/buzz-hosting/#pricing)
From here you can add agents, invite teammates with a link, and swap the demo domain for your own custom domain whenever you’re ready to go live properly. Your server keeps running under xCloud’s management, so backups, SSL renewals, and updates are handled without you touching the command line.
If you get stuck at any point, our support team is available around the clock from your xCloud dashboard.
---
# How to Install ionCube Loader Using SSH for Nginx and OpenLiteSpeed - xCloud
> Learn how to install ionCube Loader using ssh for Nginx or OpenLiteSpeed with step by step guide.
ionCube Loader is a PHP extension that decodes and executes PHP files that have been encoded using the ionCube Encoder. This is often needed when running commercial PHP software.
This guide will show you how to install ionCube Loader on a Linux server such as Ubuntu, Debian, or CentOS using SSH. Let’s go through the steps to install ionCube loader using SSH for the **Nginx** and **OpenLiteSpeed (OLS)** web servers.
## **Step 1: Connect to Your Server** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
You first need to connect to your server using SSH. Open your terminal and run the command below, replacing username and your\_server\_ip with your actual server login details.
ssh username@your\_server\_ip
Copy to clipboard
1
2
ssh username@your\_server\_ip
## **Step 2: Check Your PHP Version** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Before downloading the loader, you must know which version of PHP is installed on your server. This will determine which loader file you need to use.
Copy to clipboard
1
2
php -v
The output will show your PHP version. For example:
Copy to clipboard
1
2
3
4
PHP 8.1.28 (cli) (built: Apr 15 2024 14:34:08) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.28, Copyright (c) Zend Technologies
From this, collect the version numbers. For example, you have PHP **8.1**, which means you will use a loader file named ioncube\_loader\_lin\_8.1.so.
## **Step 3: Download and Extract ionCube Loader** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Now, download the ionCube Loader package into a temporary directory and extract it.
Copy to clipboard
1
2
3
4
5
6
7
8
# Navigate to the temporary directory
cd /tmp
# Download the latest loader package for 64\-bit systems
wget https://downloads.ioncube.com/loader\_downloads/ioncube\_loaders\_lin\_x86-64.tar.gz
# Extract the archive
tar -xzf ioncube\_loaders\_lin\_x86-64.tar.gz
This will create a new folder named ioncube inside /tmp.
## **Step 4: Find Your PHP Extension Directory** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
PHP needs to know where to load extensions from. Run the following command to find the extension directory path.
Copy to clipboard
1
2
php -i | grep extension\_dir
The output will look similar to:
filename.js
Copy to clipboard
1
2
extension\_dir => /usr/lib/php/20210902 => /usr/lib/php/20210902
Copy this path. You will use it when placing the loader file in the next step.
## **Step 5: Copy the Correct Loader File** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Move into the extracted ionCube folder and look for the file that matches your PHP version.
Copy to clipboard
1
2
3
cd ioncube
ls
Look for the file that matches your PHP version from Step 2. For example, if you are using PHP 8.1, choose **ioncube\_loader\_lin\_8.1.so**.
Copy that file into your PHP extension directory (the path you found in Step 4):
filename.js
Copy to clipboard
1
2
3
\# Replace 'ioncube\_loader\_lin\_8.1.so' and the destination path if yours are different
sudo cp ioncube\_loader\_lin\_8.1.so /usr/lib/php/20210902/
Using sudo here ensures you have permission to copy files into system directories.
## **Step 6: Configure PHP to Load the Extension** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
You now need to edit your php.ini file to load ionCube Loader. The location of this file depends on your setup. You may need to edit more than one file one for your web server (FPM or OLS) and one for the command-line interface (CLI).
Common locations include:
- **For Nginx / PHP-FPM:**
Copy to clipboard
1
2
/etc/php/8.1/fpm/php.ini
- **For OpenLiteSpeed:**
Copy to clipboard
1
2
/usr/local/lsws/lsphp81/etc/php/8.1/litespeed/php.ini
- **For CLI:**
Copy to clipboard
1
2
/etc/php/8.1/cli/php.ini
Open the relevant file(s) with a text editor such as nano.
filename.js
Copy to clipboard
1
2
3
4
5
6
\# Example for Nginx (PHP\-FPM)
sudo nano /etc/php/8.1/fpm/php.ini
# Example for CLI
sudo nano /etc/php/8.1/cli/php.ini
At the very top of the file, add the following line. If there are other zend\_extension entries, make sure this one is listed first.
Copy to clipboard
1
2
zend\_extension=/usr/lib/php/20210902/ioncube\_loader\_lin\_8.1.so
Save and close the file. For nano, you do this with **Ctrl+X**, then press **Y**, then **Enter**.
## **Step 7: Restart Services** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
For the changes to take effect, restart your PHP process and your web server.
### **For Nginx / PHP-FPM:** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Copy to clipboard
1
2
3
4
\# Replace with your PHP version
sudo systemctl restart php8.1\-fpm
sudo systemctl restart nginx
### **For OpenLiteSpeed:** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Copy to clipboard
1
2
3
4
\# This command restarts the OLS server
sudo systemctl restart lsws
## **Step 8: Verify the Installation** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
You can confirm that ionCube Loader is working in two ways.
### **Check via Command Line:** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Copy to clipboard
1
2
php -v
You should now see an additional line mentioning ionCube Loader, for example:
Copy to clipboard
1
2
with the ionCube PHP Loader v13.0.3, Copyright (c) 2002\-2023, by ionCube Ltd.
### **Check via Web Server (Recommended):** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
Create a file named phpinfo.php in your website’s public root directory.
Copy to clipboard
1
2
3
4
Open this file in your browser by visiting http://your\_domain.com/phpinfo.php. You should see a section that says “with the ionCube PHP Loader” near the top.
Delete this file afterward for security.
## **Troubleshooting** [#](/docs/how-to-install-ioncube-loader-using-ssh/)
- **Loader Not Appearing:** If php -v does not show ionCube Loader, you may have edited the wrong php.ini file or used an incorrect path. Check the extension directory from Step 4 and the path in Step 6.
- **Website Errors (500, etc.):** Review your web server’s error logs. This can happen if there are permission issues with the .so file or if you are using a loader version that does not match your PHP version.
- **Wrong Loader Version:** The .so file version must match your PHP version exactly. For example, a PHP 8.0 loader will not work on PHP 8.1.
That is it. You have successfully set up ionCube Loader. Your server can now decode and run ionCube protected PHP code with Nginx or OpenLiteSpeed. You can continue your work, deploy apps, and test your site with confidence in a smooth environment.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# Can I Install MariaDB With xCloud? - xCloud
> Now easily you install MariaDB with xCloud.
To install MariaDB with xCloud, you need to **[create a new server](/docs/setup-your-first-server-site-with-xcloud/)** and choose MariaDB from the Databases option. **[Read this documentation](/docs/install-mariadb-with-xcloud/)** for detailed step-by-step guidelines on how to install MariaDB with xCloud.
---
# How to Install Site.pro with xCloud (One Click Apps) - xCloud
> Learn how to install Site.pro with xCloud One Click Apps and build websites faster with secure deployment powered by Site Security PRO.
[Site.pro](https://site.pro/) is a powerful website builder that allows you to create, manage, and publish professional websites quickly without complex development work. It provides an intuitive visual editor, ready-made templates, and built-in tools for designing websites, landing pages, and online projects with ease.
Whether you are **[building a site](/docs/how-to-create-a-site-with-xcloud/)** for a client, a business, or personal use, Site.pro simplifies the entire website creation process. Follow the documentation to install Site.pro with xCloud using One Click Apps in just a few steps.
## **Step 1: Access the One Click Apps Dashboard** [#](/docs/how-to-install-site-pro-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
Then choose your server from the dropdown menu. Next, click on the ‘Next’ button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One-Click Apps section. You will see ‘Site.pro’, click on it to proceed with the deployment of this application.
## **Step 2: Install Site.pro with xCloud** [#](/docs/how-to-install-site-pro-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: ‘Go Live’ for a production-ready deployment or ‘Demo Site’ for testing purposes. Selecting ‘Go Live’ will immediately create a live environment, while choosing ‘Demo Site’ allows you to experiment in a staging environment before promoting it to production.
## **Step 3: Configure Domain Settings** [#](/docs/how-to-install-site-pro-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your Site.pro application. Next, enter your application’s domain.
You can get a ‘Site User’of your application. You can also adjust it according to your preferences, or leave it as the default.
## Step 4: Visit the Application [#](/docs/how-to-install-site-pro-with-xcloud/)
After completing the setup, you will be able to visit your site.pro site. From the dashboard, click on the ‘Edit Now’ button.
Next, you can start building your website using site.pro. You can choose your preferred template to proceed.
Next, edit the site using the **[Site.pro](http://site.pro)’s** drag and drop builder. Add your preferred widgets, customize and click on the ‘Publish button to make the site live.
Now, if you visit the site from the xCloud dashboard, you will be able to access your newly created site with Site.pro.
👉 If you want to learn about editing the Template of Site.pro, visit this **[documentation](https://site.pro/Videos/Editing-the-Template/).**
## **How to Delete a Site Built with Site.pro** [#](/docs/how-to-install-site-pro-with-xcloud/)
If you want to delete a site built using Site.pro on xCloud, you must first unsubscribe from your Site.pro subscription (if you are using any Site.pro Pro features) through the Site.pro dashboard. Once you have canceled the subscription from Site.pro, you can delete the site from xCloud.
This is how easily you can install Site.pro with xCloud using One Click Apps. The entire setup takes only a few simple steps, making it possible to deploy the application without technical complexity or manual configuration. xCloud simplifies server management while ensuring a smooth and reliable installation process.
Still stuck? Feel free to reach out to our support team.
---
# How to Install Supabase with xCloud(One Click Apps) - xCloud
> Learn how to install Supabase with xCloud using One Click Apps, from server setup to deployment, with a fast and hassle-free process.
[Supabase](/supabase-hosting/) is an open-source backend-as-a-service (BaaS) platform designed to help developers build scalable applications faster. It provides essential backend features such as a PostgreSQL database, authentication, real-time subscriptions, storage, and APIs – all wrapped into a developer-friendly ecosystem. Often described as an open-source alternative to Firebase, Supabase gives you full control over your data while maintaining simplicity and performance.
Follow the guide to install Supabase with xCloud with [**One Click Apps**](/docs/deploy-n8n-with-xcloud-with-one-click-apps/) with xCloud. Let’s get started.
_Note: xCloud currently supports one Supabase project per server due to service and port conflicts in its multi-container Docker setup,_ especially with Kong_. To ensure a stable environment, each Supabase project should be deployed on a separate server._
Copy to Clipboard
## Step 1: Create a Docker+ NGINX Server [#](/docs/how-to-install-supabase-with-xcloud/)
First, you need to create a Docker server to deploy Supabase. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Supabase either on your **[own serve](/self-managed-hosting/)**[**r**](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy Supabase with xCloud. You can either use an **[xCloud Managed Server](/managed-hosting/)** or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the ‘**Server Name’,** set the **‘App Type’** to Supabase(it is optional to select), and add any relevant **‘Tags’** to help identify your server later.
Next, choose between the ‘General’ and ‘Premium’ options based on your requirements. Then, select a plan that best fits your needs.
Next, choose the ‘Region’ and ‘Ubuntu Version for your server. You can also enable or disable the Backup option as needed.
Next, you can see the **‘Docker + NGINX’** stack is already selected, which is mandatory for deploying the Supabase application. Then click on the ‘Create’ button to proceed.
Once the server is created, you will be able to deploy your Supabase Application in this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## How to Install Supabase on a Cloud Server [#](/docs/how-to-install-supabase-with-xcloud/)
Learn how to install Supabase on a cloud server. It walks you through creating a server, configuring the environment, and launching your Supabase application easily.
### Step 2: Access the One Click Apps Dashboard [#](/docs/how-to-install-supabase-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
Then choose your server from the dropdown menu. Next, click on the ‘**Next’** button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One Click Apps section. You will see ‘**Supabase’,** click on it to proceed with the deployment of this application.
### Step 3: Set Up the Supabase Application [#](/docs/how-to-install-supabase-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant ‘**Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: ‘Go Live’ for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting ‘Go Live’ will immediately create a live environment, while choosing ‘Demo Site’ allows you to experiment in a staging environment before promoting it to production.
### **Step 4: Configure Domain Settings** [#](/docs/how-to-install-supabase-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a demo domain for your Supabase application. Next, enter your application’s domain.
You will get a **‘Site User’** of your application. You can also adjust it according to your preferences, or leave it as the default. In the next section, you will get **‘Admin Username’**, **‘Admin Password**’, and **‘Admin Email Address’**.
_Note: From here, copy your Admin Username and Admin Password to log in to your Supabase application later._
Next, get the **‘Database Name’, ‘Database Username’ and ‘Database Password’** for this application and click on the **‘Next’** button
## **Step 4: Visit the Application** [#](/docs/how-to-install-supabase-with-xcloud/)
After completing the setup, you will be able to visit your Supabase site. From the dashboard, click on the **‘Visit Site’** app.
## **Environment Editor for Supabase** [#](/docs/how-to-install-supabase-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your Supabase app. Just go to the ‘**Environment’** option from the sidebar and adjust as you need, then click on the **‘Update Environment**’ button.
## ⚠️ Important Notes for Self-Hosted Supabase [#](/docs/how-to-install-supabase-with-xcloud/)
- Edge Functions won’t deploy automatically to a self-hosted instance – you must deploy them manually to your self-hosted Supabase.
- Self-hosted Supabase does NOT auto-run database migrations.
Unlike Supabase Cloud, you are responsible for applying SQL migrations manually. If you update Supabase versions, enable new features, or pull a newer Docker Compose, the DB schema does NOT update by itself.
That’s it! This is how easily you can install Supabase using xCloud’s One Click Apps. xCloud takes care of the heavy lifting, server provisioning, Docker configuration, and deployment, so you can focus on building and scaling your application with Supabase’s powerful backend features.
If you’re setting up a demo project or going live in production, this streamlined process lets you get started quickly and confidently.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Install Umami with xCloud (One Click Apps) - xCloud
> Learn how to quickly Install Umami With xCloud using one-click apps for fast, privacy-focused web analytics on your cloud server.
**[Umami](https://umami.is/)** is a lightweight, privacy-focused web analytics tool that makes it easy to track website performance without compromising user data. It’s simple to use, fast to deploy, and ideal for anyone who wants clean, reliable analytics without the complexity of larger platforms.
Follow the guide to install Umami with xCloud with [**One Click Apps**](/docs/deploy-n8n-with-xcloud-with-one-click-apps/) with xCloud. Let’s get started.
## **Step 1: Create a Docker+ NGINX Server** [#](/docs/how-to-install-umami-with-xcloud/)
First, you need to create a Docker server to deploy Umami. Click the **‘Add New Server’** button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Umami either on your [**own server**](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy Umami with xCloud. You can either use an [xCloud Managed Server](/managed-hosting/) or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the **‘Server Name’**, set the **‘App Type’** to Umami, and add any relevant **‘Tags’** to help identify your server later.
Next, choose between the **‘General’** and **‘Premium’** options based on your requirements. Then, select a plan that best fits your needs.
Next, choose the ‘Region’ and ‘Ubuntu Version for your server. You can also enable or disable the Backup option as needed.
Next, you can see the **‘Docker + NGINX’** stack is already selected, which is mandatory for deploying the Umami application. Then click on the ‘Create’ button to proceed.
Once the server is created, you will be able to deploy your Umami Application in this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## **How to Install Umami on a Cloud Server** [#](/docs/how-to-install-umami-with-xcloud/)
Learn how to install Umami on a cloud server. It walks you through creating a server, configuring the environment, and launching your Umami application easily.
### **Step 2: Access the One Click Apps Dashboard** [#](/docs/how-to-install-umami-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One-Click Apps section. You will see **‘Umami’**, click on it to proceed with the deployment of this application.
### Step 3: Set Up the Umami Application [#](/docs/how-to-install-umami-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting it to production.
### **Step 4: Configure Domain Settings** [#](/docs/how-to-install-umami-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your Umami application. **Next**, enter your application’s domain.
You can will get a **‘Site User’**of your application. You can also adjust it according to your preferences, or leave it as the default.
Next enter the **‘Database Name’, ‘Database Username’ and ‘Database Password’** for this application and click on the **‘Next’** button
## Step 4: Visit the Application [#](/docs/how-to-install-umami-with-xcloud/)
After completing the setup, you will be able to visit your Umami site. From the dashboard, click on the **‘Visit Site’** app.
> **Note:** After your site is created, xCloud will send an automated email containing a default Umami credentials of username and password for your Umami application. You need to collect these credentials, click on the link provided in the email, and reset your password immediately.
### **Default Umami Credentials** [#](/docs/how-to-install-umami-with-xcloud/)
Umami provides default login credentials when first installed:
- **Username:** `admin`
- **Password:** `umami`
Users must log in using these default credentials and immediately change both the username and password for security.
### **Optional: Disable Password/Sensitive Info Emails** [#](/docs/how-to-install-umami-with-xcloud/)
If you prefer not to receive credentials via email, xCloud provides an option to disable sending passwords or sensitive information. You can go to ‘Notifications’ and toggle the **‘Do Not Send Sensitive Information’** option to stop receiving sensitive information through email.
### Environment Editor for Umami [#](/docs/how-to-install-umami-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your Umami app. Just go to the **‘Environment’** option from the sidebar and adjust as you need, then click on the **‘Update Environment**’ button.
With xCloud’s one-click setup, installing Umami is quick and simple. You can create your server, set up your app, and get your self-hosted Analytics dashboard live in just a few steps.
💬 If you still face difficulties, **[feel free to contact our support team](/support/)**.
---
# How To Install WordPress Multisite With xCloud? - xCloud
> xCloud has just introduced WordPress multisite feature where you can create & manage multiple websites easily.
WordPress Multisite offers a great solution for **[WordPress](https://wordpress.org/download/)** users looking to manage multiple websites effortlessly. With Multisite, you can operate numerous websites using just one dashboard, eliminating the need for separate WordPress installations.
Today, we will guide you through the step-by-step process of installing WordPress multisite with [**xCloud**](/) hosting. Follow along as we simplify the setup for you.
## **Step 1: Activate WordPress Multisite** [#](/docs/how-to-install-wordpress-multisite-with-xcloud/)
To activate WordPress multisite when setting up a new site on xCloud, start by logging in to your xCloud account. Next, navigate to the “**All Servers**” page and select “**Install A New WordPress Site”**. Make sure to give a “**Site Title**” on the site creation page.
Scroll down a bit more, and you’ll find the WordPress multisite tab. Just toggle the option to enable it
_**Note: you can create the multisite with the both sub-domain and sub-directory.**_
After adding all the necessary information, click on the ‘Next’ button & your site will be created soon.
## **Step 2: Add A New Site From WordPress Dashboard** [#](/docs/how-to-install-wordpress-multisite-with-xcloud/)
Next, you’ll need to log in to your WordPress site from xCloud.
We will now create a new site from the dashboard. Navigate to **My Sites → Network Admin → Sites.**
To add a new site, simply click on “**Add New Site**” from the Sites page. Then, enter your site address, title, language, and admin email
Once you’ve clicked on “**Add Site**,” your newly created site will appear on the WordPress dashboard instantly. For this tutorial, we’ve named the newly added site “**WordPress**.” Click on the site, and it will take you to your original domain.
This is how you can create and configure WordPress multisite with xCloud.
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How to Integrate a Git Provider with xCloud and Deploy Your Site Easily - xCloud
> Learn how to seamlessly integrate a Git provider with xCloud and deploy your website quickly and securely in just a few simple steps.
Deploying a website directly from a Git repository streamlines development and updates, making development faster, easier, and more secure. However, manually deploying every project from Git can be a complex and time-consuming process. xCloud simplifies this by integrating with Git, allowing you to deploy your projects with just a few simple steps.
With xCloud, you can seamlessly integrate a Git provider, [**clone your git repositories**](/docs/clone-a-website-from-git-repository-with-xcloud/), and automate deployments. This eliminates the need for manual uploads or complex server configurations, allowing you to focus on building and improving your application.
Follow this guide to easily integrate a Git provider and deploy your projects with xCloud in just a few clicks.
## **Step 1: Integrate a Git Provider** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
To integrate Git with xCloud, start from your xCloud dashboard and navigate to the ‘**Team Settings’** option located in the top-right menu. From the sidebar, go to **‘Integrations’ → ‘Git Provider’** and click on the **‘Connect Git Provider’** button
A popup window will appear, choose **‘GitHub’** from the provider options. Next, enter **a ‘Label’** and click on the **‘Connect GitHub’** button to authenticate and connect your [**GitHub**](https://github.com/) account with xCloud.
**_Note:_** _You must be logged in to your GitHub account to connect with xCloud_
Next, you will be redirected to authorize your GitHub account. Review the account and click on the **‘Authorize’** button to complete the authorization process.
Once the connection is successful, your account and all of your Git repositories will be visible directly from the xCloud dashboard. You can easily **‘Edit’** or **‘Remove’** the connected account at any time, depending on your requirements. Also, click on the **‘Folder’** icon to see the repositories of your connected GitHub account.
## **Step 2: Choose the Application** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
To begin deployment, click on the **‘Create Site’** button from the dashboard. You will then be asked to choose **‘Server’** from the dropdown.
Afterwards, go to your preferred deployment options from **‘WordPress’, ‘Laravel’,** or **‘Custom PHP’** as your preference. In this documentation, we are selecting the **‘Custom PHP’** option.
## **Step 3: Select the Option to Clone a Git Repository** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
After that, choose the **‘Clone A Git Repository’** option to import your PHP site using Git Provider.
## **Step 4: Set Up Domains** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
The **‘Domains’** tab allows you to decide how you want to configure your site’s domain. You can either create a **‘Demo Site’** or **‘Live Site’**.
For this documentation, we are proceeding with the **‘Demo Site’** option and clicking **‘Next’** to go to the next step.
## **Step 5: Manage Database Settings** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
In the **‘Settings’** tab, you will find options to configure the **‘PHP Version’** and manage **‘Site Users’**. Adjust these settings based on your requirements.
In the next step, you can either proceed with **‘No Database’**, **‘Add an Existing Database’,** or **‘Create a new database’** directly on the server and click on **‘Next’**.
## **Step 6: Insert Git Repository Credentials** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
In the ‘Git Repo’ tab, you will get three repository options: **‘Private Repository (Manual SSH URL)’, ‘Public Repository (Manual HTTPS URL)’**, and **‘Connected Git Provider’.**
If you choose the **‘Public Repository(Manual HTTPS URL)’** option, enter the **‘GitHub Repository URL’** into the dedicated field and branch into the **‘Git Branch’**.
_Note: Collect the HTTPS URL from your GitHub dashboard repository to deploy the Public repository._
If you choose the **‘Private Repository(Manual SSH URL)’** option, enter the **‘GitHub Repository URL’** into the dedicated field and branch into the **‘Git Branch’**.
_Note: Collect the SSH URL from your GitHub dashboard repository to deploy the Public repository._
We are going to deploy Git projects using **‘Git Provider’** option here. Choose the **‘Connected Git Provider’** option from the dropdown menu.
From the **‘Select Git Provider’** dropdown, choose the connected account you want to use. Once selected, navigate through the list of repositories, pick the one you want to deploy, and then select the specific **‘Branch’** of that project.
## **Step 7: Enable Push to Deploy** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
The next step is to enable automated deployment. Toggle on the ‘Enable push to deploy’ option. You need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
_Note: if you want to learn more about the process, follow the steps from this_ [_document_](/docs/deploy-custom-php-applications-with-xcloud/).
## **Step 8: Run Deployment Script** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
Once the repository integration is complete, you can configure post-deployment actions. In the **‘Deployment Script’** field, enter any custom commands you want to run after deployment. You can also select one of the provided example scripts. After setting this up, click on **‘Next’** to continue.
## **Step 9: Confirm Migration** [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
The final step is to confirm and start the migration. Click on the ‘**Start’** button, and the migration process will begin immediately. You will be able to monitor the progress in real time.
Once the migration is complete, a success message will appear. From there, you can access your site dashboard.
After the migration is complete, you can visit your site to see your PHP application deployed successfully. With these steps, you can quickly set up Git integration, configure your database, and launch your site with either a staging or live domain.
## Git Pull Script & Deploy Script (Advanced Configuration) [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
In this step, you can customize how your application pulls code from your Git repository and define actions to run after deployment.
### Available Variables [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
You can use the following variables in both Git Pull Script and Deploy Script:
**Project variables (all sites)**
• PROJECT\_DIR — absolute path to your site root
• XCLOUD\_SITE\_PATH — absolute path to your site root
• XCLOUD\_SITE\_BRANCH — current Git branch used for deployment
**PHP variables (PHP sites only)**
• XCLOUD\_PHP\_VERSION — PHP version (e.g. 8.2)
• XCLOUD\_PHP — full path to PHP binary
• XCLOUD\_COMPOSER — PHP-prefixed Composer path
**Node.js variables (all sites)**
• XCLOUD\_NODE — path to Node.js binary
• XCLOUD\_NODE\_VERSION — installed Node.js version
• XCLOUD\_NPM — path to npm binary
**PM2 variable (Node.js sites only)**
• PM2\_PROCESS\_NAME — the PM2 process name for the site
### Git Pull Script [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
The Git Pull Script allows you to control how the code is fetched from your Git repository during deployment. You can go to the ‘Git Pull Script’ section and enter your custom script. If you leave this field empty, xCloud will use the default pull process.
### Deploy Script [#](/docs/how-to-integrate-a-git-provider-with-xcloud/)
The ‘Deploy Script’ runs after your code is successfully pulled from the repository. To access this, make sure the “Run this script after every site deployment” option is turned on. Enter your scripts under the ‘Deploy Script’ section.
After configuring your scripts, click on the ‘Save Changes’ button to continue.
Whether you prefer to use Git repositories or upload files directly, xCloud provides a straightforward and secure way to bring your applications online.
If you encounter any difficulties, feel free to reach out to our support team for assistance.
---
# How to Manage PHP Extensions With xCloud - xCloud
> Learn how to manage PHP extensions in xCloud. Install, remove and switch extensions by PHP version from a single server dashboard.
[**xCloud’s**](/) PHP extensions add extra capabilities to PHP, such as image processing, caching, and database support. With xCloud, you can install or remove these extensions for a specific PHP version directly from your server dashboard without connecting through SSH or editing configuration files by hand.
The **Manage PHP Extensions** panel shows every extension that is already installed on the server, along with the extensions that are available to add. Some extensions are marked as **Core** because PHP requires them to run; these are protected and cannot be removed.
## **How PHP Versions And Extensions Work in xCloud** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
In xCloud, [**PHP extensions**](https://www.php.net/manual/en/extensions.php) are tied to a **specific PHP version**, not to the server as a whole. Every PHP version ships with its own set of extensions, so the **Installed Extensions** and **Available Extensions** lists you see always depend on the version selected in the panel.
An extension that is offered for one PHP version may not exist for another, which is why the same server can show different extensions when you switch versions.
Which PHP versions you can choose from depends on the web server stack your server runs on. xCloud supports two web server stacks, and each one offers its own range of PHP versions:
**Web Server Stack**
**Supported PHP Versions**
OpenLiteSpeed (OLS)
PHP 8.1, 8.2, 8.3, 8.4 and 8.5
NGINX
PHP 5.6, PHP 8.0 – 8.5 and PHP 7.0 – 7.4
A small group of extensions in every version are labelled **Core**. These are the extensions PHP must load to serve a website on that version without them, the sites running on that PHP version would not work at all. Because they are mandatory, Core extensions are protected: xCloud does not display a **Remove** button for them, and they stay installed for as long as that PHP version exists on the server.
## **Before You Begin** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
Before you open the panel, take a moment to confirm the following:
Before you begin, make sure you have access to the xCloud team where the server is hosted and know which PHP version your site is using, since extensions are managed separately for each PHP version installed on the server.
You should also identify the extension you want to install or remove. If you plan to remove an extension, first verify which extensions your websites actually depend on to avoid uninstalling one that a live site requires. Taking a moment to confirm this beforehand can prevent unexpected site issues and is far easier than troubleshooting and recovering a broken website later.
**Note:** _Installing or removing an extension restarts the PHP service for that version so the change can take effect; PHP-FPM on NGINX servers or the LiteSpeed Web Server_ **_(lsws)_** _on OpenLiteSpeed_ **_(OLS)_** _servers._
_Either way, every site running on that PHP version is briefly affected, so where possible, make changes during a low-traffic window._
## **Step 1: Open the Manage PHP Extensions Panel** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
From your xCloud dashboard, go to ‘**Servers’** and select the server you want to manage. Open the ‘**Management’** menu, then click ‘**Manage PHP’**.
On the Manage PHP page, select the ‘**Manage PHP Extensions’** tab. xCloud loads the list of extensions for the PHP version shown in the dropdown at the top-right corner.
### **Inside the Manage PHP Extensions Panel** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
The Manage PHP Extensions panel is **divided into two sections.**
**‘Installed Extensions’** lists every extension currently enabled for the selected PHP version, along with the total count shown in the heading.
Extensions you can remove display a ‘**Remove’** button. Extensions marked **Core** are required by PHP and are protected.
**‘Available Extensions’** lists every extension that is supported but not yet installed for the selected PHP version. Each available extension displays an ‘**Install’** button.
## **Step 2: Install a PHP Extension** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
In the ‘**Available Extensions’** section, find the extension you want to add and click the ‘**Install’** button. The button changes to ‘**Installing…’** while xCloud adds the extension and restarts the PHP service for that version **(PHP-FPM on NGINX, or lsws on OpenLiteSpeed).**
Once the process completes, the extension moves to the ‘**Installed Extensions’** section and the installed count increases. In the example below, **apcu** has been installed.
## **Step 3: Remove a PHP Extension** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
You can remove any extension that shows a ‘**Remove’** button; Core extensions cannot be removed. In the ‘**Installed Extensions’** section, click the ‘**Remove’** button which you want to uninstall.
A confirmation dialog appears, warning that the extension will be uninstalled, that the PHP service for that version will restart (PHP-FPM on NGINX or the LiteSpeed Web Server on OpenLiteSpeed) and that sites using the extension may stop working. Click ‘**Yes, Remove’** to continue or ‘**Cancel’** to keep the extension.
The button changes to ‘**Removing…’** while xCloud uninstalls the extension and restarts that PHP service. Once the process completes, the extension returns to the ‘**Available Extensions’** section and the installed count decreases.
## **Step 4: Switch PHP Version And Refresh the List** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
Because extensions are managed separately for each PHP version, you will switch versions whenever you want to view or change the extensions of a different version. Use the PHP version dropdown in the top-right corner to choose the version whose extensions you want to view or change.
After you select a version, the ‘**Installed Extensions’** and ‘**Available Extensions’** lists update to match it. If a change does not appear right away, click ‘**Refresh’** to reload the list.
## **Troubleshooting** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
### **The Extension You Need Is Not in the Available List** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
If an extension does not appear in either the Installed or Available list, it may not be supported for the PHP version you have selected. Remember that each PHP version has its own set of extensions, so availability genuinely differs between versions.
Switch to a different PHP version using the dropdown, then click **Refresh**. If the extension is already installed, it will appear in the Installed Extensions section instead.
### **A Site Stopped Working After You Removed an Extension** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
Removing an extension uninstalls it for every site that uses the selected PHP version. If a site breaks, return to the **Available Extensions** section and click **Install** to add the extension back. The site should recover once the PHP service restarts **(PHP-FPM on NGINX, or lsws on OpenLiteSpeed).**
### **The Extension List Did Not Update** [#](/docs/how-to-manage-php-extensions-with-xcloud/)
If the Installed or Available list does not reflect your most recent change, click the **Refresh** button in the top-right corner to reload the current state for the selected PHP version.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Manage Services on Your Server - xCloud
> Want to install PHP, Node.js, or Redis on your server? Follow this simple step-by-step guide to set up services from your dashboard in just a few clicks.
A server is only as useful as the services running on it. To get the most out of your server, you need to install the right tools for your project. For example, PHP is needed to run websites built with platforms like WordPress or Laravel. Node.js is used for modern web apps and JavaScript-based projects. Redis helps speed up your applications by storing data in memory for quick access.
The good news is that you do not need to be a server expert to install these services with xCloud. Your dashboard comes with a simple installer that lets you add any of these tools with just a few clicks.
Follow this guide to walk you through the process of installing a service on your server on xCloud.
### **Step 1: Access Server Management Option** [#](/docs/how-to-manage-services-on-your-server/)
First, navigate to your server, then go to **Management** → **Settings** from the dashboard.
Next, locate the **Install a Service** button on the dashboard and click it to proceed.
### **Step 2: Install a Service** [#](/docs/how-to-manage-services-on-your-server/)
A pop-up window will appear with three available options: **PHP**, **Node.js**, and **Redis**. From here, you can choose which service to add to your server. Version-specific options will appear once you make your selection.
- **Installing PHP:** If you select PHP, you will be redirected to the PHP management page of the server, where you can configure your PHP settings.
- **Installing Node.js:** If you expand the Node.js option, you can choose your preferred Node.js version, then click the **Install Node.js** button to begin the installation.
**Installing Redis:** If you select Redis, simply click the **Install Redis** button to install the service on your server.
Installing services on your server is easier than most people think. With the dashboard installer, you can add PHP, Node.js, or Redis in just a few clicks, without dealing with technical setup or command-line tools. This makes it a great option for both beginners and experienced users.
After your services are installed, your server will be ready to run websites, web apps, and other projects without any extra setup. If your needs change later, you can always return to the same dashboard to add more services, update versions, or adjust your settings. With everything ready, you can now focus on building and growing your project.
---
# How To Manage Your Server Utilities With xCloud? - xCloud
> Follow this simple guide to manage your server utilities with xCloud.
Managing the services of a server is super easy with **[xCloud](/)**. Key server utilities processes, such as the Web Server (Nginx), **[Redis](https://redis.io/)**, SSH, MySQL, MariaDB, and various versions of PHP, are run through services. All of these can be controlled using the xCloud web application. Follow this simple guideline on how to manage your servers with xCloud?
## How To Manage Your Server Utilities With xCloud? [#](/docs/how-to-manage-your-server-utilities-with-xcloud/)
From your xCloud dashboard, go to **‘All Servers’.** Click on the server where you want to configure and manage the server utilities.
You can configure the services’ settings now. Go to the **‘Server Management’** tab to manage the services.
You can manage your Server Utilities like MySQL, MariaDB, NGINX, Redis, PHP, OpenSSH, etc as needed. There are three actions that you can perform.
- Enable: Start a service if it is disabled
- Disable: Stop a service if you want to discontinue it
- Reboot: Restart the service after configurations
So, here, in this visual, each of the services is enabled. Reboot or Disable any of the utilities as needed. You can enable the services later as well. You can also archive or delete your server if needed.
Thus, following the simple steps you can manage the services of a server with xCloud.
Getting stuck? Feel free to reach out to our [support team](/contact/) for further assistance.
---
# How To Manually Upload WordPress Websites On xCloud - xCloud
> Here is the step-by-step guide on how to manually upload WordPress Websites On xCloud without any hassle.
With [**xCloud**](/), you can manually upload WordPress Websites On xCloud without any hassle. Follow the step-by-step guide below to get started.
## **Prerequisites To Manually Upload WordPress Websites On xCloud:** [#](/docs/how-to-manually-upload-wordpress-websites/)
- Disable 2FA if there are any.
- Disable additional security like Cloudways Bot protection, OR Site Grounds Security optimizer from your hosting end.
- Uninstall Must use plugins of hosts.
- Clear Cache and disable cache plugins like Object Cache PRO
- Disable Wordfence or any other security plugins.
## **Step 1: Create A New Site** [#](/docs/how-to-manually-upload-wordpress-websites/)
First, you have to log in to xCloud with your credentials. Then click on ‘**New Site**’ from the xCloud dashboard.
After that, you have to choose your server to upload your site. Click on the ‘**Choose Server**’ field and select your server from the drop-down and before clicking on the ‘**Next**’ button.
Now, you will be redirected site creation dashboard. Click on the ‘**Manually Upload WordPress Website**’ option.
## **Step 2: Add Information To Manually Upload WordPress Website** [#](/docs/how-to-manually-upload-wordpress-websites/)
Now, select the destination server to migrate your site. Afterward, click on the ‘**Next**’ button.
In the next step, you need to add your source site URL. And if you choose to migrate to a new domain you can include your custom domain. xCloud offers a staging environment and with it, you can upload your site and visit it live with a temporary domain. After successfully uploading your site, you may update the site with your custom domain later.
In this tutorial, we will be working on a staging site. Select ‘**Staging Environment**’ and then click on the ‘**Next**’ button.
Now, you will be sent to the ‘**Settings**’ step. Make sure to correctly add your **PHP Version**, Prefix, **Site Users,** and other details before clicking the ‘**Next**’ button.
## **Step 3: Upload The Exported Zip File & SQL File** [#](/docs/how-to-manually-upload-wordpress-websites/)
You will be now directed to the ‘**Settings**’ step. Just upload your exported WordPress file as shown and click on the ‘**Next**’ button.
Now from the ‘**Files**’ step, upload your SQL file similarly. Afterward, click on the ‘**Next**’ button.
## **Step 4: Complete Database Settings & Finalize** [#](/docs/how-to-manually-upload-wordpress-websites/)
In the ‘**Database**’ tab you can configure your preferred database setup. If you are good to go for uploading an existing WordPress website with xCloud, click on the ‘**Start**’ button.
Within a few moments, your WordPress website will be uploaded on xCloud automatically. You will see the following screen while uploading.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
This is how you can manually upload WordPress Websites On xCloud with ease.
Still stuck? Contact our [**support team**](mailto:support@xcloud.host) for any of your queries.
---
# How to Migrate Emails From Legacy MailBox To The New xCloud MailBox - xCloud
> Migrate emails from legacy mailbox to the new xCloud MailBox in bulk per domain. Transfer all emails securely, verify DNS, and start using your upgraded mailbox.
The xCloud MailBox Addon allows you to create and manage professional email addresses using your own custom domain. With a centralized dashboard, you can access your inbox, manage existing mailboxes, set up aliases, configure mail forwarding, and migrate your legacy email accounts to the new MailBox infrastructure, all from one place.
If you are currently using a legacy Mailbox and want to move your existing emails to the new MailBox system, xCloud makes the process seamless with its built-in migration workflow. The migration runs in bulk per domain, ensuring all emails under a chosen domain are transferred together without disruption.
Follow the steps below to access your MailBox dashboard, migrate your legacy mailboxes, verify your DNS records, and start using your new MailBox right away.
_Note: Before starting the migration, keep in mind that when you migrate a MailBox, all emails from the legacy MailBox under the selected domain will be migrated together._
## Step 1: Go To the Migrate MailBox Option [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Now navigate back to the xCloud MailBox Addon dashboard and from the left sidebar, click on the Migrate MailBox tab.
Important: Before you proceed, remember that migration will be bulk per domain, which means every legacy MailBox on the chosen domain moves all emails together.
## Step 2: Select the Domain to Migrate [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
First, select the domain you want to migrate from the Domain dropdown. Below the domain selector, you will see the complete list of mailboxes that will be migrated. All mailboxes under the selected domain are listed along with their individual storage amounts.
Scroll down and read the general information. Once you have reviewed everything and are ready to proceed with this migration, click the Next button.
## Step 3: Download Mailbox Credentials [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
In the next step, click the Download credentials CSV button to download the CSV file containing all your mailbox credentials for the migration. Keep this file safe, as you will need to upload it to the migration tool in the next step.
## **Step 4: Open The Migration Tool** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Now open the migration tool using the provided link. This opens the Audriga Email Migration tool in a new browser tab.
On this page, you will see a Terms of Service checkbox. Accept the Terms of Service and Privacy statement checkbox, then click the Proceed button.
## **Step 5: Select the Email Providers** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Next, you will see the Email provider selection page. You need to select the email providers from which you want to migrate your emails. Keep the source provider set to Custom, and the destination provider is automatically set to OX App Suite Cloud (EU) on the right side.
Below the provider selection, enter any required additional information in the provided field. Then click Proceed to continue.
## **Step 6: Upload the CSV File** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
On the next page, go to the Add multiple accounts tab and upload the CSV file you downloaded earlier. Next, click on the Check button. The system begins checking account data, which may take a few moments.
Once the validation is complete, click on the Save button.
Then click the Proceed button to start the migration right away.
## **Step 7: Start the Migration** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
You will then see the Migration summary. Click on the Start migration button and it will begin migrating the emails from the legacy MailBox to the new MailBox.
Depending on the number of mailboxes and the volume of data, the migration may take some time. Wait until all accounts finish migrating successfully before moving on.
## **Step 8: Confirm the Data Transfer** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Once all accounts finish migrating successfully, navigate back to the xCloud dashboard tab.
Now, check the confirmation checkbox that reads I confirm that I have completed the data transfer for all mailboxes in this migration. Then click the Next button.
Click the OK button from the confirmation dialog to proceed to the DNS configuration step.
After the migration completes, you must verify the DNS records of your domain to finalize the switch to the new MailBox.
## **Step 9: Verify DNS Records** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
If you have a different domain provider, then click on the Open DNS settings button for the domain you want to verify and verify the records manually.
Or if your domains are managed through Cloudflare and you have Cloudflare integration with xCloud, then you can verify the DNS records in just a click. Simply enable the Auto-update DNS via Cloudflare option.
After enabling, you will see that the domains are verified.
Click the Next button to proceed to the final step.
## **Step 10: Finish the Migration** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
All four mailboxes are listed below with green checkmarks confirming they are ready for the final switch. Click the Finish Migration button to complete the process.
Once the migration is complete, you can log in to your new MailBox and confirm that all emails have been successfully transferred.
## **Step 11: Access Your New Mailbox** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Next, go back and click on the Access button, copy the credentials, and visit the new MailBox. Log in using the credentials. Now you can see all your emails have been migrated successfully from the previous legacy mailbox.
And that’s it, this is how easily you can migrate your legacy mailboxes to the new xCloud MailBox in just a few steps. Your professional emails are now hosted on the upgraded MailBox infrastructure with all your historical messages intact.
### **⚠️ Important Considerations** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
1. Bulk Migration Per Domain: All mailboxes under the selected domain will migrate together. You cannot migrate individual mailboxes one by one, so plan your migration during a low-activity window to minimize disruption.
2. Keep Credentials Safe: The downloaded CSV file contains sensitive mailbox credentials. Store it in a secure location and delete it once the migration is complete.
3. DNS Propagation Time: After verifying DNS records, allow some time for the changes to propagate globally. Cloudflare usually updates within minutes, while other providers may take a few hours.
4. Failed Verification Fix: If the DNS verification fails, double-check that all DNS records are correctly added. If you’re using Cloudflare, try toggling the Auto-update DNS via Cloudflare option OFF and then ON again.
### **📌 Limitations** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
To ensure fair and stable service, here are some limitations and notes you should keep in mind during and after the migration:
1. Migration is bulk per domain. Every legacy mailbox under the chosen domain will be migrated together; selective migration of individual mailboxes is not supported.
2. You cannot create mailboxes or aliases using the same domain in different teams. For instance, if demo@domain.com is part of Team A, then test@domain.com cannot be created under Team B.
3. Avoid using POP email clients during and after migration. POP only downloads emails to your device and does not sync changes like read status or sent emails. Use IMAP-supported email clients to ensure full syncing across all your devices.
4. Each mailbox can send up to 250 emails in a 24-hour rolling window. You can also create up to 20 email forwards for each mailbox.
5. If you are using Cloudflare and face verification issues even after automatic integration, try toggling the DNS integration off and on again. This often helps reset the settings and successfully verifies your domain.
### **xCloud MailBox Migration – Frequently Asked Questions (FAQs)** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
### **Will my old emails be preserved after the migration?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Yes. The migration tool transfers all your existing emails from the legacy mailbox to the new MailBox. Once the migration completes, you can log in to the new MailBox and see all your historical messages intact.
### **Can I migrate only one mailbox at a time?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
No. The migration is bulk per domain, meaning every legacy mailbox on the chosen domain will be migrated together in one operation. You cannot migrate individual mailboxes selectively.
### **How long does the migration take?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
The duration depends on the number of mailboxes and the total volume of email data being transferred. Smaller migrations may finish in minutes, while larger ones can take longer. The migration tool will display progress for each account.
### **What is the Audriga Email Migration tool?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Audriga is the third-party migration service used by xCloud to securely transfer emails between providers.
### **What if my DNS verification fails after migration?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Double-check that all DNS records are correctly added. If you are using Cloudflare with xCloud integration, try toggling the Auto-update DNS via Cloudflare option OFF and then back ON. Wait a few minutes for the records to propagate and try verifying again.
### **Can I use my old credentials on the new MailBox?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
Once migration is complete, click the Access button next to any mailbox in the new MailBox dashboard, copy the new credentials, and use those to log in. Your inbox, folders, and historical emails will all be available.
### **What happens if I close the migration tool while it’s running?** [#](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)
It is recommended to keep the Audriga migration tab open until all accounts finish migrating successfully. If you close it accidentally, the migration may need to be restarted. Always wait for confirmation before navigating away.
Still stuck? Contact our support team for any of your queries.
---
# How To Monitor Server Resource Usage with xCloud - xCloud
> Learn how to monitor server resource usage easily using xCloud’s dashboard following just a few steps.
Monitoring server resources is very important to ensure smooth performance and prevent downtime. By keeping an eye on RAM, CPU, and disk usage, you can identify potential issues before they affect your applications or websites. With xCloud, you can easily monitor these server resources through a user-friendly dashboard.
Learn from the step-by-step guide below to monitor server resource usage easily with xCloud.
## **Step 1: Go to the Server Dashboard** [#](/docs/how-to-monitor-server-resource-usage-with-xcloud/)
From your xCloud dashboard, select the site you want to monitor. You can also go to the ‘**Servers’** tab, click on the specific server, and then select ‘**Monitoring’** from the sidebar.
## **Step 2: Check the Usage Statuses** [#](/docs/how-to-monitor-server-resource-usage-with-xcloud/)
Here, you will see the complete status of the **RAM, CPU, Disk usage, and Uptime Overview** of the server.
Next, go to the **Server Statistics (Time Zone UTC)** section to check server usage over a specific timeframe. You can change the filter from **Last 24 Hours** or **Last 7 Days** to get a more customized view.
After that, go to the **Individual Site Details** section to view server resource usage for all sites created inside the server separately. You can click on the **View Report** button for more details about a specific site.
Next, head to the **Top CPU Usage Process** section to see which process is using the most CPU.
Similarly, go to the **Top RAM Usage Process** section to check which process is consuming the most RAM.
Finally, go to the **Largest Files & Folders** section and click on the **Scan Now** button to identify files or folders that are using the most server resources.
By following these steps, you can easily monitor the **RAM, CPU, and Disk usage** of your server with xCloud. Regular monitoring helps you maintain server health, optimize performance, and prevent resource overload. If you need further assistance, feel free to contact our [support team](https://support.xcloud.host/) for help.
---
# How To Monitor The RAM, CPU & Disk Usage Of A Site? - xCloud
> From xCloud dashboard you can monitor the RAM usage, CPU usage & much more.
With **[xCloud](http://hidden-hamlet-226309.wp1.sh)**, you can easily monitor the RAM, CPU, and disk usage of a site. Learn from the step-by-step guide below.
### **Step 1:** Log In To Your xCloud Dashboard [#](/docs/how-to-monitor-the-ram-cpu-disk-usage-of-a-site/)
From your xCloud dashboard select the site you want to monitor or go to the ‘**All Sites’** tab and click on the specific site.
### **Step 2:** Check The Usage Status & Monitor The Ram Usage [#](/docs/how-to-monitor-the-ram-cpu-disk-usage-of-a-site/)
Now, move to the **‘Monitor’** tab and you will see the complete status of the RAM, CPU, and Disk usage of that specific site.
Thus, you can easily monitor the RAM, CPU, and Disk usage of a site using xCloud.
Need assistance? Feel free to contact our **support team**.
---
# How to Read Your xCloud Invoice With xCloud - xCloud
> An xCloud invoice can include multiple bill rows, such as managed server charges, resize adjustments, backup add-ons, credits, or other services. This guide
An xCloud invoice can include multiple bill rows, such as managed server charges, resize adjustments, backup add-ons, credits, or other services. This guide explains how to read an invoice before contacting Support about a charge or refund.
## When this guide applies [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Use this guide if:
- you see an invoice but do not understand the charge,
- you need to ask Support about a refund,
- the invoice contains multiple bill IDs,
- you resized a managed server and see an adjustment,
- you deleted a server but still see a billing record,
- Support asked you for a specific bill ID.
## Invoice ID vs bill ID [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
The **invoice ID** identifies the overall invoice. The **bill ID** or line item ID identifies a specific row inside that invoice.
This distinction matters because one invoice may contain several charges. For example:
- managed server monthly charge,
- managed server resize charge,
- backup add-on charge,
- credit or adjustment,
- renewal charge,
- another server charge.
If only one row is incorrect or refundable, Support may ask for the exact bill ID instead of refunding the full invoice.
## Common invoice fields [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Field
What it means
Invoice ID
The main invoice reference
Bill ID
A specific charge or line item inside the invoice
Status
Paid, unpaid, refunded, partially refunded, or pending
Service period
The dates the charge covers
Amount
The charge for that line item
Credit/refund
An adjustment already applied or pending
Server/service name
The managed server, add-on, or product connected to the row
## How to identify managed server charges [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Managed server charges usually reference the server, plan, service period, or resize. If you see multiple managed server rows, check whether they are for:
- different servers,
- old plan vs new plan after resize,
- current month renewal,
- pro-rated upgrade charge,
- credit for unused old plan time.
## How to identify resize charges [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Resize charges may appear when you upgrade or downgrade a managed server. The invoice can show only the difference for the remaining billing period.
Look for:
- plan name changes,
- old and new server size,
- adjustment wording,
- charge amount smaller than the full monthly plan,
- multiple rows created around the same time.
## How to identify refund-related rows [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Refunds or credits may appear as separate rows, status changes, or payment adjustments. Depending on the payment flow, a refund may not remove the original invoice row. Instead, the invoice remains as a record and the refund/credit is shown separately.
If the invoice is partially refunded, some rows may still be valid.
## Step-by-step: prepare an invoice question for Support [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
### 1\. Open the invoice detail page [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Go to your billing area and open the invoice you want reviewed.
### 2\. Copy the invoice ID [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
The invoice ID helps Support find the exact billing record.
### 3\. Copy the relevant bill IDs [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
If your question is about only some rows, copy those bill IDs. This is especially important for resize charges or invoices that include several servers.
### 4\. Check the service period [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
The service period helps Support calculate unused time for pro-rated managed server refunds.
### 5\. Explain what looks wrong [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Tell Support whether you are asking about:
- full invoice refund,
- selected bill row refund,
- pro-rated managed server refund,
- resize adjustment,
- cancelled subscription,
- deleted server charge,
- duplicate charge.
## How to decide whether the full invoice or selected bill rows need review [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Before asking for a refund, separate the invoice into two parts: the overall payment record and the individual bill rows. The full invoice should be reviewed only when every row on that invoice is connected to the same incorrect charge. If the invoice contains several rows, Support usually reviews only the rows connected to the issue.
For example, if an invoice includes one managed server resize row, one backup add-on row, and one unrelated renewal row, the refund request should mention the exact bill ID for the resize row. This avoids delaying the review and prevents unrelated valid charges from being included by mistake.
Use this simple checklist:
- If every row is wrong, ask Support to review the full invoice.
- If only one service is wrong, send the specific bill ID.
- If the issue is a managed server deletion, include the deletion date.
- If the issue is a resize, include the old plan, new plan, and resize date.
- If the issue is a refund already promised, ask Support to check the refund status instead of opening a new refund request.
## What xCloud Support can check [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Support can review:
- invoice status,
- payment status,
- eligible managed server rows,
- pro-rated refund calculation,
- resize-related bill IDs,
- backup add-on rows,
- whether a refund or credit was already applied.
## What to send xCloud Support [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Include:
- invoice ID,
- bill IDs,
- screenshot of the invoice rows,
- server name if available,
- cancellation, deletion, or resize date,
- expected correction,
- whether the issue is full invoice or selected rows only.
## FAQ [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
### Why did Support ask for bill IDs? [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Because one invoice can include several charges. Bill IDs help Support refund or review only the relevant line items.
### Can one invoice be partially refunded? [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Yes. If only some bill rows are eligible, the invoice can be partially refunded or adjusted.
### Why does a refunded invoice still show in my account? [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Invoices remain as billing records. A refund does not always remove the original invoice from your history.
### Does xCloud refund managed server unused time? [#](/docs/how-to-read-your-xcloud-invoice-with-xcloud/)
Yes. xCloud Managed Servers are eligible for pro-rated refunds for unused time when the service qualifies.
---
# How to Rebuild A Server With xCloud - xCloud
> Learn how to rebuild an xCloud server in a few simple steps through the settings panel. Choose your configuration and restart your server with a fresh setup quickly.
A server rebuild is one of the useful for the system administrators and developers. Whether you need to switch your database engine, upgrade to a newer version, or reset your environment to a clean state, a rebuild lets you reconfigure your server without provisioning new infrastructure from scratch.
Follow the steps to rebuild a server rebuild process on xCloud with easy steps.
_**Note:** This feature is currently available only for xCloud Managed servers. It is not yet supported on self-managed servers, but support for self-managed servers is coming soon._
## Step 1: Access Your Server Settings [#](/docs/how-to-rebuild-a-server-with-xcloud/)
First, navigate to the server you want to rebuild from your main dashboard. Once the server is open, click on the **Management** tab in the top navigation menu, and then select the **Rebuild Server** option.
## Step 2: Configure and Rebuild Your Server [#](/docs/how-to-rebuild-a-server-with-xcloud/)
Next, locate the **Rebuild Server** section within the Settings dashboard. To configure your new setup, choose the **Database** dropdown, either **MySQL** or **MariaDB** and your preferred version you want to install on your server.
_Note: You can install your preferred database, whether or not you have used it before._
After configuring the database, choose the **web server** you originally created (such as OpenLiteSpeed or Nginx) from the available options. Take a moment to review your selections and confirm that everything is correct, as the rebuild will apply these settings to your server. Once you are confident with the configuration, click the **Rebuild Server** button to start the rebuild process.
_**Note:** You can install your preferred web server, whether or not you have used it before._
**Important:** A server rebuild will reset your server’s configuration. Make sure to back up any critical data before proceeding.
The system will now begin rebuilding your server with the new configuration. The process typically takes a few minutes to complete, depending on your server size and the components selected.
And that’s it, this is how easily you can rebuild a server in a few clicks. Server rebuilds are an easier way to refresh your environment, switch database engines, or apply major version upgrades without the overhead of creating a new server.
Always remember to back up your data before initiating a rebuild, and double-check your database and web server selections to ensure they match your application’s requirements. If you run into any issues during the process, consult your hosting provider’s documentation or reach out to their support team for assistance.
## **Frequently Asked Questions** [#](/docs/how-to-rebuild-a-server-with-xcloud/)
### **1\. Will I lose my data during a server rebuild?** [#](/docs/how-to-rebuild-a-server-with-xcloud/)
Yes. A server rebuild wipes the disk and resets your server’s configuration. Always back up your databases, files, and any custom configurations before starting the rebuild process.
### **2\. Will my server’s IP address change after a rebuild?** [#](/docs/how-to-rebuild-a-server-with-xcloud/)
No. Your public IP address stays the same after the rebuild.
### **3\. Can I change my web server during the rebuild?** [#](/docs/how-to-rebuild-a-server-with-xcloud/)
Yes. You can select your preferred web server, such as OpenLiteSpeed or Nginx, before confirming the rebuild.
### **4\. Which servers support the Rebuild Server feature?** [#](/docs/how-to-rebuild-a-server-with-xcloud/)
The Rebuild Server feature is currently available only for xCloud Managed servers. Support for self-managed servers is coming soon.
---
# How to Remove a Card or Delete an xCloud Account - xCloud
> Users may sometimes need to update their billing information or close their account due to changes in subscription needs, billing preferences, or personal
Users may sometimes need to update their billing information or close their account due to changes in subscription needs, billing preferences, or personal circumstances.
Follow the process for removing a saved payment card and requesting the deletion of an xCloud account.
## Remove a Payment Card [#](/docs/how-to-remove-a-card-or-delete-an-xcloud-account/)
To remove or delete a payment card from your xCloud account, you must contact our support team. Once your request is received, our [support team](/support/) will remove the card from your account and downgrade your subscription to the Free Plan. Payment methods cannot be removed while an active paid subscription is in place, so the downgrade is required before the card can be deleted.
## Delete an xCloud Account [#](/docs/how-to-remove-a-card-or-delete-an-xcloud-account/)
To downgrade your account to the Free Plan or to delete your xCloud account, you must contact our support team. Our support team will handle the entire account deletion process and verify your account to ensure there are no servers and no active billing.
Once the verification is complete, we will permanently delete your account.
_We will soon add an option that allows users to manage this process on their own._
If you still have queries, feel free to contact our [support team.](/support/)
---
# How to Repair OpenClaw with an AI-Powered Agent With xCloud (OpenClaw Troubleshooting) - xCloud
> Learn how to repair OpenClaw and resolve 502 Bad Gateway, configuration errors, and gateway failures in under 90 seconds with xCloud.
[**OpenClaw**](https://openclaw.ai/), also known as Clawdbot, is an AI agent built to perform real actions instead of only replying to messages. It can sometimes run into issues that disrupt your workflow from unexpected crashes and dependency conflicts to configuration errors that are tricky to resolve.
With **[xCloud](/openclaw-hosting/)’s AI Powered OpenClaw Repair Agent**, you can automatically detect common OpenClaw errors, analyze system conflicts and apply guided fixes in seconds instead of hours.
Need to repair OpenClaw? Fix 502 errors, crashed gateways, and config issues automatically with xCloud’s AI Repair Agent.
**Follow the steps below to repair OpenClaw quickly and keep your setup running smoothly:**
## **What It Fixes** [#](/docs/how-to-repair-openclaw-with-xcloud/)
If you are on this page, something likely stopped working. The OpenClaw Repair Agent is designed to automatically detect and fix the most common OpenClaw issues without requiring manual server troubleshooting.
**It helps resolve:**
- OpenClaw showing a 502 Bad Gateway error
- Gateway service crashed or stuck after a server restart
- **“Pairing required”** error on the Control UI dashboard
- OpenClaw binary missing or corrupted after an OS or package update
- Configuration errors after manual edits or OpenClaw version upgrades
- Stale process (PID/lock) files causing **“already running”** startup failures
Instead of manually checking logs, reinstalling services or editing config files, xCloud handles the repair OpenClaw process safely and automatically.
## **How the Repair Agent Works** [#](/docs/how-to-repair-openclaw-with-xcloud/)
The OpenClaw Repair Agent runs in two structured phases. Understanding these phases helps you know exactly what happens behind the scenes.
### **Phase 1: Automatic System Repair (No AI Required)** [#](/docs/how-to-repair-openclaw-with-xcloud/)
This phase handles system-level issues automatically. **It will:**
- Check whether the OpenClaw binary is installed and reinstall it if missing or broken
- Clear stale PID or lock files that prevent OpenClaw from starting
- Detect if the Gateway service is not responding and reinstall/restart it
- Run a built-in health check **(****openclaw doctor****)** to detect hidden system problems
Most OpenClaw failures are resolved during this phase without needing AI intervention.
### **Phase 2: AI Configuration Repair** [#](/docs/how-to-repair-openclaw-with-xcloud/)
If the issue is related to configuration errors, the AI-powered repair phase begins. **This phase will:**
- Read your **openclaw.json** configuration file
- Detect syntax errors, invalid parameters, or version mismatches
- Send the broken configuration and error output to AI for analysis
- Apply the minimal required fix
Your API keys, connected channels, integrations and custom settings are never modified unless absolutely necessary to restore functionality. After applying the fix, the system verifies whether OpenClaw starts correctly. If needed, it retries up to 5 times to ensure a stable repair.
## **Automatic Backup Protection** [#](/docs/how-to-repair-openclaw-with-xcloud/)
Before making any changes, the Repair Agent creates a timestamped backup of the original configuration.
**This means:**
- The original openclaw.json file is safely stored before modification
- If all repair attempts fail, the system automatically rolls back to the original configuration
- Setup is never left in a worse state than before
This backup mechanism ensures safe AI repair and addresses **the most common concern:**
**“What if the AI breaks something?”**
With automatic rollback protection, your configuration is always secure.
## **Step 1: Open the OpenClaw Dashboard in xCloud** [#](/docs/how-to-repair-openclaw-with-xcloud/)
Log in to your xCloud account and open your OpenClaw instance dashboard.
From the left sidebar, navigate to **OpenClaw** → **Overview**. Here you will get the ‘**Repair’** button**.**
## **Step 2: Repair Your OpenClaw Issues** [#](/docs/how-to-repair-openclaw-with-xcloud/)
Click on the **‘Repair Button’.** A pop-up will appear showing Repair OpenClaw. Tap **‘Yes, Start Repair’**.
Then you will be redirected to the ‘**OpenClaw Gateway Status’**, where you’ll see your Gateway status as Checking and the ‘**OpenClaw Repair Agent’** actively running to fix any OpenClaw issues.
Within 90 seconds, you will see the **Gateway Final Status** of your OpenClaw, including any detected issues. Based on these issues, the **xCloud OpenClaw Repair Agent** will be running to fix them using the power of AI.
After a few seconds (within 90 seconds), you will see that your OpenClaw issues have been resolved, with an **Active Gateway Status** and the repaired issues displayed in the repair log.
Here, you will see a message indicating **OpenClaw Repair Finished** and **‘Repair complete! Gateway is running.** From here, you can review all the fixed configuration issues.
### **Additional Option:** [#](/docs/how-to-repair-openclaw-with-xcloud/)
You can also access the repair option directly from the OpenClaw Status. In the left sidebar, navigate to OpenClaw ‘**Status’**, where you’ll see the **‘Repair’** button. Clicking this button will start the repair process, just as described above.
## **Final Outcome** [#](/docs/how-to-repair-openclaw-with-xcloud/)
After the repair process completes successfully:
- The Gateway status becomes active
- The **502 Bad Gateway** error disappears
- Configuration issues are resolved
- OpenClaw starts running normally again
If the Repair Agent cannot resolve the issue after its automated attempts, it automatically rolls back to your original configuration, your setup is never left in a worse state than when you started. This ensures a safe, controlled and reversible repair process every time.
And that’s it. This is how easily you can repair OpenClaw issues on xCloud using its **AI-powered Repair Agent**. OpenClaw deployment on xCloud removes the complexity of [**self managed hosting**](/self-managed-hosting/) and lets you focus on what matters most.
## **What the Repair Agent Does NOT Fix** [#](/docs/how-to-repair-openclaw-with-xcloud/)
To set proper expectations, there are certain issues the Repair Agent cannot resolve. It does **not** fix:
- Billing or subscription-related issues
- Telegram bot token errors caused by revoked or invalid API keys
- Problems caused by unsupported server specifications (for example, servers with less than 4GB RAM)
- Network-level firewall or hosting provider restrictions
If your issue falls into one of these categories, you may need to manually update credentials, upgrade server resources, or contact support. Setting this expectation helps ensure the Repair Agent is used for technical repair scenarios it is designed to handle.
Still stuck? Feel free to reach out to our [**support team**](https://support.xcloud.host/) for any issues.
---
# How to Reset OpenClaw With xCloud (OpenClaw Troubleshooting) - xCloud
> Learn how to reset OpenClaw with xCloud safely. Wipe data, fix broken configs, and start fresh using the dashboard reset feature.
OpenClaw issues often appear after heavy testing, broken configurations, or failed integrations. Old data, stuck cron jobs, or misconfigured channels can prevent agents from working correctly. A clean reset removes these blockers and restores a stable environment.
A reset can help when troubleshooting no longer helps, or when you want to rebuild OpenClaw from scratch with a fresh setup. xCloud simplifies this process by offering a safe reset directly from the dashboard.
Follow the steps below to reset OpenClaw with xCloud.
## Step 1: Open the OpenClaw Dashboard in xCloud [#](/docs/how-to-reset-openclaw-with-xcloud/)
Log in to your xCloud account and open your OpenClaw instance dashboard.
From the left sidebar, navigate to OpenClaw → Reset. Here you will get details about the reset process.
## Step 2: Review Reset Details Carefully [#](/docs/how-to-reset-openclaw-with-xcloud/)
Read all the information shown on the reset screen before taking action. This reset action is irreversible and permanently deletes all OpenClaw data and memory.
### Data that will be deleted [#](/docs/how-to-reset-openclaw-with-xcloud/)
- All agent memory and conversation history
- All configuration files and custom settings
- All workspace files and documents
- All cron jobs and scheduled tasks
- All connected channels and integrations, such as Telegram.
### What happens during the reset [#](/docs/how-to-reset-openclaw-with-xcloud/)
- The current OpenClaw setup is backed up temporarily in /tmp
- A fresh OpenClaw installation starts automatically
- All channels and integrations require reconfiguration
- The gateway service restarts and may take around 30 seconds
## Step 3: Confirm and Reset OpenClaw [#](/docs/how-to-reset-openclaw-with-xcloud/)
Check the confirmation box that states you understand this action will completely wipe all OpenClaw data and memory. After confirming, click Reset OpenClaw to begin the process.
The OpenClaw reset feature in xCloud provides a reliable way to return to a clean state when needed. Use this option only when you are certain you no longer need the existing data or configurations. After the reset completes, set up your integrations, channels, and workflows again to continue using OpenClaw smoothly.
---
# How to Reset Uptime Kuma Password via CLI with xCloud - xCloud
> Reset Uptime Kuma password using the terminal on xCloud. Follow simple steps to regain access without two-factor authentication.
If you are using **[Uptime Kuma](/docs/deploy-uptime-kuma-with-xcloud/)** on xCloud and forgot your password, you can reset Uptime Kuma password using the terminal with CLI command. Follow the steps below to regain access to your monitoring dashboard.
## **Step 1: Open Your Terminal** **to Reset Uptime Kuma Password** [#](/docs/how-to-reset-uptime-kuma-password/)
First, SSH onto your server where Uptime Kuma is installed:
```
ssh your-user@your-server-ip
```
Copy to Clipboard
## **Step 2: Run the Reset Password Command** [#](/docs/how-to-reset-uptime-kuma-password/)
Uptime Kuma stores user information in a SQLite database file. Then navigate to your Uptime Kuma installation directory.
Once you are in the Uptime Kuma directory, run the following command:
```
npm run reset-password
```
Copy to Clipboard
This will launch a script that prompts you to enter a new password for your admin account. Follow the on-screen instructions to complete the reset.
## **Disable Two-Factor Authentication (Optional)** [#](/docs/how-to-reset-uptime-kuma-password/)
If you also lost access to your 2FA device or method, you can disable two-factor authentication using this command:
```
npm run remove-2fa
```
Copy to Clipboard
Run this in the same directory where Uptime Kuma is installed. It will remove 2FA from your admin account so that you can log in with just your username and new password.
And that’s it. This is how easily you can reset your [Uptime Kuma](https://uptime.kuma.pet/) password from the command line is even with xCloud. By using the built-in scripts, you can quickly regain access to your admin account and disable two-factor authentication if necessary.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How To Restore a Backup To Another Site In xCloud? - xCloud
> Learn how to restore a backup to another site for WordPress site in xCloud with a simple step-by-step process for safe and reliable site migration.
[**Backups**](/docs/site-backups-in-xcloud/) give you safety, but flexibility comes when you can move them across sites without friction. xCloud allows restoring to another site, a feature that lets you restore a WordPress site backup directly onto a different existing WordPress site on the same server or on a different one within your team.
This is useful for cloning a production site to a staging site, recovering a site using another site’s recent backup, or replacing a broken site’s content without creating a new site from scratch. Follow this to learn how to restore a backup to another site in xCloud:
## **Step 1: Go to Your Site** [#](/docs/how-to-restore-a-backup-to-another-site/)
Navigate to the source site in the dashboard. Open **‘Site Backup’ → ‘Previous Backups’** from the sidebar.
Now, click on the action menu on any backup. The action menu on each backup provides three restore options:
- **Restore Backup:** Restore to the same site (existing behavior)
- **Restore to Another Site:** Restore to a different existing WordPress site
- **Restore to New Site:** Create a new site from the backup
Select the ‘**Restore to Another Site**’ option to proceed.
## **Step 2: Select the Destination Server And Site** [#](/docs/how-to-restore-a-backup-to-another-site/)
In the modal that opens, use the Select Server dropdown to choose the target server. You can type to search by server name. Once a server is selected, the Select WordPress Site dropdown becomes active. Choose the site you want to overwrite with the backup.
## **Step 3: Confirm the Restore** [#](/docs/how-to-restore-a-backup-to-another-site/)
Then read the warning message carefully. Type “**RESTORE”** (in capitals) in the confirmation field to enable the Restore button and click on the ‘Restore’ button to start the restoration process.
Restoring a backup to another site in xCloud gives you a fast and controlled way to migrate or recover WordPress environments without manual setup. The process ensures data integrity by validating backup compatibility, protecting the destination site through confirmation steps, and allowing safe rollback if anything goes wrong.
Still stuck? Contact our **[Support team](https://support.xcloud.host/).**
---
# How to Run Commands in Your Site And Server Easily with xCloud? - xCloud
> Discover how to run commands on your site and server easily directly from the xCloud dashboard with simple step by guide.
With command runner Users can execute specific commands such as bash scripts or WP-CLI commands at both server and site levels. You do not need to access the command line interface manually, making the whole process faster and more efficient.
## **How to Run Commands from xCloud Dashboard on Your Website** [#](/docs/how-to-run-commands-in-your-site-and-server/)
You can easily run custom commands directly from xCloud dashboard with easily steps. Here is how you can do it:
### **Step 1: Select Your Website** [#](/docs/how-to-run-commands-in-your-site-and-server/)
Begin by logging into your server. Once you are in, choose the site where you wish to run the custom command. After selecting your site, navigate to the **Tools → Commands** option from the navigation menu.
### **Step 2: Run a Command on Your Website** [#](/docs/how-to-run-commands-in-your-site-and-server/)
Now click on the **‘Run Custom Command’** button which will bring up a popup dashboard where you can input your desired command.
### **Step 3: Easily Enter Your Commands** [#](/docs/how-to-run-commands-in-your-site-and-server/)
In the command box that appears, type in the command you want to execute. For example, you can run maintenance command using WP-CLI with xCloud. To activate maintenance mode, just run this code and hit on the ‘Run Command’ button:
wp maintenance-mode activate
### **Step 4: Final Outcome** [#](/docs/how-to-run-commands-in-your-site-and-server/)
Afterward, the command will be executed instantly. Now if you look the ‘Most Recent Commands’ box, you will find the the last 10 executed commands alongside the command that was executed,
- The user who initiated the command.
- When the command is executed
- The status of the command.
You can also check out the details of the executed command by clicking on the ‘Details’ button.
**_Note:_** _By default, only the team owner has access to the command runner. To grant access to other members, adjust the role permissions in the team management section._
By following these steps, you can effectively manage and run custom commands on your website.
## **Run Commands From xCloud Dashboard on Your Server** [#](/docs/how-to-run-commands-in-your-site-and-server/)
xCloud also allows you to execute such command in your server from directly the dashboard as well. Just choose the server and go to **Management → Commands** from the sidebar. Then click on the **‘Run Custom Command’** enter the command and click on the **‘Run Command’** to execute the command.
This is how easily you can run command in your site and server effortlessly and make server and site management more smoother. Whether you are updating plugins or performing other tasks, these tools give you the flexibility and control you need.
Still stuck? Contact our **[support](/support/)** team for any of your queries.
---
# How to Self Host LLMs with xCloud - xCloud
> Learn how to self host LLMs like Ollama and OpenWebUI with xCloud for full control, privacy, and easy cloud deployment.
With the growing popularity of large language models (LLMs), developers and businesses are increasingly looking for ways to host these powerful AI tools on their own servers. Self-hosting an LLM provides greater control over data privacy, customization, and performance, without relying on third-party platforms.
Learn how to self host LLMS and deploy OpenWebUI and Ollama with xCloud or your own cloud servers.
> _Note: Make sure your system has at least 20 – 30% more RAM than the model size before downloading._
>
> Also, If you want to use Ollama, we recommend deploying it on a GPU server for optimal performance and faster model inference.
### **Step 1: Create a Docker+ NGINX Server** [#](/docs/how-to-self-host-llms-with-xcloud/)
First, you need to **[create a server](/docs/setup-your-first-server-site-with-xcloud/)** to deploy any LLMs. Click on the **‘Add New Server**’ button from the dashboard and enter all the credentials required to connect your server. You can deploy Ollama on your own server or on an xCloud server.
Next, enter a**‘Server Name’** and choose an **‘App Type’** from the dropdown menu. You will see all available application types here, including **‘OpenWebUI’** and **‘Ollama,’** which will provide the user with the necessary configuration settings.
Then choose a ‘**Server Size**’ and ‘**Region**’ of the server according to your preferences.
Then choose your preferred **‘Ubuntu Version’** of this server and enter the ‘**Tags’** for this server.
Next, you can see the ‘**Docker + NGINX**’ stack is already selected, which is mandatory for deploying the LLM application.
Once the server is created, you will be able to deploy your OLLAMA Application to this server.
> After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## **How to Install Ollama on a Cloud Server** [#](/docs/how-to-self-host-llms-with-xcloud/)
Learn how to install Ollama on a cloud server. It walks you through creating a server, configuring the environment, and launching your Ollama application easily.
### **Step 2: Access the One Click Apps Dashboard** [#](/docs/how-to-self-host-llms-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button. Then choose your server and click on the **‘Next’** button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One-Click Apps section. You will see two options: OpenWebUI and Ollama. Choose Ollama to proceed with the deployment of this application.
### **Step 3: Set Up the Ollama Application** [#](/docs/how-to-self-host-llms-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags**’ to help organize your deployment.
At this point, you can choose between two deployment modes: ‘**Go Live**’ for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live**’ will immediately create a live environment, while choosing **‘Demo Site**’ allows you to experiment in a staging environment before promoting it to production.
### **Step 4: Configure Domain Settings** [#](/docs/how-to-self-host-llms-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your Ollama application. You can adjust the **‘Site User’** according to your preferences, or leave it as the default.
## **Step 4: Visit the Ollama Application** [#](/docs/how-to-self-host-llms-with-xcloud/)
With Ollama set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** app.
### **Environment Editor for Ollama** [#](/docs/how-to-self-host-llms-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your Ollama instance. Just go to the ‘Environment’ option from the sidebar and adjust as you need, then click on the **‘Save’** button.
### **Manage Ollama Models** [#](/docs/how-to-self-host-llms-with-xcloud/)
Later, you can manage your Ollama application. Go to the **‘Ollama’ → ‘Management’**. Next, click on the**‘Add New Model’** to install more AI models. Also, you can click on the ‘Delete Icon’ to delete the AI models of this application.
## **How to Install OpenWebUI on a Cloud Server** [#](/docs/how-to-self-host-llms-with-xcloud/)
Learn how to set up OpenWebUI on a cloud server and get it running quickly. It covers server setup, application configuration, and accessing your deployed site, making it easy to get started regardless of your technical background.
> _Note: It is recommended that you install Ollama before installing OpenWebUI app._
### **Step 1: Access the One Click Apps Dashboard** [#](/docs/how-to-self-host-llms-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the ‘New Site’ button. Then choose your server and click on the ‘Next’ button to proceed.
This will take you to the Site Creation Interface. From here, choose your Server, then go to the One-Click Apps section. You will see two options **‘OpenWebUI’** and **‘Ollama’**. Choose ‘**OpenWebUI**’ to begin deploying the application.
### **Step 2: Set Up the OpenWebUI Application** [#](/docs/how-to-self-host-llms-with-xcloud/)
In the site setup screen, you will be asked to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** for your application.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing ‘Demo Site’ allows you to experiment in a staging environment before promoting to production.
### **Step 3: Configure Domain Settings** [#](/docs/how-to-self-host-llms-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your OpenWebUI application. Adjust the Site User according to your preferences, or leave it as the default.
### **Step 4: Install Ollama Application** [#](/docs/how-to-self-host-llms-with-xcloud/)
If you want to install Ollama, toggle on the installation option and choose a model from the dropdown menu. Then, click **‘Next’** to proceed with the installation.
### **Step 5: Visit the OpenWebUI Application** [#](/docs/how-to-self-host-llms-with-xcloud/)
Once OpenWebUI is set up on xCloud, you can log in to confirm that it’s working. From the dashboard, click on **‘Visit Site’**.
### **Environment Editor for OpenWebUI** [#](/docs/how-to-self-host-llms-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your OpenWebUI instance. Just go to the ‘Environment’ option from the sidebar and adjust as you need, then click on the ‘Save’ button.
### **Manage AI Models** [#](/docs/how-to-self-host-llms-with-xcloud/)
Later, you can manage your OpenWebUI application. Go to the **‘OpenWebUI’ → ‘Management’**. Next, click on the **‘Add New Model’** to install more AI models. Also, you can click on the **‘Delete Icon’** to delete the AI models of this application.
Self-hosting LLMs with xCloud empowers developers and businesses to take full control of their AI deployments, ensuring data privacy, customization, and optimized performance.
By following the instructions for setting up Docker + NGINX servers, deploying Ollama, and configuring OpenWebUI, you can quickly get your AI models up and running on a cloud environment tailored to your needs. With xCloud’s One Click Apps, Environment Editor, and model management tools, maintaining and scaling your LLM deployments becomes straightforward and efficient
Still stuck? Contact our [**support team**](https://app.xcloud.host/support/all-tickets) for any of your queries.
---
# How to Set the Default Site For Your Server - xCloud
> Learn how to replace the generic server landing page with your preferred website or domain in just a few clicks.
When someone accessed your server using its IP address, they were previously shown a generic default page. With the new Default Site feature, you can now replace that page with your own chosen website or domain. This lets you control what visitors see first and create a more intentional, branded landing experience.
This helps you control where visitors land by automatically redirecting them to the site you prefer. Follow the steps below to set it up quickly and easily.
_**Note: If anyone points any domain or subdomain, it will redirect to the default domain.**_
## **Step 1: Go to Your Server** [#](/docs/how-to-set-the-default-site-for-your-server/)
Begin by logging into the server where you want to set the default site. Once you’re on the server dashboard, navigate to the **‘Others’** section.
## **Step 2: Configure Default Site Settings** [#](/docs/how-to-set-the-default-site-for-your-server/)
Next, locate the **‘Set Default Site Settings’** section. Toggle the **‘Default Site Redirection’** switch to enable the feature. After enabling it, you will see two options ‘**Choose from Existing Site’, ‘Use Other Domain’**
### **Using an Existing Site** [#](/docs/how-to-set-the-default-site-for-your-server/)
Select **“Choose from Existing Site”** to pick your preferred site from the dropdown menu.
### **Using a Different Domain** [#](/docs/how-to-set-the-default-site-for-your-server/)
If you want to set a separate domain as the default, select **“Use Other Domain”** and enter the domain name you want to use.
And that’s it! This is how easily you can set a custom landing page for your server and replace the old default view. With just a few steps, you can guide visitors to the page you want them to see first.
If you use your existing site, when you update the domain of that site, it will automatically update the server’s default domain redirection as well.
---
# How To Set Up AWS Server In xCloud? - xCloud
> Discover how to integrate and setup AWS server in xCloud seamlessly and easily manage from xCloud dashboard.
AWS, or Amazon Web Services, provides comprehensive cloud solutions. Using AWS and setting up a server in xCloud is simple. **Amazon Web Services** (AWS) offers both **EC2** and Lightsail instances for cloud computing. EC2 provides flexibility, scalability, and advanced configurations, while **Lightsail** simplifies the process with pre-configured environments.
You can easily set up an AWS server in [**xCloud**](/) for both EC2 and Lightsail instances. This self-managed hosting aims to simplify the hosting and managing of WordPress sites, allowing developers and agencies to focus on building great websites without worrying about the underlying infrastructure. Now let us follow these steps to get you started.
### **Step 1: Sign Up/Login With xCloud** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
To [**create the AWS server**](https://app.xcloud.host/) in xCloud, the first step is to visit the xCloud website and create your account or log in using your existing credentials. Once you are signed, you can effortlessly set up your AWS server.
If you already have an account please [**visit our app URL**](https://app.xcloud.host/) to log in to your account to set up an AWS server in xCloud Host.
### **Step 2: Create Your AWS Server In xCloud** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **‘Add New Server’** button from your dashboard.
The next screen will provide the list of our available server providers. Select the AWS option from the list. The billing of the server will be handled on your AWS account.
### **Step 3: Sign In to the AWS Management Console** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
Now, before going to the next step, you need to log in to the AWS management console. Sign in as a **‘Root User’** to the [**AWS Management Console**](https://aws.amazon.com/console/) using your AWS account credentials. Once logged in, navigate to the main dashboard where you can access various AWS services.
### **Step 4: Navigate to the IAM Console** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
From the AWS Management Console, click on the Services menu located at the top left corner or search with **“IAM”** and select **IAM** from the list of services. This will direct you to the IAM dashboard, where you can manage users, groups, roles, and policies.
### **Step 5: Add a New User** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
On the IAM dashboard, locate and click on the Users option in the left navigation panel. This will display a list of existing IAM users. To create a new user, click on the **‘Create User’** button.
### **Step 6: Configure User Details** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
In this step, enter a unique ‘**Username’** for the new IAM user. Next, choose the type of access the user requires. Check-in **‘AWS Management Console’** access option if the user requires access to the AWS Management Console and click on the ‘**Next**’ button.
### **Step 7: Set Permissions for Amazon EC2 Instance** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
You have three options to set permissions for the new user. The first one is ‘**Add user to group’** which lets you add the user to an IAM group with predefined permissions, which is efficient for managing multiple users with similar access needs. The second one is ‘**Copy permissions’** which enables you to duplicate the permissions of another IAM user. And the final policy ‘**Attach policies directly’** allows you to assign AWS-managed policies or custom policies.
Here we are choosing the **‘Attach policies directly’** and assigning the access for [**Amazon EC2 Instance**](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to the user and hit on the **Next**.
**_Note:_** _If you do not find the EC2 Access here, search for the policy in the search bar._
### **Step 8: Add Tags, Review and Create** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
You can add ‘**Tags’** to help organize and manage users. Now carefully review all the details and permissions assigned to the new IAM user. If everything is accurate and complete, click the ‘**Create user**’ button to finalize the creation of the IAM user.
### **Step 9: Give Another permission for Amazon Lightsail** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
Now, set another permission for the new user for [**Amazon LightSail**](https://docs.aws.amazon.com/decision-guides/latest/lightsail-or-ec2/lightsail-or-ec2.html) easily. To specify the permissions for the created user, go to the Permission Policies and click on the **‘Add Permissions Menu’**. Choose the **‘Create Inline Policy’** option from the dropdown menu.
Click on the ‘**JSON’** button from the **Policy Editor** and paste the below given JSON code in the editor. Finally, tap on the **‘Next’** button.
Here is the **JSON** code:
Copy to clipboard
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
{
"Version": "2012-10-17",
"Statement": \[
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": \[
"lightsail:GetInstances",
"lightsail:GetKeyPair",
"lightsail:DeleteKeyPair",
"lightsail:GetStaticIp",
"lightsail:ReleaseStaticIp",
"lightsail:SetIpAddressType",
"lightsail:CreateInstances",
"lightsail:GetInstance",
"lightsail:GetInstanceAccessDetails",
"lightsail:DeleteInstance",
"lightsail:CreateKeyPair",
"lightsail:ImportKeyPair",
"lightsail:StartInstance",
"lightsail:DownloadDefaultKeyPair",
"lightsail:GetInstancePortStates",
"lightsail:StopInstance",
"lightsail:AttachStaticIp",
"lightsail:GetRegions",
"lightsail:RebootInstance",
"lightsail:GetOperation",
"lightsail:DetachStaticIp",
"lightsail:GetInstanceState",
"lightsail:GetBundles",
"lightsail:TagResource",
"lightsail:PutInstancePublicPorts"
\],
"Resource": "\*"
}
\]
}
Once the policy is created for Lightsail instance, give the policy a name and hit on the **‘Create Policy’** button.
### Step 10: Create & Retrieve a User Access Key [#](/docs/how-to-set-up-aws-server-in-xcloud/)
Now we have to create a user access key. Find **‘Create access key’** under the Summary tab and click on it. Then you will be redirected to the **Access Key best practices & Alternatives page,** from here select the ‘**Other’** option and click on Next.
Now give a Description Tag to proceed to create an access key. Once the access key is created copy the Access Key and Secret from from here and go back to your xCloud Dashboard to integrate the server with xCloud.
### **Step 11: Connect the Account & Add Necessary Information** [#](/docs/how-to-set-up-aws-server-in-xcloud/)
From the AWS dashboard, select an existing or connect new account from the dropdown menu. Then choose the AWS services from, you can use any one with the proper credentials or both from the xCloud dashboard.
_Note: EBS-supported instances of AWS are not supported. For example, T3 instances use EBS storage. These instances are not available through the API. However, you can set up such instances manually in your AWS account first and then add them through the **Any Provider** method in xCloud._
As you have the Access Key and Secret Key Paste them into the designated blank boxes one by one carefully. Now click on **‘Verify’** button, it will start verifying the credential and connect you with the AWS server.
Fill all the information like **‘Server Name’, ‘Server Region’, ‘Server Zone’,’Server Size’,** etc according to your preference.
Next, choose the web server stack from **NGINX** or **OLS** as your requirements and click on **‘NEXT’** button to proceed with the server creation process.
It will start creating a AWS server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many site as you want under this server
This is how easily you can create an AWS server from xCloud seamlessly without going through any difficulties.
After creating your server with AWS, you would want to create your first site with xCloud. Follow [**this documentation**](/docs/how-to-create-a-site-with-xcloud/) to learn how to do that. You can also take a look at how to add [**xCloud managed email servic**e](https://xcloud.host/docs/add-xcloud-managed-email-service/) for WordPress site emails.
Still stuck? Contact our **[support team](https://support.xcloud.host/)** for any of your queries.
---
# How to Set Up Email Alias with MailBox Addon - xCloud
> Learn how to set up email alias with the xCloud MailBox Addon to manage multiple addresses in one inbox.
Aliases allow you to create extra email addresses that redirect to existing mailboxes without needing to set up new ones.
For instance, if you own a mailbox, user@example.com, and wish to receive emails at another address, user2@example.com, without having a separate mailbox, you can establish user2@example.com as an alias that directs to user@example.com. Now, you only need to log in to user@example.com to check the emails received at both addresses.
Follow the step-by-step process to set up email Alias with xCloud MailBox Addon:
## **Step 1: Go to Your MailBox Account** [#](/docs/how-to-set-up-email-alias-with-mailbox-addon/)
First, go to the MailBox addon, click on your MailBox, and head over to the ‘Aliases’ tab from the dashboard.
## **Step 2: Add an Email Alias** [#](/docs/how-to-set-up-email-alias-with-mailbox-addon/)
Click the **‘Add New’** button. A pop-up will appear allowing you to add a new alias email address. Enter the alias and select the domain from the dropdown menu.
Next, select the email address you wish to be a member of that alias. Finally, click on the **‘Add Alias’** button.
Next, you will see that your email address has been added as an Alias. You can also delete the email. Just click on the three-dot icon, choose the ‘Delete’ option, and click on the ‘OK’ button.
And that’s it. This is how easily you can set up aliases with the xCloud MailBox Addon. It is a simple way to manage multiple email addresses without the need for separate MailBoxes.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up FFmpeg in Your Server - xCloud
> Learn how to check, install, and set up FFmpeg on your server for smooth multimedia processing.
FFmpeg is a powerful and widely used tool for handling audio, video, and multimedia files. It supports converting, recording, and streaming media content. Whether you are developing an application or working on a media project, having FFmpeg properly set up is essential for smooth performance.
Follow the steps below to check and set up FFmpeg FFmpeg is already installed on your server.
## **How Can You Check If FFmpeg Is Already Installed?** [#](/docs/how-to-set-up-ffmpeg-in-your-server/)
To find out if FFmpeg is already installed on your server, you need to connect to it using a terminal or SSH. Once connected, you can run a simple command to check for its presence.
To find the installation path, use this command:
```
which ffmpeg
```
Copy to Clipboard
If FFmpeg is installed, this command will return a path like:
```
/usr/bin/ffmpeg
```
Copy to Clipboard
To check the version of FFmpeg installed, run this command:
```
ffmpeg -version
```
Copy to Clipboard
If FFmpeg is installed, this will show you the version details. If the command is not recognized, it means FFmpeg is likely not installed on your server.
## **How Do You Install FFmpeg With Root Access?** [#](/docs/how-to-set-up-ffmpeg-in-your-server/)
If you have root access or sudo privileges, you can install FFmpeg directly using the command line. This is useful if FFmpeg is not already installed or if you need to upgrade to a newer version.
On servers that run Ubuntu or Debian, you can start by updating the package list. Run this command:
```
apt update
```
Copy to Clipboard
Then, install FFmpeg using this command:
```
apt install ffmpeg -y
```
Copy to Clipboard
Once the installation is finished, verify the installation by checking the version. Use this command:
```
ffmpeg -version
```
Copy to Clipboard
You should see the installed version of FFmpeg. The binary is usually located at
```
/usr/bin/ffmpeg
```
Copy to Clipboard
Properly configuring FFmpeg allows your application or server to process media files without encountering errors. Checking the installation and performing a straightforward setup with root access only takes a few minutes.
And that is how easily you can make sure that FFmpeg is available and ready to support your multimedia needs.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Set Up Hermes Workspace with xCloud - xCloud
> Learn how to set up Hermes Workspace with xCloud. Connect your own dashboard or let xCloud host it, then add a custom domain and secure it
Hermes Workspace is a dedicated web command center for your Hermes Agent. It connects to the agent over an authenticated HTTP API, so you can manage and interact with your agent from a single browser-based dashboard instead of juggling separate tools.
This guide walks you through the full setup inside xCloud: enabling the API server, generating a secure access token, pointing your own domain at the Workspace, securing it with SSL, and deploying it. By the end, you will have a live Hermes Workspace ready to open and use. The entire process takes only a few minutes, and most settings come preconfigured with safe defaults.
## Before You Begin [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
Make sure you have an active xCloud account with a Hermes Agent already running. If you plan to use a custom domain, have access to your domain provider’s DNS settings, or a connected Cloudflare account, ready to go.
## Step 1: Open the Hermes Dashboard [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
From your xCloud dashboard, go to the Hermes Agent page. Select Hermes from the sidebar menu, then click the Workspace option from the menu.
## Step 2: Enable the API Server [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
The Workspace connects to your agent over an authenticated HTTP API. Enable the API server to generate a shared token that any Workspace can use to connect.
## Step 3: Generate the API Token [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
Click the Rotate token button to generate your API key. Once the token appears, copy it and store it somewhere safe. You will need it to authenticate the connection, and it will not be shown again in full.
## Step 4: Add a Domain & Set Up SSL [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
Enter a custom domain for your Workspace. You have two options to verify it. Add the provided records with your domain provider and verify the DNS manually, or connect your domain through Cloudflare and verify the DNS on xCloud with a single click. A free SSL certificate is enabled by default, so your Workspace is secured automatically. If you prefer, you can use your own SSL certificate instead.
## Step 5: Configure a Docker Image (Optional) [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
If your setup requires it, you can also configure a Docker image for the Workspace at this stage.
Once all your settings are in place, click Deploy Workspace to begin configuration. xCloud will provision everything for you.
## Step 6: Open Your Workspace [#](/docs/how-to-set-up-hermes-workspace-with-xcloud/)
After a short wait, you will see that the Hermes Workspace has been deployed. Copy the password, then click the Open Workspace button to go straight to your Hermes Workspace dashboard.
Next, you will be redirected to the Hermes Workspace’s login page, enter the password you have copied and click on the ‘Continue’ button.
Your Hermes Workspace is now live and connected to your Hermes Agent through a secure, authenticated API. From the Workspace dashboard, you can manage your agent, run tasks, and monitor activity, all from one place in the browser.
Keep your API token and Workspace password stored securely, and rotate the token whenever you need to refresh access. With the setup complete, you are ready to put Hermes Workspace to work.
Still stuck? Please contact our [**support team.**](https://support.xcloud.host/)
---
# How to Set Up Hide My WP plugin in xCloud? - xCloud
> Hide My WP Ghost is a WordPress Security plugin. Discover how to set up hide my wp plugin in xCloud for your NGINX server and OLS server.
[**OpenLightSpeed**](https://openlitespeed.org/) & [**NGINX**](https://www.nginx.com/) are the top choices for web servers for their adaptability and strength. Many online services and applications use **NGINX** and **OLS** and customise them to boost their system’s efficiency, secure their data, and add new features. However, you might find it challenging to configure custom NGINX and OLS settings, as it often requires manual edits in the Linux terminal.
But with [**xCloud**](/), you can simplify this process. You can set up the Hide My WP plugin in xCloud, which lets you add a custom OLS and NGINX easily. **Hide My WP Ghost** is a WordPress security plugin that provides robust protection for your website without physically altering any directories or files.
_**Note:** For the OLS server, you need to install and activate the plugin by yourself; on the other hand, for NGINX, you do not need to go through this complex process._
## **How to Configure Custom OLS in xCloud** [#](/docs/how-to-set-up-hide-my-wp-plugin-on-xcloud/)
You can easily set up custom **OLS** from the xCloud dashboard with some simple steps. Now let’s follow these steps to get you started.
### **Step 1: Navigate to the xCloud Dashboard** [#](/docs/how-to-set-up-hide-my-wp-plugin-on-xcloud/)
To set up the **Hide My WP** **Ghost** plugin first, log in and go to the xCloud dashboard. Then move on to the ‘**All Servers’** tab and select the OLS server.
Select the site, where you want to install the **Hide My WP Ghost** plugin and Click on the **‘Magic Login’** button to directly access your site’s WordPress dashboard from the xCloud dashboard.
### **Step: Install and Activate the Hide my WP Ghost plugin** [#](/docs/how-to-set-up-hide-my-wp-plugin-on-xcloud/)
After going to your site’s WP dashboard, select the **plugins → Add new plugin** and search for the Hide My WP Ghost plugin. Now install the plugin, and activate it from here.
### **Step: Go to the Compatibility Settings** [#](/docs/how-to-set-up-hide-my-wp-plugin-on-xcloud/)
Afterwards, first you need to go to the **‘Advanced’** section of the sidebar and proceed with the **‘Compatibility’** option.
Now, you will get a drop-down menu of **‘Server types’**, find out the server type, look for the OLS server from the drop-down menu of the server names, and click on the **‘Save’** button.
Now, go to the ‘**Change paths**’ from the sidebar of your WordPress dashboard and look for the ‘**Ghost Mode**’ option. From here, just activate this.
Afterwards, go back to your **xCloud dashboard → OLS server** and head over to the **‘Sever Management’** tab and click on the restart the LightSpeed server.
And the **Hide MY WP Ghost** will sync and start protecting your website.
## **How to Configure Custom NGINX in xCloud** [#](/docs/how-to-set-up-hide-my-wp-plugin-on-xcloud/)
Moreover, we are offering to [**set up built-in custom NGINX**](/docs/configure-custom-nginx-xcloud/) support for RankMath and Hide My WP on the xCloud dashboard. That means, if your website has the RankMath or Hide My WP plugins installed, you can choose from the ‘Select Template’ list, and you’re all good to go. Or else, you can choose **‘Use My Own Config’** to run your config manually. However, we will be gradually adding more plugins.
That is how easily you can configure custom OLS and NGINX in **xCloud**.
Still stuck? Contact our **[dedicated support team](https://support.xcloud.host/)** for any of your queries.
---
# How to Set Up Laravel on DigitalOcean Server with xCloud? - xCloud
> Learn how to set up Laravel on DigitalOcean server. This guide covers server creation, deployment steps and Laravel configuration with xCloud.
[**Laravel**](/laravel-hosting/) is a popular PHP framework for building modern web applications. With DigitalOcean’s cloud hosting and xCloud’s one‑click deployment, you can set up Laravel on DigitalOcean Server quickly and manage it with ease. This guide walks you through the process step by step.
First, set up your DigitalOcean server in xCloud. Follow these steps to get started.
## **How to Set Up a DigitalOcean Server in xCloud?** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
This guide shows how to set up a DigitalOcean server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Create Your New DigitalOcean Server in xCloud** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a Digital Ocean server and for that select the [**DigitalOcean**](https://xcloud.host/go/digitalocean/) option. The billing of the server will be handled on your Digital Ocean account.
**Note:** Don’t have a DigitalOcean account? Check out the documentation below to find out how to provision a server with any providers:
- [**How To Setup First Server With Vultr?**](/docs/how-to-get-free-hosting-with-vultr/)
- [**How To Setup Your First Server With Google Cloud Platform Provider?**](https://dev1.xcloud.host/docs/first-server-with-google-cloud-platform)
- [**How To Setup a Server With Other Providers?**](https://dev1.xcloud.host/?post_type=docs&p=268&preview=true)
We’ve made it easier and safer for you to connect xCloud with your DigitalOcean account. You no longer have to go through the hassle of generating and copying access tokens.
Now, xCloud will guide you through an OAuth flow, where you simply authorize xCloud to use your DigitalOcean account.
All you have to do is provision a new DigitalOcean server, click **“Authorize”** during the setup, and you’ll be redirected to DigitalOcean to grant permission to your account. It’s a straightforward and hassle-free process to set up your server with Digital Ocean.
### **Step 3: Add Necessary Information** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
You will be taken to the server creation page after successfully integrating your DO account. Now you need to provide the Server name, your preferred Server Size (**CPU, RAM, Storage**) and Region nearest to you and your visitors. Only, **MySQL 8.0** database server is now available.
By default Database, the **‘Root’** Password is auto-filed but you can change this and save it in a safe place.
We recommend at least a **2GB/ 1 shared CPU server** for 10-20 sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a **4 GB / 2 dedicated CPUs server**.
We are almost done with our server creation of Digital Ocean in xCloud. After submitting the form this might take **up to 12-15 minutes** to make the Digital Ocean server live and ready to install a lightning fast WordPress Site.
If you already have a [**DigitalOcean server**](https://www.digitalocean.com/), you can skip the first phase and proceed directly to the second. Follow these steps to get started.
## **How to Set Up Laravel on DigitalOcean Server: Deploy Laravel Applications with xCloud** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Deploying a **[Laravel application](/laravel-hosting/)** can feel complex, with multiple steps and detailed setup. This guide walks you through everything from configuration to deployment, so you can set up Laravel on DigitalOcean Server.
### **Step 1: Choose Your Server** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘Add New Site’** button.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **DigitalOcean server** you set up in xCloud from this dropdown.
### **Step 2: Go to The Laravel Tab** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Then navigate to the ‘**Laravel’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
### **Step 3: Set Up Domains** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch or you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the **‘Migrate into a New Domain’** option. Then you have to put **‘New Site Title’** and **‘Domain Name’**. Here we are choosing the **‘Demo Site’** domain. Then click on **‘Next’**.
### **Step 4: Settings to Manage Database** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your **‘PHP Version’**, **‘Site User’**, **‘Web root’**.
Now, it is time for database management. You will get three options. You can either create a new database on the server, you can add your existing database that is hosted on another server.
You can also proceed without a database. For this tutorial, we are going with the **‘Create Database In Server’** option.
If you select this option, enter your **‘Database Name’**, **‘Database Username’** and **‘Database Password’**. You can keep these auto-generated credentials or you can modify them according to your choice.
After selecting any one option and providing all essential information and credentials, click on **‘Next’**.
### **Step 5: Insert Git Repository Credentials** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
In the **‘Git Repo’** tab, add your **‘Git Repository’** and **‘Git Branch’**. Also, toggle on the **‘Enable push to deploy’** option. Once you enable the **‘Push To Deploy’**, it will generate a **‘Deployment URL’**. We can use this URL to CICD pipeline and copy the **‘Deployment URL’** from here.
### **Step 6: Add the Deployment URL to the Git Repository** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Now, go to your Git repository. From the **‘Code’** tab, go to the **‘Settings’** tab and click on the **‘Webhooks’** page from the **‘Code and Automation’** section of the left navigation. Insert the deployment URL into the **‘Payload URL’** field. Select **‘application/json’** from the **‘Content type’** dropdown.
_**Note:** This step is optional. Adding a webhook enables automatic deployments when you push changes to the repository but it’s not required if you prefer to deploy manually._
### **Step 7: Add Public Key to Git Repository** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Next, in the ‘Deploy Script’ field, any script that needs to be executed after the site is deployed. For example, you can use it to install dependencies or run database migrations.
Next, in the **‘Deploy Script’** field, specify any commands that need to be executed after the site is deployed.
If your project uses PHP, you can specify the version _(e.g., php8.1)_ and run Composer along with **Laravel-specific commands like this:**
php8.1 $(which composer) install --no-interaction --prefer-dist --optimize-autoloader --no-dev
php8.1 artisan migrate --force
php8.1 artisan optimize:clear
If your project also involves Node.js, you can include additional commands as well. These scripts ensure that your backend and frontend are fully prepared after deployment.
From the xCloud dashboard, copy the ‘**Public Key’** to add it to your Git repository as a deploy key. Git migration uses the **‘Public Key’** for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the **‘Code’** tab, go to the ‘**Settings’** tab and click on **‘Deploy Keys’** in the security section of the left navigation. Click on the **‘Add key’** button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on **‘Next**’ on your xCloud settings of the **‘Git Repo’** tab.
### **Step 8: Confirm Migrating The Website** [#](/docs/how-to-set-up-laravel-on-digitalocean-server/)
Now, to start the migration process, click on the **‘Start’** button. After clicking the migration process will start and you will see the progress of migration.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there. Go to the **‘Laravel’** Option from the menu and customize the **‘Application’** and **‘Environment’** as your preferences.
**Check out the other features of Laravel:**
- [_How to Use Supervisor for Process Management With xCloud_](/docs/supervisor-for-process-management/)
- [_How to Set Up Laravel Horizon with xCloud_](/docs/set-up-laravel-horizon/)
- [_How to Set Up a Queue Worker for Laravel Applications_](/docs/set-up-queue-worker-for-laravel-applications/)
Configure Laravel Scheduler with cron job for your Laravel projects with ease. Check out this documentation for more details:
- [_How To Configure xCloud Cron Job?_](/docs/how-to-configure-xcloud-cron-job/)
And that’s it. This is how easily you can successfully deploy your Laravel application on xCloud. Now you can go to your site dashboard from xCloud and customize according to your preferences.
If you are still stuck, feel free to contact our [**support team**](/support/).
---
# How to Set Up Lovable on AWS with xCloud? - xCloud
> Learn how to set up Lovable on AWS with xCloud. Deploy AI powered apps easily, manage servers, and streamline application development.
[**Lovable**](/lovable-hosting/) is a modern AI-powered application-building platform designed to help anyone create user-friendly, scalable, and production-ready applications and websites through chatting.
Set up **Lovable** on AWS with xCloud quickly and easily. This guide walks you through the basic steps to configure and launch Lovable on a AWS server, helping you streamline deployment and manage your application with minimal effort
You can easily set up an AWS server in [**xCloud**](/) for both EC2 and Lightsail instances. Now let us follow these steps to get you started.
### **Step 2: Create Your AWS Server In xCloud** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **‘Add New Server’** button from your dashboard.
The next screen will provide the list of our available server providers. Select the AWS option from the list. The billing of the server will be handled on your AWS account.
### **Step 3: Sign In to the AWS Management Console** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
Now, before going to the next step, you need to log in to the AWS management console. Sign in as a **‘Root User’** to the [**AWS Management Console**](https://aws.amazon.com/console/) using your AWS account credentials. Once logged in, navigate to the main dashboard where you can access various AWS services.
### **Step 4: Navigate to the IAM Console** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
From the AWS Management Console, click on the Services menu located at the top left corner or search with **“IAM”** and select **IAM** from the list of services. This will direct you to the IAM dashboard, where you can manage users, groups, roles, and policies.
### **Step 5: Add a New User** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
On the IAM dashboard, locate and click on the Users option in the left navigation panel. This will display a list of existing IAM users. To create a new user, click on the **‘Create User’** button.
### **Step 6: Configure User Details** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
In this step, enter a unique ‘**Username’** for the new IAM user. Next, choose the type of access the user requires. Check-in **‘AWS Management Console’** access option if the user requires access to the AWS Management Console and click on the ‘**Next**’ button.
### **Step 7: Set Permissions for Amazon EC2 Instance** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
You have three options to set permissions for the new user. The first one is ‘**Add user to group’** which lets you add the user to an IAM group with predefined permissions, which is efficient for managing multiple users with similar access needs. The second one is ‘**Copy permissions’** which enables you to duplicate the permissions of another IAM user. And the final policy ‘**Attach policies directly’** allows you to assign AWS-managed policies or custom policies.
Here we are choosing the **‘Attach policies directly’** and assigning the access for [**Amazon EC2 Instance**](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to the user and hit on the **Next**.
**_Note:_** _If you do not find the EC2 Access here, search for the policy in the search bar._
### **Step 8: Add Tags, Review and Create** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
You can add ‘**Tags’** to help organize and manage users. Now carefully review all the details and permissions assigned to the new IAM user. If everything is accurate and complete, click the ‘**Create user**’ button to finalize the creation of the IAM user.
### **Step 9: Give Another permission for Amazon Lightsail** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
Now, set another permission for the new user for [**Amazon LightSail**](https://docs.aws.amazon.com/decision-guides/latest/lightsail-or-ec2/lightsail-or-ec2.html) easily. To specify the permissions for the created user, go to the Permission Policies and click on the **‘Add Permissions Menu’**. Choose the **‘Create Inline Policy’** option from the dropdown menu.
Click on the ‘**JSON’** button from the **Policy Editor** and paste the below given JSON code in the editor. Finally, tap on the **‘Next’** button.
Here is the **JSON** code:
📋
JSON
{
"Version": "2012-10-17",
"Statement": \[
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": \[
"lightsail:GetInstances",
"lightsail:GetKeyPair",
"lightsail:DeleteKeyPair",
"lightsail:GetStaticIp",
"lightsail:ReleaseStaticIp",
"lightsail:SetIpAddressType",
"lightsail:CreateInstances",
"lightsail:GetInstance",
"lightsail:GetInstanceAccessDetails",
"lightsail:DeleteInstance",
"lightsail:CreateKeyPair",
"lightsail:ImportKeyPair",
"lightsail:StartInstance",
"lightsail:DownloadDefaultKeyPair",
"lightsail:GetInstancePortStates",
"lightsail:StopInstance",
"lightsail:AttachStaticIp",
"lightsail:GetRegions",
"lightsail:RebootInstance",
"lightsail:GetOperation",
"lightsail:DetachStaticIp",
"lightsail:GetInstanceState",
"lightsail:GetBundles",
"lightsail:TagResource",
"lightsail:PutInstancePublicPorts"
\],
"Resource": "\*"
}
\]
}
Once the policy is created for Lightsail instance, give the policy a name and hit on the **‘Create Policy’** button.
### Step 10: Create & Retrieve a User Access Key [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
Now we have to create a user access key. Find **‘Create access key’** under the Summary tab and click on it. Then you will be redirected to the **Access Key best practices & Alternatives page,** from here select the ‘**Other’** option and click on Next.
Now give a Description Tag to proceed to create an access key. Once the access key is created copy the Access Key and Secret from from here and go back to your xCloud Dashboard to integrate the server with xCloud.
### **Step 11: Connect the Account & Add Necessary Information** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
From the AWS dashboard, select an existing or connect new account from the dropdown menu. Then choose the AWS services from, you can use any one with the proper credentials or both from the xCloud dashboard.
_Note: EBS-supported instances of AWS are not supported. For example, T3 instances use EBS storage. These instances are not available through the API. However, you can set up such instances manually in your AWS account first and then add them through the **Any Provider** method in xCloud._
As you have the Access Key and Secret Key Paste them into the designated blank boxes one by one carefully. Now click on **‘Verify’** button, it will start verifying the credential and connect you with the AWS server.
Fill all the information like **‘Server Name’, ‘Server Region’, ‘Server Zone’,’Server Size’,** etc according to your preference.
Next, choose the web server stack from **NGINX** or **OLS** as your requirements and click on **‘NEXT’** button to proceed with the server creation process.
It will start creating a AWS server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many site as you want under this server
This is how easily you can create an AWS server from xCloud seamlessly without going through any difficulties.
## **How to Deploy Lovable Applications with xCloud?** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
xCloud allows you to deploy Lovable applications easily from your Git repositories. You can install and set up Lovable and get your application live in just a few clicks. Follow the steps below to set up Lovable with xCloud and deploy **AI powered projects easily on AWS Server:**
### **Step 1: Create a New Site** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
### **Step 2: Choose Your Server** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Lovable applications.
### **Step 3: Go to the Lovable Tab** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
From here, go to the **‘Lovable’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
Before you proceed, make sure your Lovable projects are properly synced with Git repositories.
### **Step 4: Set Up Domains** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the **‘Migrate into a New Domain’** option.
### **Step 5: Configure Site Settings** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
Next, under the **‘Settings’** tab, you will get the **‘Node.js Version’** and **‘Site User’** for this application. After that, click on the **‘Next’** button.
### **Step 6: Insert Git Repository Credentials** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
In the **‘Git Repo’** tab, you will get three repository options: **‘Private Repository (Manual SSH URL)’**, **‘Public Repository (Manual HTTPS URL)’** and ‘**Connected Git Provider’**.
We are going to deploy Git projects using the **‘Git Provider’** option here. Choose the **‘Connected Git Provider’** option from the dropdown menu.
From the **‘Select Git Provider’** dropdown, choose the connected account you want to use. Once selected, navigate through the list of repositories, pick the one you want to deploy and then select the specific **‘Branch’** of that project.
You can also deploy Lovable projects from your Public or Private Git repositories as well. For more details read this documentation:
**👉** [**How to Insert Your Git Repositories with xCloud**](/docs/how-to-integrate-a-git-provider-with-xcloud/)
### **Step 7: Enable Push to Deploy** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
The next step is to enable automated deployment. Toggle on the **‘Enable push to deploy’** option. You need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
**Note:** If you want to learn more about the process, follow the steps in this [**document**](/docs/deploy-custom-php-applications-with-xcloud/)**.**
Finally, review all the details and click on the **‘Start’** button to create the Lovable application.
### **Step 8: Visit the Application** [#](/docs/how-to-set-up-lovable-on-aws-with-xcloud/)
After completing the setup, you will be able to visit your Lovable site. From the dashboard, click on the **‘Visit Site’** app.
That’s it! This is how easily you can deploy Lovable with xCloud and launch your web apps in just a few clicks.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up Lovable on Linode with xCloud? - xCloud
> Learn how to set up Lovable on Linode with xCloud. Deploy AI powered apps easily, manage servers, and streamline application development.
[**Lovable**](/lovable-hosting/) is a modern AI-powered application-building platform designed to help anyone create user-friendly, scalable, and production-ready applications and websites through chatting.
Set up **Lovable** on Linode with xCloud quickly and easily. This guide walks you through the basic steps to configure and launch Lovable on a Linode server, helping you streamline deployment and manage your application with minimal effort.
## **How to Set up Linode Server with xCloud?** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
This guide shows how to set up the Linode server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Create Your Linode Server in xCloud** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a Linode server and for that select the [**Linode**](https://www.linode.com/) option.
### **Step 2: Authorize Your Linode Account** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
We have made it easier and safer for you to connect xCloud with your Linode account. Now provision a new Linode server, click **‘Authorize on Linode’** during the setup, and you will be redirected to Linode to grant permission to your account. It is a straightforward and hassle-free process to set up your server with Linode.
### **Step 3: Connect the Account & Add the Necessary Information** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
You will be taken to the server creation page after successfully integrating your Linode account and your server will be connected with xCloud. Now you need to provide the **‘Server name’**, your preferred **‘Server Size’** (CPU, RAM, storage), the **‘Region’** nearest to you and your visitors, and then select the **‘Database Server’** from MySQL and MariaDB.
**_Note:_** _We recommend at least a 2GB/ 1 shared CPU server for 10-20 brochure sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server._
Next, choose the web server stack from **‘NGINX’** or **‘OpenLiteSeed’** as your requirements and click on the **‘Next’** button to proceed with the server creation process.
It will start creating a Linode server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many sites as you want under this server.
## **How to Deploy Lovable Applications with xCloud?** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
xCloud allows you to deploy Lovable applications easily from your Git repositories. You can install and set up Lovable and get your application live in just a few clicks.
Follow the steps below to set up Lovable with xCloud and deploy AI-powered projects easily:
### **Step 1: Create a New Site** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
### **Step 2: Choose Your Server** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Lovable applications.
### **Step 3: Go to The Lovable Tab** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
From here, go to the **‘Lovable’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
📝 Before you proceed, make sure your Lovable projects are properly synced with Git repositories.
### **Step 4: Set Up Domains** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
From the ‘Domains’ tab, you will get two options: either you can create a ‘Demo Site’ with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the ‘Migrate into a New Domain’ option.
### **Step 5: Configure Site Settings** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
Next, under the **‘Settings’** tab, you will get the **‘[Node.js](http://node.js/) Version’** and ‘**Site User’** for this application. After that, click on the **‘Next’** button.
### **Step 6: Insert Git Repository Credentials** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
In the ‘**Git Repo’** tab, you will get three repository options: **‘Private Repository (Manual SSH URL)’, ‘Public Repository (Manual HTTPS URL)’,** and **‘Connected Git Provider’.**
We are going to deploy Git projects using the **‘Git Provider’** option here. Choose the **‘Connected Git Provider’** option from the dropdown menu.
From the **‘Select Git Provider’** dropdown, choose the connected account you want to use. Once selected, navigate through the list of repositories, pick the one you want to deploy, and then select the specific **‘Branch’** of that project.
You can also deploy Lovable projects from your Public or Private Git repositories as well. For more details read this documentation:
_**👉 [How to Insert Your Git Repositories with xCloud](/docs/how-to-integrate-a-git-provider-with-xcloud/)**_
### **Step 7: Enable Push to Deploy** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
The next step is to enable automated deployment. Toggle on the ‘Enable push to deploy’ option. You need to insert this URL into GitHub. Copy the ‘Deployment URL’ from here.
_**Note: If you want to learn more about the process, follow the steps in this [document](/docs/deploy-custom-php-applications-with-xcloud/).**_
Finally, review all the details and click on the **‘Start’** button to create the Lovable application.
### **Step 8: Visit the Application** [#](/docs/how-to-set-up-lovable-on-linode-with-xcloud/)
After completing the setup, you will be able to visit your Lovable site. From the dashboard, click on the **‘Visit Site’** app.
That’s it! This is how easily you can deploy Lovable on Linode with xCloud and launch your web apps in just a few clicks.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up n8n on AWS with xCloud? - xCloud
> Learn how to set up n8n on AWS with xCloud. Deploy workflows easily, streamline automation, and manage servers with minimal effort
[**n8n**](/n8n-hosting/) is an open-source workflow automation platform that allows users to connect different services and build complex workflows with minimal effort. With support for hundreds of integrations and a visual interface, n8n is ideal for teams looking to increase productivity without writing extensive custom code.
Set up **n8n** on AWS with xCloud is a straightforward way to bring automation to the cloud. This guide walks you through the essential steps to configure, deploy, and run n8n seamlessly on AWS, so you can start building powerful workflows without the usual complexity.
You can easily set up an AWS server in [**xCloud**](/) for both EC2 and Lightsail instances. Now let us follow these steps to get you started.
### **Step 1: Sign Up/Login With xCloud** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
To [**create the AWS server**](https://app.xcloud.host/) in xCloud, the first step is to visit the xCloud website and create your account or log in using your existing credentials. Once you are signed, you can effortlessly set up your AWS server.
If you already have an account please [**visit our app URL**](https://app.xcloud.host/) to log in to your account to set up an AWS server in xCloud Host.
### **Step 2: Create Your AWS Server In xCloud** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **‘Add New Server’** button from your dashboard.
The next screen will provide the list of our available server providers. Select the AWS option from the list. The billing of the server will be handled on your AWS account.
### **Step 3: Sign In to the AWS Management Console** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
Now, before going to the next step, you need to log in to the AWS management console. Sign in as a **‘Root User’** to the [**AWS Management Console**](https://aws.amazon.com/console/) using your AWS account credentials. Once logged in, navigate to the main dashboard where you can access various AWS services.
### **Step 4: Navigate to the IAM Console** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
From the AWS Management Console, click on the Services menu located at the top left corner or search with **“IAM”** and select **IAM** from the list of services. This will direct you to the IAM dashboard, where you can manage users, groups, roles, and policies.
### **Step 5: Add a New User** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
On the IAM dashboard, locate and click on the Users option in the left navigation panel. This will display a list of existing IAM users. To create a new user, click on the **‘Create User’** button.
### **Step 6: Configure User Details** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
In this step, enter a unique ‘**Username’** for the new IAM user. Next, choose the type of access the user requires. Check-in **‘AWS Management Console’** access option if the user requires access to the AWS Management Console and click on the ‘**Next**’ button.
### **Step 7: Set Permissions for Amazon EC2 Instance** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
You have three options to set permissions for the new user. The first one is ‘**Add user to group’** which lets you add the user to an IAM group with predefined permissions, which is efficient for managing multiple users with similar access needs. The second one is ‘**Copy permissions’** which enables you to duplicate the permissions of another IAM user. And the final policy ‘**Attach policies directly’** allows you to assign AWS-managed policies or custom policies.
Here we are choosing the **‘Attach policies directly’** and assigning the access for [**Amazon EC2 Instance**](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to the user and hit on the **Next**.
**_Note:_** _If you do not find the EC2 Access here, search for the policy in the search bar._
### **Step 8: Add Tags, Review and Create** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
You can add ‘**Tags’** to help organize and manage users. Now carefully review all the details and permissions assigned to the new IAM user. If everything is accurate and complete, click the ‘**Create user**’ button to finalize the creation of the IAM user.
### **Step 9: Give Another permission for Amazon Lightsail** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
Now, set another permission for the new user for [**Amazon LightSail**](https://docs.aws.amazon.com/decision-guides/latest/lightsail-or-ec2/lightsail-or-ec2.html) easily. To specify the permissions for the created user, go to the Permission Policies and click on the **‘Add Permissions Menu’**. Choose the **‘Create Inline Policy’** option from the dropdown menu.
Click on the ‘**JSON’** button from the **Policy Editor** and paste the below given JSON code in the editor. Finally, tap on the **‘Next’** button.
Here is the **JSON** code:
📋
JSON
{
"Version": "2012-10-17",
"Statement": \[
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": \[
"lightsail:GetInstances",
"lightsail:GetKeyPair",
"lightsail:DeleteKeyPair",
"lightsail:GetStaticIp",
"lightsail:ReleaseStaticIp",
"lightsail:SetIpAddressType",
"lightsail:CreateInstances",
"lightsail:GetInstance",
"lightsail:GetInstanceAccessDetails",
"lightsail:DeleteInstance",
"lightsail:CreateKeyPair",
"lightsail:ImportKeyPair",
"lightsail:StartInstance",
"lightsail:DownloadDefaultKeyPair",
"lightsail:GetInstancePortStates",
"lightsail:StopInstance",
"lightsail:AttachStaticIp",
"lightsail:GetRegions",
"lightsail:RebootInstance",
"lightsail:GetOperation",
"lightsail:DetachStaticIp",
"lightsail:GetInstanceState",
"lightsail:GetBundles",
"lightsail:TagResource",
"lightsail:PutInstancePublicPorts"
\],
"Resource": "\*"
}
\]
}
Once the policy is created for Lightsail instance, give the policy a name and hit on the **‘Create Policy’** button.
### **Step 10: Create & Retrieve a User Access Key** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
Now we have to create a user access key. Find **‘Create access key’** under the Summary tab and click on it. Then you will be redirected to the **Access Key best practices & Alternatives page,** from here select the ‘**Other’** option and click on Next.
Now give a Description Tag to proceed to create an access key. Once the access key is created copy the Access Key and Secret from from here and go back to your xCloud Dashboard to integrate the server with xCloud.
### **Step 11: Connect the Account & Add Necessary Information** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
From the AWS dashboard, select an existing or connect new account from the dropdown menu. Then choose the AWS services from, you can use any one with the proper credentials or both from the xCloud dashboard.
_Note: EBS-supported instances of AWS are not supported. For example, T3 instances use EBS storage. These instances are not available through the API. However, you can set up such instances manually in your AWS account first and then add them through the **Any Provider** method in xCloud._
As you have the Access Key and Secret Key Paste them into the designated blank boxes one by one carefully. Now click on **‘Verify’** button, it will start verifying the credential and connect you with the AWS server.
Fill all the information like **‘Server Name’, ‘Server Region’, ‘Server Zone’,’Server Size’,** etc according to your preference.
Next, choose the web server stack from **NGINX** or **OLS** as your requirements and click on **‘NEXT’** button to proceed with the server creation process.
It will start creating a AWS server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many site as you want under this server
This is how easily you can create an AWS server from xCloud seamlessly without going through any difficulties.
## **How to Deploy n8n with xCloud with One Click Apps** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
With **xCloud’s One Click Apps** feature, you can deploy n8n with ease. Follow the steps below to quickly set up n8n in a demo or production environment with xCloud.
### **🔖Recommendations** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
### **📌Web Server for Deployment** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
Though you can deploy n8n application from both NGINX and OLS server, but we recommend deploying n8n on an **Nginx** server for the best performance and stability. While, you can use an **OLS** server, Nginx generally provides a more reliable experience.
### **📌CPU Requirements** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
We recommend using a server with more than **1 CPU** when running n8n. A 1 CPU server may not function as expected, so choosing a server with higher resources will help ensure smooth and successful operation.
_**Note**: n8n is available in our plans, including the free plan. But you have to upgrade to our PRO plans to access the Environment feature._
### **Step 1: Access the One Click Apps Dashboard** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
This will take you to the site creation interface. From here, choose the **‘Server’,** then go to the **‘One Click Apps’** section. Select **‘n8n’** from the available applications to initiate the deployment process.
This will take you to the site creation interface. From here, go to the **‘One Click Apps’** section. Select **“n8n”** from the available applications to initiate the deployment process.
Ensure your server is already connected to xCloud. If not, follow the instructions on the dashboard to establish a server connection. Once connected, you can create a new site either from the main dashboard or the site list by selecting the **‘Create New Site**‘ option.
### **Step 2: Set Up the n8n Application** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘**Site Title’** and add relevant ‘**Tags’** to help organize your deployment. At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
### **Step 3: Configure Domain Settings** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
If you select the ‘**Demo Site’** option, xCloud will assign a temporary subdomain for your n8n application.
**_Note:_** _Note that once a demo site is promoted to a live environment, you cannot revert back to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding._
### **Step 4: Configure and Install the Site** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
Then, a default **‘Port’, ‘Site User’** will be selected automatically. Then choose a ‘Timezone’ for this site. Once all settings have been configured, click the **‘Next’** button to proceed.
_**Note:** We recommend leaving the port and site user as default._
### **Step 6: Add Your Custom Domain** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
You can add your own **‘Domain’** to host the site by going to the Domain section. Also, you can add an **‘Additional Domain’** with your custom domain.
### **Step 7: Visit the n8n Site** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
With n8n set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** app.
This will open the n8n dialog window for registration, which should look something like the example below. Simply enter your details and create a password according to the specs indicated. Hit the Next button, then click through any additional popups, leaving them empty for now.
This should bring you to the n8n Overview page. Now that your n8n instance is up and running, let’s fine-tune its settings for security and customization. From here, go to the ‘**Create workflow**’ , set according to your preferences.
### **Environment Editor for n8n** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your n8n instance. Just go to the **‘Environment’** option from the sidebar and adjust as you needed then click on the **‘Save’** button.
### **Update N8N Version** [#](/docs/how-to-set-up-n8n-on-aws-with-xcloud/)
To update n8n to the latest version, simply go to **‘Updates’** from the sidebar of the dashboard. Then simply search for the **‘Check for Updates’** button. Click the Update button, and this will install the latest N8N version on your server.
And that’s it, this is how easily you can quickly and efficiently deploy an n8n instance on AWS using xCloud’s One Click Apps feature. You can create your own n8n application and automate with workflows seamlessly.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up Nextcloud with One Click - xCloud
> Discover how to set up Nextcloud easily using xCloud’s one-click setup to manage your files, collaborate, and protect your data seamlessly.
Nextcloud is a powerful open-source platform that enables you to host and manage your own private cloud for file storage, collaboration, and sharing — ensuring full control over your data.
Follow these steps to create a server, configure your deployment environment, and set up the Nextcloud application quickly and efficiently.
> _Note: To use the Nextcloud app, you need to set up a server with a ‘**Docker + Nginx’ serve**r._
## **Step 1: Create a Docker+ NGINX Server** [#](/docs/how-to-set-up-nextcloud-with-one-click/)
First, you need to create a Docker server to deploy Nextcloud. Click the **‘Add New Server’** button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Nextcloud either on your own server or on an xCloud server.
Next, choose your server provider to deploy Nextcloud with xCloud. You can either use an xCloud Managed Server or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the **‘Server Name’**, set the **‘App Type’** to Nextcloud, and add any relevant **‘Tags’** to help identify your server later.
Next, choose between the **‘General’** and **‘Premium’** options based on your requirements. Then, select a plan that best fits your needs.
Next, choose the **‘Region’** and **‘Ubuntu** Version for your server. You can also enable or disable the Backup option as needed.
Next, you can see the ‘**Docker + NGINX**’ stack is already selected, which is mandatory for deploying the Nextcloud application. Then click on the ‘**Create**’ button to proceed.
Once the server is created, you will be able to deploy your Nextcloud Application in this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## How to Install NexCloud on a Cloud Server [#](/docs/how-to-set-up-nextcloud-with-one-click/)
Learn how to install Nextcloud on a cloud server. It walks you through creating a server, configuring the environment, and launching your Ollama application easily.
### **Step 2: Access the One Click Apps Dashboard** [#](/docs/how-to-set-up-nextcloud-with-one-click/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the ‘**New Site**’ button.
Then choose your server from the dropdown menu. Next, click on the ‘Next’ button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One-Click Apps section. You will see **‘NextCloud’**, click on it to proceed with the deployment of this application.
### Step 3: Set Up the Nextcloud Application [#](/docs/how-to-set-up-nextcloud-with-one-click/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘Site Title’ and add relevant ‘Tags’ to help organize your deployment.
At this point, you can choose between two deployment modes: ‘Go Live’ for a production-ready deployment or ‘Demo Site’ for testing purposes. Selecting ‘Go Live’ will immediately create a live environment, while choosing ‘Demo Site’ allows you to experiment in a staging environment before promoting it to production.
### Step 4: Configure Domain Settings [#](/docs/how-to-set-up-nextcloud-with-one-click/)
If you select the ‘Demo Site’ option, xCloud will assign a temporary subdomain for your NextCloud application. Next, enter your application’s domain.
You can adjust the **‘Site User, ‘Admin Username’, ‘Admin Password’, ‘Admin Email Address’** of your application according to your preferences, or leave it as the default.
Next enter the **‘Database Name’, ‘Database Username’** and **‘Database Password’** for this application and click on the **‘Next’** button
## Step 4: Visit the Application [#](/docs/how-to-set-up-nextcloud-with-one-click/)
After completing the setup, you will be able to visit your Nextcloud site. From the dashboard, click on the ‘Visit Site’ app.
### Environment Editor for NextCloud [#](/docs/how-to-set-up-nextcloud-with-one-click/)
The Environment section in xCloud allows you to customize configuration settings for your NextCloud instance. Just go to the ‘Environment’ option from the sidebar and adjust as you need, then click on the ‘Update Environment’ button.
With xCloud’s one-click setup, installing Nextcloud is quick and simple. You can create your server, set up your app, and get your private cloud running in just a few steps. Once everything is ready, you can start using Nextcloud to store files, share them, and collaborate securely.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How to Easily Set up pCloud Storage in xCloud? - xCloud
> Learn how to set up pCloud storage in xCloud for secure and automated website backups. Follow simple steps to protect your site data.
Ensuring the safety and reliability of your website data is crucial, and integrating [**pCloud**](https://www.pcloud.com/) storage for site backup is a smart way to achieve it. pCloud is a trusted cloud storage platform, offering a user-friendly interface, robust security, and scalable storage solutions. These features make it an ideal choice for protecting your site backups and ensuring easy accessibility whenever needed.
In this tutorial, we will show you how to seamlessly set up pCloud storage in xCloud for site backup with [**xCloud**](/), enabling a smooth and efficient backup process. Ready to secure your data with pCloud? Let us dive into the step-by-step instructions!
_Note: pCloud integration is now working for the both EU and US regions. In general, region selection is handled automatically by pCloud ([check out their official documentation](https://docs.pcloud.com/))._
## **Steps to Integrate pCloud Storage for Site Backups with xCloud** [#](/docs/how-to-set-up-pcloud-storage-in-xcloud/)
Follow the steps below to integrate pCloud for site backups with xCloud and back up your websites effortlessly.
### **Step 1: Integrate pCloud into Your Account** [#](/docs/how-to-set-up-pcloud-storage-in-xcloud/)
Before getting started to back up your websites with pCloud, you need to integrate the storage provider into xCloud. For that,[**log in to your xCloud account**](https://app.xcloud.host/) and navigate to **‘Team Settings’.**
Then go to the **‘Integrations’ → ‘Storage Provider’** and click on the **‘Add New Provider’** button and choose pCloud as your provider.
Next, select pCloud and enter a label of your choice. Then click on **‘Link pCloud Account’**. You’ll be redirected to the pCloud sign-in page, where you can choose an account or create a new one to continue.
Once integrated, you will see the pCloud integrated and listed on the Storage Provider page in xCloud, as shown below.
### **Step 2: Configure Backup Settings for pCloud** [#](/docs/how-to-set-up-pcloud-storage-in-xcloud/)
Once you are done integrating pCloud as a storage provider into xCloud, you can now configure **‘Backup Settings’** for taking backups with pCloud. Now, go to sites, choose the one you want to take backups and navigate to the ‘**Site Backup’ → ‘Backup Settings**’.
Now, in the **‘Remote Backup’** section, choose Backup Type as **‘Full’ or ‘Incremental’** and select the **‘Bucket’** you have just created for pCloud. You can then choose to exclude paths if necessary (for the paths you do not want to take a backup).
Then, you can also enable **‘Automatic Backup’** and choose the backup frequency. Plus, you have the option to use the **‘Automatic Delete’** option, with which you can set days after which your backup will be deleted automatically. Once done, hit the **‘Save’** button.
### **Step 3: Take a Backup of Your Site** [#](/docs/how-to-set-up-pcloud-storage-in-xcloud/)
Once you are done configuring the site backups, you can now take backups of your websites using this provider. Now, go to the **‘Previous Backups’** of your site settings and you will see all the available remote backups and local backups. You can take a backup of your site from here by simply clicking on the **‘Backup Now’** button. Your backup process will be initiated and the backup files will be shown here once done.
You can also check your pCloud. A folder will be created with the name of your backup label, and your backups will be saved inside the folder.
And that’s it. This is how easily you can integrate pCloud for Site Backup with xCloud and take backups of your websites.
Still stuck? Contact our **[support team](/support/)** for any of your queries.
---
# How to Set Up PHP on Linode with xCloud? - xCloud
> Learn how to set up PHP on Linode with xCloud, create servers, deploy custom PHP applications, manage databases, and launch your site with ease
Setting up **[PHP](/php-hosting/)** on Linode with xCloud is simpler than you think. This guide walks you through the essential steps to configure your server and get PHP running smoothly, so you can deploy applications with confidence
xCloud makes hosting and managing PHP sites easy, so you can focus on building great websites. This guide will show you how to set up PHP on Linode using xCloud.
## **How to Integrate and Set Up a Linode Server with xCloud?** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
This guide shows how to set up the Linode server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Create Your Linode Server in xCloud** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a Linode server and select the [**Linode**](https://www.linode.com/) option.
### **Step 2: Authorize Your Linode Account** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
We have made it easier and safer for you to connect xCloud with your Linode account. Now, provision a new Linode server, click **‘Authorize on Linode’** during the setup, and you will be redirected to Linode to grant permission to your account. It is a straightforward and hassle-free process to set up your server with Linode.
### **Step 3: Connect the Account & Add the Necessary Information** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
You will be taken to the server creation page after successfully integrating your Linode account and your server will be connected with xCloud. Now you need to provide the **‘Server name’**, your preferred **‘Server Size’** (CPU, RAM, storage), the **‘Region’** nearest to you and your visitors, and then select the **‘Database Server’** from MySQL and MariaDB.
**_Note:_** _We recommend at least a 2GB / 1 shared CPU server for 10-20 brochure sites with cache enabled. And for a site whose pages cannot be cached (e.g., a WooCommerce site), we recommend a 4 GB / 2 dedicated CPU server._
Next, choose the web server stack from **‘NGINX’** or **‘OpenLiteSeed’** according to your requirements and click on the **‘Next’** button to proceed with the server creation process.
It will start creating a Linode server with xCloud within a while and if you go to the **‘Servers’** from the menu, you can see your created server and create as many sites as you want under this server.
## **How to Set Up PHP on Linode with xCloud** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
Creating a website using custom [**PHP applications**](/php-hosting/) on xCloud can be a powerful way to build a tailored online presence. Unlike traditional WordPress-based sites, xCloud allows you to go beyond WordPress and develop fully customized PHP applications to meet your unique requirements.
Follow the guide to deploy your Node.js application easily on Linode with xCloud:
### **Step 1: Choose the Application** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
To begin deployment, click on the **‘Add New Site’** button from the dashboard.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **Linode server** you set up in xCloud from this dropdown.
Next, you will see options such as ‘**WordPress**’ and **‘Custom PHP’**. Go to the ‘**Node.js**’ option from the tab.
Then choose your preferred way from the **‘Clone a Git Repository’** and **‘Manually Upload a Website’** options.
## **How to Install Custom PHP Applications from Your Git Repository** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
Migrating a website from a Git repository with xCloud involves several easy steps. The guide below can help you understand how you can perform this migration. Follow the steps below to migrate a custom PHP site from a Git Repository.
### **Step 1: Select Option To Clone A Git Repository Option** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
First, click on **‘New Site’** from the xCloud dashboard. Click on the **‘Custom PHP’** field. Now, choose ‘**Clone A Git Repository**’ to import your custom PHP site.
### **Step 2: Select Destination Server** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
From the **‘Destination’** tab, select the destination server to migrate your site. You can keep the server that is already selected or you can change it from the dropdown. Then, click on **‘Next**’.
### **Step 3: Set Up Domains** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
From the **‘Domains’** tab, you will get two options, either you can create your site in a staging domain and refine it until it is ready for launch or, you can migrate into a new domain to get your site up and running in a new domain. To create a site with your live domain, you need to select the **‘Migrate into a New Domain’** option. Then you have to put **‘New Site Title’** and **‘Domain Name’**.
Here, you need to enable HTTPS to make your website more secure. From the DNS Setup section, toggle on the **‘Do You Want To Enable HTTPS?’** option.
After enabling it, you will get two options to select. Either choose to use a free SSL certificate issued & managed by xCloud or you can provide the certificate and manage it yourself. Select according to your choice.
Instead of migrating into a new domain, you can select the **‘Demo Site’** option. xCloud offers a temporary staging domain to make your site live, which helps promptly showcase your site’s progress and collect feedback from teammates or clients. Subsequently, you can integrate your custom domain to make the site accessible to your users or visitors. Now, click on **‘Next’**.
### **Step 4: Settings To Manage Database** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
In the **‘Settings’** tab, you will see the **‘PHP Version’** and **‘Site Users’**. You can change these according to your choice.
Now, it is time for database management. You will get two options. Either you can create a new database on the server, or you can add your existing database that is hosted on another server. If you select this option, you need to get a **‘Database Name’**, **‘Database Username’** and **‘Database Password’**. You can keep these auto-generated credentials or you can modify them according to your choice.
If you select this option, you need to put in a few information and credentials such as **‘Database Host’**, **‘Database Port’**, **‘Database User’**, **‘Database Name’** and **‘Database Password’**. Please make sure that the database connection configuration is correct.
After selecting any one option and providing all essential information and credentials, click on **‘Next’.**
**_Note:_** _For this documentation, we are going with the_ **_‘Create Database In Server’_**_option._
### **Step 5: Insert Git Repository Credentials** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
In the **‘Git Repo’** Tab, add your **‘Git Repository’** and **‘Git Branch’**. Also, toggle on the **‘Enable push to deploy’** option. Once you enable the **‘Push To Deploy’**, it will generate a **‘Deployment URL’**. We need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
### **Step 6: Add Deployment URL In Git Repository** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
Now, go to your Git Repository. From the **‘Code’** tab, go to the **‘Settings’** tab and click on **‘Webhooks’** page from the **‘Code and automation’** section of the left navigation. Insert the Deployment URL into the **‘Payload URL’** field. Select the **‘Application/json’** from the **‘Content type’** dropdown.
### **Step 7: Add Public Key to Git Repository** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
From the xCloud dashboard, copy the **‘Public Key’** to add it to your Git repository as a deploy key. Git migration uses the **‘Public Key’** for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the **‘Code’** tab, go to the **‘Settings’** tab and click on **‘Deploy Keys’** in the security section of the left navigation. Click on the **‘Add Deploy Key’** button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on **‘Next’** on your xCloud settings of the **‘Git Repo’** tab.
### **Step 8: Confirm Migrating The Website** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
Now, to start the migration process, click on the **‘Start’** button. After clicking on the **‘Start’** button, the migration process will start. And you will see the progress of the migration.
**Note:** The Git Repository must contain a wp-config-sample.php. xCloud generates a wp-config.php file from the wp-config-sample.php file with the database information.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
## **How To Manually Upload a PHP Site on xCloud** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
If you’re migrating an existing PHP site or starting from scratch, xCloud makes it easy to upload and configure your website. Follow the steps below to successfully upload your site, set up your database, and get your site live on a custom domain or a staging environment.
### **Step 1: Create A New Site** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
First, click on **‘New Site’** from the xCloud dashboard. Click on the **‘Custom PHP’** field. Now, you choose **‘Manually Upload Website’** to import your custom PHP site.
### **Step 2: Add Information To Manually Upload Website** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
Now, select the destination server to migrate your site. Afterward, click on the **‘Next’** button.
In the next step, you need to add your source site URL. And if you choose to migrate to a new domain, you can include your custom domain. xCloud offers a staging environment and with it, you can upload your site and visit it live with a temporary domain. After successfully uploading your site, you may update the site with your custom domain later.
In this tutorial, we will be working on a staging site. Select **‘Demo Site’** and then click on the **‘Next’** button.
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your **‘PHP Version’**, **‘Site Users’**, **‘Web root’** and other details before clicking the **‘Next’** button.
**Note:** The directory where your website’s main files, including **index.php**, are stored. The Web root defines the base folder from which your website is served, and it must be set correctly to ensure proper functionality.
Additionally, ensure that your index.php file is correctly placed for the system to function automatically. The index.php file should be located in the root directory. However, if it is placed in a subdirectory, you must update the Web Root Settings accordingly.
Users may upload their entire website directory instead of just the necessary files. For example, if the website files are inside a folder named public\_html, then the root directory does not contain index.php directly.
To resolve this, you need to update the Web root settings. For this, navigate to Web Root Settings from the **‘Site Settings’**. Then enter the name of the folder that contains the index.php file (e.g., public\_html) and click on the **‘Update’**.
Once updated, our system will correctly detect and load the index.php file from the specified folder.
### **Step 3: Upload The Exported Zip File & SQL File** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
You will now be directed to the **‘Settings’** step. Just upload your exported custom PHP file as shown and click on the **‘Next’** button.
Now, from the **‘Files’** step, upload your SQL file similarly. Afterward, click on the **‘Next’** button.
### **Step 4: Complete Database Settings & Finalize** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
In the **‘Database’** tab, you can configure your preferred database setup. If you are good to go for uploading an existing custom PHP website with xCloud, click on the **‘Start’** button.
Within a few moments, your PHP website will be automatically uploaded to xCloud. You will see the following screen while uploading.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
## **Final Outcome** [#](/docs/how-to-set-up-php-on-linode-with-xcloud/)
After the migration is completed, if you visit the site, you can see the newly custom PHP site that you have uploaded with xCloud.
This is how easily you can create a site with custom PHP applications in xCloud. With just a few simple steps, you can quickly deploy your site, configure your database, and select your preferred domain settings. If you’re using a Git repository or uploading files directly, xCloud provides easy ways to get your website live and running smoothly.
Still feeling stuck? Contact our [**dedicated support team**](/support/) for further assistance.
---
# How to Set Up PHP on Vultr with xCloud - xCloud
> Learn how to set up PHP on Vultr with xCloud and deploy custom PHP applications using Git or manual upload in just a few simple steps.
Building a custom online presence often requires more flexibility than a standard CMS can provide. xCloud allows you to go beyond the limitations of WordPress, giving you the freedom to develop and host fully customized [**PHP applications**](/php-hosting/) tailored to your specific needs.
In this guide, we will show you how to **set up PHP on Vultr** using xCloud’s streamlined dashboard. Whether you are deploying code directly from a Git repository or manually uploading your files, xCloud makes the process seamless. Follow these simple steps to configure your server and get your custom PHP project live in minutes.
First, set up your Vultr server in xCloud. Follow these steps to get started.
## **How to Set Up a Vultr Server in xCloud?** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
This guide shows how to set up a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Create Your New Vultr Server in xCloud** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available services. For this tutorial, we will create a Vultr server and for that select the Vultr option under **“Bring your own server service”.** The billing of the server will be handled on your Vultr account, and in xCloud, we won’t charge for this first server.
### **Sign Up in Vultr with xCloud Promo** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Sign up at [**Vultr.com**](http://vultr.com), verify with a credit card ($2.50 hold) or PayPal ($5 minimum), and get $100 free credit. Use promo code **“XCLOUD25”** during signup.
_**Note:** If you already have a Vultr account, then please skip this step and check how to collect the API from Vultr._
### **Collect the API key from Vultr** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
After you have successfully completed setting up your billing method, you will need to get the Vultr API key to add it to xCloud to create and manage 1 server and 10 sites for free. Navigate to the Account → API tab from your Vultr dashboard. After that, click on the **‘Enable API’** button.
Now, your **‘Personal Access Token’** will be auto-generated. Copy the API Key/Token.
Please make sure you have added Any **IPv4** and Any **IPv6** both under Access Control.
Now, you need to go back to the xCloud dashboard and add your Vultr Label & API Key.
### **Add Team Members In Vultr** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
If you want your team members to use xCloud with Vultr, then make sure these permissions are given.
### **Add Vultr API key in xCloud** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Thanks to xCloud, you can create your first server without spending any money. Now, click on **‘Add New Server’** from the xCloud dashboard and you will be redirected to the server selection screen. Then click on **‘Vultr’** to proceed further.
After selecting **‘Vultr’**, set your **‘Key’**, **‘Vultr Label’**, and ‘**Vultr API Key’**. Then click on **‘Verify’**.
### **Step 3: Create a Vultr Server in xCloud** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Now that you have successfully verified your Vultr account, you will need to add other details to create a server in Vultr using xCloud. Choose your Region, Database Server, Server Size, and much more from one easy dashboard.
After putting all the information, click on **‘Next’** and xCloud will automatically install and set up everything for you in a few minutes.
## **How to Set Up PHP on Vultr with xCloud** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Creating a website using custom **[PHP applications](/php-hosting/)** on xCloud can be a powerful way to build a tailored online presence. Unlike traditional WordPress-based sites, xCloud allows you to go beyond WordPress and develop fully customized PHP applications to meet your unique requirements.
xCloud provides an intuitive interface that allows you to easily deploy, manage and scale your [**Node.js**](/node-js-hosting/) applications directly from your Git repository without worrying about manual setup or infrastructure maintenance.
Follow the guide to deploy your Node.js application easily on Vultr with xCloud:
### **Step 1: Choose the Application** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
To begin deployment, click on the **‘Add New Site’** button from the dashboard.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **Vultr server** you set up in xCloud from this dropdown.
Next, you will see options such as ‘WordPress’ and **‘Custom PHP’**. Go to the ‘Node.js’ option from the tab.
Then choose your preferred way from the **‘Clone a Git Repository’** and **‘Manually Upload a Website’** options.
## **How to Install Custom PHP Applications from Your Git Repository** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Migrating a website from a Git repository with xCloud involves several easy steps. The guide below can help you understand how you can perform this migration. Follow the steps below to migrate a custom PHP site from a Git Repository.
### **Step 1: Select Option To Clone A Git Repository Option** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
First, click on **‘New Site’** from the xCloud dashboard. Click on the **‘Custom PHP’** field. Now, choose ‘Clone A Git Repository’ to import your custom PHP site.
### **Step 2: Select Destination Server** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
From the **‘Destination’** tab, select the destination server to migrate your site. You can keep the server that is already selected or you can change it from the dropdown. Then, click on **‘Next**’.
### **Step 3: Set Up Domains** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
From the **‘Domains’** tab, you will get two options, either you can create your site in a staging domain and refine it until it is ready for launch or, you can migrate into a new domain to get your site up and running in a new domain. To create a site with your live domain, you need to select the **‘Migrate into a New Domain’** option. Then you have to put **‘New Site Title’** and **‘Domain Name’**.
Here, you need to enable HTTPS to make your website more secure. From the DNS Setup section, toggle on the **‘Do You Want To Enable HTTPS?’** option. After enabling it, you will get two options to select. Either choose to use a free SSL certificate issued & managed by xCloud or you can provide the certificate and manage it yourself. Select according to your choice.
Instead of migrating into a new domain, you can select the **‘Demo Site’** option. xCloud offers a temporary staging domain to make your site live, which helps promptly showcase your site’s progress and collect feedback from teammates or clients. Subsequently, you can integrate your custom domain to make the site accessible to your users or visitors. Now, click on **‘Next’**.
### **Step 4: Settings To Manage Database** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
In the **‘Settings’** tab, you will see the **‘PHP Version’** and **‘Site Users’**. You can change these according to your choice.
Now, it is time for database management. You will get two options. Either you can create a new database on the server, or, you can add your existing database that is hosted on another server. If you select this option, you need to get a **‘Database Name’**, **‘Database Username’** and **‘Database Password’**. You can keep these auto-generated credentials or you can modify them according to your choice.
If you select this option, you need to put in a few information and credentials such as **‘Database Host’**, **‘Database Port’**, **‘Database User’**, **‘Database Name’** and **‘Database Password’**. Please make sure that the database connection configuration is correct.
After selecting any one option and providing all essential information and credentials, click on **‘Next’.**
**_Note:_** _For this documentation, we are going with the_ **_‘Create Database In Server’_**_option._
### **Step 5: Insert Git Repository Credentials** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
In the **‘Git Repo’** Tab, add your **‘Git Repository’** and **‘Git Branch’**. Also, toggle on the **‘Enable push to deploy’** option. Once you enable the **‘Push To Deploy’**, it will generate a **‘Deployment URL’**. We need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
### **Step 6: Add Deployment URL In Git Repository** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Now, go to your Git Repository. From the **‘Code’** tab, go to the **‘Settings’** tab and click on **‘Webhooks’** page from the **‘Code and automation’** section of the left navigation. Insert the Deployment URL into the **‘Payload URL’** field. Select the **‘Application/JSON’** from the **‘Content type’** dropdown.
### **Step 7: Add Public Key to Git Repository** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
From the xCloud dashboard, copy the **‘Public Key’** to add it to your Git repository as a deploy key. Git migration uses the **‘Public Key’** for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the **‘Code’** tab, go to the **‘Settings’** tab and click on **‘Deploy Keys’** in the security section of the left navigation. Click on the **‘Add Deploy Key’** button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on **‘Next’** on your xCloud settings of the **‘Git Repo’** tab.
### **Step 8: Confirm Migrating The Website** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Now, to start the migration process, click on the **‘Start’** button. After clicking on the **‘Start’** button, the migration process will start. And, you will see the progress of migrating.
**Note:** The Git Repository must contain a wp-config-sample.php. xCloud generates a wp-config.php file from the wp-config-sample.php file with the database information.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
## **How To Manually Upload a PHP Site on xCloud** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
If you’re migrating an existing PHP site or starting from scratch, xCloud makes it easy to upload and configure your website. Follow the steps below to successfully upload your site, set up your database, and get your site live on a custom domain or a staging environment.
### **Step 1: Create A New Site** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
First, click on **‘New Site’** from the xCloud dashboard. Click on the **‘Custom PHP’** field. Now, you choose **‘Manually Upload Website’** to import your custom php site.
### **Step 2: Add Information To Manually Upload Website** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
Now, select the destination server to migrate your site. Afterward, click on the **‘Next’** button.
In the next step, you need to add your source site URL. And if you choose to migrate to a new domain you can include your custom domain. xCloud offers a staging environment and with it, you can upload your site and visit it live with a temporary domain. After successfully uploading your site, you may update the site with your custom domain later.
In this tutorial, we will be working on a staging site. Select **‘Demo Site’** and then click on the **‘Next’** button.
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your **‘PHP Version’**, **‘Site Users’**, **‘Web root’** and other details before clicking the **‘Next’** button.
**Note:** The directory where your website’s main files, including **index.php**, are stored. The Web root defines the base folder from which your website is served, and it must be set correctly to ensure proper functionality.
Additionally, ensure that your index.php file is correctly placed for the system to function automatically. The index.php file should be located in the root directory. However, if it is placed in a subdirectory, you must update the Web Root Settings accordingly.
Users may upload their entire website directory instead of just the necessary files. For example, if the website files are inside a folder named public\_html, then the root directory does not contain index.php directly.
To resolve this, you need to update the Web root settings. For this, navigate to Web Root Settings from the **‘Site Settings’**. Then enter the name of the folder that contains the index.php file (e.g., public\_html) and click on the **‘Update’**.
Once updated, our system will correctly detect and load the index.php file from the specified folder.
### **Step 3: Upload The Exported Zip File & SQL File** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
You will now be directed to the **‘Settings’** step. Just upload your exported custom php file as shown and click on the **‘Next’** button.
Now from the **‘Files’** step, upload your SQL file similarly. Afterward, click on the **‘Next’** button.
### **Step 4: Complete Database Settings & Finalize** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
In the **‘Database’** tab, you can configure your preferred database setup. If you are good to go for uploading an existing custom PHP website with xCloud, click on the **‘Start’** button.
Within a few moments, your PHP website will be uploaded on xCloud automatically. You will see the following screen while uploading.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there.
## **Final Outcome** [#](/docs/how-to-set-up-php-on-vultr-with-xcloud/)
After the migration is completed, if you visit the site, you can see the newly custom PHP site that you have uploaded with xCloud.
This is how easily you can create a site with custom PHP applications in xCloud. With simple steps, you can quickly deploy your site, configure your database, and choose your preferred domain settings. If you’re using a Git repository or uploading files directly, xCloud provides easy ways to get your website live and running smoothly.
Still feeling stuck? Contact our [**dedicated support team**](/support/) for further assistance.
---
# How To Connect Existing Fresh Ubuntu Server On xCloud From Any Provider? - xCloud
> Here we have learned how to connect fresh Ubuntu server in xCloud.
At **[xCloud](/)** you can manage servers from any provider simply from the dashboard. Follow these steps to get started.
## Step 1: Create A Fresh Ubuntu Server On Your Server Provider [#](/docs/how-to-set-up-server-with-other-providers/)
To start, access your provider’s platform to create a VPS or dedicated server. Ensure that you have root user privileges, which can be enabled either through a password or by configuring SSH keys and the server is fresh without anything installed. Do not connect any server that is already setup and has sites.
Before you proceed further add these to your checklist and follow them carefully. Please make sure to follow these requirements for your custom server.
**Server Setup:**
You can now add and connect freshly installed **Ubuntu 24.04 LTS x64** servers from any provider to xCloud. Both **NGINX** and **OpenLiteSpeed (OLS)** stacks are fully supported on Ubuntu 24.04.
Key details:
- **PHP Versions for OLS Stack on Ubuntu 24.04**: PHP 8.1, 8.2, and 8.3 are available.
- PHP 8.3 is available for ARM servers using the OLS/NGINX stack.
### **ARM Servers supported:** [#](/docs/how-to-set-up-server-with-other-providers/)
Now, xCloud provides built-in support for the Hetzner cloud server. Moreover, you can connect any provider that is based on ARM server and set up with xCloud.
Please note that you will not be able to use MySQL 8.4 on ARM servers, as ARM servers do not support MySQL 8.4.
### **Port Check:** [#](/docs/how-to-set-up-server-with-other-providers/)
Ensure that ports 22 (SSH), 80 (HTTP), and 443 (HTTPS) are open on your server. These are usually default open ports on most providers and are necessary for various services.
## **Step 2:** Manage Servers With xCloud [#](/docs/how-to-set-up-server-with-other-providers/)
First, you will need to visit the [**xCloud**](http://hidden-hamlet-226309.wp1.sh) website and click on the “**Sign Up For xCloud**” button to create a new account.
After successful login, select Other Providers to add an existing fresh Ubuntu server and manage it with xCloud.
After successfully provisioning a new Ubuntu 22.04 x64/LTS server in your server provider account, ensure that it has a minimum of 1GB of memory. To proceed further, you will require the following essential information:
- The server IP address
- The root password / public key with access to the server
- Select Web Server: NGINX/OLS
To access your newly provisioned Ubuntu 20.04 or Ubuntu 22.04 server, make sure SSH access is enabled for the designated user. The simplest method is to enable SSH login using a password
However, if password authentication is disabled, you’ll need to SSH into the server and add a public key to the default user for authentication.
It might take around 12-15 min to make the server fully provisioned and this depends on your cloud provider.
### Configure Your Email Server [#](/docs/how-to-set-up-server-with-other-providers/)
For users on managed hosting services like Kinsta, WPEngine, Runcloud, and Cloudways, email providers like Office 365, GSuite, and MXroute are commonly used. If you are migrating from cPanel/Plesk, new email hosting is needed. xCloud doesn’t automatically include email setup for your sites. WordPress often requires reliable transactional email delivery, but default systems can fail, causing spam or delivery issues. Using services like Mailgun for efficient email delivery is recommended. Setting up and configuring Mailgun for WordPress can be found **[here](/docs/setting-up-site-emails-for-wordpress-on-xcloud/)**.
#### Integrate & Manage Servers From Different Providers [#](/docs/how-to-set-up-server-with-other-providers/)
**[How To Setup Your Server With Vultr?](/docs/how-to-get-free-hosting-with-vultr/)**
**[How To Setup Your Server With Google Cloud Platform](/docs/first-server-with-google-cloud-platform/)**
**[Setup Your First Server and WP Site With Digital Ocean in xCloud](/docs/how-to-setup-your-server-with-digital-ocean/)**
Check out our Quick Start Guide to learn how to easily install a WordPress Site on provisioned servers. Still stuck? You can contact our support team for information.
[**Quick Start Guide: Setup Your First Server & Site With xCloud?**](/docs/setup-your-first-server-site-with-xcloud/)
---
# How to Set Up SMTP for n8n with Environment in xCloud - xCloud
> Learn how to set up SMTP for n8n in xCloud using environment and start sending emails through your own mail server with ease.
When setting up a new **[n8n instance](/n8n-hosting/)** in xCloud, you may want to enable email functionality for sending notifications, password resets, and workflow messages. To do this, you can configure SMTP using environment variables.
Follow the steps below to set up SMTP for [n8n](/docs/deploy-n8n-with-xcloud-with-one-click-apps/) with environment so you can start sending emails reliably through your own mail server.
## **Step 1: Go to the Environment Dashboard** [#](/docs/how-to-set-up-smtp-for-n8n-with-environment/)
Begin by logging into your xCloud account. Once logged in, navigate to your site dashboard and click on the **n8n → Environment** from the sidebar.
## **Step 2: Configure SMTP Environment Variables** [#](/docs/how-to-set-up-smtp-for-n8n-with-environment/)
Once you are on the n8n environment, just add the following variables with your SMTP server details:
```
N8N_EMAIL_MODE=smtp
N8N_SMTP_HOST=host.example.com
N8N_SMTP_PORT=587
N8N_SMTP_USER=username
N8N_SMTP_PASS=password
N8N_SMTP_SENDER=admin@mail.com
N8N_SMTP_SSL=false
```
Copy to Clipboard
_Note: The SMTP configuration will only work if_ _N8N\_SMTP\_SSL_ _is set to_ _false__. It will not function correctly if you set this value to_ _true__._
## **Step 2: Test Your SMTP Configuration** [#](/docs/how-to-set-up-smtp-for-n8n-with-environment/)
After saving the environment settings, open the n8n dashboard. Look at the lower-left menu and click on **Settings**.
Then go to the **Users** tab from the sidebar. Click the **Invite** button to open a pop-up window.
In the pop-up, enter the user’s **‘Email address’** and **‘Role’**. Then click the ‘**Invite User’** button. This will trigger an email, helping you confirm that your SMTP setup works properly.
If your SMTP setup is correct, the user will receive an invitation email. If the email arrives, that means everything is working properly.
## **How to Add SMTP in Workflows** [#](/docs/how-to-set-up-smtp-for-n8n-with-environment/)
If you want to send emails directly from within workflows, using environment variables is not enough. You will need to set up SMTP as a saved credential.
Open the ‘**Overview’** section from the n8n sidebar. Then go to the ‘**Credentials’** tab on the dashboard and click ‘**Add First Credentials’**.
A pop-up will appear. Fro. here, choose ‘**SMTP’** as the credential type.
You will now see a form. Fill out this form with the following details:
- Host (your SMTP server address)
- Port (usually 587 or 465)
- User (your SMTP username)
- Password (your SMTP password)
Fill in the required fields accordingly. Once done, click the **Save** button.
And that’s it. This is how easily your [**n8n**](https://n8n.io/) instance could be fully configured to send emails using your specified SMTP server.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries..
---
# How to Set Up Supabase on AWS with xCloud? - xCloud
> Learn how to Set Up Supabase on AWS using xCloud, a cloud management platform to easily deploy, configure and manage your Supabase applications.
[**Supabase**](https://supabase.com/) is an open-source backend-as-a-service (BaaS) platform designed to help developers build scalable applications faster. It provides essential backend features such as a PostgreSQL database, authentication, real-time subscriptions, storage, and APIs – all wrapped into a developer-friendly ecosystem.
Set Up **Supabase** on AWS with xCloud quickly and easily. This guide walks you through the simple steps to configure and launch Supabase on AWS with xCloud, giving you a smooth way to manage databases, authentication and APIs without the usual complexity.
## **How to Setup AWS Server with xCloud?** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
This guide shows how to set up the **[AWS](/docs/how-to-set-up-aws-server-in-xcloud/)** server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Create Your AWS Server in xCloud** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a AWS server and for that select the [**AWS**](https://www.linode.com/) option.
### **Step 3: Sign In to the AWS Management Console** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
Now, before going to the next step, you need to log in to the AWS management console. Sign in as a **‘Root User’** to the [**AWS Management Console**](https://aws.amazon.com/console/) using your AWS account credentials. Once logged in, navigate to the main dashboard where you can access various AWS services.
### **Step 4: Navigate to the IAM Console** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
From the AWS Management Console, click on the Services menu located at the top left corner or search with **“IAM”** and select IAM from the list of services. This will direct you to the IAM dashboard, where you can manage users, groups, roles, and policies.
### **Step 5: Add a New User** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
On the IAM dashboard, locate and click on the Users option in the left navigation panel. This will display a list of existing IAM users. To create a new user, click on the **‘Create User’** button.
### **Step 6: Configure User Details** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
In this step, enter a unique **‘Username’** for the new **IAM** user. Next, choose the type of access the user requires. Check-in **‘AWS Management Console’** access option if the user requires access to the AWS Management Console and click on the **‘Next’** button.
### **Step 7: Set Permissions for Amazon EC2 Instance** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
You have three options to set permissions for the new user. The first one is **‘Add user to group’** which lets you add the user to an IAM group with predefined permissions, which is efficient for managing multiple users with similar access needs. The second one is **‘Copy permissions’** which enables you to duplicate the permissions of another IAM user. And the final policy **‘Attach policies directly’** allows you to assign AWS-managed policies or custom policies.
Here we are choosing the ‘Attach policies directly’ and assigning the access for [**Amazon EC2 Instance**](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to the user and hit on the Next.
**_Note:_** _If you do not find the EC2 Access here, search for the policy in the search bar._
### **Step 8: Add Tags, Review and Create** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
You can add **‘Tags’** to help organize and manage users. Now carefully review all the details and permissions assigned to the new IAM user. If everything is accurate and complete, click the **‘Create user’** button to finalize the creation of the IAM user.
### **Step 9: Give Another permission for Amazon Lightsail** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
Now, set another permission for the new user for [**Amazon LightSail**](https://docs.aws.amazon.com/decision-guides/latest/lightsail-or-ec2/lightsail-or-ec2.html) easily. To specify the permissions for the created user, go to the Permission Policies and click on the **‘Add Permissions Menu’**. Choose the **‘Create Inline Policy’** option from the dropdown menu.
Click on the **‘JSON’** button from the Policy Editor and paste the below given JSON code in the editor. Finally, tap on the **‘Next’** button.
**Here is the JSON code:**
📋
JSON
{
"Version": "2012-10-17",
"Statement": \[
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": \[
"lightsail:GetInstances",
"lightsail:GetKeyPair",
"lightsail:DeleteKeyPair",
"lightsail:GetStaticIp",
"lightsail:ReleaseStaticIp",
"lightsail:SetIpAddressType",
"lightsail:CreateInstances",
"lightsail:GetInstance",
"lightsail:GetInstanceAccessDetails",
"lightsail:DeleteInstance",
"lightsail:CreateKeyPair",
"lightsail:ImportKeyPair",
"lightsail:StartInstance",
"lightsail:DownloadDefaultKeyPair",
"lightsail:GetInstancePortStates",
"lightsail:StopInstance",
"lightsail:AttachStaticIp",
"lightsail:GetRegions",
"lightsail:RebootInstance",
"lightsail:GetOperation",
"lightsail:DetachStaticIp",
"lightsail:GetInstanceState",
"lightsail:GetBundles",
"lightsail:TagResource",
"lightsail:PutInstancePublicPorts"
\],
"Resource": "\*"
}
\]
}
Once the policy is created for Lightsail instance, give the policy a name and hit on the **‘Create Policy’** button.
### **Step 10: Create & Retrieve a User Access Key** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
Now we have to create a user access key. Find **‘Create access key’** under the Summary tab and click on it. Then you will be redirected to the Access Key best practices & Alternatives page, from here select the **‘Other’** option and click on Next.
Now give a Description Tag to proceed to create an access key. Once the access key is created copy the Access Key and Secret from here and go back to your xCloud Dashboard to integrate the server with xCloud.
### **Step 11: Connect the Account & Add Necessary Information** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
From the AWS dashboard, select an existing or connect new account from the dropdown menu. Then choose the AWS services from, you can use any one with the proper credentials or both from the xCloud dashboard.
For example, T3 instances use EBS storage. These instances are not available through the API. However, you can set up such instances manually in your AWS account first and then add them through the Any Provider method in xCloud.
As you have the Access Key and Secret Key, Paste them into the designated blank boxes one by one carefully. Now click on the **‘Verify’** button, it will start verifying the credential and connect you with the AWS server.
Fill in all the information like **‘Server Name’**, **‘Server Region’**, **‘Server Zone’**,**’Server Size’**, etc according to your preference.
Next, choose the web server stack from NGINX or OLS as your requirements and click on **‘NEXT’** button to proceed with the server creation process.
It will start creating a AWS server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many site as you want under this server
## **How to Install Supabase on AWS with xCloud** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
Learn how to install **[Supabase](/supabase-hosting/)** on a cloud server. It walks you through creating a server, configuring the environment and launching your Supabase application easily.
### **Step 1: Access the One Click Apps Dashboard** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘Add New Site’** button.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **AWS server** you set up in xCloud from this dropdown.
Then navigate to the ‘**One Click Apps’** section. You will see **‘Supabase’** just as shown below, click on it to proceed with the deployment of this application.
**_Note:_** _You must complete Phase 2 to meet Docker’s requirements for using Supabase. Without completing Phase 2, Supabase will not be unlocked._
### **Step 2: Set Up the Supabase Application** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting it to production.
### **Step 3: Configure Domain Settings** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a demo domain for your Supabase application. Next, enter your application’s domain.
You will get a **‘Site User’** of your application. You can also adjust it according to your preferences or leave it as the default. In the next section, you will get **‘Admin Username’**, **‘Admin Password’**, and **‘Admin Email Address’**.
**_Note:_** _From here, copy your Admin Username and Admin Password to log in to your Supabase application later._
Next, get the **‘Database Name’**, **‘Database Username’** and **‘Database Password’** for this application and click on the **‘Next’** button.
## **Final Outcome: Visit the Application** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
After completing the setup, you will be able to visit your Supabase site. From the dashboard, click on the **‘Visit Site’** app.
### **Environment Editor for Supabase** [#](/docs/how-to-set-up-supabase-on-aws-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your Supabase app. Just go to the **‘Environment’** option from the sidebar and adjust as you need, then click on the **‘Update Environment’** button.
That’s it! This is how easily you can install Supabase on AWS using **xCloud’s One Click Apps**. xCloud takes care of the heavy lifting, server provisioning, Docker configuration and deployment, so you can focus on building and scaling your application with Supabase’s powerful backend features.
If you’re setting up a demo project or going live in production, this streamlined process lets you get started quickly and confidently.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up Supabase on Vultr with xCloud? - xCloud
> Learn how to Set Up Supabase on Vultr using xCloud, a cloud management platform to easily deploy, configure, and manage your Supabase applications.
[**Supabase**](https://supabase.com/) is an open-source backend-as-a-service (BaaS) platform designed to help developers build scalable applications faster. It provides essential backend features such as a PostgreSQL database, authentication, real-time subscriptions, storage, and APIs – all wrapped into a developer-friendly ecosystem.
Set up **Supabase** on Vultr with xCloud quickly and easily. This guide walks you through the basic steps to configure and launch Supabase on a Vultr server, helping you streamline deployment and manage your application with minimal effort
## **How to Setup A Vultr Server in xCloud?** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
This guide shows how to set up a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1 : Create Your New Vultr Server in xCloud** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available services. For this tutorial, we will create a Vultr server and for that select the Vultr option under **“Bring your own server service”.** The billing of the server will be handled on your Vultr account and in xCloud we won’t charge for this first server.
### **Signup in Vultr with xCloud Promo** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
Start your free hosting offer by signing up at **[Vultr.com](https://vultr.com)**. Create a new account and verify your payment method with either a credit card (temporary $2.50 hold, refunded) or PayPal (minimum $5 payment linked to a card or bank). Once verified, $100 in free credits will be applied automatically. Use promo code “XCLOUD25” during sign‑up to claim the offer
**_Note:_** _If you already have a Vultr account then please skip this step and check how to collect API from Vultr._
### **Collect API key from Vultr** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
After you have successfully completed setting up your billing method, you will need to get the Vultr API key to add it to xCloud to create and manage 1 server and 10 sites for free. Navigate to the Account → API tab from your Vultr dashboard. After that click on the **‘Enable API’** button.
Now, your **‘Personal Access Token’** will be auto-generated. Copy the API Key/Token.
Please make sure you have added Any **IPv4** and Any **IPv6** both under Access Control.
Now, you need to go back to the xCloud dashboard and add your Vultr Label & API Key.
### **Add Team Members in Vultr** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
If you want your team members to use xCloud with Vultr, then make sure these permissions are given.
### **Add Vultr API Key in xCloud** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
Thanks to xCloud, you can create your first server without spending any money. Now, click on **‘Add New Server’** from the xCloud dashboard and you will be redirected to the server selection screen. Then click on **‘Vultr’** to proceed further.
After selecting **‘Vultr’**, set your **‘Key’**, **‘Vultr Label’**, and ‘**Vultr API Key’**. Then click on **‘Verify’**.
### **Step 3: Create a Vultr Server in xCloud** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
Now that you have successfully verified your Vultr account, you will need to add other details to create a server in Vultr using xCloud. Choose your Region, Database Server, Server Size, and much more from one easy dashboard.
After putting all the information, click on **‘Next’** and xCloud will automatically install and set up everything for you in a few minutes.
## **How to Install Supabase with xCloud (One Click Apps)** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
Follow the guide to install Supabase with xCloud with [**One Click Apps**](/docs/deploy-n8n-with-xcloud-with-one-click-apps/) with xCloud. Let’s get started.
### **Step 1: Create a Docker+ NGINX Server** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
First, you need to create a Docker server to deploy Supabase. Click the **‘New Server’** button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Supabase on the Vultr server you previously created with xCloud.
Next, choose your Vultr server to deploy Supabase with xCloud.
Afterward, enter the **‘Server Name’**, set the **‘App Type’** to Supabase and add any relevant **‘Tags’** to help identify your server later.
Next, choose between the **‘General’** and **‘Premium’** options based on your requirements. Then, select a plan that best fits your needs.
Next, choose the **‘Region’** and **‘Ubuntu Version’** for your server. You can also enable or disable the Backup option as needed.
Next, you can see the **‘Docker + NGINX’** stack is already selected, which is mandatory for deploying the Supabase application. Then click on the **‘Create’** button to proceed.
Once the server is created, you will be able to deploy your Supabase Application in this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## **How to Install Supabase on Vultr with xCloud** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
Learn how to install Supabase on a cloud server. It walks you through creating a server, configuring the environment and launching your Supabase application easily.
### **Step 1: Access the One Click Apps Dashboard** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘Add New Site’** button.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **Vultr server** you set up in xCloud from this dropdown.
Then navigate to the ‘**One Click Apps’** section. You will see **‘Supabase’** just as shown below, click on it to proceed with the deployment of this application.
**_Note:_** _You must complete Phase 2 to meet Docker’s requirements for using Supabase. Without completing Phase 2, Supabase will not be unlocked._
### **Step 2: Set Up the Supabase Application** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting it to production.
### **Step 3: Configure Domain Settings** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a demo domain for your Supabase application. Next, enter your application’s domain.
You will get a **‘Site User’** of your application. You can also adjust it according to your preferences or leave it as the default. In the next section, you will get **‘Admin Username’**, **‘Admin Password’**, and **‘Admin Email Address’**.
**_Note:_** _From here, copy your Admin Username and Admin Password to log in to your Supabase application later._
Next, get the **‘Database Name’**, **‘Database Username’** and **‘Database Password’** for this application and click on the **‘Next’** button.
## **Final Outcome: Visit the Application** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
After completing the setup, you will be able to visit your Supabase site. From the dashboard, click on the ‘Visit Site’ app.
### **Environment Editor for Supabase** [#](/docs/how-to-set-up-supabase-on-vultr-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your Supabase app. Just go to the **‘Environment’** option from the sidebar and adjust as you need, then click on the **‘Update Environment’** button.
That’s it! This is how easily you can install Supabase on Vultr using **xCloud’s One Click Apps**. xCloud takes care of the heavy lifting, server provisioning, Docker configuration and deployment, so you can focus on building and scaling your application with Supabase’s powerful backend features.
If you’re setting up a demo project or going live in production, this streamlined process lets you get started quickly and confidently.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up xCloud Mail Delivery Addon For Your Site - xCloud
> Learn how to set up xCloud Mail Delivery Addon to send reliable WordPress transactional emails, avoid spam issues, and manage email plans easily.
WordPress frequently requires sending site emails to you or your users, known as transactional emails. These may include admin notifications, new user signups, password resets, and form submissions. Sometimes, WordPress’s default email delivery system may fail, leading to potential issues like emails being flagged as spam or failing to reach their intended recipients.
Web hosting servers are not optimized for sending emails, and you may also want to [**avoid running your own mail server**.](https://www.digitalocean.com/community/tutorials/why-you-may-not-want-to-run-your-own-mail-server) To solve this issue, xCloud provides a **Mail Delivery Addon** that allows you to send transactional emails through a reliable managed email service. Each team receives **100 free emails per month**, and you can purchase additional plans if you need a higher email limit.
Available xCloud Mail Delivery plans are:
- **1000 emails/month – $1**
- **3000 emails/month – $3**
- **5000 emails/month – $5**
- **8000 emails/month – $8**
Follow the steps below to set up **xCloud** **Mail Delivery** for your website.
## **Step 1: Add xCloud Mail Delivery Email Service Provider** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
First, log in to your **xCloud dashboard** and navigate to **Addons → Mail Delivery** from the sidebar. Click the **Enable** button to activate the Mail Delivery addon.
Next, select **xCloud Email Provider**, choose your preferred email plan, and add a **Label** to identify the provider. After selecting the plan, click the **Buy & Add Email Provider** button to proceed.
Each team can claim **100 free emails per month** directly from the Mail Delivery addon page. From the Email Provider section, click the **Claim Free Plan** option to activate the free email allowance. Once claimed, the free email plan will appear in the provider list.
After claiming the free plan or selecting a paid plan, enter a **Label** in the provided field to identify the provider. Then click the **Buy & Add New Provider** button. A payment gateway will appear where you can complete the purchase using a valid payment method.
Once the payment is completed, the selected email plan will be added to your **Email Provider list**, where you can manage or set it as the default provider for your team.
Once the payment is completed, the purchased email plan will appear in the **Email Provider list**. You can set this plan as the default email provider for your team by clicking the **Set as Default icon** on the right side of the row. If you want to cancel the subscription later, click the **Cancel Subscription icon**.
To review billing information, go to Subscriptions → **Email Subscriptions** and head over to the **Billing History** from the dashboard. This section shows all billing records related to your Mail Delivery subscriptions. You can also click the **Action** button to view more details about each plan.
## **Step 2: Add Email Service To Site** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
After adding the xCloud Email Provider, you need to connect it to your website. Go to your website inside the xCloud dashboard and navigate to **Email Config → Mail Delivery**. From the **Email Provider** dropdown menu, select the xCloud Mail Delivery plan you purchased.
Next, configure the sender details. Choose the **Domain**, enter the sender name in the **From Name** field, and provide the sender email address in the **From Email** field. After completing these settings, click the **Save Changes** button.
You can also choose whether to use the **xCloud domain** or your **own domain** for sending emails. If you select **Use Own Domain**, enter your domain name in the domain field.
Enter your ‘From Name’, ‘From Email’, and ‘Domain’ in the dedicated fields. After entering the domain, you will need to verify it by adding the following required DNS records in your DNS provider.
#
Record Type
Name
Value
1
TXT (SPF)
yourdomain.com
v=spf1 a mx include:xcloud.email ~all
2
CNAME
tracking.yourdomain.com
host.xcloud.email
3
TXT (DKIM)
api.\_domainkey.yourdomain.com
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC bmGbDM2YeMvcwtNQoXN0waGYaciuKx8mtMh5czguT4EZLlXuCf6 V=l56mmt3t68FEX5JJOq4li27lBGoFRkl87uJl7LrQtTZZmZCvrEll0YO 4mp8sDLXC8g1aUAol8TJgxq2MJqCaMyJ5kAm3Fdy2tztPCVlbdLlq mBnWKjtwIDAQAB
4
TXT (DMARC)
\_dmarc.yourdomain.com
v=DMARC1;p=none;
If you have Cloudflare integrated, you can verify DNS in just 1 click. Once the DNS records are added and verified, click **Save Changes** again to complete the setup.
You can also enable Mail Delivery during WordPress site creation. When creating a new WordPress website, simply toggle the Mail Delivery option.
If you have already set an email provider as the Default Provider from the Mail Delivery addon settings, xCloud will automatically select that provider during site creation. This allows you to skip manual provider selection for every new site.
After enabling Mail Delivery, confirm the From Name and From Email details, then continue with the site creation process.
## **How To Manage xCloud Mail Delivery Subscriptions** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
Manage your Mail Delivery plans, monitor email usage, and configure SMTP or API access from one place. xCloud also allows you to automate plan upgrades to keep your transactional emails running without interruption.
### **Step 1: Go to The Subscriptions** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
To manage your email subscriptions, open the **xCloud dashboard** and navigate to **Settings → Subscriptions → Email Subscriptions**.
From this section, you will see an overview of your email usage, including the **Total Emails** and **Available Emails**. This overview helps you monitor how many emails remain in your current plan. You will also find options for **SMTP Configuration** and **API Key** in this section.
Under the **SMTP Configuration** section, you will find details such as **Username, Password, SMTP Server, and Port**. These credentials allow you to connect the xCloud Mail Delivery service with your website or external applications that require SMTP authentication.
The **API Key** section provides a key that developers can use to integrate the xCloud Mail Delivery service with custom applications or services.
### **Enable Auto Upgrade Mail Delivery Plan** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
Email delivery is a critical service for any business. Transactional emails such as password resets, order confirmations, and form notifications must reach users without interruption. To prevent your email limit from blocking these important messages, you can enable the **Auto Upgrade Mail Delivery Plan** option.
xCloud will notify you when your email usage reaches **90% of your available quota**, giving you time to take action before the limit is reached. If you enable **Auto Upgrade**, xCloud will automatically add credits to your current plan once the limit is reached. This ensures that your transactional emails continue sending without disruption and removes the need for manual plan upgrades.
Enable the toggle for this feature. After enabling it, a dropdown menu will appear where you can select the plan you want xCloud to upgrade to automatically. Choose your preferred plan and click the **Save** button.
Once this feature is enabled, xCloud will automatically upgrade your email plan. When the threshold is reached **(90% limit)**. This ensures that your website emails continue sending without interruption
Below the configuration section, you will see all the **subscribed email plans** for your team. From here, you can click the **Actions** button beside each plan to manage or cancel subscriptions. You can also check the **Billing History** to review all transactions related to your Mail Delivery subscriptions.
## **How Does xCloud Managed Emails Usage Limits Work?** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
xCloud Managed Email limits are applied at the team level, not per individual site. This means the total number of emails you have purchased, whether it’s the free 100 monthly emails or additional purchased email plans, is available for use across all sites within the same team.
For example, if you have 10 sites under a single team and you purchase a plan of 1000 emails, those 1000 emails become part of a shared email pool. Any of your sites in that team can send transactional emails using this shared quota. You are not required to buy separate email packages for each website.
## **💡Troubleshooting Tip** [#](/docs/how-to-set-up-xcloud-mail-delivery-addon/)
If you cannot connect to your email provider because the domain is already linked with another email service, you need to check if the domain is still registered with your previous hosting provider.
For example, if your domain was registered or managed by Cloudways, their system may still have it linked. In this case, contact the Cloudways support team and request that they manually remove the domain from their email service.
Once it is removed, you can connect your domain with xCloud without any issues.
That’s how easily you can add the xCloud Managed Email Service provider for site emails for the xCloud environment to streamline the email delivery process of transactional emails.
You can check [**this documentation**](/docs/setting-up-site-emails-for-wordpress-on-xcloud/) if you want to connect any SMTP provider to your xCloud environment for site emails. Still stuck? Contact our support team for any of your queries.
---
# How to Set Up xCloud MailBox Addon - xCloud
> Learn how to set up a professional mailbox with your own domain using xCloud Mailbox Addon.
A mailbox stores and manages your emails. It allows you to send, receive, and organize messages using an email address that includes your own domain. For example, instead of using a generic email like **yourname@gmail.com**, you can use **yourname@yourbusiness.com**.
Having a professional mailbox with your domain helps you build trust with customers. It gives your communication a branded, business-like look. It also helps you manage business emails more securely and efficiently, all in one place.
The xCloud MailBox Addon has been upgraded with a powerful new email infrastructure partner to bring you much more than just email. Your mailbox is now a complete business productivity suite with AI-powered features, a built-in calendar, task management, cloud drive, document editors, shared contacts, and enterprise-grade security.
### **Here’s what you can now do with xCloud MailBox:** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
- **AI-Powered Productivity** – Auto-generate email replies and subject lines with AI, summarize long email threads in seconds, let smart classification sort your inbox automatically, hand off routine work to Smart Tasks, and have your emails read aloud with text-to-speech.
- **Full Business Workspace** – Manage your schedule with a built-in calendar that supports RSVP, smart scheduling, and resource booking. Track work with shared task lists, due dates, and comment threads. Store and share files with Cloud Drive, including version history, WebDAV, and sync clients for every platform. Edit documents, spreadsheets, and presentations right in your browser with real-time collaboration.
- **Enterprise-Grade Security** – Protect your inbox with two-factor authentication, WebAuthn hardware key support, end-to-end encryption, and premium antivirus, antispam, and antiphishing protection.
To learn more about all available features and plans, visit the [**xCloud Mailbox Addon**](/mailbox/).
_Note: xCloud is offering a free 100 MB Mailbox plan that is available exclusively for xCloud Managed Servers and xCloud Provider Servers. To get this offer, you need to create a new mailbox on an xCloud Managed Server or on an xCloud Provider. Existing mailboxes are not eligible for the free plan._
_If you already have a mailbox, you can move it to our new mailbox provider and enjoy the upgraded features while keeping your current price._
To create professional email addresses with your own domain, use the Mailbox Addon. With the xCloud MailBox Addon, you can create and manage professional email addresses using your own domain name.
You can send and receive emails securely from your email addresses. It helps you manage business emails with ease and gives you full control over your mailbox setup. Follow the steps below to set up your Mailbox easily.
_Note: This Addon is not available on our Reseller Hosting Program. To learn about the features that are available on the Reseller Hosting Program, please visit_ [_**here**_](/docs/xcloud-reseller-hosting-program-features/)_._
## **Step 1: Go to Addons** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Log in to your xCloud dashboard, then head over to the left navigation menu and click on the**‘Addons’ option** from the dashboard. Here you will find all the **[addons](https://app.xcloud.host/user/addons-list)** available in xCloud.
## **Step 2: Enable xCloud Mailbox Addon** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Look for the **‘MailBox’** addon from the list of available addons. If you have not purchased it yet, click the ‘Enable’ button to purchase it.
Next, click on the ‘Get Mailbox For $1” button to proceed.
## Step 3: Subscribe to a Mailbox Subscription Plan [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Next, a pop-up will appear. Enter the credentials ‘Email’ and ‘Password’ in the dedicated fields. Then choose a plan according to your needs. And finally, click on the ‘Pay’ button.
Right now, xCloud Mailbox offers 5 plans:
Free 100MB
8GB MailBox
25GB MailBox
50GB MailBox
80GB MailBox
Available on all plans:
Everything in the 8GB Plan, and:
Everything in the 50GB plan
Everything is free, and:
Everything in 50GB plan
Email Signatures
Two-Factor Authentication
Smart mail sorting
Schedule Send
Smart Classification
Email Rules Engine
Undo Send
Event attachments
Trash & Recovery
AI Email Suggestions
Spam/Phishing Protection
Follow-up Reminders
Task collaboration with team
Snooze emails for later
Text-to-Speech
Unified Inbox
Customizable Dashboard
File Preview
Smart Scheduling
Email Summarization
Recurring Events
Profile picture
Global Address Book
Public Share Links
Smart Tasks
Recurring Tasks
10 language options
Shared Contacts
File Upload & Download
25+ language Support
Personal Address Books
External Calendar Subscriptions
WebAuthn Support
Office Compatibility
Task collaboration with the team
Recurring Events
CSV/vCard Import & Export
RSS Widget Support
Built-in Document Editors
Unlimited Version History
Multi-view Calendar + More
Keyboard navigation + More
Mail Templates + More
20+ language support + More
Advanced Spam/Phishing Protection + More
[Get Started For Free](https://app.xcloud.host/addons/mailboxes?fbclid=IwY2xjawRhTWJleHRuA2FlbQIxMQBicmlkETFzOHhxTGdNSlp2a1BoZ3Fwc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHpvLywXhMPSEKLNESdart9pnGXjg-vlAMYT7S2EgYWozkG5R-ySlhmCuih_E_aem_TdEr6eHWRy4PewSvF29gnA&_gl=1*1ik5gcl*_gcl_au*MzkzOTY0Nzg0LjE3NzMwMjc3MjYuNDQxOTE3ODc3LjE3Nzg2NTM3MDMuMTc3ODY1NTY5Nw..)
[Get Started For $1/mo](https://app.xcloud.host/addons/mailboxes?fbclid=IwY2xjawRhTWJleHRuA2FlbQIxMQBicmlkETFzOHhxTGdNSlp2a1BoZ3Fwc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHpvLywXhMPSEKLNESdart9pnGXjg-vlAMYT7S2EgYWozkG5R-ySlhmCuih_E_aem_TdEr6eHWRy4PewSvF29gnA&_gl=1*1ik5gcl*_gcl_au*MzkzOTY0Nzg0LjE3NzMwMjc3MjYuNDQxOTE3ODc3LjE3Nzg2NTM3MDMuMTc3ODY1NTY5Nw..)
[Get Started For $2.5/mo](https://app.xcloud.host/addons/mailboxes?fbclid=IwY2xjawRhTWJleHRuA2FlbQIxMQBicmlkETFzOHhxTGdNSlp2a1BoZ3Fwc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHpvLywXhMPSEKLNESdart9pnGXjg-vlAMYT7S2EgYWozkG5R-ySlhmCuih_E_aem_TdEr6eHWRy4PewSvF29gnA&_gl=1*1ik5gcl*_gcl_au*MzkzOTY0Nzg0LjE3NzMwMjc3MjYuNDQxOTE3ODc3LjE3Nzg2NTM3MDMuMTc3ODY1NTY5Nw..)
[Get Started For $5/mo](https://app.xcloud.host/addons/mailboxes?fbclid=IwY2xjawRhTWJleHRuA2FlbQIxMQBicmlkETFzOHhxTGdNSlp2a1BoZ3Fwc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHpvLywXhMPSEKLNESdart9pnGXjg-vlAMYT7S2EgYWozkG5R-ySlhmCuih_E_aem_TdEr6eHWRy4PewSvF29gnA&_gl=1*1ik5gcl*_gcl_au*MzkzOTY0Nzg0LjE3NzMwMjc3MjYuNDQxOTE3ODc3LjE3Nzg2NTM3MDMuMTc3ODY1NTY5Nw..)
[Get Started For $8/mo](https://app.xcloud.host/addons/mailboxes?fbclid=IwY2xjawRhTWJleHRuA2FlbQIxMQBicmlkETFzOHhxTGdNSlp2a1BoZ3Fwc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHpvLywXhMPSEKLNESdart9pnGXjg-vlAMYT7S2EgYWozkG5R-ySlhmCuih_E_aem_TdEr6eHWRy4PewSvF29gnA&_gl=1*1ik5gcl*_gcl_au*MzkzOTY0Nzg0LjE3NzMwMjc3MjYuNDQxOTE3ODc3LjE3Nzg2NTM3MDMuMTc3ODY1NTY5Nw..)
_**Note: xCloud is offering a free 100 MB Mailbox plan that is available exclusively for xCloud Managed Servers and xCloud Provider Servers. To get this offer, you need to create a new mailbox on an xCloud Managed Server or on an xCloud Provider. Existing mailboxes are not eligible for the free plan.**_
_However, existing mailboxes can be migrated to our new mailbox provider. This allows you to benefit from all the upgraded features while continuing to pay your current rate._
## Step 4: Verify Mailbox [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Once the purchase is done, your subscription plan for the xCloud Mailbox will be shown in the dashboard. Here you can see the ‘Pending Verification’ status. Click on the ‘Verify Now’ button to start the DNS setup process.
You can do this in two ways. If you have already connected your domain with Cloudflare, the easiest method is to toggle the “Auto Manage DNS Records” switch. This will automatically add all the required DNS records like MX and SPF to your Cloudflare account and verify them.
If you manage your domain’s DNS settings with a different domain provider, you will need to copy the required records provided and paste them into your domain provider’s DNS panel. These include various types of DNS records like MX and SPF. After adding records on your DNS provider, click on the ‘Verify Records’ button
## Step 5: Launch Your Mailbox [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
After configuring everything, let’s go back to the Mailbox dashboard and click on the Access option to log in to your Mailbox dashboard.
Once logged in, you can check out the ‘Inbox’, ‘Draft’, and more from the dashboard. Even send the new message to your preferred email address as well. Moreover, access, Calendar, Drive, AI-powered replies, summarize, and more features to increase your productivity.
And that’s it, this is how easily you can set up your xCloud Mailbox for your site in just a few clicks.
👉 Want to migrate your emails from legacy Mailbox to the new xCloud MailBox? Follow the steps in this **[documentation](/docs/how-to-migrate-emails-from-legacy-mailbox-to-the-new-xcloud-mailbox/)**.
## **Advanced Configuration Settings Of Mailbox** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
With the xCloud Mailbox Addon, you get a lot of advanced options to tailor your email communication more easily and hassle-free. Let’s setup few more advanced configurations:
### **Set up Aliases** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Aliases allow you to create extra email addresses that redirect to existing mailboxes without needing to set up new ones.
For instance, if you own a mailbox, user@example.com, and wish to receive emails at another address, user2@example.com, without having a separate mailbox, you can establish user2@example.com as an alias that directs to user@example.com. Now, you only need to log in to user@example.com to check the emails received at both addresses.
Navigate to Aliases from the left side menu and click ‘Add Alias’. Enter the alias and select the domain from the dropdown menu. Next, select the email address you wish to be a member of that alias. Finally, click on the ‘Add Alias’ button.
## Set up Mail Forwarding [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Mail forwarding lets you send a copy of incoming emails from one mailbox to another address. This is useful if you want to manage multiple email addresses from a single inbox.
For example, if you own info@yourdomain.com and want to receive those emails at your main address, you@yourdomain.com, you can set up forwarding. All emails sent to info@yourdomain.com will automatically be sent to you@yourdomain.com.
You can also forward the emails in your mailboxes. Navigate to the ‘Forwarding Mail’ option from the dashboard. Click on the three-dot icon and click on the ‘Edit’ option.
A pop-up will appear; you need to enter your email account in the dedicated field. Next, add the forwarding email addresses where you want to forward the emails. Finally, click on the ‘Save forwarding’ button
## Enable Catch All For Your Email Account [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Next, go to the ‘Catch All’ option from the left side menu. Next, toggle on to enable and set an email address to send messages to in case of a non-existent recipient for this domain. Then, under the Catch All Address dropdown, select the email address where you want to catch the email addresses and click on the ‘Add Catch All’ button.
## **Setup Your Email Clients With IMAP & POP** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
On the other hand, POP3 (Post Office Protocol v3) is designed for downloading emails to a single device. Once downloaded, emails are typically removed from the server, and any changes made on one device won’t sync to others. POP3 is best suited for users who only check their email on one device and prefer to store their emails locally.
Next, go to the POP option on the left side. Here you will get the credentials to set up your email client using POP.
IMAP (Internet Message Access Protocol) is the recommended option for most users. It allows for two-way synchronization between your email client and the server, meaning any changes you make—such as reading, deleting, or moving messages—will reflect across all your devices. This makes IMAP ideal if you plan to access your email from multiple devices, like your smartphone, tablet, or computer.
Next, go to the IMAP option on the left side. Here you will get the credentials to set up your email client using IMAP.
👉 To learn more about IMAP and POP, read this **[documentation](/docs/configure-email-client-with-mailbox-addon-xcloud/)**
## **Reset Password** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
If you want to change your Mailbox password, go to the ‘Change Password’ option, and head over to the ‘New Password’ field. Here, enter your new password and click on the ‘Change Password’ button.
## **Upgrade Your Mailbox** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
If you want to upgrade your existing Mailbox plan, just click on the ‘Upgrade Mailbox’ option and choose your preferred plan, and click on the ‘Upgrade’ button. It will instantly upgrade the plan.
## ⚠️ Important Considerations [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
1\. MX Record Conflicts:
If your domain already has existing MX records, verification will fail. Make sure to remove all existing MX records before connecting your mailbox.
2\. Failed Verification Fix: If clicking ‘Verify Records’ does not work, Double-check that all DNS records have been correctly added. If you’re using Cloudflare, try toggling the ‘Auto Manage DNS Records’ setting OFF and then ON again. Wait a few seconds and it will start working again.
Also, keep in mind that DNS records may take some time to publish globally. Depending on your DNS provider, it can take up to a few hours for the records to fully propagate. Cloudflare usually updates DNS records the fastest, often within minutes.
## **📌 Limitations** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
To ensure fair and stable service, here are some limitations and notes users should keep in mind:
1\. There are some rules and limitations you need to be aware of. You are allowed to create multiple mailboxes under the same domain as long as they are in the same team. However, you cannot create mailboxes or aliases using the same domain in different teams. For instance, if demo@domain.com is part of Team A, then test@domain.com cannot be created under Team B.
2\. You cannot have aliases with the same name as the mailboxes or the alias of aliases.
2\. It is also important to avoid using POP email clients. These clients only download emails to your device and do not sync changes like read status or sent emails. To ensure full syncing across all your devices, you should use IMAP-supported email clients.
4\. If you are using Cloudflare and face verification issues even after automatic integration, try toggling the DNS integration off and on again. This often helps reset the settings and successfully verifies your domain.
## **xCloud Mailbox Add-on – Frequently Asked Questions (FAQs)** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
### **How is xCloud Mailbox Addon billed?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
The billing is monthly, based on your chosen plan. You only pay for the plan you subscribe to. There are no hidden charges for aliases or forwarding.
### **Can I create multiple mailboxes under one domain?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes, you can create multiple mailboxes as long as they’re within the same xCloud team.
You cannot use the same domain across different teams.
Example: If user@domain.com is in Team A, then admin@domain.com can’t be in Team B.
### **Are aliases free to use?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. Creating and using email aliases is completely free and included with your Mailbox plan.
### **Is there a limit on how many aliases I can have?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No, there is no limit to how many aliases you can create under a domain. An alias cannot have the same name as an existing mailbox, and aliases cannot forward to other aliases.
### **What is email forwarding, and is it free?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Email forwarding automatically sends a copy of incoming mail from one address to another. Email forwarding is included for free. Each mailbox supports an unlimited number of email forwarding addresses.
### **What if my domain verification fails?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Try the following:
- Double-check all DNS records
- If using Cloudflare, toggle ‘Auto Manage DNS’ OFF and then ON again
- Wait a few minutes and try verifying again.
### **After logging in, if you see the white page, what do you do?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Once you log in to your webmail page, if you encounter a blank white screen, it may be due to your ad blocker. Please ensure that you turn off your ad blocker, clear your cache, and then refresh the page.
### **Can I use xCloud Mailbox for transactional emails?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes, it is possible. SMTP is included with the mailbox and comes with a sending limit of 250 emails per day. However, for SMTP or transactional emails such as subscriber notifications, order confirmations, and marketing messages, we recommend using the **[Email Delivery Addon](/docs/how-to-set-up-xcloud-mail-delivery-addon/)** for better reliability and performance.
### **What is a business email?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
A business email uses your own domain name as the address, like you@yourdomain.com. You use it for professional communication, and it makes your brand look more credible. You get your business name in the address, more control over security, and the ability to add more accounts as your team grows.
### **How is business email different from personal email?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
You use personal email to talk with friends and family, sign up for services, and manage social media. Business email handles professional communication and contacts. It comes with email aliases, group aliases, more storage, and features like migration support, an admin control panel, and team-level integrations.
### **What is email hosting?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Email hosting lets you send and receive emails using your own domain name. You get a professional address, more storage, and strong security and privacy controls. If you want full control over your business email without relying on free providers, email hosting gives you that.
### **How do I create a business email address with xCloud Mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
If you own a domain, connect it to xCloud Mailbox and set up your email in minutes. If you don’t have a domain, you can buy one, and create a Mailbox using that domain.
### **How much storage do I get with xCloud Mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
xCloud Mailbox has 5 plans, including a free tier. Storage ranges from 100 MB free plan to 80 GB and each plan includes different features. If you need more space later, you can add storage to your account at any time.
### **Can I create aliases and forwarding rules?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. You can create unlimited aliases and forwarding addresses per mailbox at no extra cost.
### **Which email protocols are supported?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
xCloud supports IMAP, POP3, and SMTP. You can set it up on Outlook, Thunderbird, Apple Mail, Gmail, iPhone, Android, and most other email clients.
### **Where is the email hosted? On my server or somewhere else?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Your email does not run on your server. xCloud partners with a mailbox provider that runs email on its own infrastructure with dedicated IP addresses. Your web server handles your sites. Your email runs on infrastructure built for reliable delivery.
### **Can I buy one large mailbox and put all my clients’ email accounts inside it?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No. Each email account has its own storage. If you need three addresses like support@yourdomain.com, sales@yourdomain.com, and contact@yourdomain.com, you buy three separate mailboxes. Each one gets its own plan and storage. This works the same way as Google Workspace and other email platforms. Plans go up to 80 GB per mailbox. If you need more, reach out to the team.
### **Can self-managed server users use xCloud Mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. Self Managed server users get the same plans, pricing, and features as everyone else on xCloud. The free mailbox plan is the only exception. It is limited to xCloud-managed server users. Self-managed server users can buy any paid plan with no feature restrictions.
### **Can I disable the AI features for my team or clients?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. You can turn AI features off at the domain level. If you manage mailboxes for clients or staff and don’t want them using AI suggestions, you control that setting.
### **Will the existing mailbox provider be removed? What happens if I don’t migrate?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
The existing provider is not going away right now. You can keep using it with no disruption. Migrating to the new provider gives you more features at the same price. xCloud built a migration tool to make the switch easy, and support can help if you need it. There is no deadline to migrate.
### **How do I claim my free mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Deploy your site on an xCloud managed server (xCloud or xCloud Provider). A “Claim Free Mailbox” banner shows up on your dashboard. Click it, follow the steps, and your free 100 MB mailbox is ready. Each domain on an xCloud managed server gets one free mailbox.
### **I am paying for email on my xCloud managed server. Will my existing mailbox become free?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No. The free mailbox applies to new mailboxes created on xCloud managed servers. Existing mailboxes are not eligible. You can migrate your existing mailboxes to the new provider using the built-in migration tool and keep paying the same price, with access to all the upgraded features.
### **I don’t see the “Claim Free Mailbox” banner. What should I check?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
A few things could be going on. Your site must run on an xCloud managed server. Hetzner, AWS, DigitalOcean, and other non-managed providers don’t qualify. The site needs to be in production, not staging. Your team may have used all its free mailbox slots (default cap is 10 per team). The domain may have a free mailbox assigned to it. Legacy mailboxes on the domain that haven’t been migrated will block the banner until migration is done. You or someone on your team may have dismissed the banner (dismissal is per domain). White-label tenants don’t see the mailbox addon.
### **I have legacy mailboxes on my domain. Can I still get a free mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes, after you finish the migration. Use the migration wizard to move all your legacy mailboxes to the new provider. Once that is done, the free mailbox banner shows up on every site that shares that base domain. You don’t need to contact support. It happens on its own.
### **If I create a new site on my xCloud Managed Server, does it qualify for a free mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. Any site on an xCloud managed server qualifies, including new ones. The domain can’t have claimed a free mailbox before.
### **Is the free mailbox available on xCloud reseller-managed servers?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No. The mailbox addon is not available on the xCloud reseller program right now. It works on standard xCloud managed servers.
### **I have a lifetime deal (LTD). Am I eligible for a free mailbox?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Free Mailbox is available for both xCloud Managed Servers and xCloud Provider Servers.
If you are using an xCloud Provider Server, you are eligible to claim the free Mailbox offer.
However, this offer is not available for self-managed servers. In other words, if you are managing your own server instead of using an xCloud Provider Server, you will not be able to claim the free Mailbox.
### **What happens to my free mailbox if I move my site off xCloud?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Your free mailbox keeps working. It won’t shut down right away. An ineligibility period starts, and you get notification emails on Day 0, 7, 14, and 30. An in-app banner gives you two options: move your site back to xCloud, or upgrade to a paid mailbox plan. Auto-suspension is not active in the current version.
### **I brought my site back to xCloud. Will the ineligibility warning go away?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. The system picks up the change within seconds, closes the ineligibility episode, and removes the warning banner on the next page load.
### **I deleted my free mailbox but my counter still shows it is at the limit.** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
The counter should update right when you delete a mailbox. Refresh the mailbox addons page. If the count is still wrong after refreshing, contact our support team so the team can look into it.
### **Can I have more than 10 free mailboxes on my team?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. The default cap is 10 per team. Contact support to request a higher limit.
### **I am getting a “Free plan limit reached” error but I only have a couple of free mailboxes.** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Your team may have a custom limit set lower than the default. A recently deleted mailbox might still be processing. Contact our support team so they can check your team’s settings and fix the issue.
### **I have a paid mailbox on my domain. Can I add a free one too?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Yes. Paid and free mailboxes can exist on the same domain as long as everything runs on the default provider. There is no restriction on combining both plan types.
### **Can I claim a free mailbox through the API?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No. Free mailbox claims go through the dashboard with a valid site context. API-based claims are not available in this version.
### **The migration wizard won’t let me cancel. Is this a bug?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No. Once any mailbox in the migration reaches the DNS-verified stage, email is flowing to the new system. Canceling at that point would lose the received mail. You need to finish the migration to keep everything intact.
### **Is it possible to downgrade my mailbox plan?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
No, downgrading your mailbox plan is not possible. Once you have selected and activated a plan, it cannot be changed to a lower tier. If you have specific concerns about your current plan, we recommend reaching out to the xCloud support team for guidance.
### **Can I use my own domain or subdomain for xCloud Webmail?** [#](/docs/how-to-set-up-xcloud-mailbox-addon/)
Currently, xCloud Mailbox does not support directly hosting the webmail interface on a custom domain, subdomain, or path such as `example.com/webmail` or `webmail.example.com`.
To access your mailbox, please use the official webmail/access link provided inside the xCloud Mailbox area.
If you want an easier URL for your team or clients, you may create a redirect from your own website, for example:
– `example.com/webmail`
– `webmail.example.com`
This redirect can point users to the official webmail URL. However, the actual webmail application will still open on the official xCloud-provided webmail address.
Still stuck? Contact our [**support team**](/support/) **for** any of your queries.
---
# How To Setup ARM Server In xCloud? - xCloud
> xCloud provides built-in support of ARM server for Hetzner. Learn how to set up ARM server in xCloud easily.
ARM-based servers are computing servers that utilize processors built on the ARM (Advanced RISC Machine) architecture. ARM processors are known for their energy efficiency, cost-effective, and high-performance solutions.
xCloud provides **built-in support of the ARM server for Hetzner**, and you can also add ARM server from any provider using our other provider integration. Follow the steps below to set up ARM server with Hetzner and Any Other provider:
## **Setup ARM Server In xCloud For Hetzner** [#](/docs/how-to-setup-arm-server-in-xcloud/)
Setup ARM server in xCloud for Hetzner easily. To create an ARM-based server with Hetzner, click on the **‘Add Server’** to create a new server then choose Hetzner server.
Now choose the account, give the server a Name, choose the server region and select the **‘Shared Amphere’** from the dropdown menu of **‘Server Size’** to select the ARM server and your Hetzner server will be created with ARM-based servers.
**Read the documentation:** [**How To Setup Hetzner Server In xCloud Host?**](/docs/set-up-hetzner-server-in-xcloud/)
Similarly, you can [**connect any provider**](/docs/how-to-set-up-server-with-other-providers/) that is based on any ARM server using Any other provider and set up with xCloud easily.
This is how easily you can set up your ARM-based servers in xCloud and get a seamless performance.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Setup DNS Record In xCloud? - xCloud
> Follow this simple guide to verify your DNS record with xCloud.
DNS record, which stands for Domain Name System record, is like a directory that helps link website names to their actual server IP addresses. It points a website domain towards the IP address of the server where it is hosted. You can easily connect your website and set DNS records with xCloud.
## How To Point A Domain To xCloud Site [#](/docs/how-to-setup-dns-record-in-xcloud-server/)
xCloud does not manage the DNS for your domains. So, there is no need to take the hassle of changing your name server. Before using xCloud, you must have a good knowledge on managing the DNS for your domains. xCloud will inform you when you should add specific DNS records, and what the values should be, but the responsibility for DNS management is up to you.
### Seamless Integration With Cloudflare [#](/docs/how-to-setup-dns-record-in-xcloud-server/)
With xCloud, you can easily integrate domain prover for DNS management to enhance the performance and security of your WordPress site. xCloud provides very powerful integration with **Cloudflare**. Read this [**step-by-step guide**](/docs/using-xcloud-with-cloudflare-for-dns-management/) to integrate Cloudflare for DNS management. Or, you can follow the below steps.
**Step 1: Choose Your Site & Add Information**
First, create a fresh WordPress site as shown below in the image.
In the next step, you have to add your site title, domain setup, domain name, and an “**A Record”**.
For example, if your DNS is in NameCheap navigate to **Domain List → Advanced DNS and** copy the **A Record** from there.
_Note: It may take a few hours to point your domain properly._
**Step 2: Verify Your DNS**
Now you have pasted your A Record, you need to verify your DNS if it has pointed successfully. Click on the ‘**Verify My DNS**’ as shown below.
Well, Cloudflare integration is not required. You can manage DNS with your own domain provider like **Namecheap**, **GoDaddy**, or anyone else. You just need to add **A Record**. There are many different types of DNS records, **A Record** is one of them. To use your website with xCloud, you will need to be familiar with The A Record. But before that, if you have any existing record, or you want to migrate your site, you need to delete all existing records.
### How To Add A Record [#](/docs/how-to-setup-dns-record-in-xcloud-server/)
**A Record** stands for **Address Record** and it is used to point a domain name to an IP address. When someone types your website domain name into their browser, the A Record lets the browser know where the website files and data are hosted. You can easily add an A Record by following the 2 steps.
1. Log in to your Domain Registrar Panel.
2. Select your target domain and visit the DNS management section.
As an example, let’s add an A Record on **Namecheap** domain provider. If you are using **GoDaddy** as your domain provider, then you can check [**this guide**](https://in.godaddy.com/help/add-an-a-record-19238) to add an A Record.
**Create An A Record**
**Step 1:** First, sign into your Namecheap account. Select Domain List from the left sidebar and click Manage next to your domain.
**Step 2:** Now, Select the Advanced DNS tab at the top of the page
**Step 3:** Now create an A record using the following information.
\# Add the below A Record if you want to point a root domain (yourdomain.com) to the xCloud server IP address.
Type: A
Host/Name: @ or blank
Value/Target: Your IP address
TTL: Automatic or Default
\# Add an A Record if you want to point a domain with www (www.yourdomain.com) to the xCloud server IP address.
Type: A
Host/Name: www
Value/Target: Your IP address
TTL: Automatic or Default
\# Add the below A Record if you want to point a subdomain (blog.yourdomain.com) to the xCloud server IP address.
Type: A
Host/Name: blog (any subdomain)
Value/Target: Your IP address
TTL: Automatic or Default
4\. Add the below A Record if you want to use a wildcard to the xCloud server IP address.
Type: A
Host/Name: \*
Value/Target: Your IP address
TTL: Automatic or Default
Once you have added the A Record, make sure to save all the changes. Your changes may take up to 24 hours to take effect across the internet.
### Check DNS [#](/docs/how-to-setup-dns-record-in-xcloud-server/)
Once you have done adding A Record, ensure there are no conflicting records for the same host and remove them if necessary. The records you need to check may be of Unmasked/Masked/Permanent Redirect, A, or other record types.
Here is an example of conflicting records. Have a look below.
You can check the status of your DNS records propagation by using any third-party tool such as [**whatsmydns.net**](https://www.whatsmydns.net/).
Thus, you can set the DNS record in xCloud without any hassle.
If you still have any issues contact our [**support**](http://support@xcloud.host) team for help.
---
# How to Setup Mautic with xCloud One Click Apps - xCloud
> Learn how to setup Mautic with xCloud One Click Apps by following simple steps to launch a live or demo site without technical hassle.
Mautic is a popular marketing automation tool. With xCloud, you can deploy Mautic in just 1 Click with our One Click Apps. Follow the steps below to have a fully operational Mautic site with just a few clicks:
## **Step 1: Access the One Click Apps Dashboard** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
Begin by logging into your xCloud account. Once authenticated, navigate to your dashboard and click on the **‘New Site’** button.
This will take you to the site creation interface. From here, choose the **‘Server’.**
Then go to the **‘One Click Apps’** section. Select **‘Mautic’** from the available applications to initiate the deployment process.
## **Step 2: Setup Mautic with xCloud** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘**Site Title’** and add relevant ‘**Tags’** to help organize your deployment. At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
## **Step 3: Configure Domain Settings** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
If you select the ‘**Demo Site’** option, xCloud will assign a temporary subdomain for your Mautic application.
**_Note:_** _Note that once a demo site is promoted to a live environment, you cannot revert back to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding._
## **Step 4: Configure and Install the Site** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
Here, you will get the credentials **‘Admin Username’, ‘Admin Password’, ‘Admin Email Address’,** to log in to the site later. You can keep them as it is or customize them as your preferences.
Also, you can create a new database to **‘Create Database to a Server**’ or ‘**Add Your Existing Database**’. Once all settings have been reviewed and configured, click the **‘Next’** button to proceed.
_Note: We recommend leaving the database settings as default because xCloud will automatically create and configure a database for you._
## **Step 5: Go Live** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
You can [**add your own ‘Domain’**](/docs/how-to-go-live-from-staging-domain/) to host the site by going to the Domain section. Also, you can add an **‘Additional Domain’** with your custom domain.
## **Step 6: Visit the Mautic Site** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
With Mautic set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** button.
## **Step 7: Visit the Mautic Site** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
With Mautic set up on xCloud, you can now verify that everything is working. From your dashboard, click the **‘Visit Site’** button. xCloud automatically registers the admin user using the credentials you provided during setup. So instead of creating a new account, simply **log in** with your admin username and password.
Once logged in, you’ll be taken to the Mautic dashboard where you can begin customizing your marketing automation environment.
This should bring you to the Mautic Overview page. Now that your Mautic instance is up and running, let’s fine-tune its settings for security and [**customization**](https://docs.mautic.org/en/6.0/index.html).
## **How to Reset the Mautic Admin Password Using xCloud Command Runner** [#](/docs/how-to-setup-mautic-with-xcloud-one-click-apps/)
If you ever forget the admin password, you can reset it easily using the **xCloud command runner**.
You do not need SSH access. Just run the below command with your user or new password:
```
cd /var/www/yoursite.com
USER="your-user-name"
PASS="your-new-password"
H=$(php bin/console security:hash-password "$PASS" "Mautic\\UserBundle\\Entity\\User" 2>/dev/null | awk '/Password hash/{print $NF}')
php bin/console doctrine:query:sql "UPDATE users SET password='$H' WHERE username='$USER';"
echo "✅ Password for $USER reset."
```
Once the command run is successfully completed, your admin password will be updated. If it shows **1 row affected**, the password is reset. You can now log in using the new password.
And that’s it, this is how easily you can quickly and efficiently deploy an Mautic instance using xCloud’s One Click Apps feature.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Setup a Digital Ocean Server in xCloud? - xCloud
> Here we have learned how to setup a Digital Ocean server with xCloud.
With [**xCloud**](/)**,** you can easily setup your Digital Ocean server in xCloud. xCloud aims to simplify the process of hosting and managing WordPress sites, allowing developers and agencies to focus on building great websites without worrying about the underlying infrastructure. Now let’s follow these steps to get you started.
### Step 1: Sign Up/Login With xCloud [#](/docs/how-to-setup-your-server-with-digital-ocean/)
First, you will need to visit the [xCloud](http://hidden-hamlet-226309.wp1.sh) website and you have to sign up for xCloud with your credentials.
If you have already an account please visit our [**app URL**](https://app.xcloud.host/) below. Now you are ready to set up your server with Digital Ocean in xCloud.
### Step 2: Create Your New Digital Ocean Server In xCloud [#](/docs/how-to-setup-your-server-with-digital-ocean/)
After logging in to your xCloud account, start by adding a new server by clicking on the “**Add New Server**” button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a **Digital Ocean** server and for that select the [**Digital Ocean**](https://xcloud.host/go/digitalocean/) option. The billing of the server will be handled on your Digital Ocean account.
_Note: Don’t have a_ **_DigitalOcean_** _account? Check out the documentation below to find out how to provision a server with any providers_:
- [**How To Setup First Server With Vultr?**](/docs/how-to-get-free-hosting-with-vultr/)
- [**How To Setup Your First Server With Google Cloud Platform Provider?**](https://dev1.xcloud.host/docs/first-server-with-google-cloud-platform)
- [**How To Setup Server With Other Providers?**](https://dev1.xcloud.host/?post_type=docs&p=268&preview=true)
We’ve made it easier and safer for you to connect xCloud with your DigitalOcean account. You no longer have to go through the hassle of generating and copying access tokens. Now, xCloud will guide you through an OAuth flow, where you simply authorize xCloud to use your DigitalOcean account. All you have to do is provision a new DigitalOcean server, click “Authorize” during the setup, and you’ll be redirected to DigitalOcean to grant permission to your account. It’s a straightforward and hassle-free process to set up your server with Digital Ocean.
### **Step 3: Add Necessary Information** [#](/docs/how-to-setup-your-server-with-digital-ocean/)
You will be taken to the server creation page after successfully integrating your DO account. Now you need to provide the **Server name**, your preferred **Server Size** (CPU, RAM, storage), and the **Region** nearest to you and your visitors. Only, MySQL 8.0 database server is now available. By default Database, the **Root Password** is auto-filed but you can change this and save it in a safe place.
We recommend at least a 2GB/ 1 shared CPU server for 10-20 sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server.
We are almost done with our server creation of Digital Ocean in xCloud. After submitting the form, this might take up to 12-15 minutes to make the Digital Ocean server live and ready to install a lightning-fast WordPress Site.
## **How To Create A Site With xCloud** [#](/docs/how-to-setup-your-server-with-digital-ocean/)
After you have completed the previous steps of creating Digital Ocean server, you are now ready to create your site. Simply follow our step-by-step guide below.
### **Step 1: Create A Site From The Dashboard** [#](/docs/how-to-setup-your-server-with-digital-ocean/)
Once your server is connected, you can create a site from the Dashboard or Site List by clicking on the button “**Create New Site**”
Then you will need to select the server on which you want to install your WordPress website.
### **Step 2: Choose Your Site & Add Information** [#](/docs/how-to-setup-your-server-with-digital-ocean/)
As we will be creating a fresh WordPress site choose the “I**nstall New WordPress Website**” options as shown below.
Now all you have to do is install and Go Live with your WordPress Site. You can do the next process with 3 simple and easy steps.
1. Add a **Site Title**
2. Add **Tags** if you want
3. Choose to **Go Live**
4. **DNS Configuration:** If you add the domain and want to visit the live site you need to configure your DNS. xCloud does not handle your DNS but all you need to do is remove any existing A records and add the A record as shown above. For example, if your domain is on Cloudflare then all you need to do is add an A record with the domain name, and your server IP address.
**Note:** Make sure to turn off the proxy status as shown in the above image and also turn off the SSL/TLS. Otherwise, you might face conflicts and redirect loops if you enable this and also xCLoud’s Free SSL service.
To use a **Free SSL certificate** by **Let’s Encrypt** simply turn on the HTTPS enable button and xCloud will automatically set everything for you.
Facing issues with adding A records in your DNS provider? Read our documentation on DNS management for various domain providers from the [FAQ](https://xcloud.host/docs-category/faq/) section.
You can then simply hit the Next Button to create your site and **Go Live** instantly.
### **Configure Additional Settings** [#](/docs/how-to-setup-your-server-with-digital-ocean/)
By default, the WordPress admin credentials are autogenerated to speed up the site creation process. As soon as your site is deployed you will receive your Site credentials on your email address. Later on, you can update your password if needed. From “**More Advanced Settings**” you can update the default **Admin Username**, **Admin Password, Admin Email Address,** etc along with other additional settings from here.
After the previous step, click on the ‘**Next**’ button. It might take only 1-2 minutes to create your WordPress site.
That’s it! You’ve successfully created a site in xCloud. Now you can start working on your website, customize it, install themes/plugins (if applicable), and take advantage of xCloud’s optimized server environment for seamless site management.
### **Not Ready Yet? Try Staging Environment** [#](/docs/how-to-setup-your-server-with-digital-ocean/)
Also, If you do not want to point your domain yet then xCloud offers temporary domains to make your site live with every Site creation method available in xCloud. For that select the **Staging Environment** option. Later, after developing your site you can then easily make it Live by adding your domain in xCloud.
### Configure Your Email Server [#](/docs/how-to-setup-your-server-with-digital-ocean/)
For users on managed hosting services like Kinsta, WPEngine, Runcloud, and Cloudways, email providers like Office 365, GSuite, and MXroute are commonly used. If you are migrating from cPanel/Plesk, new email hosting is needed. xCloud doesn’t automatically include email setup for your sites. WordPress often requires reliable transactional email delivery, but default systems can fail, causing spam or delivery issues. Using services like Mailgun for efficient email delivery is recommended. The process of setting up and configuring Mailgun for WordPress can be found **[here](/docs/setting-up-site-emails-for-wordpress-on-xcloud/)**.
Still stuck? Contact our **support team** for any of your queries.
---
# How To Solve Automatic Site Backup Failures? - xCloud
> Solve automatic site backup failures and protect data from any loss like unintentional deletions, server malfunctions, and cyberattacks.
Site backups are important to protect data from any loss like unintentional deletions, server malfunctions, and cyberattacks. By keeping backups regularly, you can ensure that the content and functionality of your site can be restored.
With xCloud, you can store automatic site backup by following [**this doc**](/docs/site-backups-in-xcloud/). But, sometimes you may find trouble or failures in this process. Follow this guide to learn how to solve automatic site backup failures.
## Solve Automatic Site Backup Failures [#](/docs/how-to-solve-automatic-site-backup-failures/)
First, let’s learn the reasons behind this failure. With xCloud, you will get two website backup options: **Remote backup** (Storage providers like DigitalOcean, Vultr, etc) and **Local backup** (stored on the same server as the site). The automatic site backup failure occurs when
- Your xCloud server does not have enough space.
- The storage provider does not have enough space.
- The storage provider integration credential is not correct or has been updated.
Now, let’s look below and see how you can solve this failure.
## Check xCloud Hard Disk Storage [#](/docs/how-to-solve-automatic-site-backup-failures/)
From your xCloud dashboard, go to the **‘Monitoring’** tab. You can see the ‘**Hard Disk Usage**’ from the ‘**Server Health**‘ section. Check whether you have enough space on your server or not. You need the site size free space +1GB extra free space to keep the site back up on your xCloud server end. It means, if your site size is 10GB, you need 11GB of free space for backup. If you don’t have enough space, it means the hard disk is not enough for your site. You need a bigger server. For that, you need to upgrade your plan.
## Check Space Of The Storage Provider [#](/docs/how-to-solve-automatic-site-backup-failures/)
You have to check the usage of remote storage from the storage provider dashboard. Here, we are showcasing the procedure of **Vultr storage**. From the **Vultr** dashboard, go to the ‘**Products**’ tab. Now, click on ‘**Cloud Storage**’. From the ‘**Usage Data**’ tab, you can see the total usage in the ‘**Bandwidth**’ section. Check whether you have enough space on your server or not. If not, then you have to make some space for backup.
## Check Credentials Of The Storage Provider [#](/docs/how-to-solve-automatic-site-backup-failures/)
When you integrate any external storage provider like Ventr, DigitalOcean, etc with xCloud, you will have a credential for that. For any reason, if you reset the credentials, it will disconnect from xCloud. If you face automatic site backup failure, you can check the credentials to see whether the storage provider is connected properly or not with xCloud.
_**Note**: storage providers **Contabo** and **Min.io** are currently not supported within the xCloud platform._
That is how easily you can solve automatic site backup failures.
Still stuck? [**Contact our support team**](/contact/) for any of your queries.
---
# How to Troubleshoot Cancelled Subscriptions, Deleted Servers, and Refund Confusion With xCloud - xCloud
> Understand what to check when a server, backup service, add-on, or subscription was cancelled or deleted, but billing, renewal, invoice, or refund status is
Understand what to check when a server, backup service, add-on, or subscription was cancelled or deleted, but billing, renewal, invoice, or refund status is still unclear.
## Symptoms [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
Use this guide if you see one or more of these issues:
- You deleted a server but still see an invoice or payment record.
- You created the wrong server, deleted it, and want to know what happens to the charge.
- A backup service or add-on was activated and then cancelled.
- A subscription appears active after the server was removed.
- You expected a prorated refund but do not see it yet.
- You want to cancel the account but still have active servers, sites, or paid services.
## Before you start [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
- Confirm you are signed in to the correct xCloud team.
- Open the related **Server**, **Site**, **Billing**, **Team**, or **Settings** page in your xCloud dashboard.
- Keep a copy of the exact error message before retrying.
- If the issue affects a live production site, avoid repeated risky changes until you understand the cause.
## Step-by-step troubleshooting [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
### 1\. Check whether the server or add-on is still active [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
1. Go to your xCloud dashboard and select the correct team.
2. Open the **Servers** area and confirm whether the server is still listed.
3. Check any paid add-ons, such as managed backups, that may have been attached to the server.
4. If the server still exists, delete or deactivate the service only if you are sure you no longer need it.
### 2\. Review the invoice and billing timeline [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
1. Open the billing or invoices area in your account.
2. Compare the invoice date with the server deletion or service cancellation date.
3. Remember that some payments are created in advance for the billing period, while refunds may require billing-team review.
4. Do not create duplicate refund tickets for the same invoice; add details to the existing ticket if possible.
### 3\. Confirm whether the request is a refund, transfer, or cancellation [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
1. For a wrong server deployment, note whether you want a refund review or help creating the correct server.
2. For account cancellation, remove active servers first so future renewals stop.
3. For backup/add-on cancellation, confirm the add-on is disabled before requesting refund review.
4. For a payment transfer request, include the old and new service names without exposing card details.
### 4\. Wait for payment-gateway processing [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
1. After xCloud approves a refund, the gateway or card issuer may take additional time to return the amount.
2. Check your payment method statement after a few business days.
3. If the refund was approved but not visible after the expected gateway window, update the support ticket.
## What xCloud Support can check [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
- Verify whether the server, add-on, or subscription is still active.
- Review invoices and payment records available in xCloud.
- Forward eligible refund or prorated refund requests to the billing team.
- Confirm whether future renewals should stop after deletion/cancellation.
## What to send xCloud Support [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
- Team name and account email used in xCloud.
- Invoice number or billing reference.
- Server or add-on name, not sensitive payment-card details.
- Date and timezone when the server/add-on was deleted or cancelled.
- Whether you want refund review, cancellation confirmation, or help avoiding duplicate charges.
## Prevention tips [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
- Delete unused servers and deactivate unused add-ons before the next renewal date.
- Keep invoice records for every server or paid feature.
- Create the correct server/provider/plan carefully before deleting a paid server.
- Use one support ticket per billing case to avoid split context.
## How to read the result [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
After you review billing, the main goal is to separate three different situations: a cancelled renewal, a deleted service, and a refund request. A deleted server normally stops future use of that server, but it does not always mean every past invoice changes automatically. If a payment was already captured, the billing team may need to review the invoice, service dates, and cancellation timing before confirming the next step. If the request is approved, the payment gateway or card issuer may still need additional time before the amount appears on your statement. Keep the original invoice and support ticket open until the billing team confirms the case is complete.
## Expected result [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
After troubleshooting, you should be able to confirm one of these outcomes:
- The issue is resolved and the related site, server, billing item, integration, or team access works as expected.
- The dashboard shows a clear error that can be shared with xCloud Support.
- The issue is outside xCloud platform support and needs action from your developer, DNS provider, payment gateway, software vendor, or third-party service provider.
If the issue affects production, verify the public site and the xCloud dashboard after every major change. Keep screenshots of the before-and-after state so support can understand what changed.
## When to contact support immediately [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
Contact xCloud Support before continuing if:
- The issue affects a live production site or active customer portal.
- A server, database, billing item, or team owner setting may be permanently changed or deleted.
- You see repeated failures after one careful retry.
- You are unsure whether a root-level, database-level, DNS, or billing action is safe.
## FAQ [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
### Does deleting a server always create an automatic refund? [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
Not always. Deleting a server stops the active service, but refund eligibility can depend on timing, service type, invoice status, and billing policy. xCloud Support can route eligible cases for billing review.
### Can xCloud transfer a payment from one deleted server to another server? [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
In many cases this requires billing-team review. Share the old server, new server, invoice, and payment time so the team can confirm the safest option.
### Should I share card details in a support ticket? [#](/docs/how-to-troubleshoot-cancelled-subscriptions-deleted-servers-and-refund-confusion-with-xcloud/)
No. Never share full card numbers, passwords, or sensitive payment credentials. Invoice numbers and transaction references are enough.
---
# How to Troubleshoot Nginx Configuration Regeneration Failures With xCloud - xCloud
> Fix or report cases where Nginx configuration regeneration fails, Nginx cannot restart, or a site stays offline after domain, SSL, Docker, redirect, or rule
Fix or report cases where Nginx configuration regeneration fails, Nginx cannot restart, or a site stays offline after domain, SSL, Docker, redirect, or rule changes.
## Symptoms [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
Use this guide if you see one or more of these issues:
- The site is offline after changing domain, SSL, redirects, headers, Docker, or proxy settings.
- The dashboard shows an Nginx regeneration or restart failure.
- A custom app or Docker app cannot finish Nginx setup.
- A site returns 500 because cache, proxy, or vhost files are invalid or inaccessible.
- Nginx cannot start after a configuration update.
## Before you start [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
- Confirm you are signed in to the correct xCloud team.
- Open the related **Server**, **Site**, **Billing**, **Team**, or **Settings** page in your xCloud dashboard.
- Keep a copy of the exact error message before retrying.
- If the issue affects a live production site, avoid repeated risky changes until you understand the cause.
## Step-by-step troubleshooting [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
### 1\. Open the latest failed event [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
1. Go to the affected **Server** in xCloud.
2. Open **Events** or the site-level event history.
3. Find the most recent failed event related to **Regenerate Nginx Config**, **Restart Nginx**, **Deploy SSL**, or **Create Site**.
4. Open the event output and copy the exact error text.
(Screenshot: open the latest failed event in xCloud.)
### 2\. Check recent setting changes [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
1. Review changes made before the failure: domain update, redirect rule, custom header, SSL retry, Docker/Compose deployment, port change, or custom Nginx rule.
2. If the issue started after adding a rule, temporarily remove the new rule if the dashboard allows it safely.
3. Avoid editing server-level Nginx files manually unless you understand the impact.
### 3\. Review site logs and cache state [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
1. Open the site **Logs** page and check Nginx error logs.
2. Look for permission denied, missing file, duplicate directive, invalid directive, unsupported HTTP/3/QUIC directive, or upstream connection errors.
3. If the issue appears cache-related, disable page/FastCGI cache temporarily only as a recovery step, then report the root cause.
### 4\. Retry only after correcting the visible cause [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
1. After fixing DNS, SSL, redirect, or unsupported setting issues, retry the failed action once.
2. If the same event fails again, stop retrying and contact support with the event output.
3. For production sites, avoid repeated regenerate/restart attempts during high-traffic periods.
## What xCloud Support can check [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
- Inspect failed event output and Nginx error logs.
- Check whether generated config files, redirect/header files, cache ownership, or proxy rules are missing or invalid.
- Regenerate supported xCloud configuration when the cause is platform-generated config.
- Escalate product bugs or unsupported directives to engineering.
## What to send xCloud Support [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
- Server and site name.
- The exact dashboard event name and error output.
- What changed immediately before the failure.
- Whether the site is WordPress, custom PHP, Docker, Node.js, or another app type.
- Screenshots of the failed event and current domain/SSL/proxy settings.
## Prevention tips [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
- Make one Nginx-related change at a time and verify the site before changing more.
- Avoid unsupported custom Nginx directives unless confirmed by support.
- Keep custom redirects and headers simple.
- Check Docker/custom-app ports before connecting them through the proxy.
## How to understand the error [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
Nginx regeneration is a validation step. xCloud builds the server configuration for the site, tests whether Nginx accepts it, and then restarts or reloads the service. If any generated or custom rule is invalid, Nginx may reject the entire configuration to avoid loading a broken web server. This can happen after domain changes, SSL retries, redirect/header changes, Docker proxy updates, custom app ports, or unsupported directives. The exact event output matters because “Nginx failed” is only the final symptom. The useful clue is usually the missing file, duplicate directive, invalid directive, permission issue, or upstream/port error shown inside the event or log.
## Expected result [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
After troubleshooting, you should be able to confirm one of these outcomes:
- The issue is resolved and the related site, server, billing item, integration, or team access works as expected.
- The dashboard shows a clear error that can be shared with xCloud Support.
- The issue is outside xCloud platform support and needs action from your developer, DNS provider, payment gateway, software vendor, or third-party service provider.
If the issue affects production, verify the public site and the xCloud dashboard after every major change. Keep screenshots of the before-and-after state so support can understand what changed.
## When to contact support immediately [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
Contact xCloud Support before continuing if:
- The issue affects a live production site or active customer portal.
- A server, database, billing item, or team owner setting may be permanently changed or deleted.
- You see repeated failures after one careful retry.
- You are unsure whether a root-level, database-level, DNS, or billing action is safe.
## FAQ [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
### Can I edit Nginx files directly over SSH? [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
xCloud provides full root access and the root password where applicable, but direct Nginx edits can break future dashboard regeneration. For security, use SSH key-based login instead of password login and contact xCloud Support before risky production changes.
### Why did SSL or Docker setup fail with an Nginx error? [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
SSL, Docker, custom apps, redirects, and domains all depend on valid Nginx configuration. A failure in one generated block can prevent Nginx from restarting.
### Should I keep retrying the regenerate button? [#](/docs/how-to-troubleshoot-nginx-configuration-regeneration-failures-with-xcloud/)
Retry once after correcting the visible cause. If it fails again, send support the event output instead of repeatedly restarting Nginx.
---
# How to Troubleshoot Server Installation Failed (xCloud & Self-managed) - xCloud
> Getting self-managed server installation failed can be frustrating. But you can get rid of that if everything required gets done smoothly. Let us learn some
Getting self-managed server installation failed can be frustrating. But you can get rid of that if everything required gets done smoothly. Let us learn some tips on reducing errors and getting your server installed and running smoothly.
Server setups are usually contacted in multiple steps and show some progress with percentage and step number counts. Below are some common setup error conditions with percentages as the progress, so you can know where you are stuck. For example, if you are stuck at 11% that means you have not finished creating the server.
However, **[xCloud](/)** simplifies the overall process of showing progress, so you can easily know where you need to troubleshoot for errors and find a fix.
## **Troubleshooting Tips For Server Installation Failed** [#](/docs/how-to-troubleshoot-server-installation-failed-xcloud-self-managed/)
While installing the server with xCloud, you can see your progress with multiple steps by step. For example, there are 27 steps for creating the server. If you are stuck at step 2, it means something went wrong with creating a server on your provider (**[Vultr](https://www.vultr.com/)**, **[DigitalOcean](https://www.digitalocean.com/)**, and **[GCP](https://cloud.google.com/)**).
### **Check Your Ubuntu Version** [#](/docs/how-to-troubleshoot-server-installation-failed-xcloud-self-managed/)
xCloud is compatible with **Ubuntu 20.04 (LTS) x64** or **22.04 (LTS) x64**. Our platform is not compatible with a minimal edition or any alternative version of Ubuntu (a common inquiry we receive).
In case your chosen provider exclusively provides minimal images rather than the complete Ubuntu 20.04 LTS, you can opt for the minimal version installation. Subsequently, continue with the regular procedure.
### **Your Servers IP Address Has Been Banned by the Service Provider** [#](/docs/how-to-troubleshoot-server-installation-failed-xcloud-self-managed/)
This is an additional problem that may arise with your service providers, particularly if their pricing is significantly lower than that of most competitors. Verify that your server can establish a connection to our platform. If the issue persists and you do not receive basic HTML, reach out to your server provider to report the problem. Unfortunately, we are unable to assist in resolving this issue.
## **xCloud Server Installation Failed** [#](/docs/how-to-troubleshoot-server-installation-failed-xcloud-self-managed/)
To troubleshoot server installation issues with xCloud all you need to do is [**contact our support team**](/contact/). No matter in which section you’re facing errors while building an xCloud server: Creating, Connecting, & Configuring servers, our team is only a click away to help you.
### **Starting Over** [#](/docs/how-to-troubleshoot-server-installation-failed-xcloud-self-managed/)
We suggest to initiate the process with a new server. However, if you prefer to attempt resolving the issue on the existing server, you can follow these steps for a retry.
STEP 1: Begin by removing the server from the xCloud servers.
STEP 2: Re-add the server through the user interface.
If your server installation is still stuck, feel free to reach out to our support for assistance.
---
# How to Troubleshoot Site Backup Failures With xCloud - xCloud
> Learn how to troubleshoot site backup failures in xCloud step by step. Fix local and remote backup issues, storage limits, database errors, and provider settings quickly.
Site backups protect your files and database before updates, migrations, staging pushes, restores, and unexpected changes. When a backup fails, the cause is usually one of these areas: server disk space, database export, remote storage access, backup schedule/settings, or old backup jobs that need support review.
Read this guide to troubleshoot both local backups and remote backups in xCloud before opening a support ticket.
## What This Guide Covers [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
This guide helps when:
- A local site backup fails.
- A remote site backup fails.
- A manual backup fails.
- A scheduled backup does not run.
- Backup emails report failures even though backups look disabled.
- A backup fails with Database backup failed or MySQL database backup failed.
- A remote backup fails even though Google Drive, S3, R2, Backblaze, DigitalOcean Spaces, pCloud, or another provider has free space.
- Old backups are not deleted as expected.
- Incremental backups look missing or confusing.
- Global or bulk backup settings do not match the site-level settings.
This guide focuses on backup creation failures. If your backup was created successfully but the restore failed, follow the restore troubleshooting guide or contact xCloud Support with the restore error.
## Before You Retry [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Before running the backup again, collect the details that explain where the backup stopped.
1. Open the failed backup entry.
2. Copy the exact error message.
3. Check whether the backup was Local or Remote.
4. Check whether it was Manual or Scheduled.
5. Note the failed backup date and time with your timezone.
6. Check the server’s available disk space.
7. Check whether you recently changed the backup schedule, storage provider, bucket, folder, retention, or exclude paths.
8. Check whether the same remote provider works on another site.
## Step 1: Find the Failed Backup Entry [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Start from the backup history so you can identify what failed.
1. Log in to your xCloud Dashboard.
2. Open the affected Site.
3. Go to Backups.
4. Open Previous Backups or the backup history area.
5. Find the failed backup.
6. Review the backup type, destination, trigger, date, and error message.
Common errors include:
- Database backup failed
- MySQL database backup failed
- Not enough storage for backup
- Failed to fetch folder id
- Failed to add storage provider
- Missing database name or database password errors
- S3-compatible upload, bucket, endpoint, or permission errors
If the error changes after retrying, save both the original error and the new error. A provider error followed by a database error can mean the backup is failing at more than one stage.
## Step 2: Understand Local vs Remote Backup Failures [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Local and remote backups can fail for different reasons, but both may still depend on server storage and database export.
Backup type
Where the final backup is stored
Common failure points
Local backup
On the server
Server disk space, local backup retention, database export, stale local backup jobs
Remote backup
External storage provider
Server temporary space, provider credentials, folder/bucket access, endpoint/region, upload permissions, database export
A remote backup does not mean xCloud can skip local temporary files. xCloud must first create backup files on the server, then upload them to the remote provider.
## Step 3: Check Server Temporary Disk Space [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Many remote backup issues are actually server storage issues.
Before xCloud uploads a backup to Google Drive, S3-compatible storage, Cloudflare R2, Backblaze, DigitalOcean Spaces, pCloud, or another provider, the server needs temporary space to create:
- Database export files
- File archive files
- Compressed backup packages
- Backup metadata
- Temporary upload files
So a remote backup can fail even when your remote provider has plenty of free space.
For example:
Error detail
Meaning
Required: 8 GB | Available: 4 GB
The server does not have enough temporary space.
Required: 10 GB | Available: 3 GB
The remote provider may have space, but the server cannot prepare the backup.
Remote quota shows 2 TB free but xCloud reports low storage
Check the server’s free disk space, not only the remote provider quota.
To check storage:
1. Open the affected Server in xCloud.
2. Review disk/storage usage.
3. Check whether old backups, large uploads, cache files, logs, or temporary files are using space.
4. Review backup retention settings.
5. Free up space only when you know the files are safe to remove.
Do not delete unknown files or directories blindly. If you are not sure what is safe, contact xCloud Support or a qualified server administrator before cleanup.
## Step 4: Review Local Backup Settings and Retention [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Local backups use server disk space. If retention is not working as expected, old backups can fill the server and cause new backups to fail.
1. Open the affected Site.
2. Go to Backups → Backup Settings.
3. Review the Local Backup section.
4. Check whether local backup is enabled.
5. Check the schedule.
6. Check the retention or automatic delete setting.
7. Check whether old backups are still listed in Previous Backups.
Local backup storage issues may happen when:
- Old backups are not removed by retention rules.
- Backup retention was changed but old files remain.
- Local backup is disabled in the dashboard but a stale job still runs.
- Orphaned backup files remain on the server.
- A legacy backup job still creates files after settings were changed.
- Large folders are included because exclude paths were not applied.
If local backup is disabled but disk usage keeps growing, contact xCloud Support. Support may need to check backup jobs, cron entries, and backup directories safely.
## Step 5: Review Remote Backup Provider Settings [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Remote backups can fail because the provider connection, folder, bucket, endpoint, or permissions changed.
1. Open the affected Site.
2. Go to Backups → Backup Settings.
3. Open the Remote Backup section.
4. Confirm the selected provider.
5. Confirm the destination folder, bucket, or path.
6. Confirm the provider connection is still active.
7. Confirm the provider account has enough storage quota.
8. Confirm the provider credentials have read and write access.
9. Save the settings, then run a manual backup test.
Remote provider issues commonly come from:
- Expired or revoked tokens
- Changed folder permissions
- Deleted or renamed destination folders
- Wrong bucket name
- Wrong region or endpoint URL
- Read-only credentials
- Missing write permission
- Provider account quota limits
- Provider-side API outage
- IP restrictions on the storage token
## Step 6: Fix Failed to Fetch Folder ID [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Failed to fetch folder id usually means xCloud could not access or identify the configured remote folder.
This can happen when:
- The remote folder was deleted, renamed, or moved.
- The connected account no longer has access to the folder.
- The provider authorization expired.
- The selected folder path is no longer valid.
- The provider API returned a temporary error.
To troubleshoot:
1. Open the remote backup settings.
2. Reconnect the remote provider if needed.
3. Re-select the destination folder or bucket.
4. Confirm the connected account can open and write to that folder.
5. Save the settings.
6. Run a manual backup.
If the next failure changes from Failed to fetch folder id to Database backup failed, continue with the database section below. The backup may have moved past the provider check and then failed during database export.
## Step 7: Check S3-Compatible Storage Providers [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
S3-compatible storage includes providers such as Cloudflare R2, Backblaze, DigitalOcean Spaces, Wasabi, Hetzner Object Storage, OVH Object Storage, and other providers that use S3-style credentials.
If xCloud cannot add or use an S3-compatible provider, check:
- Access key
- Secret key
- Bucket name
- Region
- Endpoint URL
- Token permissions
- Bucket permissions
- Read/write access
- IP restrictions
- Provider account quota
- Provider status page
For errors like Failed to add storage provider, common causes include:
- The token has limited or read-only permission.
- The token is restricted to an IP address that does not match the request path.
- The endpoint URL was copied incorrectly.
- The bucket name is wrong.
- The bucket is in a different region.
- The bucket does not allow write access.
- The credentials belong to another provider account.
Recommended checks:
1. Copy the endpoint URL directly from the provider dashboard.
2. Confirm the bucket name exactly, including spelling and case.
3. Make sure the token has read and write access.
4. Remove unnecessary token IP restrictions while testing if your security policy allows it.
5. Confirm the provider account has available storage.
6. Try adding the provider again.
Do not send secret keys, access keys, passwords, or private tokens in plain text unless xCloud Support asks you to use a secure method.
## Step 8: Test a Manual Backup [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Manual backup testing helps separate a one-time schedule issue from an active backup failure.
1. Open the affected Site.
2. Go to Backups.
3. Choose the same backup type that failed: Local or Remote.
4. Start a manual backup.
5. Wait for the process to complete.
6. Open the failed entry if it fails again.
7. Save the exact error message.
Use the result this way:
Manual test result
What it means
Manual backup succeeds
The original issue may have been temporary or schedule-related. Monitor the next scheduled backup.
Manual backup fails with the same error
The issue is still active. Continue troubleshooting or contact Support.
Manual backup fails with a different error
Save both errors. The backup may be failing at multiple stages.
## Step 9: Troubleshoot Database Backup Errors [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
A site backup usually includes both files and database data. If the database export fails, the whole backup may fail.
Common database-related errors include:
- Database backup failed
- MySQL database backup failed
- Missing database name
- Missing or null database password
- Database connection error
- MySQL export error
- Empty database tables
- Database exists but cannot be exported
### If You See Database Backup Failed [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
1. Retry the backup once after a short wait.
2. Confirm the site is online.
3. Check whether the site was recently migrated, cloned, restored, or edited.
4. Check whether database credentials were changed.
5. Contact xCloud Support if the error repeats.
Sometimes a database backup failure works on retry. If it fails repeatedly, Support may need to review the database configuration and export logs.
### If the Database Name Is Missing [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
A missing database name usually needs support review. Contact xCloud Support and include the site name, server name, exact error, and whether the site was recently migrated, restored, or cloned.
### If the Database Password Is Empty or Null [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
A null or missing database password can stop the backup process from finding or exporting the database. Do not manually change database credentials unless you understand the effect on the site. Contact xCloud Support for a safe review.
### If the Database Has No Tables [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
If a database is empty, the database backup may fail or be skipped depending on the site state.
This can happen when:
- WordPress installation did not complete.
- A new site has no database tables yet.
- A migration or restore did not finish.
- The site is connected to a different database than expected.
Complete the WordPress installation or contact Support if the database should already contain tables.
## Step 10: Check Schedule, Global Settings, and Bulk Backup Updates [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Backup settings may exist at more than one level. If scheduled backups do not match what you configured globally or in bulk, check the site-level settings.
1. Open the affected Site.
2. Go to Backups → Backup Settings.
3. Review the site-level schedule.
4. Review the selected provider or local destination.
5. Review retention settings.
6. Review file backup exclude paths.
7. Compare the site-level settings with the global or bulk settings you expected.
8. Save the settings.
9. Run a manual backup test.
Check carefully when:
- Exclude paths were not copied from global settings.
- The wrong bucket or provider is selected after a bulk update.
- Scheduled backups stopped after changing settings.
- No backup notification was received.
- A site still uses an old storage provider.
- The dashboard says backups are inactive but remote backup emails continue.
If the settings look correct but the behavior is wrong, contact xCloud Support. This may need engineering review.
## Step 11: Check Incremental Backup Entries [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Incremental backups may appear under a parent full backup. If the child entries are collapsed, it can look like backups are missing.
1. Open the site’s Previous Backups.
2. Find the latest full backup.
3. Expand the full backup entry if an expand option is available.
4. Review the incremental backup entries under it.
5. Check the dates and times.
Contact Support if:
- The latest full backup is older than expected.
- Incremental backups are not listed.
- Backups are going to the wrong bucket or provider.
- The schedule does not match your settings.
- Manual backups work but scheduled backups do not.
## Step 12: Compare Failed Sites With Working Sites [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
If the same remote storage credentials work on one site but fail on another, compare the affected site with a working site.
Check:
- Server free disk space
- Site size
- Database status
- Backup type
- Selected provider
- Bucket, folder, endpoint, and region
- Backup schedule
- Retention settings
- Exclude paths
- Whether the site was recently migrated, cloned, or restored
- Whether the sites are on the same server
This helps identify whether the issue is provider-wide, server-specific, or site-specific.
## Step 13: Avoid Risky Manual Cleanup [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
If storage is full, cleanup may be needed, but removing the wrong files can break a site or remove the only usable backup.
Do not blindly delete:
- WordPress uploads
- Site directories
- Database files
- Backup metadata
- Server configuration files
- Unknown folders
- Files owned by system services
Avoid recursive delete commands unless you fully understand the exact path and impact.
xCloud provides full root access and the root password where applicable. For better security, xCloud recommends SSH key-based login instead of password login. Use root access carefully and avoid risky production changes unless you understand the impact.
If you are unsure, contact xCloud Support or a qualified server administrator before deleting backup-related files.
## Troubleshooting by Error or Symptom [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Error or symptom
Likely reason
What to do
Database backup failed
Database export failed.
Retry once, confirm the site is online, then contact Support if it repeats.
MySQL database backup failed
MySQL export failed during backup.
Save the exact error and contact Support if persistent.
Not enough storage for backup
Server lacks temporary space.
Free server disk space safely, check old backups, then retry.
Remote backup fails but remote provider has space
Remote backup still needs server temporary space.
Check server disk space, not only remote quota.
Failed to fetch folder id
xCloud cannot access the remote folder.
Reconnect provider, re-select folder/bucket, check permissions, retry.
Failed to add storage provider
Credentials, endpoint, bucket, token, region, or permissions are invalid.
Verify S3/provider settings and token permissions.
Failed S3 emails after disabling remote backup
Old config, stale job, another site, or notification issue may exist.
Check site-level settings and contact Support if emails continue.
Same provider works on other sites
Site/server-specific issue.
Compare settings, server disk, database status, and destination.
Old backups not deleting
Retention or orphaned file issue.
Do not delete unknown files; contact Support for safe review.
Incremental backups look missing
Entries may be collapsed under a full backup.
Expand the parent full backup and review child entries.
Scheduled backups do not follow settings
Site-level settings may differ from global/bulk settings.
Review site-level schedule, provider, retention, and exclude paths.
## What xCloud Support Can Check [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
xCloud Support can help review:
- xCloud backup settings
- Site-level backup configuration
- Backup history and visible backup errors
- Server storage usage
- Backup logs and events
- Local backup retention behavior
- Remote storage configuration guidance
- Stale or old backup jobs where support access is needed
- Cron-related backup issues where support access is needed
- Database configuration issues
- Missing database name or database password issues
- Repeated database export failures
- Orphaned backup files or backup cleanup issues
- Confirmed backup bugs that need engineering review
## What xCloud Support Cannot Guarantee [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
xCloud cannot guarantee recovery if no successful backup exists.
Remote storage providers can also have their own issues, including:
- API outages
- Quota limits
- Expired tokens
- Revoked credentials
- Bucket permission problems
- Endpoint or region changes
- Folder access changes
- Account restrictions
If the issue is inside the remote provider account, you may need to review that provider’s dashboard or contact the provider directly.
## What to Send xCloud Support [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
To help Support investigate faster, include:
- Site name
- Server name
- Whether the failed backup is Local or Remote
- Whether it is Manual or Scheduled
- Remote provider name, if used
- Exact error message
- Failed backup date and time
- Your timezone
- Screenshot of the failed backup
- Screenshot of backup settings
- Whether a manual backup also fails
- Whether the same provider works on other sites
- Recent changes to backup settings, schedule, provider, bucket, folder, or exclude paths
- Server free disk space, if visible
- Remote provider quota, if relevant
- Whether the site was recently migrated, cloned, restored, or changed
- Any database-related error text
Do not send secret keys, passwords, access keys, or private tokens in plain text unless Support asks you to use a secure method.
## Prevention Tips [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
- Keep enough free disk space on your server.
- Do not rely only on remote storage quota.
- Review backup retention settings regularly.
- Use exclude paths for large cache, temporary, or generated folders when appropriate.
- Test remote storage after changing credentials or tokens.
- Run a manual backup after changing backup settings.
- Check site-level settings after using global or bulk backup updates.
- Keep provider tokens active and correctly permissioned.
- Avoid read-only tokens for backup destinations.
- Monitor backup emails and dashboard backup history.
- Download critical backups before major cleanup.
- Contact Support before deleting unknown backup files from the server.
## FAQ [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
### Why does a remote backup need local server storage? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
xCloud must create the backup archive on your server before uploading it to the remote provider. If the server does not have enough temporary space, the remote backup can fail before upload.
### My Google Drive or pCloud account has enough space. Why did the backup fail? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Remote quota is only one part of the process. The server also needs enough temporary disk space to create the database and file archives before upload.
### Why did a database backup fail once and then work later? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
A temporary MySQL, server load, or export issue can cause a one-time failure. If the same database error repeats, contact xCloud Support.
### Why do I still receive remote backup failure emails after disabling remote backups? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
There may be stale backup configuration, an old scheduled job, another site using the same provider, or a notification issue. Check site-level backup settings and contact Support if emails continue.
### Why do the same S3 credentials work on one site but not another? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
The affected site may have different settings, server storage, bucket, endpoint, schedule, database configuration, or provider assignment. Compare it with a working site.
### Can xCloud clean up old backup files for me? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
xCloud Support can help investigate backup-related storage usage, retention issues, orphaned backup files, and stale backup jobs. Risky cleanup should be handled by Support or a qualified server administrator.
### Can xCloud recover my site if no successful backup exists? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
xCloud cannot promise recovery if there is no successful backup available. Keep regular local and remote backups and confirm they are completing successfully.
### Should I use root access to delete backup files manually? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Only use root access if you understand the impact. xCloud provides root access where applicable, but recommends SSH key-based login for security. If you are unsure, contact Support before deleting files.
### Why do incremental backups look missing? [#](/docs/how-to-troubleshoot-site-backup-failures-with-xcloud/)
Incremental backups may be collapsed under a parent full backup. Expand the full backup entry and check whether incremental entries are listed underneath.
---
# How to Troubleshoot SSL Issues Easily? - xCloud
> Fix SSL Issues on your website! Learn how to troubleshoot common SSL certificate problems & ensure a secure browsing experience for your visitors.
SSL issues occur when the security certificate used to encrypt communication between a website and your browser malfunctions. An SSL issue can prevent visitors from trusting your site. [**Fixing these SSL errors**](/docs/how-to-fix-a-failed-free-ssl-issue/) is often easier than you think. Let us explore this guide to understand which SSL issues you may encounter and how to troubleshoot SSL.
## **What Is an SSL Certificate?** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
Imagine a secure tunnel protecting sensitive information as it travels between your web browser and a website. That is the role of an SSL certificate, which encrypts data to keep it safe from prying eyes.
## **Types of SSL Certificates You Can Use in xCloud** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
There are three main options for managing your SSL certificate:
1. **Free SSL Certificate Issued And Managed by xCloud**
This is the simplest option, ideal for those just getting started with SSL. xCloud will handle the entire process of obtaining and renewing your certificate without any cost.
2. **Provide Owned Certificate And Manage It Yourself**
If you choose to provide your own certificate, you will need to paste your SSL certificate and private key on your xCloud server to install the Certificate. This option offers more control over your certificate configuration but requires more technical knowledge to set up and maintain.
3. **Use Cloudflare Managed SSL Certificate**
If you’re already using **[Cloudflare](https://www.cloudflare.com/)** for your website, you can use their managed SSL certificate in your xCloud hosting. This provides a good balance between ease of use and control.
No matter which option you choose, it is important to be familiar with potential SSL issues and how to troubleshoot them. In the next section, we’ll explore common SSL problems and steps you can take to resolve them.
## **How to Check for SSL Issues?** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
There are two ways to identify SSL certificate issues in xCloud:
1. **Using an SSL Checker Tool:** Several online tools can analyze your SSL certificate and identify any problems. These tools are usually free and easy to use. Just search for ‘**SSL checker tool**’ on your preferred search engine.
2. **Diagnosing SSL Failures:** Navigate to your xCloud dashboard and access the **SSL** option. This section will display any existing SSL certificate issues for your applications. Check the **SSL Renewal** expiration date in xCloud regarding upcoming SSL certificate renewals or potential failures if expired.
## **Common SSL Errors And Solutions:** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
Let us explore the most common SSL issues and how to fix them.
### 1\. **DNS Is Not Pointing to Your Server’s IP Address** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
Your website visitors are sent to the wrong location because your domain name isn’t properly directed to your server’s IP address.
#### **How to Fix:** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
Verify that your domain name servers (DNS) are correctly configured to point to your xCloud server’s IP address. You can manage your DNS records through your domain registrar’s control panel.
### **3**. Too Many Redirects Errors**:** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
Conflicts between the Cloudflare and xCloud configurations or errors in the Cloudflare settings are frequently the cause of the **ERR\_TOO\_MANY\_REDIRECTS** issue. Since Cloudflare functions as a reverse proxy, you must enable proxy settings from either xCloud or Cloudflare.
#### **How to Fix:** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
- Turn off HTTPS from xCloud if you intend to use the Cloudflare proxy. Navigate to the SSL/HTTPS tab on the xCloud dashboard to disable it.
- Turn off the HTTPS option now, then select “OK” from the confirmation window. You can follow this [**Cloudflare troubleshooting documentation**](/docs/troubleshooting-cloudflare-issues-for-wordpress/) for more details.
### 3\. **The NET::ERR\_CERT\_INVALID Error** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
This error message, which usually appears in Chrome and is similar in other browsers, means that the browser does not trust the SSL certificate in your website.
There are a few reasons for this Error:
**Expired Certificate:** SSL certificates have an expiration date, usually within a year. This error will appear if the certificate has expired.
**Mismatched Certificate:** The domain name that users are attempting to access may not be the one for which the certificate was issued.
**Untrusted Certificate Authority:** This error appears if the browser does not recognize the certificate authority that issued the SSL certificate.
#### **How to Fix:** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
- Check the expiration date on the certificate and renew it if required. The majority of hosting companies give automated SSL certificate renewals. xCloud hosting offers a free SSL certificate with a renewal.
- Make sure the domain name, including any subdomains, exactly matches the certificate.
### 3\. **WordPress Site HTTP to HTTPS Redirect Not Working** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
If your site is not automatically redirecting from HTTP to HTTPS, you will need to configure it.
#### **How to Fix:** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
xCloud hosting comes inbuilt HTTPS Option. Enable it by toggling on the button from your SSL/HTTPS setting menu.
## **Additional Tips** [#](/docs/how-to-troubleshoot-ssl-issues-in-wordpress/)
- **Clear Browser Cache:** Sometimes, cached data can cause problems. Clear your browser cache and try again.
- **Check System Date and Time:** An incorrect system date and time can lead to SSL errors. Ensure your computer’s date and time settings are accurate.
Now, you can effectively troubleshoot SSL issues and ensure your website visitors have a safe and secure browsing experience by following these steps.
If you need further help [**contact xCloud support**](/contact/). Our team always welcomes you to assist you further.
---
# How To Enable Cloudflare Under Attack Mode With xCloud - xCloud
> Learn how to enable Cloudflare Under Attack mode directly from your xCloud dashboard to protect your website from DDoS attacks in just a few clicks.
If your website is experiencing a sudden spike in malicious traffic or a DDoS attack, every second counts. Cloudflare’s Under Attack mode is a powerful defensive tool that can help protect your site during these critical moments. In this guide, we’ll walk you through how to quickly enable it directly from your xCloud dashboard — no need to log into Cloudflare separately.
Cloudflare’s Under Attack mode performs additional security checks to help mitigate layer 7 DDoS attacks. Validated users can still access your website, while suspicious traffic is blocked. It is designed to be used as a last resort when your site is under attack, and will temporarily pause access to your site and may impact your site analytics.
With xCloud, you can enable Cloudflare Under Attack mode right from the xCloud dashboard.
## Step 1: Go to the Tools Options [#](/docs/how-to-turn-on-cloudflare-under-attack-mode/)
First, go to your site dashboard. From there, navigate to **Tools → Nginx and Security** in your xCloud dashboard.
## Step 2: Enable Under Attack Mode [#](/docs/how-to-turn-on-cloudflare-under-attack-mode/)
Go to the **Cloudflare Under Attack Mode** section. Once you are there, toggle the button to enable it and click the **Save Settings** button.
After enabling the feature, if you visit the Cloudflare dashboard and open your domain’s settings, you will see that Under Attack mode is active and working.
That’s all it takes. With just a few clicks in your xCloud dashboard, you can activate Cloudflare’s Under Attack mode and add an extra layer of protection to your site during a DDoS attack. Remember that this mode is meant for active threats — once the attack subsides, turn it off so your visitors can access your site without the additional security challenge.
---
# How to Understand Deleted Server Billing With xCloud - xCloud
> Deleting a server can affect billing, but the result depends on the server type, invoice timing, subscription status, and whether the charge came from xCloud
Deleting a server can affect billing, but the result depends on the server type, invoice timing, subscription status, and whether the charge came from xCloud or an external provider. This guide explains the common billing situations after server deletion and what xCloud Support can review.
For the official refund rules, always refer to the [xCloud Refund Policy](https://xcloud.host/refund-policy).
## Quick answer [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Situation
What usually happens
xCloud Managed Server deleted before next billing cycle
Eligible for pro-rated refund based on actual usage
xCloud Provider Server deleted before next billing cycle
Eligible for pro-rated refund based on actual usage
Full Server Backup for Managed/Provider Server
Follows the same pro-rated usage/refund rules
Self-Managed Hosting / BYOS purchased through xCloud
Full refund within 14 days of purchase for new servers
External provider server bill
Handled by the provider, not xCloud
Addons after activation
Non-refundable once activated
Invoice already generated before deletion
May still appear as a billing record; Support can review eligible rows
## Why this can feel confusing [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Customers often see confusion after deleting a server because several things can happen at nearly the same time:
- the server is deleted from the dashboard,
- the subscription is cancelled or scheduled not to renew,
- an invoice was already generated before deletion,
- payment was already captured,
- the invoice contains multiple bill rows,
- one row is refundable but another row is still valid,
- a backup/addon row follows different rules,
- a provider invoice arrives separately from an xCloud invoice.
The key point is: **server deletion, invoice visibility, refund eligibility, and external provider billing are separate checks.**
## Server deletion vs invoice record vs refund [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
### Server deletion [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Server deletion removes the server from active use in xCloud. It may also stop the related xCloud subscription from renewing, depending on the service type.
### Invoice record [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
An invoice is a billing record. It may remain visible even if a refund, credit, or adjustment is later applied. Seeing an invoice after deletion does not always mean the charge is still active.
### Refund review [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Refund review checks whether unused paid time remains and which invoice line items are eligible under the refund policy.
## xCloud Managed Servers and xCloud Provider Servers [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
If you delete an **xCloud Managed Server** or **xCloud Provider Server** before the next billing cycle, you may be eligible for a **pro-rated refund** based on actual usage.
Official policy notes:
- You pay for the time the server was used.
- The unused portion can be reviewed for refund.
- A minimum charge of **one full day** applies if the server was used for less than 24 hours.
- Stripe processing fees, up to **10%**, may be deducted.
- Approved refunds are processed to the original payment method.
- Approved refunds usually take **5–10 business days**, depending on banking/payment processing time.
- Refunds are calculated in **USD**.
## Pro-rated refund formula [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
The official refund policy uses this structure:
```
Total paid − usage charge − processing fee = refund amount
```
Copy to Clipboard
Example only:
```
Monthly server charge: $100
Billing period: 30 days
Used time before deletion: 15 days
Usage charge: $50
Processing fee: deducted where applicable
Refund: remaining unused amount after usage and processing fee
```
Copy to Clipboard
The final amount depends on the real invoice, deletion time, service period, related bill rows, and applicable fee.
## Full Server Backup after server deletion [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Full Server Backup for xCloud Managed Servers and xCloud Provider Servers follows the same pro-rated logic. You pay for backup time used, and the unused portion can be reviewed for refund after applicable processing fees.
This applies to the full server backup service connected to Managed/Provider Servers. It does not make all addons refundable.
## Self-Managed Hosting / BYOS after deletion [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Self-Managed Hosting / BYOS purchased through xCloud is eligible for a **full refund within 14 days of purchase** for new servers.
Important notes:
- Refund requests are eligible only within the first 14 days of purchase.
- The 14-day refund applies to new servers.
- Requests after 14 days are not eligible.
- Recurring charges and cancellations after 14 days are not eligible for refunds.
- Deleting your server automatically cancels the related subscription, so it will not be charged in the next billing cycle.
## External provider billing after deleting a self-managed server [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
If you connected a server from an external provider account, such as Hetzner, Vultr, DigitalOcean, AWS, or another provider, xCloud does not control that provider invoice.
Removing the server from xCloud may disconnect it from the xCloud panel, but you should still check the provider dashboard for active billable resources, such as:
- servers,
- volumes,
- backups,
- snapshots,
- reserved IPs,
- load balancers,
- other provider services.
If the provider charged you directly, the provider must review that refund request.
## Addons after server deletion [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Addons are non-refundable once activated. This includes:
- Mailbox,
- Mail Delivery,
- Site Security PRO.
If an invoice includes both a refundable server row and a non-refundable addon row, Support may review only the eligible server row. The whole invoice is not automatically refunded.
## Why only part of an invoice may be refunded [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
One invoice can include several bill rows. For example, the same invoice may include:
- a managed server charge,
- a server resize adjustment,
- a full server backup row,
- an addon row,
- another server charge,
- a previous unpaid amount.
Only eligible rows are reviewed for refund. This is why Support may ask for a specific **bill ID** or line item ID instead of refunding the entire invoice.
## Step-by-step: check deleted server billing [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
### 1\. Identify the server type [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Confirm whether the deleted server was:
- xCloud Managed Server,
- xCloud Provider Server,
- Self-Managed Hosting / BYOS purchased through xCloud,
- external provider server connected to xCloud.
### 2\. Open the invoice [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Open the invoice that still shows the charge. Check the invoice ID, payment status, service period, and each bill ID.
### 3\. Match each bill row to a service [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Do not assume the full invoice belongs to the deleted server. Match each row to the server, backup, addon, reseller plan, or another service.
### 4\. Check the deletion or cancellation date [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
The billing team uses the deletion/cancellation date to calculate unused time for eligible Managed/Provider Server refunds.
### 5\. Check external provider resources if needed [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
If the charge came from an external provider, open the provider dashboard and verify whether the provider-side server or other resources are still active.
### 6\. Contact xCloud Support [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Ask Support to review the billing and include the exact invoice details listed below.
## What xCloud Support can check [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
xCloud Support can review:
- whether the deleted server was Managed, Provider Server, BYOS, or external provider-connected,
- invoice ID and bill IDs,
- deletion/cancellation date,
- eligible pro-rated refund for Managed/Provider Servers,
- eligible 14-day BYOS refund cases,
- full server backup refund eligibility,
- addon rows that are non-refundable,
- whether a refund or credit was already applied,
- whether the charge appears to be from xCloud or an external provider.
## Important data warning [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Deleted server data may not be recoverable unless a valid backup exists. Billing review does not restore deleted server data. If you need a site or server recovered, contact Support immediately and provide the server/site details.
## What to send xCloud Support [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Include:
- xCloud account email,
- invoice ID,
- bill ID or line item ID,
- server name,
- server type,
- deletion/cancellation date,
- purchase date for BYOS 14-day refund cases,
- screenshot of invoice rows,
- screenshot of provider invoice if you are unsure who charged you,
- expected refund or correction,
- whether you also had full server backup or addons enabled.
## FAQ [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
### Does deleting an xCloud Managed Server give a pro-rated refund? [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Yes. xCloud Managed Servers are eligible for pro-rated refunds before the next billing cycle, based on actual usage and the official refund policy.
### Does deleting an xCloud Provider Server give a pro-rated refund? [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Yes. xCloud Provider Servers follow the same pro-rated refund rule before the next billing cycle.
### Why do I still see an invoice after deleting a server? [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Invoices are billing records. An invoice may remain visible even after a refund, credit, or adjustment is processed.
### Why did Support say only some bill IDs are refundable? [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Because one invoice can include multiple services. Only eligible bill rows are reviewed for refund.
### Does deleting a self-managed server from xCloud cancel my external provider bill? [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
Not always. If the server exists in your external provider account, you must check and cancel it from the provider dashboard.
### Are addons refunded after deleting the server? [#](/docs/how-to-understand-deleted-server-billing-with-xcloud/)
No. Addons are non-refundable once activated, even if a related server is later deleted.
---
# How to Update Server Name in xCloud? - xCloud
> Learn how to update server name in xCloud and set any name as your preferences easily from the xCloud dashboard.
xCloud allows you to rename or update server name from the dashboard. Follow this step-by-step guide below to learn how you can easily do it.
## Step-by-Step Guide: How to Update Server Name in xCloud [#](/docs/how-to-update-server-name-in-xcloud/)
To update server name in xCloud, first, visit the **Server** you want to update and go to the **Metadata** section from the navigation bar. Here, you can change the server’s name to whatever you prefer and save your changes.
**_Note:_** _Keep in mind that if you are using your own provider, this update will only reflect within the xCloud platform and not on your provider’s end. This means the server name will remain unchanged on your provider’s side, but you will see the new name in xCloud._
This is how easily you can update the server name in xCloud and set any name as your preferences from the xCloud dashboard.
---
# How to Update SSH Port in xCloud? - xCloud
> Strengthen your server's security through update SSH port in xCloud. Learn how to configure your firewall & follow step-by-step guide for a secure setup.
The SSH port is the doorway you use to connect to your server securely. Changing the default port (22) adds an extra layer of security. This documentation will show how to update SSH port on your [**xCloud**](/) server using the terminal and xCloud Graphic User Interface (GUI).
## **Preparations: Before You Update SSH Port** [#](/docs/how-to-update-ssh-port-in-xcloud/)
Before updating ports check and prepare the following things:
- **Allow the port on your firewall:** You will need to configure your firewall to allow access to the new port you choose. See our guide on [**How to Configure Firewall Management in xCloud**](/docs/how-to-configure-firewall-management-in-xcloud/) for detailed instructions.
## **Update the SSH Port Using Terminal** [#](/docs/how-to-update-ssh-port-in-xcloud/)
We will be using the command line to update the SSH port, this method involves directly editing the SSH configuration file and restarting the service as a **sudo user**. Follow the step below to update the SSH port using Terminal.
### **Step 1: Open Terminal** [#](/docs/how-to-update-ssh-port-in-xcloud/)
Open the Terminal and navigate to the SSH configuration file by running the following command with nano: “**sudo nano sshd\_config**“
### **Step 2: Update the Port Number** [#](/docs/how-to-update-ssh-port-in-xcloud/)
Look for the line that reads **#Port 22**. The # symbol indicates a comment, and the actual port number is 22 (the default). Remove the #symbol and replace **22** with your desired port number. For example, if you want to use port **2222**, the line should look like this:
Once you have updated the port number, save the changes in your text editor (usually by pressing **Ctrl+O** followed by Enter). Then, exit the editor (typically with **Ctrl+X**).
### **Step 3: Restart SSH Service** [#](/docs/how-to-update-ssh-port-in-xcloud/)
Run the following command in the Terminal to restart the SSH service and apply the new port configuration: “ sudo service ssh restart ”
Congratulations! You’ve successfully updated the SSH port on your server using the Terminal. Now you have to update it on the xCloud web GUI.
## **Update SSH Port Using xCloud Web GUI** [#](/docs/how-to-update-ssh-port-in-xcloud/)
Now, we will be updating the SSH port in the xCloud web GUI part. Follow the steps shown below and update your SSH port accordingly.
### **Step 1: Go to SSH Configuration Settings** [#](/docs/how-to-update-ssh-port-in-xcloud/)
From your xCloud dashboard, go to **‘Servers**’ and select a server to navigate settings. Click on ‘**Others**’ from the settings menu. Here Update the SSH port Number and click on ‘**Save Settings**’.
### **Step 2: Add a Rule in Firewall Management** [#](/docs/how-to-update-ssh-port-in-xcloud/)
Now add a SSH Port Rule in your firewall management. To do that navigate from the server overview page go to the ‘**Security**’ menu and click one ‘**Add New Rule**’ button.
Here, Add your Rule name as **SSH** and add the decided port number. Then click on **‘Add Rule**’ to successfully update the SSH port in xCloud.
Following these steps, you can successfully update your SSH port on your xCloud server. Remember to choose a strong, non-standard port number and adjust your firewall settings accordingly for optimal security.
Still need help with updating your SSH Port? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Upgrade Nginx to the Official nginx.org Build - xCloud
> xCloud can now move an existing Nginx server from the deprecated Ondřej/Ubuntu package source to the official nginx.org build in one click, straight from your
xCloud can now move an existing Nginx server from the deprecated Ondřej/Ubuntu package source to the official nginx.org build in one click, straight from your server dashboard. The Ondřej PPA that xCloud previously relied on is being deprecated and no longer ships new Nginx releases, which left servers on it stuck on older versions.
This upgrade moves you to the officially maintained nginx.org build so your server stays current, and it rebuilds the modules xCloud depends on (headers-more for custom headers/Web Rules, and brotli compression) so you lose none of the functionality your sites already use. You also gain newer capabilities like HTTP/3.
The upgrade is designed to be safe by default. Your existing Nginx keeps serving traffic the entire time, xCloud validates your configuration before it starts, and if the final check or module build fails it automatically rolls back and leaves your original Nginx running. It runs in the background and usually finishes in a few minutes, without you needing to run any server commands manually.
This guide is for server owners and admins on Ubuntu 24.04 who want newer, supported Nginx releases, and it covers what the upgrade does, how to run it, and what to expect at each step.
Follow the steps below:
## Prerequisites / required permissions [#](#prerequisites--required-permissions)
Requirement
Details
Server stack
Nginx-based server. OpenLiteSpeed servers are not offered this upgrade.
OS version
Ubuntu 24.04.
Current Nginx source
The server must not already be marked as using the official nginx.org source.
Server state
The server must be provisioned and connected.
Permission
The user must be allowed to manage server services for the server’s team.
Recommended prep
Back up sites before starting the upgrade, especially if the server has custom Nginx snippets.
### Step 1: Open the eligible server [#](#step-1-open-the-eligible-server)
Open the server dashboard for an eligible Nginx server. xCloud shows an upgrade banner near the top of the server page.
### Step 2: Review what the upgrade will do [#](#step-2-review-what-the-upgrade-will-do)
The confirmation modal explains the upgrade plan before anything is queued. If the information looks correct, choose **Upgrade Nginx**.
### 3\. Resolve pre-flight warnings when custom config is incompatible [#](#3-resolve-preflight-warnings-when-custom-config-is-incompatible)
Before queuing the upgrade, xCloud scans custom Nginx config for directives that are known to break on newer official Nginx builds. If it finds blockers, the modal switches to an incompatibility view.
If you intentionally want to proceed, type the server name in the confirmation field and select **Upgrade anyway**. The rollback gate still protects the server if the final config test fails.
### Step 4: Let the upgrade run in the background [#](#step-4-let-the-upgrade-run-in-the-background)
After the upgrade is queued, the banner changes to a running state.
### Step 5: Confirm completion [#](#step-5-confirm-completion)
When the upgrade completes successfully, xCloud shows a success banner.
## Limits / edge cases [#](#limits--edge-cases)
- The offer is only shown for provisioned Nginx-based servers on Ubuntu 24.04 that are not already on the official nginx.org source.
- OpenLiteSpeed servers are intentionally excluded.
- xCloud blocks automatic package restart during the swap and performs one final reload only after the generated configuration passes `nginx -t`.
- If the final config test or module build fails, xCloud rolls back and leaves the existing Nginx serving traffic.
- Pre-flight issues do not make the upgrade impossible, but they should be fixed first unless you are intentionally relying on rollback protection.
## Frequently Asked Questions [#](#frequently-asked-questions)
### What is this upgrade? [#](#what-is-this-upgrade)
This is xCloud’s guided move from the older Ondřej/Ubuntu Nginx package source to the official nginx.org build. xCloud handles the repository change, rebuilds compatible `headers-more` and brotli modules, and keeps xCloud features such as Web Rules/custom headers and brotli compression available after the upgrade. It also enables newer Nginx capabilities such as HTTP/3.
### Was my server vulnerable earlier? [#](#was-my-server-vulnerable-earlier)
No customer action is needed for earlier exposure. xCloud already mitigated the relevant vulnerability immediately with targeted package and security fixes. This guided upgrade is the long-term package-source transition; it does not mean customer sites were left exposed until now.
### Why did xCloud not update earlier? [#](#why-did-xcloud-not-update-earlier)
Moving to the official nginx.org packages was a large platform change. xCloud previously used the Ondřej package source because it included modules and features xCloud needed. The official nginx.org package does not include every xCloud-required module out of the box, so xCloud needed to rebuild and support missing pieces such as `headers-more` and brotli, add compatibility checks, add rollback behavior, and verify the flow carefully before offering it on customer servers.
### Should I back up my sites first? [#](#should-i-back-up-my-sites-first)
A backup is recommended, but it is not required for the upgrade to run. xCloud keeps the current Nginx serving during the build and rolls back if the final config test or module build fails. A recent backup is still a good precaution and helps you recover faster if the server has unrelated site issues, custom Nginx snippets, or manually edited configuration.
### Does this restart Nginx during the build? [#](#does-this-restart-nginx-during-the-build)
No. Existing Nginx continues serving sites while xCloud prepares the repository and compiles compatible dynamic modules. xCloud blocks automatic package restarts during the swap and performs a single `nginx -t`\-gated reload at the end.
### What happens to `headers-more` and brotli? [#](#what-happens-to-headersmore-and-brotli)
xCloud rebuilds them as compatible dynamic modules for the official nginx.org build, so custom headers/Web Rules and brotli compression remain available after the upgrade.
### Can I leave the page after starting? [#](#can-i-leave-the-page-after-starting)
Yes. The upgrade is queued and runs in the background. The banner reflects the current status when you return.
### What should I do if pre-flight warnings appear? [#](#what-should-i-do-if-preflight-warnings-appear)
Fix the listed custom Nginx config first whenever possible. If you proceed anyway, xCloud still uses the final config test and rollback path to avoid leaving the server on a broken Nginx build.
### What happens if I dismiss or ignore the banner? [#](#what-happens-if-i-dismiss-or-ignore-the-banner)
Dismissing the banner disables the upgrade banner for that server. If you need it again, contact support, or start the same upgrade from the server’s **Management Settings** page when the server is still eligible.
### Where else can I start the upgrade? [#](#where-else-can-i-start-the-upgrade)
For eligible servers, xCloud also shows an **Upgrade Nginx** action in the server’s **Management Settings** service list. The action opens the same confirmation and pre-flight flow as the dashboard banner.
---
# How to Install, Upgrade PHP Version & Customize PHP Settings With xCloud Hosting? - xCloud
> Here you can learn how to upgrade PHP version with xCloud hosting.
Managing PHP versions and settings is an important part of maintaining a fast, secure, and compatible website. With xCloud Hosting, you have complete control over installing, upgrading, and customizing PHP to meet your website’s specific requirements.
Whether you need the latest PHP features, compatibility with older versions, or optimization for performance, xCloud allows a single interface to manage it all. Follow the steps to Install, Upgrade, & Customize PHP Settings with xCloud
## **PHP Configuration for Server** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
If you want to keep default settings for your server so that all sites created under it use the same configuration, you can set a default PHP configuration for that server. When a site is created under that server, it will automatically use those settings.
## **Step 1: Install a PHP Version** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
First, go to your Server from the xCloud dashboard. Then navigate to the **‘Management’** →**‘PHP Configuration’** to access all the available PHP versions and manage them easily.
Under the **‘PHP Version Configurations’,** get access to all available PHP versions. Choose the **‘PHP Version’** and click on the **‘Install’** button beside the version that you want to install.
## **Step 2: Set a Default PHP Version** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
Next, to keep your installed PHP version default, simply click on the **‘Set As Default’** button and the preferred version will be set as default.
## **Step 3: Configure PHP Settings** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
You can now easily customize your PHP as well. Just click on the three dot icon beside the version you have installed or set as default or want to configure. The following options can be modified:
1. **Max Execution Time**
2. **Max Input Time**
3. **Memory Limit**
4. **Max File Upload Size**
5. **Max Input Vars**
6. **Post Max Size**
7. **Session GC Maxlifetime**
Customize the options according to your preferences and click on the ‘Save Changes’ button.
## **Step 4: Enable OPCache** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
Enabling OPcache can significantly improve the efficiency of your PHP applications. To enable OPCache, just go to the **‘OPCache’** column from the dashboard and toggle the button to enable OPCache with just one click.
_Note: In PHP 8.5, OPcache is enabled automatically and cannot be enabled or disabled from the xCloud dashboard._
## **PHP Configuration for Sites** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
With xCloud, you can also manage your site’s PHP settings separately. Just go to your site, navigate to the **‘Site Settings’** option in the sidebar. You can manage your PHP settings for these sites easily.
👉 To learn more about PHP settings for your site**,** read this [**documentation**](/docs/how-to-configure-php-settings/)
## **Currently Supported PHP Version in xCloud Hosting** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
With xCloud Hosting, you can select from a wide range of PHP versions to match your website’s specific needs, whether you require compatibility with older versions or want to leverage the latest features. Here’s an overview of the supported PHP versions based on the server stack and configuration:
### **PHP Versions for NGINX Servers:** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
- Ubuntu 22.04.5 LTS: PHP 5.6 to PHP 8.5
- Ubuntu 24.04 LTS: PHP 8.1, PHP 8.2, and PHP 8.5
### **PHP Versions for OpenLiteSpeed (OLS) Servers:** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
- Ubuntu 22.04.5 LTS: PHP 7.4 to PHP 8.2
- Ubuntu 24.04 LTS: PHP 8.1, PHP 8.2, PHP 8.3 and 8.4
### **ARM Servers:** [#](/docs/how-to-upgrade-php-version-with-xcloud-hosting/)
- Ubuntu 24.04 LTS (OLS stack): PHP 8.3
You can now also add and connect freshly installed Ubuntu 24.04 LTS x64 servers from any provider to xCloud, with full support for both NGINX and OLS stacks. This ensures broad compatibility and flexibility across various server setups.
If you encounter any difficulties, feel free to reach out to our support team for assistance.
---
# How to Upgrade to 22.04 from 20.04? - xCloud
> A quick explanation on how to upgrade to 22.04 from 20.04 using xCloud.
Wondering how you can upgrade to 22.04 from 20.04? The easiest way to move your websites is to create a new server in xCloud with the 22.04 version and then use our full server migration feature to clone all of your websites on the new server.
---
# How to Upgrade xCloud Lifetime Deal Package - xCloud
> Learn how to quickly choose and pay for an xCloud Team Plan upgrade to boost your team’s productivity.
Upgrading your xCloud Team Package allows you to access more features, add team members, and enhance your overall cloud experience. Follow the steps to seamlessly upgrade your plan and continue enjoying the benefits of xCloud.
## **Step 1: Go to Bills & Payment** [#](/docs/how-to-upgrade-xcloud-lifetime-deal-package/)
From your xCloud Dashboard, click on **“Bills & Payment”** in the top bar menu.
## **Step 2: Access Team Packages** [#](/docs/how-to-upgrade-xcloud-lifetime-deal-package/)
From the sidebar menu, navigate to **Bills & Payment → Team Packages**. Once there, click on the **“Upgrade”** button.
## **Step 3: Choose a Plan to Upgrade** [#](/docs/how-to-upgrade-xcloud-lifetime-deal-package/)
Select your preferred plan and then click on **“Upgrade Now & Pay”** to proceed with the payment.
And that’s is how easily you can upgrade your existing lifetime deal pack easily in just a few clicks.
---
# How To Upgrade Your Server in xCloud? - xCloud
> with xCloud you can upgrade your server over virtual server.
[**xCloud**](http://hidden-hamlet-226309.wp1.sh/) is a cloud-based server management tool that gives you control to upgrade your server over your virtual servers. While you have the power to make changes, it’s essential to understand when and how to do it wisely.
xCloud has just rolled out a handy new feature called Upgrade Server. Now, with just a single click, you can easily switch to a higher-tier server to enhance your website’s capabilities. Currently, we are providing server upgrades for only xCloud & Vultr servers.
However, upgrading your Server with [**xCloud**](/) is now available to expand the server’s capabilities. You have the freedom to effortlessly boost your server’s power with just a few clicks.
Our Server Resize feature allows you to easily add more computing muscle, like CPU, memory, and storage, to your existing server. You may have to resize your server when you are out of disk space but there are a few things that you must take into account.
- **Downtime Warning**: If you resize or upgrade your server, it can cause downtime, which means your websites will be temporarily unavailable. But usually, it does not take more than 2/3 minutes.
- **Possible Issues**: Making changes to your server can sometimes lead to unexpected problems, just like when you update your computer’s operating system. It may require extra troubleshooting and, in some cases, a fresh start.
- You can’t go back to a lower tier once you’ve upgraded.
- Turning on or taking a full backup of the server before resizing is recommended.
Another name for this feature is Vertical Scaling, or scale-up as it’s commonly called, which is all about beefing up your server’s performance within the same region it was created.
## **Billing Guide To Follow Before Upgrading Your Server** [#](/docs/how-to-upgrade-your-server-in-xcloud/)
There are two categories of xCloud servers – **General** & **Premium**. But you need to keep in mind that you can upgrade to Premium category servers if your existing server is under the Premium category or vice versa.
When upgrading server plans, you only pay the price difference. We adjust for any unused portion of your previous plan, so you’re only charged for what you need. It’s easy to upgrade, all you need to do is pay the difference.
To learn more about how billing works in xCloud, dive into the below documentation.
👉 **[How Do Pricing Plans And Billing Work In xCloud?](/docs/how-billing-works-in-xcloud/)**
## **Guide To Upgrade Your Server With xCloud** [#](/docs/how-to-upgrade-your-server-in-xcloud/)
Begin by navigating to the “**All Servers**” page and select any of your active servers.
After you have selected it, you’ll be on the Server dashboard. From there, simply click on “**Server Management**” to access the options for resizing your server to suit your needs perfectly.
Now under the “**Choose Your Server Size**” dropdown, you will get your available server upgrading options. Select the one that suits your needs.
Once you’ve selected your server, click on “**Upgrade Server**.” This will prompt a popup where you’ll need to enter your server name for confirmation. Take a moment to review any warning messages before proceeding to ensure caution. After all that click on **Resize** for upgrading.
Now you will see that your server has been upgraded successfully.
## **Alternative Strategies for Server Resizing When Provider Options Are Limited** [#](/docs/how-to-upgrade-your-server-in-xcloud/)
1. **Moving Some Sites to a New Server:** Create a new server with the same size and move some websites from your existing server to the new one. This minimizes downtime, and you can leave important sites on the old server. You can use our Site Clone feature to clone any site to any connected servers.
2. **Moving All Sites to a Bigger Server:** Alternatively, you can create a larger server and move all your websites to it. Once everything is transferred, you can shut down the old server. This can be cost-effective. You can use our built-in Full Server Migration Feature to do this for bulk site migration with xCloud temporary staging domains.
3. **Follow Resize Procedure:** If none of the above options work for you, follow the resizing instructions provided by your cloud provider:
[**Vultr
**](https://docs.vultr.com/how-to-upgrade-your-plan-without-reinstalling)[**Digital Ocean
**](https://docs.digitalocean.com/products/droplets/how-to/resize/)[**Google Cloud**](https://cloud.google.com/sdk/gcloud/reference/compute/disks/resize)
[**Hetzner**](https://docs.hetzner.com/robot/dedicated-server/general-information/root-server-upgrade/)
**_Note: Check Disk Space: First, check if there are unnecessary files or folders taking up space on your server. Remove them to free up server storage. Normally server logs might take up many space which can be solved by easily restarting the server._**
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Use Blueprints in xCloud - xCloud
> Learn how to use Blueprints in xCloud to create website with pre-installed themes and plugins and speed up your website building projects.
Blueprints can save huge amounts of time with pre-saved website settings like theme and plugins. Once you create blueprints in xCloud, you do not have to install certain sets of plugins or theme each time you create a website. While creating a website in xCloud, all you need to do is select a blueprint, and then your plugins and theme will be automatically installed.
Follow these steps by step guidelines to use blueprints in xCloud hosting.
## Step 1: Create A Blueprint [#](/docs/how-to-use-blueprints-in-xcloud/)
First of all, from your xCloud dashboard, navigate to the **‘My Profile’** option. Now, go to the **‘My Blueprints’** tab.
If you have created any blueprints first, you will see them there.
If you have created any blueprints, you will see them listed there. Click on **‘Create New Blueprint’** to start creating a blueprint. First, choose one or multiple themes under Themes. Then switch to the Plugins tab to select the plugins for this blueprint. Finally, click on the **‘Create’** button.
You can click on the three-dot button to edit, clone, delete, or set this Blueprint as the default Blueprint. Click on the ‘Set as Default’ button and then confirm it from the appeared popup.
Or if you have created any, you need to create a blueprint first. Similarly, you need to confirm to clone or delete this blueprint.
To edit your Blueprint, click on the **‘Edit Blueprint’** and then remove or add any plugins or themes you want and hit the **‘Update’** button.
To create a new Blueprint, click on the **‘Create New Blueprint’** button. A pop-up will appear where you need to provide your Blueprint name to keep track. Afterwards, find the theme that you want and select it from the **‘Theme’** tab. Then go to the **‘Plugins’** tab to choose the plugins that you want. Similarly, find and select all the plugins you want. Also, from the ‘Popular Plugins’ section, you will find the popular WordPress plugins. Once you are done, click on the **‘Create’** button.
## **Create a Custom Blueprint** [#](/docs/how-to-use-blueprints-in-xcloud/)
You can create custom blueprints with your preferred plugins and themes. Choose the **‘Custom Items’** option from the tab. Give your custom blueprint a name first. Then enter a name for the item in the **‘Item Name’** field and choose the **‘Item Type’** as either **‘Plugin’** or **‘Theme’** from the dropdown. Then choose a source method from the ‘Download URL’ and ‘Upload ZIP File’ options
For the detailed step-by-step guide, check out this documentation:
[How to Create a Custom Blueprint with xCloud](/docs/how-to-create-a-custom-blueprint/)
## Use a Blueprint While Creating a Website [#](/docs/how-to-use-blueprints-in-xcloud/)
The Blueprints options will appear while you are [creating your website in xCloud](/docs/how-to-create-a-site-with-xcloud/).
Navigate to the Blueprint section below while you are creating your website and choose the Blueprint you want to use. You can click on the ‘View all’ button to see all of your Blueprints. Afterwards, hit the **‘Next’** button to start creating your website with this Blueprint.
From the Blueprint section, you can also create another Blueprint. Just click on the **‘Create New Blueprint‘** button and choose the theme and plugins as shown previously.
This is how you can use Blueprint in xCloud and save your time.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Use Gemma 4 with OpenClaw and Ollama on xCloud? - xCloud
> Learn how to run Gemma 4 with Ollama and OpenClaw on xCloud. Set up a private, self-hosted AI agent with no API costs in a few simple steps.
Gemma 4 is a lightweight open model family from Google that can be run through Ollama. It gives you a way to run OpenClaw with a local or self-hosted model setup using Ollama on xCloud. This is useful if you want more privacy, no API costs, and more control over how your model is hosted.
In xCloud, this setup lets you pair:
- OpenClaw for the AI agent runtime
- Ollama for local or self-hosted model serving
- Gemma 4 as one of the available models for your agent workflows
Gemma 4 is a recently introduced model that you can try alongside other options such as DeepSeek R1 and more. This setup works well if you want to experiment with private or lower-cost agent workflows on xCloud.
Follow this guide to run Gemma 4 with Ollama and connect it to OpenClaw on xCloud.
## **Step 1: Deploy OpenClaw on xCloud** [#](/docs/how-to-use-gemma-4-with-xcloud/)
If you have not already deployed OpenClaw, follow the xCloud OpenClaw deployment guide.
In short, you need to:
- Create an xCloud Managed Server for OpenClaw
- Complete the initial provider or messaging setup
- Finish provisioning and confirm the OpenClaw instance is working
👉Read this [documentation](/docs/how-to-deploy-openclaw-with-xcloud/) for a step-by-step guide to installing OpenClaw.
## **Step 2: Deploy Ollama on xCloud** [#](/docs/how-to-use-gemma-4-with-xcloud/)
Next, deploy Ollama using xCloud’s self-hosted LLM workflow. You can install Ollama on a Docker NGINX server.
If you are using xCloud’s Ollama app flow, complete the installation and confirm the service is running before connecting it to OpenClaw.
👉Read this [documentation](/docs/how-to-self-host-llms-with-xcloud/) for a step-by-step guide to installing Ollama.
## **Step 3: Add a New Model** [#](/docs/how-to-use-gemma-4-with-xcloud/)
Next, go to ‘Ollama’ → ‘Management’ from your xCloud Ollama dashboard. Then, find the ‘Add New Model’ button and click on it.
A pop-up will appear. Select the ‘Gemma 4’ model from the dropdown and click on the ‘Pull Model’ button. It will start installing the Gemma 4 model in Ollama.
## **Step 7: Expose Ollama API (Important)** [#](/docs/how-to-use-gemma-4-with-xcloud/)
1. Open your Ollama server.
2. Navigate to the Nginx config directory:
/etc/nginx/sites-available
3. Edit the config to expose the Ollama API endpoint.
4. Save changes.
5. Restart or reload Nginx.
6. Verify the endpoint is accessible from OpenClaw.
## Step 4: Open the OpenClaw Dashboard [#](/docs/how-to-use-gemma-4-with-xcloud/)
Next, go to your xCloud OpenClaw dashboard and click on the “Config” option from the sidebar.
## Step 2: Add an Ollama Provider [#](/docs/how-to-use-gemma-4-with-xcloud/)
Next, add your Ollama endpoint under the Model Provider section in your config file. You can also use the OpenClaw UI to update the config. Manual updates can lead to mismatches or incorrect setups.
Instead, use the OpenClaw UI chat or a messaging platform like Telegram. Share the config and details while chatting with your agent, and OpenClaw will automatically configure the provider for you.
## Step 3: Add the Models to Agent Defaults [#](/docs/how-to-use-gemma-4-with-xcloud/)
Scroll down in the config file and register those models in the default agent model list. After adding them, click the “Update Config” button to proceed.
_💡 The format is: / and alias is the display name shown inside OpenClaw._
## Step 4: Restart OpenClaw [#](/docs/how-to-use-gemma-4-with-xcloud/)
After saving the config, go to the “Status” option from the left-side menu in xCloud OpenClaw, then click the “Restart” button.
And that’s it, this is how easily you can run OpenClaw using Gemma 4 and Ollama in xCloud.
## ⚠️ Important: Expose Ollama API [#](/docs/how-to-use-gemma-4-with-xcloud/)
One important step to note is that your Ollama API must be accessible from your OpenClaw server. By default, the Ollama API may not be publicly reachable. Without exposing it, OpenClaw cannot communicate with your model.
To fix this, you need to update the Nginx configuration of your Ollama server and expose the API endpoint.
After updating the configuration:
- Reload or restart Nginx
- Verify that the Ollama endpoint is accessible from your OpenClaw server
Once the API is properly exposed, OpenClaw will be able to connect and use your Ollama models without issues.
That’s the full setup. You now have Gemma 4 running through Ollama and connected to OpenClaw on xCloud – a fully self-hosted agent stack with no external API dependencies.
If you run into issues, check that Ollama is running and accessible from your OpenClaw server, and make sure your model IDs in the provider config match exactly what Ollama reports.
Still stuck? Feel free to reach out to our [support team](https://support.xcloud.host/).
---
# How To Use xCloud Playground Feature? - xCloud
> Learn how to use xCloud Playground feature from this documentations and create a demo website to test xCloud.
xCloud comes with a playground feature that you can try and create a demo website for 24 hours. Learn how to use the xCloud Playground feature from the step-by-step guidelines below.
_Note: If you have premium access already, the Playground feature will not be available for you. xCloud Playground feature demonstrates how easy it is to create a website in xCloud. We recommend not to create any serious site here as it will be removed after 24 hours._
## **Step 1: Sign Up For xCloud With Credentials** [#](/docs/how-to-use-xcloud-playground-feature/)
First, you must go to the [**xCloud login page and sign up**](https://app.xcloud.host/login) with your credentials. Add all the necessary credentials and make sure to add a secure password. If you already have an account login to the app dashboard.
## **Step 2: Create Demo Website In xCloud Playground** [#](/docs/how-to-use-xcloud-playground-feature/)
Once you have logged into xCloud, you will see options to try the xCloud Playground feature. You can click on the ‘**Try Playground**’ from the menu bar or click on the ‘**Try xCloud Playground**’ button from the middle of the dashboard page.
Afterward, you will be redirected to the WordPress installation page. Provide your site title and other necessary information before clicking on the ‘**Next**’ button.
You can also try the advanced features below. Click on the ‘**More Advanced Settings**’ button and a drop-down section will appear. Provide your username, and password, as you want. You can also set up PHP versions from 5.6 to the latest version and even WordPress 5.0 to the latest versions as well. In addition, you can deploy scripts from there as well.
By default, you can create a database in the xCloud server for this demo site. If you want, you can add your existing database as well. To do that click on the ‘**Add Your Existing Database**’ button and fill out the necessary fields before clicking on the next button.
Now, a popup will appear where you need to click on the ‘**Accept**’ button to be added to the Playground Team.
## **Step 3: Login To Your Demo Website** [#](/docs/how-to-use-xcloud-playground-feature/)
Instantly your demo website will be ready to explore. Now, click on the ‘**Magic Login**’ feature to log in to your demo WordPress website dashboard. You can also view site events, enable Purge cache, or delete this demo site by clicking on the 3 dots button.
This is how easily you can create a WordPress website in xCloud Playground at ease.
## **Step 3: Manage Your WordPress Website** [#](/docs/how-to-use-xcloud-playground-feature/)
From your dashboard, click on the newly created website. Your website management panel will appear where you can manage your website with ease.
xCloud offers advanced site management features like staging, WordPress plugin and theme management, redirection, caching, event, performance monitoring, and remote and local site backup. You can check out [**our docs on website creation**](https://xcloud.host/docs-category/sites/) features to learn more about all of these settings and features.
That’s how you can use the xCloud Playground feature and get a glimpse of what’s inside xCloud.
Still stuck? Contact our [**support team**](/contact/) for any of your queries.
---
# What Extra Steps Does xCloud Take to Manage Community-Driven Websites? - xCloud
> xCloud offers performance optimization features to manage community-driven websites like BuddyBoss and BuddyPress, ensuring smooth, real-time user interactions.
xCloud goes the extra mile by offering performance optimization features specifically tailored to manage community-driven websites, such as **BuddyBoss** and **BuddyPress**. We offer advanced caching mechanisms, database optimization, and automated backups to handle high-user interactions and real-time data. This ensures a smooth, lag-free experience for your users, even during peak activity periods.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How xCloud Managed Server Resize Charges Work With xCloud - xCloud
> When you resize an xCloud Managed Server, the invoice may show new charges, credits, or multiple bill rows. This guide explains why resize charges appear, how
When you resize an xCloud Managed Server, the invoice may show new charges, credits, or multiple bill rows. This guide explains why resize charges appear, how pro-rated adjustments work, and what to send Support if the invoice looks confusing.
## When this guide applies [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Use this guide if:
- you resized a managed server and saw an unexpected invoice,
- you upgraded or downgraded a managed server plan,
- your invoice contains multiple bill rows for the same server,
- you see a charge after resizing and want to understand the calculation,
- only some bill rows in an invoice should be refunded or credited.
## Why resize charges happen [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
A managed server resize changes the plan, resources, or service level for the server. Because billing periods are time-based, xCloud may need to calculate the difference between the old plan and the new plan for the remaining time in the current billing period.
Resize billing can include:
- a pro-rated charge for the new, higher plan,
- a pro-rated credit for unused time on the old plan,
- an adjustment row if the resize happened mid-cycle,
- a renewal row if the resize happened near the next billing date,
- separate bill IDs for each billing component.
This is why one invoice can contain more than one server-related bill row.
## Pro-rated resize logic [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
The basic idea is:
```
Resize adjustment = new plan unused-period cost - old plan unused-period credit
```
Copy to Clipboard
If you upgrade, the invoice may charge only the difference for the unused part of the billing cycle. If you downgrade, there may be an unused credit depending on the product rules and billing review.
## Example upgrade calculation [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Example only:
```
Old plan: $30/month
New plan: $60/month
Billing period: 30 days
Days remaining after resize: 15 days
Old plan unused value: $30 × 15 ÷ 30 = $15
New plan remaining value: $60 × 15 ÷ 30 = $30
Resize charge: $30 - $15 = $15
```
Copy to Clipboard
In this example, the customer is not charged the full new monthly price immediately. The charge is the difference for the remaining days in the cycle.
## Example refund or credit after resize [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
If a resize was accidental or corrected, Support may review only the bill rows connected to that resize. If the invoice also contains other charges, such as backup add-ons or other servers, those unrelated rows are not included in the resize refund.
This is important when Support says only specific **bill IDs** from an invoice are refundable. The invoice can stay partially valid while selected bill rows are adjusted.
## How to review a resize invoice [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
### 1\. Open the invoice [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Open the invoice from the billing area and check all line items.
### 2\. Find server-related bill rows [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Look for rows that reference the managed server, plan change, resize, upgrade, downgrade, or resource adjustment.
### 3\. Note the bill IDs [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
If the invoice has multiple rows, write down the specific bill IDs that belong to the resize. Support may need these exact IDs to process the correct refund or credit.
### 4\. Check the resize date [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Find when the resize happened. The refund or charge calculation depends on the remaining time in the billing period after this date.
### 5\. Contact Support if the charge looks wrong [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Send the invoice ID, bill IDs, server name, resize date, and expected plan. Support can check whether the resize charge was calculated correctly.
## What xCloud Support can check [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
xCloud Support can review:
- whether the server is an xCloud Managed Server,
- the previous and new plan,
- invoice rows connected to the resize,
- whether the charge is pro-rated,
- whether the invoice includes unrelated bill rows,
- whether a correction, credit, or refund is needed.
## Common confusion [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
### The invoice has several rows [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
This is normal when billing includes a resize, renewal, add-on, or adjustment. Review the bill IDs instead of assuming the entire invoice is one charge.
### The charge happened after I deleted the server [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
If deletion and resize happened close together, Support should review the timeline and bill IDs. Managed server unused time may be eligible for a pro-rated refund.
### Only some bill IDs are refundable [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
That can happen when only some rows are related to the eligible managed server resize charge. Other rows may belong to different services or already-used time.
## What to send xCloud Support [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Include:
- invoice ID,
- resize-related bill IDs,
- managed server name,
- old plan and new plan,
- date and time of resize,
- whether the server was later deleted or cancelled,
- screenshot of the invoice if possible.
## FAQ [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
### Are xCloud Managed Server resize charges pro-rated? [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Yes. Managed server resize charges are handled using pro-rated billing for the relevant period.
### Can I get a refund if I resized by mistake? [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
Contact Support with the invoice ID and bill IDs. The billing team can review the eligible managed server rows and unused period.
### Why did I receive a charge instead of a credit? [#](/docs/how-xcloud-managed-server-resize-charges-work-with-xcloud/)
If the new plan costs more than the old plan, the unused-period difference may create a charge. If the new plan costs less, the review may result in a credit or adjustment depending on the case.
---
# How xCloud Support Scope Works for Different Services With xCloud - xCloud
> Clear breakdown of xCloud support scope across services. Learn what is covered, what is not, and how to get faster help with hosting, servers, WordPress, and more.
xCloud Support helps you use the xCloud platform, supported hosting tools, managed server features, and common server/site workflows. This page explains what our team can help with, what may require your developer or third-party provider, and where support boundaries apply.
This is not meant to limit help. It is meant to set clear expectations so issues reach the right team faster.
## Quick overview [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Area
We help with
Outside standard support
xCloud Panel
Dashboard, servers, sites, SSL, backups, restores, logs, events, platform errors
Unsupported custom server changes, root access guidance, third-party account control
xCloud Managed Servers
Provisioning, supported stack, xCloud-managed services, health checks, security events
Custom code, third-party app bugs, custom architecture, app business logic
Self-Managed Servers
Connecting to xCloud, supported stack operations, xCloud panel workflows
Provider billing, provider outages, unsupported root-level custom changes, unsupported packages
Free Migration Offer
Standard eligible WordPress migrations into xCloud
Redesign, rebuild, malware cleanup, custom code, email migration, complex custom apps unless agreed
WordPress
Hosting tools, domains, SSL, backups, restores, logs, permissions, common platform-level issues
Website building, SEO guarantees, plugin/theme code fixes, custom feature development
DNS
Required records, propagation checks, domain/SSL guidance
External DNS account management without access, registrar issues, propagation timing control
Email
xCloud mailboxes, SMTP, DNS records, service checks
Deliverability guarantees, third-party client/provider deep troubleshooting
Git
Git connection, branch selection, deployment logs, webhooks/deployment URL guidance
Code fixes, merge conflicts, CI/CD pipeline writing, repository development
Laravel/PHP
Runtime, PHP versions/extensions, logs, domains, SSL, env/cron/queue guidance
Laravel code, business logic, package internals, application architecture
Lovable Apps
Hosting/deploy guidance, env/domain/SSL/log checks
Fixing generated code, redesign, business logic, Lovable project internals
Ollama
Supported hosting stack, access, service health, logs visible in xCloud
Model quality, prompting, fine-tuning, custom model debugging, GPU/provider limits
Docker / Compose
Deployment workflow, logs, ports, proxy/routing, env guidance
Writing Dockerfiles/Compose files, image internals, custom app debugging
AI Agent Hosting
OpenClaw/Hermes/Paperclip provisioning, dashboard, server health, SSL/domain, basic pairing guidance
Agent result guarantees, prompt engineering, custom workflow building, third-party LLM/API billing
Malware Cleanup
Basic hosting/security guidance, logs, backups, restore guidance, vulnerability/firewall guidance
Malware removal, forensic cleanup, guaranteed disinfection, reputation repair
## How to get support faster [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Before opening a ticket, please check the relevant xCloud documentation first. Many common issues are already documented with step-by-step instructions.
When opening a support ticket, include:
- xCloud server, site, or app link
- Public URL or domain
- Exact error message
- Screenshot or screen recording
- What you expected to happen
- What happened instead
- When the issue started
- Recent changes: deployment, plugin update, DNS change, restore, migration, server change, or custom code change
- Logs or event output if available
- Whether the issue affects all users or only some users
Do not post passwords, private keys, API keys, access tokens, or secrets in public channels. Share credentials only through the secure method requested by xCloud Support.
## Core support principle [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud Support focuses on:
- xCloud platform and dashboard issues
- Supported xCloud hosting workflows
- Supported server stack operations
- Server/site health visible through xCloud
- Logs, events, SSL, backups, restores, domains, and deployment status
- Guidance for supported configuration
xCloud Support does not replace:
- A web developer
- A Laravel/PHP developer
- A Docker engineer
- A WordPress plugin or theme developer
- A DNS registrar or DNS provider
- An email deliverability consultant
- A third-party app support team
- A custom AI workflow or prompt engineering team
When an issue is outside standard support scope, we may still provide general guidance, logs, documentation links, or next-step recommendations where possible.
## xCloud Panel and platform support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
The xCloud Panel is the dashboard where you manage servers, sites, backups, SSL, domains, deployments, logs, teams, and billing-related workflows.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- xCloud dashboard access and platform errors
- Server provisioning status and failed setup checks
- Server connection status inside xCloud
- Site creation, deletion, clone, staging, migration, and progress issues
- SSL installation, retry, pending, or failed status in xCloud
- Domain update status and xCloud-side domain checks
- Backup and restore jobs created through xCloud
- xCloud event logs, deployment logs, and task status
- xCloud-managed service restarts and platform repair workflows
- Team/account navigation and role guidance
- Billing routing, invoice review handoff, and refund-review guidance
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Provide root access guidance, including root password availability where applicable and safer SSH key-based login recommendations
- Guarantee recovery from unsupported manual changes made outside xCloud
- Perform unsupported custom server modifications
- Manage external cloud provider accounts unless an integration or access is provided
- Take responsibility for provider-side billing, provider outages, or provider account restrictions
- Act as an outsourced system administrator for every custom server change
## xCloud Managed Servers vs Self-Managed Servers [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud supports different server ownership models. Support scope depends on who owns and controls the server infrastructure.
## xCloud Managed Servers [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud Managed Servers are provisioned and billed through xCloud-supported managed workflows. xCloud manages the supported server stack and platform services needed to host WordPress sites and supported applications.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
For xCloud Managed Servers, we help with:
- Server provisioning through xCloud
- Supported hosting stack setup
- xCloud-managed services and configuration
- SSL and domain tools
- Backups and restores through xCloud
- WordPress/site management tools
- Server health checks visible in xCloud
- Logs and events visible in xCloud
- Security events and supported xCloud-side patches/mitigations
- Supported server service checks and restarts
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
For xCloud Managed Servers, we do not handle:
- Customer custom code
- Plugin or theme code bugs
- Application business logic
- Third-party API behavior
- Third-party account billing
- SEO outcomes
- Email inbox placement guarantees
- Custom server architecture beyond supported xCloud workflows
- Unsupported manual system-level changes
### Root and sudo access note [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud provides full root access and the root password where applicable. For better security, we recommend SSH key-based login instead of password login. Where supported, you can create:
- Sudo users for server-level access
- Site users for site-specific access
Do not remove xCloud-managed SSH keys. xCloud uses its managed access for dashboard operations such as deployments, server checks, and site management.
## Self-Managed Servers [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Self-managed servers are servers you own or rent from your own cloud provider and connect to xCloud. The server and provider account remain your responsibility.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
For self-managed servers, we help with:
- Connecting the server to xCloud
- xCloud panel integration
- Supported xCloud stack operations
- Site management features available through xCloud
- SSL/domain guidance through xCloud
- Backups/restores created through xCloud
- Logs/events visible in the xCloud dashboard
- General DNS and hosting guidance
- Identifying whether an issue appears to be xCloud-related or provider/server-related
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
For self-managed servers, you or your provider are responsible for:
- Provider billing
- Provider outages
- Provider account access
- Root-level custom changes
- Unsupported packages or manual server modifications
- Firewall/network rules outside xCloud’s supported setup
- Hardware, region, IP, or infrastructure problems from the provider
- Removing resources from the provider dashboard after you no longer need them
- Provider support tickets and abuse reports, unless xCloud specifically created or manages the related service
### Important self-managed server note [#](/docs/how-xcloud-support-scope-works-for-different-services/)
On self-managed servers, root/provider access remains with you or your hosting provider. xCloud Support may request a supported user or panel-level access to troubleshoot xCloud-related issues.
## Free WordPress Migration Offer [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud may offer free standard WordPress migration assistance for eligible sites moving into xCloud.
Migration availability depends on:
- Site access
- Site size
- Source hosting limitations
- Source security restrictions
- Site complexity
- Whether the migration is standard WordPress or a custom application
- Whether required credentials and permissions are available
### What the free migration offer usually includes [#](/docs/how-xcloud-support-scope-works-for-different-services/)
For eligible standard WordPress migrations, we may help with:
- Moving a standard WordPress site into xCloud
- Migrating files and database where access is available
- Basic post-migration checks
- Temporary URL testing guidance
- Domain/DNS guidance for pointing the site to xCloud
- SSL setup after DNS is ready
### What the free migration offer does not include [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Free migration support does not include, unless separately agreed:
- Website redesigns
- Website rebuilds
- Custom development
- Malware cleanup, forensic cleanup, or guaranteed disinfection
- Fixing broken plugins or themes from the source site
- Rewriting custom code
- Email mailbox migration
- DNS/provider account management
- Domain ownership or registrar account changes
- Migrating non-WordPress applications
- Complex multisite or custom architecture migrations without prior review
- Performance optimization after migration beyond basic hosting checks
- SEO cleanup, content cleanup, or page builder redesign
### What you need to provide for migration [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Depending on the migration method, support may ask for:
- Source website URL
- WordPress admin access
- SFTP/SSH or hosting panel access
- Destination xCloud server/site
- Whether the site is single-site or multisite
- Source host name, such as Cloudways, cPanel/WHM, InstaWP, or another provider
- Any special requirements before migration
Do not share credentials in public channels. Use the secure method requested by support.
## WordPress support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud hosts and manages WordPress sites at the hosting/platform level.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- WordPress site creation through xCloud
- Domain and SSL setup
- xCloud-managed backups and restores
- Migration, clone, and staging workflows
- WordPress site logs available from xCloud
- File permission or ownership issues related to hosting operations
- PHP version and PHP service checks
- Cache-related hosting checks
- WP-CLI availability or hosting-level WP-CLI errors
- Database connection checks at the hosting level
- Identifying likely plugin, theme, cache, PHP, or resource issues from logs
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Build, redesign, or edit your website content as a development service
- Write custom plugin or theme code
- Maintain third-party plugin or theme code
- Deep-debug arbitrary plugin/theme internals beyond identifying the likely cause
- Guarantee SEO rankings, indexing, traffic, Core Web Vitals, or conversion outcomes
- Fix issues caused by unsupported manual code changes as part of standard support
- Replace a WordPress developer for custom functionality
## DNS and domain support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
DNS controls where your domain points. xCloud can tell you what records are required and help verify whether they are resolving correctly.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- Required DNS records for xCloud-hosted sites
- A, CNAME, MX, SPF, DKIM, and DMARC guidance where relevant
- Checking whether DNS points to the correct xCloud server IP
- Explaining DNS propagation status
- Troubleshooting xCloud-side domain status
- SSL validation issues related to DNS
- Cloudflare proxy guidance when it affects xCloud SSL/domain behavior
- xCloud domain update and additional domain workflows
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Manage your external DNS provider account unless you grant access or connect an approved integration
- Control DNS propagation timing
- Fix registrar outages or domain ownership issues
- Renew domains purchased outside xCloud
- Guarantee third-party DNS provider behavior
- Manage all Cloudflare WAF/security settings as a managed Cloudflare service unless explicitly supported
## Email, SMTP, and mailbox support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Email involves xCloud settings, DNS records, mailboxes, SMTP settings, sender reputation, recipient filters, and sometimes third-party providers.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- xCloud mailbox setup where available
- xCloud email service configuration
- SMTP host, port, security, username, and password guidance
- IMAP/SMTP details for standard email clients
- DNS records for email: MX, SPF, DKIM, and DMARC.
- Sender verification steps.
- Checking xCloud mail service status
- Troubleshooting xCloud-side mailbox, SMTP, and DNS configuration issues
- Guidance for WordPress/contact form SMTP setup
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Guarantee inbox placement or deliverability
- Control recipient spam filters
- Control sender reputation across the internet
- Deep-troubleshoot every third-party email client
- Manage Google Workspace, Microsoft 365, Mailgun, SendGrid, Elastic Email, or other providers unless access/integration is provided
- Guarantee that direct outbound mail on port 25 is available, because many providers block it
- Write or maintain custom mailing code inside your app
- Include email mailbox migration in the free WordPress migration offer unless separately agreed
### Email deliverability note [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Even when DNS and SMTP are configured correctly, inbox placement can depend on sender reputation, domain history, email content, bounce/complaint rates, recipient filters, and SPF/DKIM/DMARC alignment.
## Git deployment support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud supports Git-based deployment workflows for supported app/site types.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- Connecting supported Git providers
- Selecting repository and branch
- Git deployment settings inside xCloud
- Push to Deploy guidance
- Deployment URL/webhook guidance
- Deployment logs and recent deployment status
- Environment variable guidance where available
- Identifying whether a deployment failure is caused by xCloud, Git access, build command, environment, or app code
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Fix your application code
- Resolve merge conflicts
- Write CI/CD pipelines
- Debug custom build scripts beyond identifying log errors
- Manage repository permissions beyond connection guidance
- Refactor or review code as part of standard support
- Guarantee that every repository will deploy without app-specific changes
## Laravel and PHP application support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud can host PHP and Laravel applications depending on the selected server stack and deployment method.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- PHP version and PHP extension guidance
- Web server/proxy configuration related to xCloud hosting
- Domain and SSL setup
- Deployment logs and failed deployment checks
- Environment variable guidance
- File and folder permission issues related to hosting
- Laravel public directory guidance
- Queue and cron guidance at the hosting level
- Database connection checks at the server/configuration level
- Error log review to identify whether the issue is runtime or application-level
- Server resource checks: CPU, memory, disk, and services
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Write Laravel controllers, models, jobs, middleware, or views
- Fix custom business logic
- Debug third-party package internals as a development service
- Design or refactor your application architecture
- Optimize your application database queries as a development service
- Build APIs, admin panels, or application features for you
- Maintain your custom codebase
## Lovable app support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Lovable can generate applications that you may want to host on xCloud. xCloud Support focuses on the hosting/deployment layer, not the generated app’s design or code quality.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- Hosting or deploying a supported Lovable-generated app on xCloud
- Environment variable guidance
- Domain and SSL setup
- Deployment logs
- Server health checks
- Basic routing/proxy checks where supported
- Identifying whether the issue appears hosting-related or app-code-related
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Fix generated Lovable code
- Redesign the app
- Change business logic
- Debug frontend/backend implementation details as a development service
- Improve app UX or generated design
- Manage your Lovable account or project settings beyond deployment guidance
- Guarantee that generated code is production-ready without developer review
## Ollama support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Ollama hosting can be used for local or self-hosted model workflows where supported by xCloud.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- Deploying the supported xCloud/Ollama hosting stack
- Accessing the service
- Basic service health checks
- SSL/domain setup where applicable
- Logs visible through xCloud
- Server resource checks
- Restarting or redeploying supported services where available
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Guarantee model output quality
- Provide prompt engineering
- Fine-tune models
- Debug custom model behavior
- Guarantee performance for every model
- Resolve GPU/provider limitations outside xCloud scope
- Handle third-party model licensing questions
- Optimize every model for speed, memory, or cost
## Docker and Docker Compose support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Docker and Docker Compose provide flexibility, but custom images and application internals remain your responsibility.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- xCloud-supported Docker/custom app deployment workflows
- Docker Compose file location and basic format guidance
- Deployment logs and container status checks
- Exposed ports and port conflict guidance
- Nginx proxy/routing configuration related to xCloud
- Domain and SSL setup
- Environment variable guidance
- Server resource checks
- Restarting or redeploying services where supported
- Identifying whether an issue appears xCloud infrastructure, proxy, port, environment, or container/app related
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Build custom Docker images for you
- Write or restructure Dockerfiles
- Write or restructure Docker Compose files as a development service
- Debug arbitrary software inside your container
- Maintain your custom application code
- Fix bugs inside third-party images
- Guarantee that every public Docker project will run unchanged on xCloud
- Provide full DevOps consulting for unsupported custom architectures
- Design custom networking beyond supported xCloud configuration
## AI Agent Hosting: OpenClaw, Hermes, and Paperclip [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud supports AI agent hosting workflows such as OpenClaw, Hermes, Paperclip, and related agentic services where available.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We help with:
- Provisioning supported AI agent hosting services
- xCloud dashboard access
- Server health checks
- SSL and domain setup
- Logs visible through xCloud
- Service restart or redeploy where supported
- Basic Telegram pairing guidance where relevant
- Basic control UI access guidance
- Identifying whether an issue appears hosting-related, service-related, or custom workflow-related
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
We do not:
- Guarantee agent task success
- Guarantee model response quality
- Provide prompt engineering as standard support
- Build custom workflows for you
- Debug arbitrary tools, plugins, or custom agent code
- Manage third-party LLM/API billing
- Pay for or control your OpenAI, Anthropic, OpenRouter, Google, or other AI provider account
- Fix user-created automation logic
- Guarantee that an agent can complete every business task autonomously
- Debug every third-party integration used by an agent
### Important AI hosting note [#](/docs/how-xcloud-support-scope-works-for-different-services/)
xCloud Support can help keep the supported hosting environment running. The quality of an AI agent’s output depends on the model, prompts, tools, API providers, user configuration, and the task itself.
## Malware cleanup support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Malware on xCloud-hosted sites is rare, but it can still happen if a WordPress plugin/theme is vulnerable, credentials are compromised, an unsafe file is uploaded, or malicious code is imported from a previous host.
xCloud provides hosting-level security features, logs, backups, firewall guidance, vulnerability-related visibility where available, and server/site management tools. However, malware cleanup itself is a specialist security service and is not included in standard xCloud Support.
### What we do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
For suspected malware or suspicious files, we can help with:
- Checking whether the server/site is online in xCloud
- Reviewing xCloud-visible logs and events
- Helping identify suspicious symptoms from a hosting point of view
- Guidance on restoring from a clean backup if one is available
- Guidance on rotating passwords, SSH/SFTP users, and database credentials
- Guidance on updating WordPress core, plugins, and themes
- Firewall, SSL, backup, and vulnerability-related guidance available through xCloud
- Explaining when a malware/security specialist may be needed
### What we do not do [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Standard xCloud Support does not include:
- Malware removal or guaranteed cleanup
- Manual forensic investigation of every file/database table
- Cleaning hacked WordPress sites
- Removing webshells/backdoors as a managed service
- Repairing injected SEO spam pages or malicious redirects
- Reviewing every plugin/theme file for compromise
- Guaranteeing that a site is fully disinfected
- Removing Google, browser, email, or security-vendor blacklist warnings
- Reputation repair after a compromise
- Installing, configuring, and maintaining third-party malware tools as a managed service
### What to do if you suspect malware [#](/docs/how-xcloud-support-scope-works-for-different-services/)
If you suspect malware:
1. Take the site offline or put it in maintenance mode if the issue is active.
2. Keep a copy of the current files/database for evidence before deleting anything.
3. Restore from a known clean backup if you have one.
4. Update WordPress core, plugins, and themes.
5. Remove unused plugins, themes, and unknown admin users.
6. Rotate WordPress, database, SFTP/SSH, xCloud, provider, and API credentials.
7. Ask a qualified malware cleanup/security specialist to inspect and clean the site if the infection is confirmed.
8. Contact xCloud Support if you need help checking backups, logs, hosting status, or xCloud-side security tools.
### Malware cleanup note [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Because malware cases are uncommon and each infection can be different, xCloud Support can provide best-effort hosting guidance, but we cannot certify a site as clean. A confirmed infection should be handled by a WordPress security or malware cleanup specialist.
## What is always outside standard support [#](/docs/how-xcloud-support-scope-works-for-different-services/)
The following are outside standard xCloud Support unless separately offered or agreed:
- Custom development
- Custom code debugging
- Theme/plugin development
- Business logic changes
- Website redesign
- Malware cleanup, forensic cleanup, or guaranteed disinfection
- SEO/content work
- Email hosting migration unless separately agreed
- Domain registrar account management
- Third-party provider billing or outages
- Third-party API billing
- Prompt engineering or AI model tuning
- Unsupported root-level server modifications
- Writing Dockerfiles, Compose files, CI/CD pipelines, or application code
- Full DevOps consulting for unsupported architectures
- Fixing third-party tools, packages, plugins, themes, images, or generated code
## Best-effort guidance [#](/docs/how-xcloud-support-scope-works-for-different-services/)
When an issue is outside standard support scope, xCloud Support may still provide:
- General guidance
- Relevant logs
- Documentation links
- Suggested next steps
- Clarification on whether the issue appears xCloud-related or app/provider-related
However, resolution may require your developer, hosting provider, domain registrar, third-party vendor, email provider, AI provider, or a separately scoped professional service.
## FAQ [#](/docs/how-xcloud-support-scope-works-for-different-services/)
### Does xCloud Support fix custom code? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. xCloud Support helps with hosting, platform, runtime, configuration, and logs. Custom application code, business logic, theme/plugin code, Docker image internals, and generated app code remain your responsibility or your developer’s responsibility.
### Can xCloud Support tell me whether the issue is platform or code? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Often, yes. We can review logs, events, server status, and configuration to help identify whether an issue appears xCloud/platform-related or application-related.
### Does free migration include every type of website? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. Free migration support is intended for eligible standard WordPress migrations into xCloud. Custom applications, complex setups, email migration, malware cleanup, redesigns, rebuilds, and custom development are not included unless separately agreed.
### Does xCloud manage my self-managed server provider account? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. For self-managed servers, your provider account, billing, infrastructure, and provider-side resources remain your responsibility.
### Does xCloud provide root passwords? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Yes, xCloud provides full root access and the root password where applicable. For better security, we recommend SSH key-based login instead of password login. Where supported, you can also create sudo users or site users.
### Can xCloud help with Docker or Docker Compose? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Yes, for supported deployment workflows, logs, ports, proxy/routing, SSL, domains, and environment guidance. We do not write Dockerfiles or Compose files or debug arbitrary software inside custom containers.
### Can xCloud help with OpenClaw, Hermes, or Paperclip? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
Yes, for supported hosting, provisioning, dashboard access, SSL, domain, service health, and logs. We do not guarantee AI task results, provide prompt engineering, manage third-party LLM billing, or build custom workflows as standard support.
### Does xCloud guarantee email deliverability? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. We can help configure DNS, SMTP, mailboxes, and xCloud mail service settings, but inbox placement depends on recipient providers, reputation, content, and email authentication.
### Does xCloud guarantee SEO or performance scores? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. We can help with hosting-level issues such as SSL, uptime, redirects, caching, and server resources, but we do not guarantee rankings, indexing, traffic, conversions, or third-party performance scores.
### Does xCloud Support clean malware from websites? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. Malware cleanup is not included in standard xCloud Support. We can help with hosting-level checks, logs, backups, restore guidance, and security-related xCloud tools, but confirmed infections should be cleaned by a qualified WordPress security or malware cleanup specialist.
### Is malware common on xCloud? [#](/docs/how-xcloud-support-scope-works-for-different-services/)
No. Malware cases are rare, but they can still happen through vulnerable plugins/themes, compromised credentials, unsafe uploads, or infected files migrated from another host.
---
# How To Increase Maximum Upload Size For Websites In xCloud? - xCloud
> Increase maximum upload size effortlessly for websites in xCloud. Elevate user engagement and streamline multimedia sharing on your website.
When you increase maximum upload size for websites, it encourages user-generated content and makes sharing large multimedia files and teamwork easier. Plus, this option improves the functionality and overall user experience of eCommerce product listings while also supporting development jobs.
With a few simple steps, you can easily increase the maximum upload size for websites in [**xCloud**](/). Follow the step-by-step instructions below to learn how to do that.
## **Step 1: Access To Your Site In xCloud** [#](/docs/increase-maximum-upload-size/)
Log in to xCloud dashboard, go to ‘**Sites**’ tab, and select your preferred site for which you want to increase maximum upload size.
## **Step 2: Check PHP Version For Your Site** [#](/docs/increase-maximum-upload-size/)
From the site’s ‘**Overview**’ page, click on the ‘**Site Settings**’ tab from the left panel.
Now, check your site’s PHP version. You can also change your **Site’s PHP version**. If you want to do that, select the **PHP version** you want and tap the ‘**Save Settings**’ button.
## **Step 3: Access Server PHP Settings & Change Upload Size** [#](/docs/increase-maximum-upload-size/)
Now, Click on your server’s name (below your site domain) to access your site’s server. There, you can increase the maximum upload size for the site’s PHP version.
Now if you want to change the file upload size then go to the tab ‘**PHP Settings**’ option again to change your maximum upload size value. There, you will see your current maximum upload size in MB (Megabyte). Select your site’s PHP version. You can change the maximum upload size value as much as you need, and it will apply to all the sites with that PHP version. Once done, hit the ‘**Save Changes**’ button.
That is how easily you can increase maximum upload size for websites in xCloud.
Still stuck? Contact our [**support team**](http://support@xcloud.host/) for any of your queries.
---
# How To Increase The PHP Maximum Input Variables In xCloud? - xCloud
> Enhance WordPress speed & functionality in xCloud by increasing PHP maximum input variables. Step-by-step guide awaits!
Input variables play a vital role in **processing functions** and supporting a variety of tasks and activities on your WordPress website. PHP maximum input variables, or simply **[Max Input Vars](https://support.undsgn.com/hc/en-us/articles/213459869-Max-Input-Vars)**, are crucial variables among these. It represents the most variables your server can provide for a particular function.
Put more simply, the smoother the general operation of your website, the greater the maximum input variables option. This configuration directly impacts WordPress’s speed and functionality by increasing its capacity to process data.
In [**xCloud**](/), you can simply increase the maximum input variables for your website. Follow the steps below to learn how you can do that.
## **Step 1: Access To Your Site In xCloud** [#](/docs/increase-the-php-maximum-input-variables/)
Log in to the xCloud dashboard, go to the ‘**All Sites**’ tab, and select your preferred site for which you want to increase the PHP maximum input variables.
## **Step 2: Check The PHP Version For Your Site** [#](/docs/increase-the-php-maximum-input-variables/)
From the site’s ‘**Overview**’ page, click on the ‘**Settings**’ tab from the left panel.
Now, check your site’s PHP version. You can also change your site’s PHP version. If you want to do that, select the PHP version you want and tap the ‘**Save Settings**’ button.
## **Step 3: Access Server PHP Settings** [#](/docs/increase-the-php-maximum-input-variables/)
Now, click on your server’s name (found below your site domain) to access your site’s server. There, you can increase the PHP maximum input variables for the site’s PHP version.
## **Step 4: Increase PHP Maximum Input Variables** [#](/docs/increase-the-php-maximum-input-variables/)
Once you click the server, you will see the ‘**PHP Settings**’ tab on the left panel. Go to the tab to increase the input variables.
There, you will see your current ‘**Max Input Vars**’ value. Select your site’s PHP version. You can change the Max Input Vars value as much as you need, and it will apply to all the sites with that PHP version. Once done, hit the ‘**Save Changes**’ button.
That is how easily you can increase the PHP maximum input variables for websites in xCloud.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Increase the PHP Memory Limit for a Site and Server With xCloud
> Boost performance with ease! Learn to increase PHP maximum memory limit in xCloud. Follow simple steps for better site speed and efficiency.
When a WordPress site needs more PHP memory, update the site-level PHP memory limit first. This controls the PHP settings for that specific site. If you also need to adjust the default PHP configuration for the server, update the server-level PHP memory limit after that.
## Before you start [#](/docs/increase-the-php-maximum-memory-limit/)
- Make sure you have access to the xCloud team where the site and server are hosted.
- Check which site needs the higher PHP memory limit.
- Use the site-level setting first if only one site needs more memory.
- Use the server-level setting only when you want to adjust the PHP configuration for that PHP version on the server.
## Increase the PHP memory limit from the site settings [#](/docs/increase-the-php-maximum-memory-limit/)
Use this method first. It updates the PHP configuration for the selected site. Go to ‘**Sites’** from the xCloud dashboard. Select the site where you want to increase the PHP memory limit. Next, open **Site Settings** from the site menu.
Find the **PHP Configurations** section from the dashboard and click on the ‘**Manage’** button.
Select **PHP Configurations** from the dropdown.
In the **Manage PHP Configurations** panel, find **Memory Limit**. Enter the new memory limit value in MB, for example **512**. Click on the ‘**Save Settings**‘.
## Increase the PHP memory limit from the server settings [#](/docs/increase-the-php-maximum-memory-limit/)
Use the server-level option when you need to update the PHP configuration for a PHP version installed on the server.
1. Go to **Servers** from your xCloud Dashboard.
2. Select the server where the site is hosted.
3. Open **Management**.
Next, choose ‘**PHP Configuration’** from the navigation menu and click on the three-dot icon beside the PHP version that you are using for all the sites of this server as default .
Open the action menu for that PHP version. Click **Manage PHP Configuration**.
In the **Update PHP Configurations** popup, find **Memory Limit**. Enter the new memory limit value in MB. Click **Save Changes**.
That is how easily you can increase the PHP maximum memory limit for websites in xCloud.
## Site-level vs server-level PHP memory limit [#](/docs/increase-the-php-maximum-memory-limit/)
Option
Use it when
**Site-level PHP memory limit**
Only one site needs a higher PHP memory limit.
**Server-level PHP memory limit**
You want to adjust the PHP configuration for the selected PHP version on the server.
## Recommended values [#](/docs/increase-the-php-maximum-memory-limit/)
A common value for WordPress sites is **256 MB** or **512 MB**. Larger WooCommerce, LMS, builder, or import-heavy sites may need more memory. Avoid setting a very high value unless the site needs it, because PHP memory usage still depends on the server’s available RAM.
## Verify the change [#](/docs/increase-the-php-maximum-memory-limit/)
1. Reload the site or WordPress admin page that previously showed the memory issue.
2. If the issue was caused by a plugin, import, backup, or update process, retry that action.
3. If WordPress still shows a lower memory value, check whether the site has a WordPress-level memory constant such as `WP_MEMORY_LIMIT` or `WP_MAX_MEMORY_LIMIT`.
## Troubleshooting [#](/docs/increase-the-php-maximum-memory-limit/)
### The site still shows a memory limit error [#](/docs/increase-the-php-maximum-memory-limit/)
Increase the site-level PHP memory limit first, then retry the failed action. If the issue continues, check whether a WordPress plugin, theme, or custom code is setting a lower WordPress memory value.
### The site needs more memory during imports or backups [#](/docs/increase-the-php-maximum-memory-limit/)
Set the site-level memory limit to a higher value, then run the import or backup again. For very large operations, also check execution time, upload size, and post max size from the same PHP configuration panel.
### The memory limit is already high but the server is still slow [#](/docs/increase-the-php-maximum-memory-limit/)
A higher PHP memory limit does not add RAM to the server. If the server is low on memory or CPU, review the server resource usage and consider optimizing the site or upgrading the server plan.
## Related docs [#](/docs/increase-the-php-maximum-memory-limit/)
- [How To Configure PHP Settings of Your Site](/docs/how-to-configure-php-settings/)
- [How To Increase The PHP Maximum Memory Limit In xCloud?](/docs/increase-the-php-maximum-memory-limit/)
- [How To Solve The WordPress Memory Limit Exhausted Error?](/docs/wordpress-memory-limit-exhausted-error/)
## FAQ [#](/docs/increase-the-php-maximum-memory-limit/)
### Should I update the site-level or server-level memory limit first? [#](/docs/increase-the-php-maximum-memory-limit/)
Update the site-level PHP memory limit first. This is the best option when only one site needs more memory.
### Does increasing PHP memory limit increase my server RAM? [#](/docs/increase-the-php-maximum-memory-limit/)
No. It only changes how much memory a PHP script is allowed to use. Your server still has the same physical RAM.
### Do I need to restart the server? [#](/docs/increase-the-php-maximum-memory-limit/)
xCloud applies the saved PHP configuration through the dashboard workflow. If the change does not appear immediately, wait a short time and reload the affected WordPress page.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How To Take Incremental Backup In xCloud? - xCloud
> Take incremental backup in xCloud effortlessly with our comprehensive guide. Preserve your website data with minimal storage use and ensure quick recovery.
Incremental backups are focused on storing modified files and data since the last conducted backup. If you take incremental backups, it will greatly help to keep slight changes in data on your websites and save storage space on your servers.
[**xCloud**](/) offers multiple backup options, including incremental backup, for keeping multiple copies of your website data, so you can utilize and restore your website to a stable phase if any emergency occurs. Follow this step-by-step guide to learn how to **take incremental backups** in xCloud.
## **Step 1: Go To Backup Settings From xCloud Dashboard** [#](/docs/incremental-backup-in-xcloud/)
Log in to your [**xCloud**](https://app.xcloud.host/) and choose a site from the dashboard or by navigating to the ‘**Sites**’ tab. Now, on the site settings page, you will find two options for the ‘**Backup**’ option at the left menu. You can check your previous backups by going to the ‘**Previous Backups**’ option. With each backup file, you will have the options to ‘**Restore**’ and ‘**Delete**’.
Here, you can also take a full backup of your site by clicking on the ‘**Backup Now**’ or ‘**Add New Backup**’ button. However, if you enable incremental backup in the ‘**Backup Settings’**, you will get to choose between taking a Full Backup or Incremental Backup.
For taking incremental backups including a full backup, you will need to go to the ‘**Backup Settings**’ option from the left menu.
## **Step 2: Select Type & Take Incremental Backup** [#](/docs/incremental-backup-in-xcloud/)
On the backup settings page, you will find two backup options: Local Backup and Remote Backup. For taking an incremental or full backup, we recommend using Remote Backup as your option.
_\[Note: Incremental backup is now supported with the **Cloudflare R2** storage.\]_
Now, on the Remote Backup tab, select ‘**Incremental**’ from the type and select a bucket from the options. If you want to exclude any file or data from the backup, you can exclude it from the ‘**Exclude Paths**’ field.
Remember, to take incremental backups, you will need to enable ‘**Automatic Full Backup**’ first. Enable it and select a backup frequency (_Daily, Weekly, Monthly, or Yearly_). You can also select dates and times for the frequencies.
Now, after enabling full backup, enable ‘**Automatic Incremental Backup**’ and select a backup frequency which can be Daily, Weekly, Monthly, or Yearly. However, to keep up to date, we recommend taking it daily. Then, select a time for backup.
If you enable ‘**Automatic Delete**’ and set the number of days, the backup file will be automatically deleted after the number of days. For example, we have set 1 here, which means the previous backup file will be deleted 1 day after taking a new backup. Once you are done setting up the backup options, hit the ‘**Save**’ button.
Now, you can see your newly taken backup and previous backup by going to the ‘**Previous Backups**’ option. Here, you can restore any taken backup. You can also delete backup files, except the most recent one. For example, here we have previous backup files for Local Backup.
## **How Incremental Backup Deletion Works in xCloud** [#](/docs/incremental-backup-in-xcloud/)
1. You will not be able to delete the latest full backup.
2. To delete any full backup, you must first take another full backup of the site. After that, the older full backup can be deleted.
3. You cannot delete individual incremental backups.
4. To remove incremental backups, the full backup associated with those incremental backups must be deleted.
5. Backups are deleted automatically based on the Automatic Delete days you configured for the site.
6. A full backup will only be deleted after the number of days set for Automatic Delete has passed, and the latest incremental backup date surpasses the automatic delete date you previously configured.
For example, if Automatic Delete is set to 7 days, incremental backups will be deleted only after they become older than 7 days. Once those incremental backups are removed, you will then be able to delete the associated full backup.
7. After the automatic delete period is surpassed, the full backup and all its associated incremental backups can be deleted together in a batch.
This is how easily you can **take incremental backups** in xCloud.
Still need help? Feel free to reach out to our [**support team**](https://support.xcloud.host/).
---
# How to Install & Set Up xCloud Pulse macOS Menubar - xCloud
> Learn how to install and set up xCloud Pulse macOS menubar. Monitor site health, SSL, backups, vulnerabilities, and servers directly from your menu bar.
xCloud Pulse is the macOS companion app for xCloud. It lives in the menu bar at the top of your Mac and keeps the health of your sites and servers one click away, so you can check on everything without opening a browser. xCloud Pulse monitors site health, SSL, backups, vulnerabilities, and server status, and it can notify you when something needs attention.
Follow the step-by-step guide to download and install the xCloud Pulse app, create an xCloud API token, connect the app to your account, set your refresh schedule, and read your dashboard. The whole process takes only a few minutes.
### **Before You Begin** [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
xCloud Pulse runs on:
- macOS 14.0 (Sonoma) or later
- An Apple Silicon (M-series) Mac
You will also need:
- An active xCloud account
- Permission to create an API token in that account
## **Collect the xCloud API Token** [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
### Step 1: Generate an API Token [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
First, go to your xCloud dashboard. Navigate to the left-hand sidebar menu, select Settings, and then click on the ‘Developers’ option from the left side menu and click on the ‘API Tokens’ option. Within the API tokens interface, click the Create New Token button.
### Step 2: Configure Token Name and Permissions [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
A pop-up will appear. Enter a descriptive name for your token and select the appropriate permissions:
1. Full Access (all permissions)
2. read:servers
3. write:servers
4. read:sites
5. write:sites
Once configured, click Create Token. After creation, your token will be displayed. Copy and store it in a secure location immediately, as you will need it for future authentication.
## Set up Your MacOS Menubar [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
### Step 1: Download the MacOS Menubar [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
Then go to the **Settings → Developers** option from the xCloud dashboard. Now click on the xCloud Pulse from the menu.
You will be redirected to the **[Git repository](https://github.com/xCloudDev/xCloud-Pulse)**, then download xCloud Pulse for macOS according to your device OS version.
Open the downloaded .dmg file, then drag the xCloud Pulse icon into your Applications folder. Open xCloud Pulse from your Applications folder. Once the app is running, the xCloud Pulse icon appears in the macOS menu bar at the top-right of your screen.
### 🔖 Allow Security Settings Permissions From Your macOS Device [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
After installing xCloud Pulse and opening it for the first time, you may find that the application does not immediately appear in your macOS menu bar, but rather shows a security concern.
This is a macOS security feature that requires manual approval for applications downloaded outside of the App Store. To proceed, click the **Done** button in the warning pop-up.
_**Note**: You must click Done before approving the application manually. If you close the pop-up without clicking **Done**, the approval option will not appear in your Mac’s Security Settings, and you will not be able to grant permission to the application manually._
Next, go to allow xCloud Pulse, open System Settings on your Mac, and search for the **Privacy & Security** option. Then scroll down to the **Security** section, where you may see a message indicating that xCloud Pulse was blocked from opening. Click **Open Anyway** to approve the application.
Mac will ask you to authenticate using your password or Touch ID. Follow the on-screen prompts to confirm that you want to allow the application to run. Once the approval process is complete, launch xCloud Pulse again from your Applications folder.
After the application starts successfully, the xCloud Pulse icon will appear in the macOS menu bar at the top-right corner of your screen. You can then continue with the setup process by connecting your xCloud account using your API token.
### Step 2: Configure the Menubar [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
Then click on the xCloud icon from your dashboard menu bar. It will instantly open the xCloud Pulse Menu bar.
Then enter the xCloud API token in the dedicated field. Click on the ‘Save Token’ button and click on the ‘Test Connection’ button.
### Step 4: Set Your Refresh Schedule and Behavior [#](/docs/install-and-set-up-xcloud-pulse-macos-menubar/)
Under Polling Interval, choose how often the app refreshes your data. The options are 5, 10, 15, or 30 minutes. Adjust the notification and behavior settings to match your preferences.
Click the xCloud Pulse icon to open the menu. The Overview shows your totals at a glance: the number of sites, the number of servers, overall health, and any open issues.
For example, go to the Sites, Issues tab for more details. Click any site to see its full details, or click the arrow next to a site to open it in xCloud directly from the app.
And that’s it; this is how easily you can download and configure the xCloud Pulse app in just a few clicks.
That is all it takes. In just a few minutes, xCloud Pulse puts your sites and servers in your menu bar and keeps them one click away.
From here, xCloud Pulse watches site health, SSL, backups, vulnerabilities, and server status for you, and it lets you know when something needs attention. You can change your settings at any time by opening the app and selecting Settings. Welcome to a simpler way to keep an eye on everything you run on xCloud.
---
# How to Install and Use xCloud AI Agent Skills Using AI Agents - xCloud
> Learn how to install and use xCloud AI Agent Skills in Claude Code. Manage your servers and sites with plain language, no dashboards or API endpoints needed.
xCloud AI Agent Skills bring your xCloud infrastructure directly into AI assistants such as Claude Code. Instead of manually navigating dashboards and API documentation, you can simply ask your AI assistant to perform tasks using natural language.
With xCloud AI Agent Skills, you can discover servers, inspect sites, check WordPress updates, monitor infrastructure, and perform actions through conversational commands powered by the xCloud Public API.
For example, the “xcloud:servers” skill lets you ask “find my servers” and get a clear list back, with the server name, status, public IP, and provisioning state. You do not need to know any API endpoints to get a useful result. The assistant makes the calls in the background and replies in plain language.
Follow this step-by-step guide to install the xCloud AI Agent Skills, connect them to your AI assistant, and start managing your xCloud resources with simple prompts. The entire setup process takes only a few minutes.
## 📸 Watch A Quick Walkthrough [#](/docs/install-and-use-xcloud-ai-agent-skills/)
## Source [#](/docs/install-and-use-xcloud-ai-agent-skills/)
- The xCloud AI Agent Skills are open source and available on **[GitHub](https://github.com/xCloudDev/xcloud-agent-skills)** for free**.**
## Prerequisites [#](/docs/install-and-use-xcloud-ai-agent-skills/)
Before you start, make sure you have:
- An active xCloud account
- Access to the xCloud Public API
- AI Agents installed
## Supported Tools [#](/docs/install-and-use-xcloud-ai-agent-skills/)
- Claude Code
- Grok Build
- Codex
- Cursor
- OpenCode
- GitHub Copilot
- Pi
- Devin
## Collect the xCloud API Token [#](/docs/install-and-use-xcloud-ai-agent-skills/)
### Step 1: Generate an xCloud API Token [#](/docs/install-and-use-xcloud-ai-agent-skills/)
First, go to your xCloud dashboard. Navigate to the left-hand sidebar menu, select Settings, and then click on the ‘Developers’ option from the left-hand menu and click on the ‘API Tokens’ option. Within the API tokens interface, click the Create New Token button.
### Step 2: Configure Token Name and Permissions [#](/docs/install-and-use-xcloud-ai-agent-skills/)
A pop-up will appear. Enter a descriptive name for your token and select the appropriate permissions:
1. Full Access (all permissions)
2. read:servers
3. write:servers
4. read:sites
5. write:sites
Once configured, click Create Token.
### Step 3: Copy and Store Your API Token [#](/docs/install-and-use-xcloud-ai-agent-skills/)
After creation, your token will be displayed. Copy and store it in a secure location immediately, as you will need it for future authentication
## Install the xCloud AI Agent Skills [#](/docs/install-and-use-xcloud-ai-agent-skills/)
### Step 4: Access the Agent Skills Repository [#](/docs/install-and-use-xcloud-ai-agent-skills/)
Then go to the Settings → Developers option from the xCloud dashboard. Now, click on the Agent Skills from the menu.
You will be redirected to the xCloud Agent Skills documentation. You can go to the md file directly, download the md file of the skills, and use it according to your preferences.
Or, you can go to the repository; from here, you can visit our git repository to access the command to install on Claude Code.
We are going to install it using xCloud’s Agent Skills Marketplace. So go to the GitHub repository and access the command for Claude code. Copy the installation commands. You will run them inside Claude Code in the next steps.
## Configure the xCloud AI Agent Skills with Claude Chat [#](/docs/install-and-use-xcloud-ai-agent-skills/)
First, go to the Profile from your Claude, then choose Settings, and click on the Capabilities option from the menu
Then, head over to the ‘Allowed Additional Domains’ and enter the ‘app.xcloud.host’ domain in the dedicated field and click on the ‘Add. button.
Next, [download the agent skill](https://github.com/xCloudDev/xcloud-agent-skills/releases/download/v3.0.0/xcloud-agent-skill.zip,) (if you haven’t downloaded it already) zip file, then open The Claude Code and go to ‘Customize’ → ‘Skills’ and upload the downloaded file. It will automatically create the Skills in Claude.
Then go to the ‘Claude Chat’ and enter your xCloud Public API key. If you haven’t created it yet, [visit here](https://app.xcloud.host/user/api-tokens) and create an API key.Go to the Claude Chat and start asking something like that ‘Give me a server and site lists”.
_Note: We recommend entering your xCloud API token in your env file rather than directly in your chat, since anything pasted into a conversation can persist in chat history. For the most secure experience, we recommend using Claude Code_
After that, you will see the Agent Skills start working and giving you the results according to your instructions.
And that’s it: this is how easily you can manage your xCloud site through AI Agents like Claude Code or Chat easily.
## Configure the xCloud AI Agent Skills with Claude Code [#](/docs/install-and-use-xcloud-ai-agent-skills/)
### Step 5: Open Claude Code and Add Your xCloud API Key [#](/docs/install-and-use-xcloud-ai-agent-skills/)
Launch Claude Code on your machine and open a new session. Then add the xCloud API key to your environment JSON file at ~/.claude/settings.json:
```
{ "env": { "XCLOUD_API_TOKEN": "your-token-here" } }
```
Copy to Clipboard
You can update the file manually, or simply ask Claude to add the xCloud API key to the JSON file for you.
### Step 6: Install the xCloud AI Agent Skills [#](/docs/install-and-use-xcloud-ai-agent-skills/)
Run the commands below to add the marketplace, install the plugin, and reload:
```
/plugin marketplace add xCloudDev/xcloud-agent-skills
```
Copy to Clipboard
```
/plugin install xcloud
```
Copy to Clipboard
```
/reload-plugins
```
Copy to Clipboard
Once you run these commands, Claude loads the skills and connects them to the xCloud API. Restart Claude Code so it picks up the token, then confirms the connection by asking Claude, “Check my xCloud API connection.” After it finishes, your AI assistant gains access to xCloud capabilities.
### Step 7: Begin Interacting Using the AI Agent Skills [#](/docs/install-and-use-xcloud-ai-agent-skills/)
Once the skills have been installed, you can begin interacting with your xCloud infrastructure.
Ask Claude:
/xcloud:servers, tell me my servers status
You can also just say “find my servers” in plain language, and Claude loads the matching skill for you.
Then the skill connects to the xCloud Public API and retrieves the servers available in your account.
Claude will return information such as:
- Server Name
- Server Status
- Public IP Address
- Provisioning Status
- Server Identifier
All data is retrieved directly from your xCloud account in real time.
And that’s it; this is how easily you can install and set up xCloud AI Agent Skills. In just a few minutes, xCloud AI Agent Skills puts your servers, sites, and WordPress installations a single prompt away. From here, you can manage your infrastructure with plain language instead of clicks and menus. Load the skill you need, ask your question, and let the assistant handle the API calls. You can keep chatting in the same conversation to refine any result.
If you have any questions or are facing issues, feel free to reach out to our [**support team**](https://support.xcloud.host/).
## Common Use Cases [#](/docs/install-and-use-xcloud-ai-agent-skills/)
xCloud AI Agent Skills can help you with the following tasks:
- **Server management.** List your servers, check status and details, track provisioning state, manage PHP and databases, and block an abusive IP through the firewall.
- **Site management.** List the sites on a server, retrieve site information, take backups, clear cache, and manage domains and SSH access.
- **WordPress management.** Check core, theme, and plugin updates, scan for vulnerabilities, review WordPress health, check page speed, and queue updates.
- **SSL management.** Set up HTTPS, issue a free Let’s Encrypt certificate, and renew certificates before they expire.
- **Monitoring.** Track background tasks, poll events, and follow update progress to completion.
## Do AI Agent Skills cost extra? [#](/docs/install-and-use-xcloud-ai-agent-skills/)
The skills use the xCloud Public API that comes with your account, so there is no extra xCloud charge to run them. Your AI assistant may have its own usage cost from its provider. Check your assistant’s plan for those details.
### 📑 Explore the Documentation [#](/docs/install-and-use-xcloud-ai-agent-skills/)
You can also visit this [**documentation**](https://app.xcloud.host/agent/skills#description/introduction) to learn more and find more details about the xCloud AI Agent Skills.
---
# How to Install Ghost with xCloud (One Click Apps) - xCloud
> Learn how to install Ghost with xCloud using One Click Apps. Deploy your blog with Docker, Nginx, and SSL configured for you in a few steps.
Ghost is an open-source publishing platform built for blogs, newsletters, memberships, and creator websites. It is fast, clean, and focused on writing rather than page building, which makes it a strong choice for anyone who wants to publish and grow an audience without the overhead of a general-purpose CMS.
With xCloud’s One Click Apps, you can deploy Ghost without touching the server. xCloud provisions the container, configures Nginx, and issues the SSL certificate for you.
Follow the guide to install Ghost with xCloud with One Click Apps. Let’s get started.
## Step 1: Create a Docker+ NGINX Server [#](#step-1-create-a-docker-nginx-server)
First, create a Docker server to deploy Ghost. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy Ghost either on your [own server](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy the server with xCloud. You can either use an [xCloud Managed Server](/managed-hosting/) or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the ‘Server Name’, set the ‘App Type’ to Ghost(it is optional to select), and add any relevant ‘Tags’ to help identify your server later.
Next, you can see the ‘Docker + NGINX’ stack is already selected, which is mandatory for deploying the Ghost application.
Next, choose the server options based on your requirements. Then, select a plan that best fits your needs, then click the ‘Create’ button to proceed.
Once the server is created, you will be able to deploy your Ghost Application on this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## Step 2: Go to One Click Apps & Choose Ghost [#](#step-2-go-to-one-click-apps--choose-ghost)
Next, from your dashboard, click the ‘One Click Apps’ button and choose ‘Ghost’.
### Step 3: Set Up the Ghost Application [#](#step-3-set-up-the-ghost-application)
In the site setup screen, you will be prompted to enter basic site information. Provide a ‘Site Title’ and add relevant ‘Tags’ to help organize your deployment.
Here, you will see site deployment options. From here, proceed with the ‘Go Live’ option or the ‘Demo Site’ option. For Go Live you need to have a custom domain. For this tutorial we are going with the demo domain that is free from xCloud.
Once you choose the Demo site, you will see that xCloud assigns you a free demo domain. Then click on the ‘Next’ button to start deploying the application.
### Step 5: Visit the Application [#](#step-5-visit-the-application)
After completing the setup, you will be able to visit your Ghost app. From the dashboard, click the ‘Visit Site’ button to access your Ghost site.
## Step 6: Complete the Ghost Setup [#](#step-6-complete-the-ghost-setup)
One you visit the site, go to the address field and add “/ghost” at the end of your domain.
Now you get an account creation page. Enter your ‘Site title’, ‘Full name’, ‘Email address’, and a ‘Password’ and then click on the ‘Create account & start publishing’ button to proceed.
After a while you will see the account has been created. You will land in the Ghost admin dashboard, where you can see your members count, post performance, and newsletter and growth analytics. From here you can write your first post, customize your theme, and configure your newsletter.
And that’s it. This is how easily you can install and launch Ghost using xCloud’s One Click Apps. With just a few guided steps, your publication is live, fully configured, and secured with SSL. xCloud takes care of the server provisioning, Docker configuration, and deployment, so you can focus on writing and growing your audience.
Still stuck? [Contact our support team](/support/) for any of your queries.
---
# How To Easily Install Let’s Encrypt SSL Certificate - xCloud
> Here we have learned how to install Let's Encrypt SSL certificate in xCloud.
With **[xCloud](/)** you can easily install the ‘[**_Let’s Encrypt_‘ SSL certificate**](https://letsencrypt.org/) on your site without any complexity. Follow this guide to proceed further.
## **How Does Let’s Encrypt SSL Certificate Work?** [#](/docs/install-lets-encrypt-ssl-certificate/)
To enable HTTPS on your website, you need a certificate from a Certificate Authority (CA) like Let’s Encrypt. You prove domain control using [**ACME**](https://datatracker.ietf.org/doc/html/rfc8555) protocol software installed on your web host.
If you don’t have shell access (SSH) and use control panels like cPanel or Plesk, you probably can’t obtain the certificate that way. Contact your hosting provider to confirm.
You can get a free SSL certificate issued by xCloud.
## **How To Install Let’s Encrypt SSL** [#](/docs/install-lets-encrypt-ssl-certificate/)
From SSL/HTTPS option from the dashboard, you can add your Let’s Encrypt SSL certificate.
Under the Certificate Issue option, you can see your Let’s Encrypt SSL certificate has been successfully added. After that, click on the Save button to save your changes.
_Note: If you want to use our free SSL certificate from xCloud, then you have to disable other providers._ For example, you need to disable ‘**proxy**‘ from your Cloudflare DNS report.
Are you stuck? Contact our support team for more information.
---
# How To Install MariaDB With xCloud? - xCloud
> Step-by-step guide on how to install MariaDB with xCloud for a fast and reliable data access for your site.
With xCloud, you can now install [**MariaDB**](https://mariadb.org/) on servers managed by your providers like GCP, Vultr, and Hertzner, as well as on xCloud-managed servers. This allows you to achieve optimal query speed and enhanced site responsiveness with MariaDB, ensuring high performance and strong data integrity. MariaDB’s optimized engines provide fast and reliable data access for your site. Learn how to install MariaDB with xCloud.
_**\*Note:** In the upcoming release, xCloud will provide MariaDB support for AWS servers._
## How To Install MariaDB With xCloud? [#](/docs/install-mariadb-with-xcloud/)
Here, we will install MariaDB in xCloud-managed servers. Follow the step-by-step guidelines to learn how.
### **Step 1: Create A New Server In xCloud** [#](/docs/install-mariadb-with-xcloud/)
First, log in to your xCloud account and move to the **‘Servers’** tab. Click on **‘New Server’** to create a new server.
### **Step 2: Choose Hosting Managed By xCloud** [#](/docs/install-mariadb-with-xcloud/)
To set up MariaDB, you need to choose your hosting provider. Here, in this tutorial, we are choosing the hosting managed by xCloud. Scroll down and choose your hosting.
### **Step 3: Configure Server Setup** [#](/docs/install-mariadb-with-xcloud/)
Add the ‘Server Name’ and ‘Server Tag’ from the **‘Server Details’** section. Choose the **‘Server Type’, ‘Server Size’, and other details** as required.
### **Step 4: Select Database Server** [#](/docs/install-mariadb-with-xcloud/)
Now, from the **‘Database’** Section**,** select your database server. Here, choose MariaDB and click **‘Next’.**
**\*Note:** xCloud supports Maria DB version 10.6.
Following these steps, you can successfully set up MariaDB in xCloud-managed servers. You can stop or restart MariaDB from here.
In one server, you can use only one database from MySQL or MariaDB. If you want to use MariaDB in your server, you need to create a new server. And if you want to migrate your existing server from MySQL to MariaDB, you need to create a new server and clone your all the sites into that server.
_**Note:** Currently MariaDB is not available on AWS servers and ARM-based servers._
If you face any issues or need further assistance, reach out to [**xCloud support**](https://support.xcloud.host/). Our team is available to help you with any challenges you face while integrating and managing your external database.
---
# How to Install WireGuard with xCloud (One Click Apps) - xCloud
> Learn how to Install WireGuard with xCloud in minutes using One Click Apps, from server creation to VPN client setup with SSL enabled.
[WireGuard](https://www.wireguard.com/) is a modern and lightweight VPN solution that helps keep your internet traffic private and secure. It’s known for being fast, easy to use, and much simpler than traditional VPN tools.
With xCloud’s One Click Apps, setting up WireGuard doesn’t require any complicated server work or technical expertise. Follow the guide to easily install WireGuard with xCloud, which involves just a few steps.
_Note: WireGuard requires the WireGuard UDP port (default: 51820) to be open on your server firewall. If a firewall is enabled, make sure this port is allowed._
Copy to Clipboard
## Step 1: Create a Docker+ NGINX Server [#](/docs/install-wireguard-with-xcloud/)
First, you need to create a Docker server to deploy WireGuard. Click the ‘Add New Server’ button on the dashboard and enter all the necessary credentials to connect your server. You can deploy WireGuard either on your [own server](/self-managed-hosting/) or on an xCloud server.
Next, choose your server provider to deploy WireGuard with xCloud. You can either use an **[xCloud Managed Server](/managed-hosting/)** or select your preferred provider. In this guide, we’ll use the xCloud Managed Server.
Afterward, enter the **‘Server Name’**, set the **‘App Type’** to WireGuard(it is optional to select), and add any relevant **‘Tags’** to help identify your server later.
Next, choose between the ‘**General’** and **‘Premium’** options based on your requirements. Then, select a plan that best fits your needs.
Next, choose the **‘Region’** and **‘Ubuntu Version’** for your server. You can also enable or disable the Backup option as needed.
_Note: The server location you have set will be used as the VPN location._
Copy to Clipboard
Next, you can see the **‘Docker + NGINX’** stack is already selected, which is mandatory for deploying the WireGuard application. Then click on the **‘Create’** button to proceed.
Once the server is created, you will be able to deploy your WireGuard Application on this server.
After creating a server, it may take a while to become fully operational. Wait a few minutes before deploying your applications to ensure everything starts correctly.
## **How to Install WireGuard with xCloud On A Cloud Server** [#](/docs/install-wireguard-with-xcloud/)
Learn how to install WireGuard on a cloud server. It walks you through creating a server, configuring the environment, and launching your WireGuard application easily.
### **Step 2: Access the One Click Apps Dashboard** [#](/docs/install-wireguard-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the ‘New Site’ button.
Then choose your server from the dropdown menu. Next, click on the ‘Next’ button to proceed.
This will take you to the site creation interface. From here, select your Server, then navigate to the One Click Apps section. You will see ‘WireGuard’, click on it to proceed with the deployment of this application.
### Step 3: Set Up the WireGuard Application [#](/docs/install-wireguard-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
Here, you will get a site deployment option. From here, proceed with the ‘Go Live’ option to install WireGuard. This will immediately create a live environment to publish your WireGuard application instantly.
_**Note**: You will not be able to create a Demo site for WireGuard. Additionally, domains that are proxied through Cloudflare will not work with the WireGuard application. Please ensure the domain is not proxied in Cloudflare._
Copy to Clipboard
### **Step 4: Configure Domain Settings** [#](/docs/install-wireguard-with-xcloud/)
Then, enter a domain for your WireGuard application in the blank field under the **‘Domain Setup’** option.
After that, go to the **‘DNS Setup’** section and enable the **‘SSL’** option. xCloud provides a free SSL certificate for this application. You can also use your own custom SSL certificate. Here you will get a **‘Site User’** of xCloud and click on the ‘Next’ Button to continue.
## Step 4: Visit the Application [#](/docs/install-wireguard-with-xcloud/)
After completing the setup, you will be able to visit your WireGuard site. From the dashboard, click on the ‘Visit Site’ app.
## Step 5: Set Up WireGuard VPN [#](/docs/install-wireguard-with-xcloud/)
Once you are on the WireGuard VPN page, click on the **‘Continue’** button to proceed.
Next, enter a **‘Username’**, **‘Password’,** and click on the **‘Create Account’** button to proceed.
Next, enter your domain in the ‘Host’ field. You will get a default ‘Port’ and click on the ‘Continue button to proceed.
## Step 6: Create a Client [#](/docs/install-wireguard-with-xcloud/)
Next, click on the ‘New Client’ button to create a new client for WireGuard VPN.
Then enter the **‘Name’** and **‘Expiry Date’** and click on the **‘Create Client’** button to proceed.
Next to the client, you will see a way to enable or disable the client, add the client via QR code, or download the configuration file. Finally, you can even delete the client if you wish.
And that’s it. This is how easily you can install and launch WireGuard using xCloud. With just a few guided steps, your VPN server is ready to use, fully configured, and secured with SSL. xCloud takes care of the heavy lifting, so you can focus on using WireGuard without worrying about complex setup or maintenance.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Integrate And Setup Linode Server With xCloud? - xCloud
> Learn how to integrate and setup Linode server with xCloud with step by step process and create your server effortlessly.
[**Linode**](https://www.linode.com/) is a trusted cloud hosting provider known for its high-performance servers, developer-friendly platform, and cost-effective pricing. With **xCloud**, you can set up and manage your Linode server with an easy-to-use interface.
xCloud aims to simplify the process of hosting and managing WordPress sites, allowing developers and agencies to focus on building great websites without worrying about the underlying infrastructure. Now let us follow these steps to get you started.
## **Step 1: Create Your New Linode Server With xCloud** [#](/docs/integrate-and-setup-linode-server-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **‘Add New Server’** button from your server dashboard or you can add it from the Server Provider Integration Page.
The next screen will provide the list of our available server providers. Now, select the [**Linode**](https://www.linode.com/) option from there. The server billing will be handled on your Linode account.
## **Step 2: Authorize Your Linode Account** [#](/docs/integrate-and-setup-linode-server-with-xcloud/)
We have made it easier and safer for you to connect xCloud with your Linode account. Now provision a new Linode server, click **‘Authorize on Linode’** during the setup, and you will be redirected to Linode to grant permission to your account. It is a straightforward and hassle-free process to set up your server with Linode.
## **Step 3: Connect the Account & Add the Necessary Information** [#](/docs/integrate-and-setup-linode-server-with-xcloud/)
You will be taken to the server creation page after successfully integrating your Linode account and your server will be connected with xCloud. Now you need to provide the **‘Server name’**, your preferred **‘Server Size’** (CPU, RAM, storage), the **‘Region’** nearest to you and your visitors, and then select the **‘Database Server’** from MySQL and MariaDB**.**
**_Note:_** _We recommend at least a 2GB/ 1 shared CPU server for 10-20 brochure sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server._
Next, choose the web server stack from **‘NGINX’** or **‘OpenLiteSeed’** as your requirements and click on the **‘Next’** button to proceed with the server creation process.
It will start creating a Linode server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many sites as you want under this server.
This is how easily you can create an Linode server from xCloud seamlessly without going through any difficulties.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Integrate Backblaze Storage Provider For Site Backup With xCloud? - xCloud
> Learn how to integrate Backblaze storage provider with xCloud to create a secure, cost-effective site backup solution.
Backing up your website data is important for maintaining a reliable and secure cloud environment. Backblaze is a cloud storage and data backup service known for its affordability, simplicity, and security. A cost-effective object storage service, similar to Amazon S3, used for storing large volumes of data, backups, and hosting files.
In this guide, we will learn how to integrate Backblaze Storage provider with [**xCloud**](/) to set up a seamless, efficient backup solution for your site. Ready to set up Backblaze Storage in xCloud? Let’s dive into the step-by-step guide.
**_Note:_** _Backblaze provides the first 10GB of B2 Cloud Storage for FREE_
## **Steps to Integrate Backblaze Storage Provider With xCloud & Backup Site** [#](/docs/integrate-backblaze-storage-provider/)
Follow the steps below to integrate Backblaze B2 storage provider with xCloud and backup your site with ease:
### **Step 1: Create a New Storage Bucket** [#](/docs/integrate-backblaze-storage-provider/)
After logging in to your Backblaze account and go to the **‘Buckets’** page. Click on the ‘**Create a Bucket’** button and enter a unique name for your bucket. Adjust the other settings, and click on the **‘Create a Bucket’** button to create a fresh bucket.
_Note: Make sure you have chosen **‘Disable’** for the **‘Object lock’** option._
### **Step 2: Create a New Application Key** [#](/docs/integrate-backblaze-storage-provider/)
Next, we need to generate Backblaze API keys. Click on the **‘Application Keys’** button under the **‘Account’** menu to go to the API keys tab. Then hit on the
Enter a name for your key and select the bucket you created in the previous step. Choose **‘Read and Write’** as the access level, and then click on the **‘Create New Key’** button.
On the next screen, you will see the three find application credentials **‘Key ID’**, **‘Key Name’** and **‘Application key’** that you need to copy for integrate with xCloud
**_Note:_** _Do not close this tab until you copy the keys, because you will only see these keys once._
## **Configure Backblaze Storage Provider For Site Backup With xCloud** [#](/docs/integrate-backblaze-storage-provider/)
Since you have collected everything that you need from the Backblaze end, now let’s see how you can configure Backblaze storage for site backup in xCloud.
### **Step 3: Login & Access New Provider** [#](/docs/integrate-backblaze-storage-provider/)
Login to your xCloud dashboard, and navigate to **‘Team Settings’ → ‘Integrations’ → ‘Storage Provider’** & click on **‘Add New Provider.’**
### **Step 4: Select The Backblaze Storage Provider** [#](/docs/integrate-backblaze-storage-provider/)
On the resulting page, click on **‘Select Provider‘** to expand the dropdown option. And select **‘Backblaze‘** as your storage provider.
### **Step 5: Fill Up All the Necessary Information** [#](/docs/integrate-backblaze-storage-provider/)
Now, fill in your **‘Bucket Name**’, **‘Access Key ID’**, **‘Secret Key’** that you have copied in the dedicated fields.
Next go back to the Backblaze dashboard, click on the **‘Buckets’** option. Then copy the ‘**Endpoint’** from your created bucket.
Next, go back to your xCloud dashboard and paste the **‘Endpoint’** into the blank field. Once everything is done, click on **‘Submit’**.
Once you have submitted it, your Backblaze storage will be added to xCloud, you can use it for site backup. Here’s how it looks in your dashboard once it gets connected successfully.
### **Step 6: Configure Site Backups Settings in xCloud** [#](/docs/integrate-backblaze-storage-provider/)
Once the integration process is done, you can move on to backup your site. As you can integrate more than one storage provider, choose one if you have multiple. For the Remote Backup Settings, choose your Bucket.
After that, you can exclude paths if required. You will find the box below the **‘File Backup’** field as shown below.
You can also choose to schedule **‘Automatic Backup’** and **‘Automatic Delete’**. For automatic backup, you need to select backup frequency and backup time. On the other hand, you can set a value for how many days after a backup will be deleted automatically.
This is how you can easily integrate Backblaze storage provider and configurefor site backup in xCloud.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Integrate Google Cloud Storage for Site Backups in xCloud? - xCloud
> Want a secure backup solution? Integrate Google Cloud Storage with xCloud to automate site backups and keep your data safe. Follow our simple steps!
Ensuring your website’s data remains secure and accessible is vital. Once you **integrate Google Cloud Storage** for your site backups in [**xCloud**](/), you are opting for a solution that combines robustness with flexibility. [**Google Cloud Storage**](https://cloud.google.com/storage) is renowned for its top-tier security features, scalable architecture, and dependable performance.
In this guide, we will show you how to integrate Google Cloud Storage with xCloud to establish an efficient and reliable backup system.
## **Steps to Integrate Google Cloud Storage for Site Backups with xCloud & Back up Site** [#](/docs/integrate-google-cloud-storage-xcloud/)
Follow the steps below to integrate Google Cloud Storage for site backups with xCloud and back up your websites effortlessly.
### **Step 1: Add a New Storage Provider** [#](/docs/integrate-google-cloud-storage-xcloud/)
Before getting started to back up your websites with Google Cloud Storage, you need to integrate the storage provider into xCloud. For that, [log in to your xCloud account](https://app.xcloud.host/) and navigate to **Team Settings → Integrations → Storage Provider**.
Now, click the ‘**Add New Provider**’ button and choose **Google Cloud Storage** as your provider. Next, set a label/name for which a folder will be created in your Google Cloud Storage.
### **Step 2: Collect Access & Secret Keys** [#](/docs/integrate-google-cloud-storage-xcloud/)
To integrate Google Cloud Storage into your xCloud account for site backups, you need an **Access Key ID** and **Secret Key** from Google Cloud Console. To get those, log in to your [**Google Cloud Console account**](https://console.cloud.google.com/) and navigate to the Cloud Storage menu from the left bar.
Next, hit the ‘**CREATE A BUCKET**’ button and set a name for your bucket. Next, you need to choose a cloud location to store your data. You can either pick **a single location** (could be nearest to your server location) or **choose multiple or dual locations**. Once done, click the ‘Continue’ option to configure other settings.
_\[_**_Note:_** _Your storage charge depends on the number of locations and types you select and add accordingly\]_
Once done, set the storage class, control access options and project object options as per your need. Then hit the **‘Create’** button. Your bucket will be created instantly. Now, you need to get the access key and secret key. To collect those, navigate to **Settings→ Interoperability** and scroll down to the **Access Keys** section.
Here, create a new key by clicking on the ‘**CREATE A KEY**’ button. If you already have generated keys, you can collect those and use them on the xCloud end.
### **Step 3: Integrate Google Cloud Storage Provider** [#](/docs/integrate-google-cloud-storage-xcloud/)
Now that you have collected the Access keys and secret keys, you can use those keys to integrate the Google Cloud Storage providers into your xCloud account. Set the bucket name as set in the storage provider, use the access key and secret key, set the region and hit the **Submit** button.
Once integrated, you will see the Google Cloud Storage integrated and listed on the Storage Provider page in xCloud, as shown below.
### **Step 4: Configure Backup Settings for Google Cloud Storage** [#](/docs/integrate-google-cloud-storage-xcloud/)
Once you are done integrating Google Cloud Storage as a storage provider into xCloud, you can now configure ‘Backup Settings’ for taking backups with Google Cloud Storage. Now, go to sites, choose the one you want to take backup and navigate to the **Site Backup → Backup Settings**.
Now, in the ‘**Remote Backup**’ section, choose Backup Type as ‘**Full**’ or ‘**Incremental**’ and select the bucket you have just created for Google Cloud Storage. You can then choose to exclude paths if necessary (for the paths you do not want to take backup).
Then, you can also enable ‘**Automatic Backup**’ and choose the backup frequency. Plus, you have the option to use the ‘**Automatic Delete**’ option with which you can set days after when your backup will be deleted automatically. Once done, hit the ‘**Save**’ button.
### **Step 5: Take a Backup of Your Site** [#](/docs/integrate-google-cloud-storage-xcloud/)
Once you are done configuring the site backups, you can now take backups of your websites using this provider. Now, go to the **Previous Backups** of your site settings and you will see all the available remote backups and local backups.
You can take a backup of your site from here by simply clicking on the ‘**Backup Now**’ button to take an immediate backup. Your backup process will be initiated and the backup files will be shown here once done.
You can also check your **Google Cloud Storage** end. A folder will be created with the name of your backup label and your backups will be saved inside the folder there.
This is how easily you can **integrate Google Cloud Storage** for Site Backup with xCloud and take backups of your websites.
Still stuck? Contact our [support team](https://support.xcloud.host/) for any of your queries.
---
# How to Integrate Hetzner Object Storage Provider for Site Backup with xCloud? - xCloud
> Learn how to integrate Hetzner Object Storage with xCloud for secure, automated website backups in a few simple steps.
Backing up your website is essential for ensuring data security, disaster recovery, and overall peace of mind. Integrating a reliable external storage provider like Hetzner with xCloud allows you to automate and manage your backups efficiently.
Hetzner’s Object Storage with your xCloud account, enabling you to set up seamless remote backups for your site. In this guide, we will learn how to integrate the Hetzner Object Storage provider with **[xCloud](/)** to set up a seamless, efficient backup solution for your site. Ready to set up Hetzner Storage in xCloud? Let’s dive into the step-by-step guide.
## 📑 Note [#](/docs/integrate-hetzner-storage-provider/)
Hetzner Object Storage and Storage Box are two completely different services.
- xCloud supports Hetzner Object Storage for remote site backups (S3-compatible).
- xCloud does NOT support Hetzner Storage Box, as it is not S3-compatible
## **Steps to Integrate Hetzner Storage Provider with xCloud & Backup Site** [#](/docs/integrate-hetzner-storage-provider/)
Follow the steps below to integrate the Hetzner storage provider with xCloud and backup your site with ease:
### **Step 1: Create a New Storage Bucket** [#](/docs/integrate-hetzner-storage-provider/)
Once you are logged in, go to Object Storage from the dashboard and click on the **‘Create Bucket ’** option.
Select a data center region from the **‘Location’** that is near your server’s physical location. Next, input a name for your bucket (e.g., turnipjuice-media-backups) and proceed by clicking the **‘Create & Buy now’** button.
**_Note_**_: You can leave the remaining settings at their default values._
### **Step 2: Generate The Credentials** [#](/docs/integrate-hetzner-storage-provider/)
Once you have created the bucket, go to the three-dot option and click on it. A menu will appear, choose the **‘Generate Credentials’** option from here to get the credentials to connect with xCloud.
Then give a description in the blank field and click on the ‘Generate Credentials’ button to proceed to the next step.
Here, you will get the **‘Access Key’** and the **‘Secret Key’**. Copy both the credentials or you can keep the tab open and go to the xCloud site in a different tab.
## **Configure Hetzner Storage Provider for Site Backup with xCloud** [#](/docs/integrate-hetzner-storage-provider/)
Since you have collected everything that you need from the Hetzner end, now let’s see how you can configure Hetzner storage for site backup in xCloud.
### **Step 3: Select The Hetzner Storage Provider** [#](/docs/integrate-hetzner-storage-provider/)
Log in to your xCloud dashboard, and navigate to **‘Team Settings’ → ‘Integrations’ → ‘Storage Provider’** & click on **‘Add New Provider’.** On the resulting page, sselect the **‘Hetzner’** as your storage provider
### **Step 4: Fill Up All the Necessary Information** [#](/docs/integrate-hetzner-storage-provider/)
Now, fill in your **‘Bucket Name’**, choose your **‘Region’** of the bucket that you have created with Hetzner.
Next, go back to the Hetzner dashboard, copy the **‘Access ID’** and **‘Secret Key’** from your created bucket. Then, go back to your xCloud dashboard and paste the**m** into the dedicated fields. Once everything is done, click on **‘Submit’**.
Once you have submitted it, your Hetzner storage will be added to xCloud, you can use it for site backup. Here’s how it looks in your dashboard once it gets connected successfully.
### Step 6: Configure Site Backups Settings in xCloud [#](/docs/integrate-hetzner-storage-provider/)
Once the integration process is done, you can move on to backup your site. As you can integrate more than one storage provider, choose one if you have multiple. For the Remote Backup Settings, choose your Bucket.
This is how you can easily integrate Hetzner storage provider and configure it for site backup in xCloud.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Integrate Object Cache Pro with xCloud? [Easy Guide] - xCloud
> Easily integrate Object Cache Pro with xCloud to boost your WordPress site's performanc with just a few simple steps.
[**Object Cache Pro**](https://objectcache.pro/) is a premium **caching solution** designed to work efficiently with WordPress, providing faster and more reliable object caching. Integrating Object Cache Pro with xCloud can greatly improve your WordPress site’s performance by reducing database queries and speeding up page load times.
Object caching stores frequently requested data in memory, allowing WordPress to retrieve it quickly instead of querying the database repeatedly. Follow the steps below to Integrate Object Cache Pro with xCloud with just a few clicks.
## **Step 1: Go to the Integration Settings** [#](/docs/integrate-object-cache-pro-with-xcloud/)
First, log in to your xCloud account. To integrate **Object Cache Pro**, go to the top-right menu, find the **Team Settings** option and click on it. Then, go to the **Integration** option from the left-side menu and click on **Integrations→ Others**.
## **Step 2: Integrate New Item** [#](/docs/integrate-object-cache-pro-with-xcloud/)
Then, look for and click the **‘Integrate New Item’** button.Once you click the **‘Integrate New Item’** button, a popup will appear on the xCloud dashboard. Here, insert your **Object Cache Pro** credentials **‘Name’** and ‘**License’**and click on **‘Add Plugin’** button.
## **Step 3: Go to Your Site** [#](/docs/integrate-object-cache-pro-with-xcloud/)
Now, navigate to the site where you want to integrate Object Cache Pro. From the left-side menu, select the **‘Caching’** option to proceed with the integration.
## **Step 4: Integrate Object Cache Pro With Your Site** [#](/docs/integrate-object-cache-pro-with-xcloud/)
Now, scroll down slightly to find the Object Cache Pro option. Then, toggle the switch to enable it and select the account you have already integrated. You also have the option to enable Debug Mode if needed. After that, click the **‘Configure Object Cache Pro’** button, and the system will automatically configure your account with your site.
And that’s it. This is how easily you can insert Object Cache Pro with xCloud. This seamless integration helps you provide a faster and more efficient user experience for your site visitors.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Integrate SFTP Storage Provider for Site Backup with xCloud - xCloud
> Learn how to integrate SFTP storage provider with xCloud to automate and manage your website backups effortlessly.
Websites require regular backups to ensure data safety and quick recovery in case of accidental loss, server failure, or security breaches. Many users prefer storing backups on external storage systems for added security and reliability.
With xCloud, you can easily integrate an [**SFTP storage provider**](/docs/site-backups-in-xcloud/) to securely store your site backups, manage them efficiently, and automate backup schedules, all within a single platform.
In this guide, you will learn how to integrate SFTP storage provider with xCloud to set up a seamless and reliable backup solution for your site.
## **Step 1: Prepare the Backup Directory on Your SFTP Server** [#](/docs/integrate-sftp-storage-provider-with-xcloud/)
First, collect the required credentials for your SFTP user account. You will need:
- Hostname or IP address
- Port number (default is 22)
- Username
- Password
- Path (directory where backups will be stored)
Before you start integrating SFTP with xCloud, you need to make sure the backup directory has the correct permissions. Connect to your SFTP server using SSH.
Copy to clipboard
1
ssh jhon@XX.XX.XX.XX
Check the file permissions of your backup directory
Copy to clipboard
1
ls -ld /path-to/jhon-backup-test
Example output:
Copy to clipboard
1
drwxr-xr-x 2 root root 4.0K Sep 15 18:13 jhon-backup-test
Here, the directory is owned by root, which means the user arafat cannot write to it yet. Give the user full access. Run the following commands to update ownership and permissions to ensure that the user has full access to the backup directory.
Copy to clipboard
1
2
3
sudo chown -R jhon:jhon /path-to/arafat-backup-test
chmod -R 700 /path-to/jhon-backup-test
This ensures that the user has full access to the backup directory.
## **Integrate SFTP Storage Provider in xCloud** [#](/docs/integrate-sftp-storage-provider-with-xcloud/)
Once you have gathered all the required details, you can move forward with configuring the SFTP storage provider in xCloud. With this setup, your SFTP server will be connected to your xCloud account, making it possible to use it as a secure storage option for your site backups.
### **Step 2: Choose the New Storage Provider** [#](/docs/integrate-sftp-storage-provider-with-xcloud/)
To add the storage provider, go to your xCloud dashboard and go to ‘**My Profile’** from the top right menu. Then navigate **‘Integrations’** → **‘Storage Provider’** option from the sidebar menu. From there, click on the **‘Add New Provider’** button to integrate SFTP storage provider.
A pop-up will appear, where you will find all the storage integrations available to integrate with xCloud. Then, select the **‘SFTP’** as your storage provider to integrate with xCloud.
### **Step 3: Fill in the Required Information** [#](/docs/integrate-sftp-storage-provider-with-xcloud/)
Next, provide the following details in the blank fields:
- **Label:** Enter a name for your SFTP integration.
- **Host:** Enter the hostname or IP address of your SFTP server.
- **Port:** Enter the port number of your SFTP server. If left blank, the default port 22 will be used.
- **Username:** Enter the username of your SFTP account.
- **Password:** Enter the password of your SFTP account.
- **Path:** Enter the directory path where you want to store the backup files (for example: /data1/home/1234/xcloud-backup). Make sure this directory exists on your server. If you leave this blank, the default path /home/{username} will be used.
After entering all the credentials, click on the ‘Submit’ button. Once submitted, your SFTP storage will be added to xCloud. You can now use it for site backups. If the integration is successful, it will appear in your dashboard.
### **Step 4: Configure Site Backup Settings in xCloud** [#](/docs/integrate-sftp-storage-provider-with-xcloud/)
Now, in the ‘**Remote Backup’** section, choose Backup Type as **‘Full’** and select the bucket you have just created for SFTP. You can then choose to exclude paths if necessary (for the paths you do not want to take backup).
Then, you can also enable **‘Automatic Backup’** and choose the backup frequency. Plus, you have the option to use the **‘Automatic Delete’** option with which you can set days after when your backup will be deleted automatically. Once done, hit the **‘Save’** button.
This is how you can easily integrate an SFTP storage provider and configure site backups in xCloud with SFTP.
If you encounter any difficulties, feel free to reach out to our support team for assistance.
---
# How to Integrate Wasabi Storage Provider for Site Backup with xCloud? - xCloud
> Discover how to integrate Wasabi storage provider with xCloud for seamless site backups with easy steps.
Backing up your site is one of the most important steps you can take to protect your data and ensure business continuity. Data loss can occur for many reasons, such as system errors, accidental deletion, or even natural disasters. To avoid these risks, you need a reliable storage provider integrated with your backup system.
Wasabi is a high-performance cloud storage solution that offers affordable, secure, and scalable storage. When combined with xCloud, it allows you to set up a smooth and efficient backup process for your site.
In this guide, we will learn how to integrate Wasabi Storage provider with **[xCloud](/)** to set up a seamless, efficient backup solution for your site.
### **Step 1: Generate Access Key on Wasabi** [#](/docs/integrate-wasabi-storage-provider-with-xcloud/)
First, go to the Wasabi, click on **‘Access Keys’** on the left sidebar. Click on the **‘Create New Access Key**’ button.
After, you can choose **‘Root User’** or **‘Sub-User’** as you wish. Next, click on **‘Download CSV’** or **‘Copy Keys To Clipboard’** and save them.
_Note: Once you will click on the copy keys to the clipboard, you will get two keys: ‘Access Key’ and ‘Secret Key’. Store these keys securely to integrate with xCloud._
## Step 2: Create a Bucket On Wasabi [#](/docs/integrate-wasabi-storage-provider-with-xcloud/)
Next, go to the ‘Buckets’ option from the sidebar and click on the ‘Create Bucket’ option to create a new bucket for your site backups.
You need to enter a bucket name and select a region for the storage bucket, then click the Create Bucket button. Once the bucket is created, collect the region code such as ap-northeast-1 along with the endpoint URL displayed on the right side, for example s3.ap-northeast-1.wasabisys.com. These details are required for integration with xCloud.
Next, set properties for this bucket like ‘Bucket Versioning’ and enable ‘Object lock’ and click on the ‘Next’ button.
Note When Bucket Versioning is enabled, you can then retrieve and restore any previous version of an object in the bucket. Note: versions of objects are added to your total data storage costs. Enabling Object Lock will allow you to prevent objects from being overwritten or deleted for a fixed amount of time. Toggling this box will permanently enable Object lock functionality for the duration of this bucket’s existence.
Then you can enable ‘Bucket Logging’, a text log file of all access to this bucket is created in the bucket specified.
You can also enable ‘Object Replication’ to copy objects from a bucket (source) to another bucket (destination) to protect against bad actors, natural disasters, and user error.
Next, add tags to your storage bucket. Add ‘Key’ and ‘Value’ to the bucket. And click on the next button.
## Configure Wasabi Storage Provider for Site Backup With xCloud [#](/docs/integrate-wasabi-storage-provider-with-xcloud/)
Since you have collected everything that you need from the Wasabi end, now let’s see how you can configure Wasabi storage for site backup in xCloud.
### Step 3: Choose the New Storage Provider [#](/docs/integrate-wasabi-storage-provider-with-xcloud/)
Log in to your xCloud dashboard, and navigate to ‘Team Settings’ → ‘Integrations’ → ‘Storage Provider’ & click on ‘Add New Provider.’ On the resulting page, click on ‘Select Provider‘ to expand the dropdown option. And select ‘Wasabi‘ as your storage provider.
### Step 5: Fill Up All the Necessary Information [#](/docs/integrate-wasabi-storage-provider-with-xcloud/)
Now, fill in your ‘**Bucket Name’**, **‘Access Key ID’** and **‘Secret Key’** that you have copied in the dedicated fields.
Then enter the ‘Endpoint’ from your created bucket, and choose the region of the created bucket. Once everything is done, click on ‘Submit’.
Once you have submitted it, your Wasabi storage will be added to xCloud, you can use it for site backup. Here’s how it looks in your dashboard once it gets connected successfully.
### Step 6: Configure Site Backups Settings in xCloud [#](/docs/integrate-wasabi-storage-provider-with-xcloud/)
Once the integration process is done, you can move on to back up your site. As you can integrate more than one storage provider, choose ‘Wasabi’ as your storage provider, Backup type ‘Full’ or ‘Incremental and other settings as your preferences and click on the ‘Save’ button.
You can also choose to schedule **‘Automatic Backup’** and ‘**Automatic Delete’.** For automatic backup, you need to select a backup frequency and a backup time. On the other hand, you can set a value for how many days after a backup will be deleted automatically.
This is how you can easily integrate the Wasabi storage provider and configure it for site backup in xCloud.
Still stuck? Contact our [support team](https://support.xcloud.host/) for any of your queries.
---
# [Troubleshooting Guide] LiteSpeed Cache Plugin: Storage Usage - xCloud
> Learn how to fix and prevent high storage usage caused by the LiteSpeed Cache plugin on OpenLiteSpeed servers.
If you are using the LiteSpeed Cache plugin on a website hosted on an OpenLiteSpeed server, you might notice that your server storage fills up very quickly. This can happen even when you have not uploaded much content. This issue is common and usually linked to how the caching system handles temporary files.
It is important to understand why this happens and how to manage it so that you can maintain a healthy website and avoid unexpected storage issues.
## **Why Is Server Storage Filling Up?** [#](/docs/litespeed-cache-plugin-storage-usage/)
You might be surprised when your disk space fills up faster than expected. The reason is usually related to how LiteSpeed Cache manages files. One of the main causes is the **CSS/JS Combine** feature. This feature creates new cache files every time a page loads. If your theme or plugins use randomised or dynamic asset names, the number of these files grows quickly. Each variation results in a new file, which adds up fast. Over time, this leads to high disk usage, even if the actual website content remains the same.
## **Who Is Most Affected?** [#](/docs/litespeed-cache-plugin-storage-usage/)
Websites on smaller hosting plans are more likely to have issues. For example, if your plan offers only 25GB of storage, your site can quickly run out of space. Sites with high traffic are at greater risk. When more users visit your site, more cached files are created. If your site is not optimized well, these files can accumulate unchecked. This can hurt performance and may lead to downtime if the server runs out of space.
## **How Can You Fix It?** [#](/docs/litespeed-cache-plugin-storage-usage/)
If your storage is already running low, there are steps you can take to fix it. You can start with a temporary fix and then apply long-term solutions to prevent the problem from returning.
### **Temporary Fix** [#](/docs/litespeed-cache-plugin-storage-usage/)
To fix the issue temporarily, you can clear the cache folder manually. This involves deleting the files directly from your server. You can also do it using the LiteSpeed Cache plugin by selecting the “Clear Cache” option in the plugin settings.
### **Permanent Fix** [#](/docs/litespeed-cache-plugin-storage-usage/)
For a more permanent solution, you need to adjust your caching settings. First, disable the CSS/JS Combine feature. This will reduce the number of temporary files generated. Then, exclude any files with dynamic or randomized names from being combined. These files tend to cause excessive cache growth. Finally, review all optimization settings in the plugin. Make sure they suit your site’s actual needs and traffic level.
## **Should You Upgrade Your Server?** [#](/docs/litespeed-cache-plugin-storage-usage/)
If your site continues to grow, or if you are running a production website with frequent updates and high traffic, it might be time to upgrade your server. A higher-tier hosting plan with more disk space and better resources can handle more cached files and prevent similar issues in the future. An upgrade also provides more stability and performance for your visitors.
If you want to understand this issue better or follow advanced troubleshooting steps, you can read the official documentation provided by LiteSpeed:
👉 [**CSS/JS Issues – LSCache for WordPress**](https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/#disk-space-filling-fast)
If you are not sure how to adjust the plugin settings or if the issue keeps coming back, you should reach out to your hosting provider’s [**support team**](/support/)**.** If you are using xCloud as your host, please contact our support team to assist you directly.
---
# Magic Login In xCloud: Login To Your WordPress Sites As Your Admin User - xCloud
> Follow this guide to explore the Magic Login feature from xCloud.
**Magic login** is a term used to describe a type of login process that provides a seamless and effortless authentication experience for users.
Our login method in [**xCloud**](/) enhances security and user experience. It eliminates the need for users to remember and manage passwords, reducing the risk of password-related security breaches. Additionally, it simplifies the login process, making it more convenient and user-friendly.
## **How Magic Login Works In xCloud?** [#](/docs/magic-login-in-xcloud/)
xCloud’s magical login feature simplifies accessing your **[WordPress](https://wordpress.org/)** admin with a hassle-free process. Say goodbye to password-related concerns and enjoy a more straightforward way to log in. To get started, click the “**Magic Login**” button. This action triggers the magic login process, and you’ll be securely logged in to your WordPress admin with a single click.
## **How To Disable Magic Login?** [#](/docs/magic-login-in-xcloud/)
With xCloud, you have the option to disable the Magic Login feature directly from your dashboard. The option is available under **Server > Settings** page. Disabling this will remove Magic Login feature from all the sites under this server.
That’s how this feature works. Now you can start working on your website, customize it, install themes/plugins (if applicable), and take advantage of xCloud’s optimized server environment for seamless site management.
Still stuck? Contact our **support team** for any of your queries.
---
# How To Manage And Update WordPress Core, Themes, & Plugins In xCloud? - xCloud
> Follow the documentation to learn how to manage and update WordPress core, themes, and plugins in xCloud.
**[xCloud](/)** allows you to easily manage and update WordPress core, themes, and plugins directly from the xCloud dashboard, which requires only a few steps.
## Steps To Manage And Update WordPress Core, Themes, and Plugins In xCloud [#](/docs/manage-and-update-wordpress-core-themes-in-xcloud/)
Follow the quick step-by-step guide below to learn how you can manage and update WordPress core, themes, and plugins in xCloud.
## Step 1: Navigate to the Your Site [#](/docs/manage-and-update-wordpress-core-themes-in-xcloud/)
First, log in to your xCloud dashboard. On the top right menu, navigate to your site from the dashboard. Then find the **‘WordPress’ → ‘Updates’** option from the sidebar.
## Step 2: Update Plugin, Themes, and Core Files [#](/docs/manage-and-update-wordpress-core-themes-in-xcloud/)
Access the updates dashboard, where you can find and update all your plugins, themes, and core files easily.
Next, go to the **‘WordPress Core’** section. Click on the version you want to update from the dropdown easily, and update in just a few clicks.
## Step 3: Rollback Plugin, Themes And Core Files [#](/docs/manage-and-update-wordpress-core-themes-in-xcloud/)
You can also roll back to your preferred version. Click on the rollback option, choose your desired version, enable the backup option, and then click “Rollback.”
Once you click, it will instantly roll back to the previous WordPress core version within a few minutes.
## Step 4: Activate & Deactivate Plugin, Themes, and Core Files [#](/docs/manage-and-update-wordpress-core-themes-in-xcloud/)
Now, select the plugin you want to ‘Activate’, ‘Deactivate’, or ‘Update’. Just click on ‘Activate,’ and the plugin will be activated on your website. Similarly, you can deactivate or update any plugin or theme as needed. These options can be performed separately for each of the plugin or theme or you can check multiple plugins or themes to do these actions all at once.
You can also roll back to your preferred version as well. Click on the rollback option, choose your desired version, enable the backup option, and then click “Rollback.” It will instantly work on rollback
Thus, you can manage and update WordPress core, themes, and plugins easily in xCloud.
To make updates easier, you can manage all your WordPress core, plugin, and theme updates from one place using the Updates Manager. Read the **[documentation](/docs/manage-wordpress-updates-with-updates-manager/)** to learn more.
Getting stuck? Feel free to **[contact our support](/contact/)** team for further assistance.
---
# How to Manage WordPress Updates Easily with Updates Manager - xCloud
> Easily update WordPress plugins, themes, and core files across all your sites with xCloud’s Updates Manager in just one click.
WordPress updates are an important step to keep your sites secure and running smoothly. With xCloud, you do not need to log in to each site separately; everything can be managed from one dashboard.
You can update plugins, themes, and even WordPress Core with just a single click. Follow the steps to access the Updates Manager in xCloud and update plugins, themes, and WordPress Core files easily
## **Step 1: Navigate to the Updates Manager** [#](/docs/manage-wordpress-updates-with-updates-manager/)
First, log in to your xCloud dashboard. On the top right menu, navigate to the **‘Updates Manager’** option from the dashboard. Click on that to access the updates manager dashboard, where you can find and update all your site plugins in just a click.
## **Step 2: Check the Updates Manager** [#](/docs/manage-wordpress-updates-with-updates-manager/)
Once you are in the **‘Updates Manager’** dashboard, you will see an overview of WordPress updates available in the server and sites for this team. Here you will get **‘Plugins’, ‘Themes’, ‘WordPress Core’,** and **‘Update History’.** Here, you can see the total required number of updates, plugins, Themes, and WordPress Core files.
## **Step 3: Choose What to Update** [#](/docs/manage-wordpress-updates-with-updates-manager/)
Next, navigate to the left sidebar and find options for **‘Plugins’, ‘Themes’, ‘WordPress Core’,** and **‘Update History’.**
## **Step 4: Update Plugins** [#](/docs/manage-wordpress-updates-with-updates-manager/)
For example, we are updating the plugins here. To update plugins, go to the Plugins tab. Inside the Plugins section, you will notice that plugins are organized into different categories. These help you understand the current state of each plugin:
- **All** – Shows all plugins regardless of status
- **Update Available (10)** – Lists plugins with pending updates
- **Active (17)** – Displays currently active plugins
- **Inactive (15)** – Shows deactivated plugins
These categories make it easier for you to filter and focus on specific types of plugins during updates.
There, you will see a full list of your plugins. You can use the search bar at the top to quickly find a specific plugin if you need to. Once you have located the plugins you want to update, select them.
After that, choose the websites where you want the updates to be applied. You can pick just one site, a few of them, or all of them. When you are ready, click on the **‘Update Selected**‘ button.
xCloud will take care of the rest and apply the updates to all selected sites at once. This saves a lot of time and avoids the hassle of updating each site manually.
## **Step 5: Update Themes and WordPress Core** [#](/docs/manage-wordpress-updates-with-updates-manager/)
Now, to update the **‘Plugins’** of your sites, go to the **‘Plugins’** → **‘Updates Available’** tab and select the **‘Sites’** you want to update and click on the **‘Update Selected’** button.
Just like with plugins, you will see a list of items that can be updated. Select the themes or core files that need to be updated, choose the websites where you want to apply the changes, and click Update Selected. Everything will be updated in just one step, and you can be sure that your sites are using the latest versions.
## **Step 6: View Your Update History** [#](/docs/manage-wordpress-updates-with-updates-manager/)
After your updates are complete, you can go to the **‘Update History** tab to see a record of everything that was done. Here, you will get the details of **‘Date’, ‘Time’** and the websites where updates were applied, and a list of updated files. If you want to see more details, you can click the **‘See Details’** button for more information. You can also filter the history by timeframe, which is helpful if you want to check what was updated recently or during a specific week or month.
And that’s it. This is how easily you can update your WordPress sites, which is a smart way to save time and reduce effort with xCloud.
Still stuck? Contact our [support team](https://app.xcloud.host/support/all-tickets) for any of your queries.
---
# How to Manually Upload WordPress Websites With SFTP on xCloud - xCloud
> Learn how to upload larger than 500 MB files to create WordPress sites with complete freedom.
If you want to manually upload a WordPress website, with [**xCloud**](/), you can manually upload WordPress Websites On xCloud without any hassle. Follow the step-by-step guide below to get started and upload WordPress websites with SFTP easily:
## Prerequisites to Manually Upload WordPress Websites with SFTP on xCloud: [#](/docs/manually-upload-wordpress-websites-with-sftp/)
- Disable 2FA if there are any.
- Disable additional security like Cloudways Bot protection, OR Site Grounds Security optimizer from your hosting end.
- Uninstall Must use plugins of hosts.
- Clear Cache and disable cache plugins like Object Cache PRO
- Disable Wordfence or any other security plugins.
## Step 1: Create A New Site [#](/docs/manually-upload-wordpress-websites-with-sftp/)
First, you have to log in to xCloud with your credentials. Then click on ‘New Site’ from the xCloud dashboard.
After that, you have to choose your server to upload your site. Click on the **‘Choose Server’** field and select your server from the drop-down and before clicking on the **‘Next’** button.
Now, you will be redirected site creation dashboard. Click on the **‘Manually Upload WordPress Website’** option.
## Step 2: Add Information To Manually Upload WordPress Website [#](/docs/manually-upload-wordpress-websites-with-sftp/)
Now, select the **‘Migrate to a New Domain’** option to deploy your manually uploaded site with a custom domain. Fill in the **‘Site title’**, **‘Domain Name’** and **‘DNS Setup’** in the necessary fields and click on the next button to proceed.
Here we are creating a demo site. Choose the **‘Demo site’** option and click on the **‘Next’** option.
## Step 3: Configure & Install Your Demo Site [#](/docs/manually-upload-wordpress-websites-with-sftp/)
Now, you will be sent to the **‘Settings’** step. Make sure to correctly add your ‘**PHP Version’**, **‘Site User’**. Enable or disable the **‘Full Page Caching’, ‘Redis Object Caching’ for this site.** And if you do not want to index this site in Google then click on the check box to deindex this site.
Next, you choose **‘Add Your Existing Database’** to add your existing database or choose **‘Create Database in Server**’ to create a new database for this site.
## **Step 4: Upload Your Site by SFTP/SSH** [#](/docs/manually-upload-wordpress-websites-with-sftp/)
Now, you will get two options, one for **‘Upload from Browser’** and another for **‘Upload Using SFTP/SSH’.** Choose the **‘Upload Using SFTP/SSH’** from here and click on the **‘Generate Credentials’** button to
Once the credentials are generated, you will get the **‘Sever Address’, ‘Password’ ‘Username’, ‘Port’, ‘Uploaded Path’.**
Now copy the **‘Server Address’, ‘Username’, ‘Password’** and **‘Port’** and go to the SFTP client dashboard. Then enter the credentials in the dedicated fields and click on the **‘Quick Connect’** button.
Then upload your site file to the **‘Uploaded path’** provided in the xCloud dashboard, and update the database file into the ‘db’ folder using the SFTP client.
And go back to the xCloud dashboard and click on the check box, if you have uploaded both the site and database, then hit the **‘Verify Upload’** button. Then click on the **‘Next’** button.
## Step 5: Complete the Site Upload [#](/docs/manually-upload-wordpress-websites-with-sftp/)
Now, if you are ready to go for uploading an existing WordPress website with xCloud, click on the **‘Start’** button. Within a few moments, your WordPress website will be uploaded to xCloud automatically. You will see the following screen while uploading. Once the migration is successfully complete, you will see the following screen. You go to the site dashboard from there.
After a while your site will be ready and you can visit right from the dashboard. This is how easily you can create your WordPress site manually with xCloud.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How To Easily Migrate A Website With Migrate Guru Plugin In xCloud? - xCloud
> Learn how you can easily and successfully migrate a website with Migrate Guru plugin in xCloud using a few, simple steps.
With xCloud, you can easily migrate a website with Migrate Guru plugin and bring your WordPress website to a new hosting platform and manage your website with ease
The Migrate Guru is a free WordPress plugin that simplifies the process of migrating or transferring your website between hosting providers. Widely known for its reliability and efficiency, it is a recommended plugin by many web-building professionals.
It is also completely compatible with [**xCloud Hosting**](/), making it easy for anyone to migrate a website with Migrate Guru plugin in a few steps.
## Prerequisites To Migrate A Website With Migrate Guru: [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
- Disable 2FA if there are any.
- Disable additional security like Cloudways Bot protection, OR Site Grounds Security optimizer from your hosting end.
- Uninstall Must use plugins of hosts.
- Clear Cache and disable cache plugins like Object Cache PRO
- Disable Wordfence or any other security plugins.
## How To Migrate A Website With Migrate Guru? [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
To learn how you can migrate a website with Migrate Guru plugin to xCloud, follow the step-by-step guide below:
### **Step 1: Create A Destination Website In xCloud** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
To get started, log in to your xCloud account and create a **‘Destination’** website or **‘Demo Site’**. [**Follow this documentation**](/docs/how-to-create-a-site-with-xcloud/) to learn how easily you can create a demo site.
### **Step 2: Install The Migrate Guru Plugin** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
Afterward, you need to install the [**Migrate Guru plugin**](https://wordpress.org/plugins/migrate-guru/) on both your Development site that you want to migrate and your Destination site.
To do so, log in and navigate to your WordPress website dashboard. From here, head over to the **‘Plugins’** option from the side panel and search for ‘**Migrate Guru**’ to install and activate it on your site.
**Note:** You need to install and activate the Migrate Guru plugin on your source website, too. You will need to come back to the development/source site in step 4.
### **Step 3: Collect Migration Key From Destination Site** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
Once the Migrate Guru plugin is activated on your sites, you will need to retrieve the ‘Migration Key.’ This key is unique to each migration and is required to **_connect your development site with your destination site_**.
To obtain the migration key, go to your destination website in xCloud and navigate to the Migrate Guru plugin tab. Click on the **‘Migration Key’** text link that appears on the dashboard and copy the key provided, as shown below.
**Note:** You will need to paste this key in the appropriate field on your development site later in the migration process.
### **Step 4: Migrate Your Source Website** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
Enter your email address for notification at your source website and click on the **‘Migrate Site’** button.
### **Step 5: Select The Host You Are Migrating To** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
You will be redirected to a screen where you have to select your destination hosting source. Scroll to the bottom and click on the ‘Other Hosts’ optin.
### **Step 6: Enter The Migration Key To Your Source Site** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
On the next screen, enter the migration key you had retrieved from the Migrate Guru plugin on your xCloud destination website earlier, and click on the ‘Migrate’ button to get started.
This will instantly start migrating your development website to your destination website on xCloud.
### **Step 7: Log In With Your Source Website’s Credentials** [#](/docs/migrate-a-website-with-migrate-guru-plugin/)
Once the migration is complete, you can navigate back to xCloud and see your source site transferred to the new destination. Please note that you will need the **login credentials from your source website** to enter the wp-admin panel of your migrated website.
And that’s it; this is how you can easily migrate a website with Migrate Guru in xCloud.
Still stuck? Contact our [support team](http://support@xcloud.host) for any of your queries.
---
# How To Migrate An Existing WordPress Website In xCloud? - xCloud
> Here we have learned how to log migrate an existing WordPress website with xCloud.
With [**xCloud**](/), you can easily migrate an existing **[WordPress](https://wordpress.org/download/)** website without any complexity at all. Let’s follow this guide to get started.
## **Prerequisites To Migrate An Existing WordPress Website In xCloud:** [#](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
- Disable 2FA if there are any. \[only do this if your token migration fails\]
- Disable Cloudflare Bot Fight Mode and any other higher security features of it. \[only do this if your token migration fails\]
- Disable additional security like Cloudways Bot protection, OR Site Grounds Security optimizer from your hosting end. \[only do this if your token migration fails\]
- Clear Cache and disable cache plugins like Object Cache PRO
- Uninstall Must use plugins of hosts.
- Disable Wordfence, Malcare or any other security plugins.
## **Step 1: Create A New Site** [#](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
First, you have to log in to xCloud with your credentials. Then click on ‘**Add New Site**’ from the xCloud dashboard.
After that, you have to choose your server to add the site. You can either create a new server or use your existing one.
Now, you will be redirected to the site creation dashboard. Click on the ‘**Migrate An Existing WordPress Website**’.
## **Step 2: Add Information To Migrate An Existing WordPress Website** [#](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
Here, simply select the destination server to migrate your site.
On the domain page, you need to add your source site URL. And if you choose to migrate to a new domain you can include your custom domain. xCloud offers a demo site environment and with it, you can migrate your site and visit it live with a temporary domain.
After successful migration, you may update the site with your custom domain later.
In this tutorial, we will be working on a demo site.
_**Note:** It is advisable to migrate your website to a temporary domain initially to ensure everything functions correctly. Following this, you can smoothly transition your temporary domain to a live one and launch your site._
Now we will be on the ‘**Settings**’ page. Make sure to correctly add your **PHP Version**, Prefix, **Site Users,** and much more and click on the **‘Next’** button
### **Step 3: Add Plugin File & Authentication Token To WordPress Site** [#](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
You will be directed to the plugin page. Just download the plugin file and copy the code to paste it to your WordPress site.
Now go to your WordPress website and add the migration plugin you have just downloaded. After that paste the access token you have copied from the Plugin tab. You can see in the following picture that the plugin has been successfully installed and the code is added.
After all the changes check the box by agreeing that you have added the token in your site and click on the ‘Next’ button to save all your progress.
### **Step 4: Complete Database Settings & Finalize** [#](/docs/migrate-an-existing-wordpress-website-in-xcloud/)
In the ‘**Database**’ tab you can configure your preferred database setup. You can either migrate all database tables or only the file systems.
After that, you are good to go for migrating an existing WordPress website with xCloud.
This is how you can easily migrate an existing WordPress website with ease.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Migrate from Cloudways to xCloud (Full Server Migration)? - xCloud
> Moving your WordPress sites from Cloudways to xCloud is now seamless with xCloud's Cloudways Full Server Migration provider. You can migrate all
Moving your WordPress sites from Cloudways to xCloud is now seamless with xCloud’s **Cloudways Full Server Migration** provider. You can migrate all your WordPress sites in bulk — without root access, without manual database exports, and without touching each site individually.
xCloud handles site discovery, file transfer, database migration, and search-replace automatically. You only need your **Cloudways Master Credentials** to get started.
## Why Migrate from Cloudways to xCloud? [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Cloudways is a managed platform — they control the server environment and limit what you can do. When you migrate to xCloud, you get:
- **Full server control** — root access, custom configurations, no platform lock-in
- **Transparent pricing** — pay for your VPS directly, not a markup on top of it
- **Bring your own server** — use Vultr, DigitalOcean, Hetzner, AWS, or any VPS provider
- **No per-site fees** — manage unlimited sites per server on one flat license
## Prerequisites [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Before starting the migration, make sure the following are ready:
- **A destination server provisioned in xCloud** — To migrate your sites to xCloud, you need an already deployed server where your sites can be hosted. You can also create a new server to migrate your sites from Cloudways
- **Cloudways Master Credentials** — SSH username and password (not your Cloudways account login). You’ll find these in your Cloudways dashboard under **Server → Master Credentials**.
- **Destination server storage** — ensure at least **1 GB of free space** more than the total size of your sites on Cloudways.
- **Disable caching plugins** — disable Object Cache Pro, Redis, or other caching on source sites before migration.
- **Disable security plugins** — temporarily disable Wordfence or similar security plugins on source sites.
- **Clear all caches** on source sites before starting.
> ⚠️ **Note:** Unlike regular Full Server Migration, you do **not** need root access to your Cloudways server. Cloudways manages SSH authentication through their own dashboard — xCloud handles this automatically when you select the Cloudways provider.
## How to Get Your Cloudways Master Credentials [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Your **Master Credentials** are the SSH login details for your Cloudways server — not your Cloudways account email/password.
Log in to your **[Cloudways dashboard](https://platform.cloudways.com/)**. Go to **Servers** and click on the server you want to migrate from.
Click the ‘**Master Credentials**‘ tab.
You’ll see:
- **Username** — your Cloudways SSH master username.
- **Password** — your master SSH password.
Keep these handy. You’ll enter them in xCloud in the next step.
## Step 1: Start Full Server Migration & Select Cloudways [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Go to **xCloud** Dashboard, click on the **‘Add New Site’ →** choose a server, the n click on the ‘Migrate **Full Server’** under the WordPress tab.
Next you will find differnet server providers options. Choose ‘Cloudways’ provider from the **‘Source’** page.
## Step 2: Enter Your Cloudways Server Credentials [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Once you select Cloudways as the provider:
1. **IP Address** — enter the public IP address of your Cloudways server (found in Cloudways dashboard → Servers)
2. **Port** — leave as `22` (default SSH port)
3. **SSH Username** — enter your Cloudways **Master Credentials username** (e.g. `master_abc123`)
💡 Unlike regular Full Server Migration, where the username is locked to `root`, Cloudways requires your master username. The username field is editable when Cloudways is selected.
4\. **Authentication** — automatically set to **Password** (public key option is hidden for Cloudways, since Cloudways manages SSH keys through their own dashboard)
5\. **Password** — enter your Cloudways **Master Credentials password**
1. Click **Next** to verify the connection and proceed to the next steps.
xCloud will connect to your Cloudways server and automatically discover all WordPress installations under your Cloudways applications directory.
## Step 3: Select the Sites to Migrate [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
After a successful connection, xCloud scans your Cloudways server and lists all WordPress sites.
**Select** the sites you want to migrate — you can select all or choose specific ones. Click **Next** to proceed.
## Step 4: Choose Migration Mode — Go Live or Demo [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
For each site, choose how you want it to land on xCloud:
- **Go Live**– Migrates directly to the same domain, point your DNS to xCloud when ready
- **Demo Site**: Creates a site using an xCloud demo domain.
Toggle your preferred option for each site and click **on Next button to start migration**.
> ⚠️ Make sure your destination server has at least **1 GB free storage** beyond your total site sizes. Check **Server Overview → Disk Usage** before starting.
## Step 5: Wait for Migration to Complete [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Next verify the informations and click on the the ‘Start’ button.xCloud handles the entire migration process automatically:
1. **File transfer** — rsyncs all site files from Cloudways to xCloud
2. **Database export** — dumps the database from Cloudways (`mysqldump` with managed hosting compatibility)
3. **Database import** — imports into the new server’s MySQL/MariaDB
4. **Search & Replace** — updates URLs in the database if domain or path changes
Migration time depends on the total size of your sites. You’ll see real-time progress in the xCloud dashboard.
## Step 6: Verify & Go Live [#](/docs/migrate-from-cloudways-to-xcloud-full-server-migration/)
Once migration is complete:
1. Test your sites using the **Demo URL** (if you chose Demo mode) or by editing your local `hosts` file
2. Verify content, images, plugins, and functionality look correct
3. When ready, **point your DNS** to your new xCloud server’s IP address
4. SSL certificates are automatically provisioned by xCloud after DNS propagates
And that’s it this is how easily, you can migrate your sites from Cloudways easily.
Still stuck? Feel free to reach to our [support team](http://support.xcloud.host/).
---
# How to Migrate from Ubuntu 20.04 to Ubuntu 24.04 with xCloud - xCloud
> Migrate from Ubuntu 20.04 to Ubuntu 24.04 using xCloud's full server clone feature. Learn how to upgrade smoothly with our step-by-step guide.
As Ubuntu 20.04 reaches its official end-of-life on **May 31, 2025**, it is essential to begin migrating your servers and applications to a supported version.
If you want to migrate from Ubuntu 20.04 to Ubuntu 24.04, you cannot upgrade your operating system in place because each version of Ubuntu has a different stack architecture. Automated upgrades do not work because of differences in dependencies and package compatibility.
Rather, with xCloud, you can create a new server with the updated Ubuntu version and use the full server clone feature to clone your entire existing server.
👉Follow the step-by-step instructions to _[clone a full server with xCloud?](/docs/how-to-clone-full-server-with-xcloud/)_
That’s it! You can successfully migrate from Ubuntu 20.04 to Ubuntu 24.04 with xCloud.
## Frequently Asked Questions [#](/docs/migrate-from-ubuntu-20-04-to-ubuntu-24-04/)
### **Can I upgrade my current server from Ubuntu 20.04 to 24.04 in place?** [#](/docs/migrate-from-ubuntu-20-04-to-ubuntu-24-04/)
We do not recommend upgrading your current server. Instead, create a new server with Ubuntu 24.04 and move your data there. Upgrading the existing server can cause problems because of significant changes in the system. To make migration easy, use xCloud’s full server clone feature.
Still stuck? Contact our [support team](/support/) for any of your queries.
---
# How to Migrate MySQL Database to MariaDB with xCloud - xCloud
> Learn how to migrate MySQL database to MariaDB with xCloud.
To migrate MySQL database to MariaDB with xCloud, you will need to create a new server with MariaDB. Then clone your current sites to your newly created server with MariaDB. Learn how to [clone site under same/different server](/docs/clone-site-under-same-different-server-in-xcloud/) in xCloud.
---
# How To Migrate Sites From cPanel To Managed Hosting At xCloud? - xCloud
> Upgrade your web hosting experience today. Migrate sites from cPanel to managed hosting! Move to xCloud for better performance and managed hosting benefits.
**cPanel** provides a user-friendly platform for managing website files and databases for many website owners. But as your website grows and traffic demands increase, you might want to consider upgrading to a managed hosting solution. Fortunately, [**xCloud Host**](https://xcloud.host/') is here to help you with all that, providing you with a simple and seamless way to migrate sites from [**cPanel**](https://cpanel.net/) to managed hosting.
Follow this step-by-step guide to learn how to **migrate sites from cPanel** to managed hosting at xCloud.
## **Step 1: Generate Backup In cPanel** [#](/docs/migrate-sites-from-cpanel-to-xcloud/)
Before getting started, you need to create backups in cPanel by navigating to **Files → Backup**. You will need to have a full account backup. So, hit the ‘**Download a Full Account Backup**’ button.
Here, you will see if you have any previous backups available. Plus, you can also generate a new full backup file. Choose one of the backup destination options and **provide your email address** if you want a notification to your email once the backup is ready. You can also choose not to get an email notification. Once done, hit the ‘**Generate Backup**’ button below.
Now, you are all set to generate and collect API tokens from cPanel to start migrating.
## **Step 2: Collect API Tokens From cPanel** [#](/docs/migrate-sites-from-cpanel-to-xcloud/)
To create and collect API tokens in cPanel for performing the migration process, **log in** to your cPanel account dashboard and navigate to **Security → Manage API Tokens**.
Now, you need to create a new token by tapping the ‘**Create**’ button. Provide a token name, choose whether you want to set an expiry date, and tap the **‘Create’** button.
The API token will be generated instantly. Copy the API token and save it for later purposes. Once done, press the ‘**Yes, I Saved My Token**’ option.
## **Step 3: Migrate Sites From cPanel To xCloud** [#](/docs/migrate-sites-from-cpanel-to-xcloud/)
Log in to your xCloud account and open your server where you want to migrate sites from cPanel. Now, hit the **‘+New Site’** to add a new site. On the next screen, select the ‘**Migrate Full Server**’ option.
At xCloud, you will have two options for migrating sites from cPanel:
- cPanel API
- Upload the Full Backup File
We recommend using the cPanel API method as it is the more convenient option. It offers a hassle-free migration without downloading and uploading a large backup file with multiple sites. Plus, with API, everything will be done on the server end.
We will be showing you the process of migrating with cPanel API.
Select the ‘**cPanel API’** option. Then, input cPanel username, cPanel API key you collected, and cPanel host.
You will find the cPanel username on the cPanel dashboard, as shown below. Also, the host can be found in the web page URL along with the port.
Now, after providing this data, hit the ‘**Fetch Existing Backups**’ button. You will now see a list of existing backups. Select the one you need, and hit the **‘Next’** button.
## **Step 4: Select Your Sites** [#](/docs/migrate-sites-from-cpanel-to-xcloud/)
On the next screen, you will need to select sites from the available ones. If you select all, all your WordPress sites will be selected. You can also choose individual sites. Once done, hit the **‘Next’** button.
## **Step 5: Select Domains & Start Migration** [#](/docs/migrate-sites-from-cpanel-to-xcloud/)
Here, you can choose to make domains either staging or live. However, you can change it to live sites later. So, we recommend making your sites as staging for now in this step. Now, go **‘Next’**.
Now, on the next screen, you will see an overview of all the details of your actions regarding to the sites. You can edit the details for individual sites here. Once done and you are ready to migrate sites, hit the **‘Start’** button. Your migration may take a few minutes to complete, depending on your site settings and file size.
That is how easily you can migrate sites from cPanel to managed hosting at xCloud.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Monitor System Processes Using htop Command [Step-by-Step Guide] - xCloud
> Learn how to monitor and troubleshoot system processes with the htop command in this step-by-step guide
The **htop** **command** is a user-friendly, interactive tool that provides a real-time view of your system’s performance, particularly processes, CPU, and memory usage. It is more visually intuitive compared to the top command, with its color-coded display and easy-to-use keyboard shortcuts.
In this guide, we will cover **two methods** on how to use htop to monitor and troubleshoot system processes, including **MySQL** resource usage and website traffic management. We have also incorporated the ability to restart **MySQL** or the server through the **xCloud dashboard**.
## **What You Can Monitor with htop:** [#](/docs/monitor-system-processes-using-htop-command/)
When you launch htop, you gain access to critical system metrics that can help diagnose performance issues:
- **CPU Usage**: Displayed for individual cores, showing the load each is handling.
- **Memory Usage**: Details on how your RAM is being used, including buffers and caches.
- **Swap Usage**: Displays swap memory, which is disk space used as virtual RAM.
- **Process Count**: Shows the number of tasks, threads, and active processes.
- **Load Averages**: Provides 1, 5, and 15-minute averages of CPU load.
- **System Uptime**: Shows how long the server has been running.
- **Active Processes**: Displays details such as process ID (PID), user, memory, and CPU usage for each process.
## **Method 1: Monitoring MySQL Processes And System Resources Using htop** [#](/docs/monitor-system-processes-using-htop-command/)
In this method, you will explore how to monitor website activity and analyze system resources through the htop command. This comprehensive approach will guide you in identifying traffic patterns, managing server performance, and addressing issues related to plugins or themes that may affect your website’s operation.
### **Step 1: Connect to Your Server Via SSH** [#](/docs/monitor-system-processes-using-htop-command/)
First, you have to create sudo users with sudo access to run commands as the root user, helping you manage the server effectively. To create sudo users and connect your server via SSH, read this documentation: [Understanding Sudo Users And Site Users In xCloud.](/docs/usudo-users-and-site-users-in-xcloud/)
### **Step 2: Run the htop Command** [#](/docs/monitor-system-processes-using-htop-command/)
Once connected to your server, type htop in the terminal and press Enter. The htop interface will open, displaying real-time system metrics like CPU usage, memory, swap usage, and active processes.
### **Step 3: Navigating htop** [#](/docs/monitor-system-processes-using-htop-command/)
You can interact with the htop interface using keyboard shortcuts. Press F3 to search for specific processes (for example, type “mysql”), F6 to sort by CPU, memory, or other metrics, F9 to kill a specific process, and F10 to exit htop.
#### **Step 4: Access Database Details via xCloud Dashboard** [#](/docs/monitor-system-processes-using-htop-command/)
To monitor database activity more effectively, log in to the xCloud dashboard and navigate to your site and find **Access Data** → **SFTP** option from the menu. Here, you can find details about where to access the database for the site.
_**Note**: During server provisioning, we send the root password for the database/MySQL to your email. Use these credentials to access and manage the database as needed._
### **Step 5: Check MySQL Resource Usage** [#](/docs/monitor-system-processes-using-htop-command/)
In the htop interface, search for MySQL processes. Use the F3 key to quickly locate them by typing **“mysql”** in the search bar. If you notice high CPU or RAM consumption, there may be problematic MySQL queries or table locking issues.
### **Step 6: Check Active MySQL Queries** [#](/docs/monitor-system-processes-using-htop-command/)
To check active MySQL queries, open a new terminal session and log into MySQL using the command mysql -u root -p. Then, use the following command to inspect active queries:
**SHOW PROCESSLIST;**
This will help identify queries causing high resource usage, such as long-running or sleeping queries.
### **Step 7: Kill Problematic Queries** [#](/docs/monitor-system-processes-using-htop-command/)
If a query is causing high resource consumption, use the KILL command with the specific query ID:
KILL QUERY\_ID;
### **Step 8: Restart MySQL or Server** [#](/docs/monitor-system-processes-using-htop-command/)
If killing problematic queries does not resolve the issue, you may need to restart MySQL or the server. To restart MySQL from the command line, use the command
sudo systemctl restart mysql
Alternatively, you can restart MySQL or the server directly from the xCloud dashboard. Log in to the dashboard, click the three-dot menu, and select ‘Restart MySQL’ or ‘Restart Server’. After restarting, use htop again to check CPU and memory usage to ensure everything is back to normal.
## **Method 2: Monitoring Website Activity And System Resources Using htop** [#](/docs/monitor-system-processes-using-htop-command/)
In this method, you will explore how to monitor website activity and analyze system resources through the htop command. This comprehensive approach will guide you in identifying traffic patterns, managing server performance, and addressing issues related to plugins or themes that may affect your website’s operation.
### **Step 1: Use htop to Monitor Website Performance** [#](/docs/monitor-system-processes-using-htop-command/)
Open htop and monitor processes related to your website, such as apache2, nginx, or php-fpm. Log into xCloud and go to the specific site’s page. Locate the **‘Site User’** field in the site details bar. In htop, you can find the processes associated with your web server (for example, nginx, apache2, or php-fpm). If the processes are running under a specific site user, log into the xCloud dashboard and navigate to the website in question. Look for the ‘Site User’ in the site’s details.
### **Step 2: Check Site Traffic and System Resource Usage** [#](/docs/monitor-system-processes-using-htop-command/)
If CPU or RAM usage is high, check the website traffic to see if a sudden surge is causing the issue. To check the traffic, visit the logs in the xCloud dashboard. Navigate to the site and go to Monitoring and Logs. If your server is an NGINX server, choose the NGINX access logs, or if your server is an OLS server, select the OLS access logs. Review the traffic patterns. If you see legitimate high traffic, consider upgrading your hosting plan. If the traffic seems suspicious, it may indicate a potential bot attack that needs attention.
### **Step 3: Filter Bot Traffic** [#](/docs/monitor-system-processes-using-htop-command/)
If bot traffic is overwhelming your server, enable the [**7G Firewall**](/docs/use-xcloud-7g-firewall-on-nginx/) and [**8G Firewall**](/docs/enable-8g-firewall-in-xcloud/), a lightweight firewall that blocks bots and malicious traffic. You can also enable Cloudflare’s **‘Under Attack Mode’** in your Cloudflare settings to protect against DDoS attacks.
### **Step 4: Check Plugins, Themes, and MySQL Processes** [#](/docs/monitor-system-processes-using-htop-command/)
Sometimes, plugins or themes can cause excessive resource usage. To troubleshoot this, ensure everything is up-to-date by updating your plugins and themes. Additionally, consider disabling non-essential plugins, as reducing the number of active plugins may improve performance. You can also check MySQL queries by following the steps in Method 1 to identify any problematic queries.
### **Step 5: Restart the Server Using the xCloud Dashboard** [#](/docs/monitor-system-processes-using-htop-command/)
If traffic issues or plugin problems persist, you can reboot the server using the xCloud dashboard. Simply go to the xCloud dashboard, find your server, click the three-dot icon, and select Restart Server.
That’s it. By following this guide, you can efficiently monitor and troubleshoot system processes using htop. From MySQL queries to web traffic and plugin management, htop combined with xCloud dashboard functionalities provides a comprehensive toolkit for maintaining server performance. The inclusion of color-coded visual metrics in htop and easy keyboard navigation further enhances the user experience and simplifies the troubleshooting process.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Monitor Website Performance with Site Insights on xCloud - xCloud
> Website performance directly affects user satisfaction, retention and search rankings. Even small delays in page load time can lead to higher bounce rates,
Website performance directly affects user satisfaction, retention and search rankings. Even small delays in page load time can lead to higher bounce rates, lower conversions and weaker SEO visibility.
**Site Insights** on xCloud gives you **real-time data across three areas:** PHP activity, MySQL operations and traffic patterns so you can find and fix issues fast.
- **Traffic**: Displays overall traffic summary (requests, unique IPs/URLs, bot requests, bandwidth), along with IP Requests, Bot Traffic, URL Requests, Status Codes, and Bandwidth Usage per URL.
- **PHP**: Shows top requested pages, live PHP-FPM processes (PID, CPU %, Memory %, state, command) and slow pages with PHP-FPM slow log configuration and entries.
- **MySQL**: Provides a summary (connections, threads, uptime, QPS, buffer pool, slow and aborted queries), Active Connections, All Queries, Running Queries and Slow Query Log configuration and entries
Follow the steps below to access Site Insights from your xCloud dashboard and learn how to read the PHP, MySQL, and traffic reports to monitor, diagnose and improve your website’s performance:
## **Step 1: Access Site Insights** [#](/docs/monitor-website-performance-with-site-insights/)
Log in to your xCloud account. From the dashboard, go to ‘**Sites’** and select your site. Navigate to **Site Insights** in the sidebar menu, then click one of the three tabs: **PHP**, **MySQL** or **Traffic**. Use these tabs to view detailed performance data for your site.
## **Step 2: Check Traffic Insights** [#](/docs/monitor-website-performance-with-site-insights/)
Traffic Insights shows how visitors and bots interact with your site. It helps you distinguish normal traffic from suspicious patterns, understand demand, and control bandwidth usage.
Click the **‘Traffic’** option to access comprehensive insights into your site’s visitor patterns, bot activity, and resource consumption. This starts with an overall Summary dashboard, followed by dedicated tabs that break down data for precise analysis and optimization.
### **Summary** [#](/docs/monitor-website-performance-with-site-insights/)
Get an instant overview of site activity:
- **Total Requests:** Complete count of all incoming requests over the selected timeframe
- **Unique IPs:** Number of distinct IP addresses accessing your site, helping gauge real visitor reach
- **Unique URLs:** Count of individual pages or endpoints hit, revealing content popularity
- **Bot Requests:** Total automated traffic volume to separate human traffic from bots
- **Total Bandwidth:** Aggregate data transfer in MB/GB, important for cost and performance planning
Use this summary to quickly understand overall load, reach, and the balance between human and automated traffic.
### **IP Requests** [#](/docs/monitor-website-performance-with-site-insights/)
The IP Requests view shows the top IP addresses driving traffic to your site, along with their request counts.
Go to this tab to identify heavy users, frequent crawlers, or suspicious endpoints. It helps you whitelist trusted sources, block abusive IPs, and investigate potential DDoS or scraping activity.
### **Bot Traffic** [#](/docs/monitor-website-performance-with-site-insights/)
The Bot Traffic section identifies automated visitors in detail, **including:**
- **Bot Name:** Recognized crawler or bot identifier (for example Googlebot, Bingbot)
- **User Agent:** Full browser or agent string for verification
- **Request Count:** Hits per bot to monitor crawl frequency
Go to this tab to distinguish useful bots from noisy or unwanted crawlers, and to adjust your rules or robot configuration to reduce unnecessary load.
### **URL Requests** [#](/docs/monitor-website-performance-with-site-insights/)
The URL Requests section reveals your most-accessed endpoints, **showing:**
- **Top URL Requests:** Ranked list of pages or paths
- **Method:** HTTP method such as GET or POST
- **Request Count:** Total hits per URL
- **Status:** Response code (for example 200 OK, 500 Error, 401 Unauthorized)
Go to this tab to see which pages matter most, prioritize performance work on highly requested URLs, and quickly find endpoints that return frequent errors.
### **Status Codes** [#](/docs/monitor-website-performance-with-site-insights/)
The Status Codes view categorizes responses for health checks, **including:**
- **Status Code:** Specific code such as 200, 404, 503
- **Category:** Groups like 2xx Success, 4xx Client Error, 5xx Server Error
- **Request Count:** Occurrences per code
- **Percentage:** Proportion of total traffic for each status
Go to this tab to spot spikes in client or server errors and address issues before they significantly impact users.
### **Bandwidth** [#](/docs/monitor-website-performance-with-site-insights/)
The Bandwidth section tracks **data-heavy pages with metrics such as:**
- **URL:** Specific endpoint
- **Total Size:** Cumulative bytes transferred
- **Request Count:** Number of requests contributing to usage
- **Average Size:** Average response size per request
Go to this tab to find pages or assets that consume a lot of bandwidth, then optimize media, caching, or response sizes to reduce costs and improve performance.
## **Step 3: Check PHP Insights** [#](/docs/monitor-website-performance-with-site-insights/)
Click the **‘PHP ’ option** to access three essential insights into your site’s PHP performance: **‘Requested Pages’**, **‘Running Processes’**, and **‘Slow Pages’**. These provide granular data to diagnose issues, optimize resource usage and ensure smooth operation.
### **Summary** [#](/docs/monitor-website-performance-with-site-insights/)
This screenshot shows the **PHP Analytics → Summary** view inside the **Site Insights** section for a specific site in xCloud.
**Four main insights are shown for PHP Summary:**
**Total Page Visits:** Total number of page visits handled by PHP in the selected time range.
**Unique Pages:** Number of distinct pages requested.
**Running Processes:** Count of active PHP-FPM processes for this site.
**PHP Version:** The PHP version currently used by this site.
**Slow Pages:** Number of pages detected as slow (based on PHP-FPM slow log thresholds) in the selected period.
Overall, this view gives a quick, high-level summary of PHP activity for the site: traffic volume, how many pages are being hit, how many PHP-FPM processes are running, which PHP version is used, and whether any slow pages were detected in the chosen timeframe.
### **Requested Pages** [#](/docs/monitor-website-performance-with-site-insights/)
This view displays the **‘Top Requested Pages’** on your site along with unique page click counts. It helps you identify the most active pages, spot unusual traffic patterns (for example sudden spikes that might indicate abuse or viral content), and prioritize optimization for high-traffic areas.
### **Running Processes** [#](/docs/monitor-website-performance-with-site-insights/)
The ‘**Running Processes’** section shows live details for each PHP process, **including:**
- PID (Process ID)
- User
- CPU% (CPU usage percentage)
- Memory% (Memory usage percentage)
- Elapsed (Time elapsed since process start)
- State (Current process state)
- Command (The specific command or script running)
Go to this tab and detect resource-heavy processes, identify scripts consuming excessive CPU or memory, and stop inefficient processes when necessary.
### **Slow Pages** [#](/docs/monitor-website-performance-with-site-insights/)
**Slow Pages** section shows detailed PHP-FPM slow log information, **including:**
- **PHP-FPM Slow Log Configuration:** Settings like the slow log file and timeout thresholds
- **Slow Log Entries:** Logs of pages exceeding slow execution thresholds, with timestamps and execution times
Go to this tab to pinpoint specific pages or scripts that regularly exceed your slow thresholds so you can review code, queries or external calls causing delays.
## **Step 4: Check MySQL Insights** [#](/docs/monitor-website-performance-with-site-insights/)
Use MySQL Insights to see how your database handles live queries and connections. This is where you detect bottlenecks, slow queries, and configuration issues that can slow down your entire application stack.
Click the **‘MySQL’** option to view comprehensive database insights, starting with an overall Summary followed by detailed tabs for deeper analysis.
[MySQL Analytics.gif](https://drive.google.com/file/d/1uJm-mmfovgcahqA_m3suS_YMGM7MgwgF/view)
### **Summary** [#](/docs/monitor-website-performance-with-site-insights/)
The Summary provides key metrics at a glance:
- Active Connections
- Threads Running
- Uptime
- Queries per Second
- Buffer Pool Usage
- Slow Queries (Total)
- Aborted Connections
These metrics help you quickly assess database load, stability, and query behavior so you can decide whether you need to optimize queries, adjust configuration, or scale resources.
### **Active Connections** [#](/docs/monitor-website-performance-with-site-insights/)
The Active Connections tab lists **live connections with details:**
- ID
- User
- Host
- Database
- Command
- Time (s)
- State
Go to this tab to see who is connected, what they are doing, and how long queries have been running. It is especially useful for identifying long-running or stuck sessions that may need investigation.
### **All Queries** [#](/docs/monitor-website-performance-with-site-insights/)
The All Queries tab shows queries from the last 15 minutes up to 24 hours, including slow log status (on or off) and the threshold duration in seconds.
Use this view to review recent query activity over different time ranges, find patterns in heavy queries and correlate slowdowns with specific operations or time windows.
### **Running Queries** [#](/docs/monitor-website-performance-with-site-insights/)
The Running Queries tab displays queries that are currently executing for real-time monitoring.
Go to this tab to monitor live load, see which queries are currently consuming resources, and react quickly when response times start to increase.
### **Slow Query Log** [#](/docs/monitor-website-performance-with-site-insights/)
The Slow Query Log section offers configuration and log management options:
- Slow Query Log Configuration
- Enable or Disable Slow Query Log
- Long Query Time (Threshold for logging slow queries)
- Save & Restart MySQL
- Log Entries
Use this area to configure how slow queries are logged, set an appropriate threshold for your workload, and review logged entries to optimize problematic queries.
These sections help you monitor database health, identify bottlenecks and optimize queries effectively.
These detailed views empower you to detect anomalies, refine security and scale traffic handling with confidence.
That’s it. With Site Insights, you can monitor PHP, MySQL and traffic regularly to keep your site fast, stable, and efficient. Use these reports during performance reviews, after deployments, and whenever you notice slow responses or traffic spikes.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# My Account/Profile - xCloud
> My Account management in xCloud
In xCloud, once you sign up for your account you will get your own profile **‘My Account’** where you get to tailor your xCloud identity by setting your Name, Email, Contact Number, & Time Zone. Plus, you can set your own Avatar or Icon for your profile.
## **Access My Profile** [#](/docs/my-account/)
From your xCloud Dashboard, navigate to your team from the top right corner. By default, you will have a personal team with the name you signed up for. Click on it and navigate to **‘My Profile.’**
## **Set General Info In My Account** [#](/docs/my-account/)
In the **‘Profile’** section, you can set your name, contact number, and time zone. Your email ID will be automatically there. If you need to change your email address now, you can do that as well.
## **Set Avatar For Your Profile** [#](/docs/my-account/)
You can complete your xCloud identity by setting up an Avatar for your profile. To do so, simply click on **‘Upload Image’**, choose any image or icon as your preferred avatar, and click on **‘Save Changes.’**
---
# Configure NinjaFirewall on an OpenLiteSpeed Server - xCloud
> Learn how to configure NinjaFirewall settings on an OpenLiteSpeed Server easily with xCloud
[**NinjaFirewall**](https://wordpress.org/plugins/ninjafirewall/) is a powerful application firewall designed to enhance the security of WordPress websites, offering advanced protection against threats. By following this guide, you will learn how to enable and configure the necessary files, set up the required configurations, and ensure NinjaFirewall is properly integrated with your OLS server.
To configure NinjaFirewall on a server running OpenLiteSpeed server, follow the steps below:
## **Step 1: Access Your File Manager** [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
Log in to your xCloud account and navigate to your site’s dashboard. In the left-hand menu, go to **Access Data** → **File Manager**.
## **Step 2: Open Your File Manager** [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
Now, toggle on the **‘Enable File Manager’** button to access your file manager and click on the **‘Launch File Manager’** button to go to your file manager.
## Step 3: Show Hidden Files [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
In the File Manager, first go to your **Profile** → **Settings** and enable the option to **‘Show Hidden Files’** to view and edit configuration files like .htaccess or user.ini. After that click on the **‘Save’** button.
## **Step 4: Create the user.ini File** [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
Navigate to the root directory of your WordPress site (typically /var/www/). Check if a **‘.user.ini’** file already exists or not. If you do not find any user.ini file then, go to the **‘New Item’** from the menu and select the **‘File’** option. Then give the file name ‘user.ini’ and hit on the ‘Create New’ button.
## **Step 4: Add the Configuration Line** [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
Now click on the **‘.user.ini’** file and choose **‘Edit’** button. Then add the following line to the file and click on the ‘Save the changes’.
```
auto_prepend_file = "/var/www/[YOUR_DOMAIN]/wp-content/nfwlog/ninjafirewall.php"
```
Copy to Clipboard
_Note: Do not use the auto-prepend line suggested in the NinjaFirewall UI, as it might not work correctly on the OLS server. Use the line provided above instead using your domain._
## **Step 5: Restart the OLS Service** [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
Access the server where your site is hosted. Restart the ‘LiteSpeed service to apply the changes. Use the following command:
Or you can run this command using xCloud command runner.
**sudo systemctl restart lsws**
**Read this detailed documentation to learn how to run this command:**
👉 [How to Run Commands in Your Site And Server Easily with xCloud?](/docs/how-to-run-commands-in-your-site-and-server/)
## **Step 6: Verify the Configuration** [#](/docs/ninjafirewall-on-an-openlitespeed-server/)
Finally, visit the NinjaFirewall settings in your WordPress admin panel. Ensure that the firewall is active and functioning correctly.
And that’s it, this is how easily you can successfully configure NinjaFireWall on your OpenLiteSpeed server and actively protect your site.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# Optimal Backup Practices For xCloud Hosting Users - xCloud
> xCloud's optimal backup practices include full server, local, and remote backups. Ensure your website's safety and quick recovery from any issue.
Ensuring optimal backup practices for websites is crucial for restoring your website after disasters like server errors, software malfunctions, hardware failures, or hacker attacks. They serve as a safeguard, enabling you to reduce downtime and promptly restore your website.
[**xCloud Host**](/) always emphasizes on data security of its users and offers **optimal backup practices** for websites. Let us explore the different backup types, their individual purposes, and why taking a solid backup strategy is crucial.
## **Recommended Types Of Optimal Backup Practices For Websites** [#](/docs/optimal-backup-practices-xcloud/)
At xCloud, we suggest **three different types** of website backups to protect your data. With these applied, you can **ensure recovery** from even the most severe situations. Here are the types of website backup types:
- **Full server backups:** are complete backups of your entire server, created on a separate instance at your server provider’s location.
- **Remote site backups:** Take completely separate copies on a remote storage. (Any S3 storage Provider is supported).
- **Local site backups:** Taken directly on your server storage.
### **Full Server Backups** [#](/docs/optimal-backup-practices-xcloud/)
Full server backups are complete backups of your entire server, created on a separate instance at your server provider’s location.
xCloud offers an [**option to enable this**](/docs/configure-server-backup-management/) on the first screen while adding a new server on xCloud’s own provider or [**Vultr**](https://www.vultr.com/). On top of that, you can enable or disable this from the dashboard after setting up one.
These backups are your quickest solutions to restore your server if you experience any disaster. It is highly unlikely that anyone needs to use these backups for recovery. But, if you need to restore your website once in a while, it can be your go-to solution.
**Recommendation:**
• **Frequency:** We recommend scheduling **weekly full server backups**.
• **Retention:** Keep at least two recent backup versions to ensure recovery options over time. (This depends on your server provider).
Read more about Full Server Backup from here:
https://xcloud.host/docs/configure-server-backup-management/
### **Remote Site Backups** (**Off-Server)** [#](/docs/optimal-backup-practices-xcloud/)
Regular site backups on your server are great for everyday issues, but what if everything gets wiped out? Remote backups, stored with a different company far away, are your best bet for these big disasters.
Even if your server burns down, your websites can still be restored because the backups are safe somewhere else. It might take a little longer to get everything back up and running, but your business will not be ruined.
With [**xCloud**](/), you can take advantage of full-fledged remote backup options with any s3 provider and this is more secured.
**Recommendation:**
• **Frequency:** We strongly recommend **daily remote off-server backups** to ensure the most up-to-date recovery option in case of a catastrophic event.
• **Retention:** Maintain a minimum of seven daily backups to cover a full week.
Read more about Site Backup from here:
[https://xcloud.host/docs/site-backups-in-xcloud/](/docs/site-backups-in-xcloud/)
### **Local Site Backups** [#](/docs/optimal-backup-practices-xcloud/)
Having backups on your website’s server offers a quick solution if you need to **revert a site** to a previous state. These backups can be helpful if someone messes up the website and you need to go back to an older version. The backup files are stored in your VPS so you should always keep an eye on your server storage usage. For more safety, we recommend users to use Remote Backup always.
**Recommendation:**
• **Frequency:** Local backups can be performed **daily** to ensure you always have a recent version available.
• **Retention:** Consider keeping backups for the last 3-5 days, depending on your storage capacity.
**Note:** While local backups are convenient, we always recommend pairing them with remote backups for comprehensive protection.
Read more about Site Backup from here:
https://xcloud.host/docs/site-backups-in-xcloud/
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# An Overview of xCloud White-label Feature - xCloud
> The white-label feature in the roadmap for xCloud. Check out what you can expect from xCloud white-label feature.
The white-label feature will enable you to resell our hosting services. Since this feature is in our roadmap, let’s have a look at a plan for this feature below. We are expecting to ship this feature within Q4-2024.
## xCloud White-label Feature: An Overview [#](/docs/overview-xcloud-white-label-feature/)
xCloud is built for WordPress and this specific feature is for agency owners who **manage multiple servers for their customers**. With this feature, an agency will get a full white-label client portal to create hosting packages, set prices, and sell the packages to their customers. It’s like building your own hosting company.
In the background, the servers and sites will be powered by xCloud’s managed infrastructure.
This white-label hosting package will be powered by **[xCloud Managed Servers](/)** and you will get additional discounts (from the retail price) based on how many servers you are selling to your customers.
## How will the billing work? [#](/docs/overview-xcloud-white-label-feature/)
You can set your own price per hosting package for your white-label solution. xCloud will only charge the managed server’s price.
## Fully white-label solution [#](/docs/overview-xcloud-white-label-feature/)
You can set up the customer portal with your domain / sub-domain (cname), and your logo. There will not be any xCloud branding in the portal. You can also accept the payment to your Stripe account.
## Manage Customer Websites [#](/docs/overview-xcloud-white-label-feature/)
You will have access to the connected websites from your customer portal and manage them like you can manage your server/site in the xCloud panel.
---
# How To Perform A Full Server Migration With xCloud?(WordPress Sites) - xCloud
> We can easily perform a full server migration with xCloud by following some simple steps.
With [**xCloud**](/), you can easily arrange a full server migration without any complexity. With full server migration, you can migrate any number of WordPress sites in bulk under the same server. Also, this is a super-fast process and unlike any basic plugin migration, this process does not cause any harm to source servers or sites.
## **Prerequisite To Perform A Full Server Migration With xCloud:** [#](/docs/perform-a-full-server-migration-with-xcloud/)
1. Server Configuration: Ensure that your source server is running **Nginx** **& OLS** server.
2. Operating System: The source server should be running either **Ubuntu 20.04** or **Ubuntu 24.04** LTS x64.
3. Root Access: Obtain **root** access to the source server. This is essential for performing the Full Server Migration.
4. Disable 2FA if there are any.
5. Disable additional security like Site Grounds Security optimizer from your hosting end.
6. Uninstall Must use plugins of hosts.
7. Clear Cache and disable cache plugins like Object Cache PRO
8. Disable Wordfence or any other security plugins.
9. You can migrate an existing server in xCloud. You need to install a fresh server from xCloud in order to perform the Full Server Migration feature.
**_NOTE: Your destination server must be provisioned in xCloud_**.
_**New update: migration from Runcloud OLS server is now also supported**_.
Let’s follow a step-by-step process on how to achieve it successfully.
## **Step 1: Add Necessary Information For Full Server Migration** [#](/docs/perform-a-full-server-migration-with-xcloud/)
To configure the connection, begin by entering the IP address of the source server, the Port number is “22” and the SSH username is usually “root”. You may visit your cloud provider to find the exact details. Then, if SSH authentication necessitates a password, choose the “**Password**” option and provide the required password. This will establish the connection with your source server.
But if your server relies on public key authentication, you will need to add the xCloud’s **provided public key** by accessing your server via root user using the terminal. This process ensures that only authorized individuals with the corresponding private key can gain access to the server and this is more secured than the Password approach.
Therefore, to add the public key to your source server you need to follow these steps:
- Copy the public key from xCloud’s FSM dashboard.
- Access your source server as a root user via SSH.
- Paste the public key.
After adding the Public key in your source server switch back to xCloud and click next.
## **Step 2: Select The WordPress Site/Sites You Want To Migrate** [#](/docs/perform-a-full-server-migration-with-xcloud/)
After you have connected your public key, you will get access to your sites for migration. Select which server to migrate, click ‘**Next**’, and push your site to the live site.
## **Step 3: Go Live Or Create Demo Site** [#](/docs/perform-a-full-server-migration-with-xcloud/)
In this step, you can either choose a Demo site or you can opt for going live. Simply, toggle on your favorable option.
_Note: Please make sure to check out the storage of your destination server. We recommend keeping your destination server with at least **1 GB** free always._
Now your full server migration will start shortly.
Our development team will help you to perform full server migration from any server if you have root access to it. Please contact our **[support team](/support/)** for any assistance.
---
# PHP Versions Compatibility in xCloud - xCloud
> Learn about PHP Versions Compatibility in xCloud. Understand which PHP versions work with different stacks and Ubuntu server versions.
With **xCloud**, you can select from various PHP versions depending on your server setup. This gives you the flexibility to support both older applications and newer PHP websites.
Check out the table below to learn PHP versions compatibility based on the server stack, operating system version, and whether they are supported on xCloud or not.
## **Supported PHP Versions on Ubuntu Servers** [#](/docs/php-versions-compatibility-in-xcloud/)
**Server Stack**
**OS Version**
**Supported PHP Versions**
**Current Status**
**NGINX**
Ubuntu 24.04 LTS
PHP 8.1, 8.2, 8.4, 8.5
Yes
Ubuntu 22.04.5 LTS
PHP 5.6 to 8.5
Yes
Ubuntu 20.04 LTS
PHP 7.4
⚠️ Deprecated
**OpenLiteSpeed (OLS)**
Ubuntu 24.04 LTS
PHP 8.1, 8.2, 8.3, 8.4
Yes
Ubuntu 22.04.5 LTS
PHP 7.4 to 8.2
Yes
Ubuntu 20.04 LTS
PHP 7.4
⚠️ Deprecated
**ARM (OLS only)**
Ubuntu 24.04 LTS
PHP 8.3
Yes
### **📌Notes** [#](/docs/php-versions-compatibility-in-xcloud/)
- **Ubuntu 20.04 is deprecated** in xCloud. You can no longer create new servers or sites using it directly.
- If you still need **PHP 7.4** or **Ubuntu 20.04**, we recommend that you migrate to the latest Ubuntu version.
- You can connect **fresh Ubuntu 24.04 LTS x64 servers** from any provider to xCloud.
- These new servers support both **NGINX** and **OpenLiteSpeed (OLS)** stacks.
If you need help choosing the right stack or PHP version, reach out to our support team. We are ready to assist you at any time.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# Do You Provide Root Access To My Servers? - xCloud
> Interested to know if xCloud provide root access to the site servers? Check out the doc to learn more.
xCloud does not provide root access on its servers directly. Instead, you can create sudo users and run commands as the root user.
Sudo users have access to the system, enabling them to view and modify all sites on a server. However, it is crucial to set file permissions manually for effective control. For more information, you can check our detailed documentation on understanding [**Sudo Users and Site Users**](/docs/usudo-users-and-site-users-in-xcloud/) in xCloud.
---
# Keep Your Server up to Date with Automated Security Updates - xCloud
> Learn how to keep your server secure with xCloud’s automated security updates effortlessly manage software updates.
xCloud handles all essentials of your server maintenance tasks, including automated **[security updates](/docs/server-and-website-security-with-xcloud/)**. This covers both security-related updates and general package updates that improve performance or provide other benefits. You do not need to take any actions to maintain the default stack or operating system (OS) of your server. As long as your server remains operational, xCloud ensures that the server stack continues to function optimally.
Many of the packages that come pre-installed with the OS are not necessary for your server’s performance or security. These can be safely ignored unless explicitly required. When we are talking about the software updates of a server meaning the entire range of software that runs on your server which includes everything from the operating system kernel to application packages such as Nginx and PHP.
## **Security Updates** [#](/docs/reboot-server-with-automated-security-updates/)
Security is our top priority at xCloud. All servers deployed through xCloud are automatically configured to install security updates as soon as they become available, significantly reducing the risk of vulnerabilities. These automated security updates are managed by the unattended-upgrades package, which xCloud installs and configures on every server.
## **Required Reboot of the Server** [#](/docs/reboot-server-with-automated-security-updates/)
Certain updates, especially kernel updates, may require a reboot for changes to take effect. When this is necessary, you will be notified through the xCloud dashboard. Rebooting can be initiated with just a few clicks. While reboots generally take a few seconds, any downtime can impact visitors. To minimize disruption, we recommend rebooting during off-peak hours. If a reboot is required, xCloud will notify you through:
- **Email Notification:** You will receive an email informing you that a reboot is necessary.
- **Dashboard Notification:** A notice will appear in the xCloud dashboard, allowing you to reboot the server easily.
## **How to Schedule Automated Reboot for Security Updates in xCloud?** [#](/docs/reboot-server-with-automated-security-updates/)
When there is a security update comes in your server, xCloud will notify you to reboot the server and you can reboot the server anytime instantly or set a time to take a security update automatically at your preferred time. Follow these simple steps to set up and manage server software updates in xCloud. Let us walk you through the process.
### **Step 1: Go to xCloud Dashboard** [#](/docs/reboot-server-with-automated-security-updates/)
To set up server software updates in xCloud, start by logging into your account and navigating to the xCloud dashboard. Here, you can check if your server requires a reboot. If a reboot is necessary, you will see a notification bar indicating which server needs to be updated.
### **Step 2: Update the Server** [#](/docs/reboot-server-with-automated-security-updates/)
You can Update the server from the xCloud dashboard with just a click easily. Just click on the **‘Reboot Now’** button to update the server.
Or click on the **Server Name** in the notification bar, which will take you to the **‘Server Update’** section under the Security settings. From there, you can also click **‘Reboot Now’** to update the server immediately.
### **Step 3: Set a Specific Time to Update the Server Automatically** [#](/docs/reboot-server-with-automated-security-updates/)
If you prefer to automate this process, you can enable automatic updates by toggling on the **‘Automatic Update’** option. Set a specific time for the server to perform the update, and once you have chosen the time, click the **‘Save Settings’** button to confirm. This way, your server will update automatically at the scheduled time.
**_Note:_** _To set up automatic security updates of the server it is recommended to set a time in off-peak hours or during low-traffic periods._
### **Final Outcome** [#](/docs/reboot-server-with-automated-security-updates/)
After rebooting the server, if you go back to the dashboard, you will see there is not any notification showing in the dashboard meaning the server is updated and the issues are fixed.
This is how easily you can reboot the server and take automated security updates with xCloud in a hassle-free way so that you can keep the server updated and free from any threat.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Recreate a Missing wp-config.php File in WordPress - xCloud
> Learn how to recreate a missing wp-config.php file in WordPress. Follow simple steps to restore your site’s database connection and settings safely.
If your WordPress site is showing errors or refusing to load, a missing wp-config.php file might be the reason. This file is essential because it connects your WordPress site to its database and defines important settings. Without it, your site simply cannot function. You can recreate this file quickly and safely.
Follow the steps below to learn how to access your file manager, recreate a missing wp-config.php file easily.
## **Step 1: Access Your File Manager** [#](/docs/recreate-a-missing-wp-config-php-file/)
To resolve this issue, first go to your site and head over to the **‘Access Data’** option from the sidebar menu. Then choose the **‘File Manager’** option from the menu.
Next, toggle to enable the **‘File Manager’** and click on the **‘Launch File Manager’** to access the file manager.
## **Step 2: Create a New wp-config File** [#](/docs/recreate-a-missing-wp-config-php-file/)
In your WordPress root directory, search for the wp-config.php file.If the file does not exist, go to the wp-config.sample file and copy the code.
Click on the **‘New Item’** from the file manager dashboard. Then choose **‘file’** and give the file name as **“wp-config.php”** and click on the **‘Create Now’** button. Then go to the file, click on the **‘Edit’,** and paste the copied code from the ‘**wp-config-sample.php’** file and hit on the save button.
_Note:_ Ensure you save it in the root directory, alongside folders like wp-content and wp-admin.
## **Step 3: Add Database Credentials** [#](/docs/recreate-a-missing-wp-config-php-file/)
Now go back to your xCloud dashboard and click on the **‘Database’** option. From here, toggle on to access the database. Then collect the **‘Database Name’**, **‘Database User’**, and **‘Databse Password’.**
Next go back to the wp-config.php file and click on the **‘Edit’,** find the following lines:
```
define('DB_NAME', 'database_name_here');
define('DB_USER', 'username_here');
define('DB_PASSWORD', 'password_here');
define('DB_HOST', 'localhost');
```
Copy to Clipboard
Replace the placeholder values with your actual database credentials. For example:
```
define('DB_NAME', 'wp_mysite');
define('DB_USER', 'admin_user');
define('DB_PASSWORD', 'secure_password123');
define('DB_HOST', 'localhost');
```
Copy to Clipboard
After inserting the values, click on the ‘**Save’** button.
## **Step 5: Regenerate Security Keys** [#](/docs/recreate-a-missing-wp-config-php-file/)
WordPress uses security keys to encrypt user data. You need to generate new keys. Visit [this](https://api.wordpress.org/secret-key/1.1/salt/) in your browser. This URL provides a set of random security keys.
Alternatively, if you have terminal access to your server, you can use a command-line tool like wp-cli to generate keys:
```
wp config shuffle-salts
```
Copy to Clipboard
Copy the generated keys from the URL or terminal. In wp-config.php, find the section with lines like:
```
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');
```
Copy to Clipboard
Replace the credentials with the new keys and save the file.
## **Alternative Method: Restore from Backup** [#](/docs/recreate-a-missing-wp-config-php-file/)
If you have a backup of your website, you can restore the wp-config.php file directly from it. First, download your backup from wherever it is stored. Then extract the backup files on your local device. Look inside for the original wp-config.php file.
Once you have the file, go to your file manager. Use the upload option to upload the wp-config.php file to the root directory of your WordPress installation. Make sure it is placed alongside the wp-content and wp-admin folders.
After the upload is complete, your site should be able to run as before, using the restored configuration file.
And that’s it this is how easily you can recreate a missing wp-config.php file for your WordPress site.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Recreate WordPress Website from Backups in xCloud? - xCloud
> Learn how to recreate WordPress website from backups in xCloud. Easily restore sites, minimize downtime, and prevent data loss following this guide.
Disasters can strike unexpectedly, and you might be able to restore your WordPress website, including all the data and files. Whether due to hardware failures, cyberattacks, or accidental deletions, the ability to recover quickly is essential to minimizing downtime and preventing data loss.
**[xCloud](/)** allows you to restore your site from your backups. Whether from **local or remote backups**, you can directly restore and recreate **[WordPress](https://wordpress.org)** website from backups in xCloud easily.
## **How to Recreate WordPress Website from Backups in your xCloud Account?** [#](/docs/recreate-wordpress-website-from-backups/)
Follow the steps below to recreate the WordPress website from backups with xCloud, whether it is an incremental or full backup.
### **Step 1: Initiate New Site Creation** [#](/docs/recreate-wordpress-website-from-backups/)
After logging in to your xCloud dashboard, to create a new site, click on the ‘**\+ New Site**’ button, then choose a server from the dropdown and click the ‘**Next**’ button. Here select ‘**Recreate Site From Backup**’ to migrate your targeted site from existing backup to a new website.
### **Step 2: Select Migration Destination & Domain** [#](/docs/recreate-wordpress-website-from-backups/)
After choosing a server as Destination, click on ‘**Next**’ Button, You can either choose to migrate to a new domain or a demo site from where you can migrate later. And hit the ‘**Next**’ button.
### **Step 3: Available Backup Sources in xCloud** [#](/docs/recreate-wordpress-website-from-backups/)
Here, you will get two options for restoring your site from backup: ‘Existing Site/Server Import’ and ‘Import From Bucket’. Choose the **‘Existing Site/Server Import’** option, if you have an existing site in xCloud that you want to migrate and create as a new site. Or you can choose the **‘Import From Backup’** option, if you want to restore your site from your storage bucket.
### **Step 4: Choose Your Preferred Backup Source & Files** [#](/docs/recreate-wordpress-website-from-backups/)
You can restore the full server or any specific website. Just go to the ‘Existing Site/Server Import’, then select a Server, Site, and backup type and click on the ‘Next’ button. Here, choose a backup file to restore and hit the ‘**Next**’ button.
If you choose the ‘**Import From Bucket**‘ option, you can restore from your backup that you have taken in your storage bucket. Now, Select a **‘Bucket’**, add the domain from which you are migrating and click on the ‘**Next**’ button. Select the file you want to restore.
### **Step 4: Configure Settings & Start Migrating** [#](/docs/recreate-wordpress-website-from-backups/)
After choosing the necessary files to restore your site, the settings tab will come to make sure you select the necessary versions and settings according to your need and click on the **‘Next’** button. And in the next, review your preferred settings and hit the ‘**Start**’ button.
After restoring and completing your site, you will see a message showing that it has been successfully migrated. This is how easily you can recreate a WordPress website from backups in xCloud.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/?_gl=1%2A1och7at%2A_ga%2AMTk3NjQ1MDU2NS4xNzMxMjI5MTI5%2A_ga_GS7G4T8PYV%2AMTczNjA3MTMxNC40MS4xLjE3MzYwNzEzMjQuMC4wLjA.) for any of your queries.
---
# xCloud Refund Policy - xCloud
> Learn about xCloud refund policy for self-managed hosting, managed servers, and addons. Includes pay-as-you-go billing details, backup refund rules, and how to request a refund.
# xCloud Refund Policy [#](/docs/refund-policy/)
Depending on how the service is used, refund eligibility may vary. In this doc, you can learn the refund policy across xCloud, including which services are eligible, how refunds are calculated, and what conditions apply.
## Refund Eligibility at a Glance [#](/docs/refund-policy/)
Service
Refund Type
Window
xCloud Managed, Provider, and OpenClaw Servers
Pro-rated
Anytime before the end of the paid billing term
Self-Managed Hosting (BYOS)
Full refund
Within 14 days of purchase
Reseller / White Label
Full refund
Within 14 days of purchase
Addons
❌ No rxefunds
—
## How to Request a Refund [#](/docs/refund-policy/)
1. **Cancel first** — Remove your server or cancel your subscription before submitting a request.
2. **Open a support ticket** — Log in with your account and submit a ticket here. Select the relevant service when creating the [**support ticket**](https://app.xcloud.host/support).
✅ Approved refunds are processed within 5–10 business days and returned to your original payment method. It also depends on your banking working days. All refund amounts are calculated in USD. In accordance with our policy, our team will review your case and respond promptly. Please check below to know more about eligible refund cases.
## xCloud Managed, Provider, and Agentic Stack Servers Refund Policy [#](/docs/refund-policy/)
If you delete an xCloud Managed Server, xCloud Provider Server, or Agentic stack (OpenClaw, Paperclip, Hermes) Server before the end of its paid billing term, you may be eligible for a pro-rated refund based on your actual usage.
This means you only pay for the time your server was active. For yearly or multi-month OpenClaw plans, the refund is calculated from the actual amount paid for that billing term, including any checkout discount.
**Important notes:**
- A minimum charge of one full day applies if the server was used for less than 24 hours.
- Stripe processing fees (up to 10%) may be deducted from the refundable amount.
- Refunds are calculated as: **Total paid − usage charge − processing fee = refund amount**
**Example (monthly plan):** You purchase a $100/month plan and delete it after 15 days. You’ll be charged for 15 days of usage plus the Stripe fee. The remaining balance is refunded.
### Full Server Backup for xCloud Managed & Provider Servers [#](/docs/refund-policy/)
The same pro-rated rules apply to server backups. You pay only for the backup time used, and the unused portion is refunded after the Stripe fee is deducted.
### OpenClaw Server Yearly & Multi-Month Billing [#](/docs/refund-policy/)
OpenClaw servers may be available with monthly, yearly, or multi-month billing terms. If you cancel or delete an OpenClaw server before the end of its paid billing term, you may be eligible for a pro-rated refund for the unused portion of the term.
This means you only pay for the time the OpenClaw server was active.
**Important notes:**
- Refunds are calculated based on the actual amount paid at checkout, including any first-purchase or term discount.
- A minimum charge of one full day applies if the server was used for less than 24 hours.
- Stripe processing fees, up to 10%, may be deducted from the refundable amount.
- Refunds are calculated as:
> **Total paid − used service charge − processing fee = refund amount**
- If server backup or other eligible server-level services were included, those services are also calculated on a pro-rated basis where applicable.
- Addons that are marked as non-refundable remain non-refundable once activated.
**Example (yearly plan):** If you purchase a yearly OpenClaw server plan and delete the server after using part of the billing term, xCloud calculates the used portion first. The unused portion is then refunded after deducting the applicable Stripe processing fee.
For example, if you paid $144 for a yearly OpenClaw server and used 3 months, the used service charge would be $36. The remaining $108 would be eligible for refund, minus the applicable Stripe processing fee.
## Self-Managed Hosting / BYOS Refund Policy [#](/docs/refund-policy/)
You’re entitled to a full refund within 14 days of purchase — no questions asked.
**Important notes:**
- Refund requests are only eligible within the first 14 days of purchase and only for new servers.
- Requests after 14 days are not eligible.
- Recurring charges and cancellations after 14 days are not eligible for refunds.
- Deleting your server automatically cancels the related subscription. Cancelled subscriptions will not be charged in the next billing cycle.
## Reseller Panel / White Label Refund Policy [#](/docs/refund-policy/)
A 14-day refund policy applies, covering subscription fees.
For full pricing and refund details specific to the Reseller Panel, check below: **Full Details on [xCloud Reseller Panel Refund Policy](/docs/how-billing-works-in-xcloud-white-label-program/)**
## Addons [#](/docs/refund-policy/)
Refunds are not available for any addon once the subscription is activated. This includes:
- Mailbox
- Mail Delivery
- Site Security PRO
All addon purchases are final and non-refundable. Please review your selection, pricing, and billing details carefully before subscribing.
## Late Payments & Account Suspension [#](/docs/refund-policy/)
- Accounts are billed on the 1st of each month for all recurring payments.
- Overdue payments may result in your account being paused until the balance is cleared.
- Clients are requested to keep funds in accounts before the month ends.
- If you need more time to complete the payment, please [**contact our support team**](https://app.xcloud.host/support/) within the last week of the previous month. We will do our best to assist you and avoid any service interruption.
If you have any questions about the refund policy, please contact our [**support team**](https://app.xcloud.host/support/) or email us at **support@xcloud.host**.
---
# How to Remove a Payment Method by Canceling Your Account With xCloud
> Learn how to remove a payment method from xCloud when account cancellation is required, including what to back up, how to cancel active services, and what to send Support.
If you want to **remove a payment method** from xCloud, you must first cancel active xCloud services and request account cancellation or account deletion. This protects your account from accidental unpaid renewals while servers, subscriptions, add-ons, or billing records are still active.
Follow this guide to understand what to check before cancellation, how to stop active billing, and what information to send to xCloud Support so your account and saved payment method can be reviewed for removal.
## Before you start [#](/docs/remove-payment-method-xcloud/)
Removing a saved card or payment method is different from canceling one server subscription. If you only want to stop billing for one server, follow [How to Cancel xCloud Subscription](/docs/how-to-cancel-xcloud-subscription/). If you want your full account and data removed, review [How to Delete Your Account and Data With xCloud](/docs/how-to-delete-your-account-and-data-with-xcloud/).
Use this guide when your goal is to remove billing access from the account and you no longer want to keep the xCloud account active.
## Why account cancellation is required to remove a payment method [#](/docs/remove-payment-method-xcloud/)
xCloud may need to keep a valid payment method while your account has active paid services, server subscriptions, add-ons, pending invoices, or billing records connected to renewals. Because of that, payment method removal is handled together with account cancellation or deletion.
This helps prevent a situation where a server or add-on remains active but the account has no valid payment method for renewal. Before requesting removal, make sure you no longer need the active services connected to that billing profile.
## Prerequisites [#](/docs/remove-payment-method-xcloud/)
- Access to the xCloud account owner or billing email address.
- A current backup of any site, database, or server data you want to keep.
- Downloaded invoices or receipts you may need for accounting.
- Access to your external cloud provider account if you use self-managed servers.
- Confirmation that you are ready to cancel the xCloud account, not only one server.
## Step-by-step [#](/docs/remove-payment-method-xcloud/)
### 1\. Download backups and billing records [#](/docs/remove-payment-method-xcloud/)
Download any files you need before cancellation. This can include website backups, database backups, server credentials, invoices, receipts, and records for your team.
After account deletion or service removal is completed, xCloud may not be able to recover deleted site or server data.
### 2\. Cancel active xCloud services [#](/docs/remove-payment-method-xcloud/)
Cancel active subscriptions by removing the services connected to them. For server subscriptions, delete the server you no longer need. If you have multiple servers, deleting one server only cancels billing for that specific server.
Review any add-ons, managed services, mailboxes, backups, or other paid services connected to your account. If you are not sure which services are still billable, contact xCloud Support before requesting payment method removal.
### 3\. Check external provider resources [#](/docs/remove-payment-method-xcloud/)
If you connected a self-managed server or brought your own provider account, also check the provider dashboard. External providers may continue billing for servers, volumes, snapshots, backups, reserved IPs, firewalls, or other resources even after you remove the server from xCloud.
xCloud can help with xCloud-side cancellation guidance, but your external provider controls its own billing and resource deletion.
### 4\. Request account cancellation and payment method removal [#](/docs/remove-payment-method-xcloud/)
After active services are removed, contact [xCloud Support](https://support.xcloud.host/) and ask for account cancellation with payment method removal review.
Include the following information:
- Your xCloud account email address.
- Confirmation that you want to cancel the account.
- Confirmation that you have downloaded the backups, invoices, and data you need.
- Confirmation that active xCloud servers and services have been deleted or should be reviewed.
- Any invoice ID, bill ID, or subscription reference if your request is related to a specific charge.
Do not send your full card number, CVC, or card password. If Support needs to identify a payment method, the last four digits of the card are usually enough.
### 5\. Wait for support confirmation [#](/docs/remove-payment-method-xcloud/)
xCloud Support will review the account, active services, billing status, and payment method removal request. If there are open invoices, active subscriptions, or remaining services, Support may ask you to resolve those before the payment method can be removed.
### 6\. Keep the final confirmation [#](/docs/remove-payment-method-xcloud/)
After the request is completed, keep the support confirmation for your records. If you later see a charge, reply in the same support thread with the invoice ID or charge date so the team can review it faster.
## Billing and refund notes [#](/docs/remove-payment-method-xcloud/)
Removing a payment method does not automatically create a refund. Refund eligibility depends on the service type, billing period, usage, and xCloud refund policy. Review the official [xCloud Refund Policy](https://xcloud.host/refund-policy/) before submitting a refund-related cancellation request.
If you use an external cloud provider, provider-side charges are separate from xCloud billing. You must cancel or delete provider-side resources from the provider dashboard to stop provider billing.
## What xCloud Support can check [#](/docs/remove-payment-method-xcloud/)
- Whether active xCloud services remain on the account.
- Whether server-related subscriptions were canceled after server deletion.
- Whether a payment method removal request can be reviewed after account cancellation.
- Which invoice or bill item is connected to a specific xCloud charge.
- Whether a refund request should be reviewed under the xCloud refund policy.
## What xCloud Support cannot control [#](/docs/remove-payment-method-xcloud/)
- Charges created directly by an external cloud provider.
- Provider-side resources that still exist outside xCloud.
- Bank processing times after a refund is approved.
- Recovery of data that was permanently deleted before a backup was downloaded.
## FAQ [#](/docs/remove-payment-method-xcloud/)
### Can I remove my card without canceling my account? [#](/docs/remove-payment-method-xcloud/)
If your account has active paid services, payment method removal requires account cancellation or deletion review. This prevents active services from remaining on an account with no valid payment method.
### Does deleting one server remove my payment method? [#](/docs/remove-payment-method-xcloud/)
No. Deleting one server cancels billing related to that server only. It does not remove the saved payment method from the full account if other services or the account remain active.
### Will payment method removal cancel my provider bill? [#](/docs/remove-payment-method-xcloud/)
No. If you use a separate cloud provider account, you must cancel or delete resources directly from that provider account.
### What should I send to Support? [#](/docs/remove-payment-method-xcloud/)
Send your account email, cancellation confirmation, data-backup confirmation, and any relevant invoice ID or bill ID. Do not send full card details.
---
# How to Request For Site Migration Support From xCloud - xCloud
> Learn how to request site migration support from xCloud. Complete the prerequisites, submit a support ticket with your site URL and WordPress admin credentials, and let the xCloud team handle the rest.
This guide provides a step-by-step walkthrough on how to request site migration support from the xCloud team. Follow the prerequisites carefully and then submit a support ticket with the required information to ensure a smooth migration process.
## **Prerequisites To Perform A Full Server Migration With xCloud** [#](/docs/request-for-site-migration-support-from-xcloud/)
Before requesting a Full Server Migration with xCloud, ensure the following conditions are met on your source server:
**#**
**Requirement**
**Details**
1
**Server Configuration**
Ensure that your source server is running Nginx or OpenLiteSpeed (OLS) server.
2
**Operating System**
The source server should be running either Ubuntu 20.04 or Ubuntu 24.04 LTS x64.
3
**Root Access**
Obtain root access to the source server. This is essential for performing the Full Server Migration.
4
**Disable 2FA**
Disable Two-Factor Authentication (2FA) if enabled on your hosting account or WordPress admin.
5
**Disable Host Security**
Disable additional security measures such as SiteGround Security Optimizer or similar tools from your hosting end.
6
**Uninstall Host Plugins**
Uninstall any must-use plugins provided by your hosting provider.
7
**Clear & Disable Cache**
Clear all caches and disable cache plugins such as Object Cache Pro or similar caching solutions.
8
**Disable Security Plugins**
Disable Wordfence or any other security plugins installed on your WordPress site.
9
**Fresh xCloud Server**
Install a fresh server from xCloud in order to use the Full Server Migration feature.
⚠️ **Important Note:** You can migrate an existing server to xCloud. However, you must install a fresh server from xCloud first in order to use the Full Server Migration feature. Make sure all prerequisites above are completed before proceeding.
## **Steps to Request Migration Support** [#](/docs/request-for-site-migration-support-from-xcloud/)
Once all prerequisites are fulfilled, follow these steps to request site migration support from the xCloud team:
### **Step 1: Create a Support Ticket** [#](/docs/request-for-site-migration-support-from-xcloud/)
Navigate to the xCloud support portal and create a new support ticket. Select **Site Migration** as the ticket category. In your ticket, clearly mention that you need site migration support and that all prerequisites have been completed.
**Tip:** Provide as much detail as possible in your initial ticket to avoid unnecessary back-and-forth communication.
### **Step 2: Provide Your Site Link** [#](/docs/request-for-site-migration-support-from-xcloud/)
Include the full URL of the website you want to migrate in the support ticket. For example: _https://www.yourwebsite.com_
If you have multiple sites to migrate, list each site URL separately.
### **Step 3: Share WordPress Admin Credentials** [#](/docs/request-for-site-migration-support-from-xcloud/)
Provide the WordPress admin login credentials for your site in the support ticket. The xCloud support team will need these to access your site during the migration process. Include the following:
- **WordPress Admin URL:** e.g., https://www.yourwebsite.com/wp-admin
- **Admin Username:** Your WordPress admin username
- **Admin Password:** Your WordPress admin password
🔒 **Security Recommendation:** It is recommended to change your WordPress admin password after the migration is complete for security purposes.
### **Step 4: xCloud Team Handles the Migration** [#](/docs/request-for-site-migration-support-from-xcloud/)
Once the xCloud support team receives your ticket with the site link and WordPress admin credentials, they will begin the migration process. The team will migrate your site to the fresh xCloud server you have set up. You will be notified via the support ticket once the migration is complete.
## **Quick Checklist** [#](/docs/request-for-site-migration-support-from-xcloud/)
Use this checklist to make sure everything is ready before submitting your migration request:
- Source server running Nginx or OLS
- Ubuntu 20.04 or 24.04 LTS x64 on source server
- Root access obtained for source server
- Two-Factor Authentication (2FA) disabled
- Host security plugins (e.g., SiteGround Security Optimizer) disabled
- Must-use hosting plugins uninstalled
- Cache cleared and cache plugins (e.g., Object Cache Pro) disabled
- Security plugins (e.g., Wordfence) disabled
- Fresh xCloud server installed
- Support ticket created with site URL and WP admin credentials
_Need help? Contact xCloud Support._ _This document is provided by xCloud for customer reference._
---
# How to Resell Hosting with Self Managed Server Provider - xCloud
> Learn how resell hosting with self managed server provider with fully white label, branding, built in client and billing management.
xCloud **[Reseller Hosting Program](/reseller-hosting/)** allows you to integrate your own server providers so you can manage and sell products using your preferred hosting infrastructure. Whether you work with Hetzner, Vultr, DigitalOcean, or Linode (Akamai), the process is simple and efficient.
Follow the documentation to resell hosting with [**self managed server**](/self-managed-hosting/) with easy steps.
## **Integrate Self Managed Server Provider with the Reseller Program** [#](/docs/resell-hosting-with-self-managed-server-provider/)
Easily connect your preferred server provider (Hetzner, Vultr, DigitalOcean, or Linode) to xCloud through the reseller dashboard. Authorize, verify, and manage multiple servers directly from a single dashboard.
### **Step 1: Access the Reseller Dashboard** [#](/docs/resell-hosting-with-self-managed-server-provider/)
To begin, log in to your reseller dashboard. From the left-hand menu, navigate to **‘Settings’** → **‘Self Managed Server Provider’** Integration. Once you are on the integration page, click on the **‘Add New Provider’** button to start adding your server provider.
### **Step 2: Choose and Authorize a Server Provider** [#](/docs/resell-hosting-with-self-managed-server-provider/)
After clicking the button, a pop-up window will appear. In this window, you will be able to select a server provider from the available options, which include **‘Hetzner’**, **‘Vultr’**, **‘DigitalOcean’**, and **‘Linode (Akamai)**. Once you have chosen your preferred provider, click on the **‘Authorize / Verify’** button to proceed.
If you need help with the setup process for integrating your Self Manged Server, you can follow the documentation below for setup set your own server provider with the Reseller Hosting program easily. –
👉 [DigitalOcean](/docs/how-to-setup-your-server-with-digital-ocean/),
👉 [Vultr](/docs/how-to-get-free-hosting-with-vultr/),
👉 [Hetzner,](/docs/set-up-hetzner-server-in-xcloud/) or
👉 [Linode (Akamai)](/docs/integrate-and-setup-linode-server-with-xcloud/).
Once the setup is completed, your selected server will be connected to xCloud and added to your dashboard. The dashboard will then display important details such as the **‘Server Name**, **‘Provider’**, and **‘Server Count’**. From the ‘**Actions’** menu, you can click on the **‘Edit**’ icon to update the server credentials whenever necessary or **‘Delete’** the server by clicking the Delete icon.
_Note: It is also possible to integrate multiple servers from the same provider, which gives you flexibility when managing your hosting resources._
## **Create a Product with xCloud Reseller Hosting Program** [#](/docs/resell-hosting-with-self-managed-server-provider/)
Once your server is integrated, create and customize hosting products with your own pricing, descriptions, and packages. Publish them under your white-label brand and start reselling instantly.
### **Step 3: Create a Product with the Provider** [#](/docs/resell-hosting-with-self-managed-server-provider/)
When your server integration is complete, you can move on to creating products. Go to the **‘Products’** tab in your dashboard and click on the **‘Add Product’** button.
### **Step 4: Choose the Integrated Server Provider** [#](/docs/resell-hosting-with-self-managed-server-provider/)
A pop-up will appear, where you should select the **‘Own Provider’** option to access the self-managed servers you have already connected. From there, choose one of the integrated server providers, such as **‘Vultr’**, to continue.
### **Step 5: Choose Server Provider and Size** [#](/docs/resell-hosting-with-self-managed-server-provider/)
Next, select a **‘Server Provider’** from the dropdown menu under **‘Select Provider’**. You will also need to choose the **‘Server Size’** according to your preferences.
### **Step 6: Add your Product Description** [#](/docs/resell-hosting-with-self-managed-server-provider/)
You will now see an overview of the plan details. Next, you will receive an auto-generated **‘Product Description’** that cannot be edited. After that, you will have access to **‘Additional Custom Fields,’** where you can add your preferred details. Once finished, click the **‘Next’** button.
### **Step 7: Customize Package** [#](/docs/resell-hosting-with-self-managed-server-provider/)
Provide the following details for your product:
- **‘Plan Name’**
- **‘Price/Month’**
- **‘SKU’**
- **‘Site Limit’**
You can disable the toggle button beside the **‘Active Package’** option if you want to restrict access. Below, you will see a pricing breakdown. For example:
**Pricing Breakdown**
1. Reseller Panel Price: $50
2. Created Product Price/ Customer payment: $70.00
3. Provider cost (Vultr): $5.00
4. Platform fee (Advanced plan): 30% or minimum $3 per sale (Based
5. Stripe Connect fees: Up to 3% (approx.)
6. You’ll receive : $58.50
This gives you a complete overview of the profit you will make by selling the product. Finally, click on the **‘Save & Publish’** button.
Once you are ready, click the publish button to finalize the process. Your newly created product will then appear in the product list on your dashboard, ready for use.
## **Subscribe to a Reseller Hosting Panel** [#](/docs/resell-hosting-with-self-managed-server-provider/)
If you have not yet subscribed to any reseller hosting plan, log in to your xCloud Dashboard using your credentials. Once logged in, locate and click on the **‘White Label’** tab in the dashboard. This will redirect you to the xCloud White Label onboarding flow, where you can begin setting up your reseller hosting.
After reviewing the Terms of Service and confirming that you have a Stripe account, click on the **‘Start Your Hosting Business Now’** button.
Next, choose from four different subscription plans for the xCloud White Label Control Panel. Review the available options, select the plan that best suits your needs, and click **‘Pay Now’** to proceed.
Once your payment method is configured, it’s time to set up your brand. Start by uploading your brand’s logo or icon. To do this, click the **‘Upload Logo’** button and select the file from your device. Then, provide your brand information, including Brand Name, Mailing Address, and Contact Number. After filling in all the details, click **‘Next’** to move on to the next step.
You’ll now need to integrate Stripe to process payments. If you already have a Stripe account, simply connect it by clicking ‘Connect Now’. This will redirect you to the Stripe Connect Dashboard, where you can log in with your Stripe credentials and complete the connection.
Note: If you don’t have a Stripe account yet, you’ll need to create one before proceeding.
Now it is time to create your custom hosting packages. Start by clicking on the ‘Create Hosting Plan’ button.
Next, create your custom hosting packages. Click the **‘Create Hosting Plan’** button to begin.
A pop-up will appear with various server configuration options. Choose **‘Self-Managed Server Provider’** and click **‘Next’.**
If you haven’t integrated any servers for reselling yet, click on the **‘Settings’** link and complete the integration setup. You can follow the integration process starting from Step 1 and complete the server integration and product creation process. Once your server integration is complete, you’ll be able to create products to resell.
## **Currency Conversion System for Reseller Hosting** [#](/docs/resell-hosting-with-self-managed-server-provider/)
xCloud supports real-time currency conversion to simplify pricing and sales for resellers using self-managed servers. This ensures that providers like Hetzner, which price services in Euros, can seamlessly be sold in any currency set in your xCloud White Label setup.
1. **Real-time Exchange Rates:** xCloud integrates with the **OpenExchangeRates API** to provide accurate, live currency conversions. Prices from your server providers are automatically converted to the currency of your choice.
2. **Multi-Currency Support:** Automatic detection and conversion allow white-label providers to sell hosting products in **any currency** supported by xCloud. For example, if Hetzner pricing is in Euros, xCloud can convert it to USD, GBP, or any currency you configure.
3. **Scheduled Updates:** Exchange rates are updated **daily** to ensure pricing remains accurate and consistent across all reseller products.
4. **Seamless Reseller Experience:** Once you set your preferred currency in the xCloud White Label dashboard, all integrated servers and products will display prices accordingly. Resellers can sell products directly in the chosen currency without manually calculating conversion rates.
**Example:**
- Hetzner Server Price: €50
- xCloud White Label Currency: USD
- Automatic Conversion: $55 (based on current exchange rate)
- Customer Sees: $55 and can pay in USD
This ensures your reselling business remains flexible and ready to serve customers worldwide, while keeping all pricing centralized and accurate within the xCloud dashboard.
And that’s it. This is how easily you can integrate your own server and resell with xCloud Reseller Hosting Program with fully white label branding. With support for multiple providers, xCloud ensures that you can build a hosting environment that matches your business needs while keeping everything centralized in one simple dashboard
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How To Reset File and Folder Permissions With xCloud Rescue Site? - xCloud
> Managing file and folder permissions is essential. Follow the step by step process to reset file and folder permissions with xCloud.
Managing file and folder permissions is essential. If permissions are not set right, you might face errors like **“Permission denied”** or **“403 forbidden error”** while uploading files, running scripts, or accessing website files. This can prevent changes to your website and compromise security.
Sometimes, if you edit files as the root user, your website’s system user may not own these files, leading to access issues such as 500, 502, 400 or 403 errors. Correcting these issues is simple and quick with just a few clicks in your xCloud account dashboard, ensuring your website operates smoothly and securely.
xCloud automatically manages file permissions for any operations it performs on your server. However, if you run commands manually, you will need to set the permissions yourself.
## **How Do You Reset File and Folder Permissions to Rescue Your Site?** [#](/docs/reset-file-and-folder-permissions-with-xcloud/)
Resetting the file and folder permissions is easier with xCloud. To automatically reset these permissions for your site, follow the steps below:
### **Step 1: Login and Select the Site** [#](/docs/reset-file-and-folder-permissions-with-xcloud/)
To reset the file and folder permissions of your site. First, log in to your **xCloud** dashboard, head over to the ‘**SITES**’, and choose the website where you want to make the changes.
### **Step 2: Reset the Permissions** [#](/docs/reset-file-and-folder-permissions-with-xcloud/)
Now to reset the file and folder permissions, go to the ‘**Site settings**’ option from the left navigation bar.
Then roll down a little and toggle on the **‘Repair Site Use’, ‘Update Directory Permissions’, ‘Regenerate NGINX Configurations’** and **‘Restart NGINX’** options and click on the **‘Run Now’** button. It will check all directory and file permissions and ensure they are in the right place.
This is how easily you can rescue your site by resetting the files and folder permissions.
## **Troubleshooting Further Issues** [#](/docs/reset-file-and-folder-permissions-with-xcloud/)
If you are still experiencing issues, you can check the error logs to identify what might be causing the problem. Just go to the **Site Monitoring > Logs** and check the Nginx/OpenLiteSpeed Error Log and identify the errors.
You can find more information on viewing logs and events of your server and site [here](/docs/view-logs-and-events-of-your-server-and-site/).
Still stuck? Contact ou**r** [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# Restricting Nextcloud Access to WireGuard VPN (Behind Cloudflare) - xCloud
> This guide explains how to lock down a self-hosted Nextcloud instance so it's only accessible to users connected via WireGuard VPN — even when the domain is
This guide explains how to lock down a self-hosted Nextcloud instance so it’s only accessible to users connected via WireGuard VPN — even when the domain is proxied through Cloudflare.
* * *
## Architecture [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
Component
Setup
Nextcloud
Docker
Reverse Proxy
Nginx (host)
VPN
WireGuard (wg-easy in Docker)
DNS/CDN
Cloudflare (Proxied)
* * *
## Why the Standard IP Whitelist Doesn’t Work [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
If you try to use xCloud’s IP management panel to restrict access to only your server’s public IP, you’ll hit two problems:
**1\. Cloudflare masks real client IPs** Nginx only sees Cloudflare’s IP ranges, not the actual user’s IP. So traditional `allow/deny` rules fail — everyone appears to come from Cloudflare.
**2\. VPN + Cloudflare causes a loopback** When a VPN user accesses `https://nextcloud.yourdomain.com`, the request leaves the server, goes through Cloudflare, and loops back — so Nginx sees the server’s own public IP rather than the WireGuard IP.
This is also why adding the server’s public IP (e.g. `159.195.67.152`) to the xCloud IP whitelist returns a “The selected IP address is invalid” error — the platform intentionally blocks self-referencing IPs at the UI level.
* * *
## Solution [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
The fix requires two things:
1. Teach Nginx to trust Cloudflare and restore real client IPs
2. Add proper allow/deny rules directly in the Nextcloud vHost config
* * *
### Step 1 — Trust Cloudflare IPs in Nginx [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
Create a Cloudflare trust config file so Nginx can read the actual client IP from the `CF-Connecting-IP` header:
```
echo "# Cloudflare Trusted IPs" | sudo tee /etc/nginx/conf.d/cloudflare.conf && \
curl -s https://www.cloudflare.com/ips-v4 | sed 's/^/set_real_ip_from /; s/$/;/' | sudo tee -a /etc/nginx/conf.d/cloudflare.conf && \
curl -s https://www.cloudflare.com/ips-v6 | sed 's/^/set_real_ip_from /; s/$/;/' | sudo tee -a /etc/nginx/conf.d/cloudflare.conf && \
echo "real_ip_header CF-Connecting-IP;" | sudo tee -a /etc/nginx/conf.d/cloudflare.conf
```
Copy to Clipboard
This file (`/etc/nginx/conf.d/cloudflare.conf`) tells Nginx:
- Treat all Cloudflare IP ranges as trusted proxies
- Use the `CF-Connecting-IP` header as the real client IP
* * *
### Step 2 — Add Access Control to the Nextcloud vHost [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
Open your Nextcloud site config:
```
sudo nano /etc/nginx/sites-available/YOUR-NEXTCLOUD-SITE
```
Copy to Clipboard
Inside the `server {}` block, add the following:
```
# WireGuard subnet (direct VPN access)
allow 10.42.44.0/24;
# Localhost
allow 127.0.0.1;
# Server public IP (CRITICAL)
# VPN → Cloudflare → Server loopback makes requests appear from this IP
allow YOUR_SERVER_PUBLIC_IP;
# Block everyone else
deny all;
```
Copy to Clipboard
Replace:
- `10.42.44.0/24` → your WireGuard subnet (check in wg-easy dashboard)
- `YOUR_SERVER_PUBLIC_IP` → your server’s public IP (e.g. `159.195.67.152`)
> **Why allow the server’s own public IP?** When a VPN user’s traffic routes through Cloudflare and loops back to the server, Nginx sees the server’s own public IP as the source. Allowing it here handles that case while still blocking all non-VPN internet traffic.
* * *
### Step 3 — Apply the Changes [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
Test and reload Nginx:
```
sudo nginx -t
sudo systemctl reload nginx
```
Copy to Clipboard
* * *
## Result [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
- Nextcloud is only accessible to WireGuard-connected users
- Cloudflare proxy stays enabled (SSL, DDoS protection, etc.)
- No public internet access leaks through
* * *
## Maintenance Notes [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
**Grant temporary access to a non-VPN IP:** Add a line before `deny all;` and reload:
```
allow x.x.x.x;
```
Copy to Clipboard
**Cloudflare IP range updates:** Cloudflare rarely changes their IP ranges, but if needed, rerun the Step 1 command to refresh the `cloudflare.conf` file.
**Check your WireGuard subnet:** Log into the wg-easy dashboard and confirm the subnet assigned to clients. The default is often `10.8.0.0/24` or `10.42.44.0/24` depending on your setup.
* * *
## Notes for xCloud Users [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare-2/)
- The xCloud IP Management panel (Site → IP Management) is designed for external client IPs, not for VPN-based access control. For WireGuard restrictions, Nginx-level configuration (as described above) is the correct approach.
- xCloud sites run on Nginx — the config file is located at `/etc/nginx/sites-available/your-site-name`.
- After editing Nginx config files on an xCloud server, always run `sudo nginx -t` before reloading to catch any syntax errors.
---
# Restricting Nextcloud Access to WireGuard VPN (Behind Cloudflare) - xCloud
> Restricting access to a self-hosted Nextcloud instance to a WireGuard VPN is a critical security measure in environments where sensitive data is stored or
Restricting access to a self-hosted Nextcloud instance to a WireGuard VPN is a critical security measure in environments where sensitive data is stored or shared. By default, exposing Nextcloud directly to the public internet significantly increases the attack surface, making it susceptible to credential stuffing, zero-day exploits, automated scanning, and abuse of application-level vulnerabilities.
Using WireGuard as the primary access boundary ensures that only authenticated and explicitly authorized clients can reach the service at the network level, before any application authentication occurs. This model aligns with zero-trust and defense-in-depth principles by eliminating unauthenticated public access entirely rather than relying solely on application security controls.
In this deployment, Cloudflare remains in use for DNS management and TLS termination, but it must not be treated as an access control mechanism. The challenge is enforcing VPN-only reachability while Cloudflare proxying obscures client IP addresses and VPN traffic may loop back through the public interface. This document describes a practical, production-ready approach to solving that problem and ensuring Nextcloud is accessible exclusively to WireGuard VPN users.
## Architecture [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
The setup consists of multiple components working together. Nextcloud runs inside Docker, while Nginx is deployed directly on the host as a reverse proxy in front of the container. WireGuard provides VPN access and is managed using `wg-easy`, which also runs in Docker. DNS and HTTPS proxying are handled by Cloudflare, with the domain configured as proxied.
This architecture allows the service to remain private to VPN users while still benefiting from Cloudflare features such as certificate management, DNS abstraction, and edge-layer protection.
## Problem Statement [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
### Cloudflare Masks Client IPs [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
When Cloudflare proxying is enabled, all incoming connections to Nginx appear to originate from Cloudflare IP addresses. As a result, Nginx does not see the real client IP by default. Traditional IP-based access control using `allow` and `deny` directives therefore become ineffective, since every request appears to come from Cloudflare rather than the actual client.
### VPN and Cloudflare Loopback Behavior [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
When a user connected to the WireGuard VPN accesses `https://nextcloud.domain`, the request exits the VPN tunnel, reaches Cloudflare, and is then routed back to the same server. In this scenario, Nginx sees the server’s own public IP address as the client IP instead of the WireGuard address. Without explicitly accounting for this behavior, legitimate VPN traffic would be denied.
## Solution Overview [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
The solution consists of three coordinated steps:
1. Configure Nginx to trust Cloudflare and restore the real client IP.
2. Enforce strict access control rules in the Nextcloud virtual host.
3. Validate and apply the configuration changes safely.
## 1\. Configure Nginx to Trust Cloudflare (Restore Real Client IP) [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
To make IP-based access control reliable, Nginx must be configured to trust Cloudflare and use the `CF-Connecting-IP` header as the authoritative source of the client IP. This is achieved by explicitly allowing Cloudflare’s published IP ranges and enabling Nginx’s `real_ip` module.
A dedicated configuration file was created at:
```
/etc/nginx/conf.d/cloudflare.conf
```
Copy to Clipboard
This file contains Cloudflare’s IPv4 and IPv6 address ranges and instructs Nginx to treat `CF-Connecting-IP` as the real client IP header. The following command was used to generate the file automatically:
```
echo "# Cloudflare Trusted IPs" | sudo tee /etc/nginx/conf.d/cloudflare.conf && \
curl -s https://www.cloudflare.com/ips-v4 | sed 's/^/set_real_ip_from /; s/$/;/' | sudo tee -a /etc/nginx/conf.d/cloudflare.conf && \
curl -s https://www.cloudflare.com/ips-v6 | sed 's/^/set_real_ip_from /; s/$/;/' | sudo tee -a /etc/nginx/conf.d/cloudflare.conf && \
echo "real_ip_header CF-Connecting-IP;" | sudo tee -a /etc/nginx/conf.d/cloudflare.conf
```
Copy to Clipboard
With this configuration in place, Nginx correctly restores the real client IP for all requests forwarded by Cloudflare.
## 2\. Enforce Access Control in the Nextcloud Virtual Host [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
Once Nginx can reliably determine the real client IP, strict access control rules can be applied at the virtual host level.
The Nextcloud site configuration was edited at:
```
/etc/nginx/sites-available/nextcloud-axsu.xc1.app
```
Copy to Clipboard
Inside the `server {}` block, the following rules were added:
```
# WireGuard subnet (direct VPN access)
allow 10.42.44.0/24;
# Localhost
allow 127.0.0.1;
# Server public IP (critical for VPN → Cloudflare → server loopback)
allow 139.84.141.111;
# Block all other traffic
deny all;
```
Copy to Clipboard
The WireGuard subnet allows direct VPN access. Localhost access is permitted for internal services and health checks. The server’s own public IP is explicitly allowed to accommodate VPN traffic that exits through Cloudflare and returns to the same host. All other traffic is denied, ensuring the service is not publicly reachable.
## 3\. Apply and Validate Changes [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
After updating the configuration, Nginx was tested and reloaded to safely apply the changes:
```
sudo nginx -t
sudo systemctl reload nginx
```
Copy to Clipboard
This validation step ensures that configuration errors do not disrupt the running service.
## Maintenance Considerations [#](/docs/restricting-nextcloud-access-to-wireguard-vpn-behind-cloudflare/)
If temporary or additional non-VPN access is required, an additional `allow x.x.x.x;` directive can be added to the virtual host configuration, followed by an Nginx reload. This is useful for controlled maintenance or access from trusted static IPs.
Cloudflare IP ranges rarely change, but if access issues arise after extended periods of uptime, the Cloudflare IP fetch command can be rerun to refresh the trusted address ranges.
This configuration ensures that Nextcloud is accessible only to authenticated WireGuard VPN clients while preserving the operational and security benefits provided by Cloudflare. Real client IPs are correctly restored, VPN loopback behavior is explicitly handled, and all unintended public access paths are effectively blocked. The result is a secure, maintainable, and production-ready deployment suitable for environments with strict access control requirements.
---
# How to Discourage Search Engines from Indexing Your Site? - xCloud
> Learn how to discourage search engines from indexing your site to make sure whether to index your WordPress site in what circumstances.
While most WordPress site owners aim to get their sites indexed, there are times when you might want to keep search engines away—such as during development or maintenance. In these cases, it’s best to discourage search engines from indexing your site. In [**xCloud**](/), how does search engine visibility work by default?
- Will be discouraged in the demo site & staging site
- Will not be discouraged in live site
## **How to Configure Search Engine Visibility in xCloud?** [#](/docs/search-engine-visibility-in-xcloud/)
Using two different methods—**WordPress built-in feature & xCloud hosting**, you can configure your WordPress site search engine visibility. By any chance, if you forgot to configure from WordPress end, you can do it with xCloud hosting. The changes will automatically reflected on the WordPress end. No need to go back and forth between WordPress & xCloud dashboard.
Let’s see the step-by-step guidelines below on how you can configure search engine visibility using two different methods.
### **1\. Using WordPress Built-in Feature** [#](/docs/search-engine-visibility-in-xcloud/)
Editing the robots.txt file in WordPress is straightforward, thanks to its built-in settings. To do this, log in to your WordPress admin dashboard and navigate to **‘Settings’ → ‘Reading**.’ Scroll down to the **‘Search Engine Visibility’** option, and check the box that says ‘**Discourage search engines from indexing this site**.’
Once selected, click on **Save Changes**. With this simple process, WordPress will automatically update its robots.txt file to prevent search engines from indexing your site.
### **2\. Using xCloud Hosting** [#](/docs/search-engine-visibility-in-xcloud/)
In xCloud, you will see the search engine visibility option in many places. For live sites, this option will not be discouraged from system setting as best practice. While adding a new site, you’ll get this option under **‘More Advanced Settings’** as shown below.
Again, stating that for the Staging & Demo site, this option is being discouraged by default. What if you don’t check this option while adding a site? No worries, you can do it later; as we mentioned, we can use this option in multiple places in xCloud.
Once you log into your xCloud dashboard, click on **‘Sites’** and from the list of multiple sites (if you have) enter the sites for which you want to discourage search engine indexing.
On the resulting page, click on **‘Site Settings’** from the left side panel. Scroll down a bit to find the option ‘Search Engine Visibility’, click to turn on the toggle button, & hit the ‘Save Settings’ option to complete the configuration. Well, you’ve done your part, _now it’s up to search engines to honor this request._
This is how you can easily configure search engine visibility directly from the xCloud dashboard to discourage indexing your WordPress site.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# Protecting Our System With Security and Vulnerability Disclosure Protocols - xCloud
> Here you will find the security and vulnerability disclosure protocols by xCloud.
## **Summary** [#](/docs/security-and-vulnerability-disclosure-protocols/)
At [**xCloud**](/), we prioritize top-notch security and vulnerability disclosure protocols. Our team puts in the effort to safeguard user data, though we acknowledge that no system is entirely immune to potential risks. Hence, we welcome the open and responsible reporting of vulnerabilities via our Security and Vulnerability Disclosure Program. Through collaboration, we aim to enhance the safety and security of our users’ experience.
## **How To Report Security Issues** [#](/docs/security-and-vulnerability-disclosure-protocols/)
We value the help of security researchers and the public in spotting potential issues. If you think you’ve found a security problem in our xCloud system, please let us know promptly.
Here’s how you can reach out:
Send an email to **support@xcloud.host** or visit this [**link**](/support/) to provide as much detail as you can about the potential problem, including:
- Description of the issue
- Steps to recreate it
- How it could affect our users
- Any other useful information or resources
## **Instructions** [#](/docs/security-and-vulnerability-disclosure-protocols/)
We kindly request that you:
- Refrain from exploiting any vulnerabilities you find.
- Avoid any actions that could compromise the reliability or integrity of our services or data.
- Hold off on publicly sharing the bug until xCloud has had the chance to address it.
## **Prerequisites and Ethical Reporting** [#](/docs/security-and-vulnerability-disclosure-protocols/)
- You must follow all relevant laws.
- Only use your own test accounts to find vulnerabilities in xCloud’s products, services, or code.
- Accessing or changing user data without the account owner’s permission is strictly forbidden.
## **Acknowledging Security Measures** [#](/docs/security-and-vulnerability-disclosure-protocols/)
After you’ve reported a vulnerability, here’s what you can anticipate from us:
- We’ll send you an acknowledgment email within 3 business days of receiving your report.
- Our team will assess the reported vulnerability to confirm its validity.
- If the issue is confirmed, we’ll promptly address it and keep you updated on our progress.
- Upon resolution, we’ll recognize your contribution in our release notes, unless you prefer to remain anonymous.
### **Rules Of Engagement** [#](/docs/security-and-vulnerability-disclosure-protocols/)
- NEVER target xCloud users or their resources (e.g. Servers, Sites, Teams, etc.). This is strictly prohibited. ONLY test against your own accounts and resources.
- Please make sure to provide detailed reports with reproducible steps for any vulnerabilities found. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for reputation.
- If the same issue is reported by multiple people, we will only recognize the first report with a clear description and steps to reproduce it.
- Please help make a good faith effort to avoid privacy violations, destruction of data, or service degradation.
- If you find a vulnerability, please do not exploit it beyond a proof-of-concept. Do not dump the database, do not pull unnecessary files or information
- Do not perform any DoS or DDoS, social engineering, or physical attacks against xCloud, WPDeveloper, or our users.
- Do not host personal or commercial servers or sites under your testing account. We may delete/remove your testing account without any prior notice.
- When testing xCloud, do not launch servers greater than 4GB, and do not launch more than 3 concurrent servers at a time.
## **The Following Domains Are In Scope** [#](/docs/security-and-vulnerability-disclosure-protocols/)
- [**xcloud.host**](http://hidden-hamlet-226309.wp1.sh) – Priority: Medium
- [**app.xcloud.host**](http://app.xcloud.host) – Priority: Critical
- xCloud Playground – Priority: Medium
Domains not listed above are out of scope.
## **Out Of Scope Domains** [#](/docs/security-and-vulnerability-disclosure-protocols/)
- Any domains or resources not mentioned in the previous list are out-of-scope.
- Any resource used as a staging platform by the xCloud team is strictly prohibited.
- Any domains or resources used by the xCloud users are out-of-scope.
## **Qualifying Vulnerabilities** [#](/docs/security-and-vulnerability-disclosure-protocols/)
xCloud will accept reports of any vulnerability that substantially affects the confidentiality or integrity of any eligible xCloud service. Eligible vulnerabilities include, but are not limited to:
- Remote Code Execution (RCE)
- Privilege Escalation and Cross Instance Data Leakage/Access
- Server-side injection vulnerabilities, including SSRF, SQL, and XML injection
- Client-side vulnerabilities, including Stored XSS and CSRF attacks (only high impact)
- Directory traversal that exposes sensitive information
- Disclosure of sensitive or personally identifiable information
- Access Control Vulnerabilities (BAC, IDOR, etc.)
- Broken authorization leads to access to other xCloud user records
- Significant security misconfiguration with a verifiable vulnerability
- Exposed system credentials, disclosed by xCloud or its employees, that pose a valid risk to an in-scope asset
## **Non-Qualifying** **Vulnerabilities** [#](/docs/security-and-vulnerability-disclosure-protocols/)
The following vulnerability types will not qualify for the Vulnerability Disclosure Program and should not be tested by any security researchers:
- Automated scan output without any real proof-of-concept and impact
- Password complexity requirements
- Email verification/validation issues
- Source code disclosure vulnerabilities
- Email bombing
- Lack of rate limiting
- Vulnerabilities in users’ own infrastructure or virtual private servers (VPS), including websites, databases, etc. These should be reported to the respective server providers or vendors.
- Self-XSS reports will not be accepted
- Clickjacking attacks
- Content Spoofing
- Missing security-related HTTP headers without any proof of exploitability.
- Lack of Secure/HTTPOnly flags on non-sensitive Cookies
- Weak Captcha / Captcha Bypass
- Username/email enumeration
- Phishing attacks on users
- Social Engineering Attacks
- Missing or incorrect SPF records of any kind
- Missing or incorrect DMARC records of any kind
- DNS configuration and SSL-related issues
- Server configuration issues
- Banner or version disclosures
- DoS/DDoS attacks, brute force
- Blackhat SEO techniques
- CSV Injection
- Any submission determined to be low risk, based on theoretical attack vectors, requiring significant user interaction, or resulting in minimal impact
- Vulnerabilities on third-party libraries without showing specific impact on the target application (e.g. a CVE with no exploit)
- Exposed credentials that are either no longer valid or do not pose a risk to an in-scope asset
- Broken links in blog pages
- Any bug that relies upon an outdated browser
- Hacking discount coupons
- Issues where paid features are accessible on free accounts with no inherent “security” implications
## **Report Submission Requirements** [#](/docs/security-and-vulnerability-disclosure-protocols/)
To report a valid bug, please include the following information:
- Full description of the vulnerability being reported, including the exploitability and impact
- Evidence and explanation of all steps required to reproduce the submission, which may include:
1. Videos or Step-by-step screenshots
2. Exploit code
3. Traffic logs
4. Web/API requests and responses
5. IP address used during testing
\* Submit the testing account details used by the researcher. This is mandatory.
## **Changes To Program Terms** [#](/docs/security-and-vulnerability-disclosure-protocols/)
The Vulnerability Disclosure Program, including any or all of its policies, is subject to change or cancellation by xCloud at any time, without any prior notice. By continuing to participate in the Vulnerability Disclosure Program, you accept the Program Terms, as modified.
## **Recognition** [#](/docs/security-and-vulnerability-disclosure-protocols/)
We recognize the effort and commitment required to uncover security vulnerabilities and appreciate researchers who help us maintain xCloud’s security. As a gesture of gratitude for confirmed and resolved security vulnerability disclosures, we will add you to our Hall Of Fame page as one of our valued members. Please note that we do not offer any monetary rewards or bounties for vulnerability disclosures. Recognition through our Hall of Fame is discretionary and assessed on a case-by-case basis.
## **Is There a Bug Bounty Program for xCloud?** [#](/docs/security-and-vulnerability-disclosure-protocols/)
xCloud currently does not offer a bug bounty program. While such programs can uncover different flaws, they sometimes attract many people interested in monetary gain rather than genuinely enhancing the platform. Therefore, we chose not to compensate for the bug bounty program.
At xCloud, our commitment lies in furnishing a secure environment for all users. Your assistance in identifying areas for improvement is invaluable. Together, we can uphold xCloud as a reliable hosting solution for WordPress.
---
# Enhancing Server and Website Security with xCloud - xCloud
> Learn how to enhance server and website security with xCloud & keep your site and server management safe from unwanted threats.
xCloud ensures robust security for your websites by default, locking down servers during the provisioning process. However, it’s important to maintain good security practices and assist clients in doing so to further enhance security.
This documentation details the security measures xCloud implements by default, allowing you to create a comprehensive security checklist for setting up new websites on xCloud.
## xCloud’s Network and Server Security [#](/docs/server-and-website-security-with-xcloud/)
### 1\. SSH Lockdown [#](/docs/server-and-website-security-with-xcloud/)
The root user is restricted to secure SSH access only to minimize the risk of unauthorized access.
### 2\. SSH Key Authentication Recommended [#](/docs/server-and-website-security-with-xcloud/)
SSH Key Authentication is more secure than password-based authentication, supporting public and private key authentication.
### 3\. System User Isolation [#](/docs/server-and-website-security-with-xcloud/)
System users created via our platform are completely isolated and secure from one another, each with only the essential permissions assigned.
### 4\. Managing Server Access: Sudo Users vs. Site Users [#](/docs/server-and-website-security-with-xcloud/)
In [**xCloud Sudo users**](/docs/usudo-users-and-site-users-in-xcloud/) have full server-wide access, allowing them to control all aspects of the server. In contrast, site users are restricted to managing a single site on the server, ensuring they cannot access or modify other sites’ files or server configurations.
### 5\. Firewall Control – Linux UFW Configuration [#](/docs/server-and-website-security-with-xcloud/)
At xCloud, the [**Linux Uncomplicated Firewall**](/docs/how-to-configure-firewall-management-in-xcloud/) is configured during the server provisioning process.
### 6\. Strict Port Control [#](/docs/server-and-website-security-with-xcloud/)
By default, only essential ports are open (22/TCP for SSH, 80/TCP for HTTP, and 443/TCP for HTTPS, reducing attack risks. Users can also change the default port if needed.
### 7\. Fail2Ban Preconfigured [#](/docs/server-and-website-security-with-xcloud/)
[**Fail2Ban**](/docs/fail2ban-in-xcloud-enhancing-server-security-with-ease/), an intrusion prevention software, is enabled on xCloud by default to protect against brute-force attacks on the SSH port.
### 8\. Vulnerability Scanner [#](/docs/server-and-website-security-with-xcloud/)
With xCloud’s [Vulnerability Scanner](/docs/vulnerability-checker-in-xcloud/), you can scan and identify the security issues of core, plugin, and theme versions that are installed on your WordPress site. Also, can configure auto updates to handle them automatically.
## xCloud’s WordPress Security [#](/docs/server-and-website-security-with-xcloud/)
### 1\. Secure PHP Version [#](/docs/server-and-website-security-with-xcloud/)
By default, new WordPress websites are provisioned with the [**most current version of PHP**](/docs/how-to-upgrade-php-version-with-xcloud-hosting/), ensuring compatibility and security.
### 2\. Latest WordPress Version [#](/docs/server-and-website-security-with-xcloud/)
New websites created by any user employ the latest WordPress version to avoid unpatched vulnerabilities.
### 3\. Disable Directory Browsing/System File Protection [#](/docs/server-and-website-security-with-xcloud/)
xCloud prevents access to critical WordPress files and directories.
### 5\. Disable PHP Execution in Uploads and Themes Directories [#](/docs/server-and-website-security-with-xcloud/)
xCloud blocks maliciously uploaded PHP files in WordPress directories.
7\. SFTP and SSH Access Only
xCloud enforces the use of secure server connections exclusively via SFTP and SSH.
## Additional WordPress Security Options [#](/docs/server-and-website-security-with-xcloud/)
### 1\. Security Headers [#](/docs/server-and-website-security-with-xcloud/)
Customize security headers to prevent cross-site scripting and clickjacking. Beyond default measures, xCloud offers customizable security options to meet specific needs:
### 2\. Web Application Firewall (WAF) Options [#](/docs/server-and-website-security-with-xcloud/)
Integrates with [**7G and 8G firewalls**](/docs/use-xcloud-7g-firewall-on-nginx/) to protect against malicious requests, bad bots, and spam referrers.
### 3\. Website Isolation Through System Users [#](/docs/server-and-website-security-with-xcloud/)
Assign unique system users to websites to keep them isolated and prevent cross-infection in case of a compromise.
### 4\. Disable XML-RPC [#](/docs/server-and-website-security-with-xcloud/)
Disabling the outdated and insecure XML-RPC method if not in use. It can be customized from PHP settings.
### 5\. 1 Click SSL Certificates [#](/docs/server-and-website-security-with-xcloud/)
Users are encouraged to use SSL certificates for enhanced security. With just one click, SSL certificates can be implemented in xCloud.
## Product Security [#](/docs/server-and-website-security-with-xcloud/)
### 1\. Two-Factor Authentication (2FA) on account [#](/docs/server-and-website-security-with-xcloud/)
It is highly recommended for password-based authentication, requiring a second form of identification.
### 2\. Permission Levels [#](/docs/server-and-website-security-with-xcloud/)
Different permissions can be assigned to users or teams within the xCloud dashboard including server/site access, billing, user data, and message permissions.
### 3\. Password and Credential Storage [#](/docs/server-and-website-security-with-xcloud/)
xCloud enforces a complex password standard, storing credentials in hash form to reduce the risk of password theft and unauthorized access.
### 4\. Credit Card Information [#](/docs/server-and-website-security-with-xcloud/)
Payments are handled by the payment gateway (Stripe), ensuring no access to your credit card information.
### 5\. Best Practices [#](/docs/server-and-website-security-with-xcloud/)
Automated server configuration follows industry best practices for securing your server or web applications.
Still, facing any security issues? [**Contact our support team**](/contact/) for any of your queries.
---
# Server Gets Disconnected - xCloud
> Whether you are managing a self-managed server or xCloud server, you might see the 'server gets disconnected' for a variety of reasons. Let us troubleshoot
Whether you are managing a self-managed server or xCloud server, you might see the ‘server gets disconnected’ for a variety of reasons. Let us troubleshoot what you can do when that happens. With **[xCloud](/)** you have two types of servers: xCloud server and Self-Manged server.
How do you know if your server is connected? When you see a green dot with the server name, then it means the server is connected and you will have the ‘Connected’ status shown below the server name.
However, if your server is disconnected, you will see the status ‘**Disconnected**’ and the dot will become gray, as shown below:
If your server is disconnected, the first things you can do before troubleshooting are below:
- Refresh your server
- Restart server
## **Why Your Server Gets Disconnected & Fixes** [#](/docs/server-gets-disconnected/)
### **CPU, Storage, Or Memory Issue** [#](/docs/server-gets-disconnected/)
If the Server CPU, storage, or memory is full or close to 100% used, you might encounter this server disconnected issue. To fix this, you need to upgrade (extend CPU storage, memory limit, etc) your server.
### **Blocked IP Address** [#](/docs/server-gets-disconnected/)
If your server provider has blocked xCloud IP address for some reason, your server might be disconnected. In that case, you need to whitelist xCloud IP addresses.
### **Credentials Issue** [#](/docs/server-gets-disconnected/)
If your credentials or server name has been changed for some reason, or someone from your team has changed the API keys, you might get this issue. In that case, contact support in xCloud.
### **Server Downtime** [#](/docs/server-gets-disconnected/)
Sometimes, the server faces downtime due to technical issues from the provider’s end. Contact the server provider to find out (**[Vultr](https://www.vultr.com/)**, **[DigitalOcean](https://www.digitalocean.com/)**, **[GCP](https://cloud.google.com/)**, etc). If the server is in xCloud, contact our support.
### **Deleted From The Provider** [#](/docs/server-gets-disconnected/)
If your server has been deleted from the provider end somehow. To have the fix, check if your server has been deleted from the provider end.
### **Billing** [#](/docs/server-gets-disconnected/)
Check Billing on your server provider end and in xCloud.
---
# How to Update a Server IP Address After Provider Relocation With xCloud
> Learn how to handle a server IP address change after provider relocation, reconnect the server in xCloud, update DNS records, and verify website access safely.
If your cloud provider relocates your server, replaces the public IPv4 address, or moves the physical host to another data center, the server may temporarily disconnect from xCloud. This guide explains what to check, what to send xCloud Support, and how to bring your sites back online safely after a server IP address change.
## When this guide applies [#](/docs/server-ip-address-change-xcloud/)
Use this guide when the server itself remains the same, but the provider changes the public IPv4 address. Common examples include a data center relocation, physical server maintenance, provider network migration, or an assigned IPv4 replacement.
This guide is not for rebuilding a deleted server, moving sites to a new server, or changing providers through a full migration. If the operating system, server data, or xCloud services were removed, follow the relevant migration or server recovery process instead.
## What happens when the server IP address changes [#](/docs/server-ip-address-change-xcloud/)
xCloud connects to your server using the server details saved in the panel. If the provider changes the public server IP address, xCloud may still try to contact the old IP. In that case, the server can appear disconnected even when the server itself is still running at the provider.
Your websites may also stop loading if their DNS records still point to the old server IP address. DNS and xCloud panel connectivity are related, but they are not the same thing. Updating xCloud helps the panel reconnect to the server. Updating DNS helps visitors reach the sites hosted on that server.
## Before you start [#](/docs/server-ip-address-change-xcloud/)
- Confirm the provider relocation or IP change is complete.
- Copy the new public IPv4 address from your provider dashboard or provider email.
- Confirm the server data, operating system, services, and xCloud agent were not reinstalled or removed.
- Check whether your domains use xCloud DNS records, your registrar DNS, or Cloudflare DNS.
- Avoid reinstalling xCloud or recreating the server unless xCloud Support confirms it is required.
## Step-by-step troubleshooting [#](/docs/server-ip-address-change-xcloud/)
### 1\. Wait until the provider relocation is finished [#](/docs/server-ip-address-change-xcloud/)
Do not update records while the provider is still moving the server unless the provider has already confirmed the final new IPv4 address. During relocation, downtime can be expected and the server may not respond to xCloud, SSH, or website traffic.
### 2\. Confirm the new public server IP address [#](/docs/server-ip-address-change-xcloud/)
After the relocation finishes, copy the new IPv4 address exactly as shown by the provider. If your provider also gives a new IPv6 address, keep it for reference, but xCloud Support usually needs the new public IPv4 first when reconnecting the server.
### 3\. Check whether the server still responds [#](/docs/server-ip-address-change-xcloud/)
If you have SSH access, test whether you can reach the server at the new server IP address. Use SSH keys where possible. If SSH does not respond, check the provider firewall, server power state, and provider maintenance notice before changing anything in xCloud.
```
ssh root@NEW_SERVER_IP
```
Copy to Clipboard
If you cannot or do not want to use SSH, share the new IP with xCloud Support and mention that the provider completed a relocation. Support can help verify the server connection from the xCloud side.
### 4\. Do not reinstall xCloud if the server data is intact [#](/docs/server-ip-address-change-xcloud/)
If only the public IP changed and the same server data, OS, services, and xCloud agent are still present, you normally do not need to reinstall xCloud or recreate the server. Reinstalling can create unnecessary risk and may not be needed for a simple provider-side IP change.
### 5\. Ask xCloud Support to reconnect the server in the panel [#](/docs/server-ip-address-change-xcloud/)
If the server appears disconnected in xCloud after the provider changes the IP address, contact xCloud Support with the new IPv4 address. Support can verify the server record and update the saved server IP from the panel side where required.
Send this information:
- The affected xCloud server name.
- The old server IP address, if available.
- The new public IPv4 address.
- The provider relocation notice or a short summary of what changed.
- Whether SSH works with the new server IP address.
- Whether your sites are using Cloudflare, registrar DNS, or xCloud-managed DNS records.
### 6\. Update DNS records for each domain [#](/docs/server-ip-address-change-xcloud/)
After the server IP is confirmed, update the A records for domains hosted on that server so they point to the new IPv4 address. This can include your root domain, www record, subdomains, staging domains, and any custom domains mapped to apps on the server.
If you use Cloudflare, update the DNS A records in Cloudflare as well. If your site uses a proxied Cloudflare record, visitors still reach Cloudflare first, but Cloudflare must know the correct origin server IP address to connect to your server.
Related docs:
- [How To Setup DNS Record In xCloud?](/docs/how-to-setup-dns-record-in-xcloud-server/)
- [Integrate Cloudflare for DNS Management with xCloud](/docs/using-xcloud-with-cloudflare-for-dns-management/)
- [Cloudflare: Create DNS records](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/)
### 7\. Verify xCloud and website access [#](/docs/server-ip-address-change-xcloud/)
After xCloud Support updates the server record and DNS points to the new IP, check the server status in xCloud. Then open the websites hosted on that server in a browser. DNS changes can take time depending on your DNS provider and TTL settings.
Also check SSL status if domains were proxied through Cloudflare or if the origin server IP address was changed recently. If SSL fails or the server still appears disconnected, share the exact error with Support instead of retrying random fixes.
(Screenshot: xCloud server page showing the server connected after the IP update.)
## What xCloud Support can check [#](/docs/server-ip-address-change-xcloud/)
- Whether the xCloud server record still points to the old IP address.
- Whether the server can reconnect after the new IP is saved.
- Whether xCloud services and the xCloud agent appear intact.
- Whether the server still shows disconnected after the IP update.
- Whether DNS or SSL status needs a follow-up check from the xCloud dashboard.
## What is outside standard support [#](/docs/server-ip-address-change-xcloud/)
- Provider-side relocation scheduling, provider downtime, or provider network issues.
- Provider firewall rules, billing, or account access problems.
- Custom DNS architecture outside the xCloud dashboard.
- Application-level issues unrelated to the server IP change.
## Prevention tips [#](/docs/server-ip-address-change-xcloud/)
- Keep provider relocation notices and maintenance emails until the change is complete.
- Record the old and new server IP addresses before contacting Support.
- Use a lower DNS TTL before planned provider maintenance when possible.
- Keep SSH key access ready so you can verify the server after the provider move.
- Keep recent backups before planned infrastructure changes.
## Expected result [#](/docs/server-ip-address-change-xcloud/)
After the new server IP address is saved in xCloud and DNS records are updated, the server should show as connected in the xCloud panel, and domains hosted on the server should resolve to the new IP address.
## FAQ [#](/docs/server-ip-address-change-xcloud/)
### Can I reconnect the same server after the provider changes the IP address? [#](/docs/server-ip-address-change-xcloud/)
Yes. If the same server data, OS, services, and xCloud agent remain intact, the server can usually be reconnected by updating the saved server IP and verifying connectivity. Contact xCloud Support with the new IPv4 address.
### Do I need to reinstall xCloud? [#](/docs/server-ip-address-change-xcloud/)
Usually no. A provider-side IP change does not automatically require a fresh xCloud installation. Reinstall only if Support confirms that the existing installation or server data is no longer usable.
### Will my websites work automatically after xCloud reconnects? [#](/docs/server-ip-address-change-xcloud/)
Not always. xCloud panel connectivity and public website DNS are separate. You still need to update the DNS A records for domains hosted on the server so they point to the new IP address.
### What if I use Cloudflare? [#](/docs/server-ip-address-change-xcloud/)
Update the Cloudflare DNS A records to the new origin server IP address. If the record is proxied, Cloudflare will continue to sit in front of the site, but the origin server IP address behind Cloudflare must be correct.
### What should I send xCloud Support? [#](/docs/server-ip-address-change-xcloud/)
Send the server name, old IP if available, new IPv4 address, provider relocation notice, whether SSH works, and the domains affected. This helps Support reconnect the server and guide the DNS follow-up faster.
## Related docs [#](/docs/server-ip-address-change-xcloud/)
- [Troubleshooting Guide: xCloud Server Disconnected, SSL Failed Or Renew Issue](/docs/troubleshooting-guide-xcloud-server-disconnected/)
- [Server Gets Disconnected](/docs/server-gets-disconnected/)
- [How To Connect Existing Fresh Ubuntu Server On xCloud From Any Provider?](/docs/how-to-set-up-server-with-other-providers/)
---
# How to Set Site Limits On Custom Hosting Plans with Reseller Hosting Program - xCloud
> Learn how to set site limits on custom hosting plans with xCloud White Label and tailor packages to fit your brand and customer needs
With xCloud White Label, you can create and sell custom hosting packages under your own brand, giving you full control over pricing, features, and limitations. One key aspect of tailoring your hosting plans is setting site limits, which helps define how many websites a customer can host under each plan. And now, you can set site limits on custom hosting plans with your reseller program.
By setting up the site limit on the server within the xCloud white label dashboard, you can offer customized hosting plans to your customers. Follow the step-by-step guide on how to set a site limit on your plans with xCloud White Label.
## **Step 1: Log in to Your xCloud Dashboard** [#](/docs/set-site-limits-on-custom-hosting-plans-reseller/)
First, log in to your xCloud dashboard using your credentials. Once you are logged in, navigate to the **‘White Label’** tab on the dashboard. Clicking on this tab will redirect you to the xCloud White Label landing page, where you can manage your white label settings and create custom hosting packages.
## **Step 2: Create Custom Hosting Packages** [#](/docs/set-site-limits-on-custom-hosting-plans-reseller/)
On the dashboard of White Label, click on the **‘Add Product’** button to begin creating your custom hosting package. A popup window will appear with server configuration options.
Here, you can choose your server plan by selecting between **‘General’** and **‘Premium’** plans based on your needs.
Next, select your desired server size from the available options. As you select different plans and server sizes, you will be able to see the corresponding prices. Once you have made your selections, click on the **‘Next’** button to proceed.
## **Step 3: Customize Your Hosting Plan & Implement Site Limit** [#](/docs/set-site-limits-on-custom-hosting-plans-reseller/)
In this step, you will customize the details of your hosting package. Enter a unique **‘Plan Name’** for your package or keep it blank and it will take the original product you have chosen. In the **‘Custom Price/Month’** field, set the monthly price you wish to charge your customer.
Then enter the number of the sites into the **‘Site Limit’** field that you want to allow for the users who will the plan. After that provide a **‘SKU’** (Stock Keeping Unit). You can also deactivate any package by clicking on the **‘Active Package’** button. Once all the details are filled out, you can make it immediately available for purchase by clicking on the **‘Save and Publish’** button.
_Note: Remember, your custom price needs to be higher than the server cost to ensure you make a profit. Also, the Stripe fees will be handled by the Reseller._
After completing these steps, you will be able to see your newly created product in the dashboard under your list of plans. Your custom hosting package is now ready to be offered to your customers under your own branding.
That’s it! This is how easily you can set site limits on your product with xCloud white label.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set up Auto Responder Email with xCloud MailBox Addon - xCloud
> Learn how to quickly Set up Auto Responder Email using the xCloud MailBox Addon to manage emails when you're away.
Automated email responses are a helpful tool for maintaining communication when you’re unavailable or managing high volumes of messages. The [**xCloud MailBox Addon**](/docs/how-to-set-up-xcloud-mailbox-addon/) offers a simple way to set up an Auto Responder that sends automatic replies based on your preferences.
Follow the steps below to set up auto responder email easily with xCloud MailBox quickly.
## **Step 1: Log in to the MailBox** [#](/docs/set-up-auto-responder-email-with-mailbox/)
First, log in to your MailBox, go to the **‘Settings’** option, and click on the ‘Autoresponder’ option from the left sidebar.
## **Step 2: Set up Auto Responder Email** [#](/docs/set-up-auto-responder-email-with-mailbox/)
Next, enable the **‘Autoresponder’** option to start setting the email that will be sent automatically. Then write a **‘Subject’** and **‘Message’** into the dedicated fields.
Then, enable the **‘Date Range’** button if you want to set it for a certain timeframe. Choose a **‘Start Date’, ‘Start Time’, ‘End Date ’** and**’ End Time’** of this email and hit on the ‘Save’ button.
And that’s it. This is how easily you can set up an Auto Responder with the xCloud MailBox Addon is a easy process that ensures your contacts receive timely replies, even when you’re unavailable.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up Email Forwarding with xCloud MailBox Addon - xCloud
> Learn how to easily set up email forwarding with xCloud MailBox Addon to manage multiple inboxes from one place.
Mail forwarding allows you to automatically send a copy of incoming emails from one mailbox to another address. This is useful if you want to manage multiple email addresses from a single inbox.
For example, if you own info@yourdomain.com and want to receive those emails at your main address you@yourdomain.com, you can set up forwarding. All emails sent to info@yourdomain.com will automatically be forwarded to you@yourdomain.com. You can also forward emails from multiple mailboxes.
Follow the steps below to set up email forwarding with xCloud MailBox Addon:
## **Step 1: Go to Your MailBox Account** [#](/docs/set-up-email-forwarding-with-xcloud-mailbox-addon/)
First, log in to your MailBox account and click on the **‘Mail Forwarding’** tab in the dashboard.
## **Step 2: Add a New Forwarding Email Address** [#](/docs/set-up-email-forwarding-with-xcloud-mailbox-addon/)
Click the **‘Add New’** button. A popup will appear allowing you to add a new forwarding email address. Select the email account you want to forward from using the dropdown menu.
Enter the destination email address in the **‘Forward email to’** field.If you want to keep a local copy of all forwarded messages, check the corresponding box.Finally, click on the **‘Save Forwarding’** button.
_**Note:** You can set up to 20 forwarding addresses for each mailbox._
You can also add one or more forwarding addresses by clicking **‘Add More Forward Address’** to automatically forward all messages received in your account.
To delete an existing forwarding address, click the three-dot icon next to the address, select **‘Delete’**, and save the changes by clicking the **‘Save’** button.
And that’s it this is how easily you can set up email forwarding with the MailBox Addon. It is a simple and effective way to manage multiple email accounts from a single inbox.
Still stuck? Contact our [**dedicated support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Set Up Git Integration for an Existing WordPress or Custom PHP Site - xCloud
> Learn how to set up Git integration for an existing site in xCloud, from selecting a GitHub provider to enabling push-to-deploy in a few easy steps.
xCloud lets you add Git integration to an existing WordPress or Custom PHP site that is not already connected to Git. From the site’s Git tab, you can select a connected GitHub provider, confirm the repository name, review the generated .gitignore, and start the setup in a single flow.
When the setup runs, xCloud creates a private GitHub repository, pushes the current site contents as the first commit, and configures the deploy key and webhook for you. Instead of wiring up a repository and connecting it by hand, you can set everything up from one page and start using push-to-deploy right away.
## Prerequisites for Git setup: [#](/docs/set-up-git-integration-for-existing-wordpress-or-php-site/)
- Available site types are WordPress or Custom PHP.
- At least one connected GitHub provider exists for the team.
## Step 1: Open the Site’s Git Tab [#](/docs/set-up-git-integration-for-existing-wordpress-or-php-site/)
First, go to your existing WordPress site. Then go to the site sidebar and click on Git from the navigation menu.
## Step 2: Select Your Provider and Repository [#](/docs/set-up-git-integration-for-existing-wordpress-or-php-site/)
On this page, select your GitHub account from the Git Provider dropdown menu, then enter the repository name you want to deploy.
If the team has no connected GitHub providers, you need to integrate your GitHub account first. Just click on the Manage Git Providers option and connect your account in a few clicks.
## Step 3: Review the Generated .gitignore & Start the Setup [#](/docs/set-up-git-integration-for-existing-wordpress-or-php-site/)
Below the provider and repository fields, you will find a generated .gitignore. For WordPress sites, xCloud pre-populates entries for WordPress core, config, uploads, cache, backups, and environment files. If a protected default entry is removed, xCloud shows a warning before submission.
Once you have confirmed the provider, repository name, and .gitignore contents, click the Setup Git Integration button to proceed. xCloud begins creating the repository, pushing your site contents, and configuring the deploy key and webhook.
And that’s it. This is how easily you can set up Git integration for existing WordPress and PHP sites easily. After the setup completes and the page is refreshed, xCloud shows the normal Git Settings page for the site.
Still stuck? Feel free to reach out to our **[support team](https://support.xcloud.host/)**.
---
# How To Set Up Hetzner Server In xCloud Host? - xCloud
> Ready to deploy? Set up Hetzner server in xCloud in minutes. Streamline your WordPress hosting journey with xCloud Self-Managed hosting today!
You can easily set up Hetzner server in **[xCloud](/)**. This self-managed hosting aims to simplify the hosting and managing of WordPress sites, allowing developers and agencies to focus on building great websites without worrying about the underlying infrastructure. Now let us follow these steps to get you started.
## **Step 1: Sign Up/Login With xCloud** [#](/docs/set-up-hetzner-server-in-xcloud/)
First, you will need to visit the xCloud website and you have to sign up or log in to xCloud with your credentials.
If you have already an account please visit our [**app URL**](https://app.xcloud.host/) to log in to your account to set up a Hetzner server in xCloud Host.
## **Step 2: Create Your Hetzner Server In xCloud** [#](/docs/set-up-hetzner-server-in-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the “**Add New Server**” button from your dashboard.
The next screen will provide the list of our available server providers. Select the Hetzner option from the list. The billing of the server will be handled on your Hetzner account.
Now, before going to the next step, you need to create an API token to connect your Hetzner account to xCloud Host. To do that, log in to your [**Hetzner Cloud Console account**](https://accounts.hetzner.com/login). Then, select a project and navigate to ‘**Security → API tokens’** from the left sidebar.
Click on the API tab to generate a new API or select an existing one. Now, hit the ‘**Generate API token**’, give a description (xCloud, for example), and select the permission as ‘**Read & Write**’. While generating a New API key, we always recommend you select the ‘**Read & Write**’ permission.
Your Hetzner API token will be created instantly. Copy the API key to set up a Hetzner server in xCloud.
## **Step 3: Connect Account & Add Necessary Information** [#](/docs/set-up-hetzner-server-in-xcloud/)
Now, go back to xCloud dashboard to create a new server with Hetzner. Select your existing server or create a new account. Then, set an API label as you prefer. The label can be anything to help you track or remember a particular one from multiple tokens. After that, paste the API token that you have copied from the Hetzner on the token field.
You will be taken to the server creation page after successfully integrating your Hetzner account. Now you need to provide the **Server name**, your preferred **Server Size** (CPU, RAM, storage), and the **Region** nearest to you and your visitors. Then select the **‘Database’** and hit on the **‘Next’** button
_**Note:** Now**,** MySQL 8.0 and MariaDB database servers are now available._
We recommend at least a 2GB/ 1 shared CPU server for 10-20 brochure sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server.
We are almost done with our server creation of Hetzner in xCloud. After submitting the form this might take up to 10-15 minutes to make the Hetzner server live and ready to install a lightning-fast WordPress Site.
## **Automatic Firewall Setup for Your Hetzner Server** [#](/docs/set-up-hetzner-server-in-xcloud/)
During this process, xCloud will automatically add a firewall with three ports to your Hetzner server.
_**Note:** It is strongly recommended that you do not remove this firewall. It helps protect your server._
That’s how easily you can set up a Hetzner server in xCloud Host.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
After creating your server with Hetzner, you would want to create your first site with xCloud. Follow [**this documentation**](/docs/how-to-create-a-site-with-xcloud/) to learn how to do that. You can also take a look at how to add [**xCloud managed email service**](https://xcloud.host/docs/add-xcloud-managed-email-service/) for WordPress site emails.
---
# How to Set Up Hostinger Server with xCloud? - xCloud
> Learn how to quickly set up Hostinger server with xCloud and start building websites in just a few clicks.
xCloud allows you to integrate your own [**Hostinger server**](https://www.hostinger.com/vps-hosting) easily and manage it with our advanced control panel. With our [**self manged hosting**](/self-managed-hosting/) service, you can easily integrate your servers in just a few clicks.
Follow the steps to set up Hostinger server with xCloud easily:
> 💡**Important:** Hostinger does not allow purchase through credit cards via their API. So, to create Hostinger servers with our new integration, you must confirm that you have a different payment method and not a credit card. Currently, supported payment methods include **Apple Pay**, **Google Pay**, and **PayPal**. We will support credit cards if Hostinger allows it in the future.
## **Step 1: Sign Up/Login with xCloud** [#](/docs/set-up-hostinger-server-with-xcloud/)
First, you will need to visit the xCloud website, and you have to sign up or log in to xCloud with your credentials.
## **Step 2: Create Your Hostinger VPS Server in xCloud** [#](/docs/set-up-hostinger-server-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the ‘Add New Server’ button from your dashboard.
The next screen will provide the list of our available server providers. Select the **‘Hostinger’** option from the list. The billing of the server will be handled on your Hostinger account.
Now, before going to the next step, you need to create an API token to connect your Hostinger account to xCloud Host. To do that, log in to your Hostinger account and create an API key. Copy the API key to set up a Hostinger VPS server in xCloud.
## **Step 3: Connect Account & Add Necessary Information** [#](/docs/set-up-hostinger-server-with-xcloud/)
Now, go back to xCloud dashboard to create a new server with Hostinger. Select your existing server or create a new account. Then, set an API label as you prefer. The label can be anything to help you track or remember a particular one from multiple tokens. After that, paste the API token that you have copied from Hostinger into the token field.
You will be taken to the server creation page after successfully integrating your Hostinger account. Now you need to provide the **‘Server name’**, your preferred **‘Server Size’**, and the **‘Region’** nearest to you and your visitors and select the ‘Database’
Then choose the **‘Ubuntu’** Version of the server, add **‘Tags’,** choose a web server and hit the **‘Next’** button
Once the processing is done, the server will be created. And you can build sites and manage them right from the dashboard.
We are almost done with our server creation of Hostinger in xCloud. After submitting the form this might take up to 10-15 minutes to make the Hostinger server live and ready to install a lightning-fast websites.
That’s how easily you can set up a Hostinger VPS server in xCloud Host.
After creating your server with Hostinger, you would want to create your first site with xCloud. Follow this [**documentation**](/docs/how-to-create-a-site-with-xcloud/) to learn how to do that. You can also take a look at how to add [**xCloud managed email service**](https://xcloud.host/docs/add-xcloud-managed-email-service/) for site emails.
Still stuck? Contact our [**support team**](https://support.xcloud.host/) for any of your queries.
---
# How to Set Up Laravel Horizon with xCloud - xCloud
> Learn how to install and set up Laravel Horizon on xCloud to monitor Laravel queues. Quick, clear setup instructions included.
**[Laravel Horizon](https://laravel.com/docs/11.x/horizon)** is a powerful dashboard and configuration tool for Laravel queues, providing deep insight into your job processing. If you are using xCloud to deploy your **[Laravel application](/laravel-hosting/)**, setting up Horizon is simple. Follow the step-by-step process to set up Laravel Horizon with xCloud.
## **Step 1: Go to the Laravel Site** [#](/docs/set-up-laravel-horizon/)
First, go to your site and navigate to the **‘Laravel’** section in the dashboard. Select your **‘Application’** from the list of deployed Laravel applications.
## **Step 2: Install The Laravel Horizon** [#](/docs/set-up-laravel-horizon/)
Now install Laravel Horizon locally by running the following commands and commit the changes to git:
```
composer require laravel/horizon
```
Copy to Clipboard
```
php artisan horizon:install
```
Copy to Clipboard
Now, if you go back to the xCloud dashboard, you will see that the Horizon is installing. After the installation process is completed, you will see that the Laravel Horizon set up proper.
Once the command is processed, Laravel Horizon will be installed. You can go back to the Laravel dashboard, where you will see the notice that Laravel Horizon is installed. And if you go to the Horizon dashboard, you will be able to see the stats of your Laravel Application
### **Add Queue Restart to Deployment Script** [#](/docs/set-up-laravel-horizon/)
To ensure that your queue workers are properly restarted after each deployment, add the following command to the **Deployment Script** field in your application settings:
```
$XCLOUD_PHP artisan horizon:terminate
```
Copy to Clipboard
This will restart the Horizon process gracefully after finishing the running tasks.
Read this [**official Laravel documentation**](https://laravel.com/docs/11.x/queues#queue-workers-and-deployment) for more best practices on queue worker deployment.
That is it! You have successfully set up Laravel Horizon with xCloud. With Horizon, now you can monitor your queues efficiently and gain better insight into your application’s background job processing.
Still stuck? Contact our [dedicated support team](https://support.xcloud.host/) for any of your queries.
---
# How to Set Up Laravel on Vultr Server with xCloud? - xCloud
> Learn how to Set Up Laravel on Vultr using a cloud management platform to easily deploy, configure, and manage your Vultr applications.
**[Laravel](/laravel-hosting/)** is a popular PHP framework for building modern web applications. With Vultr’s cloud hosting and xCloud’s one‑click deployment, you can set up Laravel quickly and manage it with ease. This guide walks you through the process step by step.
If you already have a Vultr server, you can skip the first phase and proceed directly to the second. First, set up your Vultr server in xCloud. Follow these steps to get started.
## **How to Set Up a Vultr Server in xCloud?** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
This guide shows how to set up a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Create Your New Vultr Server in xCloud** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available services. For this tutorial, we will create a Vultr server and for that select the Vultr option under **“Bring your own server service”.** The billing of the server will be handled on your Vultr account and in xCloud we won’t charge for this first server.
### **Signup in Vultr with xCloud Promo** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
To get started with the free hosting offer, head over to [**Vultr.com**](https://www.vultr.com/) and sign up for a new account. During the registration process, you’ll need to link a valid credit card or a verified PayPal account to activate your account and be eligible for the $100 promotional credit. As part of the validation, Vultr will place a small temporary authorization on your credit card, approximately $2.50 USD to verify your payment method.
This charge is not permanent and will be automatically reversed by your bank, although depending on your bank’s policy, it might take up to 30 days for the funds to be released.
If you choose to verify using PayPal, note that Vultr requires a minimum payment of $5.00 USD for validation. Additionally, PayPal must be linked to a valid credit card or bank account to complete this verification process. Once your payment method is verified and your account is deemed eligible, the $100 in free credits will be automatically applied to your account. Make sure to use the promo code **“XCLOUD25”** during the sign-up to claim this offer.
**_Note:_** _If you already have a Vultr account then please skip this step and check how to collect API from Vultr._
### **Collect API key from Vultr** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
After you have successfully completed setting up your billing method, you will need to get the Vultr API key to add it to xCloud to create and manage 1 server and 10 sites for free. Navigate to the Account → API tab from your Vultr dashboard. After that click on the **‘Enable API’** button.
Now, your **‘Personal Access Token’** will be auto-generated. Copy the API Key/Token.
Please make sure you have added Any **IPv4** and Any **IPv6** both under Access Control.
Now, you need to go back to the xCloud dashboard and add your Vultr Label & API Key.
### **Add Team Members In Vultr** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
If you want your team members to use xCloud with Vultr, then make sure these permissions are given.
### **Add Vultr API key in xCloud** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Thanks to xCloud, you can create your first server without spending any money. Now, click on **‘Add New Server’** from the xCloud dashboard and you will be redirected to the server selection screen. Then click on **‘Vultr’** to proceed further.
After selecting **‘Vultr’**, set your **‘Key’**, **‘Vultr Label’**, and ‘**Vultr API Key’**. Then click on **‘Verify’**.
### **Step 3: Create a Vultr Server in xCloud** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Now that you have successfully verified your Vultr account, you will need to add other details to create a server in Vultr using xCloud. Choose your Region, Database Server, Server Size, and much more from one easy dashboard.
## **How to Deploy Laravel Applications on Vultr with xCloud?** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Deploying [**Laravel applications**](/laravel-hosting/) can often involve multiple steps and intricate configurations. xCloud simplifies this process by providing a streamlined platform tailored for deploying modern PHP applications, including Laravel, with minimal complexity.
Follow this step-by-step guide to configure and deploy your fully functional Laravel website with ease.
### **Step 1: Choose Your Server** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘Add New Site’** button.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **Vultr server** you set up in xCloud from this dropdown.
### **Step 2: Go to The Laravel Tab** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Then navigate to the ‘**Laravel’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
### **Step 3: Set Up Domains** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch or you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the **‘Migrate into a New Domain’** option.Then you have to put **‘New Site Title’** and **‘Domain Name’**. Here we are choosing the **‘Demo Site’** domain. Then click on **‘Next’**.
### **Step 4: Settings To Manage Database** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Now, you will be sent to the ‘Settings’ step. Make sure to correctly add your ‘PHP Version’, ‘Site User’, ‘Web root’.
Now, it is time for database management. You will get three options. You can either create a new database on the server, you can add your existing database that is hosted on another server.
You can also proceed without any database. For this tutorial, we are going with the ‘Create Database In Server’ option.
If you select this option, enter your **‘Database Name’**, **‘Database Username’** and **‘Database Password’**. You can keep these auto-generated credentials or you can modify them according to your choice.
After selecting any one option and providing all essential information and credentials, click on **‘Next’**.
### **Step 5: Insert Git Repository Credentials** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
In the ‘Git Repo’ tab, add your ‘Git Repository’ and ‘Git Branch’. Also, toggle on the ‘Enable push to deploy’ option. Once you enable the ‘Push To Deploy’, it will generate a ‘Deployment URL’. We can use this URL to CICD pipeline and copy the ‘Deployment URL’ from here.
### **Step 6: Add the Deployment URL to the Git Repository** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Now, go to your Git repository. From the **‘Code’** tab, go to the **‘Settings’** tab and click on the **‘Webhooks’** page from the **‘Code and Automation’** section of the left navigation. Insert the deployment URL into the ‘Payload URL’ field. Select ‘application/json’ from the **‘Content type’** dropdown.
Note: This step is optional. Adding a webhook enables automatic deployments when you push changes to the repository but it’s not required if you prefer to deploy manually.
### **Step 7: Add Public Key to Git Repository** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Next in the **‘Deploy Script’** field any script that needs to be executed after the site is deployed. For example, you can use it to install dependencies or run database migrations.
Next, in the **‘Deploy Script’** field, specify any commands that need to be executed after the site is deployed.
If your project uses PHP, you can specify the version _(e.g., php8.1)_ and run Composer along with Laravel-specific commands like this:
**php8.1 $(which composer) install –no-interaction –prefer-dist –optimize-autoloader –no-dev**
**php8.1 artisan migrate –force**
**php8.1 artisan optimize:clear**
If your project also involves Node.js, you can include additional commands as well. These scripts ensure that your backend and frontend are fully prepared after deployment.
From the xCloud dashboard, copy the ‘Public Key’ to add it to your Git repository as a deploy key. Git migration uses the ‘Public Key’ for SSH authentication. This is necessary to enable xCloud to access your Git repository and clone it. It ensures secure and authorized access for the cloning process.
Now, again, go to your Git Repository. From the ‘Code’ tab, go to the ‘Settings’ tab and click on ‘Deploy Keys’ in the security section of the left navigation. Click on the ‘Add key’ button and paste the key that you copied from xCloud.
After inserting the deploy key in GitHub, click on ‘Next’ on your xCloud settings of the ‘Git Repo’ tab.
### **Step 8: Confirm Migrating The Website** [#](/docs/set-up-laravel-on-vultr-server-with-xcloud/)
Now, to start the migration process, click on the **‘Start’** button. After clicking the migration process will start and you will see the progress of migration.
Once the migration is successfully complete will see the following screen. You go to the site dashboard from there. Go to the **‘Laravel’** Option from the menu and customize the **‘Application’** and **‘Environment’** as your preferences.
**Check out the other features of Laravel:**
- [_How to Use Supervisor for Process Management With xCloud_](/docs/supervisor-for-process-management/)
- [_How to Set Up Laravel Horizon with xCloud_](/docs/set-up-laravel-horizon/)
- [_How to Set Up a Queue Worker for Laravel Applications_](/docs/set-up-queue-worker-for-laravel-applications/)
Configure Laravel Scheduler with cron job for your Laravel projects with ease. Check out this documentation for more details: [How To Configure xCloud Cron Job?](/docs/how-to-configure-xcloud-cron-job/)
And that’s it. This is how easily you can successfully deploy your Laravel application on xCloud. Now you can go to your site dashboard from xCloud and customize according to your preferences.
If you are still stuck, feel free to contact our [**support team**](/support/).
---
# How to Set Up Lovable on DigitalOcean with xCloud? - xCloud
> Learn how to Set Up Lovable on DigitalOcean using a cloud management platform to easily deploy, configure, and manage your Lovable applications.
Deploy [**Lovable**](/lovable-hosting/) on DigitalOcean with xCloud quickly and easily. This guide walks you through the basic steps to configure and launch Lovable on a DigitalOcean server, helping you streamline deployment and manage your application with minimal effort
## **How to Setup A DigitalOcean Server in xCloud?** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
This guide shows how to set up a DigitalOcean server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Create Your New Digital Ocean Server In xCloud** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a Digital Ocean server and for that select the [**Digital**](https://try.digitalocean.com/)[**Ocean**](https://xcloud.host/go/digitalocean/) option. The billing of the server will be handled on your Digital Ocean account.
**Note:** Don’t have a DigitalOcean account? Check out the documentation below to find out how to provision a server with any providers:
- [**How To Setup First Server With Vultr?**](/docs/how-to-get-free-hosting-with-vultr/)
- [**How To Setup Your First Server With Google Cloud Platform Provider?**](https://dev1.xcloud.host/docs/first-server-with-google-cloud-platform)
- [**How To Setup a Server With Other Providers?**](https://dev1.xcloud.host/?post_type=docs&p=268&preview=true)
We’ve made it easier and safer for you to connect xCloud with your DigitalOcean account. You no longer have to go through the hassle of generating and copying access tokens.
Now, xCloud will guide you through an OAuth flow, where you simply authorize xCloud to use your DigitalOcean account.
All you have to do is provision a new DigitalOcean server, click **“Authorize”** during the setup, and you’ll be redirected to DigitalOcean to grant permission to your account. It’s a straightforward and hassle-free process to set up your server with Digital Ocean.
### **Step 2: Add Necessary Information** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
You will be taken to the server creation page after successfully integrating your DO account. Now you need to provide the Server name, your preferred Server Size (**CPU, RAM, Storage**) and Region nearest to you and your visitors. Only, **MySQL 8.0** database server is now available.
By default Database, the **‘Root’** Password is auto-filed but you can change this and save it in a safe place.
We recommend at least a **2GB/ 1 shared CPU server** for 10-20 sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server.
We are almost done with our server creation of Digital Ocean in xCloud. After submitting the form this might take **up to 12-15 minutes** to make the Digital Ocean server live and ready to install a lightning fast WordPress Site.
## **How to Deploy Lovable Applications with xCloud?** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
Lovable is a modern AI-powered application-building platform designed to help anyone create user-friendly, scalable, and production-ready applications and websites through chatting.
xCloud allows you to deploy Lovable applications easily from your Git repositories. You can install and set up Lovable and get your application live in just a few clicks. Follow the steps below to set up Lovable with xCloud and deploy **AI powered projects easily:**
### **Step 1: Create a New Site** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
### **Step 2: Choose Your Server** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Lovable applications.
### **Step 3: Go to The Lovable Tab** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
From here, go to the **‘Lovable’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
📝 Before you proceed, make sure your Lovable projects are properly synced with Git repositories.
### **Step 4: Set Up Domains** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the **‘Migrate into a New Domain’** option.
### **Step 5: Configure Site Settings** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
Next, under the **‘Settings’** tab, you will get the **‘Node.js Version’** and **‘Site User’** for this application. After that, click on the **‘Next’** button.
### **Step 6: Insert Git Repository Credentials** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
In the **‘Git Repo’** tab, you will get three repository options: **‘Private Repository (Manual SSH URL)’**, **‘Public Repository (Manual HTTPS URL)’** and ‘**Connected Git Provider’**.
We are going to deploy Git projects using the **‘Git Provider’** option here. Choose the **‘Connected Git Provider’** option from the dropdown menu.
From the **‘Select Git Provider’** dropdown, choose the connected account you want to use. Once selected, navigate through the list of repositories, pick the one you want to deploy and then select the specific **‘Branch’** of that project.
You can also deploy Lovable projects from your Public or Private Git repositories as well. For more details read this documentation:
**👉** [**How to Insert Your Git Repositories with xCloud**](/docs/how-to-integrate-a-git-provider-with-xcloud/)
### **Step 7: Enable Push to Deploy** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
The next step is to enable automated deployment. Toggle on the **‘Enable push to deploy’** option. You need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
**Note:** If you want to learn more about the process, follow the steps in this [**document**](/docs/deploy-custom-php-applications-with-xcloud/)**.**
Finally, review all the details and click on the **‘Start’** button to create the Lovable application.
### **Step 8: Visit the Application** [#](/docs/set-up-lovable-on-digitalocean-with-xcloud/)
After completing the setup, you will be able to visit your Lovable site. From the dashboard, click on the **‘Visit Site’** app.
That’s it! This is how easily you can deploy Lovable with xCloud and launch your web apps in just a few clicks.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up Lovable on Vultr with xCloud? - xCloud
> Learn how to set up Lovable on Vultr using xCloud. Follow a clear step-by-step guide to deploy and manage AI-powered applications with ease.
[**Lovable**](/lovable-hosting/) is a modern AI-powered application-building platform designed to help anyone create user-friendly, scalable, and production-ready applications and websites through chatting.
Set up **[Lovable](/lovable-hosting/)** on Vultr with xCloud quickly and easily. This guide walks you through the basic steps to configure and launch Lovable on a Vultr server, helping you streamline deployment and manage your application with minimal effort
## **How to Set up A Vultr Server in xCloud?** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
This guide shows how to set up a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey:
### **Step 1: Create Your New Vultr Server In xCloud** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available services. For this tutorial, we will create a Vultr server and for that select the Vultr option under **“Bring your own server service”.** The billing of the server will be handled on your Vultr account and in xCloud we won’t charge for this first server.
### **Collect API key from Vultr** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
After you have successfully completed setting up your billing method, you will need to get the Vultr API key to add it to xCloud to create and manage 1 server and 10 sites for free. Navigate to the Account → API tab from your Vultr dashboard. After that click on the **‘Enable API’** button.
Now, your **‘Personal Access Token’** will be auto-generated. Copy the API Key/Token.
Please make sure you have added Any **IPv4** and Any **IPv6** both under Access Control.
Now, you need to go back to the xCloud dashboard and add your Vultr Label & API Key.
### **Add Team Members in Vultr** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
If you want your team members to use xCloud with Vultr, then make sure these permissions are given.
### **Add Vultr API Key in xCloud** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
Thanks to xCloud, you can create your first server without spending any money. Now, click on **‘Add New Server’** from the xCloud dashboard and you will be redirected to the server selection screen. Then click on **‘Vultr’** to proceed further.
After selecting **‘Vultr’**, set your **‘Key’**, **‘Vultr Label’**, and ‘**Vultr API Key’**. Then click on **‘Verify’**.
### **Step 3: Create a Vultr Server in xCloud** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
Now that you have successfully verified your Vultr account, you will need to add other details to create a server in Vultr using xCloud. Choose your Region, Database Server, Server Size, and much more from one easy dashboard.
After putting all the information, click on **‘Next’** and xCloud will automatically install and set up everything for you in a few minutes.
## **How to Deploy Lovable Applications with xCloud?** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
xCloud allows you to deploy Lovable applications easily from your Git repositories. You can install and set up Lovable and get your application live in just a few clicks. Follow the steps below to set up Lovable with xCloud and deploy **AI powered projects easily:**
### **Step 1: Create a New Site** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘New Site’** button.
### **Step 2: Choose Your Server** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
Then choose your server from the dropdown menu. Next, click on the **‘Next’** button to proceed to start creating Lovable applications.
### **Step 3: Go to the Lovable Tab** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
From here, go to the **‘Lovable’** tab to deploy your Laravel applications. Now, choose **‘Clone A Git Repository’** to import your custom PHP site.
Before you proceed, make sure your Lovable projects are properly synced with Git repositories.
### **Step 4: Set Up Domains** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
From the **‘Domains’** tab, you will get two options: either you can create a **‘Demo Site’** with a test domain and refine it until it is ready for launch, or, you can migrate into a new domain to get your site up and running in a new domain.
Or you can create your site with your live domain; you need to select the **‘Migrate into a New Domain’** option.
### **Step 5: Configure Site Settings** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
Next, under the **‘Settings’** tab, you will get the **‘Node.js Version’** and **‘Site User’** for this application. After that, click on the **‘Next’** button.
### **Step 6: Insert Git Repository Credentials** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
In the **‘Git Repo’** tab, you will get three repository options: **‘Private Repository (Manual SSH URL)’**, **‘Public Repository (Manual HTTPS URL)’** and ‘**Connected Git Provider’**.
We are going to deploy Git projects using the **‘Git Provider’** option here. Choose the **‘Connected Git Provider’** option from the dropdown menu.
From the **‘Select Git Provider’** dropdown, choose the connected account you want to use. Once selected, navigate through the list of repositories, pick the one you want to deploy and then select the specific **‘Branch’** of that project.
You can also deploy Lovable projects from your Public or Private Git repositories as well. For more details read this documentation:
**👉** [**How to Insert Your Git Repositories with xCloud**](/docs/how-to-integrate-a-git-provider-with-xcloud/)
### **Step 7: Enable Push to Deploy** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
The next step is to enable automated deployment. Toggle on the **‘Enable push to deploy’** option. You need to insert this URL into GitHub. Copy the **‘Deployment URL’** from here.
**Note:** If you want to learn more about the process, follow the steps in this [**document**](/docs/deploy-custom-php-applications-with-xcloud/)**.**
Finally, review all the details and click on the **‘Start’** button to create the Lovable application.
### **Step 8: Visit the Application** [#](/docs/set-up-lovable-on-vultr-with-xcloud/)
After completing the setup, you will be able to visit your Lovable site. From the dashboard, click on the **‘Visit Site’** app.
That’s it! This is how easily you can deploy Lovable with xCloud and launch your web apps in just a few clicks.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up n8n on Linode with xCloud? - xCloud
> Learn how to Set Up n8n on Linode using a cloud management platform to easily deploy, configure, and manage your n8n applications.
Setting up [**n8n**](/n8n-hosting/) on Linode with xCloud is a straightforward way to bring automation to the cloud. This guide walks you through the essential steps to configure, deploy, and run n8n seamlessly on Linode, so you can start building powerful workflows without the usual complexity.
## **How to Integrate And Setup Linode Server with xCloud?** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
This guide shows how to set up the Linode server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Sign Up/Login With xCloud** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
First, you will need to visit the [**xCloud**](http://hidden-hamlet-226309.wp1.sh/) website and you have to sign up for xCloud with your credentials.
If you already have an account please visit our [**login page**](https://app.xcloud.host/login).
Now you are ready to set up your server with Digital Ocean in xCloud.
### **Step 2: Create Your Linode Server in xCloud** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a Linode server and for that select the [**Linode**](https://www.linode.com/) option.
### **Step 2: Authorize Your Linode Account** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
We have made it easier and safer for you to connect xCloud with your Linode account. Now provision a new Linode server, click **‘Authorize on Linode’** during the setup, and you will be redirected to Linode to grant permission to your account. It is a straightforward and hassle-free process to set up your server with Linode.
### **Step 3: Connect the Account & Add the Necessary Information** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
You will be taken to the server creation page after successfully integrating your Linode account and your server will be connected with xCloud. Now you need to provide the **‘Server name’**, your preferred **‘Server Size’** (CPU, RAM, storage), the **‘Region’** nearest to you and your visitors, and then select the **‘Database Server’** from MySQL and MariaDB.
**_Note:_** _We recommend at least a 2GB/ 1 shared CPU server for 10-20 brochure sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server._
Next, choose the web server stack from **‘NGINX’** or **‘OpenLiteSeed’** as your requirements and click on the **‘Next’** button to proceed with the server creation process.
It will start creating a Linode server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many sites as you want under this server.
## **Deploy n8n on Vultr Server via xCloud** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
With xCloud’s One Click Apps feature, you can deploy n8n with ease. Follow the steps below to quickly set up n8n in a demo or production environment with xCloud.
### **🔖Recommendations** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
Here are some key suggestions to help you optimize your setup and get the best results 👉🏻
#### **🌐Web Server for Deployment** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
Though you can deploy n8n applications from both NGINX and OLS server, we recommend deploying n8n on an Nginx server for the best performance and stability. While you can use an OLS server, Nginx generally provides a more reliable experience.
#### **⚙️ CPU Requirements** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
We recommend using a server with more than 1 CPU when running n8n. A 1 CPU server may not function as expected, so choosing a server with higher resources will help ensure smooth and successful operation.
**_Note:_** _n8n is available in our plans, including the free plan. But you have to upgrade to our PRO plans to access the Environment feature._
This guide shows how to set up or deploy n8n on a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Access One Click Apps** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘Add New Site’** button.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **Vultr server** you set up in xCloud from this dropdown. Then click **‘Next’.**
Then go to the **‘One Click Apps’** section. Select **‘n8n’** from the available applications to initiate the deployment process.
### **Step 2: Set Up the n8n Application** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
### **Step 3: Configure Domain Settings** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your n8n application.
**_Note:_** _Once a demo site is promoted to a live environment, you cannot revert back to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding._
### **Step 4: Configure and Install the Site** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
Then, a default **‘Port’**, **‘Site User’** will be selected automatically. Then choose a **‘Timezone’** for this site. Once all settings have been configured, click the **‘Next’** button to proceed.
**_Note:_** _We recommend leaving the port and site user as default._
### [#](/docs/set-up-n8n-on-linode-with-xcloud/)
### **Step 6: Add Your Custom Domain** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
You can add your own **‘Domain’** to host the site by going to the Domain section. Also, you can add an **‘Additional Domain’** with your custom domain.
### **Step 7: Visit the n8n Site** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
With n8n set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** app.
This will open the n8n dialog window for registration, which should look something like the example below. Simply enter your details and create a password according to the specs indicated. Hit the **‘Next’** button, then click through any additional popups, leaving them empty for now.
This should bring you to the n8n Overview page. Now that your n8n instance is up and running, let’s fine-tune its settings for security and customization. From here, go to the **‘Create workflow’** , set according to your preferences.
## [#](/docs/set-up-n8n-on-linode-with-xcloud/)
### **Environment Editor for n8n** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your n8n instance. Just go to the **‘Environment’** option from the sidebar and adjust as you need then click on the **‘Save’** button.
### **Update N8N Version** [#](/docs/set-up-n8n-on-linode-with-xcloud/)
To update n8n to the latest version, simply go to **‘Updates’** from the sidebar of the dashboard. Then simply search for the **‘Check for Updates’** button. Click the Update button and this will install the latest **n8n** version on your server.
And that’s it, this is how easily you can quickly and efficiently deploy an n8n on a Vultr server instance using xCloud’s **One Click Apps** feature. You can create your own n8n application and automate with workflows seamlessly.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up n8n on Vultr with xCloud? - xCloud
> Learn how to Set Up n8n on Vultr using a cloud management platform to easily deploy, configure, and manage your n8n applications.
[**n8n**](/n8n-hosting/) is a powerful open-source workflow automation tool that helps teams connect services and automate tasks with minimal code. By combining Vultr’s cloud infrastructure with xCloud’s intuitive server management, you can deploy n8n quickly and efficiently.
This guide walks you through setting up a Vultr server in xCloud and deploying n8n using xCloud’s One Click Apps.
## **How to Setup A Vultr Server in xCloud?** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
This guide shows how to set up a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Sign Up/Login With xCloud** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
First, you will need to visit the [**xCloud**](http://hidden-hamlet-226309.wp1.sh/) website and you have to sign up for xCloud with your credentials.
If you already have an account please visit our [**login page**](https://app.xcloud.host/login).
Now you are ready to set up your server with Digital Ocean in xCloud.
### **Step 2: Create Your New Vultr Server In xCloud** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available services. For this tutorial, we will create a Vultr server and for that select the Vultr option under **“Bring your own server service”.** The billing of the server will be handled on your Vultr account and in xCloud we won’t charge for this first server.
### **Signup in Vultr with xCloud Promo** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
To get started with the free hosting offer, head over to [**Vultr.com**](https://www.vultr.com/) and sign up for a new account. During the registration process, you’ll need to link a valid credit card or a verified PayPal account to activate your account and be eligible for the $100 promotional credit. As part of the validation, Vultr will place a small temporary authorization on your credit card, approximately $2.50 USD to verify your payment method.
This charge is not permanent and will be automatically reversed by your bank, although depending on your bank’s policy, it might take up to 30 days for the funds to be released.
If you choose to verify using PayPal, note that Vultr requires a minimum payment of $5.00 USD for validation. Additionally, PayPal must be linked to a valid credit card or bank account to complete this verification process. Once your payment method is verified and your account is deemed eligible, the $100 in free credits will be automatically applied to your account. Make sure to use the promo code **“XCLOUD25”** during the sign-up to claim this offer.
**_Note:_** _If you already have a Vultr account then please skip this step and check how to collect API from Vultr._
### **Collect API key from Vultr** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
After you have successfully completed setting up your billing method, you will need to get the Vultr API key to add it to xCloud to create and manage 1 server and 10 sites for free. Navigate to the Account → API tab from your Vultr dashboard. After that click on the **‘Enable API’** button.
Now, your **‘Personal Access Token’** will be auto-generated. Copy the API Key/Token.
Please make sure you have added Any **IPv4** and Any **IPv6** both under Access Control.
Now, you need to go back to the xCloud dashboard and add your Vultr Label & API Key.
### **Add Team Members In Vultr** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
If you want your team members to use xCloud with Vultr, then make sure these permissions are given.
### **Add Vultr API key in xCloud** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
Thanks to xCloud, you can create your first server without spending any money. Now, click on **‘Add New Server’** from the xCloud dashboard and you will be redirected to the server selection screen. Then click on **‘Vultr’** to proceed further.
After selecting **‘Vultr’**, set your **‘Key’**, **‘Vultr Label’**, and ‘**Vultr API Key’**. Then click on **‘Verify’**.
### **Step 3: Create a Vultr Server in xCloud** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
Now that you have successfully verified your Vultr account, you will need to add other details to create a server in Vultr using xCloud. Choose your Region, Database Server, Server Size, and much more from one easy dashboard.
After putting all the information, click on **‘Next’** and xCloud will automatically install and set up everything for you in a few minutes.
## **Deploy n8n on Vultr Server via xCloud** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
With xCloud’s One Click Apps feature, you can deploy n8n with ease. Follow the steps below to quickly set up n8n in a demo or production environment with xCloud.
### **🔖Recommendations** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
Here are some key suggestions to help you optimize your setup and get the best results 👉🏻
#### **🌐Web Server for Deployment** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
Though you can deploy n8n applications from both NGINX and OLS server, we recommend deploying n8n on an Nginx server for the best performance and stability. While you can use an OLS server, Nginx generally provides a more reliable experience.
#### **⚙️ CPU Requirements** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
We recommend using a server with more than 1 CPU when running n8n. A 1 CPU server may not function as expected, so choosing a server with higher resources will help ensure smooth and successful operation.
**_Note:_** _n8n is available in our plans, including the free plan. But you have to upgrade to our PRO plans to access the Environment feature._
This guide shows how to set up or deploy n8n on a Vultr server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Access One Click Apps** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
Begin by logging into your xCloud account. Once logged in, navigate to your dashboard and click on the **‘Add New Site’** button.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **Vultr server** you set up in xCloud from this dropdown. Then click **‘Next’.**
Then go to the **‘One Click Apps’** section. Select **‘n8n’** from the available applications to initiate the deployment process.
### **Step 2: Set Up the n8n Application** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
In the site setup screen, you will be prompted to enter basic site information. Provide a **‘Site Title’** and add relevant **‘Tags’** to help organize your deployment.
At this point, you can choose between two deployment modes: **‘Go Live’** for a production-ready deployment or **‘Demo Site’** for testing purposes. Selecting **‘Go Live’** will immediately create a live environment, while choosing **‘Demo Site’** allows you to experiment in a staging environment before promoting to production.
### **Step 3: Configure Domain Settings** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
If you select the **‘Demo Site’** option, xCloud will assign a temporary subdomain for your n8n application.
**_Note:_** _Once a demo site is promoted to a live environment, you cannot revert back to using the demo domain. Ensure your choice aligns with your deployment goals before proceeding._
### **Step 4: Configure and Install the Site** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
Then, a default **‘Port’**, **‘Site User’** will be selected automatically. Then choose a **‘Timezone’** for this site. Once all settings have been configured, click the **‘Next’** button to proceed.
**_Note:_** _We recommend leaving the port and site user as default._
### [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
### **Step 6: Add Your Custom Domain** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
You can add your own **‘Domain’** to host the site by going to the Domain section. Also, you can add an **‘Additional Domain’** with your custom domain.
### **Step 7: Visit the n8n Site** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
With n8n set up with xCloud, you should be able to log in and confirm that it’s working. From the dashboard, click on the **‘Visit Site’** app.
This will open the n8n dialog window for registration, which should look something like the example below. Simply enter your details and create a password according to the specs indicated. Hit the **‘Next’** button, then click through any additional popups, leaving them empty for now.
This should bring you to the n8n Overview page. Now that your n8n instance is up and running, let’s fine-tune its settings for security and customization. From here, go to the **‘Create workflow’** , set according to your preferences.
## [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
### **Environment Editor for n8n** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your n8n instance. Just go to the **‘Environment’** option from the sidebar and adjust as you need then click on the **‘Save’** button.
### **Update N8N Version** [#](/docs/set-up-n8n-on-vultr-with-xcloud/)
To update n8n to the latest version, simply go to **‘Updates’** from the sidebar of the dashboard. Then simply search for the **‘Check for Updates’** button. Click the Update button and this will install the latest **n8n** version on your server.
And that’s it, this is how easily you can quickly and efficiently deploy an n8n on a Vultr server instance using xCloud’s **One Click Apps** feature. You can create your own n8n application and automate with workflows seamlessly.
Still stuck? Contact our [**support team**](/support/) for any of your queries.
---
# How to Set Up Node.js on AWS with xCloud? - xCloud
> Learn how to Set Up Node.js on AWS using a cloud management platform to easily deploy, configure, and manage your Node.js applications.
Node.js is a powerful runtime that enables fast, scalable and modern web applications.
With xCloud, you can easily setup Node.js on the AWS server in xCloud.
xCloud makes hosting and managing Node.js sites easy, so you can focus on building great websites.This guide will show you how to set up Node.js on AWS using xCloud.
## **How to Setup AWS Server with xCloud?** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
This guide shows how to set up the AWS server in xCloud. Follow the steps to quickly launch, configure and start your cloud journey.
### **Step 1: Sign Up/Login With xCloud** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
First, you will need to visit the [**xCloud**](http://hidden-hamlet-226309.wp1.sh/) website and you have to sign up for xCloud with your credentials.
If you already have an account please visit our [**login page**](https://app.xcloud.host/login).
Now you are ready to set up your server with Digital Ocean in xCloud.
### **Step 2: Create Your AWS Server in xCloud** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
After logging in to your xCloud account, start by adding a new server by clicking on the **“Add New Server”** button from your dashboard.
The next screen will provide the list of our available server providers. For tutorial purposes, we will create a AWS server and for that select the [**AWS**](https://www.linode.com/) option.
### **Step 3: Sign In to the AWS Management Console** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
Now, before going to the next step, you need to log in to the AWS management console. Sign in as a **‘Root User’** to the [**AWS Management Console**](https://aws.amazon.com/console/) using your AWS account credentials. Once logged in, navigate to the main dashboard where you can access various AWS services.
### **Step 4: Navigate to the IAM Console** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
From the AWS Management Console, click on the Services menu located at the top left corner or search with **“IAM”** and select IAM from the list of services. This will direct you to the IAM dashboard, where you can manage users, groups, roles, and policies.
### **Step 5: Add a New User** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
On the IAM dashboard, locate and click on the Users option in the left navigation panel. This will display a list of existing IAM users. To create a new user, click on the **‘Create User’** button.
### **Step 6: Configure User Details** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
In this step, enter a unique **‘Username’** for the new **IAM** user. Next, choose the type of access the user requires. Check-in **‘AWS Management Console’** access option if the user requires access to the AWS Management Console and click on the **‘Next’** button.
### **Step 7: Set Permissions for Amazon EC2 Instance** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
You have three options to set permissions for the new user. The first one is **‘Add user to group’** which lets you add the user to an IAM group with predefined permissions, which is efficient for managing multiple users with similar access needs. The second one is **‘Copy permissions’** which enables you to duplicate the permissions of another IAM user. And the final policy **‘Attach policies directly’** allows you to assign AWS-managed policies or custom policies.
Here we are choosing the ‘Attach policies directly’ and assigning the access for [**Amazon EC2 Instance**](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to the user and hit on the Next.
**_Note:_** _If you do not find the EC2 Access here, search for the policy in the search bar._
### **Step 8: Add Tags, Review and Create** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
You can add **‘Tags’** to help organize and manage users. Now carefully review all the details and permissions assigned to the new IAM user. If everything is accurate and complete, click the **‘Create user’** button to finalize the creation of the IAM user.
### **Step 9: Give Another permission for Amazon Lightsail** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
Now, set another permission for the new user for [**Amazon LightSail**](https://docs.aws.amazon.com/decision-guides/latest/lightsail-or-ec2/lightsail-or-ec2.html) easily. To specify the permissions for the created user, go to the Permission Policies and click on the **‘Add Permissions Menu’**. Choose the **‘Create Inline Policy’** option from the dropdown menu.
Click on the **‘JSON’** button from the Policy Editor and paste the below given JSON code in the editor. Finally, tap on the **‘Next’** button.
**Here is the JSON code:**
**{**
**“Version”****:** **“2012-10-17”****,**
**“Statement”****:** **\[**
**{**
**“Sid”****:** **“VisualEditor0”****,**
**“Effect”****:** **“Allow”****,**
**“Action”****:** **\[**
**“lightsail:GetInstances”****,**
**“lightsail:GetKeyPair”****,**
**“lightsail:DeleteKeyPair”****,**
**“lightsail:GetStaticIp”****,**
**“lightsail:ReleaseStaticIp”****,**
**“lightsail:SetIpAddressType”****,**
**“lightsail:CreateInstances”****,**
**“lightsail:GetInstance”****,**
**“lightsail:GetInstanceAccessDetails”****,**
**“lightsail:DeleteInstance”****,**
**“lightsail:CreateKeyPair”****,**
**“lightsail:ImportKeyPair”****,**
**“lightsail:StartInstance”****,**
**“lightsail:DownloadDefaultKeyPair”****,**
**“lightsail:GetInstancePortStates”****,**
**“lightsail:StopInstance”****,**
**“lightsail:AttachStaticIp”****,**
**“lightsail:GetRegions”****,**
**“lightsail:RebootInstance”****,**
**“lightsail:GetOperation”****,**
**“lightsail:DetachStaticIp”****,**
**“lightsail:GetInstanceState”****,**
**“lightsail:GetBundles”****,**
**“lightsail:TagResource”****,**
**“lightsail:PutInstancePublicPorts”**
**\],**
**“Resource”****:** **“\*”**
**}**
**\]**
**}**
Once the policy is created for Lightsail instance, give the policy a name and hit on the **‘Create Policy’** button.
### **Step 10: Create & Retrieve a User Access Key** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
Now we have to create a user access key. Find **‘Create access key’** under the Summary tab and click on it. Then you will be redirected to the Access Key best practices & Alternatives page, from here select the **‘Other’** option and click on Next.
Now give a Description Tag to proceed to create an access key. Once the access key is created copy the Access Key and Secret from here and go back to your xCloud Dashboard to integrate the server with xCloud.
### **Step 11: Connect the Account & Add Necessary Information** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
From the AWS dashboard, select an existing or connect new account from the dropdown menu. Then choose the AWS services from, you can use any one with the proper credentials or both from the xCloud dashboard.
**_Note:_** _EBS-supported instances of AWS are not supported._
For example, T3 instances use EBS storage. These instances are not available through the API. However, you can set up such instances manually in your AWS account first and then add them through the Any Provider method in xCloud.
As you have the Access Key and Secret Key, Paste them into the designated blank boxes one by one carefully. Now click on the **‘Verify’** button, it will start verifying the credential and connect you with the AWS server.
Fill in all the information like **‘Server Name’**, **‘Server Region’**, **‘Server Zone’**,**’Server Size’**, etc according to your preference.
Next, choose the web server stack from NGINX or OLS as your requirements and click on **‘NEXT’** button to proceed with the server creation process.
It will start creating a AWS server with xCloud within a while and if you go to the **‘Servers’** from the menu you can see your created server and create as many site as you want under this server
## **How to Set Up Node.js on AWS with xCloud** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
xCloud provides an intuitive interface that allows you to easily deploy, manage and scale your [**Node.js**](/node-js-hosting/) applications directly from your Git repository without worrying about manual setup or infrastructure maintenance.
Follow the guide to deploy your Node.js application easily on AWS with xCloud:
### **Step 1: Choose the Application** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
To begin deployment, click on the **‘Add New Site’** button from the dashboard.
You will then be asked to **‘Choose a Server to add Site’** from the dropdown. You must select the **AWS server** you set up in xCloud from this dropdown.
Next, you will see options such as ‘WordPress’ and ‘Custom PHP’. Go to the **‘Node.js’** option from the tab. After that, choose the **‘Choose a Git Repository’** option to import your **Node.js application** using a Git provider.
### **Step 2: Set Up Domains** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
The **‘Domains’** tab allows you to configure your site’s domain. You can either create a **‘Demo Site’** or a **‘Live Site’**. For this documentation, we’ll proceed with the **‘Demo Site’** option and click **‘Next’** to continue.
### **Step 3: Configure Node.js Application** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
In the **‘Settings’** tab, you will find options to configure the **Node.js version** and manage site users. Adjust them according to your preferences.
Next, you will see the **‘Server-Side Rendering App’** option. To proceed with a **‘Client-Side Rendering App’**, keep the toggle off.
To deploy a **‘Server-Side Rendered App’**, toggle it on.
#### **Client-Side Rendering (CSR):** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
If your application is built using frameworks like **React or Vue** that render content in the browser, keep the toggle off. In this mode, the server mainly serves static files and all rendering happens on the client side.
#### **Server-Side Rendering (SSR):** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
If your Node.js application _(for example, Next.js or Nuxt.js)_ renders pages on the server before sending them to the client, toggle this option on. This allows xCloud to configure the environment to **support SSR** processes properly.
Here we are proceeding with deploying a **‘Server Side Rendered App’** option →
**Then you’ll need to provide a few essential details:**
**◽Port:** Enter the port number your Node.js application listens on (e.g., 3000 or 8080). xCloud uses this port to connect incoming traffic to your app.
**◽Start Command:** Specify the command that runs your application (for example, npm start, node server.js, or yarn dev). This tells xCloud how to start your Node.js server after deployment.
**◽Web Root Path:** If your project’s main application files are located in a subdirectory (for instance, /app or /src), enter that path here. If your app is in the root directory, you can leave this field blank.
Now, insert the **‘Port’** and **‘Start Command’** in the respective fields. You can also specify a **‘Web Root’** Path for your application.
In the following step, you can choose one of the database options **‘No Database’**, **‘Add an Existing Database’**, **‘Create a New Database’** directly on the server. Once selected, click **‘Next’**.
### **Step 4: Insert Git Repository Credentials** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
In the **“Git Repo”** tab, you will find three repository options: **‘Private Repository (Manual SSH URL)’**, **‘Public Repository (Manual HTTPS URL)’**, **‘Connected Git Provider’**.
If you choose Public Repository (Manual HTTPS URL), enter your GitHub Repository URL and specify the Git Branch.
**Note:** _Copy the HTTPS URL from your GitHub repository dashboard._
If you choose **Private Repository (Manual SSH URL)**, enter your **GitHub Repository SSH URL** and specify the **Git Branch**.
**Note:** _Copy the SSH URL from your GitHub repository dashboard._
In this document, we’ll deploy the project using the **“Git Provider”** option.
Choose **“Connected Git Provider”** from the dropdown menu. From the **“Select Git Provider”** list, choose the connected account you want to use. Then, browse through the repositories, select the one you want to deploy and choose the specific branch of that project.
### **Step 5: Enable Push-to-Deploy** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
The next step is to enable automated deployment. Toggle on the **‘Enable Push to Deploy’** option. Copy the **‘Deployment URL’** provided here, you will need to insert it into your GitHub repository’s webhook settings.
### **Step 8: Run Deployment Script** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
Once the repository integration is complete, you can configure post-deployment actions.
In the **‘Deployment Script’** field, enter any custom commands you want to execute after deployment.
You can also select one of the example scripts provided. After configuring this, click **‘Next’** to continue.
Next, you can specify the subdirectory where your .env file should be created in the **“.env File Path”** field. You can also enter the contents of your **.env** file in the **“File Content”** field.
### **Step 9: Confirm Deployment** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
The final step is to confirm and start the deployment. Click the **‘Start’** button to begin the process. You can monitor the deployment progress in real time.
After deployment, a success message will appear. From there, access your site dashboard and visit your site to confirm your Node.js app is running on **AWS server** with xCloud.
### **Environment Editor for Node.js Application** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
The Environment section in xCloud allows you to customize configuration settings for your n8n instance. Just go to the **‘Environment’** option from the sidebar and adjust as you need then click on the **‘Save’** button.
### **SSR Configuration for Node.js application** [#](/docs/set-up-node-js-on-aws-with-xcloud/)
If you are deploying an SSR application, you can update the **‘Application Port’**, **‘Start Command’** later as well.
Just go to the **‘SSR Configuration’** from the **‘Node.js’** Menu under the site dashboard and click on the **‘Update Configuration’** button.
Setting up a Node.js application on a AWS server with xCloud is simple and efficient.