Changelog - Hypernode

Release 2932: Update PHP 5.5 ioncube loader

During today’s PHP 5.4 to PHP 5.5 migration some customers reported problems with the ioncube loader in PHP 5.5. This release updates the ioncube loader to 5.1.2 in order to fix the following error: PHP Fatal error: The file [path_to_file] was encoded by the ionCube Encoder for PHP 5 and cannot run under PHP 5.5….

Release 2911: Rate limit HTTP code now 429

Our rate limiter kicks in when foreign bots (non-search engines) hammer your shop. Previously, they were rejected with a HTTP 503 code (temporarily unavailable). This has been changed into 429 (too many requests) as that is a more apt response. Also, we have added better out-of-band access for our operations department, in case something is…

Release 2902: Solr for Excellence plans, fixed session cleaner

11 April 2017: due to low demand we deprecated SOLR in favor of sphinx. Starting now we don’t sell SOLR plans anymore. In today’s release we have: Solr is available on request for all Excellence Hypernodes. Please contact Support if you’d like it enabled. We moved the sessions from one place to the other. We…

Release 2871: manage server name with custom_server_name and an expansion on our monitoring

Release 2871 brings a new variable $custom_server_name to control the custom server name instead of overwriting server_name directly. This fixes a potential configuration collision between licensing based on server_name and TLS certificate selection: server_name is used to select vhosts and the TLS certificates. It is also passed on to PHP as fastcgi_param so it shows…

Release 2856: New Relic 6.2, now also for PHP 7.0

We’ve updated the New Relic agent to the latest version, which is compatible with PHP 7.0. So we’ve also added New Relic to PHP 7.0 when you enable it on the Service Panel. Also, we’ve made some tweaks to the OOM killer, which is a piece of software that is triggered when your Hypernode runs…

Release 2846 – ftp/mysql firewall, php7 modules and much more!

It’s been a while but a lot has happened with Hypernode as always! Let’s get right to it: external FTP connections are now rejected by default, unless specific IP is whitelisted external MySQL connections are now rejected by default, unless specific IP is whitelisted PHP 7 has received extra modules: gd, zip and soap We’ve…

Release 2757: PHP 7, Vagrant LXC, API restricted and more

The moment is finally here! PHP 7 is available on Hypernode. These are the changes we’ve made since the last release: PHP 7 support New PHP version available: 7.0.4. You can upgrade in the service panel or try it out in the Vagrant Installed modules: Curl, GD, IMAP, intl, mbstring, mcrypt, mysql, ldap, pgsql, pspell,…

Release 2684: Varnish 4.0.3 and Vagrant

We’ve been quite busy here at Byte, this changelog highlights some of the changes we made since the last reported release: Varnish 4.0.3 is now the default on new Hypernodes We will be reaching out to customers who are currently running Varnish 3 to discuss upgrading to Varnish 4. added esi_disable_xml_check flag to Varnish 4…

Release 2658: Magerun extensions

This release adds some great functionality to the preinstalled Magento Swiss army knife N98-Magerun: The handy extensions of Peter Jaap Blaakmeer have been added. Hypernode-sponsored features to check for updated modules and required patches.

Release 2628: Http2 support, magento 2 pre-installed

We’ve updated our nginx webserver to include http2 support. All our hypernodes now have http2 enabled. Magento2 trials now get magento2 pre-installed, to make it much more convenient to explore Magento2. When ordering a normal hypernode trial, the pre-installed magento version is still Magento 1. In HHVM we’ve enabled the zend compatibility mode which makes…

Release 2498: Magento2 support

Support for Magento2 has been in the works for a while. It started with the update to PHP 5.5 in release 2451. And now we have a first version of Magento2 support for Hypernodes. To get an Nginx config for Magento2: place a file named magento2.flag in /data/web/nginx/ Our Nginx config reloader will pick that…

Release 2451: PHP 5.5 for new hypernodes

Hypernode changes: New hypernodes will be provisioned with php 5.5 All existing nodes remain on php 5.4, if you would like to switch to 5.5 please ask our support staff. In case a website on a hypernode gets hacked, we can now administratively disable the sites on it to prevent further damage. Improvements to our…

Release 2384: Passive FTP through AWS, fdupes and various infrastructure changes

Hypernode changes: Added fdupes to hypernode stack for deduplicating images Passive FTP through AWS is now supported Improvements to our deployment infrastructure: Tweaks to internal tools for faster access to all nodes More expansive monitoring of our internal systems Shorter cycle times for scaling our continuous deployment Persistent storage of job progress for inspection and…

Release 2192: No more PHP memory limits, blocking certain bots entirely

No more memory limits on PHP processes A while ago, we introduced a global cgroup limit on memory. This is a safeguard that makes sure the app user does not use more memory than is healthy for the Hypernode. The total of memory used by processes owned by the app now cannot exceed a certain…

Release 2166: Crash recovery backups, stability tweaks and updated composer

A lot of exciting stuff has happened since the last update, mostly on the infrastructure side of things relating to the stability and monitoring of the platform. Internal changes: New method for creating crash recovery backups on the Digital Ocean nodes using S3 Automatic complete restoration of production nodes from backup All Magento Start and…

Release 1810: Varnish fixes, Turpentine continuous integration

So it’s been a busy week at Hypernode headquarters. There’s been lots of development on internal processes and customers testing Varnish brought up lots of interesting bugs to fix 🙂 This release brings you: Migrating nodes that have Varnish enabled will now just work ™ instead of crashing. We’ve created Jenkins jobs that test Hypernodes…

Release 1767: Varnish support

This release features preliminary support for Varnish using the Turpentine module for Magento. The change should not affect current Hypernodes, because Varnish is disabled by default (requests are not routed through Varnish, nor is it started by default so it does not use up any memory). Customer overrides of Nginx should all still work. To…

Release 1736: Memory management enhancements and magmi importer security

Access to magmi is now blocked by default to protect shop owners from exposing an unsecured magmi installation to the world. Further improvements to memory management have been made, ensuring even greater stability in the event of an out-of-memory situation.

Release 1720: Automatically install Magento, added Composer and other updates

Automatically install Magento on new Hypernodes Composer has been made available due to popular request Updated n98-magerun to 1.97.4 Updated the ionCube Loader to v5.0.15 Increased stability in memory management

Release 1441: Rate-limiter tuned to solve issue with Sphinx, lftp secure ftp client

In some configurations Sphinx failed to respond to requests from the Magento admin panel, this is now resolved. Additionally, by request lftp has now been made available on the Hypernodes.

Release 1378: Fix memory issues, better Shoplift protection

Stability release: It was discovered that the php.ini memory_limit wasn’t enforced for PHP-FPM which would crash a node in extreme circumstances. Now a large but sane limit is enforced (256M for Start, 512M for all other Hypernodes). The filter that we installed to counter the immediate threat of Shoplift exploitation turned out to block a…

Release 1364: Better memory management for Start plans

This is primarily a stability release with the following tweaks: Better memory management for Hypernode Start plans. Fix bug with SSL file verification Automatic cleanup old incident files (2 months+) Better handling of full disks

Release 1326: CVE-2015-3428 mitigation

This release implements a filter that prevents SQL injection attacks made possible by a security flaw in aheadWorks Blog.

Release 1294: inode monitoring

We’ve had quite a few cases recently where nodes became unresponsive due to the runaway creation of PHP sessions on the disk. In practice, a storage filesystem has two limits: size in bytes, and number of files (inodes). With this release, we actively monitor on the percentage of available inodes. Reaching the limit is an…