Unable to reach containers, even with tsdproxy.container_port specified

[hvanbenschop]

-Im running tsdproxy 1.3.2 on network_mode host.
-I have a stack of containers that connect outward through a gluetun vpn. Each container uses network_mode: service:gluetun. the gluetun container uses network_mode: specialbridge and devices: - /dev/net/tun:/dev/net/tun
-I have applied labels to 4 container in the stack, but strangely 2 of them work but 2 fail to work.

When visiting nzbget.funny-name.ts.net the log reads:

ERR error host=nzbget.funny-name.ts.net method=GET module=proxymanager proxyname=nzbget status=502 url=/
http: proxy error: dial tcp 192.168.55.50:80: connect: connection refused

Appearantly it redirects to port 80, but nzbget is located on 192.168.55.50:2121

Adding tsdproxy.autodetect: "false" and tsdproxy.container_port: 2121 to the yaml seems to have no impact.

Possibly related to #52 ?

[almeidapaulopt]

should be fixed in c33dd1b v1.4.0
send feedback please

[hvanbenschop]

confirmed fixed in v.1.4.0

      tsdproxy.autodetect: "false"
      tsdproxy.container_port: 2121

now correctly forwarding nzbget.funny-name.ts.net to port 2121.