Customize your Portal's domain

 

V12 4:24 Start+.svg

 

Using the steps below, makers with admin access can customize a portal's domain.

Note: We recommend using Cloudflare as your DNS provider. The only provider-specific instructions in this article relate to Cloudflare.

In this article:

Create a custom CNAME record with your DNS provider

If you're using a provider that isn't Cloudflare, make sure it supports SSL (AWS Cloudfront. for example).

  1. Change your domain nameservers to point to the provider you will be using. Here is documentation on how to change your domain nameserver to Cloudflare.
  2. Wait for DNS propagation. DNS changes can take up to 72 hours to take effect (but are typically much faster).
  3. Go to the DNS section on your provider's website and add a CNAME record for your public portal custom domain. The name is based on the first part of your custom domain, so if your custom domain is roadmap.example.com, use ‘roadmap‘.
  4. Point the CNAME record at Productboard’s portal domain: portal.productboard.com.
Warning: It is NOT recommended to enable Cloudflare's orange “Proxy” option as Productboard already uses Cloudflare CDN and it might cause additional issues. Please refer to the troubleshooting section below if you have issues with the proxy enabled.

Checking CAA records

Productboard will automatically issue a certificate for your custom domain using Cloudflare’s integration with the Let’s Encrypt certificate authority. This ensures Let’s Encrypt can safely generate a certificate for you. If you do not use CAA records, feel free to skip ahead.

CAA DNS records are used to restrict which certificate authorities can generate certificates for your domains. Please check your DNS zones for CAA records. You can use online tools such as this one from entrust.com.

If you do use CAA records, please make sure you are allowing letsencrypt.org. This means having a CAA record such as 0 issue "letsencrypt.org" for your domain or any of its parent domains. For example, if your custom domain is portal.example.com, it is also inheriting CAA records from example.com.

Warning: you cannot place CNAME and CAA records at the same level. Your CAA records must be placed at a higher level to be effective. For example, a portal at portal.example.com must have CAA records set at example.com. If your internal policy forbids Let’s Encrypt, please contact Productboard Support. We might be able to use an alternate authority or guide you in setting up your own TLS proxy.

The example below shows Cloudflare's process for adding a CAA record for productboard.com to the list of CAA records, which currently includes only amazon.com.

Untitled (4).png

Set up a custom domain on your Productboard workspace

  1. Go to your Productboard workspace.
  2. Go to the portal you wish to share.
  3. Click Share.Screen Shot 2023-04-05 at 4.09.10 PM.png
  4. In Portal share settings, select Public and toggle on Host Portal on your domain.
  5. Add your custom domain and click Save.

Screenshot_2020-05-11_at_15_48_32__1_.png

Once saved, changes will be deployed on our back end. It might take up to 30 minutes for changes to take effect. Wait 30 minutes and try to visit the custom domain for your public portal.

If you see your public portal on your custom domain, your portal is fully secured and ready to go. Users visiting your portal will see the green lock icon in their browser, letting them know the site is secure! ✅

Note: Portal sharing options apply only to the portal from which you access them. That means you can have several different portals with their own custom domains going at once!

Troubleshooting

HTTPS is not working

Symptoms:

  • Cloudflare's error code for this is 1001.
  • Other DNS providers will throw other errors, SSL errors, or display an unexpected page.
Resolution

Please wait at least 30 minutes after making any DNS changes for results to appear.

If nothing happens, your provider may be having problems generating a certificate for your custom domain via Let’s Encrypt or validating your CNAME record internally.

First, ensure you have no CAA records blocking Let’s Encrypt from issuing a certificate. If you have CAA records installed for your domain, please make sure one of your CAA records includes 0 issue "letsencrypt.org". Please mind that CAA records are frequently placed at level 2 domains, so for example if your custom domain is portal.example.com, your CAA record might be at example.com.

If you are using the orange proxy option on Cloudflare or another proxy in between, try removing said proxy temporarily to see if that fixes the issue. Your proxy might be blocking Let’s Encrypt’s validation bot or Cloudflare’s own domain validation bot.

If the issue still persists, please disable your custom domain in Productboard, wait 30 minutes, then enable it again. Cloudflare uses a backoff schedule if your domain fails to validate for some time and it can take up to 24 hours. Re-enabling your domain can trigger the validation sooner.

Cloudflare Rocket Loader conflict

Symptoms:

  • Your portal appears blank after deployment and you can see a green lock icon in the browser.
Resolution

Open DevTools in your browser.

rocket_loader_error.png

If you see that the rocket-loader.mins.js script is not allowed to load, turn off the Rocket Loader script in your Cloudflare settings by going to Cloudflare > Speed tab > Optimalization > scroll down to Rocket Loader > click Turn off.

rocket_loader_settings.png

See also:

Was this article helpful?
3 out of 20 found this helpful

Comments

0 comments

Article is closed for comments.

Articles in this section

Our Support hours:
Monday to Friday from 9:00 am - 2:00 am CET. Monday to Friday from 0:00 am - 5:00 pm PST.
Productboard Academy
Become a Productboard expert with self-paced courses, quick tip videos, webinars and more.
Product Makers Community
Connect with product leaders, share and find product jobs, and learn how to approach similar challenges. Come join our Product Makers community.