web socket timeout error every time I restart computer

[jligeza]

Every time I start noflo-nodejs, the runtime has different ip address for ws listening, while the old address is kept saved in the indexed db at flowhub. This causes connection time out, and the only way to solve it is to remove old runtime entry, which has old ip address, or open a tab in incognito mode.

[bergie]

This would be better reported against noflo-ui (since that's where the issue is).

But yes, I've also seen situations where noflo-ui uses the old connection details from IndexedDB instead of the ones supplied in the URL.

For now, easiest workaround is to fix the noflo-nodejs hostname to localhost.