Release-4535: Update Nginx in preparation for brotli compression. Improve OCSP cache warming
We’ve updated Nginx to version 1.13.5. With this update we’ve included the option to use the brotli compression algorithm (it’s still disabled for everyone though). We are looking for volunteers to test the brotli compression, if you are interested please send us an e-mail to support@byte.nl. Brotli is a new compression algorithm from Google which…
Read moreRelease-4379: fix Blackfire for PHP 5.6
Fixed the Blackfire PHP 5.6 integration. When we released PHP 5.6 for Hypernode we forgot a small step which prevented Blackfire from working. This has been fixed.
Read moreRelease-4333: Install/prepare PHP 5.6 release
In preparation for the PHP 5.6 release, we are installing PHP 5.6 alongside the other PHP versions. The ability to use PHP 5.6 for your shop will follow soon. Additionally, we now allow LOAD DATA INFILE queries from all locations
Read moreRelease-4310: Updated PHP 7 to 7.0.22
We have updated our PHP 7 version to 7.0.22. This new release includes various minor bugfixes, for a complete list of changes click here.
Read moreRelease-4295: Updating php-redis, php-imagick and blackfire
PHP 5.6 preparations In preparation for the PHP 5.6 release we’ve rebuilt the php-redis and php-imagick PHP modules. These have already been re-built for existing PHP versions (PHP 5.5 & PHP 7). In addition they are also built for PHP 5.6 now. Blackfire updates We’ve also updated our Blackfire probes: blackfire-agent 1.11.0 -> 1.14.1 blackfire-php…
Read moreRelease-4287: ioncube for php7, more mysql connections for larger nodes
Ioncube for PHP 7 We’ve made ioncube available for PHP 7 as an opt-in option. If you would like to use ioncube for PHP 7 please contact support, and let them know for which nodes you would like to enable ioncube. More MySQL connections For larger Hypernodes (from 20 cores and up) we’ve increased the…
Read moreRelease-4252: Automatic recovery delayed at night
We’ve changed our automatic recovery to be delayed at night. When a server goes offline or becomes unresponsive, an automated process attempts certain rescue strategies in order to resolve the issue. Some customers run cron jobs at night which would cause database locks and effectively causing their websites to go offline. Our recovery is now…
Read moreRelease-4224: add php snappy module
We’ve added the snappy compression algorithm to PHP. Snappy offers much higher compression/decompression speeds compared to gzip, at a slight compression ratio cost. This is taken from the Squash Benchmark, which is a good overview over various compression algorithms vs various input data. From the above benchmarks, using the core i-7 machine together with the…
Read moreRelease-4199: Various improvements
We’ve fixed a bug where nginx configuration was not correctly re-generated when using Let’s Encrypt and enabling/disabling Varnish. This could have resulted in SSL domains pointing towards Varnish while varnish was disabled/not running resulting in a 502 error. Now depending configurations are re-generated correctly when changes are being applied. We’ve added TLS support for FTP…
Read moreRelease-4091: Varnish improvements
We’ve improved how our code manages the varnish installation for Ubuntu 16.04 Xenial and Ubuntu 12.04 Precise nodes. fixed configured vcl being lost on full update (16.04 Xenial) fixed configured vcl being lost between node migrations (16.04 Xenial) fixed varnish getting reinstalled on full update (16.04 Xenial) fixed varnish getting restarted on full update (12.04…
Read moreRelease-4046: whitelisted Ayden’s user agent
We’ve whitelisted the Ayden’s HTTP user agent, from the bot ratelimiting. It’s no longer subject to the bot ratelimiting mechanisms.
Read moreRelease-3981: Deny specific configuration files on magento1 installations
We’ve moved certain security restrictions from the magento2 configuration into the global magento1/2 security configuration file. In specific the following files are no longer reachable from external: auth.(json|lock) package.(json|lock) composer.(json|lock) Gruntfile.js cron.php Hidden files are also denied with a 403 now instead of a 404. Furthermore we’re working hard on the Xenial migration. Many changes…
Read moreRelease-3864: IP authentication exceptions on development plans
In this release it becomes possible to whitelist IP addresses on development plans, so that they are exempt from the basic authentication requirements. This may be useful to test external payment providers or other kind of external services which do no support basic auth. The whitelist file is placed in /data/web/nginx/whitelist-development-exception.conf and looks like this:…
Read moreRelease-3760: Updated monitoring for development plans
We’ve updated the monitoring of development nodes. The alerting for these plans has been changed to only alert during business hours.
Read moreRelease-3728: allow let’s encrypt on dev plans. fix ibdata1 shrink automation
On development plans it’s now possible to use let’s encrypt again. The relevant requests have been made exempt from the basic auth. We fixed a regression in our shrink_ibdata1 automation. A regression had been introduced by the MySQL version update end November. We added an alias `sf2` which shows all magento2 storefronts. It executes `cd…
Read moreRelease-3586: Updated composer
We’ve changed our composer update itself with the –stable flag. Freshly provisioned nodes however did not understand this flag yet, due to the initially deployed composer being too old. We’ve updated composer in our repository so that all new nodes will be able to update themselfs to the latest stable composer.
Read moreRelease-3523: block Visbot user-agent
We now block all user-agents which contain the term “Visbot” inside the user-agent string.
Read moreRelease-3513: Updating MySQL to 5.6.33
We are in the process of updating MySQL to the latest version, to get the latest improvements and security fixes. Last night we updated all Hypernodes with starting letters U-Z. Tonight we will update all Hypernodes with starting letters M-T. Tomorrow night all Hypernodes with the starting letters A-L and 0-9 will be updated. …
Read moreRelease-3470: Improved auto recovery
We’ve improved our auto recovery to automatically attempt fix filesystem inconsistencies on boot. In rare occasions a Hypernode would be forced to reboot off an uncleanly closed filesystem. On boot it would then prompt asking what to do (if it should recover). A recovery is now automatically attempted, reducing recovery time for these cases.
Read moreRelease-3447: stricter fail2ban rules on rss notifystock
We tightened our fail2ban rules for rss/notifystock bruteforce attempts to ban 24 hours instead of previously 2 hours. Additionally we enabled the automatic recovery for all nodes now, along with a minor improvement in the auto recover logic.
Read moreRelease-3428: Stop HHVM on all A-L Hypernodes which are not using it
For all Hypernodes with the first letter A-L we’ve stopped HHVM unless it was used. On the remaining Hypernodes (M-Z), we stopped HHVM already in an the earlier release. HHVM is deprecated in favor for PHP7. In order to save memory we’ve stopped HHVM on all nodes which were not using it to reclaim memory….
Read moreRelease-3421: Stop HHVM on all M-Z Hypernodes which are not using it
For all Hypernodes with the first letter M-Z we’ve stopped HHVM unless it was used. The remaining Hypernodes (A-L) will also receive this feature in due time. HHVM is deprecated in favor for PHP7. In order to save memory we’ve stopped HHVM on all nodes which were not using it to reclaim memory. New Hypernodes…
Read moreRelease-3411: Automatic recovery
For all Hypernodes, whose first letter begins with M-Z, we’ve enabled a new automatic recovery feature today. All Hypernodes starting with letters A-L will receive this feature as well in due time. Should a Hypernode become unreachable or unresponsive, our automation will attempt to resolve the problem before alerting one of our technicians. The automation…
Read moreRelease-3377: Remove HHVM for new Hypernodes
As of now newly ordered Hypernodes will not have HHVM available anymore. Support can re-enable HHVM for you, should it really be necessary. We recommend everyone to use PHP7 instead. It delivers an even better performance boost and is better maintained by the community.
Read more