ByteInternet · tdgroot · Mar 18, 2025 · Mar 17, 2025 · Mar 17, 2025 · Mar 17, 2025
diff --git a/README.md b/README.md
@@ -2,14 +2,14 @@
 
 ## Generating new docs
 
-``` bash
+```bash
 DOC_URL=https://support.hypernode.com/en/ecommerce/magento-1/how-to-enable-mysql-query-logging-for-magento-1-x
 bin/download_doc --output-dir=docs/ecommerce-applications $DOC_URL
 ```
 
 ## Setting up the project
 
-``` bash
+```bash
 mkvirtualenv hypernode-docs-next
 echo "export PYTHONPATH=$(pwd)" >> $VIRTUAL_ENV/bin/postactivate
 workon hypernode-docs-next
@@ -19,33 +19,38 @@ pre-commit install
 
 ## Building the docs
 
-``` bash
+```bash
 bin/build_docs
 ```
 
 ## Serving the docs
 
-``` bash
+```bash
 bin/serve_docs
 ```
+
 ## Setup Frontend step by step
+
 ```
 clone the repository
 pip install -r requirements/development.txt
 bin/build_docs
 bin/serve_docs
 ```
+
 in another terminal run
-``` bin/watch ```
+`bin/watch`
 
 open localhost and now you can make changes in style and refresh the page without rebuilding
 
 when you're working on scss to compile it automatically run
+
 ```
 npx sass --watch docs/_static/scss:docs/_static/css
 ```
 
 or as a production build:
+
 ```
 npx sass --style compressed --no-source-map docs/_static/scss:docs/_static/css
 ```
@@ -57,6 +62,7 @@ Deploys automatically after merging branchers to master.
 ### Deploy with Hypernode Deploy
 
 To deploy to a local Hypernode Docker environment:
+
 ```
 $ docker pull docker.hypernode.com/byteinternet/hypernode-buster-docker:latest
 $ docker run docker.hypernode.com/byteinternet/hypernode-buster-docker:latest
@@ -66,6 +72,7 @@ $ # Note the IP address, it should be 172.17.0.2 (otherwise refer to deploy.php)
 Next make sure your `~/.ssh/yourdeploykey` equivalent can log in to the Docker host (172.17.0.2) as the app user. You can add it to the `/data/web/.ssh/authorized_keys` file on in the instance manually.
 
 Then deploy to your local Hypernode Docker:
+
 ```
 docker run --rm -it --env SSH_PRIVATE_KEY="$(cat ~/.ssh/yourdeploykey | base64)" -v ${PWD}:/build quay.io/hypernode/deploy:latest hypernode-deploy build -vvv  # First build the artifact
 docker run --rm -it --env SSH_PRIVATE_KEY="$(cat ~/.ssh/yourdeploykey | base64)" -v ${PWD}:/build quay.io/hypernode/deploy:latest hypernode-deploy deploy docker -vvv  # Then perform the deploy
@@ -74,6 +81,7 @@ docker run --rm -it --env SSH_PRIVATE_KEY="$(cat ~/.ssh/yourdeploykey | base64)"
 ## Building the manpage deb
 
 The docs are also packaged as a debian package named `hndocsnext` so that on a Hypernode you can run `man hypernode` (or `hypernode-manual`) and page through a `manpage` version of the Hypernode docs. To build that debian package on a Debian machine you can run these commands:
+
 ```
 # First create the cow environment
 export ARCH=amd64
@@ -91,16 +99,19 @@ gbp buildpackage --git-pbuilder --git-dist=$DIST --git-arch=$ARCH --git-ignore-b
 ```
 
 Then after building the Deb you could install it with dpkg. For example:
+
 ```
 dpkg -i ../hndocsnext_20230121.173551_all.deb
 ```
 
 And test it out with:
+
 ```
 man hypernode
 ```
 
 To inspect the contents of the deb archive you can run:
+
 ```
 # dpkg -L hndocsnext
 /.

diff --git a/docs/about-hypernode/billing/how-to-choose-and-order-a-hypernode-plan.md b/docs/about-hypernode/billing/how-to-choose-and-order-a-hypernode-plan.md
@@ -68,8 +68,6 @@ DigitalOcean and Amazon both have data centers all over the world.
 
 You can order a Hypernode plan via our [order page](https://www.hypernode.com/magento-cloud-hosting/#plans). The Control Panel is our default panel, which means all new Hypernode plans and trials will be booted in the Control Panel.
 
-**Please note:** if you are a Service Panel user (i.e. you use the Dutch panel), please order your new plans directly via [this page in the Service Panel](https://service.byte.nl/planinfo/order-selection/). This is to prevent plans from being booted in the wrong system.
-
 ## Tips For Ordering a Hypernode
 
 - Choose a logical name. IE: If your site is example.com, order example.hypernode.com

diff --git a/docs/about-hypernode/security-policies/security-hall-of-fame.md b/docs/about-hypernode/security-policies/security-hall-of-fame.md
@@ -29,7 +29,7 @@ We would like to thank the following individuals and/or organizations, who have
 | [Pethuraj M](https://www.pethuraj.com/)                                                                                                                                                                 | 1 July 2020       | Reported a flaw in our password reset flow                                                             |
 | [Miguel Santareno](https://www.linkedin.com/in/miguelsantareno/)                                                                                                                                        | 14 May 2020       | Reported information leakage from marketing sites.                                                     |
 | [Gaurav Kumar](https://www.facebook.com/drago4344) and [Shivam Dattana](https://www.facebook.com/profile.php?id=100010397858328) / [Team Bugmania](https://www.openbugbounty.org/researchers/bugmania/) | 28 September 2019 | Reported a Cross site scripting (XSS) on magereport.com.                                               |
-| [Mike de Landgraaf](https://www.linkedin.com/in/mdelandgraaf/) / [MDL Online](https://mdlonline.com/)                                                                                                   | 21 March 2019     | Reported a misconfiguration that allowed user impersonation on Hypernode hosted webshops.              |
+| [Mike de Landgraaf](https://www.linkedin.com/in/mdelandgraaf/) / MDL Online                                                                                                                             | 21 March 2019     | Reported a misconfiguration that allowed user impersonation on Hypernode hosted webshops.              |
 | [Maksym Bendeberia](https://www.linkedin.com/in/jogspokoen/) / [WebSafety Ninja](https://websafety.ninja/)                                                                                              | 12 March 2019     | Reported information leakage from an internal deployment server.                                       |
 | [Jan Piet van Dijk](https://www.linkedin.com/in/janpietvandijk/) / [Interwijs B.V.](https://www.interwijs.nl/)                                                                                          | 28 August 2018    | Reported a privilege escalation on Hypernode, leading to a local root exploit.                         |
 | [Wijnand Wieskamp](https://www.linkedin.com/in/wijnand-wieskamp-8a784313/) / [Crystalsoft B.V.](https://www.crystalsoft.nl/)                                                                            | 1 June 2018       | Reported a misconfiguration that allowed a Hypernode’s preconfigured security settings to be bypassed. |
diff --git a/docs/about-hypernode/support/how-to-handle-os-and-room-change-upgrade.md b/docs/about-hypernode/support/how-to-handle-os-and-room-change-upgrade.md
diff --git a/docs/best-practices/performance/how-to-improve-your-magento-search.md b/docs/best-practices/performance/how-to-improve-your-magento-search.md
@@ -34,7 +34,6 @@ Please note that due to the relatively heavy resource requirements for ElasticSe
 If you are on a lower plan, you’ll need to either upgrade, or make use of an external search provider. There a several companies you can choose for a monthly subscription:
 
 - [Bonsai.io](https://bonsai.io/)
-- [Qbox.io](https://qbox.io/)
 - [Elastic.co](https://www.elastic.co/cloud/as-a-service)
 
 **If you choose Bonsai, we have made a special deal with Bonsai. Please send a mail to [email protected] for a discount code.**

diff --git a/docs/best-practices/performance/how-to-optimize-your-images.md b/docs/best-practices/performance/how-to-optimize-your-images.md
@@ -15,7 +15,7 @@ redirect_from:
 
 If you want a faster shop, you have probably looked at [Google Pagespeed Insights](https://developers.google.com/speed/pagespeed/insights/) for useful suggestions. It probably told you to optimize your images. Which means, reducing the size-on-disk without losing quality. This is a very cumbersome process if you do this by hand (opening in Photoshop, saving-as, etcetera). But it is very easy if you use Hypernode. If you follow this article, **it will take you only a couple of minutes to set up automatic image optimization**.
 
-Thanks to Peter Jaap for doing the [initial research](https://www.byte.nl/blog/afbeeldingen-optimaliseren-magento-bespaart-veel-webruimte/) (in Dutch).
+Thanks to Peter Jaap for doing the initial research.
 
 > [@Hypernode_com](https://twitter.com/Hypernode_com) hypernode-image-optimizer is pretty effective "Optimization profit over all files: 502812 KB (82%)". Thanks for that!
 >

diff --git a/docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md b/docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md
@@ -26,7 +26,7 @@ With this relatively new way of hacking, malware is added in the browser of your
 
 In 2015 we analyzed the malware and found out that a staggering amount of 3500 Magento shops are part of a zombie network that interfere credit card credentials, and send this data to so called command&control servers. (Command&control servers are a network of servers where hackers collect this sort of data). This was the first time we encountered an automated credit card fraud on this scale. It’s obvious hackers have massively improved in becoming more professional in automating large-scale credit card fraud.
 
-[Read more about Credit card Hijack](https://www.byte.nl/blog/widespread-credit-card-hijacking-discovered)
+[Read more about Credit card Hijack](../../best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md#what-is-credit-card-hijack)
 
 We suspect this leak has been made possible due to unpatched Magento shops. So if you haven’t completely patched your Magento shop yet, make sure you do. Use Magereport.com to check if there are any patches not yet installed.
 

diff --git a/docs/best-practices/testing/hypernode-docker.md b/docs/best-practices/testing/hypernode-docker.md
@@ -13,8 +13,6 @@ redirect_from:
 
 The official Hypernode Docker image for Magento development is now available. This image can be used to set up a fast and easy local development environment for Hypernode, or as a build machine in a CI environment representative of the production environment. The image contains the exact same packages and configuration as a real Hypernode except for some Docker specific tweaks. By testing and developing against this image you can be sure that when you deploy to a Hypernode in production there will be no surprises because of different software versions or configurations.
 
-Interested in a case study? Read [this article](https://blog.guapa.nl/local-development-with-the-hypernode-docker-container-linux/) about the Hypernode docker of one of our partners!
-
 ## About the Hypernode Docker Image
 
 We build this image multiple times a day (every time we do a [release](https://changelog.hypernode.com/)) by applying our configuration management on the [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker) ["fat" container](https://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/). By treating the Docker as a lightweight VM instead of as a vehicle for a single process we stay close to what an actual Hypernode actually looks like. No micro-services or a multi-container application, but a single instance with minimal network overhead and all batteries included.

diff --git a/docs/best-practices/usage/hypernode-magerun.md b/docs/best-practices/usage/hypernode-magerun.md
@@ -72,7 +72,7 @@ Outputs or saves a http.magerunmaps boilerplate containing your store setup for
 n98-magerun hypernode:varnish:config-save
 ```
 
-Fetches the VCL configuration from turpentine and applies it. Make sure [turpentine is installed and configured](https://support.hypernode.com/knowledgebase/varnish-on-hypernode/) correctly.
+Fetches the VCL configuration from turpentine and applies it. Make sure [turpentine is installed and configured](../../ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md#configure-turpentine) correctly.
 
 ### Flush all URL's in Varnish cache
 
@@ -120,7 +120,7 @@ Building a .deb for release:
 ./build.sh
 ```
 
-Then if everything is alright, upload the new version to your repository with something like [dput](http://manpages.ubuntu.com/manpages/precise/man1/dput.1.html)
+Then if everything is alright, upload the new version to your repository with something like [dput](https://manpages.ubuntu.com/manpages/plucky/en/man1/dput.1.html)
 
 ## n98-magerun2 compatibility
 

diff --git a/docs/ecommerce-applications/magento-1/how-to-clean-the-magento-1-x-logs.md b/docs/ecommerce-applications/magento-1/how-to-clean-the-magento-1-x-logs.md
@@ -65,4 +65,4 @@ Scroll down to select ‘Empty’ from the dropdown ‘With selected’ and clic
 
 ## Turn Off Database Logging
 
-If you don’t need any database logging it can be worthwhile to disable all logging. To do so, install the [`disablelog extension by Yireo`](https://www.yireo.com/software/magento-extensions). For shops that are heavy on the database, this can help reduce the amount of update/insert queries and therefore reducing load times.
+If you don’t need any database logging it can be worthwhile to disable all logging. To do so, install the [`disablelog extension by Yireo`](https://github.com/yireo-magento1/Yireo_DisableLog). For shops that are heavy on the database, this can help reduce the amount of update/insert queries and therefore reducing load times.
diff --git a/...ecommerce-applications/magento-1/how-to-create-a-sitemap-xml-for-magento-1-x.md b/...ecommerce-applications/magento-1/how-to-create-a-sitemap-xml-for-magento-1-x.md
@@ -120,11 +120,3 @@ We've seen one or two special cases where creating a sitemap was extremely slow.
      <active>1</active>
  </connection>
 ```
-
-## Additional Links
-
-There is lots of information about setting up and pushing your sitemap to Google and other search indexes. See:
-
-- <http://alanstorm.com/generating_google_sitemaps_in_magento>
-- <http://www.aschroder.com/2010/01/sitemap-submit-magento-extension-to-submit-your-google-sitemap/>
-- <https://support.google.com/webmasters/answer/183669?hl=en&topic=8476&ctx=topic>
diff --git a/docs/ecommerce-applications/magento-1/how-to-install-magento-1-on-hypernode.md b/docs/ecommerce-applications/magento-1/how-to-install-magento-1-on-hypernode.md
@@ -14,7 +14,7 @@ redirect_from:
 
 Although Magento 1 has been End of Life since June 30 2020, it is still possible to host your Magento 1 store at Hypernode by using OpenMage. OpenMage is a free of charge fork of Magento 1, and allows store owners to continue the use of Magento 1 as a stable and secure eCommerce platform for the next years to come.
 
-OpenMage can be installed by using their [documentation](https://www.openmage.org/magento-lts/install.html). Don't implement OpenMage on production nodes without testing OpenMage first on a [Development plan](../../hypernode-platform/tools/how-to-use-hypernode-development-plans.md).
+OpenMage can be installed by using their [documentation](https://docs.openmage.org/users/install/use-composer/#configuration). Don't implement OpenMage on production nodes without testing OpenMage first on a [Development plan](../../hypernode-platform/tools/how-to-use-hypernode-development-plans.md).
 
 Would you rather install the officially supported Magento 2? Installing Magento 2 on Hypernode can be done by following the steps in the article: [Installing Magento 2 on Hypernode](../../ecommerce-applications/magento-2/how-to-install-magento-2-on-hypernode.md)
 

diff --git a/.../ecommerce-applications/magento-2/how-to-create-a-robots-txt-for-magento-2-x.md b/.../ecommerce-applications/magento-2/how-to-create-a-robots-txt-for-magento-2-x.md
@@ -118,5 +118,4 @@ Disallow: /
 ## Additional resources
 
 - <https://developers.google.com/s/results?q=control-crawl>
-- <https://support.google.com/webmasters/answer/6062596?hl=en>
 - <http://www.robotstxt.org/>
diff --git a/docs/ecommerce-applications/magento-2/how-to-enable-the-magento-2-api.md b/docs/ecommerce-applications/magento-2/how-to-enable-the-magento-2-api.md
@@ -13,7 +13,7 @@ redirect_from:
 
 # How to Enable the Magento 2 API
 
-To enable the Magento API, first [**create the correct users**](https://www.yireo.com/tutorials/magebridge/administration/596-step-by-step-create-a-magento-api-user).
+To enable the Magento API, first create the correct users.
 
 The Magento API is supposed to work out-of-the box on Hypernodes, but due to clean-url-rewrites sometimes the API does not work and returns a 404 error.
 To resolve this issue, some additional configuration is required.

diff --git a/docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md b/docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md
@@ -30,7 +30,8 @@ To order a domain at Hypernode you need a Presence plan. We offer two different
 
 To order one of these plans, please follow the steps below:
 
-1. Go to <https://service.byte.nl/bestellen2/>
+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. This step will not initiate a transfer. If you want to transfer the domain to Hypernode you can choose the option 'Domein + hosting verhuizen' if you only want to order a Presence Plan but you have no plans for transferring the domain name you can choose the option 'Hosting only verhuizen'
 1. Select the plan you need.

diff --git a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md
@@ -17,9 +17,9 @@ When you want to use Office365 and your domain is registered with Hypernode or h
 
 ## Validation Record
 
-When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://auth.byte.nl/)and follow the next steps:
+When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://my.hypernode.com/)and follow the next steps:
 
-1. Log in to the Service Panel (service.byte.nl).
+1. Log in to the Service Panel (my.hypernode.com).
 1. Select the domain from the domain overview.
 1. Click the tab **Instellingen**.
 1. Then select **DNS**.

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
@@ -20,8 +20,6 @@ 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).
 
-For Service Panel customers only: when your domain is hosted at Hypernode, simply link it to your Hypernode through the [Service Panel](https://service.byte.nl/)
-
 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

diff --git a/...-validate-your-ssl-certificate-and-more-frequently-asked-questions-about-ssl.md b/...-validate-your-ssl-certificate-and-more-frequently-asked-questions-about-ssl.md
@@ -17,7 +17,7 @@ redirect_from:
 
 ## What Kind of Certificates Can I Order via Hypernode?
 
-At Hypernode you can request various SSL certificates via the [Service Panel](https://auth.byte.nl/login/). There are three types of certificates:
+At Hypernode you can request various SSL certificates via the [Service Panel](https://my.hypernode.com/login/). There are three types of certificates:
 
 - SSL single certificate; you can use this on a single domain for the naked domain and the www domain (example.com and [www.example.com](http://www.example.com)).
 - SSL wildcard certificate; You can use this to secure all subdomains (\* .example.nl) for your domain name, but also on [www.example.nl](http://www.example.nl) and the naked domain (ie example.nl). However, this certificate does not work on \*. \*. example.nl.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -65,4 +65,4 @@ Scroll down to select ‘Empty’ from the dropdown ‘With selected’ and clic

		## Turn Off Database Logging

		If you don’t need any database logging it can be worthwhile to disable all logging. To do so, install the [`disablelog extension by Yireo`](https://www.yireo.com/software/magento-extensions). For shops that are heavy on the database, this can help reduce the amount of update/insert queries and therefore reducing load times.
		If you don’t need any database logging it can be worthwhile to disable all logging. To do so, install the [`disablelog extension by Yireo`](https://github.com/yireo-magento1/Yireo_DisableLog). For shops that are heavy on the database, this can help reduce the amount of update/insert queries and therefore reducing load times.