Auto-populate failed
What to do when Reloop Domain Connect Auto-populate errors, popups are blocked, or the provider has not onboarded the template.
Messages you might see
| Message (paraphrased) | Meaning | Action |
|---|---|---|
| Provider doesn’t support automatic configuration | No Domain Connect / no sync UX | Manual setup |
| Supports Domain Connect but hasn’t onboarded Reloop’s template | Protocol yes, Reloop template no | Manual setup |
| Failed to start auto-configuration / signing key | Reloop server-side apply URL issue | Retry later or manual; contact support if persistent |
| Popup blocked / nothing opened | Browser blocked the provider tab | Allow popups for Reloop, click again |
| You cancelled at the provider | Consent denied | Retry Auto-populate or configure manually |
When Auto-populate is offered
Auto populate appears when Reloop recognizes nameservers for a host where Reloop’s Domain Connect template is known to work today: Cloudflare, Vercel, Domain Chief, and NameSilo. Clicking the button also runs live discovery as a safety check. See Auto-populate DNS.
Other Domain Connect–capable hosts may still need manual setup until Reloop’s template is available there and the dashboard offers the button.
Fallback
Every domain can be configured manually with the same records. Auto-populate is convenience, not a hard requirement.
Was this page helpful?
- Need help? Contact Support.
- Chat with Reloop developers on Discord.
- Check out our changelog.
- Questions? Contact Sales.
- LLM? Read llms.txt.