# Connecting multiple spaces, error on neo4j

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fconnecting-multiple-spaces-error-on-neo4j%2F98091%3E%5C
**Category:** Research\
**Created:** [July 18, 2024, 8:04am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fconnecting-multiple-spaces-error-on-neo4j%2F98091 "2024-07-18T08:04:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![melihdarcan](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@melihdarcan](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmelihdarcan)%5C
**Post date:** [July 18, 2024, 8:04am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fconnecting-multiple-spaces-error-on-neo4j%2F98091%2F1 "2024-07-18T08:04:49Z")

</div>

Hello everyone, we are a Bioinformatics research group currently at nearly the end of a research project.

Our current workflow includes Neo4j, Apollo (GraphQL), Streamlit, NGINX (to host a multipage website, and to proxy\_pass other services to website paths like /neo4j)

Every service is defined with a Dockerfile, and then all of them are connected with a docker compose file.

For neo4j, we are using Docker Spaces and, we couldn’t get it to working. Other public examples on the huggingface doesn’t build, ours do. But it doesn’t work somehow.

> **[Neo4j Test - a Hugging Face Space by melihdarcan](https://huggingface.co/spaces/melihdarcan/neo4j-test)**
>
> Discover amazing ML apps made by the community

 ![image](https://us1.discourse-cdn.com/hellohellohello/original/3X/a/f/af844dd016af48a0771bfe3d8f8eb03d7c9bab8e.png)

The error above happens. Would using nginx in the docker container help with headers, maybe?

For apollo, and streamlit we still want to use Docker Spaces and connect them to neo4j space. To be able to connect them to neo4j, do we have to set up inference endpoints feature for neo4j?

Finally, for the website, we can use nginx with docker space / GitHub pages / other available huggingface service that is proper for our usage.

We’re glad to have your feedback and suggestions. How can we achieve such infrastructure with Huggingface? Or should we look at other services?