Skip to main content

Reverse Proxy

DoubleDino includes a lightweight HTTP server.

For production environments, you may place DoubleDino behind an existing reverse proxy to handle:

  • TLS certificates.
  • HTTPS termination.
  • Domain routing.
  • Existing security controls.

The architecture:

DoubleDino continues to run internally while the reverse proxy manages external access.

Example: Nginx​

Example configuration:

server {
    listen 443 ssl;

    server_name doubledino.example.com;

    location / {
        proxy_pass http://127.0.0.1:8080;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

Replace:

doubledino.example.com

with your own domain.

HTTP port​

By default, DoubleDino listens on:

8080

To change the port:

DD_HTTP_PORT=9000

Your reverse proxy should forward traffic to the configured port.

TLS​

DoubleDino does not manage TLS certificates.

TLS can be handled by:

  • Nginx.
  • Caddy.
  • Apache.
  • Cloud load balancers.
  • Existing company infrastructure.

The connection flow:

Access control​

DoubleDino still requires API authentication.

Every request must include:

x-api-key: your-api-key

The reverse proxy adds an additional infrastructure layer but does not replace DoubleDino authentication.

Notes​

  • DoubleDino can run without a reverse proxy.
  • Use a reverse proxy when HTTPS or existing routing infrastructure is required.
  • DoubleDino remains responsible for source connections and data transformation.