Fix node connection failures by aligning pairing state, active token, and public URL settings in one clean pass.
Your app is reaching a gateway, but the gateway is rejecting trust state (unpaired node, expired/invalid token, stale browser auth state, or wrong public endpoint).
A sudden "Auth failed: pairing required" after an in-browser session freeze is often session-state drift, not a full outage. Treat browser state (cookies/site data) as part of the pairing path.
Make sure your app’s connect target matches the gateway you actually restarted/edited. Mixed local vs VPS URLs are the #1 hidden mismatch.
You regenerate token on one host, but your app is still pointed at another host.
Generate a new pairing link/code and complete pairing once. Don’t reuse stale screenshots/old QR links.
If you expose the gateway remotely, confirm your published URL is the one apps can actually reach and that it maps to the same running gateway/token set.
Any time you rotate token or change public URL, pair again. Old pairings can become invalid by design.
After config updates, restart gateway and retry from a fresh app state (close/reopen app, then reconnect once).
Connect succeeds without “pairing required” or “unauthorized,” and your node appears online in the expected workspace.
Generate a new token/code and pair immediately. Some tokens are intentionally short-lived for security.
Your local bind may be fine, but remote URL exposure is wrong (DNS, tunnel, or allow-list mismatch). Validate remote URL routing and pair using that same endpoint.
You likely rotated token/config unintentionally or restarted a different gateway instance. Reconfirm single source of truth for runtime + config path.
This is commonly stale browser auth/pairing state. Do one clean browser reset path before deeper debugging:
If multiple users report this at the same time, include that in escalation — it may indicate backend auth instability rather than a single-device issue.
Post this packet so support can diagnose quickly: