Troubleshooting

It is possible that you run into issues with the Neo4j configuration. For example, the Neo4j Browser may produce an error that the database is unavailable. To print your Docker logs, run Docker without the –rm flag and please run the following command:

docker logs neo4j

The logs may suggest that you adjust a parameter in the configuration file. It is not possible to do this within the Docker, but you can adjust the command you use to start the Docker to set these parameters. For detailed instructions, check the and the summary of configuration settings. In brief, you can add any of the configuration settings by adding a NEO4J prefix, replacing . with _ (a single underscore) and replacing _ with __ (double underscores). For example, to allow the database to upgrade, you could run the following command:


docker run -d -v 
           data:/data 
           --publish=7475:7474 
           --publish=7688:7687
           --name=neo4j 
           --env NEO4J_AUTH=neo4j/test 
           --env NEO4J_dbms_allow__upgrade=true
           neo4j:4.2.0