bug description
Two users (HannesB and Fredrik) report that https://home.fortytwowatts.com now gets stuck at “Reaching your home…” after the recent speed-up changes.
evidence gathered
- live
remote-loader.js?v=loader5 loads p2p.js?v=p2p14
- live
p2p.js contains the new non-blocking/strict P2P path: connect() is fired on load, strict owner calls fail closed on public relay context, and the loader/gate appears to wait for the P2P route to become usable
- the text is consistent with the owner gate waiting for the home/Pi channel instead of falling through to a usable error/retry state
expected behavior
home.fortytwowatts.com should either open the saved home or show an actionable re-auth/setup/reset message within the connection timeout.
actual behavior
stays on “Reaching your home…” indefinitely/long enough that both current dogfood users report it as stuck.
next diagnostics
Ask one reporter for the first browser-console warning/error. Likely useful lines: p2p: ..., /signal/... status, P2P channel unavailable, or a JS exception in the owner gate.
suspected area
web/p2p.js + owner-access/home-route gate introduced around the p2p14 deploy / “make faster” changes. Check whether no-device-key, identity-pending, or strict 503 responses update the gate UI instead of leaving it in “Reaching your home…”.
bug description
Two users (HannesB and Fredrik) report that
https://home.fortytwowatts.comnow gets stuck at “Reaching your home…” after the recent speed-up changes.evidence gathered
remote-loader.js?v=loader5loadsp2p.js?v=p2p14p2p.jscontains the new non-blocking/strict P2P path:connect()is fired on load, strict owner calls fail closed on public relay context, and the loader/gate appears to wait for the P2P route to become usableexpected behavior
home.fortytwowatts.comshould either open the saved home or show an actionable re-auth/setup/reset message within the connection timeout.actual behavior
stays on “Reaching your home…” indefinitely/long enough that both current dogfood users report it as stuck.
next diagnostics
Ask one reporter for the first browser-console warning/error. Likely useful lines:
p2p: ...,/signal/...status,P2P channel unavailable, or a JS exception in the owner gate.suspected area
web/p2p.js+ owner-access/home-route gate introduced around thep2p14deploy / “make faster” changes. Check whetherno-device-key,identity-pending, or strict 503 responses update the gate UI instead of leaving it in “Reaching your home…”.