有人让Neo4j使用LetsEncrypt证书吗？
我有一个与LetsEncrypt合作的常规网站，所以我知道我的证书很好。Neo4j正在工作，我可以通过https访问Neo4j浏览器，并收到自签名证书警告。
我一直在遵循有关设置SSL的文档，但当我尝试启动服务时，它会立即失败。我甚至没有得到任何输出到我的日志，因为问题是什么。
myself@localhost:/var/lib/neo4j/certificates/bolt/trusted# service neo4j status
● neo4j.service - Neo4j Graph Database
Loaded: loaded (/lib/systemd/system/neo4j.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/neo4j.service.d
└─override.conf
Active: inactive (dead) (Result: exit-code) since Sat 2018-07-21 21:08:37 MDT; 658ms ago
Process: 19066 ExecStart=/usr/share/neo4j/bin/neo4j console (code=exited, status=1/FAILURE)
Main PID: 19066 (code=exited, status=1/FAILURE)
Jul 21 21:08:37 Swingset systemd[1]: neo4j.service: Unit entered failed state.
Jul 21 21:08:37 Swingset systemd[1]: neo4j.service: Failed with result 'exit-code'.
Jul 21 21:08:37 Swingset systemd[1]: neo4j.service: Service hold-off time over, scheduling restart.
Jul 21 21:08:37 Swingset systemd[1]: Stopped Neo4j Graph Database.
Jul 21 21:08:37 Swingset systemd[1]: neo4j.service: Start request repeated too quickly.
Jul 21 21:08:37 Swingset systemd[1]: Failed to start Neo4j Graph Database.
所以我正在寻找一个完成这项工作的人，他可以给我一份清单，让我仔细检查。我相信我已经有了正确的文件夹结构，我认为我有正确的权限，我认为neo4j.conf修改正确，并且我认为我已经将正确的LetsEncrypt文件复制到正确的文件夹中并使用正确的文件名。但我一定是错过了什么，因为它不起作用。
有趣的是，我今天做了完全相同的事情，在试图弄清楚时偶然发现了这个问题。。。以下是对我有效的方法和我遵循的过程，基于ssl框架上的Neo4j文档中的说明。
-
创建适当的目录结构
cd /var/lib/neo4j/certificates mkdir -p default/revoked default/trusted -
将letsencrypt证书复制到neo4j文件夹
# Copy your server cert to the base dir and the trusted dir of neo4j cp $your_cert_dir/cert.pem /var/lib/neo4j/certificates/default/cert.pem cp $your_cert_dir/cert.pem /var/lib/neo4j/certificates/default/trusted/cert.pem # Copy your key to the base dir of neo4j cp $your_cert_dir/privkey.pem /var/lib/neo4j/certificates/default/privkey.pem -
确保文件具有正确的权限
# To my system, Ubuntu 16.04, it was neo4j:adm chown -R neo4j:adm /var/lib/neo4j/certificates/default/ -
确保neo4j(
/etc/neo4j/neo4j.conf(配置文件中的以下条目如下# Set the base dir for certificates dbms.directories.certificates=/var/lib/neo4j/certificates # To enable connections from remote servers dbms.connectors.default_listen_address=0.0.0.0 # This can remain "OPTIONAL" dbms.connector.bolt.tls_level=REQUIRED # Enable https connector dbms.connector.https.enabled=true dbms.connector.https.listen_address=:7473 # Set up the policy for the connectors to the default bolt.ssl_policy=default https.ssl_policy=default # Create default policy dbms.ssl.policy.default.base_directory=certificates/default # Set the paths for the private key and of the server cert. # These must be absolute paths. dbms.ssl.policy.default.private_key=/var/lib/neo4j/certificates/default/privkey.pem dbms.ssl.policy.default.public_certificate=/var/lib/neo4j/certificates/default/cert.pem # Set up client authentication to "optional" or "none". # If this is left to "default" then the client (a.k.a person who tries to # access the web-portal) would need to authenticate with a certificate dbms.ssl.policy.default.client_auth=none -
确保您有以下端口打开到服务器的防火墙
- https连接器端口：7473
- http连接器端口：7474(好吧，你可以保持阻止；-((
- 螺栓连接器端口：7687
-
重新启动neo4j
service neo4j restart -
现在，您应该能够使用
https://<your server domain name>:7473连接到web界面。如果你尝试使用https://IP:7473，那么你的浏览器会抱怨证书和地址不一样。
仅供参考我在Neo4j日志中仍然收到以下错误，我目前正在努力解决它。到目前为止，其他一切似乎都很好。
Jul 24 14:13:34 sstest neo4j[18181]: 2018-07-24 12:13:34.556+0000 ERROR Unexpected error detected in bolt session 'fa163efffeefd082-00004705-00000003-81330a20f088cbac-29e11d2a'. The client is unauthorized due to authentication failure.
Jul 24 14:13:34 sstest neo4j[18181]: org.neo4j.bolt.v1.runtime.BoltConnectionFatality: The client is unauthorized due to authentication failure.
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.v1.runtime.BoltStateMachine.handleFailure(BoltStateMachine.java:742)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.v1.runtime.BoltStateMachine.handleFailure(BoltStateMachine.java:728)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.v1.runtime.BoltStateMachine.access$500(BoltStateMachine.java:62)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.v1.runtime.BoltStateMachine$State$1.init(BoltStateMachine.java:435)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.v1.runtime.BoltStateMachine.init(BoltStateMachine.java:145)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.v1.messaging.BoltMessageRouter.lambda$onInit$0(BoltMessageRouter.java:70)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.runtime.DefaultBoltConnection.processNextBatch(DefaultBoltConnection.java:195)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.runtime.DefaultBoltConnection.processNextBatch(DefaultBoltConnection.java:143)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.runtime.ExecutorBoltScheduler.executeBatch(ExecutorBoltScheduler.java:170)
Jul 24 14:13:34 sstest neo4j[18181]: at org.neo4j.bolt.runtime.ExecutorBoltScheduler.lambda$scheduleBatchOrHandleError$2(ExecutorBoltScheduler.java:153)
Jul 24 14:13:34 sstest neo4j[18181]: at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590)
Jul 24 14:13:34 sstest neo4j[18181]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Jul 24 14:13:34 sstest neo4j[18181]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Jul 24 14:13:34 sstest neo4j[18181]: at java.lang.Thread.run(Thread.java:748)