VPS Hosting for CMS X-Cart on SSD
X-Cart is a PHP online store that you install on a server of your own. VPS hosting for X-Cart at HIP-HOSTING means a separate machine with full root access, though the panel has no ready X-Cart image, so the platform is installed by hand. The 5.6 branch asks for much more than older releases: Redis, Node and a recent MariaDB. Read the documentation of your version before choosing a plan, and leave room in the memory budget.
Get VPS from $3/mo- Standardfrom $3/mo
- Memoryfrom $10/mo
- Hi-CPUfrom $5/mo
VPS / VDS PLANS
Our VPS hosting plans for CMS X-Cart
Choose a location and plan line. Prices shown per month.
FAQ
Frequently asked questions
IN DETAIL
Service description
What you rent
A KVM server: a system of your own, root access and no neighbours in your files. The platform is not preinstalled; you deploy it. If you want to buy X-Cart VPS hosting without extras, begin with one modest server and enlarge it after the catalogue.
Choosing the system and version
Decide on the X-Cart branch first: PHP and database versions follow from it. For 5.6 pick a recent Linux distribution that offers PHP 8.3 or newer, and check Node 22 and MariaDB 11 in advance, since the system repositories may not carry them. For older releases take the PHP and database versions from the X-Cart compatibility chart. A Unix-compatible system is recommended: the X-Cart documentation advises *NIX servers.
The directory and the web server
The X-Cart package contains sample Nginx and Apache settings in its docs folder. For 5.6 Nginx is the named web server, and the site root must be the public folder rather than the whole X-Cart directory. The files index.php and service.php have to be executable. Read the sample carefully and adapt it: paths and the PHP socket differ from server to server.
Installation
From the 5.5 branch there is no installation wizard: the store is installed with the console script install.sh, and an administrator can be passed with the -a parameter. Settings come from the .env file: put your own changes into .env.local. Both Redis instances must be running before the start. After installation the admin area opens at /admin/ on your domain.
Background work
Version 5.6 needs an asynchronous task worker that runs constantly: the command ./bin/console messenger:consume async. It can be run, for example, as a system service so that it comes back after a reboot. Without the worker, the store's asynchronous tasks are not executed.
Backups
The database is dumped with mysqldump, and according to a help article it can also be done from the admin area: System tools → Database (close the storefront before copying). For 5.6 the copying method is not confirmed by the documentation. Files are packed with tar from the X-Cart root. Keep copies off the server and now and then bring up a test store from them, otherwise you do not know whether restoring works.
Friendly URLs and moving to a new server
In release 5.4.x, friendly addresses are switched on in the admin area (Store Setup → SEO Settings, the Enable clean URL switch), but the server must support address rewriting. From 5.5 such addresses are always on and there is no switch. When moving a 5.4.x store, make a copy of files and database, correct http_host, https_host and web_dir in the host_details section of etc/config.php, correct RewriteBase in .htaccess and delete the var/datacache folder. For 5.6 the documentation does not describe such a scheme, so check the order of a move against the guide for that very branch.
Speed
A store is limited by its database and cache. A fast disk speeds up large queries and index rebuilds, and an NVMe VPS server with X-Cart on Hi-CPU is the quickest option. Concurrent load is still capped by memory: Redis, PHP and the database split it between them, so set memory_limit deliberately and watch free space.
Security
Keep the database and Redis ports closed to the internet: the store needs them only locally. Restrict SSH access to a key. The documentation names only one requirement for file rights: index.php and service.php must be executable. Set the rest on a least-privilege basis and test the store.
Who it suits
- stores on X-Cart that have outgrown shared hosting;
- developers who maintain client storefronts;
- teams that need a test copy next to the live one;
- anyone moving to 5.6 who wants to build an environment for it from scratch.
How to choose a plan
Work from the X-Cart branch and the size of the catalogue. On the 5.6 branch memory has to be shared at once between the database, two Redis instances, PHP and the background worker, and that matters most if you set out to rent VDS hosting for X-Cart. A VPS/VDS for X-Cart grows with the store (disk space is added but not taken away), and cheap X-Cart VPS hosting is good for getting to know the platform and a test storefront.