Onboard one domain
Run a read-only preflight and review planned changes before execution.
Chapters · Onboard one domain
1. Select and inspect
Open 自动接入, choose an eligible domain and target settings, then run preflight. Review DNS, existing resources, website type and planned operations. Preflight does not create resources.
2. Resolve conflicts and confirm
If root DNS, same-name resources or website settings conflict, have an administrator review the existing configuration before repeating preflight. Do not delete existing records merely to bypass a conflict. Confirm execution when preflight passes.
3. Follow the stages
The workflow creates or reuses a compatible Baota site, ESA service record, SaaS hostname and origin Host rule. It then preserves existing Namecheap DNS records while adding the root CNAME.
4. Wait for certificates
ESA status is checked every 10 seconds for up to 10 minutes. The hostname must be active and its edge certificate OK before proceeding. The tool then checks Baota SSL, requests and installs an ACME certificate if needed, and finally applies selected cache and Gzip rules.
5. Check completion
Review each stage and confirm the domain, DNS, ESA certificate and Baota SSL match the intended site. Compatible existing resources are reused; a site with working HTTPS does not receive a duplicate certificate request.