Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.
12-10-2018 01:11 AM
When I am trying to login neo4j browser with default id password i.e. neo4j/neo4j am getting below error:
**> ServiceUnavailable: WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver.**
I changed few things to neo4j.conf file also as mentioned in https://community.neo4j.com/t/troubleshooting-connection-issues-to-neo4j/129:-
dbms.connector.bolt.tls_level=OPTIONAL
in your neo4j config.But still ending with the same error.
I am using neo4j:latest docker image in an Azure platform as container instance.
Please help me to resolve this issue.
Thanks
12-10-2018 06:31 AM
Can you provide some extra details?
12-12-2018 12:59 AM
I tried usiong both https and http with 7473 and 7474 respectively, still facing same error.
12-10-2018 06:19 PM
I have encountered the same situation.
2018-12-11 02:04:46.168+0000 INFO [REQUEST] [AsyncLog @ 2018-12-11 02:04:46.167+0000] 192.168.10.253 - [Tue Dec 11 10:04:46 CST 2018] "/browser/?null" 200 2895 "" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36" 2
2018-12-11 02:04:46.493+0000 INFO [REQUEST] [AsyncLog @ 2018-12-11 02:04:46.493+0000] 192.168.10.253 - [Tue Dec 11 10:04:46 CST 2018] "/?null" 200 146 "http://192.168.10.236:7474/browser/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36" 2
2018-12-11 02:04:46.713+0000 INFO [REQUEST] [AsyncLog @ 2018-12-11 02:04:46.713+0000] 192.168.10.253 - [Tue Dec 11 10:04:46 CST 2018] "/browser/assets/images/device-icons/favicon-32x32.png?null" 200 2216 "http://192.168.10.236:7474/browser/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36" 1
#*****************************************************************
#*****************************************************************
dbms.connectors.default_listen_address=0.0.0.0
#dbms.connectors.default_advertised_address=localhost
dbms.connector.bolt.enabled=true
dbms.connector.bolt.tls_level=OPTIONAL
dbms.connector.bolt.listen_address=:7687
dbms.connector.http.enabled=true
dbms.connector.http.listen_address=:7474
dbms.connector.https.enabled=true
dbms.connector.https.listen_address
neo4j.conf File settings as above.Never been able to access the database remotely
12-10-2018 06:21 PM
the screenshot of browser
12-11-2018 01:35 PM
We provide support to run Neo4j in Azure in an easy way, you can read about that here:
https://neo4j.com/developer/neo4j-cloud-azure-image/
However -- if you want to stick with the Docker approach, have you verified that through your network settings port 7687 is open? It's not clear why the connection is failing, so I'm wondering if you've eliminated connection timeouts or firewall / dropped packets as a cause.
12-12-2018 02:48 AM
Earlier it was working perfectly fine sincelast 2 months. Suddenly this error occurred last week. All ports are open.
12-12-2018 08:04 AM
I'm going to try to raise this to more attention internally and see if I can find you an answer; please stand by. When you say "all ports are open", it would help if you could post the evidence that port 7687 is open for TCP because that's the most likely culprit in my mind. Port 7474 and 7473 affect how you fetch the web page that is Neo4j Browser, but when you try to connect to the database you're going over port 7687 (bolt TCP) to the database directly.
12-12-2018 08:14 AM
Hi All,
We had identified a regression in Neo4j 3.5.0 that prevents the discovery document (which Neo4j Browser uses to discover the bolt address) being served includes localhost
as the host name rather than the expected host name derived from the request URI.
The bug has already been fixed in the code base and will be included in the next patch release.
In the meantime, you can explicitly set dbms.connector.bolt.advertised_address
configuration option to your expected externally visible address, for example to 192.168.10.216:7687
as per the screen shot @mp5088643 has shared earlier in the thread.
12-21-2018 01:40 AM
Any update on the solution above ? I have just tried this solution with Community Edition 3.5.1 and I face the same issue as well. After reading some posts for solutions, I have the following configurations set up in the neo4j.conf file.
neo4j.conf:
dbms.connectors.default_listen_address=0.0.0.0
dbms.connectors.default_advertised_address="external IP"
dbms.connector.bolt.tls_level=OPTIONAL
dbms.connector.bolt.listen_address=:7687
dbms.connector.http.listen_address=:7474
dbms.connector.https.listen_address=:7473
Environment:
I can access the Neo4j browser via localhost but not via IP. Any comments and suggestions ? Thanks very much !
Thomas
01-26-2019 04:22 AM
Can you try what Ali shared here:
07-26-2019 06:44 AM
Hi, unfortunately there is no neo4j.conf file created during the installation of Desktop version...should it be manually created? In what location? Thanks
08-28-2019 11:28 AM
It is created when you create a graph instance and then you can access it from that graph
02-15-2020 06:11 AM
I am sure I'm being dim, but I am having what I think to be the same problem. I set up Neo4j 3.5.14 on Ubuntu server 18.04.3 and can connect on the IP address: https://MYIPADDRESS:7594/browser/
When I first set up the server I was able to ignore the SSL warning and continue through to the browser. I was able to connect to the database and run queries. However when I tried today I got the error:
WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver.**
I check the browser console and I see:
WebSocket connection to 'wss://MYIPADDRESS:7288/' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID
I don't have a certificate and can't install one with certbot as I only want to run this directly on the server IP address. I don't really want to set up a subdomain just for this server.
Settings in my /etc/neo4j/neo4j.conf
file are:
`
dbms.connector.bolt.enabled=true
dbms.connector.bolt.tls_level=OPTIONAL
dbms.connector.bolt.listen_address=0.0.0.0:7288
dbms.connector.http.enabled=true
#dbms.connector.http.listen_address=:7594
dbms.connector.https.enabled=true
dbms.connector.https.listen_address=0.0.0.0:7594`
Any idea how to fix this please?
Thanks!
All the sessions of the conference are now available online