Remove references to Managed Vhosts' legacy nginx configuration

Jonathan Visser · Jonathan Visser · commit 978502b3393e · 2025-10-24T16:14:43.000+02:00
diff --git a/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md b/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md
@@ -73,17 +73,6 @@ Flush the cache of Magento on the Hypernode. (`magerun cache:flush`)
 
 ## Step 7: Set up Hypernode Managed Vhosts
 
-The Hypernode Managed Vhosts (HMV) system is currently enabled by default on all new booted Hypernodes (all Hypernodes created after 01-05-2020).
-
-Check if you have HMV enabled by running this command:
-
-```console
-app@abcdef-example-magweb-cmbl:~$ hypernode-systemctl settings managed_vhosts_enabled
-managed_vhosts_enabled is set to value True
-```
-
-If this is not enabled, skip the part below.
-
 Due to this configuration it is required to add a new vhost for every domain you want to link to your Hypernode. So you need to configure your DNS correctly and add a new vhost for the domain.
 
 To add a new vhost, for example the domainname [www.example.com](http://www.example.com), to your configuration, you can simply run the command `hypernode-manage-vhosts www.example.com`. This will create a new vhost configuration in `/data/web/nginx/www.example.com/`, using the Magento 2 template.
diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode.md
@@ -14,13 +14,9 @@ redirect_from:
 
 Akeneo 3 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 5.7, PHP 7.2 and Elasticsearch 6.x**, so it won’t affect your shop negatively. Installing Akeneo version 3.x may take up to 15 minutes.
 
-## Enable managed_vhosts
+## Managed Vhosts
 
-All new Hypernodes (from April 2020) will automatically be booted with [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). If you already have an older Hypernode, then you need to enable Hypernode Managed Vhosts by running the following command:
-
-```bash
-hypernode-systemctl settings managed_vhosts_enabled True
-```
+Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
 
 ## Create a Managed_vhost for a (Sub)Domain
 
diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md
@@ -15,13 +15,9 @@ redirect_from:
 
 Akeneo 4 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.3 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 4.x may take up to 15 minutes.
 
-## Enable managed_vhosts
+## Managed Vhosts
 
-All new Hypernodes (from April 2020) will automatically be booted with [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). If you already have an older Hypernode, then you need to enable Hypernode Managed Vhosts by running the following command:
-
-```bash
-hypernode-systemctl settings managed_vhosts_enabled True
-```
+Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
 
 ## Create a Managed_vhost for a (Sub)Domain
 
diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md
@@ -14,13 +14,9 @@ redirect_from:
 
 Akeneo 5 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.4 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 5.x may take up to 15 minutes.
 
-## Enable managed_vhosts
+## Managed Vhosts
 
-All new Hypernodes (from April 2020) will automatically be booted with [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). If you already have an older Hypernode, then you need to enable Hypernode Managed Vhosts by running the following command:
-
-```bash
-hypernode-systemctl settings managed_vhosts_enabled True
-```
+Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
 
 ## Create a Managed_vhost for a (Sub)Domain
 
diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md
@@ -14,13 +14,9 @@ redirect_from:
 
 Akeneo 6 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.0 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 6.x may take up to 15 minutes.
 
-## Enable managed_vhosts
+## Managed Vhosts
 
-All new Hypernodes (from April 2020) will automatically be booted with [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). If you already have an older Hypernode, then you need to enable Hypernode Managed Vhosts by running the following command:
-
-```bash
-hypernode-systemctl settings managed_vhosts_enabled True
-```
+Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
 
 ## Create a Managed_vhost for a (Sub)Domain
 
diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-7-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-7-on-hypernode.md
@@ -15,13 +15,9 @@ redirect_from:
 Akeneo 7 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.1 and OpenSearch 2.x**, so it won’t affect your shop negatively. Installing Akeneo version 7.x may take up to 15 minutes.\
 **Important note: Akeneo 7.x requires MySQL 8.0.30, which is only available on Debian Bookworm.**
 
-## Enable managed_vhosts
+## Managed Vhosts
 
-All new Hypernodes (from April 2020) will automatically be booted with [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). If you already have an older Hypernode, then you need to enable Hypernode Managed Vhosts by running the following command:
-
-```bash
-hypernode-systemctl settings managed_vhosts_enabled True
-```
+Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
 
 ## Create a Managed_vhost for a (Sub)Domain
 
diff --git a/docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md b/docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md
@@ -71,18 +71,6 @@ In our support documentation you will find detailed information about installing
 
 ### Step 4 – Set up Hypernode Managed Vhosts
 
-The Hypernode Managed Vhosts (HMV) system is currently enabled by default on all new booted Hypernodes (all Hypernodes created after 01-05-2020).
-
-Check if you have HMV enabled by running this command:
-
-`hypernode-systemctl settings managed_vhosts_enabled`
-
-If so, it will give the following output:
-
-`managed_vhosts_enabled is set to value True`
-
-If this is not enabled, skip the part below.
-
 Due to this configuration it is required to add a new vhost for every domain you want to link to your Hypernode. So you need to configure your DNS correctly and add a new vhost for the domain.
 
 To add a new vhost, for example the domainname [www.example.com](http://www.example.com), to your configuration, you can simply run the command `hypernode-manage-vhosts www.example.com`. This will create a new vhost configuration in `/data/web/nginx/www.example.com/`, using the Magento 2 template.
diff --git a/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md b/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md
@@ -129,19 +129,7 @@ Don’t fancy these solutions? Migrate your domain to Hypernode and let us manag
 
 ## DNS and Hypernode Managed Vhosts
 
-The Hypernode Managed Vhosts (HMV) system is currently enabled by default on all newly booted Hypernodes (all Hypernodes created after 01-05-2020).
-
-Check if you have HMV enabled by running this command:
-
-`hypernode-systemctl settings managed_vhosts_enabled`
-
-If so, it will give the following output:
-
-`managed_vhosts_enabled is set to value True`
-
-If this isn't enabled, you can just skip the part below.
-
-Due to this configuration, it is required to add a new vhost for every domain you want to link to your Hypernode. So you need to configure your DNS correctly and add a new vhost for the domain.
+With Hypernode Managed Vhosts (HMV), you must add a new vhost for every domain you want to link to your Hypernode. So you need to configure your DNS correctly and add a new vhost for the domain.
 
 To add a new vhost, for example the domain name `www.example.com`, to your configuration, you can run the command `hypernode-manage-vhosts www.example.com`. This will create a new vhost configuration in `/data/web/nginx/www.example.com/`, using the Magento 2 template.
 
diff --git a/docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md b/docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md
@@ -1,9 +1,7 @@
 ---
 myst:
   html_meta:
-    description: 'We recommend serving your site only over HTTPS traffic. This is
-      safer and is better for search index optimization. Configure your shop with
-      these steps. '
+    description: 'We recommend serving your site only over HTTPS traffic. This is safer and is better for search index optimization. Configure your shop with these steps. '
     title: How to configure your shop to only use https? | Hypernode
 redirect_from:
   - /en/hypernode/nginx/how-to-configure-your-shop-to-only-use-https/
@@ -26,40 +24,16 @@ Please check out [this article](../ssl/how-to-use-ssl-certificates-on-your-hyper
 
 ## Order Let’s Encrypt Certificates
 
-### On Hypernodes With Hypernode Managed Vhosts Enabled
+### Ordering Let’s Encrypt Certificates on Hypernodes
 
 **Please note: If you want to use Let’s Encrypt and have the Hypernode Managed Vhosts (HMV) system enabled, you need to configure LE during the creation of the vhost. Using the old method with dehydrated won't work!**
 
-First, check if HMV is enabled on your Hypernode:
-
-`hypernode-systemctl settings managed_vhosts_enabled`
-
-If so, it will give the following output:
-
-`managed_vhosts_enabled is set to value True`
-
 If you want to request a LE certificate you need to add the `--https` flag with the HMV-command.
 
 `hypernode-manage-vhosts www.example.com --https --force-https`
 
 This command will not only request a LE Certificate but because of the --force-https flag it will also redirects all traffic for that specific vhost to HTTPS.
 
-### On Hypernodes Without Hypernode Managed Vhosts Enabled
-
-To order [Let’s Encrypt](../ssl/how-to-use-lets-encrypt-on-hypernode.md) certificates for all storefronts, use the following command:
-
-```bash
-## Create an entry for each storefront
-for DOMAIN in $( n98-magerun sys:store:config:base-url:list --format=csv | sed 1d | cut -d , -f 3 | perl -pe "s/https?://(www.)?//" | tr -d "/" | sort -u ); do
-    echo -e "$DOMAIN www.${DOMAIN}" >> ~/.dehydrated/domains.txt
-done
-
-## Order the certificates
-dehydrated -c --create-dirs
-```
-
-Don’t forget to [add the cron to renew your certificates](../ssl/how-to-use-lets-encrypt-on-hypernode.md) to the crontab if you are using Let’s Encrypt!
-
 ## Changing Your Base URLs
 
 If your SSL certificates are linked to your Hypernode, or you ordered Let’s Encrypt certificates, we can change the base URLs to use only HTTPS. To make this easier, we created a little Python script that changes all your base URLs to HTTPS:
@@ -89,7 +63,7 @@ if ($scheme = http) {
 }
 ```
 
-**Please note that if you have [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) enabled, you can skip this.**
+**Please note that with [Hypernode Managed Vhosts](hypernode-managed-vhosts.md), you typically do not need this snippet.**
 
 ## Check Settings of Third Party Solutions
 
diff --git a/docs/hypernode-platform/nginx/how-to-redirect-from-or-to-www.md b/docs/hypernode-platform/nginx/how-to-redirect-from-or-to-www.md
@@ -24,7 +24,7 @@ More info can be found [on our page about setting your DNS](../dns/how-to-manage
 
 ## Redirect From Apex to WWW
 
-**When hypernode-managed-vhosts enabled**
+**When Hypernode Managed Vhosts is enabled**
 
 To redirect all traffic to www you have to create both a vhost for the Apex and for the `www`. For the non-www vhost you can create the vhost as type wwwizer. This will redirect all traffic to the `www`. version of that vhost. This can be achieved by running: `hypernode-manage-vhosts example.com --type wwwizer`.
 
@@ -34,17 +34,7 @@ To redirect all traffic to www you have to create both a vhost for the Apex and
 | www.example.com | magento2 | False          | False | False       | False   | intermediate |
 ```
 
-**Without hypernode-manage-vhosts enabled (old legacy nginx-config)**
-
-You can redirect all traffic to www with the following Nginx snippet:
-
-```nginx
-if ($http_host ~* "^example.com$") {
-    rewrite ^ https://www.$http_host$request_uri;
-}
-```
-
-Save this snippet in `/data/web/nginx/server.rewrites`.
+<!-- Legacy nginx instructions removed: Hypernode platform uses Managed Vhosts across the board. -->
 
 ## Redirect From WWW to Apex
 
diff --git a/docs/hypernode-platform/nginx/hypernode-managed-vhosts.md b/docs/hypernode-platform/nginx/hypernode-managed-vhosts.md
@@ -60,14 +60,6 @@ Please take not that the webroot option is not used for the built-in staging for
 
 **Please note: If you want to use Let’s Encrypt and have the Hypernode Managed Vhosts (HMV) system enabled, you need to configure LE during the creation of the vhost. Using the old method with *dehydrated* won't work!**
 
-First, check if HMV is enabled on your Hypernode:
-
-`hypernode-systemctl settings managed_vhosts_enabled`
-
-If so, it will give the following output:
-
-`managed_vhosts_enabled is set to value True`
-
 If you want to request a LE certificate you need to add the `--https` flag with the HMV-command.
 
 `hypernode-manage-vhosts www.example.com --https --force-https`
@@ -114,7 +106,7 @@ hypernode-manage-vhosts example.com --object-storage-defaults
 
 ### Vhost-specific configuration
 
-Once you have setup a vhost, say [www.example.com](http://www.example.com), you can place your domain specific configuration in its configuration folder, /data/web/nginx/[www.example.com](http://www.example.com). You can do this the same way you configured your legacy, or global configuration. Simply place a file with a `server.` prefix, and it will be included in the vhost's server {} configuration block. You can also still use the `public.` and `staging.` prefixes, if you wish to have public, or staging, specific configuration.
+Once you have setup a vhost, say [www.example.com](http://www.example.com), you can place your domain specific configuration in its configuration folder, /data/web/nginx/[www.example.com](http://www.example.com). You can do this the same way you configure your global configuration. Simply place a file with a `server.` prefix, and it will be included in the vhost's server {} configuration block. You can also still use the `public.` and `staging.` prefixes, if you wish to have public, or staging, specific configuration.
 Please note that any files with the 'HTTP.' prefix will also be loaded in the HTTP context. Nginx, however, only has a single http context. As such, any http configuration placed in a vhost, will also be loaded for all other vhosts.
 
 ### Global configuration
@@ -133,42 +125,4 @@ If you are running into issues (e.g. SSL or other configuration errors) with Hyp
 
 This regenerates the HMV configuration based on what is set in `hypernode-manage-vhosts --list` and in our experience resolves most basic issues with Hypernode Managed Vhosts.
 
-## Enabling Managed Vhosts
-
-The Hypernode Managed Vhosts (HMV) system is currently enabled by default on all new booted Hypernodes.
-
-However if you have a Hypernode created before 01-05-2020 your Hypernode may still be running in 'legacy' mode. To enable the HMV you can run the command:
-
-`hypernode-systemctl settings managed_vhosts_enabled True`.
-
-This will convert your current legacy config into the HMV config. It will also convert all currently active vhosts into managed vhosts.
-
-Please note that while switching to HMV is very easy, there are a few things to check after switching to make sure everything works, as not every setting is automatically transferred.
-
-Run `hypernode-manage-vhosts --list` to get an overview of your current configuration and use the list below to check if it's correct. Not everything will apply to your Hypernode.
-
-- Make sure your domain is the default server instead of the Hypernode. You can do this by running the following command:
-
-`hypernode-manage-vhosts www.example.com --default-server`
-
-- Configure the vhosts to only use HTTPS. If you already have an SSL certificate configured and you don't want to use Let's Encrypt, use this command:
-
-`hypernode-manage-vhosts www.example.com --https --force-https --ssl-noclobber`
-
-This will make sure you won't overwrite the existing SSL certificate.
-
-If you do want to configure Let's Encrypt for the vhost you can use this command:
-
-`hypernode-manage-vhosts www.example.com --https --force-https`
-
-- If you make use of Varnish, make sure to enable Varnish for the specific vhosts:
-
-`hypernode-manage-vhosts www.example.com --varnish`
-
-- Want to redirect all traffic over www? Set up your naked domains to be wwwizers, with this command:
-
-`hypernode-manage-vhosts --type wwwizer [example.com](//example.com)`
-
-Please make sure to also double check your custom Nginx configurations, as these might not be converted automatically.
-
-You can always use `hypernode-manage-vhosts --help` to get more information on the different configurations.
+##
diff --git a/docs/hypernode-platform/ssl/how-to-use-lets-encrypt-on-hypernode.md b/docs/hypernode-platform/ssl/how-to-use-lets-encrypt-on-hypernode.md
