Haridas N

Yes, it works in Safari and firefox quantum. But not on chrome-62.0.3202.94. Also I got the connection issue on neo4j-3.3.0 version initially, then was downgraded to 3.2.8 and trying. **conf/neo4j.conf**...

Hostname used to access the "https" and "bolt" are same. Usually UI will show the default hostname from this property for bolt connection `dbms.connectors.default_advertised_address`. Port is different thought, https using...

Tested on chrome 58 and other different versions, the problem seems persisting. We are using wildcard certificate for our domain(`*.domain.com`), will that have any thing todo with this ? The...

Now it worked, changes done on the `conf/neo4j.conf` file. ```text bolt.ssl_policy=legacy https.ssl_policy=legacy ``` I put our wild card certificate and key in legacy location `./certificates/neo4j.cert` and `./certificates/neo4j.key`. The `default` ssl...

I noticed another thing, may be it's a bug or indented behavior. peers binding its ports to the hostname it gets from the os command `hostname`, which may not be...

Sure @diestrin, I will check and update the PR.

Thanks for showing interest in adding this feature into the library. I will send you a pull request with Ketama implementation done on it.

Hi, I committed changes on the forked version of this repository. This is the initial version of changes to see how it works and how I was used it before...

Cool ! I would like to see the new changes that you make on the codebase, please update this issue or via PR also fine for me. Thank you.

Awesome. Thanks for making the code much better. Hoping to getting it merged soon.