Startup screen shows the raw response body when the dashboard API is unreachable #1738

Closed
opened 2026-11-02 04:12:31 +00:00 by sam · 1 comment
Owner

ui/src/App.vue:67 renders accounts.error as-is when /api/auth/status fails. With archie-ui down behind a proxy, the page shows "bad gateway" top-left with a Retry link, no logo, and role="status" (a failure is announced politely). errorMessage in ui/src/lib/api.ts:51-59 passes through the first line of whatever body arrived, including a proxy's HTML.

Done when: the startup failure is a centred panel with the logo, a plain statement ("Can't reach Archie") and the detail below it, uses role="alert", and retries on its own.

`ui/src/App.vue:67` renders `accounts.error` as-is when `/api/auth/status` fails. With archie-ui down behind a proxy, the page shows "bad gateway" top-left with a Retry link, no logo, and `role="status"` (a failure is announced politely). `errorMessage` in `ui/src/lib/api.ts:51-59` passes through the first line of whatever body arrived, including a proxy's HTML. Done when: the startup failure is a centred panel with the logo, a plain statement ("Can't reach Archie") and the detail below it, uses `role="alert"`, and retries on its own.
sam added the highbug labels 2026-11-02 04:12:31 +00:00
sam self-assigned this 2026-11-02 04:12:31 +00:00
Author
Owner

Fixed in dafd4263. The startup screen (App.vue) is now a centred card with the logo: on a failed /api/auth/status it shows "Can't reach Archie" with the detail in a destructive Alert (role="alert") below it, and retries the read every 5s on its own until it succeeds (the manual Retry link is gone). api.ts errorMessage now only reads text/plain bodies — archied's http.Error reason — so a proxy's HTML error page falls back to the status line instead of rendering raw. Loading state keeps role="status". Verified: task check (fmt, lint, vet, build, go test, ui build + tests) passed on the committed tree.

Fixed in dafd4263. The startup screen (App.vue) is now a centred card with the logo: on a failed /api/auth/status it shows "Can't reach Archie" with the detail in a destructive Alert (role="alert") below it, and retries the read every 5s on its own until it succeeds (the manual Retry link is gone). api.ts errorMessage now only reads text/plain bodies — archied's http.Error reason — so a proxy's HTML error page falls back to the status line instead of rendering raw. Loading state keeps role="status". Verified: task check (fmt, lint, vet, build, go test, ui build + tests) passed on the committed tree.
sam closed this issue 2026-11-06 11:34:51 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1738