Open kevinschaper opened 7 months ago
Thinking about this issue, I think this is actually a problem with how we deploy the neo4j VM on the stack in a way that creates blocks on ports which should be open for a standard Neo4J server. I think this is related to the core issue of some weirdness in the way the google cloud deploy is done;
https://github.com/monarch-initiative/monarch-stack-v3/issues/31
Default connect info is currently
neo4j://
connection to neo4j.monarchinitiative.org, but we need it to be a bolt:// connection to neo4j-bolt.monarchinitiative.org