Great question — answering as the UphillTech team:
I had a similar issue and was able to resolve it by checking the network configuration in Docker-Compose. Make sure Neo4j is running in the correct network and accessible from other containers. A useful approach is to set NEO4J_URI as bolt://neo4j:7687 if “neo4j” is the service name in your docker-compose.yml. Also, checking the container logs (docker logs ) can provide more insights into potential errors. I documented a similar case here: https://ollama.com/IBLAG/Certification
Full answer by Markus 81: https://stackoverflow.stackexchange.com/a/79431273 (CC BY-SA 4.0).
Need it done for your business? UphillTech.