UniFi Network app: every /app/network/* route 404s #9

Open
opened 2026-08-22 18:29:21 -07:00 by jwed · 0 comments
Owner

Steps

  1. Log in as superadmin@playwright.test (dev login).
  2. Navigate to any UniFi/Network app route resolved via Ziggy, e.g.:
    • route('unifi.dashboard') -> /app/network
    • route('unifi.settings') -> /app/network/settings
    • route('unifi.wifi') -> /app/network/wifi
    • route('unifi.devices') -> /app/network/devices
    • route('unifi.settings.sites') -> /app/network/settings/sites

Expected

The UniFi Network dashboard/settings/wifi/devices pages load normally for an
authorized admin persona (as with every other snap-in app).

Actual

Every single /app/network/* route returns an HTTP 404, for every route
checked (dashboard, settings, wifi, devices, settings.sites, webhooks.index).
This is not the "app shows as Not Installed" App Store cosmetic issue seen
after dev DB resets (that one fails open — routes still work per
EnsureAppEnabled's docblock). This is the routes themselves 404ing — looks
like the UniFi controller/routes aren't being registered at all on this
deploy, unlike every other snap-in.

This has been re-observed as a blocker across many regression/full/security
sweeps over the past several days (2026-08-17 through 2026-08-22) but had not
actually been filed as an issue yet — prior notes treated it as equivalent to
the separate, legitimate "no UniFi controller configured in dev" limitation
(which only affects the hourly capture-snapshots job's ability to reach live
hardware), but that's a different problem from the entire app 404ing at the
HTTP routing layer.


Filed automatically by the Claude-driven QA sweep (/opt/qa-agent). The marker below dedupes repeat reports — do not edit it.

## Steps 1. Log in as `superadmin@playwright.test` (dev login). 2. Navigate to any UniFi/Network app route resolved via Ziggy, e.g.: - `route('unifi.dashboard')` -> `/app/network` - `route('unifi.settings')` -> `/app/network/settings` - `route('unifi.wifi')` -> `/app/network/wifi` - `route('unifi.devices')` -> `/app/network/devices` - `route('unifi.settings.sites')` -> `/app/network/settings/sites` ## Expected The UniFi Network dashboard/settings/wifi/devices pages load normally for an authorized admin persona (as with every other snap-in app). ## Actual Every single `/app/network/*` route returns an HTTP 404, for every route checked (dashboard, settings, wifi, devices, settings.sites, webhooks.index). This is not the "app shows as Not Installed" App Store cosmetic issue seen after dev DB resets (that one fails *open* — routes still work per `EnsureAppEnabled`'s docblock). This is the routes themselves 404ing — looks like the UniFi controller/routes aren't being registered at all on this deploy, unlike every other snap-in. This has been re-observed as a blocker across many regression/full/security sweeps over the past several days (2026-08-17 through 2026-08-22) but had not actually been filed as an issue yet — prior notes treated it as equivalent to the separate, legitimate "no UniFi controller configured in dev" limitation (which only affects the hourly `capture-snapshots` job's ability to reach live hardware), but that's a different problem from the entire app 404ing at the HTTP routing layer. - Persona: superadmin@playwright.test (also platform-wide, not persona-specific) - URL: https://central-dev.vancs.org/app/network (and all sub-routes) - Console: `Failed to load resource: the server responded with a status of 404 () @ .../app/network/wifi` --- _Filed automatically by the Claude-driven QA sweep (`/opt/qa-agent`). The marker below dedupes repeat reports — do not edit it._ <!-- claude-qa-fingerprint: bae084ccf793 -->
jwed added the e2e-failure label 2026-08-22 18:29:21 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jwed/central-unifi#9