Healthcheck issue when using TUNNEL_DNS_ADDRESS parameter

[GJvdS]

When using the TUNNEL_DNS_ADDRESS parameter other than "0.0.0.0" the Healthcheck will report Unhealthy

For example: TUNNEL_DNS_ADDRESS=192.168.1.38

The Healthcheck command used is "dig +short @127.0.0.1 -p $TUNNEL_DNS_PORT cloudflare.com A || exit 1"

Changing it to "dig +short @$TUNNEL_DNS_ADDRESS -p $TUNNEL_DNS_PORT cloudflare.com A || exit 1" will solve this.

[ItsJamesMurray]

Ahh is that why I keep seeing it be "Unhealthy" in Portainer? I have a weird issue with my raspberry pi stalls out ~ once per month. The only service I have running that is not healthy is this one.

[GJvdS]

Ahh is that why I keep seeing it be "Unhealthy" in Portainer? I have a weird issue with my raspberry pi stalls out ~ once per month. The only service I have running that is not healthy is this one.

You have basically two options:

• Don't use TUNNEL_DNS_ADDRESS
• Run the container with --no-healthcheck or add

healthcheck: disable: true

to your compose file