Premium Servers - Replacement Nameservers

The nameservers for our Premium Hosting have now changed...

ns1.premium.hostns.io (109.70.148.4)
ns2.premium.hostns.io (109.70.148.5)

Please note that we have already re-routed the previous nameservers to the above, so DNS will continue to resolve as before. 

It is however recommended, that you update any domains which are using the Premium Hosting facility to use those mentioned above. 

Cloud and NVMe now available in the USA!

We are incredibly pleased to announce that we have provisioned our latest USA server on cloud infrastructure using 100% NVMe storage!

In Ashburn, Virginia (USA), we also provide AMD-based cloud servers on a highly redundant, highly scalable infrastructure. 

The Ashburn location is in a region nicknamed "Data Center Alley", which is one of the most highly trafficked regions in North America, making our proximity to it ideal.

Any new orders being placed are being provisioned to the new infrastructure!

If you currently use our UK reseller hosting, then take advantage of selling to the USA by purchasing a second reseller hosting plan! 

You can add the additional server/location to your WHMCS and provision clients in a location of their choice, widening your hosting range and catering for a much larger market. In addition, you are able to obtain a '£5 Reseller Discount' as an existing reseller off any 'additional' reseller plans!

Use code SUBRESELLER in the checkout to get £5 off your USA Reseller Hosting! 

Please note, this discount is applicable only to secondary Reseller Hosting plans. To claim this discount, you must have an existing, full-price Reseller plan active.  

Brixly Preview Plugin

We're please to announce an upgrade to our Website Preview plugin to work alongside the API changes to SkipDNS.

This also comes alongside improvement to the service to store the Preview URL created, if you choose to use the Website Preview tool now the generated URL will be available for a week to augment your workflow - you can then generate a new URL once this has run out.

For further information please see our knowledge base available here.

Important AutoSSL / SSL Certificate Changes

We are pleased to announce we have now rolled out some significant changes and improvements to the way in which SSL certificates are handled. 

Until now, our servers across the board have been using 'Sectigo' for SSL issuance by default, however, over time this has become somewhat of a 'mixed bag', with some servers running LetsEncrypt and others still running Sectigo!

The reason for this is that both solutions have their own benefits and their own limitations. For example, LetsEncrypt has incredibly 'strict' rate-limiting, whereas Sectigo has no rate limits at all. Similarly, LetsEncrypt supports wildcards, whereas Sectigo does not!

To combat this, we have decided to change things slightly, so that you are able to benefit from both solutions simultaneously. 

Please note: SSL Certificates installed through AutoSSL are powered by Sectigo, which provides you with full 256-bit encryption, similarly to the LetsEncrypt solution. 

Sectigo is suitable for almost all sites and domains, however, Sectigo does have certain restrictions and limitations in the types of SSL certificates that can be installed.  

LetsEncrypt however, also offers you additional functionality, such as the ability to support wildcard coverage, and also supports redirection tracing which can be simpler for some sites hosted behind Cloudflare, or other CDNs / proxy services. 

Unfortunately, citizens from the countries listed below cannot obtain any Sectigo SSL certificates due to US Export restriction laws:

  • Afghanistan
  • Cuba
  • Eritrea
  • Guinea
  • Iran
  • Liberia
  • North Korea
  • North Cyprus
  • Sudan
  • Sierra Leone
  • South Sudan
  • Syria
  • Zimbabwe

However, if you do require SSL coverage for these domains / TLD's, then you are able to install an SSL certificate via LetsEncrypt, which does not have the same exclusions.


The introduction of LetsEncrypt SSL Certificates

As outlined above, Sectigo SSL certificates offer optimal coverage, completely automatically and free of charge. In addition, they also do not 'rate limit' requests, making it an ideal solution for us as shared hosting providers.

LetsEncrypt however, also offers you additional functionality, such as the ability to support wildcard coverage, and also supports redirection tracing which can be simpler for some sites hosted behind Cloudflare, or other CDNs / proxy services. 

If your use-case/scenario requires a LetsEncrypt SSL certificate, then we now provide you with the ability to install a free LetsEncrypt SSL certificate from within cPanel...

cPanel -> Let's Encrypt™ SSL 

We have provided a full guide in our knowledgebase of how to install LetsEncrypt SSL certificates for your website / domains...

https://support.brixly.uk/en/knowledgebase/article/how-do-i-install-a-free-ssl-via-cpanel


Will I need to do anything?

In most cases, absolutely no changes are required.

However, if you do require 'wildcard' coverage (and if you are unsure of what this is, the chances are you aren't using it!), then we would recommend installing a new SSL certificate via the articles outlined above. 

In addition, if your domains are included in the list of Comodo's banned countries outlined above, then you would need to install a new SSL certificate via the process outlined in the articles also. 

In short, if you do not use wildcard domains, and you also do not have domains from the country list above, then no changes are required, and this can likely be ignored. 

Important: Credit / Debit Card Processing Changes

Until now, we have accepted credit and debit card payments through our partners at WorldPay, using a facility called 'FuturePay Agreements'. 

Whilst we have built a fantastic, long-standing relationship with WorldPay, we do feel their solution is somewhat outdated and restricted in a number of ways causing complications in areas which we completely understand, shouldn't be complex!

As such, we have partnered with Stripe as our new merchant provider, who will handle credit and debit card payments moving forward. 

This brings a wealth of benefits to you as a client, upfront and foremost a significantly more intuitive and self-managed approach to making payments. 

If you have previously paid via WorldPay, to avoid any potential disruption to service we would strongly encourage that you login to our client area, and add a new card to your account with us. In addition, we would also recommend that you remove any previous WorldPay FuturePay agreements also.

This can now be entirely managed from our client area...

Client Area -> Billing -> Payment Methods

Once you have done this, it is essential that you also change your 'Default Payment Method', which will be applicable for all future invoices / services and renewals. This should now be set to the new card.

To do this, you will need to edit the 'Payment Method' set against your 'Profile'...

https://client.brixly.uk/clientarea.php?action=details

From the dropdown provided, ensure you have selected the appropriate option (if paying via Credit / Debit Card, select that option above). 

Once you have done the above, all future payments will be taken from the new card, as opposed to the WorldPay FuturePay agreement. 

Whilst we are not phasing out WorldPay entirely at this stage, we may do so within a few weeks. As such, the steps above are recommended as soon as possible to ensure that invoices continue to be paid. 

Please note: PayPal payments and Direct Debit Payments (paid via GoCardless) are not affected. This is only applicable if you pay via WorldPay / Credit / Debit Card. 

If you have any questions in relation to the above, feel free to reach out to our sales and billing team directly at sales@brixly.uk for more assistance. 

BitNinja OptinMonster Update

Patched OptinMontster Vulnerability

BitNinja’s WAF has patched a serious vulnerability within a WordPress plugin named OptinMonster, affecting over 1,000,000 websites.

With a carefully crafted request, an unauthorized party could bypass authentication when calling some endpoints provided by the plugin.

The team has patched it with a WAF rule (Rule ID 406002) that is available for every BitNinja user worldwide, preventing a possible exploit of this vulnerability.

Memcached release for all cPanel Reseller Servers

We have just pushed an update out to allow all customers using our cPanel Reseller platform to make use of Memcached for object caching with LiteSpeed.

Previously there were some concerns about using Memcached across our infrastructure due to users data being exposed, however through LSMCD and SASL these issues have been alleviated and we're happy to make this available for all of our cPanel customers.

More information about setting this up can be found within the article below:
https://support.brixly.uk/en/knowledgebase/article/how-do-i-enable-memcached-object-cache-for-litespeed

Improved Account Verification Process

We have now introduced an automated verification process for orders which have been flagged as higher-risk. 

Previously, we were capturing verification through a manual review process, however, to speed up this process we have now added automated verification to our checkout process, through a custom integration with Stripe Identity.

This has allowed us to introduce a fully automated ID and document verification process, allowing flagged orders to be reviewed in just a few minutes. 

Please note that if you already have an active service, this change will not be applicable to you, and will not be required. 

Removal of Cloudflare 'CNAME' Provisioning

Hi there,

We received an email from Cloudflare, confirming that the 'CNAME' method of provisioning accounts is no longer going to be supported via the cPanel or DirectAdmin plugins.

What does this mean?

If you are using Cloudflare via the cPanel plugin, you are given two options. Full zone provisioning where you update to Cloudflare nameservers, and a 'CNAME' method, which would previously just reconfigure your DNS zones so that certain records routed through to Cloudflare. 

Cloudflare have now removed compatability with the latter, and therefore CNAME provisioning will no longer be possible via the plugin or the API. 

You are still able to make full use of the Cloudflare plugin, however until they provide us with an updated cPanel module the CNAME provisioning will still be available as an option, but will not work. 

Instead, if you are looking to use Cloudflare through the plugin simply use the Full Provisioning option, whereby you are also required to update to the Cloudflare provided nameservers against the domain. 

Show Previous EntriesShow Previous Entries