Domain and SSL issues

Fix DNS propagation, certificate status, default hostnames, and routing mismatches for custom domains on Services.

Written By Zoro

Last updated 3 days ago

Custom domains and Services

Custom domains attach to a Service inside an Application and Environment. Control-plane hostnames for self-hosted installs are separate; use Control plane domains and SSL under Self-Hosting dFlow in the sidebar for the dashboard URL itself.

Certificate stays pending or fails

  1. Confirm DNS points to the targets the UI shows for this Service (record types and names must match exactly).
  2. Wait for DNS propagation (often minutes, sometimes longer depending on TTL and provider).
  3. Remove conflicting old records (duplicate A/AAAA/CNAME) that send traffic elsewhere.
  4. If you changed DNS recently, trigger a renew or re-check from the product only after propagation stabilises (Domains and SSL under Deployments and Operations in the sidebar).

Browser shows wrong site or TLS warning

  1. Verify the hostname you typed matches the hostname attached in dFlow.
  2. Check whether a default hostname is set when multiple domains exist on one Service.
  3. Mixed HTTP/HTTPS or proxy headers: review Proxy and routing under Deployments and Operations in the sidebar for Nginx parameters if you customised them.

404 or routing to another Service

Hostnames are scoped to the Service you configured. A hostname pointing at the wrong Environment or Application will not show the app you expect. Trace Application → Environment → Service in the UI.

Apex vs www

Use separate host rows if you need both, or CNAME/ALIAS patterns your DNS provider supports. Follow the records the dFlow UI documents for your case.

Self-hosted operators

If the problem is Traefik or the control plane certificate, not an app Service hostname, use Self-hosting troubleshooting under Self-Hosting dFlow in the sidebar and Control plane domains and SSL under Self-Hosting dFlow in the sidebar.

Related