Config generator

The config generator has two modes: HTTPS server snippets, or a deploy-client config.yaml plus install commands. Open it at Config generator.

Automated deployment config

Use this to connect a host to Automated deployment.

1. Switch to automated deployment

   Use the top switch, or open the tool with ?mode=deploy.

2. Fill server connection

   Use the current account Access Key. Set the HTTP-01 port to match the challenge listener.

3. Enable local and panel targets as needed

   • Nginx / Apache: certificate directories.
   • RustFS: TLS directory, optional SSH.
   • fnOS: local or SSH.
   • 1Panel / BT Panel / SafeLine: admin URL and API key. You can skip TLS verify for a trusted self-signed panel.

4. Add cloud and DNS providers as needed

   Certificate deployment and DNS configuration share the local provider credentials. One-click DNS-01 CNAME configuration supports Cloudflare, Alibaba Cloud DNS, Tencent DNSPod, Huawei Cloud DNS, Baidu Cloud DNS, JD Cloud DNS, and Volcengine DNS. For Cloudflare, use an API Token scoped to the required zones with Zone:Read, DNS:Read, and DNS:Edit. For other providers, grant the DNS read and create permissions shown in the config generator. Store only the required AccessKey / Secret or token. Do not put CDN or load-balancer IDs in the file; discover and bind those resources later on the automated deployment page.

5. Download and install

   After validation, download config.yaml and run the install, install-config, and start commands on the target host. The full file contains secrets; download it only on a trusted device.

Tip

DNS credentials stay in the deploy CLI’s local config.yaml and are not uploaded to the platform. Grant separate permissions for certificate deployment when needed; DNS CNAME configuration does not require certificate-center or CDN permissions.

Caution

A real config.yaml includes the Access Key, SSH password, panel token, or cloud secret. Do not paste it into chat, tickets, or Git.

HTTPS site config

Generate an Nginx or Apache TLS snippet. Domains can be prefilled from a managed or self-signed certificate.

1. Switch to HTTPS site config

2. Choose the server

   Nginx or Apache.

3. Enter domains and certificate paths

   Primary name, aliases, certificate path, and private-key path. You can also pick an issued certificate to prefills domains.

4. Copy the result

   Paste the snippet into the site config, run nginx -t or the Apache equivalent, then reload.

Tip

For HTTP-01, the automated-deployment mode also emits Nginx / Apache reverse-proxy snippets that forward challenge requests to the client listener.