Add new http Proxy - Docker Names/IPs not listed

[Supasong]

Hello,

i am new to Zoraxy and the whole reversy proxy thing. I tried NGINX first, but missed some features. Overall Zoraxy runs very nice and providesd everything i need in a nice GUI. So far, good work !

One thing did not work as expected:
I am running Zoraxy and my other applications as docker CT with portainer. When creating a new proxy rule, the is a button "pick from docker containers". This should list all the CTs with theier hostnames, but all CTs are only listed as "0.0.0.0:"

The Zoraxy container has "/var/run/docker.sock:/var/run/docker.sock" mounted as advised in Setup Guide (Line is C&P from Stack /DockerCopose File). That has caused a lot of trouble at the beginning, beaucse not a single proxy rule had worked. I had thought, "if there is button that provides data, then that must be working".

The workaroud is easy: exchange the "0.0.0.0" to CT name, and its running, but had taken me a few days to get this.
(Correct behavior would be CT name, because the docker managed IPs are not static and may change after reboot)

So IF there is nice button "pick from docker containers" it would be great, if its working as intended ;)

Regards,

Supa

[tobychui]

Well this is a community contributed section of Zoraxy. I will leave this here to see if anyone want to add this feature.

[eyerrock]

I'm aware of the issue with the Docker container list showing "0.0.0.0" instead of the correct internal IP addresses.
I'm currently working on a new approach that automatically fetches the right internal IP directly from the Docker socket, based on the network the container is connected to. I still need to run a few more tests to get this stable before submitting a PR.

Please note:

• Using container names as addresses only works when Zoraxy and the target container share a network that supports Docker DNS (e.g., a user-defined bridge network).
• If your container does not expose ports to the host, you can select the "Show Containers with unexposed ports" option to use container name-based address resolution.

[Supasong]

Thanks fpr reply! Just as info - on my search for an alternative to nginx, i had stumbled over this video and had come to zoraxy. at video time 6:03 you can see, that this feature already had worked.

Source
https://www.youtube.com/watch?v=5-lps8DC6_Y&t=352s

[eyerrock]

If I remember correctly, the IP "172.17.0.1" was always shown instead of "0.0.0.0". While "172.17.0.1" might seem more specific, it's not ideal because it doesn't actually represent the internal IP address of the container - it’s typically the default gateway of the Docker bridge network. This was leading to issues, especially if some proxied containers are running on different networks.