mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #1536] Controlling Nginx in another Docker Container from Nginx-UI running in a Container, failed API calls #3069
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#3069
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
My docker-compose.yml includes the
To Reproduce
Steps to reproduce the behavior:
Get data failed, Nginx is not runningExpected behavior
I would expect to see a connection to the Nginx Container.
Info (please complete the following information):
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.