Opening it from another device

Connect to your installation securely from another device on your network.

1. Choose an HTTPS address

Point a DNS name such as agents.example.com at your server or ingress. Allow only your administrator to reach it until setup is complete, then grant your team access through your firewall or private network.

2. Route to Omnimatch

Terminate HTTPS at your reverse proxy and forward requests to port 8787. Preserve the original Host header and support WebSockets. Use a certificate trusted by your team’s browsers.

For example, with Caddy installed directly on the Docker host, replace the hostname in this Caddyfile and reload Caddy:

agents.example.com {
    reverse_proxy 127.0.0.1:8787
}

Caddy needs DNS and network access appropriate for issuing a certificate. For a private hostname, configure your organisation’s certificate instead.

The supplied Compose file binds to the server’s loopback interface. If your proxy runs in another container or on another server, route over a shared container network or bind port 8787 to a private interface that only the proxy can reach.

For Kubernetes, configure your ingress controller with TLS and a route to service omnimatch, port 8787, in namespace omnimatch. Certificate and ingress configuration depend on your cluster.

3. Finish setup at that address

Open https://agents.example.com, using your chosen hostname, and complete the wizard. This becomes your installation’s address. Plain HTTP is allowed only on localhost; a remote server’s IP address over HTTP will not work for setup.