Starting in 2017 Google Chrome and other web browsers will start marking HTTP sites as insecure. While this won't impact your mobile apps directly, users of your control panel will definitely see a warning message in their web browser stating the the site isn't secure.

In order to prevent this from happening, you must take the following steps:

  1. Find a website such as GoDaddy, that can issue an SSL Certificate. Make sure to purchase a Wildcard SSL Certificate (one that can support multiple subdomains). Once you have purchased your SSL Certificate you will need to request your certificate.
  2. They will need your certificate request file and/or private key files. You can download each of those text files below. When you copy and paste them, make sure to copy everything. If they are asking for the signature algorithm, choose SHA-2. Once you have requested your certificated it may take some time to approve your request and provide you with the certificate file.
  3. After your certificate has been approved, download the certificate file(s). If you receive multiple certificate files, one file contains your certificate and the other is known as the certificate authority bundle. While you can just use your certificate file, a better practice is to combine the two into a single file. You can simply open both files and copy the contents of the bundle file into your certificate file, below the existing text, and then save the changes.
  4. Log into your white label reseller admin control panel under Account >> Settings and upload the certificate in the "Certificate Upload" section below.
  5. Once you have uploaded your certificate file to BuildFire White Label Admin, you will need to update the DNS for your control panel, white label admin sites, (and sign-up site if applicable) to point to For example: You may have pointing to, change that to
  6. You're finished! Certificate files are valid for up to three years, depending on the type you purchase. When it comes time to renew your certificate, you can reuse your existing certificate request and private key files.
Did this answer your question?