Release 8403: PHP 7.4.28, 8.0.16 and 8.1.3
In this release we’re updating PHP versions to 7.4.28, 8.0.16 and 8.1.3. This is to counter the new CVE-2021-21708, where a bug was found in the PHP function php_filter_float. The changes in the new versions are covered in the PHP changelogs. Please refer to either the PHP 7.4.28 changelog, PHP 8.0.16 changelog or PHP 8.1.3…
Read moreRelease 8336: Varnish 6 available on Hypernode
In this release we add a new feature for upgrading your Varnish version to Varnish 6. We will be installing Varnish version 6.1.1-1+deb10u1 when you upgrade your Varnish version to 6. Using Varnish 6 Upgrading your Hypernode to Varnish 6 is an easy process, but should be handled with some caution. The Varnish team says…
Read moreRelease 7807: Sansec’s Magento corediff
Yesterday our friends over at Sansec announced they opensourced their corediff tool! You can check out their Github repository and enjoy it for yourself. Corediff is a commandline tool that can be used to uncover server side payment skimming amongst other things. It does this by comparing your Magento directory to legitimate code hashes provided…
Read moreRelease 7786: Ensuring stability on Hypernode
In the coming days of the holiday season, the last thing you want to worry about is your hosting environment. This is why we have taken extra proactive measures to ensure the stability of your Hypernode. We do this with the changes that are listed in this changelog. These changes have been released alongside our…
Read moreRelease 7785: Increasing performance on Hypernode
At Hypernode, we constantly look for opportunities to improve our platform. In a proactive approach for the coming holiday season, we’ve been benchmarking our platform to find possible improvements of our Hypernode setup. Here is a list of changes that we’ve made to our platform that give a significant improvement of response times and reduce…
Read moreRelease 7721: Block python-requests/2.13.0
We have started automatically blocking all requests that have the user agent python-requests/2.13.0 on our fleet of servers. This is because we have seen an increase of this user agents performing a malicious amount of requests, as can be seen in this graph: If you do not want to have this user agent blocked,…
Read moreRelease 7620: Hypernode-systemctl bash-completion, PHP CLI memory limit increase
This changelog introduces the addition of bash-completion functionality to the hypernode-systemctl command, which helps you find the right command to execute on the command line. Next to this, we made a change to the memory limit for PHP CLI. We will be applying both of these changes to all Hypernodes over the coming week. Hypernode-systemctl…
Read moreRelease 7166: Hypernode-manage-vhosts enabled by default
From this release onwards we will enable the Hypernode managed vhosts feature on newly created Hypernodes. This does not affect any existing Hypernodes, and will only affect Hypernodes that are newly created. What are Hypernode managed vhosts? Hypernode managed vhosts is a feature specifically made for Hypernode that allows you to easily add, remove and…
Read moreRelease 7004 – List option for hypernode-manage-vhosts
In release 6640 we’ve added a new feature that allows you to easily manage your Nginx VHosts using the hypernode-manage-vhosts command. Enabling the use of this feature allows you to configure one or more VHosts in a quick and easy manner. We’re extending the usability of this feature in this release by adding the –list…
Read moreRelease 7003 – Elasticsearch 7.6
Elasticsearch 7.6 In this release we’ve added support for Elasticsearch 7.6. Elasticsearch 7.6 was released on 11 February 2020 which includes a whole range of new features and performance improvements! This is based on the new major version Elasticsearch 7, which also included significant improvements compared to version 6. Start using Elasticsearch 7.6 You can…
Read moreRelease 7000 – MySQL 8.0
With this release, we add support for MySQL 8.0 on Hypernode. This is one of the requirements needed for Akeneo 4.0. To prevent compatibility issues with older versions, we do not allow downgrading from MySQL 8.0 back to either 5.6 or 5.7. Upgrading your Hypernode to MySQL 8.0 Upgrading your database to MySQL 8.0 can…
Read moreRelease 6640: Managing your Nginx VHosts with hypernode-manage-vhosts
This release allows you to enable support for the new hypernode-manage-vhosts command on your Hypernode. This commands allows for easy management of your Nginx server blocks, or commonly referred to as VHosts, on your Hypernode. Managing your VHosts in an easy manner becomes increasingly important if you want to set up multiple VHosts on your…
Read moreRelease 6584: Block requests to sql and archive files by default
From this release we will start blocking .sql files and archive files by default in Nginx. We do this to prevent accidental exposure This is done by placing the following line in the Nginx configuration: location ~ .(sql|zip|tar|tar.gz|tgz)$ { deny all; } Any requests to files with the extenstion sql, zip, tar, tar.gz or tgz…
Read moreRelease 6583: Upgrading to MySQL 5.7
In order to support Akeneo and Shopware properly, we have added a new feature in our hypernode-systemctl tool to give you the ability to upgrade your MySQL version to 5.7.26-29. Upgrading your Hypernode to MySQL 5.7 If you want to upgrade your existing Hypernode from MySQL 5.6 to MySQL 5.7, you can simply run the…
Read moreRelease 6394 – Dehydrated version updated to v0.6.5
In this release we updated our Dehydrated version from v0.6.2 to v0.6.5. This was done in order to fix an issue we noticed when generating new Let’s Encrypt certificates. We received a 400 error with the following error message: Malformed account ID in KeyID header URL: “https://acme-v02.api.letsencrypt.org/acme/acct/” This bug was fixed in v0.6.5 of Dehydrated….
Read moreRelease 5469: Log rotation and improved memory management
We’ve made several changes to our log rotation setup in this release. Here is a summary of the most important changes. Log rotation for SFTP We have noticed several Hypernodes gradually filling up their disk because the SFTP logs grew out of proportions. We prevent this by enabling log rotation on the SFTP logs. When…
Read more