VPS Hosting for CMS MODX on SSD

MODX Revolution is a platform in PHP for sites whose markup you write yourself: in its documentation a site is assembled from templates, chunks and snippets, and the presentation is written by hand. VPS hosting for MODX at HIP-HOSTING gives the site a private virtual machine with PHP and a database of your choosing. MODX does not appear among the applications, so you unpack it yourself and run the setup wizard in a browser. Resources and add-ons dictate the size, and a bigger plan is available when the site grows.

Get VPS from $3/mo
12 locationsFull root access
VPS for MODX
  • Standardfrom $3/mo
  • Memoryfrom $10/mo
  • Hi-CPUfrom $5/mo

VPS / VDS PLANS

Our VPS hosting plans for CMS MODX

Choose a location and plan line. Prices shown per month.

Tokyo, JapanAvailable

1 vCPU1 GB RAM

  • 10 GB SSD
  • 200 Mbps

$3/ mo

Order VPS

2 vCPU2 GB RAM

  • 20 GB SSD
  • 200 Mbps

$4/ mo

Order VPS

2 vCPU4 GB RAM

  • 40 GB SSD
  • 200 Mbps

$6/ mo

Order VPS

4 vCPU8 GB RAM

  • 80 GB SSD
  • 200 Mbps

$12/ mo

Order VPS

6 vCPU12 GB RAM

  • 120 GB SSD
  • 200 Mbps

$18/ mo

Order VPS

8 vCPU16 GB RAM

  • 160 GB SSD
  • 200 Mbps

$24/ mo

Order VPS

8 vCPU24 GB RAM

  • 240 GB SSD
  • 200 Mbps

$32/ mo

Order VPS

8 vCPU32 GB RAM

  • 320 GB SSD
  • 200 Mbps

$48/ mo

Order VPS

12 vCPU48 GB RAM

  • 400 GB SSD
  • 200 Mbps

$64/ mo

Order VPS

16 vCPU64 GB RAM

  • 500 GB SSD
  • 200 Mbps

$96/ mo

Order VPS

FAQ

Frequently asked questions

Current MODX 3 releases require PHP 8.1 or higher, with 8.2 or newer recommended. The first releases of the line made do with PHP 7.2 and the minimum was raised in 3.2, so on an early release check its own requirements. The database is MySQL 5.7 or later; MySQL 8.0 and up or MariaDB 10.6 and up are recommended.

IN DETAIL

Service description

Installation

Extract the distribution to the document root so that index.php stands beside the core, manager, connectors and setup folders. PHP must be able to write at least to core/cache, core/config, core/packages, core/import and core/export. Create a database in utf8mb4, open /setup/ and choose a new installation. For the administrator pick a name other than admin.

After installation

Delete the setup folder so that outsiders cannot run the installer over your site: the last wizard step has a checkbox for that. After an upgrade, return core/config/config.inc.php to permissions 644. Deactivate developer accounts you no longer need.

Protecting the core

Rules for Apache and nginx shut off core, service folders and files with a dot in the name. Make the answer "404" rather than "forbidden": it gives away less about the system. Serve your own error page instead of the web server's stock one, which makes the system easier to identify.

The manager and connectors

The manager and connectors folders may be renamed, preferably during installation; if you do it later, correct the paths and addresses in core/config/config.inc.php and check that the manager still opens. Connectors are the manager's access points, so they stay on its domain. Limit access to the manager by address or with HTTP authentication in the server config.

Cache and log

Cached data sits in core/cache; you can wipe it safely, as MODX regenerates it on demand. The error log is core/cache/logs/error.log, so look there when a page goes blank. If clearing from the manager did not help after a move, delete the folder contents by hand.

Upgrading

The order is: copy files and database, update the add-ons, log everyone out, clear the cache, unpack the new release separately and merge it into the root without replacing whole folders. Do not overwrite core/config/config.inc.php and core/components. Then open /setup/ and choose the upgrade rather than a new installation, which would overwrite the database.

Moving to a new server

After a move, six paths in core/config/config.inc.php change, and the entry in the workspaces table keeps the old path and can cause a blank manager page until it is corrected. Delete the contents of core/cache by hand. Run setup again only if the move broke something, and choose the upgrade rather than a new installation.

Speed

A MODX site caches its results in core/cache, and an enabled PHP opcode cache takes a good deal of load off the processor. On an NVMe VPS server with MODX the cache regenerates quicker following an upgrade or a purge, whereas concurrency depends on RAM.

Mail and disk

Hand newsletters and form mail to an external provider, since new servers may block mail ports. Panel disk space only grows, so look at the free space monthly. Remove unneeded add-ons through the package manager and do not touch the archives in core/packages without a backup: the core package used by setup lives there too.

Who it suits

  • front-end developers and studios building sites from layouts, theme-free;
  • teams with a second-branch MODX site waiting to move to the third;
  • owners who want web server rules of their own;
  • people leaving shared hosting who want control over PHP.

Choosing a plan

Start by finding out which MODX and PHP versions the site uses today. Anyone planning to buy MODX VPS hosting a pair of vCPUs and 2 GB is a reasonable yardstick for a mid-sized site: this is our own estimate, not a MODX requirement. To rent MODX VDS hosting suits teams ready to run updates and backups themselves. A VPS/VDS for MODX scales without a move, and cheap MODX VPS hosting is one where cache and pages do not compete for memory.