-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Getting the following error when trying to connect to openclaw via HTTPS (or WSS) when i navigate to /settings/openclaw-config. My openclaw configuration is behind a nginx server that terminates HTTPS. I am able to connect to openclaw using my public DNS, using HTTPS certs, via CLI, Web, and Mac apps. But when MosBot tries i get the following error. I know some connectivity to my openclaw is working because i do see sessions at /monitor.
{"timestamp":"2026-03-02T20:44:52.766Z","level":"DEBUG","message":"Device auth not configured — using allowInsecureAuth fallback (requires gateway.controlUi.allowInsecureAuth: true)"}
{"timestamp":"2026-03-02T20:44:52.779Z","level":"DEBUG","message":"Sending allowInsecureAuth connect handshake"}
{"timestamp":"2026-03-02T20:44:52.779Z","level":"DEBUG","message":"Sending allowInsecureAuth connect handshake"}
{"timestamp":"2026-03-02T20:44:52.783Z","level":"WARN","message":"Session usage poller: sync failed","error":"control ui requires device identity (use HTTPS or localhost secure context)"}
{"timestamp":"2026-03-02T20:44:52.904Z","level":"WARN","message":"OpenClaw workspace service unavailable after retries","method":"GET","path":"/status","url":"http://openclaw-workspace.agents.svc.cluster.local:8080/status","retryCount":3,"hint":"Set OPENCLAW_WORKSPACE_URL to disable or configure the service URL"}
{"timestamp":"2026-03-02T20:44:52.905Z","level":"ERROR","message":"Request error","error":"OpenClaw workspace service is unavailable. This may be expected in local development.","stack":"Error: OpenClaw workspace service is unavailable. This may be expected in local development.\n at makeOpenClawRequest (/app/src/services/openclawWorkspaceClient.js:148:19)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async /app/src/routes/openclaw.js:457:18","status":503}
{"timestamp":"2026-03-02T20:44:53.544Z","level":"INFO","message":"Fetching OpenClaw config via Gateway RPC","userId":"51036a98-eeb6-4bd1-9e67-1d4b002f9bc8","userRole":"owner"}
{"timestamp":"2026-03-02T20:44:53.544Z","level":"DEBUG","message":"Device auth not configured — using allowInsecureAuth fallback (requires gateway.controlUi.allowInsecureAuth: true)"}
{"timestamp":"2026-03-02T20:44:53.633Z","level":"DEBUG","message":"Sending allowInsecureAuth connect handshake"}
{"timestamp":"2026-03-02T20:44:53.633Z","level":"DEBUG","message":"Sending allowInsecureAuth connect handshake"}
{"timestamp":"2026-03-02T20:44:53.636Z","level":"ERROR","message":"Failed to fetch OpenClaw config","error":"control ui requires device identity (use HTTPS or localhost secure context)","userId":"51036a98-eeb6-4bd1-9e67-1d4b002f9bc8"}
{"timestamp":"2026-03-02T20:44:53.636Z","level":"ERROR","message":"Request error","error":"control ui requires device identity (use HTTPS or localhost secure context)","stack":"Error: control ui requires device identity (use HTTPS or localhost secure context)\n at doConnectAndRpc (/app/src/services/openclawGatewayClient.js:700:24)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)","status":500}
I see references in the envs to a device auth flow but cannot find it in the documentation. So i cannot test that workflow.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels