DIRECT_ADDRESS env variable is ignored.

[AxelFooley]

Seems like the variable is ignored and services still start listening on 127.0.0.1

Also, i configured a cloudflare tunnel and provided the token as an env var, the tunnel connector is created as expected:

2024-09-02T10:57:25Z INF Starting tunnel tunnelID=eccc958c-XXX
2024-09-02T10:57:25Z INF Version 2024.8.2
2024-09-02T10:57:25Z INF GOOS: linux, GOVersion: go1.22.2, GoArch: amd64
2024-09-02T10:57:25Z INF Settings: map[metrics:localhost:2999 token:*****]
2024-09-02T10:57:25Z INF Environmental variables map[CF_TUNNEL_TOKEN:eyXXX]
2024-09-02T10:57:25Z INF cloudflared will not automatically update if installed by a package manager.
2024-09-02T10:57:25Z INF Generated Connector ID: e267210b-b41c-4001-b19e-dddf0bc68b13```

I have mapped in the tunnel configuration a public hostname to 127.0.0.1:11111 but when trying to pointing my browser at it i get the default nginx reverse proxy page, adding /login gives a 404.

I am deploying this in runpod with the provided docker image.

[robballantyne]

Services are always bound to localhost with http and no Auth. It's caddy that binds to the external interface on 1111

DIRECT_ADDRESS is unrelated to the cloudflare tunnel, but if you want it to point to your domain you can use SERVICEPORTAL_URL

I don't use RunPod anymore so not sure if anything has changed there but everything was working as expected last I tried

[mattgagliardi]

Apologies for glomming on, but is this related to the question I posed here?