Merge branch 'master' into feature/uv-support

Author: poespas

docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md

@@ -0,0 +1,43 @@
+______________________________________________________________________
+
+myst:
+html_meta:
+description: 'Find out here how to order a domain.'
+redirect_from:
+
+- /en/getting-started/how-to-order/how-to-order-a-domain-presence-plan/
+- /getting-started/how-to-order/how-to-order-a-domain-presence-plan.html
+
+______________________________________________________________________
+
+<!-- source: https://support.hypernode.com/en/getting-started/how-to-order/how-to-order-a-domain-presence-plan/ -->
+
+# How to Order a Domain
+
+To order a domain you will need a Hypernode as the domain needs to be linked to it during the ordering process.
+
+## How to Order
+
+To order a domain, please follow the steps below:
+
+1. Log into the [Hypernode control panel](https://my.hypernode.com/domain/)
+1. Go to the 'Domains' tab and press Order domain
+1. Enter the domain name that you want to register with/transfer to Hypernode.
+1. When you want to transfer a domain, our ordering system will recognize you want to order an existing domain and will ask you if you want to transfer the domain or only manage the DNS. These steps will not initiate a transfer right away. If you want to transfer the domain to Hypernode you can choose the option 'Transfer to Hypernode'.
+1. Make a selection of the Hypernode it needs to link to.
+1. Select the Legal owner or fill in the information.
+1. After completing your order you can either transfer your domain with the authorisation token or manage the DNS after providing the domain registrar with the new nameservers.
+
+## FAQ
+
+**What extensions do you offer?**
+
+A complete list of extensions we offer can be found [here](../../services/domain-procedures/which-tlds-does-hypernode-offer.md).
+
+**How can I transfer my domain?**
+
+You can read a detailed description of the step-by-step plan [here](../../services/domain-procedures/how-to-use-domains-in-the-control-panel.md#transfer-an-existing-domain-to-hypernode).
+
+**How can I order an SSL certificate?**
+
+You can read a detailed description of the step-by-step plan [here](../../hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#buy-an-ssl-certificate-via-hypernode-recommended).

docs/getting-started/how-to-order/how-to-order-a-domain.md

@@ -20,7 +20,13 @@ More information about DNS settings for your webshop on Hypernode technology, fo
 
 ## Manage DNS With a Third Party
 
-Please note that Hypernode cannot provide uptime guarantees for external DNS. Your SLA does not apply in this case. When a domain name is registered externally, please keep in mind that Hypernode has no influence on the functioning of the DNS. If you don't want to transfer your domain name to Hypernode, changing the name servers to the Byte name servers is a good second option. You will need a Presence plan to be able to manage your DNS from the Service Panel. When you have the DNS set up correctly you can ask your domain name provider to change the name servers to the Byte name servers:
+Please note that Hypernode cannot provide uptime guarantees for external DNS, so your SLA does not apply in this case.
+
+If your domain name is registered with an external provider, please be aware that Hypernode has no control over the availability or functioning of that provider’s DNS services.
+
+If you prefer not to transfer your domain name to Hypernode, a good alternative is to update your domain’s nameservers to the Hypernode nameservers. To manage your DNS through the Service Panel, you will need a Presence plan.
+
+Once your DNS has been configured correctly, you can ask your domain provider to update the nameservers to the Hypernode nameservers:
 
 ns1.hypernode.com
 
@@ -94,11 +100,11 @@ Different DNS records have been created for the different types of internet traf
 
 The NS records contain the "authoritative name servers" or prevailing name servers. When your domain name is listed with Hypernode, these will always be on Byte's name servers by default. This determines that we are the party that manages the DNS records. You can also find them in the WHOIS. The Byte name servers are:
 
-nsa.byte.nl
+ns1.hypernode.com
 
-nsb.byte.nl
+ns2.hypernode.com
 
-nsc.byte.nl
+ns3.hypernode.com
 
 If you have set up other name servers, the DNS data will be downloaded from that server. Hypernode always recommends using the Byte name servers so that in the event of IP changes (if you switch from datacenter) we can switch quickly, without having to make changes to the DNS configuration. You can NOT change the name servers from the Service Panel. If you need to change the name servers (to for example Cloudflare) you can request this by sending an email to [support@hypernode.com](mailto:support@hypernode.com) (from the email address that is linked to the account).
 
@@ -114,13 +120,19 @@ This is the A record for IPv6 addresses.
 
 ### MX Records
 
-The MX records contain the host names of the mail server(s). In addition to the hostname, you can assign a priority to each MX record. For example, you can give your own mail servers a higher priority (a lower number) than our smtp2.byte.nl server. This means that smtp2.byte.nl is only used as a mail server when your own servers are not available. We also call this "fallback server". Also make sure that you do not give every MX record a priority of 10, otherwise our server will not be able to determine which record is about the primary mail server. These are the MX records of the Hypernode mail servers:
+MX records determine where email for your domain should be delivered. The value of an MX record must point to the mail server that handles incoming email for your domain. Each MX record also includes a priority: the lower the number, the higher the priority.
+
+If you use multiple mail servers, the server with the lowest priority number is treated as the primary server. A second server can be configured as a fallback by giving it a higher priority number.
+
+Make sure not all MX records use the same priority. If they do, sending servers may distribute delivery across them instead of treating one as the primary server.
+
+Example MX configuration:
 
-|             |          |               |          |
-| ----------- | -------- | ------------- | -------- |
-| **Name**    | **Type** | **Value**     | **Prio** |
-| example.com | MX       | smtp1.byte.nl | 10       |
-| example.com | MX       | smtp2.byte.nl | 20       |
+|             |          |                   |          |
+| ----------- | -------- | ----------------- | -------- |
+| **Name**    | **Type** | **Value**         | **Prio** |
+| example.com | MX       | smtp1.example.com | 10       |
+| example.com | MX       | smtp2.example.com | 20       |
 
 Always use your primary domain for your MX records. An MX record with the Name on “mail.example.nl” will only work for …@mail.example.nl addresses.
 

docs/hypernode-platform/dns/dns-for-control-panel-users.md

@@ -151,7 +151,7 @@ If you want to connect to FTP you’ll have to use the following credentials:
 - Password: **Your password**
 - Port:
   - **21** For regular FTP
-  - **2222** For SFTP (you need to opt-in first!)
+  - **2222** For SFTP
 
 ## ACTIVE Mode or PASSIVE Mode
 

docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md

@@ -132,5 +132,5 @@ 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.
+- To allow Google Pagespeed analysis in development hypernodes you can whitelist the following IPs https://www.gstatic.com/ipranges/goog.json. PSI uses different user agents than Google bot and will be able to perform analysis on your frontend without allowing crawling.
 - 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.

docs/hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md

@@ -37,9 +37,9 @@ set $storecode "example_storecode";
 ```
 
 ```{important}
-If you have a multistore, with hypernode-manage-vhost enabled AND you are using Varnish.
-You'd have to prefix the file with `varnish` instead of `server`, like `varnish.storecode`.
-This way these multistore requests will go through varnish and will then be rewritten accordingly with the `varnish.storecode` configuration.
+If you have a multistore with `hypernode-manage-vhost` enabled **and** you are using Varnish, you need to prefix the file with `varnish` instead of `server`, like `varnish.storecode`. This way multistore requests will go through Varnish and be rewritten accordingly using the `varnish.storecode` configuration.
+
+This does **not** apply if your Hypernode is running behind a load balancer (e.g. a cluster setup). In that case, you should keep using `server.storecode` instead.
 ```
 
 ### Use a different Store Type

docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md

@@ -74,3 +74,7 @@ Composer version 2.2.18 2022-08-20 11:33:38
 ```
 
 So if you want to use Composer 2 you only need to run `composer2` instead of `composer`.
+
+## Update Composer to a Newer Version
+
+You can update Composer to a newer version using the [hypernode-systemctl CLI tool](how-to-use-the-hypernode-systemctl-cli-tool.md).