Domain Issues
Fix custom domain issues -- stuck on "Pending," SSL certificate errors, CNAME misconfigurations, and domains loading the wrong site.
Custom domains need a correctly configured CNAME record and a valid SSL certificate.
Domain Not Verifying
If your domain shows as "Pending" or "Not verified":
Verify your CNAME record points to your Jamdesk URL:
docs.example.com CNAME your-project.jamdesk.appDNS changes can take up to 48 hours to propagate worldwide.
Use a tool like dig or dnschecker.org to verify your records.
SSL Certificate Errors
Certificate not provisioning
Jamdesk uses Let's Encrypt for automatic SSL. If provisioning fails:
- Verify DNS is correctly configured
- Wait 15 minutes for provisioning
- Check that your domain isn't blocked by firewall rules
Certificate expired
Certificates auto-renew. If yours expired:
- Go to Settings → Domains
- Click Refresh Certificate
- If it fails, contact support
Mixed content warnings
Your domain works but shows security warnings:
- Check for
http://links in your content - Update all asset URLs to use
https://
Domain Not Loading
"Site can't be reached"
- Verify DNS records are correct
- Check domain wasn't deleted in Jamdesk
- Clear your browser DNS cache
Wrong site showing
Your DNS may be pointing to an old server:
- Update CNAME to your Jamdesk URL
- Remove any conflicting A records
- Wait for DNS propagation
Common DNS Mistakes
Jamdesk requires a CNAME record, not an A record. CNAME allows us to route traffic correctly.
Don't include https:// in your CNAME value. Use just the domain:
✓ your-project.jamdesk.app
✗ https://your-project.jamdesk.app
If you have both A and CNAME records for the same subdomain, remove the A record.
Subpath Domains
For domains at a subpath (e.g., example.com/docs):
- Configure a reverse proxy (Cloudflare, nginx, etc.)
- See Subpath Hosting for setup instructions
Subpath configuration requires additional setup outside of Jamdesk.