Basic authentication on Hypernode development plans

Byte offers its customers discounted development plans of all the regular Hypernode plans for development and testing. These plans are meant to develop one webshop at the time, to run all the tests you can think of, and to give your customer (the shop-owner) access during development. Keep in mind though, these development plans cannot be used to go live with a shop.

Default username and password

The default credentials for development nodes are:

  • Username: dev
  • Password: dev

Changing your settings

Change the default username and password as soon as possible. The htpasswd in which the usernames and passwords are defined is located at
/data/web/nginx/htpasswd-development.

This file must exist and a valid username and password must be defined within this file in order to be able to login.

Adding or removing users

To add users, use the command: htpasswd /data/web/nginx/htpasswd-development username
Remove users is simply done by editing the file and remove the line where the user is defined in or using the following command: htpasswd -D /data/web/nginx/htpasswd-development username.

Overriding basic authentication

To override a single IP from using basic authentication, you can whitelist this IP address by adding it to /data/web/nginx/whitelist-development-exception.conf.
This way you can easily test API connectivity, do load tests or run Magereport on your development node.

Alternatively, you can whitelist user agents as well by using the following snippet in /data/web/nginx/whitelist-development-exception.conf:

As a precaution all Google and Bing crawlers are blocked to avoid production usage of the node.

To use a node for production, please upgrade your development plan to one of the regular Hypernode plans, the basic authentication will no longer be enforced, bots will no longer be blocked and you can go live with your webshop. You can easily upgrade your plan on the Byte Service Panel.

Ordering Let’s Encrypt certificates

Ordering Let’s Encrypt certificates on your development node is possible by issuing a certificate request that will fail the first time.

After the request failed, check your /var/log/nginx/access.log and retrieve the IP address the Letsencrypt validation robot uses to validate your certificate.
If you add this ip address to the /data/web/nginx/whitelist-development-exception.conf, the second certificate request will succeed.

Troubleshooting

  • Google Pagespeed analysis uses the Google bot user agent and can therefor not be used on development nodes.
30