On my server I am running a neo4j server hosted with the docker compose file specified here, only instead of the ports I have a network_mode: host so that the docker container doesnt publish the ports all over the internet. I do have firewalls on my server but they allow everything from my home network. So from my laptop I am able to open the neo4j browser in a browser with http://<ip>:7474. In neo4j desktop I am unable to open a remote connection to neo4j+s://:7687.
Can anyone tell me what could cause that? If I need to add anything to my .conf, please instruct me on how to find it, since i have not found it yet.
Also, as a side quest, the neo4j browser that opens in the browser is the legacy version. Is there any way to get the new version? Should probably open an extra ticket for this though.
Just started the server again while looking at the logs:
Gave me the idea to just try bolt protokoll in neo4j desktop and that actually worked. Now I am wondering what the difference is and if I could enable the neo4j protocol if I ever found the config file.
Nevermind, just tried again, its actually the +s that is the problem, both bolt and neo4j without the +s work. Probably some secure connection thing?
Yes, there are different URI schemes for different things Neo4j Driver API - Bolt Protocol
In short:
- neo4j:// when you want a default routing driver ( +s for tls +scc to allow self signed ca )
- bolt:// when you want a non-routing driver (special scenarios when you want to target a specific server in a cluster)
Talking in terms of a “driver” here (neo4j lingo for the database client) as these uri schemes controls how the driver under should connect to the database.
1 Like
