Hello Vercel Community,
I am experiencing an SSL/TLS certificate provisioning issue for www.taxilink.co.ls on my Vercel project "taxilink".
The apex domain https://taxilink.co.ls is already working successfully over HTTPS and returns HTTP 200 from Vercel.
The problem affects www.taxilink.co.ls.
Vercel is configured to redirect:
www.taxilink.co.ls → taxilink.co.ls
using a 308 Permanent Redirect.
The DNS record for www is:
CNAME www → ace94c5f0b2e410c.vercel-dns-017.com
Cloudflare proxying is disabled (DNS only).
The authoritative nameservers are:
duke.ns.cloudflare.com miki.ns.cloudflare.com
Both authoritative nameservers resolve the www CNAME correctly.
Public DNS resolution also works through both Cloudflare (1.1.1.1) and Google (8.8.8.8).
HTTP requests to:
reach Vercel successfully.
However, HTTPS for www fails because the certificate has not been provisioned.
When I manually run:
vercel certs issue taxilink.co.ls www.taxilink.co.ls
Vercel reports:
"We could not generate a cert for www.taxilink.co.ls because the required http-01 challenge failed. DNS problem: NXDOMAIN looking up A for www.taxilink.co.ls; DNS problem: NXDOMAIN looking up AAAA for www.taxilink.co.ls."
This conflicts with Vercel's own domain verification.
Using Vercel CLI 59.26.0:
vercel domains verify www.taxilink.co.ls --project taxilink --format json
returns:
status: ok reason: configured_correctly domainStatus: configured-correctly configurationStatus: configured-correctly ok: true issues: [] misconfigured: false configuredBy: CNAME acceptedChallenges: ["http-01"] domainOwnership: current-scope
The project is also reported as:
attached: true verified: true
Vercel recommends exactly the CNAME that is currently configured:
CNAME www → ace94c5f0b2e410c.vercel-dns-017.com
As another validation test, requesting an HTTP ACME-style path on www reaches Vercel and returns a Vercel response rather than failing DNS resolution.
The Vercel Agent initially suggested that certificate issuance was failing because co.ls was not present in the Public Suffix List. However, co.ls is already present in the current Public Suffix List, so that explanation does not appear applicable.
At this point there appears to be a discrepancy between:
- Vercel's domain verifier, which reports the domain as correctly configured and verified;
- authoritative and public DNS, which resolve the hostname;
- Vercel's HTTP infrastructure, which receives requests for the hostname; and
- the certificate provisioning process, which reports NXDOMAIN during the HTTP-01 challenge.
Could a Vercel team member please investigate the certificate provisioning/HTTP-01 validation state for www.taxilink.co.ls?
I have intentionally not changed the currently working DNS configuration because Vercel's own verifier reports it as correct.
Thank you.
