# Custom domain pending — HTTPS not working for kcmobilenotarypros.com
**URL:** https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331
**Category:** Teable Discussions
**Tags:** bug
**Created:** [September 30, 2026, 9:28pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331 "2026-09-30T21:28:58Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@marshallluettgen](https://community.teable.ai/u/marshallluettgen)
#### Post date: [September 30, 2026, 9:28pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/1 "2026-09-30T21:28:58Z")
I connected [kcmobilenotarypros.com](http://kcmobilenotarypros.com) to app appIajCkhE7yVfo2xAj. Its DNS A record points to 76.76.21.21, and the new website loads over HTTP. However, HTTPS fails and Teable still shows the custom domain as Pending after almost ten hours. Please investigate domain verification and SSL certificate provisioning.
---
### Author:  [@teable-bot](https://community.teable.ai/u/teable-bot)
#### Post date: [September 30, 2026, 9:30pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/2 "2026-09-30T21:30:04Z")
Thanks for reporting this. It’s logged as **T7657** , and we’ll post updates in this topic as it moves along.
---
### Author:  [@Sky](https://community.teable.ai/u/Sky)
#### Post date: [October 2, 2026, 4:04am UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/3 "2026-10-02T04:04:01Z")
Hi marshallluettgen, the SSL certificate has been issued and [https://kcmobilenotarypros.com](https://kcmobilenotarypros.com) is now accessible. No DNS changes are needed.
The “Pending” status doesn’t refresh automatically — please open the Custom Domain dialog in your app and click “Verify DNS” once to update it.
---
### Author:  [@marshallluettgen](https://community.teable.ai/u/marshallluettgen)
#### Post date: [October 7, 2026, 10:24am UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/4 "2026-10-07T10:24:31Z")
_Hi Sky,_
_Following up on ticket **T7657**. The main website at [https://kcmobilenotarypros.com](https://kcmobilenotarypros.com) is working, and the custom domain shows Activated._
_However, [https://www.kcmobilenotarypros.com](https://www.kcmobilenotarypros.com) still shows a certificate error because the certificate does not cover the `www` address. We confirmed this again on October 7._
_Could you please resolve the `www` certificate coverage and ensure both HTTP and HTTPS versions of `www` redirect safely to [https://kcmobilenotarypros.com?](https://kcmobilenotarypros.com?)_
_We have made no further DNS changes, as advised. Please let us know the current status and expected resolution time._
_Thank you,_
-
Marshall\*
---
### Author:  [@Sky](https://community.teable.ai/u/Sky)
#### Post date: [October 10, 2026, 1:09pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/5 "2026-10-10T13:09:37Z")
Hi marshallluettgen, I checked both hostnames.
[www.kcmobilenotarypros.com](http://www.kcmobilenotarypros.com) is already attached to your app and set to redirect to [https://kcmobilenotarypros.com](https://kcmobilenotarypros.com). The only missing piece is its certificate, and that’s blocked by the DNS record: www is currently a CNAME to [kcmobilenotarypros.com](http://kcmobilenotarypros.com), which our hosting layer doesn’t accept as a valid target, so no certificate gets issued for it.
Please change the www record at your DNS provider to:
CNAME www → [cname.vercel-dns.com](http://cname.vercel-dns.com)
Leave the apex A record (@ → 76.76.21.21) as is. Once the change propagates (minutes, up to about an hour), the www certificate is issued automatically and both http and https www will redirect to [https://kcmobilenotarypros.com](https://kcmobilenotarypros.com).
Reply here once it’s updated and I’ll confirm from our side.
---
### Author:  [@marshallluettgen](https://community.teable.ai/u/marshallluettgen)
#### Post date: [October 15, 2026, 1:34pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/6 "2026-10-15T13:34:52Z")
T7657 Escalation: www SSL Certificate Still Failing After DNS Update
Teable Discussions
bug
post by marshallluettgen just now
marshallluettgen
Business · 3 seats
1m
Hi Sky and Support,
Please escalate ticket T7657 to the team responsible for hosting and domain certificates.
On October 10, I updated the GoDaddy record as instructed:
CNAME www → [cname.vercel-dns.com](http://cname.vercel-dns.com)
A @ → 76.76.21.21 remains unchanged.
As of October 15 at 8:26 a.m. Central, [https://kcmobilenotarypros.com](https://kcmobilenotarypros.com) works, but [https://www.kcmobilenotarypros.com](https://www.kcmobilenotarypros.com) still fails because the certificate does not cover that hostname.
Please investigate why the certificate has not issued, confirm who is handling this, and provide an expected resolution time. Please also verify both HTTP and HTTPS www redirects once it is fixed.
Thank you,
Marshall
---
### Author:  [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [October 23, 2026, 4:03pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/7 "2026-10-23T16:03:48Z")
Hi @marshallluettgen,
Sorry for the delay, and for the confusion caused by our earlier guidance. Changing the `www` CNAME was not the fix, and we should have caught that sooner.
Here is the actual situation: Teable currently supports binding one custom domain per app, and `kcmobilenotarypros.com` is the domain bound to your app. That part is working correctly: it has a valid certificate, and HTTP redirects to HTTPS. Because only one hostname can be bound, Teable does not provision a certificate for [`www.kcmobilenotarypros.com`](https://www.kcmobilenotarypros.com), so HTTPS on `www` will keep failing regardless of the DNS value.
To keep `www` working, please set up forwarding from `www` to `https://kcmobilenotarypros.com` in GoDaddy. Forwarding normally replaces the current `www` CNAME record. Please leave the apex A record (`@ → 76.76.21.21`) as it is. Once forwarding is in place, HTTP on `www` will redirect to your main site. Whether `https://www` redirects cleanly depends on GoDaddy issuing a certificate for its forwarding, so please test both after the change. Reply here and we’ll verify them from our side too. If you’d rather avoid this, sharing only `https://kcmobilenotarypros.com` works today.
We’ve also noted that Teable could handle `www` alongside the apex domain on its own. If that matters to you, please add it as a feature request here on the community so others can upvote it.
Thanks for your patience.