[GH-ISSUE #1556] Docker Compose: Unable to Connect #5288

Open
opened 2026-03-01 15:40:59 +03:00 by kerem · 0 comments
Owner

Originally created by @Foxxify1 on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1556

Describe the bug
I used the example docker compose to write my own stack, with a cloudflare tunnel, some bind mounts, and internal network that will be for adding containers to. However, after deploying my compose, I was not able to access the panel at http://<your_server_ip>:8080/install, making me unable to set up my instance.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy docker compose
  2. Navigate to http://<your_server_ip>:8080/install
  3. Get 'Unable to Connect' error

Expected behavior
I should be able to access the container at the URL in the docs

Info (please complete the following information):

  • Server OS: TrueNAS Scale 25.10.1 (kernel 6.12.33)
  • Server Arch: x86_64
  • Nginx UI Version: 2.3.2
  • Your Browser: Firefox

Additional context
I ended up binding 9000:9000 and being able to set it up there, but only after I did a combination of clearing my bind mount directories, setting NGINX_UI_IGNORE_DOCKER_SOCKET=true with the guidance of DeepWiki (I don't know if this helped), and waaaay more research than it should have taken.

Here is my docker compose for reference

compose.yaml

I only changed my port mappings to 80:80 443:443 after I gained access to the Nginx UI panel.

services:

  cloudflared:
    image: cloudflare/cloudflared
    container_name: cloudflare-tunnel
    restart: unless-stopped
    command: tunnel --no-autoupdate run -token ${CLOUDFLARED_TOKEN}
    networks:
      - public-proxy

  nginx-ui:
    image: uozi/nginx-ui:${VERSION:-latest}
    container_name: nginx-ui
    restart: always
    stdin_open: true
    tty: true
    environment:
      - TZ=${TIMEZONE:-UTC}
      - NGINX_UI_IGNORE_DOCKER_SOCKET=true
    networks:
      - reverse-proxy
      - public-proxy
    ports:
      - 80:80
      - 443:443
      - 9000:9000
    volumes:
      - data:/etc/nginx
      - config:/etc/nginx-ui
      - www:/var/www

networks:
  reverse-proxy:
  public-proxy:

volumes:
  data:
    name: nginx-ui-data
    driver_opts:
      type: none
      o: bind
      device: ${DATA_LOCATION}/data
  config:
    name: nginx-ui-config
    driver_opts:
      type: none
      o: bind
      device: ${DATA_LOCATION}/config
  www:
    name: nginx-ui-www
    driver_opts:
      type: none
      o: bind
      device: ${DATA_LOCATION}/www
Originally created by @Foxxify1 on GitHub (Feb 11, 2026). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1556 **Describe the bug** I used the example docker compose to write my own stack, with a cloudflare tunnel, some bind mounts, and internal network that will be for adding containers to. However, after deploying my compose, I was not able to access the panel at http://<your_server_ip>:8080/install, making me unable to set up my instance. **To Reproduce** Steps to reproduce the behavior: 1. Deploy docker compose 2. Navigate to http://<your_server_ip>:8080/install 3. Get 'Unable to Connect' error **Expected behavior** I should be able to access the container at the URL in the docs **Info (please complete the following information):** - Server OS: TrueNAS Scale 25.10.1 (kernel 6.12.33) - Server Arch: x86_64 - Nginx UI Version: 2.3.2 - Your Browser: Firefox **Additional context** I ended up binding 9000:9000 and being able to set it up there, but only after I did a combination of clearing my bind mount directories, setting NGINX_UI_IGNORE_DOCKER_SOCKET=true with the guidance of [DeepWiki](https://deepwiki.com/0xJacky/nginx-ui/2.3-docker-deployment) (I don't know if this helped), and waaaay more research than it should have taken. Here is my docker compose for reference <details> <summary>compose.yaml</summary> I only changed my port mappings to 80:80 443:443 after I gained access to the Nginx UI panel. ``` services: cloudflared: image: cloudflare/cloudflared container_name: cloudflare-tunnel restart: unless-stopped command: tunnel --no-autoupdate run -token ${CLOUDFLARED_TOKEN} networks: - public-proxy nginx-ui: image: uozi/nginx-ui:${VERSION:-latest} container_name: nginx-ui restart: always stdin_open: true tty: true environment: - TZ=${TIMEZONE:-UTC} - NGINX_UI_IGNORE_DOCKER_SOCKET=true networks: - reverse-proxy - public-proxy ports: - 80:80 - 443:443 - 9000:9000 volumes: - data:/etc/nginx - config:/etc/nginx-ui - www:/var/www networks: reverse-proxy: public-proxy: volumes: data: name: nginx-ui-data driver_opts: type: none o: bind device: ${DATA_LOCATION}/data config: name: nginx-ui-config driver_opts: type: none o: bind device: ${DATA_LOCATION}/config www: name: nginx-ui-www driver_opts: type: none o: bind device: ${DATA_LOCATION}/www ``` </details>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-ui#5288
No description provided.