The operation is insecure
Gregory King
Hi all,
Merging all these posts into one as I think they all have the same underlying cause. We're working on solutions to make this error less common or easier to navigate (though doing so is proving harder than we would like). In the interim, you should find this helps:
If you are connecting to a
non
-certificate secured neo4j instance (ie with one of the following url schemes, neo4j://
or bolt://
), typically a Neo4j Desktop instance or self managed local install then please make sure you use the data importer app hosted at http://data-importer.graphapp.io.If you are using a certificate secured neo4j instance (ie with one of the following url schemes,
neo4j+s://
or bolt+s://
), typically an Aura instance or one that you have setup certificates for yourself, then please make sure you use the data importer app hosted at https://data-importer.neo4j.io.Note that the
http://
vs the https://
is what is makes the difference here and the http://
variant is currently not available on the neo4j.io domain. Please let us know if you encounter any issues and we can help out on this thread. Thanks for your patience while we work on a cleaner solution.Greg
Gregory King
Merged in a post:
Websocket error
mario.gledhill@education.gov.uk
I'm trying out the data importer against our Aura DB and getting the following websocket issue in edge and chrome.
"An Error Occurred: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS."
Gregory King
Merged in a post:
An Error Occurred: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
pratyushag8912@outlook.com
i geeting this error
An Error Occurred: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
Gregory King
Hey,
Sorry you're having issues connecting.
Were you connecting to an Aura instance or a self managed Neo4j instance? For Aura the host should be populated for you, but if you were connecting to your own instance, what URL scheme prefix were you using (eg neo4j://, bolt://, neo4j+s:// etc)?
This may help me identify what the root cause of the error you're seeing is.
Thanks!
Greg