[Bug]: Frontend stuck on "Loading…" after local Docker installation

[MammadTavakoli]

Bug Description

Hi team,

I followed the Hoop.dev Docker installation guide
to run Hoop locally on a VM. All containers start successfully, but when I open the developer portal at http://:8009, the page shows “Loading…” indefinitely.

When I inspect the network requests in the browser, the request to /api/publicserverinfo returns 0 B:

GET http:///api/publicserverinfo

My .env file is currently:

API_URL=http://:8009
GRPC_URL=http://:8010

I’ve checked that:

Ports 8009 and 8010 are open on the VM firewall.

docker compose ps shows all containers are up.

Logs don’t show obvious errors, but the frontend never receives API data.

Could you clarify:

What should the correct API_URL and GRPC_URL be for a local Docker deployment?

Are there any additional steps needed to make the frontend reach the backend?

Thanks in advance!

Steps to Reproduce

I followed the Hoop.dev Docker installation guide to run Hoop locally on a VM.

Expected Behavior

it must show the landing page

Actual Behavior

Frontend stuck on "Loading…" after local Docker installation

Version

1.42.9

Browser(s)

Firefox

Operating System

ubunto 24.04

Screenshots

No response

Additional Context

Disable Cache
12 requests
9.14 MB / 0 B transferred
Finish: 2.53 s
DOMContentLoaded: 2.23 s
load: 2.28 s

OPTIONS
http://10.1.49.122/api/publicserverinfo
Transferred0 B (0 B size)
Referrer Policystrict-origin
DNS ResolutionSystem

Accept
/
Accept-Encoding
gzip, deflate
Accept-Language
en-US,en;q=0.5
Access-Control-Request-Headers
authorization,content-type,user-client
Access-Control-Request-Method
GET
Connection
keep-alive
Host
10.1.49.122
Origin
http://10.1.49.122:8009
Priority
u=4
Referer
http://10.1.49.122:8009/
User-Agent
Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0

Relevant Log Output

Code of Conduct

• I agree to follow this project's Code of Conduct

[matheusfrancisco]

Hey, thanks for reporting this issue. I was trying to reproduce it and didn't have success
Did you run the command https://hoop.dev/docs/setup/deployment/docker-compose

touch .env && curl -sL https://hoop.dev/docker-compose.yml > docker-compose.yml && docker compose up

When you said

My .env file is currently:
API_URL=http://:8009
GRPC_URL=http://:8010

I’ve checked that:

You create .env with those env, if so, could you try with the command above without your .env.
Because Docker Compose already has those env, so my guess is you are overriding for an internal Docker IP if you want a different environment from docker-compose, then you can override it other.

name: hoop

services:
  db:
    image: postgres:17.6
    networks:
      - hoopdev
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: hoopdb
      PGUSER: postgres
    healthcheck:
      test: ["CMD-SHELL", "pg_isready", "-U", "postgres"]
      interval: "2s"
      timeout: "30s"
      retries: 10
      start_period: "20s"
  gateway:
    image: hoophq/hoop
    environment:
      - GIN_MODE=release
      - POSTGRES_DB_URI=postgres://postgres:postgres@db:5432/hoopdb?sslmode=disable
      - DLP_PROVIDER=mspresidio
      - DLP_MODE=best-effort
      - MSPRESIDIO_ANALYZER_URL=http://presidio-analyzer:3000
      - MSPRESIDIO_ANONYMIZER_URL=http://presidio-anonymizer:3000
    env_file: ".env"
    command: ["hoop", "start", "gateway"]
    ports:
      - "8009:8009"
      - "8010:8010"
      - "15432:15432"
      - "12222:12222"
      - "13389:13389"
    networks:
      - hoopdev
    depends_on:
      db:
        condition: "service_healthy"
    healthcheck:
      test:
      - CMD-SHELL
      - |
        PROTO=http; [ -n "$$TLS_KEY" ] && PROTO=https
        curl -k -f $$PROTO://127.0.0.1:8009/api/healthz || exit 1
      interval: "2s"
      timeout: "30s"
      retries: 10
      start_period: "20s"
  agent:
    image: hoophq/hoopdev
    networks:
      - hoopdev
    env_file: ".env"
    environment:
      - POSTGRES_DB_URI=postgres://postgres:postgres@db:5432/hoopdb?sslmode=disable
      - DEFAULT_AGENT_GRPC_HOST=gateway:8010
      - HOOP_GATEWAY_URL=ws://gateway:8009
    depends_on:
      gateway:
        condition: "service_healthy"
    command: hoop-default-agent.sh

  presidio-analyzer:
    image: mcr.microsoft.com/presidio-analyzer:2.2.360
    networks:
      - hoopdev
    depends_on:
      gateway:
        condition: "service_healthy"

  presidio-anonymizer:
    image: mcr.microsoft.com/presidio-anonymizer:2.2.360
    networks:
      - hoopdev
    depends_on:
      gateway:
        condition: "service_healthy"

networks:
  hoopdev:

https://drive.google.com/file/d/1ZJ2C47L8rpYTThZvaHpn6frGrTOTCOOK/view?usp=drive_link

I did the same process on OSx and Ubuntu.

[svetlinsem]

I have the same issue. My deploy is in Hetzner.
Ubuntu 24.04 no firewall.
No errors in the docker.
I have this error in chrome:
Failed to load resource: net::ERR_CONNECTION_REFUSED

[MammadTavakoli]

Hey, thanks for reporting this issue. I was trying to reproduce it and didn't have success Did you run the command https://hoop.dev/docs/setup/deployment/docker-compose

touch .env && curl -sL https://hoop.dev/docker-compose.yml > docker-compose.yml && docker compose up

When you said

My .env file is currently:
API_URL=http://:8009
GRPC_URL=http://:8010

I’ve checked that:

You create .env with those env, if so, could you try with the command above without your .env. Because Docker Compose already has those env, so my guess is you are overriding for an internal Docker IP if you want a different environment from docker-compose, then you can override it other.

name: hoop

services:
db:
image: postgres:17.6
networks:
- hoopdev
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
POSTGRES_DB: hoopdb
PGUSER: postgres
healthcheck:
test: ["CMD-SHELL", "pg_isready", "-U", "postgres"]
interval: "2s"
timeout: "30s"
retries: 10
start_period: "20s"
gateway:
image: hoophq/hoop
environment:
- GIN_MODE=release
- POSTGRES_DB_URI=postgres://postgres:postgres@db:5432/hoopdb?sslmode=disable
- DLP_PROVIDER=mspresidio
- DLP_MODE=best-effort
- MSPRESIDIO_ANALYZER_URL=http://presidio-analyzer:3000
- MSPRESIDIO_ANONYMIZER_URL=http://presidio-anonymizer:3000
env_file: ".env"
command: ["hoop", "start", "gateway"]
ports:
- "8009:8009"
- "8010:8010"
- "15432:15432"
- "12222:12222"
- "13389:13389"
networks:
- hoopdev
depends_on:
db:
condition: "service_healthy"
healthcheck:
test:
- CMD-SHELL
- |
PROTO=http; [ -n "$$TLS_KEY" ] && PROTO=https
curl -k -f $$PROTO://127.0.0.1:8009/api/healthz || exit 1
interval: "2s"
timeout: "30s"
retries: 10
start_period: "20s"
agent:
image: hoophq/hoopdev
networks:
- hoopdev
env_file: ".env"
environment:
- POSTGRES_DB_URI=postgres://postgres:postgres@db:5432/hoopdb?sslmode=disable
- DEFAULT_AGENT_GRPC_HOST=gateway:8010
- HOOP_GATEWAY_URL=ws://gateway:8009
depends_on:
gateway:
condition: "service_healthy"
command: hoop-default-agent.sh

presidio-analyzer:
image: mcr.microsoft.com/presidio-analyzer:2.2.360
networks:
- hoopdev
depends_on:
gateway:
condition: "service_healthy"

presidio-anonymizer:
image: mcr.microsoft.com/presidio-anonymizer:2.2.360
networks:
- hoopdev
depends_on:
gateway:
condition: "service_healthy"

networks:
hoopdev:

https://drive.google.com/file/d/1ZJ2C47L8rpYTThZvaHpn6frGrTOTCOOK/view?usp=drive_link

I did the same process on OSx and Ubuntu.

I test with your solution and new version. but the problem is continues

[racerxdl]

Btw @MammadTavakoli can you share a screenshot of the browser network tab? It might be easier to understand what's happening ^^

[grov]

Hello ! I have exactly the same issue on a Ubuntu 25.04 VM hosted in OVH.
Here is a screenshot :

[grov]

Maybe a more explicit screenshot showing a CORS issue ? :
Or maybe it should access "http://xxx.cloud:8009/api/publicserverinfo" instead of "http://xxx.cloud/api/publicserverinfo" ?

[MammadTavakoli]

I have problem with this now again