-
-
Notifications
You must be signed in to change notification settings - Fork 49
Description
EDIT: it works if I expose the port to the host (e.g. use "Publish port on the host for external access"). I understand this allows Tailscale to access the host directly, but I thought the "proxy" part of "tsdproxy" meant it didn't need to (i.e. everything goes through tsdproxy!). Should I set up caddy/traefik instead?
I'm using truenas scale and configured a number of apps from their store. They are all configured with:
- network mode of "Expose port for inter-container communication".
- label of tsdproxy.enable = true mapped to the actual service
- label of tsdproxy.port = "<whatever is configured in the TrueNAS UI>"
I ran tsdproxy (v1) manually as root via the provided docker-compose and haven't changed the generated tsdproxy.yaml.
Visiting the tsdproxy dashboard shows the correct names of the dockers and I can authorised them.
However, when I try and connect it isn't managing to forward on to them and times out, showing a 502 in the tsdproxy logs.
I've tried adding the "tsdproxy.container_port=<the actual port running in the downstream docker container>" but no luck.
For example:

and

My thinking is that if tsdproxy can query the labels then it should be able to access the correct port without the app container (e.g. gitea) having to export the port to the host?
Help :-).
(similar: #244)