Hi,
I am trying to setup multiple servers via docker.
When the ports are exposed 55414:55414 then I can connect to the webinterface.
Since I would like multiple servers from the same Docker Host, the servers will need different port numbers exposed, eg. 90:55414 and 91:55414
Locally this partially works, in that the webinterface loads eventually after a couple of refreshes.
This does not work from an external network, i.e. router config = 55414:90, docker config = 90:55414
I have tried adding the tcp flag to the container, with no change in results. This is an intermediary test, ultimately I would like to have 55414 point to my load balancer which can then direct traffic to the service via acl, however, I am stuck with traffic failing when I use a custom port on the container externally
I don’t understand the problem and Chat GPT is not as helpful as it used to be
Guidance to get me out of my ignorance would be sincerely appreciated
Thank you
EDIT:
I have taken testing a step further by incorporating HAProxy in the same stack as URBackup. Exposing ports 55413-55415 on the HAProxy service, setting up a front end for each port, with an ACL and then also a backend for each port pointing to the URBackup service by docker service name (not by IP nor hostname)
From the stats page HAProxy shows the connection to backends as alive, however, never do I see any traffic comming in through the default ports.
to clarify, router is set to open ports 55413-55415 and point them to this stack 55413-55415.
docker exposes port 55413-55415 to HAProxy in the stack, with HAProxy binding to each port on an individually configured frontend
incomming connection does not reach URBackup
6 posts - 2 participants