Failed to connect to web interface with conf in volume about docker-neo4j

[spacecowboy]

@toddleo I would guess that there is a problem with your configuration files in ${CONF_DIR}. Could you post their contents?

[toddleo]

@spacecowboy Hi Jonas, thanks for your concern.

As I said, my configuration files in ${CONF_DIR} is dumped from the official neo4j docker image, and their contents are untouched. Posting all contents is too verbose, and I thought maybe posting each md5 is enough:

48d847f235e702a0812a8e37d35821f4  ./neo4j-http-logging.xml
4829c92593e1bb2c79080eec5fb6b1f7  ./neo4j.properties
a07d6c229478f60154c4e1f607bb522b  ./neo4j-server.properties
8338e742125c96ed0716463f176fb1ad  ./neo4j-wrapper.conf
6eb5b8fbea7447287c23de354411a352  ./README.txt

[toddleo]

Inside the container, I can successfully reach the 7474 port via curl:

root@040ce878d09c:/var/lib/neo4j# curl 127.0.0.1:7474
{
  "management" : "http://127.0.0.1:7474/db/manage/",
  "data" : "http://127.0.0.1:7474/db/data/"
}

also, this request is logged in data/http.log.

However, I still get Connection reset by peer failure from the host machine, and data/http.log doesn't document this request. Didn't --publish=7474:7474 work? Also tried other ports but doesn't help.

[benbc]

@toddleo Thanks for reporting this. Can you give me a bit more information, please? What versions of Docker and Neo4j are you using? What platform are you running on?

[toddleo]

@benbc Hi Ben,

I'm using the neo4j docker image from docker hub, which I believe it is still the latest. Image ID: 7d94602c724e .

My docker version is Docker version 1.10.3, build 20f81dd.

Should I also try the Official Neo4j Image for Production Use?

[benbc]

Hello @toddleo. We recommend using the image from the official library, but it's basically identical to the one in neo4j/neo4j, so it won't fix your problem.

What platform are you running on?

[toddleo]

Ahhh forgot to attach my environment. We are running docker on Gentoo 2.2, with 4.0.5-gentoo-ks kernel.

[benbc]

@toddleo Please could I ask you to try the same thing but without mounting the /conf volume, so that we can rule out the possibility of config problems?

docker run --rm --publish=7474:7474 --volume=${DB_DIR}:/data/graph.db neo4j

[toddleo]

@benbc Hi Ben,

I did what you said, except with --publish=7478:7474 since my friends are currently using that port hosting the other neo4j container.

In this case, 7478 port can be well reached by curl.

[benbc]

Thanks, @toddleo. Could you run this, please?

docker run --volume=/tmp/conf:/conf neo4j dump-config
diff /tmp/conf ${CONF_DIR}

[toddleo]

@benbc Hi Ben,

Absolutely, the diff command prints the following:

$ diff /tmp/conf ${CONF_DIR}
diff /tmp/conf/neo4j-server.properties /home/users/liulx/dk/dm-graph/cs-it/conf.d/neo4j-server.properties
68c68
< org.neo4j.server.http.log.enabled=false
---
> org.neo4j.server.http.log.enabled=true

It is worth to point out that the only difference on log.enabled is exactly what I changed to see what's going on with the http server, after I discovered this issue.

Apologies for this late reply.

[toddleo]

Turns out you have to uncomment this, before using custom conf files, even the content is exactly the same:

# To have HTTP accept non-local connections, uncomment this line
dbms.connector.http.address=0.0.0.0:7474

[benbc]

@toddleo You are quite right, I should have thought of that. Well spotted. We'll add something to the docs about this.

[toddleo]

@benbc Hi Ben,

I reckon it's better off allow non-local connections by default when using docker, or at least add an environment variable when starting docker container:

--env=NEO4J_dbms_connector_http_address=0.0.0.0:7474

[jmwnoble]

Could a line be added to the documentation, section 2.5.4.2. /conf volume indicating that this needs to be uncommented:
To accept non-local connections, uncomment this line:
dbms.connectors.default_listen_address=0.0.0.0

Will save people time if they have this issue, which I bumped into today

[spacecowboy]

we'll do that @jmwnoble

[jjaderberg]

@jmwnoble a note to that effect has been added and will be published in a few days or so