psa-systems/lets-chat
Watch
9
0
Fork
You've already forked lets-chat
 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

fix(dev): serve dev-web on the nebula-secure entrypoint too #363

Merged
longjacksonle merged 1 commit from fix/dev-web-nebula-entrypoint into main 2026-06-19 03:43:14 +02:00
Conversation 0 Commits 1 Files changed 1 +5 -1
longjacksonle commented 2026-06-19 03:42:50 +02:00
Owner
Copy link

Problem

just dev-web came up healthy but ${USER}-chat.a8n.run returned 404 page not found in the browser. The router bound only to the web-secure entrypoint, which in this dev environment listens on :20443. The dev hosts are reached over the Nebula overlay, where Traefik's nebula-secure entrypoint listens on :443 (the default asDefault entrypoint), so the browser hit :443 and found no matching router. Every other dev app (bunyip and friends) binds both entrypoints.

Fix

Bind the dev-web router to web-secure,nebula-secure.

Verification

Against the dev Traefik (resolving the host to the Traefik container and hitting each entrypoint with the correct SNI):

  • :443 (nebula-secure, the browser-over-Nebula path) -> HTTP 200 on /login (was 404).
  • :20443 (web-secure) -> HTTP 200, preserved.
## Problem `just dev-web` came up healthy but `${USER}-chat.a8n.run` returned `404 page not found` in the browser. The router bound only to the `web-secure` entrypoint, which in this dev environment listens on `:20443`. The dev hosts are reached over the Nebula overlay, where Traefik's `nebula-secure` entrypoint listens on `:443` (the default `asDefault` entrypoint), so the browser hit `:443` and found no matching router. Every other dev app (bunyip and friends) binds both entrypoints. ## Fix Bind the dev-web router to `web-secure,nebula-secure`. ## Verification Against the dev Traefik (resolving the host to the Traefik container and hitting each entrypoint with the correct SNI): - `:443` (nebula-secure, the browser-over-Nebula path) -> HTTP 200 on `/login` (was 404). - `:20443` (web-secure) -> HTTP 200, preserved.
fix(dev): serve dev-web on the nebula-secure entrypoint too
All checks were successful
check-secrets / Kingfisher (push) Successful in 4s
Details
check-secrets / Nosey parker (push) Successful in 5s
Details
check-secrets / TruffleHog (push) Successful in 7s
Details
check-secrets / Kingfisher (pull_request) Successful in 4s
Details
check-secrets / Nosey parker (pull_request) Successful in 4s
Details
check-secrets / TruffleHog (pull_request) Successful in 4s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
Check / clippy + fmt + tests (pull_request) Successful in 3m24s
Details
c23d097194 
The dev-web Traefik router bound only to `web-secure`, which in this dev environment listens on :20443. The dev hosts are reached over the Nebula overlay, where Traefik's `nebula-secure` entrypoint listens on :443 (the default), so a browser hitting `${USER}-chat.a8n.run` got a 404 with no matching router. Every other dev app (bunyip et al) binds both entrypoints.

Bind the router to `web-secure,nebula-secure` to match. Verified against the dev Traefik: `${USER}-chat.a8n.run` now returns 200 on both :443 (nebula-secure) and :20443 (web-secure).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
longjacksonle deleted branch fix/dev-web-nebula-entrypoint 2026-06-19 03:43:14 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/lets-chat!363
No description provided.