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

kerem commented

2026-03-01 15:40:56 +03:00

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:

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

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

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.

kerem added the

bug

label

2026-03-01 15:40:56 +03:00

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 6, 2026):

Thank you for your feedback. We will update the version of the Docker client to be compatible with the new version of the API.

@0xJacky commented on GitHub (Feb 6, 2026): Thank you for your feedback. We will update the version of the Docker client to be compatible with the new version of the API.

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 6, 2026):

@cursoragent Update Docker client verison to match the new api version.

@0xJacky commented on GitHub (Feb 6, 2026): @cursoragent Update Docker client verison to match the new api version.

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@cursor[bot] commented on GitHub (Feb 6, 2026):

I've successfully fixed the Docker client API version compatibility issue. Here's what I did:

Problem: The Docker client SDK v28.5.2 defaults to API version 1.51, which requires Docker Engine 28.x. When users run older Docker versions, API calls fail with "404 Not Found for API route and version".

Root Cause: While WithAPIVersionNegotiation() was used when creating the client, the manual Ping() call in initClient() didn't trigger the automatic version negotiation flow. The ping response contained the daemon's supported API version, but it wasn't being used to downgrade the client version.

Solution: After the Ping() call succeeds, I added an explicit call to cli.NegotiateAPIVersionPing(ping) which:

Takes the API version from the ping response
Downgrades the client's API version if the server version is lower than the client's default
Ensures subsequent API calls use a compatible version

The fix is minimal and follows the Docker SDK's recommended pattern for API version negotiation.

@cursor[bot] commented on GitHub (Feb 6, 2026): I've successfully fixed the Docker client API version compatibility issue. Here's what I did: **Problem:** The Docker client SDK v28.5.2 defaults to API version 1.51, which requires Docker Engine 28.x. When users run older Docker versions, API calls fail with "404 Not Found for API route and version". **Root Cause:** While `WithAPIVersionNegotiation()` was used when creating the client, the manual `Ping()` call in `initClient()` didn't trigger the automatic version negotiation flow. The ping response contained the daemon's supported API version, but it wasn't being used to downgrade the client version. **Solution:** After the `Ping()` call succeeds, I added an explicit call to `cli.NegotiateAPIVersionPing(ping)` which: - Takes the API version from the ping response - Downgrades the client's API version if the server version is lower than the client's default - Ensures subsequent API calls use a compatible version The fix is minimal and follows the Docker SDK's recommended pattern for API version negotiation. <a href="https://github.com/0xJacky/nginx-ui/pull/1543"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/view-pr-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/view-pr-light.png"><img alt="View PR" width="86" height="28" src="https://cursor.com/assets/images/view-pr-light.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-c80ad23f-9cb9-4208-a670-80f594c5a6fb"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> <a href="https://cursor.com/agents?id=bc-c80ad23f-9cb9-4208-a670-80f594c5a6fb"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 6, 2026):

Hi @kladderadeng, you can use the uozi/nginx-ui:dev image to check if the issue has been resolved.

@0xJacky commented on GitHub (Feb 6, 2026): Hi @kladderadeng, you can use the `uozi/nginx-ui:dev` image to check if the issue has been resolved.

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@kladderadeng commented on GitHub (Feb 8, 2026):

Thank you very much @0xJacky! In the meantime I switched to a native installation setup (nginx via apt and nginx-ui via install.sh), which proved to be working fine. I need to find a bit of time to spin up a setup with Docker again to test this.

@kladderadeng commented on GitHub (Feb 8, 2026): Thank you very much @0xJacky! In the meantime I switched to a native installation setup (nginx via apt and nginx-ui via install.sh), which proved to be working fine. I need to find a bit of time to spin up a setup with Docker again to test this.

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@kladderadeng commented on GitHub (Feb 8, 2026):

Fortunately, my Docker Test VM was still around.

I switched to the uozi/nginx-ui:dev image, but I still get the following error in the nginx-ui Container logs:

nginxui-1  | 2026-02-08 12:08:57.544    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

curl --silent -XGET --unix-socket /run/docker.sock http://localhost/version | jq .:

{
  "Platform": {
    "Name": "Docker Engine - Community"
  },
  "Version": "29.2.0",
  "ApiVersion": "1.53",
  "MinAPIVersion": "1.24",
  "Os": "linux",
  "Arch": "amd64",
  "Components": [
    {
      "Name": "Engine",
      "Version": "29.2.0",
      "Details": {
        "ApiVersion": "1.53",
        "Arch": "amd64",
        "BuildTime": "2026-01-26T19:27:07.000000000+00:00",
        "Experimental": "false",
        "GitCommit": "9c62384",
        "GoVersion": "go1.25.6",
        "KernelVersion": "6.8.0-94-generic",
        "MinAPIVersion": "1.24",
        "Os": "linux"
      }
    },
    {
      "Name": "containerd",
      "Version": "v2.2.1",
      "Details": {
        "GitCommit": "dea7da592f5d1d2b7755e3a161be07f43fad8f75"
      }
    },
    {
      "Name": "runc",
      "Version": "1.3.4",
      "Details": {
        "GitCommit": "v1.3.4-0-gd6d73eb8"
      }
    },
    {
      "Name": "docker-init",
      "Version": "0.19.0",
      "Details": {
        "GitCommit": "de40ad0"
      }
    }
  ],
  "GitCommit": "9c62384",
  "GoVersion": "go1.25.6",
  "KernelVersion": "6.8.0-94-generic",
  "BuildTime": "2026-01-26T19:27:07.000000000+00:00"
}

Since it says Minimum version is 1.24 and the current version is 1.54, and Nginx-UI seems to query 1.51 (which is in between), I think I should not get the error?
Since this seems to be an error thrown back by Docker to nginx-ui I am not even sure if this is something that can fixed on the nginx-ui side. I am not very deep into the Docker API to say on which side to fix this.

My current docker-compose.yml for nginx-ui:

services:
  nginxui:
    image: 'uozi/nginx-ui:dev'
    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?
      #- '81:81' # Stream Test
      # Add any other Stream port you want to expose
      # - '21:21' # FTP

    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

      # Uncomment this if you want to change the location of
      # the SQLite DB file within the container
      # DB_SQLITE_FILE: "/data/database.sqlite"

      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'

    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

@kladderadeng commented on GitHub (Feb 8, 2026): Fortunately, my Docker Test VM was still around. I switched to the uozi/nginx-ui:dev image, but I still get the following error in the nginx-ui Container logs: ``` nginxui-1 | 2026-02-08 12:08:57.544 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 ``` `curl --silent -XGET --unix-socket /run/docker.sock http://localhost/version | jq .`: ``` { "Platform": { "Name": "Docker Engine - Community" }, "Version": "29.2.0", "ApiVersion": "1.53", "MinAPIVersion": "1.24", "Os": "linux", "Arch": "amd64", "Components": [ { "Name": "Engine", "Version": "29.2.0", "Details": { "ApiVersion": "1.53", "Arch": "amd64", "BuildTime": "2026-01-26T19:27:07.000000000+00:00", "Experimental": "false", "GitCommit": "9c62384", "GoVersion": "go1.25.6", "KernelVersion": "6.8.0-94-generic", "MinAPIVersion": "1.24", "Os": "linux" } }, { "Name": "containerd", "Version": "v2.2.1", "Details": { "GitCommit": "dea7da592f5d1d2b7755e3a161be07f43fad8f75" } }, { "Name": "runc", "Version": "1.3.4", "Details": { "GitCommit": "v1.3.4-0-gd6d73eb8" } }, { "Name": "docker-init", "Version": "0.19.0", "Details": { "GitCommit": "de40ad0" } } ], "GitCommit": "9c62384", "GoVersion": "go1.25.6", "KernelVersion": "6.8.0-94-generic", "BuildTime": "2026-01-26T19:27:07.000000000+00:00" } ``` Since it says Minimum version is 1.24 and the current version is 1.54, and Nginx-UI seems to query 1.51 (which is in between), I think I should not get the error? Since this seems to be an error thrown back by Docker to nginx-ui I am not even sure if this is something that can fixed on the nginx-ui side. I am not very deep into the Docker API to say on which side to fix this. My current docker-compose.yml for nginx-ui: ```yaml services: nginxui: image: 'uozi/nginx-ui:dev' 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? #- '81:81' # Stream Test # Add any other Stream port you want to expose # - '21:21' # FTP 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 # Uncomment this if you want to change the location of # the SQLite DB file within the container # DB_SQLITE_FILE: "/data/database.sqlite" # Uncomment this if IPv6 is not enabled on your host # DISABLE_IPV6: 'true' 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 ```

kerem commented

2026-03-01 15:40:57 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 8, 2026):

@cursoragent fix this bugs

@0xJacky commented on GitHub (Feb 8, 2026): @cursoragent fix this bugs

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@cursor[bot] commented on GitHub (Feb 8, 2026):

I have completed the improvement of the StatPath function in Docker. Here are the changes I made:
Problem Analysis:
The 404 error reported by the user (request returned 404 Not Found for API route and version http://%2Fvar%2Frun%2Fdocker.sock/v1.51/containers/nginx/archive) is not actually an issue related to API version compatibility. The API version 1.51 should function properly (the user's Docker daemon is 1.53, which supports backward compatibility down to 1.24).
The actual problem:
The 404 error indicates that the Docker daemon cannot locate the specified container. Possible causes include:

The container name does not match (for example, using the default prefix of Docker Compose)
The container does not exist or is not running
The nginx-ui and nginx containers are in different Docker Compose projects
Solution:
The StatPath function in internal/docker/stat_path.go has been improved:

Before calling ContainerStatPath, it checks if the container exists.
If the container is not found, it provides detailed error information and troubleshooting tips.
It records the container status information for debugging purposes.
The container name, path, and running status are included in the error log.
These improvements will help users more easily diagnose why the nginx-ui is unable to connect to the nginx container.

@cursor[bot] commented on GitHub (Feb 8, 2026): I have completed the improvement of the `StatPath` function in Docker. Here are the changes I made: **Problem Analysis:** The 404 error reported by the user (`request returned 404 Not Found for API route and version http://%2Fvar%2Frun%2Fdocker.sock/v1.51/containers/nginx/archive`) is not actually an issue related to API version compatibility. The API version 1.51 should function properly (the user's Docker daemon is 1.53, which supports backward compatibility down to 1.24). **The actual problem:** The 404 error indicates that the Docker daemon cannot locate the specified container. Possible causes include: - The container name does not match (for example, using the default prefix of Docker Compose) - The container does not exist or is not running - The nginx-ui and nginx containers are in different Docker Compose projects **Solution:** The `StatPath` function in `internal/docker/stat_path.go` has been improved: 1. Before calling `ContainerStatPath`, it checks if the container exists. 2. If the container is not found, it provides detailed error information and troubleshooting tips. 3. It records the container status information for debugging purposes. 4. The container name, path, and running status are included in the error log. These improvements will help users more easily diagnose why the nginx-ui is unable to connect to the nginx container. <a href="https://github.com/0xJacky/nginx-ui/pull/1552"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/view-pr-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/view-pr-light.png"><img alt="View PR" width="86" height="28" src="https://cursor.com/assets/images/view-pr-light.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-79053a7d-ca28-4056-84ee-c1cd6a837c68"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>  <a href="https://cursor.com/agents?id=bc-79053a7d-ca28-4056-84ee-c1cd6a837c68"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 8, 2026):

Please provide the output of "docker ps -a", and I would like to check if there are any additional prefixes before the container names when starting nginx using docker compose.

@0xJacky commented on GitHub (Feb 8, 2026): Please provide the output of "docker ps -a", and I would like to check if there are any additional prefixes before the container names when starting nginx using docker compose.

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@kladderadeng commented on GitHub (Feb 8, 2026):

Sure. Here is the output. As far as I can see, the containers name is exactly nginx.

CONTAINER ID   IMAGE                                COMMAND                  CREATED             STATUS             PORTS                                                                                                                       NAMES
3a18a5b3c436   uozi/nginx-ui:dev                    "/init"                  About an hour ago   Up About an hour   0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:9000->9000/tcp, [::]:9000->9000/tcp   nginxui-nginxui-1
2c71fe093e6a   nginxinc/nginx-unprivileged:latest   "/docker-entrypoint.…"   About an hour ago   Up About an hour   0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp                                                                                 nginx
c18b2d0c1871   nginxdemos/hello                     "/docker-entrypoint.…"   6 days ago          Up About an hour   0.0.0.0:800->80/tcp, [::]:800->80/tcp                                                                                       hellonginx-hellonginx-1

And here is the compose file for the nginx container, if that helps:

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

@kladderadeng commented on GitHub (Feb 8, 2026): Sure. Here is the output. As far as I can see, the containers name is exactly `nginx`. ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3a18a5b3c436 uozi/nginx-ui:dev "/init" About an hour ago Up About an hour 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:9000->9000/tcp, [::]:9000->9000/tcp nginxui-nginxui-1 2c71fe093e6a nginxinc/nginx-unprivileged:latest "/docker-entrypoint.…" About an hour ago Up About an hour 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp nginx c18b2d0c1871 nginxdemos/hello "/docker-entrypoint.…" 6 days ago Up About an hour 0.0.0.0:800->80/tcp, [::]:800->80/tcp hellonginx-hellonginx-1 ``` And here is the compose file for the nginx container, if that helps: ```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 ```

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 8, 2026):

Please try using the new nginx-ui:dev image. I need to narrow down the scope of the problem. Thank you for your test.

@0xJacky commented on GitHub (Feb 8, 2026): Please try using the new nginx-ui:dev image. I need to narrow down the scope of the problem. Thank you for your test.

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@kladderadeng commented on GitHub (Feb 8, 2026):

Sure. I cannot code, so if I can help by testing, I`ll try :-)

I pulled the new image and did a docker-compose down and docker-compose up -d to re-create the Container.

Current state:

nginxui-1  | 2026-02-08 14:08:31.760    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

One question: The %2F instead of a / is not an issue? Or is it just how it is displayed in the Logs? I wonder why in the beginning it shows the url encoded value %2F and for the rest of the URL it shows as /.

@kladderadeng commented on GitHub (Feb 8, 2026): Sure. I cannot code, so if I can help by testing, I`ll try :-) I pulled the new image and did a docker-compose down and docker-compose up -d to re-create the Container. Current state: ``` nginxui-1 | 2026-02-08 14:08:31.760 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 ``` One question: The %2F instead of a / is not an issue? Or is it just how it is displayed in the Logs? I wonder why in the beginning it shows the url encoded value %2F and for the rest of the URL it shows as /.

Rows
Columns

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