From b29a80ab71d252b34f984d60b94a7493b343ee89 Mon Sep 17 00:00:00 2001 From: Jonathan Visser Date: Fri, 21 Nov 2025 14:26:05 +0100 Subject: [PATCH 1/2] Update wording across our docs now that all Hypernodes use Managed Vhosts --- .../how-to-go-live-with-your-hypernode.md | 4 +-- .../how-to-install-akeneo-3-on-hypernode.md | 7 +++-- .../how-to-install-akeneo-4-on-hypernode.md | 8 +++--- .../how-to-install-akeneo-5-on-hypernode.md | 8 +++--- .../how-to-install-akeneo-6-on-hypernode.md | 8 +++--- .../how-to-install-akeneo-7-on-hypernode.md | 8 +++--- ...basic-staging-environment-with-akeneo-3.md | 4 +-- ...ow-to-configure-varnish-for-magento-2-x.md | 2 +- ...how-to-configure-varnish-for-shopware-5.md | 2 +- .../how-to-host-shopware-on-hypernode.md | 2 +- ...how-to-configure-varnish-for-shopware-6.md | 2 +- ...o-get-started-with-your-hypernode-trial.md | 4 +-- docs/hypernode-platform/cluster.md | 2 +- ...tication-on-hypernode-development-plans.md | 1 - ...how-to-configure-nginx-for-a-multistore.md | 4 +-- .../nginx/how-to-redirect-from-or-to-www.md | 4 +-- ...-limited-requests-429-too-many-requests.md | 2 +- .../nginx/hypernode-managed-vhosts.md | 26 +++++++++---------- .../php/how-to-resolve-502-gateway-errors.md | 2 +- .../how-to-use-lets-encrypt-on-hypernode.md | 4 +-- .../tools/how-to-use-mailhog-on-hypernode.md | 4 +-- ...to-use-the-hypernode-systemctl-cli-tool.md | 5 ---- 22 files changed, 48 insertions(+), 65 deletions(-) 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 index c7d8aa07..4a764a2e 100644 --- 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 @@ -71,9 +71,9 @@ Only if you use Hypernode’s WWW-redirection service, ensure that the base URL Flush the cache of Magento on the Hypernode. (`magerun cache:flush`) -## Step 7: Set up Hypernode Managed Vhosts +## Step 7: Set up Your Vhosts -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. +You need 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 index c8a4ad9a..1d0cb2b6 100644 --- 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,12 @@ 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. -## Managed Vhosts -Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain. +## Create a Vhost for a (Sub)Domain -## Create a Managed_vhost for a (Sub)Domain +Ensure you have a vhost for your Akeneo domain. -If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. +If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. ```bash hypernode-manage-vhosts akeneo.example.hypernode.io --type akeneo --https --force-https 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 index 0117fa67..78f3617a 100644 --- 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,11 @@ 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. -## Managed Vhosts +## Create a Vhost for a (Sub)Domain -Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain. +Ensure you have a vhost for your Akeneo domain. -## Create a Managed_vhost for a (Sub)Domain - -If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. +If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. ```bash hypernode-manage-vhosts akeneo.example.hypernode.io --type akeneo4 --https --force-https 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 index 20b6c6e8..e6833124 100644 --- 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,11 @@ 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. -## Managed Vhosts +## Create a Vhost for a (Sub)Domain -Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain. +Ensure you have a vhost for your Akeneo domain. -## Create a Managed_vhost for a (Sub)Domain - -If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. +If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. ```bash hypernode-manage-vhosts akeneo.example.hypernode.io --type akeneo4 --https --force-https 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 index 59ed60e4..07416905 100644 --- 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,11 @@ 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. -## Managed Vhosts +## Create a Vhost for a (Sub)Domain -Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain. +Ensure you have a vhost for your Akeneo domain. -## Create a Managed_vhost for a (Sub)Domain - -If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. +If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. ```bash hypernode-manage-vhosts akeneo.example.hypernode.io --type generic-php --https --force-https --webroot /data/web/akeneo/public 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 index f4918d18..3a5adc47 100644 --- 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,11 @@ 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.** -## Managed Vhosts +## Create a Vhost for a (Sub)Domain -Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain. +Ensure you have a vhost for your Akeneo domain. -## Create a Managed_vhost for a (Sub)Domain - -If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. +If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS. ```bash hypernode-manage-vhosts akeneo.example.hypernode.io --type generic-php --https --force-https --webroot /data/web/akeneo/public diff --git a/docs/ecommerce-applications/akeneo/how-to-use-a-basic-staging-environment-with-akeneo-3.md b/docs/ecommerce-applications/akeneo/how-to-use-a-basic-staging-environment-with-akeneo-3.md index 04ecb17c..4b57e7ea 100644 --- a/docs/ecommerce-applications/akeneo/how-to-use-a-basic-staging-environment-with-akeneo-3.md +++ b/docs/ecommerce-applications/akeneo/how-to-use-a-basic-staging-environment-with-akeneo-3.md @@ -14,9 +14,9 @@ redirect_from: Hypernode offers a staging environment so it can be used as a sandbox for your Akeneo PIM project. Please keep in mind that your staging environment for Akeneo shares resources (disk, CPU, memory) with your production environment. It’s also possible to order a [development plan](../../hypernode-platform/tools/how-to-use-hypernode-development-plans.md) instead, so your production environment will not be affected. Once again a big thank you to our partner [Experius](https://www.experius.nl/) for contributing to this article! -## Update managed_vhosts +## Update Vhosts -Update the current managed_vhost with staging port. +Update the current vhost with staging port. ```bash hypernode-manage-vhosts akeneo.example.hypernode.io --port-http-staging 8888 --port-https-staging 8443 --force-https --https diff --git a/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md b/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md index 1d49c483..1ec716c6 100644 --- a/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md +++ b/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md @@ -41,7 +41,7 @@ $ hypernode-systemctl settings varnish_enabled True ## Configure Varnish on the Vhost -Since the introduction of [hypernode-manage-vhosts](https://changelog.hypernode.com/changelog/release-7166-hypernode-manage-vhosts-enabled-by-default/) Hypernode may work somewhat different than you might be used to. With HMV enabled, it requires one more step to configure Varnish for your shop/vhost. Remember, for each domain, there should be a vhost created. You can list an overview of all configured vhosts with `hypernode-manage-vhosts --list`. While you do that, note that there is a column, "varnish". By default this is set to "False". Which means that Varnish isn't configured for this vhost. You can configure Varnish for the vhost by running the following command: +The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) command requires one additional step to configure Varnish for your shop/vhost. Remember, for each domain, there should be a vhost created. You can list an overview of all configured vhosts with `hypernode-manage-vhosts --list`. While you do that, note that there is a column, "varnish". By default this is set to "False". Which means that Varnish isn't configured for this vhost. You can configure Varnish for the vhost by running the following command: ```console $ hypernode-manage-vhosts EXAMPLE.COM --varnish diff --git a/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md b/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md index 0f7da801..3bbfc9bf 100644 --- a/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md +++ b/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md @@ -25,7 +25,7 @@ Varnish can be enabled with a simple command using the [hypernode-systemctl CLI] ## Step Two: Enable Varnish for NGINX Vhost -The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts) (HMV) config allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts: +The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) command allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts: - example.com - [www.example.com](http://www.example.com) diff --git a/docs/ecommerce-applications/shopware-5/how-to-host-shopware-on-hypernode.md b/docs/ecommerce-applications/shopware-5/how-to-host-shopware-on-hypernode.md index 8b19d089..ffc48248 100644 --- a/docs/ecommerce-applications/shopware-5/how-to-host-shopware-on-hypernode.md +++ b/docs/ecommerce-applications/shopware-5/how-to-host-shopware-on-hypernode.md @@ -28,7 +28,7 @@ Shopware is an e-commerce system roughly the same as Magento and both have the s ## Configuring Hypernode for Shopware -All you need to do is create a [vhost](../../hypernode-platform/nginx/hypernode-managed-vhosts.md#managing-vhosts) (or change an existing vhost) with type `shopware5` or `shopware6`. +All you need to do is create a vhost (or change an existing vhost) with type `shopware5` or `shopware6`. This will make sure the specific vhost has the right nginx configuration to host your Shopware environment. So for example, your domain is `www.example.com` and you'd like a vhost with Shopware 6 configuration. You can create this vhost with the following command: `hypernode-manage-vhosts www.example.com --type shopware6 --https --force-https`. diff --git a/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md b/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md index f81ccfa1..34e9e6f2 100644 --- a/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md +++ b/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md @@ -25,7 +25,7 @@ You can enable varnish on the hypernode using the [systemctl-tool](../../hyperno ## Step Two: How to Setup Varnish for the Vhost -The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) (HMV) config allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts: +The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) command allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts: - example.com - [www.example.com](http://www.example.com) 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 index 70e7633d..b7a32a01 100644 --- 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 @@ -69,9 +69,9 @@ In our support documentation you will find detailed information about installing - [Shopware 5](../../ecommerce-applications/shopware-5/how-to-install-shopware-5-on-hypernode.md) - [Shopware 6](../../ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode.md) -### Step 4 – Set up Hypernode Managed Vhosts +### Step 4 – Set up Your Vhosts -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. +You need 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/cluster.md b/docs/hypernode-platform/cluster.md index 698d95de..20b38c61 100644 --- a/docs/hypernode-platform/cluster.md +++ b/docs/hypernode-platform/cluster.md @@ -91,7 +91,7 @@ To add custom NGINX rules for handling specific things on the loadbalancer (like used in `/data/web/nginx` and `/data/web/nginx/`. This can be very crucial for your performance, accelerating asset delivery and lowering pressure on varnish. -When running `hypernode-manage-vhosts` ([docs](nginx/hypernode-managed-vhosts.md)) on a loadbalancer server for a specific vhost, a +When running [hypernode-manage-vhosts](nginx/hypernode-managed-vhosts.md) on a loadbalancer server for a specific vhost, a preconfigured loadbalancer configuration file will be created for you (for example `/data/web/nginx/example.com/loadbalancer.magento2.conf`). These preconfigured files act as a good starting point for your loadbalancer setup, but can be customized to your needs. diff --git a/docs/hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md b/docs/hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md index b4228889..7ea19b82 100644 --- a/docs/hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md +++ b/docs/hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md @@ -133,4 +133,3 @@ map $http_user_agent $development_exceptions { ## Troubleshooting - Google Pagespeed analysis uses the Google bot user agent and can therefore not be used on development nodes. -- In some cases, particularly if you have not yet enabled [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md), it’s possible the Basic Authentication blocks the Let’s Encrypt validation server. If you wish to make use of Let’s Encrypt on your development Hypernode, you should add the ‘letsencrypt’ user agent to the whitelist file. diff --git a/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md b/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md index e8637cfc..627ac96d 100644 --- a/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md +++ b/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md @@ -26,7 +26,7 @@ There are multiple ways to set up your Magento multistore. You can choose betwee - Using subdirectories (e.g. example.com/en/ and example.com/fr/ etc.) - Using a combination of different domains and subdirectories (e.g. example.com and example.net/en/ and example.net/fr/) -Below we have provided the instructions on how to set up each of the scenarios within Nginx on your Hypernode. Please do note that in order to follow the instructions your Hypernode must have [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) enabled. Furthermore, we cannot guarantee that the instructions will work with all plugins and custom configurations since this has only been tested with the default Luma theme and without any customizations. +Below we have provided the instructions on how to set up each of the scenarios within Nginx on your Hypernode. Furthermore, we cannot guarantee that the instructions will work with all plugins and custom configurations since this has only been tested with the default Luma theme and without any customizations. ### Using Different Domains @@ -144,7 +144,7 @@ Magento Stores - Base URLs +----+---------+------------------------------------+--------------------+ ``` -First add the following vhosts using the information from the [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) documentation. +First add the following vhosts using the information from the [vhost configuration](hypernode-managed-vhosts.md) documentation. - [www.example.com](http://www.example.com) - [www.example.nl](http://www.example.nl) 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 index 0f7f094a..e7c89580 100644 --- 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 @@ -18,14 +18,12 @@ Many constructions are possible when it gets to the base URL. Some shop owners p There are some restrictions when choosing your base URL. -If you use the wwwizer servers, which are sometimes used when your domain is not hosted at Hypernode and thus the DNS can’t be automagically changed in case of up or downgrades, your domain will always redirect to [www](http://www). +If you use the wwwizer servers, which are sometimes used when your domain is not hosted at Hypernode and thus the DNS can’t be automagically changed in case of up or downgrades, your domain will always redirect to www. More info can be found [on our page about setting your DNS](../dns/how-to-manage-your-dns-settings-for-hypernode.md). ## Redirect From Apex to WWW -**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`. ```text diff --git a/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md b/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md index 04558761..54085fa3 100644 --- a/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md +++ b/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md @@ -121,7 +121,7 @@ Besides the above-known plugins that will hit the blacklisted keyword, `http.rat To prevent a single IP from using all the FPM workers available simultaneously, leaving no workers available for other visitors, we implemented a per IP rate limit mechanism. This mechanism sets a maximum amount of PHP-FPM workers that can be used by one IP to 20. This way, one single IP address cannot deplete all the available FPM workers, leaving other visitors with an error page or a non-responding site. -**Please note:** if [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) is enabled, only add the `http.ratelimit` file in the Nginx root. Don't add it to the specific vhost as well, as this may cause conflicts. +**Please note:** only add the `http.ratelimit` file in the Nginx root. Don't add it to the specific vhost as well, as this may cause conflicts. ### How per‑IP limiting works (what you can influence) diff --git a/docs/hypernode-platform/nginx/hypernode-managed-vhosts.md b/docs/hypernode-platform/nginx/hypernode-managed-vhosts.md index b162afc0..bc798707 100644 --- a/docs/hypernode-platform/nginx/hypernode-managed-vhosts.md +++ b/docs/hypernode-platform/nginx/hypernode-managed-vhosts.md @@ -1,7 +1,7 @@ --- myst: html_meta: - description: Learn all about The Hypernode Managed Vhosts (HMV). The system is + description: Learn all about the Hypernode Managed Vhosts (HMV). The system is an easy to use, yet powerful, system of configuring Nginx on Hypernode. title: How to enable and manage Hypernode Vhosts? redirect_from: @@ -14,11 +14,11 @@ redirect_from: The Hypernode Managed Vhosts (HMV) system is an easy to use, yet powerful, system of configuring Nginx on Hypernode. A vhost is a configuration that allows you to setup multiple domainnames, each with it's own, independent, configuration. With it, you can easily host a Wordpress blog on a subdomain, and a Magento on your main domain, set up HTTPS for both automatically, and efficiently redirect visitors to your www-domain. -The main advantage of HMV is that it separates your Nginx config into a global folder, containing configuration for all server blocks, and domain specific configs, giving you more control and reducing unexpected side-effects of domain specific configurations. +The main advantage of vhosts is that it separates your Nginx config into a global folder, containing configuration for all server blocks, and domain specific configs, giving you more control and reducing unexpected side-effects of domain specific configurations. ## Managing Vhosts -Once the Hypernode Managed Vhosts (HMV) system is enabled, you can start defining and configuring your vhosts. On new booted Hypernodes there will be one vhosts by default: example.hypernode.io. +You can start defining and configuring your vhosts. On new booted Hypernodes there will be one vhost by default: example.hypernode.io. ### Adding Vhosts @@ -58,27 +58,27 @@ Please take not that the webroot option is not used for the built-in staging for ## Let’s Encrypt and Hypernode Managed Vhosts -**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!** +**Please note: If you want to use Let's Encrypt, you need to configure it during the creation of the vhost. Using the old method with *dehydrated* won't work!** -If you want to request a LE certificate you need to add the `--https` flag with the HMV-command. +If you want to request a LE certificate you need to add the `--https` flag with the 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. -## Varnish and Hypernode Managed Vhosts +## Varnish Configuration -Using Varnish works slightly differently with HMV enabled. Of course Varnish needs to be enabled with the **systemctl** tool. `hypernode-systemctl settings varnish_enabled True` +Using Varnish works with vhosts. Of course Varnish needs to be enabled with the **systemctl** tool. `hypernode-systemctl settings varnish_enabled True` -But with HMV you need to configure the vhost for Varnish as well. You can do this by adding the `--varnish`flag to you HMV-command. For example: `hypernode-manage-vhosts example.com --varnish` +You need to configure the vhost for Varnish as well. You can do this by adding the `--varnish`flag to your command. For example: `hypernode-manage-vhosts example.com --varnish` Once the command is processed you could list all the vhosts to check if Varnish is enabled for that vhost. The value in the Varnish column should be set to **True**. To disable Varnish for a vhost, use the following command: `hypernode-manage-vhosts example.com --disable-varnish` -## Object Storage and Hypernode Managed Vhosts +## Object Storage Configuration -If you're using object storage with Magento 2.x or Shopware 6.x you can use HMV to adjust your nginx config to serve assets directly from your bucket. +If you're using object storage with Magento 2.x or Shopware 6.x you can adjust your nginx config to serve assets directly from your bucket. If you're using Hypernode's object storage solution, simply run the following command for the relevant vhosts: @@ -111,7 +111,7 @@ Please note that any files with the 'HTTP.' prefix will also be loaded in the HT ### Global configuration -Even when using the Hypernode Managed Vhosts (HMV) system, it's still possible to setup configuration on the 'global' level by placing a file in `/data/web/nginx`. +It's possible to setup configuration on the 'global' level by placing a file in `/data/web/nginx`. ### Multi-domain configuration @@ -119,8 +119,8 @@ If you have multiple vhosts, and want to share configuration between them, witho ## Troubleshooting -If you are running into issues (e.g. SSL or other configuration errors) with Hypernode Managed Vhosts, we recommend running this command first: +If you are running into issues (e.g. SSL or other configuration errors), we recommend running this command first: `hypernode-manage-vhosts --all` -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. +This regenerates the configuration based on what is set in `hypernode-manage-vhosts --list` and in our experience resolves most basic issues. diff --git a/docs/hypernode-platform/php/how-to-resolve-502-gateway-errors.md b/docs/hypernode-platform/php/how-to-resolve-502-gateway-errors.md index 8f1cdb4d..c3463702 100644 --- a/docs/hypernode-platform/php/how-to-resolve-502-gateway-errors.md +++ b/docs/hypernode-platform/php/how-to-resolve-502-gateway-errors.md @@ -73,7 +73,7 @@ You could experience a 502 error due to a misconfiguration of Varnish. For examp - Have you configured Varnish caching in the backend? Check if Varnish is enabled on the Hypernode: `hypernode-systemctl settings varnish_enabled` this should return `true`. If not, enable Varnish: `hypernode-systemctl settings varnish_enabled true` -- Is [HMV](../nginx/hypernode-managed-vhosts.md) enabled? Check if Varnish is enabled for the vhost: +- Check if Varnish is enabled for the vhost: `hypernode-manage-vhosts --all` If not, enable Varnish for the vhost:`hypernode-manage-vhosts example.com --varnish` - Or if you've just disabled Varnish in the backend, make sure to disable Varnish for the vhosts as well: 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 index 483622cd..5aa36910 100644 --- 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 @@ -30,12 +30,12 @@ See their website for more information about how to use [Let's Encrypt](https:// ## Let’s Encrypt and Hypernode Managed Vhosts -**Please note:** The [Hypernode Managed Vhosts (HMV)](../nginx/hypernode-managed-vhosts.md) system requires a vhost for every domain you want to use Let’s Encrypt on. +**Please note:** You need a vhost for every domain you want to use Let's Encrypt on. Then run this command to set up a vhost for the domain: `hypernode-manage-vhosts www.example.com --https --force-https` This command redirects everything for the domain from http to https and installs a Let’s Encrypt certificate. -**Note**: If you use Let's Encrypt with HMV, the cron for the renewal of the certificates will be placed automatically in the crontab, you don't have to do anything manually! +**Note**: If you use Let's Encrypt for vhosts, the cron for the renewal of the certificates will be placed automatically in the crontab, you don't have to do anything manually! ### Adding an Third Party Certificate When Let’s Encrypt Is Configured diff --git a/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md b/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md index c64dbca1..55777e2a 100644 --- a/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md +++ b/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md @@ -39,9 +39,9 @@ ssh app@appname.hypernode.io -L 8025:localhost:8025 This will forward `localhost:8025` (where MailHog is running) to our local `8025` port. Now going to `localhost:8025` in a browser will show the MailHog mailbox with all the mails it catches from the Hypernode. -## Access MailHog with HMV and Basic Authentication +## Access MailHog with Basic Authentication -If HMV ([Hypernode Managed Vhosts](../nginx/hypernode-managed-vhosts.md)) is enabled on your Hypernode, you can easily create a vhost for MailHog by using the command below which also enables Basic Authentication. +You can create a vhost for MailHog by using the command below which also enables Basic Authentication. ```bash hypernode-manage-vhosts mailhog.example.hypernode.io --https --force-https --type mailhog diff --git a/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md b/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md index 0fba1209..fb1e53c0 100644 --- a/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md +++ b/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md @@ -32,7 +32,6 @@ To see which values you can set and which values they are allowed to have take a | **firewall_block_ftp_enabled**
Indicates whether FTP (which is unsafe) is completely blocked or not | False | True, False | | **magerun2_version**
Change the N98 Magerun version | latest | 3.x, 4.x, 5.x, 6.x, 7.x, latest | | **mailhog_enabled**
Enable the Mailhog feature | False | True, False | -| **managed_vhosts_enabled**
Enable the managed_vhosts nginx configuration | True | True, False | | **modern_ssh_config_enabled**
Enable modern SSH configuration | False | True, False | | **modern_ssl_config_enabled**
Safer SSL and SSH configuration:
you can configure Mozilla Modern SSL and enable
stricter SSH encryption | False | True, False | | **mysql_disable_stopwords**
Disable MySQL stopwords | False | True, False | @@ -125,10 +124,6 @@ Indicates whether FTP is completely blocked or not in favour of SFTP. For more i This options enables Mailhog. Mailhog is an email testing tool for developers. Check our [documentation](../../hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md) for a more detailed explanation about Mailhog on Hypernode. -### Managed Vhosts - -Eanble the Hypernode Managed Vhosts option to setup the Hypernode with a specific Nginx config which allows you to setup multiple domain names with their own independent Nginx configuration. See our [documentation](../nginx/hypernode-managed-vhosts.md) for more information. - ### Modern SSH config enabled Indicates whether this node will have a stricter set of SSH encryption algorithms enabled. See [this changelog](https://changelog.hypernode.com/release-5139-stricter-ssh-encryption-algorithms/) for more information about this setting. From cc58ed7ad669af17201faf5ff0a2f0bc5dd1a91a Mon Sep 17 00:00:00 2001 From: Jonathan Visser Date: Fri, 21 Nov 2025 15:21:23 +0100 Subject: [PATCH 2/2] Run formatting on how-to-install-akeneo-3-on-hypernode.md --- .../akeneo/how-to-install-akeneo-3-on-hypernode.md | 1 - 1 file changed, 1 deletion(-) 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 index 1d0cb2b6..27ca0f45 100644 --- 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,7 +14,6 @@ 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. - ## Create a Vhost for a (Sub)Domain Ensure you have a vhost for your Akeneo domain.