This repository has been archived by the owner on May 23, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Not able to connect with database with non-standard bolt port and TLS #51
Comments
Have you tried passing the |
Hello @nicolewhite, the issue still persists using the Cycli version:
Passing the port number for Bolt and the ssl flag:
Passing the port number for HTTPS and the ssl flag:
Note: this database has been deleted any further connection attempt using this set or another set of credentials will fail. |
I'm facing the same problem; my setup has HTTP at :8080 and BOLT at :8081. I cannot use the default ports.
It appears cycli is able to get some information from the database though, since autocomplete works and |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm having troubles connecting with a database hosted in GrapheneDB using
cycli 0.7.6
.I'm only able to connect databases with Neo4j version < 3.
If I try the same parameters that I used to connect with a database >= 3, I get the following:
I think passing
bolt=None
to py2neo makes it try to connect via Bolt. The database version is >= 3, but GrapheneDB uses a non-standard port for Bolt connections and also needs to use TLS secure connections. I managed to connect to my database using py2neo with the following options:It would be great if you can add more options to be able to use your tool for GrapheneDB (at least: bolt, bolt_port). Currently, with databases >= 3 is not possible to connect with neither HTTP/HTTPS, nor Bolt protocol.
The text was updated successfully, but these errors were encountered: