Skip to main content
All CollectionsGovernance and securityLearn about My Betty Blocks
Changing the front end to your own custom domain (with SSL certificate)
Changing the front end to your own custom domain (with SSL certificate)

Сhange the front end of your application to your custom domain domain by using SSL.

Updated over a week ago

After reading the article you'll know:

  • What an SSL certificate is

  • How to define a host within Betty Blocks

  • How to verify your domain hostname

  • How to provide the SSL to Betty Blocks

My own domain?

When you've developed a fully customized front end on top of your back-end application, you might want to show this custom UI to the entire world. Well, you can already do this straight away because your app's front end is directly accessible with the link every page has (e.g. 

But instead of having to use the domain, you might rather want your custom UI to be accessible through your own domain. Well, let's set this up then!

What is an SSL certificate?

The SSL certificate ensures an encrypted connection, which will also grant you an HTTPS connection. An SSL certificate is required in order to set the app to your own domain so we're not only learning how you can set the app to your own domain, but we'll also explain how we can install an SSL certificate on your domain. 

What are we going to do? 

Setting up your app to load on your own domain is not that hard, but it has to follow certain steps. We need to set some settings for you, based on the certificate you've got, and you need to set some settings for your domain as well. Basically, we need to do 2 things. We need to (1) set up the application to load on your own domain and (2) we need to install the SSL on this domain. In detail, it includes the following:

  1. Define the host in the application settings in My Betty Blocks. (1)

  2. Verify your domain via the hostname settings.

  3. Create a CNAME record for the app in your domain's DNS settings. (1)

  4. Send us the SSL certificate (min. 12 months) and Private Key, along with the needed details to install this on the app. (2)

That's all! Piece of cake, right?
Not? Don't worry. We'll elaborate on each step for you.

Define the host in My Betty Blocks

First, you'll have to set your own domain as a host in the applications web options in My Betty Blocks. If you're in your app right now, go to the settings menu in the builder bar and click on general to open the application overview. You can also open, login and click on your application if you're not logged in to your app at the moment.

Once you're at the overview, go to the app settings in My Betty Blocks, and then click on the HOSTNAMES tab in the middle of your page.
Here, you can enter each host you want to use for your web app.

A normal app SSL will provide 1 full domain (e.g. or but if you're using a Wildcard SSL, you'll have to define all the full domains you want to use, so a different host for every subdomain (i.e.,, 

Verifying your domain in the hostname section

Before being able to connect with your domain, we have to make sure that the domain is secure and that you or your colleagues have complete control of the domain.

To verify your domain, follow the next steps in the hostname section of your application's settings.

As an example, we are going to verify ‘’:

  1. Add ‘’ to the list of hosts in and press the "add hostname" button.

  2. A new field opens up with a domain-verification token. Copy the token for ‘’

  3. Navigate to your DNS provider with your domain verification token.

  4. Add a TXT record to ‘’ via the interface of your DNS Provider with the value: ‘bettyblocks-domain-verification=<yourtokenhere>’

  5. Click on the verify button next to ‘’ in to have Betty verify your domain.

*It may take up to 48 hours for the txt record to take into effect due to DNS caching.

*Values and settings per DNS provider might differ, make sure to read the provider's guide when working with your DNS settings.

Create a CNAME record in your domain's DNS settings

After a successful verification, you can remove the TXT verification line from your DNS and set the CNAME record for your application.
If you can log in to the management environment of your domain provider you can likely do this here. If you don't have a login for a management environment you can contact your domain provider (or your IT department) for this. If you tell them you need to add a CNAME to your DNS, they'll know how to help. Most providers also offer some kind of documentation on how you can do this for your domain. The DNS resource records you can create have only got 3 properties most of the time. See the example below.

Beware! There's some inconsistency between providers here. In our example, the first field asked for the HOST. If your provider asks for a subdomain instead of a domain or host, the correct value would be www, instead of (or app if you want to connect

When this is all set up, your application is connected to your domain! It may take a couple of minutes for your provider to process your request, but it shouldn't take very long (and the message 'default backend - 404' will appear)

From here on, get in touch with our support department to get things finalized since you need an SSL certificate to be installed on our servers, this is where your effort becomes a joint effort. :)

Provide us with your SSL certificate and private key

If you've got an SSL certificate, you'll have to share this with us via our portal by creating a Service Request. Don't forget to send the private key in a separate email. We ask you to forward this via mail due to security reasons. Without the private key, we are not able to handle your request. Whichever way you please, you'll need to get in touch with our Support Team via the Intercom button in your app or by sending an email to is what you need to provide the support team:

  • Application identifier

  • Name of the application

  • External domain URL

  • The SSL certificate (.crt or .pem) in a zip file

  • The private key (.key) that was used to generate the certificates’ CSR

  • Any urgent deadlines?

  • Phone number

  • Description

Additional information

Please, keep the following in mind:

  • We only accept SSL certificates with a duration of 12 months or longer. Anything shorter than 12 months will be rejected.

  • Submit your SSL certificate request to our support department, a minimum of 14 days prior to the launch (or expiration) date of your website's certificate

  • You will be charged fees if you do not submit the SSL certificate necessary for the installation, in time.

After this step, you can reach out to our support crew to whitelist your data API. Ask your internal IT department which services inside of the application need to be whitelisted. This ensures that only trusted and authorized sources can access your API, so by doing this, you prevent your system from data breaches and security threats.

Did this answer your question?