Proxy and routing

How dFlow terminates TLS and routes HTTP to Services, and how to edit Nginx parameters on a Service.

Written By Zoro

Last updated 3 days ago

Traffic reaches your App and Docker Services through a reverse proxy layer on the Worker Node (Dokku-style routing in the current stack).

The dashboard exposes a Proxy tab so you can inspect and adjust Nginx parameters the platform maps onto that layer.

Default routing

  • Each Service gets a default hostname under the platform proxy domain (shown in the UI). That hostname is usually marked as the default domain on the Domains tab.
  • Custom domains add extra hostnames. The proxy matches the Host header and forwards to the correct Service on the node.
  • TLS for Letsencrypt certificates is tied to domain records you configure; see Domains and SSL.

On dFlow Cloud, a shared proxy tier may synchronize routing rules for your organisation. The exact topology is transparent to most tasks, but DNS must still match what the product displays for each Service.

Proxy tab in the dashboard

  1. Open the Service → Proxy tab. The heading is Proxy, with the description: reverse proxy and routing configuration.
  2. The interface uses two subtabs:
    • Nginx (active): key or value fields the product exposes (for example timeouts and buffer sizes). Submitting changes triggers a restart path on the Service so Nginx picks up new values (watch toasts for confirmation).
    • Traefik (disabled in the current UI): reserved for future or alternate stacks.

Edit only fields you understand; invalid combinations can break routing or TLS handshakes.

Relationship to domains

Domains define which names reach the Service. Proxy defines how the edge proxy handles those requests (headers, buffering, upstream timeouts). Change domains when hostname or certificate issues appear; change proxy tuning when connections time out or uploads fail at the edge.

Related