You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
root ERROR Failed to start the backend application: root ERROR Error: listen EADDRNOTAVAIL: address not available 127.0.0.1 at Server.setupListenHandle [as _listen2] (node:net:1298:21) at listenInCluster (node:net:1363:12) at GetAddrInfoReqWrap.doListen [as callback] (node:net:1501:7) at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8) root ERROR Uncaught Exception: root ERROR Error: listen EADDRNOTAVAIL: address not available 127.0.0.1 at Server.setupListenHandle [as _listen2] (node:net:1298:21) at listenInCluster (node:net:1363:12) at GetAddrInfoReqWrap.doListen [as callback] (node:net:1501:7) at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8)
We do not yet know what's causing the problem, but we managed to figure out that disabling the IPv6 support on macOS fixes the issue:
sudo networksetup -setv6off Wi-Fi
Steps to Reproduce:
Download and start the latest Theia Blueprint app,
Sometimes, it does not start
Additional Information
Operating System: macOS 11+ and 12+
Theia Version: TheiaBlueprint, Version 1.31.1 (1.31.1.86)
I could not reproduce the bug on my macOS env. I will investigate the issue further and update this issue. If anybody has the seem issue, please let us know.
The text was updated successfully, but these errors were encountered:
The issue at first glance looks similar to #11578, is there an issue with localhost not being properly binded, or the loopback address somehow being messed up?
Bug Description:
We have received reports of non-functional Theia electron apps from multiple users:
Our users were friendly to help us, and they could reproduce the bug with the TheiaBlueprint application.
Relevant stack traces:
We do not yet know what's causing the problem, but we managed to figure out that disabling the IPv6 support on macOS fixes the issue:
Steps to Reproduce:
Additional Information
I could not reproduce the bug on my macOS env. I will investigate the issue further and update this issue. If anybody has the seem issue, please let us know.
The text was updated successfully, but these errors were encountered: