WebSocket connection failure. Due to security constraints in your web browser

Question

Today I download neo4j-community-3.2.0 in windows, when i start the server, i meet one problem in browser, i meet this problem in neo4j-community-3.1.2 and i had solved it by Ticking the "Do not use Bolt" option in settings solved the issue. But in neo4j-community-3.2.0 , i can't see "Do not use Bolt" option ,and i don't know how to do.

N/A: 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

Answer 1

2025 probable solution: I tried uncommenting these two, and it worked:

server.default_listen_address=0.0.0.0

and

server.bolt.listen_address=:7687

Answer 2

I closed the powershell.exe which is running in the background and ran into the same error. Fixed by simply restarting

Answer 3

for me it was uncommenting the following rule in the .conf file

server.bolt.listen_address=:7687

I was not able to locate the dbms.connector.bolt.address=0.0.0.0:7687

Answer 4

I was facing the same issue with Neo4J version 4 installed on an Ubuntu 18 EC2 instance. Tthe workaround that did the trick for me was to replace the 0.0.0.0 entries in /etc/neo4j/neo4j.conf with the actual private IP of my instance.

Following are the lines where the replace happened:

dbms.default_listen_address=172.X.X.232

dbms.connector.bolt.address=172.X.X.232:7687

Post restart of the DB, the Connect URL when accessing from browser should also use the private IP instead of localhost.

Answer 5

I resolve this error by replace the port 7687 with node port 30033 inside Neo4j then it works fine.

Answer 6

Please mention the correct bolt port under the Connect URL textbox.if you are using the service port the mention the service port in place of bolt port.

Then finally I resolve it by replacing the bolt port with service port inside k8s. user: neo4j password: neo4j

Answer 7

Assuming you have valid certs and placed them under the correct certificates directory:

dbms.ssl.policy.bolt.client_auth=NONE

Version 4.0. Took it from this article.

I shared my full ssl config on this other answer.

Answer 8

Adding another option, which worked for me. If your bolt's tls_level is set to REQUIRED, you need to change it to OPTIONAL, if you are not using it with SSL certificate; to get this working.

If you are using Neo4J Community Edition (ver 3.5.1 - in my case) from AWS Marketplace, you need to change the configuration in:

/etc/neo4j/pre-neo4j.sh

Change this line:

echo "dbms_connector_bolt_tls_level" "${dbms_connector_bolt_tls_level:=REQUIRED}"

to

echo "dbms_connector_bolt_tls_level" "${dbms_connector_bolt_tls_level:=OPTIONAL}"

You can find more about Neo4J connector configuration option here. Ideally as per docs, by default bolt.tls_level should have been OPTIONAL only. But I'm not really sure what exactly happened in my case, which got it changed to REQUIRED. Or if it came as is from AWS Marketplace.

Answer 9

1. In the lower left corner of the browser gear, select do not use bolt.
2. Open your ${NEO4J_HOME}/conf/neo4j.conf file and edit the bolt settings. It is just about uncommenting this line dbms.connector.bolt.address=0.0.0.0:7687
3. Change the version of Neo4j
4. Check your JDK version, use JDK1.8

Answer 10

This happens because the browser is trying (under the hood) to also access the bolt port, which uses an unsigned certificate.

You probably allowed the browser to access the SSL 7474 port through allowing the unsigned certificate as an exception on your browser (and if you didn't, you should in order to make it work). The url was:
https://[neo4j_host]:7474

Do the same for the bolt certificate, allow it as an exception for url:
https://[neo4j_host]:7687

Answer 11

I had the same error. New to Neo, so take this with a grain of salt, but my solution didn't match these above idea. But thanks as they did lead me to the right "water". So

I went into the conf file, noticed that there was the same port number (previously, the Neo desktop had been constantly telling me it'd needed to update the port numbers...I never checked to verity, but they'd be #, #+1 and #+2. But that didn't work yet that'd happened again and again...but now, after checking the conf file myself, I noticed that the number was the same for all three port requirements for BOLT. Tried that and it didn't work either...but maybe that was important in what did:

In the folder, where the specific database is housed, named "..neo4jdatabases/[GUID Value]" there were two directories titled "/installation-3.4.0" and "...1". I removed the ".0", restarted things and IT WORKED.

So, either there should NOT be two versions under the same database collection OR that's true AND you need the three ports to be the same.

Final add for any Neo4j experts who actually know what they're doing, I have three databases running, two without issue. This occurred AFTER I was messing around trying to see how PowerShell might be useful. Not sure if this is related, but the other databases have worked fine...but, this db is the original playground/sandbox I'd had since the beginning. Not 100% sure, I made the version update before or after, creating the other two databases. HTH.

Using a windows trial version on a Windows 10 machine. Current N4j version is 3.4.1.

Do love what I see so far with Neo BTW!!!

Answer 12

I ran into the same problem trying to use Neo4j Community Edition on an AWS Ubuntu 16.04 instance. The key thing that solved it was to open port 7687 (the bolt port) in the AWS security group settings.

Found this based on https://stackoverflow.com/a/45234105/1529646

Thus, full answer is:

1. Make sure to configure Neo4j correctly, ie. uncomment the line dbms.connectors.default_listen_address=0.0.0.0 AND the line dbms.connector.bolt.listen_address=:7687
2. Open ports 7474 AND 7687 in the AWS security group settings.