Skip to main content
If a domain remains pending or fails HTTPS setup:
  1. Confirm that the full hostname in Biqli matches the DNS record.
  2. Compare the record type, host, and target with the current instructions.
  3. Remove conflicting records for the same hostname.
  4. Disable DNS proxies, redirects, and Workers during verification.
  5. Wait for DNS propagation, then check the status again.
For an SSL failure, keep the correct DNS record in place. If the status still does not recover, contact support with the domain and workspace name. Never send registrar credentials.

​
Check authoritative DNS

Make sure you edited the provider responsible for the nameservers, not merely the registrar where the domain was purchased. Public DNS lookup tools should show the record Biqli requested.

​
Check the hostname

go.example.com and www.go.example.com are different hostnames. The name in Biqli, DNS, browser, and any certificate-related record must match exactly.

​
Check HTTPS and redirects

Disable provider forwarding, proxying, Workers, and redirect rules during diagnosis. A loop often means the proxy and origin disagree about HTTPS or a rule sends the hostname back to itself. When contacting support, include the exact hostname, current Biqli status, DNS provider, public record values, and an approximate time. Do not include account passwords, registrar recovery codes, or API tokens.

​
Frequently asked questions

​
Does buying the domain verify it?

No. Biqli must see the exact DNS records for the hostname.

​
Should I repeatedly delete and reconnect it?

No. Keep the correct record stable while DNS and certificate systems process it. Reconnection can restart diagnosis without fixing the cause.

​
Can a VPN affect DNS editing?

It can affect what your browser or resolver sees, but authoritative public DNS must still contain the required record.