-
Notifications
You must be signed in to change notification settings - Fork 8
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
Bolt URI in Neo4j 3.1.0 raises "SocketError: Connection refused" #605
Labels
Comments
Connecting to a localhost neo4j 3.1.1 instance with the uri of With
|
esmono
referenced
this issue
in esmono/flask-neo4j
Jul 27, 2017
…echnige/py2neo/issues/605 . It must work on py2neo v2 because it will not call anything else. And in py2neo v3 will add the parameter when the port is used in the connection string
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While diagnosing another issue, @veleritas and I stumbled upon an odd behavior in py2neo 3.1.2. In this bug report, we'll try to connect to neo4j.het.io (which is currently running Neo4j 3.1.0) using bolt:
We receive the following error:
However, the following works:
So shouldn't
bolt=True
be inferred given that the URI begins withbolt://
?The text was updated successfully, but these errors were encountered: