Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontend does not connect to local docker instance neo4j with APOC installed #1057

Open
CanBayraktaroglu opened this issue Feb 4, 2025 · 3 comments

Comments

@CanBayraktaroglu
Copy link

CanBayraktaroglu commented Feb 4, 2025

db is running smoothly at bolt://localhost:7687

still, i am unable to connect to this using the login popup on frontend.

After selecting bolt; i have tried typing all "://localhost:7687", "bolt://localhost:7687", "localhost:7687"

none of them work and some of them somehow resolve to bolt:7687 in the backend.

Anyone encountered the same problem?

@dhiaaeddine16
Copy link
Contributor

If you continue to encounter connectivity issues, you might opt for Docker’s host networking mode. This makes the container share the host’s network stack, which can eliminate issues related to port mapping.

To run with host networking, use:

docker run --rm --name neo4j  --network="host" \
      -e NEO4J_apoc_export_file_enabled=true \
      -e NEO4J_apoc_import_file_enabled=true \
      -e NEO4J_apoc_import_file_use__neo4j__config=true \
      -e NEO4J_PLUGINS='["apoc"]' \
      -d neo4j:5.24.2-community

This approach lets the container use the host’s IP address directly, which might resolve any networking isolation problems.

@richdatasci
Copy link

If you continue to encounter connectivity issues, you might opt for Docker’s host networking mode. This makes the container share the host’s network stack, which can eliminate issues related to port mapping.

To run with host networking, use:

docker run --rm --name neo4j  --network="host" \
      -e NEO4J_apoc_export_file_enabled=true \
      -e NEO4J_apoc_import_file_enabled=true \
      -e NEO4J_apoc_import_file_use__neo4j__config=true \
      -e NEO4J_PLUGINS='["apoc"]' \
      -d neo4j:5.24.2-community

This approach lets the container use the host’s IP address directly, which might resolve any networking isolation problems.

I've just tried this as I was having the same issue as the OP.

It has created a neo4j container which I can open and connect to the local DB..

Image

I am still getting the issue when trying to connect on the LLM builder app popup page:

Image

Any advice?

@danielpettycognizant
Copy link

Have you tried neo4j://host.docker.internal:7687?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants