#5647·kopia

Allow insecure server on non-loopback when behind secure reverse proxy

Author: lbuttorffCreated Sep 15, 2026Updated Sep 15, 2026

I am setup with a reverse proxy in a private docker network, with authentik intercepting and requiring users belonging to a special group to be allowed through.

Here is my docker compose command:

yaml
    command:
      - server
      - start
      - --without-password
      - --insecure
      - --address=0.0.0.0:51515

And this is the log I get trying to start up the server:

log
listen address not allowed for insecure server without password: refusing to expose unauthenticated server on non-loopback network bind: "0.0.0.0:51515" is not a loopback address; pass --allow-extremely-dangerous-unauthenticated-server-on-the-network only in isolated lab environments (extremely dangerous)

This error log doesn't make sense for my setup because it is a very controlled environment with a more secure authentication server blocking access. I think this should at the very least be changed to not require the ridiculously long flag to disable this warning. Ideally, if kopia supported an external authentication provider for the management of users, that would be excellent but I understand why that might not be possible or desirable at this time.

I also want to make sure that this use case is not abandoned in the future, so I will say I appreciate the ridiculously long flag existing in the first place.