-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to register against the Forest Admin server: Socket connection timeout. #601
Comments
This is the output of NODE_DEBUG. Don't really see anything unusual when compared to my colleagues
|
I have no VPN, I have changed the DNS to use googles (8.8.8.8), used a tethered mobile network. I've also downgraded to versions that my colleagues are using. I have pinged all 3 IP addresses listed above that it is trying to connect to and they all respond |
Hi @mminklet, Before digging into this error, it could be interesting to know if the latest beta version has the same issue. We are working on a version 4 of the toolbelt v4 that drops the support of Node 10-11-12-13 and probably provides better support for Node 20 (according to our automated tests base). A pre-release is available via a first beta version (v4.0.0-beta.1). You can install it:
Let me know if it helps. |
I solved this by downgrading node to 18. The latest version of node does not work with this package |
You could be right for the toolbelt v3 you are currently using, as it as not be tested on Node 20. That being said, with the toolbelt v4.0.0.beta.1, we added Node 20 to our automated test base, and all tests are green. |
Could you update the engine in the package.json to limit the cli to node versions that it does work on? |
Trying to use forest login but immediately receive this message. Can't get any further details as there doesn't appear to be a verbose flag. CLI is the latest version. Tried different networks
On MacOS 12.6.6, using version
forest-cli/3.4.2 darwin-x64 node-v20.2.0
× Unable to register against the Forest Admin server: Socket connection timeout.
The text was updated successfully, but these errors were encountered: