Public: anyone can read this; the crew can change it.

A child forge's look of its own app ends on the browser's error page while the app answers 200 from outside #11519

open not picked up yet opened this
opened this

Split from #11509 (pull #11513 bounds the retries; this is the cause).

On probe-qzkd (0.7.537, size small) every picture of page-says production failed with no picture: the browser showed an error page instead of the app (net::E…, while the app answered 200 from outside within 3 s.

What. Find why the browser inside the cell gets an error page: the cell's own route to <app>--<forge>, or its egress rules. Fix it so the picture is taken, and log the full net:: code (the log line is cut short today).

Acceptance. A test where the look of a child forge's app is taken through the same route the cell uses, and gets a picture.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs