Try or ByeTry or Bye

Payhip Custom Domain Not Working

Share
Workaround available Web Updated November 13, 2026Based on 3 user reportsHow we research

Quick answer

Use an A record for a root domain or a CNAME for a subdomain, remove conflicting old records, and wait up to 24-48 hours. Payhip creates the SSL certificate automatically after DNS is correct.

Most likely fix: Pick the correct record

How to fix it

Try these in order — the most common fix is first.

  1. 1. Pick the correct record

    1. Root domain (yourdomain.com): add an A record
    2. Subdomain (shop.yourdomain.com): add a CNAME record
    3. Follow Payhip's guide for your registrar (GoDaddy, Namecheap, Bluehost, etc.)
    Did this fix it?

  2. 2. Clean up and wait

    1. Delete older conflicting records
    2. Allow 24-48 hours for DNS updates
    3. If you use Cloudflare, try DNS only (grey cloud)
    Did this fix it?

  3. 3. Reconnect and ask for help

    1. On the Domains page, disconnect and reconnect the domain
    2. If SSL stays stuck, email contact@payhip.com
    Did this fix it?

Symptoms

The domain will not connect, the store does not load on it, or the browser shows a 'not private' or 'setting up SSL' message.

Why it happens

  • Wrong record type for root domain vs subdomain
  • Conflicting leftover A or CNAME records
  • DNS changes not yet propagated
  • Cloudflare proxy or registrar setting interfering
  • SSL certificate still being generated

This guide also covers

  • payhip custom domain not working
  • payhip ssl not private
  • payhip connect domain godaddy

Still not working?

If Payhip keeps failing, you're not alone. See every Payhip problem users report or the alternatives people switch to.

Done fighting Payhip? Our small team builds your own Payhip alternative, or any software you need: web, mobile, games, desktop. Price agreed together.

Talk to us
Fixed it? Share this guide

Other Payhip errors