Vercel SSL certificate stuck on generating status despite HTTPS working

Help
,
1

Problem

My domain www.kolab.lv (project: marketplace-frontend) has been stuck showing “Generating SSL Certificate” in the Vercel dashboard for 3+ days, but the SSL certificate is actually working perfectly - the site loads successfully via HTTPS.

Current vs Expected Behavior

Current:

  • Dashboard status: “Generating SSL Certificate” (stuck for 3+ days)
  • Site behavior: HTTPS works perfectly at https://www.kolab.lv
  • Apex domain kolab.lv: Shows “Valid Configuration” ✓
  • Vercel app domain: Shows “Valid Configuration” ✓

Expected:

  • Dashboard should show “Valid Configuration” for www.kolab.lv

DNS Configuration

✓ www.kolab.lv has ONLY a CNAME record pointing to marketplace-frontend-tau-seven.vercel.app
✓ NO A or AAAA records exist for the www subdomain
✓ DNS provider: Site.eu
✓ All DNS recommendations from Vercel docs have been implemented

Steps Already Taken

  1. Verified DNS records are correct (CNAME only, no conflicting A/AAAA records)
  2. Clicked “Refresh” in Domains settings multiple times
  3. Removed and re-added the domain
  4. Applied all troubleshooting recommendations from Vercel documentation
  5. Waited 3+ days for DNS propagation

Analysis

Vercel’s diagnostic tool reports:

Error: Multiple Networks Detected

IPv6 resolves to Site.eu (my DNS provider), which is normal behavior for CNAME records. The SSL certificate is clearly working (site loads with HTTPS), but the dashboard UI is not updating to reflect this.

This appears to be either:

  • Dashboard UI not syncing with actual certificate status
  • Vercel’s DNS checker seeing cached/stale DNS data
  • Internal SSL provisioning system issue

Request

Could someone from Vercel support or the community help investigate why the dashboard status is stuck, even though the certificate is working? There’s nothing more I can configure on my DNS side - this needs manual verification on Vercel’s end.

Account: Ojay’s projects (Hobby plan)
Project: marketplace-frontend
Domain: www.kolab.lv

5

I think you have A records pointing to Vercel and AAAA records pointing somewhere else, this is the error I’m seeing

IPv4 and IPv6 records resolve to different network providers (IPv4: STUB-103-149-168SLASH23, IPv6: SITE_BV)
2 Likes
6

Thank you so much, Jacob for your help! You were right, there were unnecessary A records pointing to a different provider, which was causing the conflict. I’ve removed them and everything works correctly now. Really appreciate the quick and accurate diagnosis!