Domains and HTTPS
1. Point the domain
Section titled “1. Point the domain”At your domain provider (Registro.br, Cloudflare, Hostinger…), create an A record with the name (e.g. shop)
pointing to the IP of the machine where the service runs.
With Cloudflare or Hostinger connected, the panel creates the record for you: see Automatic DNS.
2. Connect it to the service
Section titled “2. Connect it to the service”In the service’s Domains (Domínios) tab:
- enter the address (e.g.
shop.yourcompany.com); - enter the app’s internal port (e.g.
3000); - leave HTTPS on.
The machine’s proxy starts answering at that address and requests the certificate from Let’s Encrypt. It is renewed on its own.
Domain states
Section titled “Domain states”| State | What it means |
|---|---|
| Not checked (Não conferido) | the panel has not tested the DNS yet |
| Waiting for DNS (Aguardando DNS) | the domain does not point to the machine yet; check the A record |
| Waiting for HTTPS (Aguardando HTTPS) | the DNS is correct and the certificate is being issued |
| Live (No ar) | answering over HTTPS |
Paths and headers
Section titled “Paths and headers”You can connect the same domain to different services by path (e.g. /api goes to the API) or by a
header rule.
Your own certificate
Section titled “Your own certificate”Have a purchased or wildcard certificate? Register it in Domains → Certificates (Domínios → Certificados) and the proxy uses it instead of Let’s Encrypt.