A Bubble app comes automatically with a bubbleapps.io subdomain, served over SSL. For instance, yourapp.bubbleapps.io. If you want to customize this and use your own domain name, you can do this in the Domain section of the Settings Tab.
You can use a domain that you own with any registrar service (NameCheap, Dreamhost, etc.) and configure it to point to Bubble. This operation is done in two steps:
Set up the domain in Bubble
Set up the DNS records in the registrar's interface to point to Bubble
To set up the domain with your app, enter the domain in the input box in the Domain Tab and click 'Set up this domain'. Once you've done this, Bubble will provide the DNS records that you should enter on the registrar's end.
Once you have the DNS from Bubble, you do not have any setting to modify in Bubble. You should instead head to the registrar service that you use to manage your domain and find the DNS section (or DNS Zone File). Once you have found that section, delete existing A records whose name is '' (empty) and 'www', and instead add the records as indicated above. (Some registrars use '@' to refer to the empty domain.)
This process can be a little technical, and each registrar has a different interface. If you need help, we recommend reaching out to the registrar's customer support to get assistance to modify the records. Don't hesitate to ask for help on the forum as it's likely another user will have experience with the same registrar service.
After setting up the DNS records, the new settings need to propagate across the internet. This can take up to 24 hours, but usually you should see some results after 2-4 hours. Bubble lets you check the success of the operation below the records, and you can check the process by clicking on the 'Check my settings' button.
As soon as a domain is properly configured, all requests to yourapp.bubbleapps.io will automatically be redirected to yourdomain.com.
If you already are using a domain and would like to use a subdomain to point to your Bubble app (for instance, app.yourdomain.com), you can do this by simply using this as the domain in the input box. The DNS records will be different, but the process of entering them in your registrar service is similar as above.
If you had a custom domain name assigned to your Bubble app prior to October 2019, you are considered a Legacy Customer. If you have never assigned a custom domain to your Bubble app before, ignore the instructions marked for Legacy Customers.
Your users will generally expect to be able to load your domain on
www.example.com. For SEO purposes, we redirect exactly one of these to the other address.
For instance, if you enter
example.com as your custom domain, we will automatically redirect
example.com—as long as your DNS records are correct!
When you choose your custom domain, Bubble will instruct you to create four records at your registrar. The records will be of the form
Type: A Name: Value: 104.xxx.xxx.xxxType: A Name: Value: 104.xxx.xxx.xxxType: A Name: www Value: 104.xxx.xxx.xxxType: A Name: www Value: 104.xxx.xxx.xxx
These are provided for redundancy, but in most cases your custom domain will work identically with either or both, so long as you have at least one record for the bare domain and one for www.
If your custom domain is of the form
app.example.com, you can register the custom domain in your Bubble app, in Settings -> Domain.
Bubble will instruct you to create two records at your registrar. The records will be of the form
Type: A Name: app Value: 104.xxx.xxx.xxxType: A Name: app Value: 104.xxx.xxx.xxx
These are provided for redundancy, but in most cases your custom domain will work identically with either or both.
You can enter these at your registrar:
Once Bubble and Cloudflare verify your domain has been updated, your custom domain will work!
If you need to change your domain, you should first remove the current domain. Clicking on 'delete this domain name' will terminate the connection between the application and the domain. Note that your domain will still point to Bubble's server until you remove the DNS records in the registrar service. A Bubble page will be displayed with a message indicating there is no app linked to this domain. Once you have removed the domain, you can add a new domain as described above.
Note that if you remove a domain and want to use an appname.bubbleapps.io domain as initially happens, you may have to clear the browser cache, as the redirection is usually cached at the browser level.
If you created your account after October 2019, SSL is mandatory. If you are on a Legacy (pre-2019) Personal Plan and higher, you can activate SSL encryption on your custom domain. Note that all apps hosted on a bubbleapps.io subdomain also offer SSL support on all plans. Using SSL encryption lets you guarantee to your users that no one can intercept traffic between them and your site, and protects their private information. SSL encryption also helps with search engine rankings, and can be required to use some features (access to geolocation on Chrome, using Stripe payments, etc.).
Once you have properly configured your domain and that Bubble has validated the A records, you can start the process. To have SSL activated on your site, enable the checkbox.
This change can take up to one hour to propagate. For customers using Cloudflare, SSL is mandatory.
The moment you register your custom domain with Bubble and Cloudflare, your domain is registered with both services. In order for it to work correctly, Cloudflare needs to validate that your DNS entries point to their servers.
When you update your DNS records (adding, removing, or renaming a record), the length of time they stay available is determined by the record's TTL (time-to-live) value.
Let's say you change a record at your registrar, and that record has a TTL of 1 hour. After 1 hour, you can be certain that that server is reporting your new record to the internet. However, there are many name servers on the internet, and all of them will need to have your most up-to-date record. On average, you can expect your records to be broadcast across the internet within twice the length of your TTL. So if your TTL is 1 hour, expect your record to be everywhere after 2 hours.
Once your record has been updated everywhere, Cloudflare will be able to verify that you own the domain, and your app will become active.
If you're having problems that you think might be caused by Cloudflare, you can temporarily disable Cloudflare by changing your DNS records from
A 104.xxx.xxx.xxx to the A record you were previously assigned.
When you've identified what the problem was and are ready to turn Cloudflare back on, delete the A record and replace it with the A records Bubble provided you.
If you click on "Advanced" and then look at the certificate details, and the certificate is of the form
ssl123456.cloudflare.net, your DNS entry is pointing to the correct place, but Cloudflare has not validated your domain yet. Please wait an hour and check again.
The first, to check to see if your domain records have propagated, is the Google DNS lookup tool.
When you've changed your domain records, you can go to the A record tab to check to see if your A record has propagated.
mywebpage.us. 299 IN A 126.96.36.199mywebpage.us. 299 IN A 188.8.131.52
You can also take advantage of a service like What's my DNS, which tests your custom domain from many locations all over the world. It's not uncommon to see a few blank entries on this page; what you're looking for is any records that return an error (red X) or different results than you are expecting.
Cloudflare serves a page on a certain route on every site hosted on their domain at
/cdn-cgi/trace. You can see bubble's page at bubble.io/cdn-cgi/trace; replace 'bubble.io' with your own custom domain (once it loads) to see if it's working.
The output should look somewhat like this:
Go to the Google DNS lookup tool's CAA tab and check to see if your bare domain (e.g.
example.com) has a CAA record. A CAA record restricts which certificate providers can issue certificates for your domain. (Only about 1% of Bubble apps have a CAA record.)
For instance, when you look up
google.com with this tool, you can see the following record:
id 61662opcode QUERYrcode NOERRORflags QR RD RA;QUESTIONgoogle.com. IN CAA;ANSWERgoogle.com. 21599 IN CAA 0 issue "pki.goog";AUTHORITY;ADDITIONAL
This means that only
pki.goog is allowed to issue certificates for sites across the
SSL Certificate issuance is a critical part of making your site work on Bubble and Cloudflare, so if you find a CAA record, delete it. Your site should begin working in a matter of minutes.
If you are a Legacy Customer who wasn't using SSL prior to switching over to Cloudflare, some of Bubble's servers won't have your updated certificate available to them. A 525 error happens when the Origin Server (where your app is hosted on Bubble) serves nonsecure content (http) to a server that is expecting secure content (https). We refresh your SSL and certificate settings on all servers once per hour, so if you've recently changed your settings wait and try again.
Cloudflare has to verify that your A records are pointing to Bubble's IPs. If you're sure your A records are correct, Cloudflare will schedule a re-check of your records for several days (starting at 1 minute intervals, increasing to a maximum of 2 hours between checks). If, after 2 hours, your site is still showing 1001 errors, go to Bubble, delete your custom domain, wait one minute, and re-create it.
The most common cause of 1014 errors is when you're using Cloudflare for DNS, and you're using an "orange cloud" (proxy) setting. Click the orange cloud to turn off proxying (resulting in a grey cloud).
You can search the forum to see if anyone else has had the same issue as you.
If you can't find an answer here or there, submit a bug report.