Troubleshoot custom-domain verification and HTTPS

Run a fresh check

1. Open Settings → Domain.
2. Compare every shown DNS record with your provider.
3. Correct any difference and wait for DNS to update.
4. Select Check now.

If the A record is wrong

Update it to the address shown by StoreMink. Remove other A records for the same host. Multiple addresses can make the site work for one visitor and fail for another.

If the certificate CNAME is missing

Copy the exact generated name and target. Check whether your provider added the domain twice or removed part of the host. Root and www use separate records.

If StoreMink reports CAA

Your domain has a CAA rule that does not allow Google's certificate authority. Add the CAA value shown by StoreMink, such as 0 issue "pki.goog", or remove the blocking CAA rule after checking with whoever manages the domain.

If certificate requests are rate-limited

Stop changing or repeatedly reconnecting the domain. Correct the records, wait for the period shown by StoreMink, and check later. Recreating certificates during a rate limit can make the wait longer.

When DNS is correct but HTTPS is still pending

Managed certificate issuance can lag behind DNS. StoreMink can reset a stale certificate attempt when it is safe, but it will not do that for a real CAA block or rate limit. You can close the page while background checks continue.