Cannot connect my containers

[jzubizarreta]

Hi!

First, thanks for this amazing proxy solution for tailscale.

I followed the documentation and added the TSDProxy container to my docker compose file, together with my other containers. However, I cannot access any of the containers using the XXX.XXXX.ts.net url. I tried both with and without funnel enabled as well.

Here is an example for one of my containers. I can see the zigbee2mqtt machine being generated in my tailscale machine list. However, I cannot access it and tried with both http and https. I also don's see certificates generated when using https. Do I need to generate them manually with tailscale cert?

  zigbee2mqtt:
    container_name: zigbee2mqtt
    image: ghcr.io/koenkk/zigbee2mqtt
    ports:
      - 8080:8080
    volumes:
      - <HOME>/zigbee2mqtt/data:/app/data
      - /run/udev:/run/udev:ro
    labels:
      tsdproxy.enable: true
      tsdproxy.name: zigbee2mqtt
      tsdproxy.scheme: https
    restart: unless-stopped

  tsdproxy:
    container_name: tsdproxy
    image: almeidapaulopt/tsdproxy:1
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - <HOME>/tsdproxy/data:/data
      - <HOME>/tsdproxy/config:/config
    ports:
      - 8081:8080
    restart: unless-stopped

In case it's useful, I see this error in the TSDProxy container logs:

http: TLS handshake error from <IP>:55394: 500 Internal Server Error: acme.GetReg: Get "https://acme-v02.api.letsencrypt.org/directory": dial tcp: lookup acme-v02.api.letsencrypt.org on 127.0.0.11:53: server misbehaving

Thanks in advance!

[noranraskin]

As far as I know, tsdproxy will create a new tls certificate when a new service is discovered, this can take a while so maybe just try again in a few minutes. Especially since it looks like it's having a problem with the output from letsencrypt. What also helped for me is specifying the container port. To do that add another label tsdproxy.port: 8080

[jzubizarreta]

Thanks. I tried as you said with the port, using the V2 this time, and I don't even get the machine on my tailnet now :( I also don't get anything on the TSDProxy dashboard.

      tsdproxy.enable: true
      tsdproxy.name: zigbee2mqtt
      tsdproxy.port.1: "443/https:8080/http"

[noranraskin]

What do the logs of tsdproxy say? You should just append tsdproxy.port: 8080 without changing it. Don't specify two ports. tsdproxy only needs the ingoing port of the application. It will handle TLS termination by itself no need to specify 443

[jzubizarreta]

I tried what you said using only a single por and I see the machine in my tailnet now. However I get the same error as I shown in my first post. There is some kind of issue with TLS

[noranraskin]

I don't know how to debug that, sorry

[kyle-imisshtml]

I also have this problem with v2. The machine shows up in tailscale admin, and shows up in the TSDProxy web interface. After approving the new machine though I can't access it vai the tailnet url

[noranraskin]

If v2 is making problems my suggestion would be to stick to v1, since this project seems to be no longer maintained it shouldn't make a big difference