[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"problem-detail-error-hermes-agent-refuses-to-expose-its-dashboard-without":3},{"stack":4,"error":5,"seoName":6,"seoStack":7,"seo":8,"breadcrumb":10,"titlePrefix":17,"titleAccent":6,"lead":18,"facts":21,"why":36,"log":41,"fix":58,"engine":72,"related":76,"pitch":83},"compose","hermes-agent-refuses-to-expose-its-dashboard-without","Hermes agent refuses to expose its dashboard without an auth provider","Docker Compose",{"description":9},"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",[11,14,16],{"label":12,"href":13},"App Installations","\u002Fapps",{"label":7,"href":15},"\u002Fapps\u002Fstacks\u002Fcompose",{"label":6},"",[19],{"text":20},"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.",[22,27,30,32],{"label":23,"value":24,"tone":25,"tooltip":26},"Type","Error","err","An 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.",{"label":28,"value":29},"Seen","1 times",{"label":31,"value":7},"Where",{"label":33,"value":34,"tooltip":35},"Status","Resolve Ready","Our team will look into this soon, verify the cause and try to fix it in an upcoming release.",{"heading":37,"body":38},"Why it happens",[39],{"text":40},"github.com\u002Foutsourc-e\u002Fhermes-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.",{"heading":42,"block":43},"What the log looks like",{"header":44,"lines":45},"Deploy log",[46,50,54],{"segments":47},[48],{"text":49},"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` (…",{"segments":51},[52],{"text":53},"Container project-hermes-agent-1 Error dependency hermes-agent failed to start",{"segments":55},[56],{"text":57},"dependency failed…",{"heading":59,"steps":60,"block":69},"How to fix it",[61],[62,64,67],{"text":63},"Configure ",{"text":65,"code":66},"dashboard.basic_auth",true,{"text":68}," in the agent's config.yaml (or bind the dashboard to loopback only) and set an LLM provider key in the project's environment variables, then redeploy.",{"header":70,"lines":71},"Fix by hand",[],{"heading":17,"body":73,"block":74},[],{"header":17,"lines":75},[],{"heading":77,"items":78},"Apps affected",[79],{"title":80,"badge":81,"tone":25,"href":82},"hermes-workspace","1 occurrence","\u002Fapps\u002Foutsourc-e\u002Fhermes-workspace",{"heading":84,"body":85,"footNote":86,"docsLabel":87,"docsHref":88},"Try PanelAlpha Engine yourself.","The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.","Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPU","Read the documentation","https:\u002F\u002Fpanelalpha.com\u002Fdocs"]