## Description When navigating to the root URL of a DLE instance (e.g., https://demo.dblab.dev/), the app loads and React Router redirects to `/instance`. However, refreshing the page at `/instance` (or any `/instance/*` SPA route) returns a **404 page not found**. ## Root Cause In `ui/packages/ce/nginx.conf`, the regex location block added in commit 6d2965dc ("Add ARM64/Colima support and fix UI API proxying") includes `instance` in the pattern: ```nginx location ~ ^/(healthz|status|instance|branch|branches|clone|clones|snapshot|snapshots|observation|admin|full-refresh)(/|$) { proxy_pass http://${DLE_HOST}:${DLE_PORT}$request_uri; } ``` In nginx, regex locations (`~`) take precedence over prefix locations. When the browser requests `/instance` on refresh, this regex matches and proxies the request to the DLE API server instead of falling through to `try_files ... /index.html`. The DLE API has no `/instance` endpoint, so it returns 404. ## Impact - Affects all DLE instances with embedded UI enabled - Any page refresh or direct navigation to `/instance`, `/instance/clones`, `/instance/snapshots`, `/instance/branches`, or `/instance/configuration` triggers the bug - Only the initial load from `/` works (because React Router handles the redirect client-side) ## Fix Remove `instance` from the regex. The actual API endpoints (`/instance/retrieval` and `/instance/logs`) are already reachable via the `/api/` and `/ws/` proxy locations.