Set a custom domain

Set a custom domain for your docs sites

This feature is available on Premium and Ultimate site plans.

This page shows how to configure a custom domain and subdomain. If you would like to configure a custom subdirectory (such as example.com/docs), see the Setting a custom subdirectory page.

By default, your sites are accessible on a [subdomain].gitbook.io domain.

You can customize this by setting a custom domain, meaning your audience can access your documentation on a chosen domain.

1

Choose a subdomain

When choosing a subdomain, you can either use www or a custom one. Some commonly used subdomains are:

• docs.example.com

• help.example.com

• developers.example.com

2

Initiate the custom domain setup

Navigate to the site for which you want to set the custom domain. Click Settings, then choose Set up a custom domain.

From here, you'll see a window where you can enter the custom domain you chose in the first step. Type it out and click Next.

3

Configure the DNS

At this stage, you'll see a window with three fields: Type, Name, Target.

Those are the details you'll use to set your custom domain in your DNS provider. This is done outside GitBook, in the provider you are using for your domain.

Copy the contents of the Name and Target fields to use in your DNS provider. Each provider is different, so when in doubt, check directly with them how to add this record. You should be able to pick the Type of record from a list in your provider.

After adding the record, it might take some time for the changes to propagate. We recommend waiting at least 1 hour before moving to the next step. Click Next when you are ready.

4

Finalize your setup

After adding the record and it being propagated, it's time to go live! GitBook will verify the domain, the record you added and will automatically configure the SSL certificate for your domain.

Once done, you'll receive a notification and can click Finish. You can also close the window if you need, and we'll send you a notification once the process is done on our side.

Troubleshooting

Setting up a custom domain can occasionally run into obstacles. Below, we outline frequent problems encountered during this process and provide detailed solutions to each of them.

SSL error: an error occurred when provisioning your SSL certificate.

When a custom domain is set for your organization, collection, or space, we set up an SSL certificate on our end so that your documentation will load securely, over HTTPS. This happens automatically when you set your custom domain — you do not need to purchase or configure an SSL certificate.

Occasionally errors occur at this stage, usually when the CNAME record for the custom domain hasn't propagated.

In these cases, we can recommend the following:

1. Check that your CNAME record is set up correctly. Please review our page about configuring DNS to help you with this. If the CNAME record is incorrect, we won't be able to configure the SSL certificate and complete the custom domain set-up.

2. Allow at least one hour between configuring the CNAME record and finalizing the custom domain setup.

3. Verify if the CNAME has propagated. You can try using a third-party DNS lookup tool, such as WhatsMyDNS, to find out what the servers believe to be correct for your correct CNAME record.

4. If you are using Cloudflare, please confirm that you don’t have the record proxied as explained here.

Domain already connected error: your subdomain is already configured for different content.

A custom domain assigned to a site must be unique. Attempting to use the same custom domain in more than one location will result in an error.

If this happens, you can click the link within the error message to look at the content the custom domain is already connected to. This may help you to decide what to do next.

It’s also possible that you might not have access to the content — if that’s the case, contact the support team and they can help you with your next steps.

The solution to this error will always be one of two things, however:

1. Choose a different custom domain; or

2. Disconnect the custom domain from the content it is already connected to, then reconnect it to the new content.