Host port label

[moenster]

I have been using tsdproxy with Nextcloud AIO. Because of the way NC AIO works, I only have control of the AIO master container, which is being used for controlling a fleet of NC containers. The master container is not serving actual content. So in order to deploy tsdproxy I was using the label tsdproxy.container_port=11000 to redirect to the apache container serving the actual NC content. Ignoring the AIO master container which has a port mapping to 8080.
Since the update, 27/11-24 4:54 PM, the label is being ignored by IP auto detect and the port mapping of the AIO container (I assume) and so the proxy is deployed to serve the content of the AIO master server on port 8080.
Is this a bug or by design?

[almeidapaulopt]

It's a bug. If container_proxy is defined it should be used first.

But btw, do you have tsdproxy working with aio?
Besides the bug, that I'll correct very soon, is it working now?

[moenster]

Yes, when I use the older version currently tagged next (26/11-24 11:57 PM) and use the label tsdproxy.container_port=11000 to redirect the proxy to the apache server, and not the AIO server. I use the labels:

• tsdproxy.enable=true
• tsdproxy.name=nextcloud
• tsdproxy.container_port=11000
• tsdproxy.authkey= (to set additional label)

In the NC config I use the variables:

APACHE_PORT: 11000
APACHE_IP_BINDING: 0.0.0.0
SKIP_DOMAIN_VALIDATION: true

And then I use the full TS name when registering the domain. nextcloud.FUNNYNAME.ts.net

[almeidapaulopt]

please try with v1.0.0-rc2 a send the logs.

[moenster]

The issue is still there. :next works and the label redirects to host:port. :latest uses the IP and port of the deployed container and ignores host/port. Which logs specifically? Just stdout or? Sorry for being a noob :)

[moenster]

Here are the stdout logs. Search for 11000 and you can see the difference between next and latest.
logs.zip