Domains, redirects, certificates, and Nginx.
An application has exactly one primary hostname and can also serve alias and redirect hostnames. ServerChirp generates its Nginx virtual host from application state, validates the configuration, and reloads Nginx only after validation succeeds.
Open the application's Domains page and add the hostname without a scheme or path. For an apex domain, choose whether to serve both apex and www or redirect one to the other.
Point DNS at the server before issuing a production certificate:
example.com. A 203.0.113.10
www.example.com. CNAME example.com.DNS can take time to propagate. ServerChirp validates resolution but cannot update records at a provider you have not connected.
Choose one of the supported certificate paths:
The dashboard shows issuer, expiry, covered hostnames, and whether changed domains require the certificate to be reprovisioned.
Applications can allow HTTP, permanently redirect HTTP to HTTPS, or enable HSTS. HSTS supports max-age, includeSubDomains, and preload behavior.
Enable HSTS only after every required hostname and subdomain works over HTTPS. Browsers remember the policy even after you change the server configuration.
Ordered snippets extend the generated virtual host at controlled locations. Recipes cover Cloudflare real IPs, redirects, CORS, proxy paths, upload sizes, WordPress hardening, rate limiting, and maintenance mode.
ServerChirp validates the complete Nginx configuration before activation. A broken snippet fails the operation without replacing the last valid configuration.
Enable Basic Authentication to protect a preview or internal application. The stored password is encrypted and is not returned by API reads.