This page describes common issues users may encounter in connecting Neo4j Browser or cypher-shell to a Neo4j database, and how to address them.
Symptom: connection attempts lag for a long time, and then fail with connection timed out errors.
- Ensure that the address is correct.
- Ensure that if the server is listening for bolt connections on a port other than 7687, that you pass the port explicitly to your client (e.g. cypher-shell) or other program you have written.
- Ensure that firewall rules do not prohibit traffic on the bolt port.
Common causes of this error:
- A cloud instance of neo4j is launched with no security groups defined or port access. Bolt is available on at the right address, but firewall rules prevent access. Packets are dropped, and so the result is a connection timeout.
- Non-standard configuration of neo4j which runs bolt on a port other than 7687, for example to comply with local network policies.
The server is not yet available. For a period of time while starting up, and particularly if the database is repairing
files or migrating an old store, the bolt endpoint may not be available. You will know that it is available when the logs
contain a message that looks like this:
2018-05-25 13:34:34.584+0000 INFO Bolt enabled on 127.0.0.1:7687.