Install CyberPanel on a newly provisioned, supported VPS, connect as root over SSH, run the official installer, choose OpenLiteSpeed or LiteSpeed Enterprise, open only the ports your services need, then sign in at https://<server-ip>:8090. Do not send store traffic to the server until DNS, TLS, backups, firewall rules, updates and a tested recovery procedure are ready.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The documented installation floor is Ubuntu 20.04 or 22.04, AlmaLinux 8 or CloudLinux OS, 1,024 MB of RAM and 10 GB of disk. Those figures are enough to install the panel, not a production sizing recommendation for a live shop.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What CyberPanel does for an ecommerce VPS
CyberPanel is a web-hosting control panel built around LiteSpeed web-server software. It provides a browser interface for creating websites, databases, email accounts, DNS records, certificates, backups and firewall rules instead of requiring every task to be performed manually from a shell. OpenLiteSpeed is the free, open-source path; LiteSpeed Enterprise is a separately licensed option with different support and feature terms.
For an online store, the panel is useful because it brings common hosting tasks into one administration layer. It does not, by itself, make an application secure, guarantee uptime or size a server correctly. Checkout reliability still depends on the store software, database, payment integration, PHP or runtime configuration, network, monitoring and operational discipline.
#1 Best Overall
Choose and size the VPS before installing
Supported operating systems and installation minimum
CyberPanel’s installation documentation lists a fresh installation of Ubuntu 20.04 or Ubuntu 22.04, AlmaLinux 8 or CloudLinux OS. The same guidance lists at least 1,024 MB RAM and 10 GB disk space. Use a clean server with no other hosting control panel installed; an existing panel or preconfigured web stack can conflict with the installer.
| Item | Documented floor | What a store operator should consider |
|---|---|---|
| Operating system | Ubuntu 20.04/22.04, AlmaLinux 8 or CloudLinux OS | Use a supported image supplied by your VPS provider and keep the exact release documented for future recovery. |
| Memory | 1,024 MB RAM | This is an installation minimum. Catalog imports, PHP workers, database buffers, caches, queues and cron jobs usually require substantially more headroom. |
| Storage | 10 GB | Account for the operating system, site files, product images, database, logs, temporary files, local backups and free space needed during upgrades. |
| Server state | Fresh installation | Do not install over another control panel or an unmanaged production stack. |
Capacity factors for ecommerce
Size the VPS from the workload rather than from the panel’s minimum. Estimate the number of catalog records, image variants, daily orders, concurrent checkout sessions, administrative imports and scheduled jobs. Database memory and storage I/O often become constraints before raw CPU does, while image processing and search indexing can create short CPU bursts.
- RAM: leave room for the operating system, web workers, database cache, object cache and deployment tasks. A server that constantly swaps can make checkout latency unpredictable.
- CPU: account for PHP or application workers, image resizing, feed generation, search indexing and background jobs, not just page views.
- Storage performance: fast persistent storage helps databases, sessions, logs and media transformations. Keep free capacity for updates and emergency exports.
- Database growth: measure product, order, customer, session and log growth. Retention policies should be explicit, especially when backups are stored locally.
- Recovery headroom: reserve enough space to create an export or temporary copy during a restore; a completely full disk can prevent both the application and the backup process from working.
Prepare access, DNS and a recovery plan
Record credentials and provider controls
Before starting, save the provider’s root credentials in a password manager and confirm that you can open a console or rescue environment. A web console is valuable if a firewall rule or SSH change locks you out. Record the VPS address, operating-system image, region, disk type and snapshot policy.
Use a staging hostname first
Keep the store’s public DNS pointed at its current service while you install and configure CyberPanel. Use a temporary hostname or hosts-file entry for testing. Prepare the final DNS records, but change them only after the site, database, TLS certificate and payment callbacks have been checked.
Decide where backups live
CyberPanel supports scheduled backups, but no backup exists until you configure and verify one. Plan both a local copy for fast recovery and a remote copy for a failed disk or compromised VPS. Perform a test restoration of the database and a representative media directory before accepting orders.
Install CyberPanel step by step
1. Provision a clean supported VPS
Choose one of the supported operating systems and deploy a new instance. Avoid images that already contain a different control panel. Confirm the server has the documented minimum resources at the absolute least, then add capacity for your store’s workload.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →2. Connect as root over SSH
From a trusted workstation, connect using the root account supplied by the provider:
ssh root@SERVER_IPThe official installation procedure is written for a root session; using sudo is not the normal path described in that guide. If your provider disables direct root login, use its documented root-enabled console or follow the provider’s method for obtaining an equivalent root shell before running the installer.
3. Run the installer
The documented command is:
sh <(curl http://cyberpanel.net/install.sh || wget -O - http://cyberpanel.net/install.sh)This command downloads and executes the installer from CyberPanel. Because it uses an HTTP URL in the published command, verify the current command and transport in CyberPanel’s live documentation immediately before a production installation; use the secure HTTPS form when the current documentation provides it. Review the script source and your provider’s security policy if your organization requires supply-chain verification.
4. Select the web-server edition
The interactive installer asks which CyberPanel variant to deploy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Choice | Licensing and positioning | Decision questions |
|---|---|---|
| CyberPanel with OpenLiteSpeed | Free and open source, according to CyberPanel’s getting-started documentation. | Does your ecommerce application support the required modules and caching behavior? Is your team comfortable operating the community-supported stack? |
| LiteSpeed Enterprise | Uses LiteSpeed Web Server Enterprise with separate licensing terms. | Do the commercial features, support arrangement and compatibility justify the license cost for this store? |
Compare the two choices on licensing cost, domain limits, support requirements, compatibility with your application, caching features and your team’s operational familiarity. Do not assume that a different web server automatically fixes application bottlenecks; validate cache rules and checkout exclusions in a staging environment.
5. Select only needed add-ons
The installer presents optional components. Add only services you will operate. Unneeded mail, FTP or DNS services increase the attack surface and create patching and monitoring work. You can add a required service later using the panel’s documented workflow, whereas exposing unused services from day one complicates hardening.
6. Wait for completion and reboot
Allow the installer to reboot the VPS when it finishes, or reboot manually if the process instructs you to do so. Do not interrupt the session while packages and services are being configured. If the SSH connection drops, reconnect through SSH or the provider console and check whether the installation completed before running anything again.
7. Sign in to the panel
Open:
https://SERVER_IP:8090Sign in with the administrator credentials created during setup. Change any temporary or default password immediately. Where practical, restrict port 8090 to trusted office addresses, a VPN or an administrative allowlist rather than leaving the panel open to every internet address.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsOpen the right ports, and no others
Permit required traffic in both layers: the VPS provider’s network firewall and the operating-system or CyberPanel firewall. A rule in only one layer will not produce the intended result. The installation guide lists these ports:
| Service | Ports and protocol | Expose only when |
|---|---|---|
| CyberPanel administration | TCP 8090 | You need browser administration; restrict source addresses whenever possible. |
| Web traffic | TCP 80 and 443; UDP 443 | The VPS serves HTTP/HTTPS traffic. UDP 443 is used for supported HTTP/3 or QUIC traffic. |
| FTP | TCP 21 and TCP 40110–40210 | You deliberately operate FTP and have configured the passive-port range in the client and firewall. |
| TCP 25, 587, 465, 110, 143 and 993 | The VPS actually provides SMTP, submission or POP3/IMAP services. Mail hosting also requires reputation, anti-abuse controls and monitoring. | |
| DNS | TCP and UDP 53 | The VPS is authoritative for DNS. Otherwise keep these ports closed and use your DNS provider. |
Protect SSH separately. Prefer key-based authentication, disable password login after confirming key access, limit source addresses where feasible and keep a provider-console recovery path. Close unused ports rather than copying a broad “allow everything” rule from a tutorial.
Configure the store before changing DNS
Create the website and database
In CyberPanel, create a website for the store’s domain and create its database and database user. Use a unique, long database password and grant only the permissions the application requires. Keep administrative and staging sites on separate hostnames or accounts so a test deployment cannot overwrite the live document root.
Point DNS records
At your DNS provider, create the required A or AAAA records for the web host and any separate mail or verification records you use. Lower the record’s time to live before a planned migration if you need faster rollback, then raise it after the change is stable. Verify propagation from more than one network before declaring the move complete.
Free tools Windows power users keep installed
One-click scans. No signup required.
Issue and test TLS
Request an SSL certificate through the panel for every hostname that handles login, checkout, APIs or administrative traffic. Confirm that HTTP redirects to HTTPS, the certificate covers the exact hostname, renewal is scheduled and the application generates secure absolute URLs. Test payment-provider callbacks and webhooks over HTTPS before opening the store to customers.
Configure application-level caching carefully
LiteSpeed caching can improve delivery of cacheable pages, but cart, account, checkout, stock and personalized responses must not be served from a shared public cache. Follow the ecommerce application’s integration guidance, define exclusions explicitly and purge cache after catalog or theme changes. Measure cache behavior in staging with separate customer accounts.
Backups, updates and monitoring
Build and verify backup jobs
- Create a scheduled backup policy for databases, site files, configuration and any required certificates or secrets.
- Send a copy to remote storage in addition to any local retention.
- Set retention periods that cover accidental deletion and a delayed compromise.
- Perform a restoration to an isolated location and document the commands or panel path used.
- Record the recovery point and recovery time you can actually achieve; do not infer them from a successful backup log alone.
Patch in a controlled sequence
Keep the operating system, CyberPanel components, web server, runtime, database and ecommerce application updated. Stage plugin, theme and application changes first, take a verified backup, schedule the production change and retain a rollback plan. Avoid applying a major runtime or database upgrade during a sales peak.
Watch the signals that matter
- Disk usage, inode usage and database growth.
- Memory pressure, swap activity and CPU saturation.
- Web-server error rates, slow requests and failed PHP or application workers.
- Database connection exhaustion, lock time and replication or queue failures if used.
- Certificate expiry, backup success and restore-test results.
- Unexpected login attempts, firewall blocks and changes to administrator accounts.
Set alerts before a resource reaches 100 percent. A full disk can prevent logging, database writes, package updates and backup creation at the same time.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.One-click images versus a manual installation
LiteSpeed’s cloud-image documentation lists one-click or marketplace deployment paths for DigitalOcean, Vultr, Linode, Google Cloud, AWS, Azure, Alibaba Cloud and IDrive Compute. These images can automate installation of components such as LSCache, WordPress, PrestaShop, Joomla and Git. They are provider-specific deployment options, not a universal performance guarantee.
| Approach | Advantages | Trade-offs |
|---|---|---|
| Manual installer on a clean VPS | Clear control over the operating-system image, selected add-ons, firewall policy and documented change history. | Requires SSH access, careful port configuration and your own validation of every component. |
| Provider marketplace image | Faster initial deployment and, for listed images, automated setup of selected web applications or caching components. | Image contents, update cadence, regional availability, snapshot behavior and support boundaries vary by provider. |
Compare region, CPU, RAM, storage performance, snapshots, support, network limits, backup policy and total cost before selecting a marketplace image. Confirm the image’s operating-system version and administrator credentials, then apply the same firewall, TLS, backup and restore checks as a manual installation.
Common installation and migration failures
The installer refuses to run
Check that the VPS uses a supported operating system, is freshly provisioned, has enough disk space and has a working network connection. Remove conflicting control-panel software by redeploying a clean image rather than trying to uninstall pieces manually.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe panel will not open on port 8090
Verify the VPS provider firewall and the server firewall independently. Confirm the installer completed and that the service is listening on TCP 8090. Test from a network that is allowed by your administrative allowlist, and use the provider console if SSH or firewall changes locked you out.
The website works by IP but not by domain
Check A and AAAA records, DNS propagation, the website’s configured domain and the TLS certificate’s hostname. Remove an incorrect AAAA record if the VPS does not provide working IPv6; otherwise some visitors may reach an unreachable address.
Checkout pages are cached or redirect incorrectly
Review cache exclusions for cart, account and checkout paths, force HTTPS consistently and test with separate logged-in and anonymous sessions. Purge stale cache after changing rules, then repeat the payment-provider callback test.
Best Value
A restore appears successful but the store is incomplete
Restore the database and files together, verify ownership and permissions, check environment secrets and confirm scheduled jobs and uploaded media. A backup job is not validated until a complete application can start and process a test order in an isolated environment.
Is CyberPanel suitable for a live ecommerce site?
It can be suitable when the team can administer a VPS, keep the panel and operating system patched, configure least-privilege firewall rules, monitor capacity and test restores. The panel supplies hosting automation, SSL and backup features, but the cited documentation does not establish a universal uptime guarantee or a controlled ecommerce performance benchmark. Suitability therefore depends on the application’s requirements and the operator’s ability to run the surrounding infrastructure.
For a small or medium store, a correctly sized VPS with OpenLiteSpeed, conservative caching rules, remote backups and disciplined updates can be a practical setup. A high-volume store, regulated workload or team without Linux administration experience may need a larger architecture or managed operations, regardless of which control panel is selected.
Frequently Asked Questions
Can I install CyberPanel over an existing hosting control panel?
No. Use a fresh supported VPS. Existing control-panel packages and web services can conflict with the installer; redeploy a clean operating-system image instead.
Do I need to open every port listed in the installation guide?
No. Open TCP 8090 and the web ports required for your site. Add FTP, mail or DNS ports only when the VPS actually provides those services, and restrict administrative access wherever possible.
Is 1 GB of RAM enough for an online store?
It is the documented installation minimum, not a production recommendation. Size memory for the application, database, cache, media processing, traffic spikes and recovery tasks, then monitor swap and memory pressure.
What should I test before switching the store’s DNS?
Test the site and database, HTTPS and redirects, cache exclusions, payment callbacks, administrator access, backup restoration and representative checkout flows on the VPS before changing public DNS.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
