MHOSTMHOST

Ready-made VMmanager 6 recipes: what you can set up in one click

A recipe is a ready-made script that VMmanager 6 runs on the server for you: it installs the software you need, sets up configuration files, and gets the server working without any manual fiddling in the console. mHost has more than twenty of these recipes — everything from control panels to monitoring and VPN.

What a recipe is

Technically, a recipe is a post-install script tied to one or more OS templates through compatibility tags. Because of this:

  • a recipe only shows up in the list if it's compatible with the selected operating system;
  • a recipe has an access level — "Owner" (visible only to its author) or "Everyone" (available to all clients); every recipe in the catalog below is set to "Everyone".

How to apply a recipe to a server

The easiest way is to run the recipe right on a live server, without reinstalling anything:

  1. Log in to VMmanager 6 — see the "How to log in to VMmanager 6" article.
  2. In the list of virtual machines, find your server and click the "⋮" (three dots) icon next to it → "Run script".
  3. Pick the recipe you need from the list (it only shows up if it's compatible with the server's OS — see the "OS" line for each entry below) and run it.
  4. Wait for the recipe to finish. No reinstall needed, no data lost.

For a step-by-step example — from logging into the panel to the finished result — see the "Installing Google Chrome on a Windows server" article.

Second method — when installing or reinstalling the OS. You can pick a recipe when ordering a server or reinstalling it, in the pre-installed software section. This is handy for a clean setup from scratch (OS-level recipes and control panels are usually installed this way). Important: reinstalling the OS wipes the server's disk completely — only use this on a new/empty server, or after making a backup first (mHost VPS don't offer snapshots).
Important: the list of available recipes depends entirely on the OS template you've selected — a recipe is only offered for the operating systems it's compatible with (see "OS" for each entry below).
Important: nested virtualization is disabled on mHost virtual servers. This means you can't run your own hypervisor inside a VPS, spin up nested virtual machines, or use software emulators (KVM and similar). Recipes that do exactly that won't work on mHost servers — they're listed separately at the very bottom of the article and marked as unavailable.
Tip: a few recipes (Zabbix server, Redmine) leave a default password in place after installation — be sure to change it right after your first login, before exposing the service to the outside world.

Recipe catalog

Control panels

  • Ispmanager (ID 17) — the ISPmanager hosting control panel: sites, mail, databases, DNS — all from a single web interface. OS: AlmaLinux 8/9/10, Debian 11/12, Ubuntu 22.04/24.04, Rocky Linux 8, plus the lic_ISPmanager_6_Lite template (an OS with an ISPmanager 6 Lite license already included).
  • ISPmanager + MariaDB (ID 26) — the same thing, but with MariaDB already configured out of the box. OS: AlmaLinux 8/9/10, Ubuntu 22.04/24.04, Rocky Linux 8, plus the lic_ISPmanager_6_Lite_mariadb template.

CMS and business applications

  • 1С-Битрикс: Веб-окружение (ID 22) — a ready-made server environment (web server, PHP, database) for 1С-Битрикс sites — all that's left is to deploy the site itself. OS: CentOS Stream 9, AlmaLinux 9, Oracle Linux 9, Rocky Linux 9.
  • 1С-Битрикс: CRM (ID 21) — a ready-made 1С-Битрикс24/CRM install. OS: CentOS 7.

Web stack

  • LEMP (ID 4) — Linux + Nginx + MySQL + PHP in one recipe. OS: Linux.
  • LAMP (ID 3) — the classic LAMP stack (Linux, Apache, MySQL, PHP), with Nginx thrown in too. OS: Linux.
  • Django (ID 1) — a Django + uWSGI + Nginx environment. OS: Linux.
After installation, open the server's IP address in your browser — you'll find further instructions for working with the environment there.
  • Tomcat (ID 8) — the Apache Tomcat servlet container, listening on port 8080. OS: Linux.
If your server's virtualization type isn't OpenVZ, the Tomcat admin web interface is also available; the login password is your server's root password.

Network and VPN

  • Wireguard VPN (ID 15) — sets up a VPN server on WireGuard. OS: CentOS Stream 9, AlmaLinux 8/9, Rocky Linux 8/9, Oracle Linux 8/9, Debian 11/12, Ubuntu 20.04/22.04/24.04.
The recipe places a ready-made client connection config at /etc/wireguard/client/client.conf.
  • Openvpn (ID 5) — sets up a VPN server on OpenVPN. OS: Linux.
The client connection key is in /etc/openvpn/easy-rsa/keys.
  • Route Reflector (ID 16) — sets up the FRR daemon as a BGP Route Reflector. OS: Debian 11/12, Ubuntu 20.04/22.04/24.04, AlmaLinux 8/9, Oracle Linux 8/9, CentOS Stream 9, Rocky Linux 8/9.
Running this recipe again on the same server adds new BGP neighbors and may enable VxLAN — keep that in mind if you plan to run it more than once.

Monitoring

  • Zabbix server (ID 11) — a full-featured Zabbix monitoring server. OS: Linux.
Web interface login: username Admin, password zabbix. Change the password right after your first login.
  • Zabbix proxy (ID 12) — a Zabbix proxy in passive mode, for collecting metrics from remote nodes and forwarding them to the Zabbix server. OS: Linux.
  • Zabbix agent2 linux (ID 10) — a Zabbix agent for monitoring the server itself. OS: Linux.
  • Nagios ncpa linux (ID 13) — the Nagios monitoring agent (NCPA). OS: CentOS Stream 9, AlmaLinux 8/9, Rocky Linux 8/9, Oracle Linux 8/9, Debian 11/12, Ubuntu 20.04/22.04/24.04.

Other

  • Teamspeak (ID 7) — a TeamSpeak 3 voice server. OS: Linux.
The server admin's login, password, and token are in the /root/ts3_login_data file.
  • Redmine (ID 6) — the Redmine bug tracker and task manager. OS: Linux.
Login: username admin, password admin, or the server's root password — depends on the OS. Change the password right after your first login.
  • Google Chrome (ID 18) — installs the Google Chrome browser on a Windows server. OS: Windows Server 2022/2019/2016/2012 R2, Windows 11, Windows 10, Windows. For a detailed step-by-step walkthrough, see the "Installing Google Chrome on a Windows server" article.

Recipes not available on mHost VPS

These recipes deploy their own hypervisor or virtualization platform inside the server — and nested virtualization is disabled on mHost VPS (see the warning above). We're listing them here for the sake of a complete catalog, but you won't be able to use them on your own VPS.

  • Installing VMmanager-KVM (ID 25) — deploys the VMmanager panel for managing KVM virtualization. OS: CentOS 6/7. — not available on mHost VPS.
  • Installing VMmanager-OVZ (ID 24) — the same thing, but for OpenVZ containers. OS: CentOS 6. — not available on mHost VPS.
  • Proxmox VE (ID 23) — deploys the Proxmox VE virtualization platform. OS: Debian 11/12. — not available on mHost VPS.

What's next

Not sure which recipe fits your task, or need one that isn't on the list? Contact mHost support — we'll help you out. And if you haven't logged into the panel yet, start with the "How to log in to VMmanager 6" article.

Related articles

PreviousHow to log in to VMmanager 6 — the control panel for your VPSNextInstalling Google Chrome on a Windows server using a ready-made recipe