Hermes agent refuses to expose its dashboard without an auth provider
The service project-hermes-agent-1 did not start (unhealthy), so the application was not started either. It printed: Refusing to bind dashboard to 0.0.0.0 — the auth gate engages on non-loopback binds (0.0.0.0), but no auth providers are registered. Configure an auth provider before exposing the dashboard: • Password: set dashboard.basic_auth.username + password_hash in config.yaml (hash with: python -c "from plugins.dashboard_auth.b… The full output is in the deploy log.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen1 times
WhereDocker Compose
StatusResolve ReadyOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
github.com/outsourc-e/hermes-workspace's compose file binds the Hermes agent dashboard to all interfaces, and the current agent image refuses to start that way until a dashboard login is configured in its config.yaml. The stack also needs an LLM provider API key.
What the log looks like
Deploy log
error: service project-hermes-agent-1 did not start (unhealthy): Refusing to bind dashboard to 0.0.0.0 — the auth gate engages on non-loopback binds (0.0.0.0), but no auth providers are registered. Configure an auth provider before exposing the dashboard: • Password: *** dashboard.basic_auth.username + password_hash in config.yaml (hash with: python -c "from plugins.dashboard_auth.basic import hash_password; print(hash_password('your-password'))") • OAuth: *** `hermes dashboard register` (…Container project-hermes-agent-1 Error dependency hermes-agent failed to startdependency failed…