Domains, DNS & TLS
Get DNS right before asking the host to serve HTTPS.
When a project does not need a domain
In v1.0.0, a Web/API project can leave domains empty. With no existing managed route, deployment skips project Nginx/Certbot work. Removing the last domain removes an existing managed route with validation and reload; the application service keeps its port. External IP:port access depends on the application bind address and host firewall; omitting a domain does not open a public port. Workers cannot have project domains. The Portal dashboard domain is still required for production installation.
Connect a domain
Add up to ten domains in a project and point their A/AAAA records at the host. Check resolution from the actual server, not just your laptop. HTTP-01 needs inbound port 80. Use DNS-only during initial certificate issuance if a proxy interferes; verify origin HTTPS before enabling a strict proxy configuration.
Managed configuration
Portal manages its own Nginx files, validates configuration before reload and restores managed routing on failure. It does not offer arbitrary Nginx directives or a config-diff editor. Production Portal binds loopback 3100 and public requests enter through Nginx.
Check the whole path
getent ahosts app.example.com
sudo nginx -t
curl -fsSI http://app.example.com/
curl -fsSI https://app.example.com/An HTTP redirect to healthy HTTPS is expected. DNS success alone does not prove reachability, certificate issuance or upstream health.