As described by http://neo4j.com/docs/developer-manual/current/drivers/#_trust, when establishing an encrypted connection, it needs to be verified that the remote peer is who we expected to connect to.
The default connection is to ‘Trust on first use’ and to do so indicates that we will read and write a certificate value in
Upon upgrading from 3.0.0 to 3.0.1 future connections may error, when establishing the connection to Neo4j, for example:
General SSLEngine problem
neo4j.v1.exceptions.ProtocolError: Server certificate does not match known certificate for 'localhost'; check details in file /home/neo4j/.neo4j/known_hosts
As detailed in the Python error message, the failure is a result of reading the
/home/neo4j is the users default home directory, and to which the file at `~/.neo4j/`known_hosts has a certificate which is no longer valid.
An example of the content of this file is
To resolve the failure above, simply delete the line which references
localhost from the
- Last Modified: 2020-08-03 16:12:21 UTC by Dana Canzano.
- Relevant for Neo4j Versions: 3.0.
- Relevant keywords connection,security,tls.