Recently I ran into the problem of generating a custom certificate that does not bind to 0.0.0.0 in Neo4j. It turns out that Neo4j - in contrast to the documentation - expects DER certificates for both the public and private key.
I will post lessons learned in respons to this question.
Rob
sudo vi /etc/neo4j/neo4j-server.properties
now set up access to https note: both the private key and the certificate need to be in DER format
See also [my notes] (http://www.blaeu.com/nl/doku.php/Notes)
As of 3.0 this has been changed.
Open up
/etc/neo4j/neo4j.conf
and uncomment and change the following line:Make sure that directory contains you certificate files named
neo4j.key
andneo4j.cert
.Make sure the files can be written by neo4j.
If you're using only
.pem
files, you can just rename those to.cert
and.key
, they're all plain text files,.pem
is just an extension.See the reference