Thanks to visit codestin.com
Credit goes to github.com

Skip to content

cli device login: /cli/authorize page 404s in production while the backend device endpoints are live #1516

Description

@lilyshen0722

commonly login (device authorization, cli 0.1.24+) prints Open https://commonly.me/cli/authorize with a code. In production that page returns 404 (checked 2026-09-03 ~10:10Z: https://commonly.me/cli/authorize 404, https://commonly.me/login 200, https://app.commonly.me/* 404 on every path). The backend half is deployed: POST /api/auth/device/start answers 400 on an empty body and POST /api/auth/device/authorize answers 401 without auth, so the flow fails only at the browser step.

frontend/src/App.tsx:276 on main has <Route path="/cli/authorize" element={<V2CliAuthorize />} />, so either the frontend deploy is behind main or the static host is not serving the SPA fallback for that path. Result: a user whose token expired cannot re-authenticate through the documented flow; both device codes issued today expired on the 404 page. Workaround used: commonly login --instance default --password (legacy prompt).

Ask: deploy the frontend with the route (and confirm the host falls back to index.html for unknown paths), then re-test commonly login end to end from a fresh device.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ne2bwodxUzLh5a9y7ho2gG

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions