[GH-ISSUE #1536] Controlling Nginx in another Docker Container from Nginx-UI running in a Container, failed API calls #3065

Open
opened 2026-02-27 12:30:49 +03:00 by kerem · 0 comments
Owner

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

Originally assigned to: @0xJacky, @Copilot on GitHub.

Describe the bug
When using the ContainerName feature to control Nginx in another Container, I see the following error message in the Nginx-UI logs:

nginxui-1  | 2026-02-01 13:45:30.235    ERROR   docker/stat_path.go:24  Failed to stat path error request returned 404 Not Found for API route and version http://%2Fvar%2Frun%2Fdocker.sock/v1.51/containers/nginx/archive?path=%2Frun%2Fnginx.pid, check if the server supports the requested API version

My docker-compose.yml includes the

To Reproduce
Steps to reproduce the behavior:

  1. Start Nginx-UI via Compose:
services:
  nginxui:
    image: 'uozi/nginx-ui:latest'
    restart: unless-stopped

    ports:
      # These ports are in format <host-port>:<container-port>
      #- '80:80' # Public HTTP Port
      #- '443:443' # Public HTTPS Port
      - '9000:9000' # UI?

    environment:
      TZ: "Europe/Berlin"
      #NGINX_UI_IGNORE_DOCKER_SOCKET: true
      NGINX_UI_SERVER_PORT: 9000
      NGINX_UI_SERVER_RUN_MODE: release
      NGINX_UI_NGINX_CONTAINER_NAME: nginx

    volumes:
      - ./appdata/nginx:/etc/nginx
      - ./appdata/nginx-logs:/var/log/nginx
      - ./appdata/nginx-ui:/etc/nginx-ui
      - ./var/www:/var/www
      - /var/run/docker.sock:/var/run/docker.sock
  1. Start a Nginx Container via Compose, for example like this:
services:
  nginx:
    image: nginxinc/nginx-unprivileged:latest
    container_name: nginx
    ports:
      - "8080:8080"
    volumes:
      # Main nginx config
      - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
      # Site configs
      - ./nginx/conf.d:/etc/nginx/conf.d:ro
      # Optional: logs on host
      - ./nginx/logs:/var/log/nginx
    restart: unless-stopped
  1. Log in to Nginx-UI, go to Nginx and you see the message Get data failed, Nginx is not running

Expected behavior
I would expect to see a connection to the Nginx Container.

Info (please complete the following information):

  • Server OS: Ubuntu Server 24.04 LTS
  • Server Arch: amd64
  • Nginx UI Version: 2.3.2
  • Your Browser: Edge, Chrome and Vivaldi

Additional context
According to the Documentation I got the impression that the only thing I need to do are including the Docker Socket in the Stack and tell Nginx-UI either in the compose file or in the app.ini the name of the nginx Container.
I suspected, that this is an issue with the Docker API version, which recently bumped up their minimum version, which caused issues with other software as well. So I went ahead and lowered the minimum API version of my Docker installation to 1.24, but this did not help.

Originally created by @kladderadeng on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1536 Originally assigned to: @0xJacky, @Copilot on GitHub. **Describe the bug** When using the ContainerName feature to control Nginx in another Container, I see the following error message in the Nginx-UI logs: ``` nginxui-1 | 2026-02-01 13:45:30.235 ERROR docker/stat_path.go:24 Failed to stat path error request returned 404 Not Found for API route and version http://%2Fvar%2Frun%2Fdocker.sock/v1.51/containers/nginx/archive?path=%2Frun%2Fnginx.pid, check if the server supports the requested API version ``` My docker-compose.yml includes the **To Reproduce** Steps to reproduce the behavior: 1. Start Nginx-UI via Compose: ```yaml services: nginxui: image: 'uozi/nginx-ui:latest' restart: unless-stopped ports: # These ports are in format <host-port>:<container-port> #- '80:80' # Public HTTP Port #- '443:443' # Public HTTPS Port - '9000:9000' # UI? environment: TZ: "Europe/Berlin" #NGINX_UI_IGNORE_DOCKER_SOCKET: true NGINX_UI_SERVER_PORT: 9000 NGINX_UI_SERVER_RUN_MODE: release NGINX_UI_NGINX_CONTAINER_NAME: nginx volumes: - ./appdata/nginx:/etc/nginx - ./appdata/nginx-logs:/var/log/nginx - ./appdata/nginx-ui:/etc/nginx-ui - ./var/www:/var/www - /var/run/docker.sock:/var/run/docker.sock ``` 2. Start a Nginx Container via Compose, for example like this: ```yaml services: nginx: image: nginxinc/nginx-unprivileged:latest container_name: nginx ports: - "8080:8080" volumes: # Main nginx config - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro # Site configs - ./nginx/conf.d:/etc/nginx/conf.d:ro # Optional: logs on host - ./nginx/logs:/var/log/nginx restart: unless-stopped ``` 3. Log in to Nginx-UI, go to Nginx and you see the message `Get data failed, Nginx is not running` **Expected behavior** I would expect to see a connection to the Nginx Container. **Info (please complete the following information):** - Server OS: Ubuntu Server 24.04 LTS - Server Arch: amd64 - Nginx UI Version: 2.3.2 - Your Browser: Edge, Chrome and Vivaldi **Additional context** According to [the Documentation](https://nginxui.com/guide/config-nginx.html) I got the impression that the only thing I need to do are including the Docker Socket in the Stack and tell Nginx-UI either in the compose file or in the app.ini the name of the nginx Container. I suspected, that this is an issue with the Docker API version, which recently bumped up their minimum version, which caused issues with other software as well. So I went ahead and lowered the minimum API version of my Docker installation to 1.24, but this did not help.
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#3065
No description provided.