24/7 monitoring and alerting

At Byte we understand like no other that the availability and stability of the application is a top priority for our customers. This stability depends on many different factors, including the stability of the Hypernode itself. To ensure the highest possible stability, our experts monitor your Hypernode 24 hours a day, 7 days a week. […]

Read more

Backups on Hypernode

On Amazon (AWS) and Combell OpenStack we use snapshots to create backups. When things go slightly wrong (ie. a product is accidentally deleted), you can go back in time to restore the appropriate database table, files or directories from the backup. Snapshots are easy to use, take up less time and there’s no need to […]

Read more

Creating your own backups with Tarsnap

Managing backups yourself If you choose to create your own backups, we recommend using Tarsnap as an offsite backup provider. This very robust third party backup service is well known for it’s excellent security and their low prices. Tarsnap encrypts your data and then stores it on Amazon S3 storage platform. S3 is extremely reliable, […]

Read more

How to attach a snapshot to your Hypernode

Some hands-on experience is required! If you have never used the command line, please contact one of our partners to get some assistance. On Amazon (AWS) and Combell OpenStack we use snapshots to create backups. When things go slightly wrong (ie. a product is accidentally deleted), you can go back in time to restore the appropriate database […]

Read more

Identifying and stopping long running processes

Long running processes can indicate that the the site might benefit from an index (SQL), that there’s inefficient or erroneous code (PHP), or that a deadlock has occurred. This article explains how to identify long running processes. Long running SQL processes To identify long running SQL processes you can use the tool Mytop. Mytop displays the […]

Read more

Limits on active PHP requests per IP

Hypernodes use Nginx and PHP-FPM for processing and serving PHP pages. PHP-FPM uses FPM worker threads to process requests from Nginx. The amount of workers that are available on the Hypernode depends on how many available CPU cores the server has. Benchmark tests have concluded that, based on CPU contention and concurrency, the optimal number […]

Read more

My Hypernode was rebooted

If a Hypernode suddenly gets rebooted, this might be the result of security updates on the operating system. If this is the case, we always create a maintenance post at our status page on Bytenoc.nl. In other cases, the reboot is most likely caused by a server being non-responsive for 15 minutes. We implemented a mechanism that […]

Read more

PHP versions for your Magento shop on Hypernode

PHP versions on Hypernode On Hypernode you can choose from a range of PHP versions: PHP 5.6 -> officially EOL from 31 Dec 2018 onwards PHP 7.0 -> officially EOL from 3 Dec 2018 onwards PHP 7.1 PHP 7.2 You can easily switch the PHP version of your Hypernode, but please thoroughly test a PHP […]

Read more

Resolving 429 Too Many Requests

To protect your Hypernode from all kinds of attacks, bots, brute forces and scriptkiddies causing downtime, we’ve implemented several layers of rate limiting. Most of these rate limit methods only apply to bots, but to avoid FPM worker depletion, we recently implemented a rate limiting mechanism per IP to prevent a single IP from exhausting […]

Read more

Resolving 502 Bad Gateway errors

A 502 Bad Gateway error indicates there has been an internal error with PHP, so the site could not be rendered and you will see an error in your browser. Verify whether 502 errors have occurred Log in on your Hypernode and issue this command (–yesterday works too):

It will tell you those requests […]

Read more