-
Notifications
You must be signed in to change notification settings - Fork 55
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
Couldn't connect on 127.0.0.1:6000 with VSCode 1.82.0 #602
Comments
Yes, downgrading to 1.81.1 solves the problem |
A workaround is to explicitly launch |
Seriously, THANK YOU ALL. I just started trying Haxe/Heaps last night and couldn't even get the Hello World file for heaps to compile. Reverting VS Code versions worked. |
Anyone reproduces this issue on linux? (or windows btw, could be a mac only issue somehow) |
Hi, I have the same problem on Windows, a few days ago before the VS update everything worked correctly. Regards |
Thanks everyone for identifying the root source of the issue, I spent all weekend trying to solve this!
|
I've been having the same issue on my linux distro since 1.78 version of vscode. #589 |
I had the same issue too! Had to downgrade VSCode to 1.81 on Windows ... is a fix possible? |
We added better connection error message to nightly, so someone can test it and write what exactly unix error this is (maybe @kLabz can rebuild this commit to make it available on build.haxe.org) |
after some testing on a Windows machine I found out what causes it and how to reproduce it: so if your hosts file contains the line |
Can be related to vscode change where v4 ips are not sorted first anymore? |
could be yes. I guess the solution would be to explicitly set hostname to |
Hm, why not replace "localhost" with "127.0.0.1" instead, in vshaxe and lsp? |
Haxe compiler defaults to 127.0.0.1 when no host is given, so maybe we just change haxe-languageserver to a fixed ip address instead of |
I'd think using
Plus other things like people actually wanting to use some other IP for localhost, etc |
well, localhost somehow doesn't seem to work. not even on console. on Windows I can on Linux localhost doesn't work even though it resolves to 127.0.0.1. using comparing
whereas the other two show
tested with haxe_20230908125023_536c388_bin.zip from build artifacts (win64 binaries) not sure what to make of it. looking at Haxe source code, I believe it only supports IPv4 sockets for |
I'm happy to add IPv6 support to Haxe for this, but that doesn't really help us with the current problem because existing versions have to function anyway... |
I'm checking for ipv6 support in Haxe atm and it seems pretty straightforward |
@AlexHaxe Does If so, proposed plan:
|
this does not work for me (windows 10/11)
in my hosts file:
Meaning its commented out, right...? |
you have some process already occupying port 6000. you can only have one combination of host and port open on a single system.
try |
@kLabz seems to be working. I'm going to do some more testing and then we can aim for a new version. |
…xe#589 added displayHost configuration option
vshaxe version 2.30.0 was just released. you should now be able to upgrade to VSCode 1.82.x |
vscode hashlink debugger stopped working around same time for me. Is this potentially the same fix? |
Seems likely indeed |
VSCode updated itself to 1.82.0 and I immediately started getting the error
Fatal error: exception Failure("Couldn't connect on 127.0.0.1:6000")
whenever I try to compile to any target.Below are the build details of my current version of VSCode:
The text was updated successfully, but these errors were encountered: