Nissanka Fernando We are running community edition and connecting on the protocol on port .

I am able to connect with the CLI tool libneo4j-omni with the following:

I suspect the issue started to happen with the release of v6 being used in Neo4j Desktop.

I ran the application through a local proxy and can see binary communication on the websocket. I've redacted some of this since it contains my credentials but you can see that the user agent and credentials are passed and then almost immedaitely we get a closed signal. This could just be part of the exchange.

I can confirm this issue has only started happening recently with no infra changes on our side or issues connecting from our application or CLI tools (only Neo4j Desktop for both me and Rene). I can't pin it to a specific version as I not aware of what version I was running before 2.1.0.

Nissanka Fernando this is a self-managed instance (no SSO) in AWS.

Nissanka Fernando Another colleague of mine just started having the exact same issue, so it's probably not something related to my machine or networking.

Any update?

Nissanka Fernando I am also getting this same issue from Neo4j Desktop (Version 2.1.0).

We've not had this issue in the past I am able to connect to the server through the CLI tool libneo4j-omni without any issues. The error I am getting is exactly the same as Rene Rosendahl reports.

Code: 50N42

I believe this issue has been introduced by an update. One other thing to note is that we run OpenVPN to allow us to connect to our instance and thus rely on Neo4j desktop to use the system proxy for connections.

Please let me know if I can be any more help in diagnosing.

Nissanka Fernando Just saw 2.1.1 is available, but it's still happening with the latest version. Any update on this issue?

Rene Rosendahl adam@labfoo.dev

Response today from one of our driver engineers below. It's unlikely we'll be able to resolve or provide support until the new year but there are some things to try below:

"

I started up a 2025.07 community database using docker and connected with the latest driver with no issue.

If I could see the driver logs there maybe more clarity to be gleaned.

The error message is essentially the driver saying "there's no server there to connect to", which, given the setup, makes me suspect there's something going on with the proxy here.

It'd be interesting to see if they could connect with a plain driver with debug logging turned on.

If the normal driver can connect without issue then they could follow the guidelines in the driver README to import the driver in a browser and see if the same query succeeds there.

"

Nissanka Fernando Does this help? Any other updates re: a fix?

Rene Rosendahl: I've shared with our Drivers engineering team and investigation is still in-progress. Unfortunately, I don't have a time for a fix yet

Nissanka Fernando any update on this?

Rene Rosendahl: Here's the response from engineering, in short we can't replicate without an identical proxy setup..

"This doesn't really give any more information than the original error message. It's just the driver saying "I can't find anyone to talk to".

The other thing the user posted looks like they used Netcat to connect to the port, which proves that it is at least reachable.

I have been unable to recreate their issue, even using the web version of Driver v6 (using websockets) against a 2025.07 CE server. Even connecting to a 2025.7 CE server as a remote connection from neo4j desktop functions without any issues. The only thing I can see that is missing from my testing is their proxy setup."

Nissanka Fernando I don't have a proxy set up (to my knowledge), I simply use a VPN, the same as before. I also don't use netcat, unless it's installed behind the scenes by something. I'm not a developer, but a product guy, so not sure I follow all the technical aspects of this. Happy to jump on a quick Zoom etc if that helps. I can with certainty say this worked with a prior version of the client. Are older versions available for re-download?

(BTW: I can use the web interface successfully.)