I'm running 4.1 enterprise using the latest EC2 AMI (ami-0afe90add2767a91c).
When I ssh in, I'm unable to connect using cypher-shell locally:
$ cypher-shell -u neo4j -p -----------
Unable to connect to localhost:7687, ensure the database is running and that there is a working network connection to it.
But I can connect remotely and successfully query via the data browser or using cypher-shell:
$ cypher-shell -a --.--.--.-- -u neo4j -p ------------
So I'm pretty sure that there's a connection and the database is working.
I found that I can indeed connect locally using that address. But I don't see reference to the need to do that in the documentation. Is this something new or related to the AMI?
When you give a specific IP address the server will bind to only that IP address. By specifying 0.0.0.0, the server will try to bind to all the available network addresses of the server.
Based on the documentation link above, I understand that it should be possible to modify the value of $dbms_default_listen_address by using a VM tag. This is an EC2 instance, so I set the tag per Tag your Amazon EC2 resources - Amazon Elastic Compute Cloud. Specifically, I created a tag with the name "dbms.default_listen_address" and a value of "0.0.0.0".
But even after rebooting, neo4j.conf is being generated as before.
Of course, I could just hard-code "0.0.0.0" into the template. But that would defeat the purpose of a template.
Does anyone know what I have to do to set this VM tag correctly? Or barring that, from where the default value is being set if there is no tag?