Self-Signed Certificates Break Websockets

[mike_blum_neo4j]

neo4j: 3.4.3

works with a let’s encrypt certificate though

ServiceUnavailable: WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver. Please use your browsers development console to determine the root cause of the failure. Common reasons include the database being unavailable, using the wrong connection URL or temporary network problems. If you have enabled encryption, ensure your browser is configured to trust the certificate Neo4j is configured to use. WebSocket readyState is: 3

[mike_blum_neo4j · Accepted solution]

Solution is to approve the self-signed certificate using the port that the websockets server is querying - in this case the bolt port :7687

stackoverflow.com

Firefox disconnects websockets connection for a self signed certificate

firefox, websocket, ssl-certificate

asked by rrevo on 08:20PM - 31 Dec 14 UTC

So browsing to https://10.x.x.x:7687/browser/ and approving the certificate exception resolves the issue.