I have a core-only cluster with 3 neo4j servers that are part of a sub-domain.
Core1 - Has 2 Network Interfaces - Public IP is the listener address
Core2 - Has 2 Network Interfaces - Public IP is the listener address
Core3 - Has 2 Network Interfaces - Public IP is the listener address
ARecords that point to Core1, Core2, Core3 's IP Addresses listed and this is the same used for RAFT as well. I see a lot of success information in logs as well as query info in
- I do not use DNS names inside the
neo4j.confand instead the public IPs.
- It's a grandstack app.
reacttalk to each other, Graphql talks to a
core-onlycluster will replace the
SINGLEdatabase when ready.
I have used Letsencrypt certbot to generate my certs i.e. publicly signed for all my cores by their IP Addresses. Each server has it's own certbot generated cert (DNS ACME Challenge).
The Cluster seems to be working. I ran a portion of my seeding and everything on the cluster looks peachy (well almost). This is not a production cluster today but in a week I want to use this as my main
neo4j instances in a specific region.
- I started having difficulties with
neo4j+sdriver on both GraphQL as well as on Neo4J Desktop.
- I cannot connect directly to my cluster unless the
Temporary Stepsis done.
- I have a
trust: 'TRUST_ALL_CERTIFICATES',for my GraphQL driver.
- I connect to
- After connecting I do
:server disconnectand then can use
I want to fix my cluster and and my
graphql as well. I cannot use the
TRUST_ALL_CERTIFICATES as this is completely counter-intuitive to having publicly-signed certs.
How do I debug? How do I proceed forward? This is probably my last step before I can finalise my cluster and move to production.