Troubleshooting custom domain

If you encounter any issue in setting up your custom domain, read this article to help you troubleshoot the most common causes.

Initial check

• Make sure that your domain is properly set up with your domain registrar and that you have a CNAME record pointing to cname.senja.cloud

• DNS changes can take up to 24 hours to propagate, but usually complete within an hour

• You can check your record's status anytime using a tool like dnschecker.org, or by running this from a terminal:

  dig yourdomain.com CNAME

Picking the right subdomain

• Choose a subdomain that isn't already pointed at another tool

• If you're already using something like testimonials.yourdomain.com for another platform (a course host, landing page builder, etc), reusing it for Senja will disconnect that other integration

• Pick a separate, unused subdomain instead, for example, if "testimonials" is taken, try "love" or "reviews"

Your domain is already associated with another Senja account

• If your domain is already associated with another Senja account, you will need to remove it from that account before you can add it to a new one

• If you're not sure which account your domain is associated with, please contact us and we'll be happy to help you out

My domain is stuck on "pending verification"

A few common causes:

• Still propagating: this is normal and usually resolves within a few hours, occasionally up to 24

• A typo in the DNS record: double check the host and target values match exactly what Senja generated, with no extra characters

• Your CNAME is pointing to the wrong location: it should point to cname.senja.cloud, nothing else

• Your domain is proxied through Cloudflare (or a similar CDN): see below

If everything looks correct and it's still pending after 24 hours, contact us and we'll take a look on our end.

I use Cloudflare and it won't verify

• If your domain's DNS is managed through Cloudflare, make sure the record is set to DNS only (grey cloud), not Proxied (orange cloud)

• A proxied record routes through Cloudflare's network first, which blocks Senja from verifying it

• There's no error message, it just stays pending indefinitely

• To fix it:

  • Go to your Cloudflare DNS settings

  • Find the CNAME record you added for Senja

  • Click the cloud icon next to it to switch it to DNS only (grey)

  • Save and allow a few minutes for the change to take effect

The domain field won't save

• Make sure the DNS record is set up correctly on your provider's end before saving in Senja

• The domain won't save until it can find and verify a matching record

• If you've just added the DNS record, give it a few minutes to propagate before trying again

Your domain has been flagged as suspicious

• We use a third-party service to protect our platform from spam and abuse

• Occasionally, this service may incorrectly flag a legitimate domain as suspicious

• When this happens, you may be blocked from adding new members to your account

• If you believe your domain has been incorrectly flagged, contact us and we'll work with the third-party service to resolve it

ERR_SSL_VERSION_OR_CIPHER_MISMATCH error

• If you’re getting this error, then Senja wasn’t able to set up an SSL certificate pointing to your domain

• This usually happens because you might have CAA records set up that restrict SSL certificates from being issued to your domain

• To fix this, you'll need to either:

  • Remove any CAA records that are blocking the SSL certificate, or

  • Add Senja’s CAA records that allows the SSL certificate to be issued

CNAME cross-user banned error

• This is a different Cloudflare issue from the proxy one above

• It happens if you have zone holds enabled on your Cloudflare account

• When that's on, Cloudflare won't allow you to CNAME to other Cloudflare zones (like Senja's)

• You can temporarily toggle it off by following this guide

• Once your domain is connected, you can turn zone holds back on

There is a problem with your CNAME configuration

• If you have checked the above and you are still having problems, there may be an issue with your CNAME configuration

• Please double-check your CNAME records to ensure that they are pointing to the correct location