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 errorsInstall CyberPanel on a fresh supported VPS, connect as root over SSH, run the official installer, choose OpenLiteSpeed or LiteSpeed Enterprise, open only the ports your store needs, and finish the panel setup at https://<server-ip>:8090. Before sending shoppers to the server, configure DNS, HTTPS, backups, firewall rules, capacity monitoring and a tested recovery procedure. CyberPanel’s documented minimum of 1,024 MB RAM and 10 GB of disk is an installation floor, not a sensible production target for most stores.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What you need before installing
A control-panel installation is easiest to recover when the VPS is empty. CyberPanel’s installation guidance lists Ubuntu 20.04 or 22.04, AlmaLinux 8 or CloudLinux OS, at least 1,024 MB of RAM and 10 GB of disk space. Use a clean server with no other hosting panel or preconfigured web stack. Mixing an existing panel, web server or database service with the installer can create conflicting packages and ports.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Supported starting point
- Operating system: Ubuntu 20.04, Ubuntu 22.04, AlmaLinux 8 or CloudLinux OS, as listed in CyberPanel’s installation documentation.
- Memory: 1,024 MB minimum for installation.
- Storage: 10 GB minimum for installation.
- Access: the VPS provider’s root credentials and network access for SSH.
- Server state: a fresh installation with no second control panel.
Why the minimum is not a store-sizing recommendation
A live shop has a catalog, database queries, checkout sessions, image files, logs, caches, scheduled jobs and backups competing for resources. Size the VPS for the application you will run rather than for the panel alone. Consider:
- CPU capacity for PHP or other application workers, imports, search indexing and administrative tasks.
- RAM for the operating system, database buffer/cache, web workers, object cache and traffic bursts.
- Fast storage and sufficient I/O for product images, database writes, logs and backup jobs.
- Database capacity for customers, orders, inventory, sessions and reporting.
- Free space for growth and for creating a temporary recovery copy during an incident.
No universal production size or controlled ecommerce benchmark is established for CyberPanel. Start with measured requirements from your application, then watch memory, CPU, storage and database growth after launch.
#1 Best Overall
Provision the VPS and connect as root
- Deploy a new VPS with one of the supported operating systems. Record the provider-assigned IP address and root password or key.
- Confirm that the provider-level firewall allows SSH from your administration network. Keep the initial rule narrow if the provider supports source-IP restrictions.
- Connect over SSH as
root. CyberPanel’s documented procedure uses a root shell; usingsudois not the normal path for this installer. - Verify that the hostname, clock and network are correct before changing DNS. Do not point a production domain at the server until the panel, site, database, HTTPS and recovery process are ready.
Keep the SSH session open while the installer runs. If your connection drops, do not start a second installer blindly; reconnect, inspect whether the first process completed and check the panel before repeating anything.
Run the CyberPanel installer
Start the documented installer
From the root shell, run CyberPanel’s documented command:
sh <(curl http://cyberpanel.net/install.sh || wget -O - http://cyberpanel.net/install.sh)The command downloads and executes the current installation script. Because a shell installer can change packages and services with root privileges, verify the current command and instructions in CyberPanel’s live documentation immediately before a production installation. Prefer the secure HTTPS form when the documentation provides one, and use a disposable or snapshot-backed VPS if you are validating the process first.
Choose the web-server edition
The interactive installer asks which CyberPanel web-server path to deploy:
- CyberPanel with OpenLiteSpeed: the free, open-source backend described by CyberPanel. It is the straightforward choice when you want the open-source edition and its available caching integrations.
- LiteSpeed Enterprise: the commercial LiteSpeed Web Server Enterprise path, with separate licensing terms. Choose it only after confirming the license, application compatibility, required support and the performance features your team actually needs.
Select only the add-ons your store requires. Every additional service creates another update, configuration and security responsibility. Record the choices you make so a replacement server can be rebuilt consistently.
Allow the installation to finish and reboot
The installer may reboot the VPS when it completes. If it does not, reboot manually after the process reports success. Wait for the operating system to return, then reconnect over SSH and confirm that the panel and selected web services are running before proceeding.
Open only the ports your deployment uses
Rules must be applied in two places: the VPS provider’s network firewall and the firewall on the server itself. A rule at only one layer can still block traffic, while an unnecessarily broad rule at either layer exposes a service you do not need.
| Purpose | Protocol and ports | When to expose it |
|---|---|---|
| CyberPanel administration | TCP 8090 | Required to reach the panel; restrict source addresses where practical. |
| Web traffic | TCP 80 and TCP 443; UDP 443 | Required for HTTP and HTTPS site traffic. UDP 443 is used for supported HTTP/3 or QUIC web traffic. |
| FTP | TCP 21 and TCP 40110–40210 | Open only if you deliberately use CyberPanel’s FTP service and its passive range. |
| TCP 25, 587, 465, 110, 143 and 993 | Open only when this VPS sends or receives mail. Otherwise leave mail ports closed and use an external mail service. | |
| DNS | TCP and UDP 53 | Required only if this server will provide authoritative DNS. |
Keep SSH access available for administration, but protect it with keys, source allowlists or a VPN where your operating model permits. Do not open FTP, mail or DNS merely because the installer lists those ports.
Sign in and harden the panel
- Open
https://<Your Server's IP Address>:8090in a browser after the reboot. - Sign in with the administrator credentials created during installation.
- Immediately replace any temporary or default password with a unique, long password stored in your team’s password manager.
- Use CyberPanel’s firewall and the provider firewall together. Remove unused inbound rules and limit panel access to trusted networks when possible.
- Document who can administer the panel, how SSH keys are revoked and how emergency access is recovered.
The panel URL is separate from your store’s public HTTPS URL. A browser warning on the IP-and-port address during initial administration does not replace the trusted certificate you must issue for the ecommerce domain.
Prepare the ecommerce site before accepting orders
Create the site and database
Use CyberPanel to create the website, its database and the application credentials. Keep database credentials out of source code and use separate accounts for development, staging and production when the application supports that arrangement. Import the catalog and media only after confirming available disk space and a rollback copy.
Free tools Windows power users keep installed
One-click scans. No signup required.
Point DNS deliberately
Create the required DNS records at the DNS provider that is authoritative for the domain. Point the store’s web records to the VPS address only after the site responds correctly on the server. If you use separate names for checkout, media, administration or an API, plan each record and its certificate rather than assuming one hostname covers all traffic.
Issue HTTPS before checkout traffic
CyberPanel advertises automatic SSL and website management. Issue a certificate for every hostname that handles storefront, account or checkout traffic, then test both HTTP-to-HTTPS redirection and the certificate chain from an external network. Do not accept real orders while checkout still depends on an unencrypted or mismatched hostname.
Stage application changes
Test themes, extensions, payment integrations and database migrations on a staging copy first. Schedule updates for a period when you can observe logs and checkout behavior, and write down the rollback action for each change. The available documentation does not provide a performance result for a particular ecommerce application, so validate your own stack under representative catalog and traffic conditions.
Choose OpenLiteSpeed or LiteSpeed Enterprise
| Decision factor | OpenLiteSpeed | LiteSpeed Enterprise |
|---|---|---|
| License model | Free and open source, according to CyberPanel’s “Get Started with CyberPanel” description. | Separate commercial licensing terms for LiteSpeed Web Server Enterprise. |
| Compatibility question | Confirm that the chosen ecommerce application, extensions and web-server directives work with OpenLiteSpeed. | Confirm compatibility and whether Enterprise-specific features justify the license. |
| Operational requirement | Your team must be comfortable operating and updating the open-source stack. | Budget for licensing and ensure the team can support the Enterprise configuration. |
| Caching decision | Validate the cache integration and purge behavior with your application. | Validate Enterprise caching features, application compatibility and purge behavior. |
Neither edition removes the need to test cart, login, checkout, inventory and cache invalidation. A cached product page may be useful; a cached cart or account response can be harmful if the application is not configured correctly.
Recommended Free Tools
Backups and recovery are part of installation
CyberPanel documents backup capability, but no backup exists until you configure and verify one. Set a schedule for both database and site files, keep a copy away from the VPS, and monitor whether each job completed. Local-only backups do not protect you from a lost disk or a deleted server.
- Include databases, uploaded product images, application configuration, certificates or certificate configuration, and any custom deployment files.
- Retain enough versions to recover from an undetected data or application error, not just the latest snapshot.
- Test restoration on a separate location. A job marked “successful” is not proof that a usable store can be rebuilt.
- Record the restore order: provision the operating system, install CyberPanel, restore files and database, configure DNS and certificates, then validate storefront and checkout.
- Keep emergency contact details, provider credentials and license information with the recovery runbook, but not in publicly accessible files.
Operate the VPS safely after launch
Keep firewall layers aligned
Review provider and server firewall rules together after every service change. Close port 8090 to the public internet if your administration method allows a trusted-network allowlist or VPN. Leave mail, FTP and DNS closed when those services are not part of the design.
Patch in a controlled window
Monitor CyberPanel, the operating system, the selected web server, the database and the ecommerce application for updates. Take a verified backup before a high-risk update, apply it to staging first, and keep the documented rollback path available. Automatic updates can be convenient, but they should not remove your ability to diagnose a failed checkout or incompatible extension.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Monitor the resources that affect checkout
Track memory pressure, CPU saturation, storage usage, disk I/O, database growth, backup duration and error logs. Set alerts before storage reaches full capacity; a full disk can prevent database writes, logs, certificates and backups from completing. Compare ordinary traffic with promotions, catalog imports and scheduled jobs so capacity decisions are based on your store’s workload.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.One-click image alternatives
If you do not want to run a command-line installer, the official LiteSpeed cloud-image documentation lists marketplace or one-click paths for DigitalOcean, Vultr, Linode, Google Cloud, AWS, Azure, Alibaba Cloud and IDrive Compute. These are provider options rather than a guarantee of identical pricing, regions or support. Compare CPU and RAM choices, storage type and I/O, snapshots, network limits, provider backups, support terms and total cost.
The same image guide says the image can automate installation of LSCache, WordPress, PrestaShop, Joomla and Git. Confirm the image’s operating-system version, included services and update process before using it for a store. A one-click image saves installation steps; it does not replace DNS, HTTPS, firewall, backup or recovery work.
Best Value
Troubleshoot common installation and launch failures
SSH cannot connect
Check the VPS state, IP address, root credentials, provider firewall and the source network from which you are connecting. If SSH was restricted to an allowlist, verify your current public address. Do not repeatedly rerun the installer until you know whether the original session is still active.
Crashes, 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 minuteWindows 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 reinstallThe panel does not load on port 8090
Confirm that TCP 8090 is allowed at both firewall layers and that the server has finished rebooting. Test the exact IP-and-port URL, not the domain name, while DNS is still being prepared. If the service is running but unreachable, inspect provider rules before changing application settings.
The storefront works but HTTPS fails
Verify that the domain resolves to this VPS, TCP 80 and 443 are reachable, and the certificate covers the exact hostname shoppers use. Check HTTP-to-HTTPS redirection and test from outside your administrative network. Do not treat the panel’s IP certificate warning as a valid store certificate.
Mail or FTP stopped working
First confirm that the service is intentionally hosted on this VPS. Check the corresponding ports and passive FTP range at both firewalls, then review service logs and credentials. If the service is not required, keep its ports closed and remove the dependency from the application rather than widening firewall access.
Backups report success but cannot restore
Run a complete test restore to a separate location, including the database and uploaded media. Compare the restored catalog, customer records, order data and checkout configuration with the original. Update the backup job or retention policy when the test exposes missing files or an unusable database dump.
Pre-launch checklist for a live store
- Fresh supported operating system and no competing control panel.
- Capacity planned above the 1,024 MB RAM and 10 GB disk installation minimum.
- CyberPanel installed and the OpenLiteSpeed or Enterprise choice documented.
- Panel access on TCP 8090 restricted as far as your administration model allows.
- Only required web, mail, FTP and DNS ports exposed.
- Store and database created, with credentials protected.
- DNS records resolving to the intended VPS address.
- Valid SSL certificate installed for every customer-facing hostname.
- Local and remote backups scheduled, monitored and restored successfully in a test.
- SSH, firewall, update and emergency-access procedures written down.
- Staging validation completed for catalog, login, cart, checkout, payment callbacks, inventory and cache purges.
- Rollback and provider recovery steps available to the person on call.
CyberPanel can provide the control panel and web-server foundation, but the reliability of an ecommerce site depends on the surrounding operations: correct sizing, restricted access, tested HTTPS, disciplined updates, monitored backups and a recovery plan that has actually been exercised.
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.
