KiCad - the KiCad Bridge

Thanks for the report. What you are seeing is the dashboard page, not KiCad or the KiCad Bridge itself: that page is served by Adom Bridge (ab) on a local port, and "127.0.0.1 refused to connect" means nothing is listening on that port any more. After a sleep, ab reconnects to the relay and can come back on a different local port, so a browser tab that was open before the sleep points at a port that is now dead. The KiCad Bridge (the verbs KiCad answers to) is unaffected; the page is just stale.

Two things that get you back right now:

1. Open the dashboard fresh from the Adom Bridge tray icon (or the Dock Bar's KiCad card) instead of reloading the old tab; that opens whatever port ab is on now.
2. If the tray shows ab itself stopped, start it from the Start menu; the KiCad card comes up with it.

Two things that would let me fix the root cause rather than the symptom: the address in that tab's URL bar (the port number), and which machine this is. With those I can tell whether ab moved ports on wake or stopped, and file it on adom/adom-bridge where the dashboard server lives, so the page reconnects to the new port by itself instead of showing a refused connection.

Port number is in the screenshot. It is http://127.0.0.1:8931/

The machine where this error appeared is "k-zephyrus". An ROG Zephyrus G16

Thanks, that is exactly what I needed: port 8931 on k-zephyrus, an ROG Zephyrus G16.

That confirms it is the Adom Bridge dashboard server, not KiCad and not the KiCad Bridge. Your tab was pointing at the port ab had before the sleep, and after the wake nothing is listening there, so the browser says "refused to connect". Your KiCad Bridge was fine the whole time.

To get back to a working dashboard right now: open it from the Adom Bridge tray icon (or the Dock Bar's KiCad card) rather than reloading that tab, which opens whatever port ab is on now. If the tray shows ab itself stopped, start it from the Start menu.

Filed the root cause where the dashboard server actually lives: adom/adom-bridge#201, with your port and machine, asking that ab reclaim its previous port after a resume instead of moving, and that a dashboard tab that outlives its port be recoverable rather than a dead link. Follow that one for the fix; closing here because there is nothing for the KiCad Bridge to change.