Create a custom CNAME record with Cloudflare
Prerequisites - a free plan on Cloudflare is enough to set up a custom domain for your public Portal.
🚨 Important: DNS changes can sometimes take up to 72 hours to take effect, but are typically much faster.
- Set up Cloudflare as the resolver for your custom CNAME by changing your domain nameserver to Cloudflare.
- Go to the DNS section in Cloudflare and add a CNAME record for your public Portal custom domain.
- The name is based on the first part of your custom domain e.g. if your custom domain is portal.example.com, use ‘portal‘.
- Point the CNAME record at productboard’s Portal domain: app.productboard.com.
🚨 It is NOT recommended to enable the orange “Proxy” option as Productboard already uses Cloudflare CDN and it might cause additional issues. Please refer to our if you have issues with the proxy enabled.
In this article:
Set up a custom domain on your Productboard workspace
- Go to your Productboard workspace.
- Go to the Portal tab.
- Click on 'Share'.
- In Portal share settings, select ‘Public’, toggle on ‘Host Portal on your domain’, add the custom domain you've just set in Cloudflare, and then press ‘Save.’
Once saved, changes will be deployed on our back end. It might take up to 30 minutes for changes to take effect. Wait approximately 30 minutes and try to visit the custom domain for your public Portal.
💡 If you can 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 that the site is secure. ✅
If your Portal appears as a blank page after deployment and you can see the green lock icon in the browser, open DevTools in your browser.
If you can observe error:
rocket-loader.mins.js is not allowed to load, turn off settings for Rocket loader script in your Cloudflare settings, we don't support loading of this script. Go to Cloudflare → Speed tab → Optimalization → scroll down to Rocket Loader -> Click Turn off