Your custom domain kube-composer.com shows a white page while gorgeous-maamoul-daf273.netlify.app works fine.
- Go to Netlify Dashboard: https://app.netlify.com/sites/gorgeous-maamoul-daf273
- Navigate to: Site settings → Domain management
- Verify custom domain: Ensure
kube-composer.comis listed as a custom domain - Check SSL certificate: Make sure HTTPS is enabled and certificate is provisioned
You need to point your domain to Netlify's servers. Choose Option A (recommended):
Type: CNAME
Name: @ (or leave blank for apex domain)
Value: gorgeous-maamoul-daf273.netlify.app
TTL: 300
Type: A
Name: @ (or leave blank)
Value: 75.2.60.5
TTL: 300
Type: CNAME
Name: www
Value: gorgeous-maamoul-daf273.netlify.app
TTL: 300
After updating DNS records, wait 5-15 minutes and test:
# Check DNS resolution
nslookup kube-composer.com
# Should return Netlify's IP or CNAME
# Expected result: gorgeous-maamoul-daf273.netlify.app- In Netlify dashboard → Domain settings
- Scroll to HTTPS section
- Enable "Force HTTPS"
- Wait for SSL certificate to be issued (can take up to 24 hours)
After DNS changes:
- Clear your browser cache
- Try accessing in incognito/private mode
- Test from different devices/networks
-
Check Netlify deployment logs:
- Go to Deploys tab in Netlify dashboard
- Verify latest deployment was successful
-
Verify build output:
- Ensure
dist/index.htmlexists and has content - Check that all assets are properly built
- Ensure
-
Test direct Netlify URL:
- If
gorgeous-maamoul-daf273.netlify.appworks but custom domain doesn't - The issue is DNS configuration
- If
-
Check browser console:
- Open developer tools
- Look for any JavaScript errors
- Check if assets are loading properly
- DNS not propagated: Wait longer (up to 48 hours)
- SSL certificate pending: Wait for Netlify to issue certificate
- Wrong DNS records: Double-check CNAME points to correct Netlify URL
- Browser cache: Clear cache or test in incognito mode
- DNS changes: 5-30 minutes
- SSL certificate: Up to 24 hours
- Full propagation: Up to 48 hours
# Test DNS resolution
dig kube-composer.com
# Test HTTP response
curl -I https://kube-composer.com
# Test redirect
curl -I http://kube-composer.comYour site should be accessible at: https://kube-composer.com