DNS issue trying to resolve hostname "Yes"

[ArvindSami]

Describe the Bug

Hi All,

My install has suddenly stopped working.

I am using Docker Compose to manage the containers.

Checking the logs:

INFO: 2025/11/09 09:40:04 Connecting to endpoint: yes

ERROR: 2025/11/09 09:40:04 Failed to resolve endpoint: DNS lookup failed: lookup yes on 127.0.0.11:53: no such host

Which in some ways makes sense. I don't think it should be connecting to "Yes"

services: newt: image: fosrl/newt:1.6.0 container_name: newt restart: unless-stopped environment: - PANGOLIN_ENDPOINT=https://pangolin.fossorial.io - NEWT_ID=xxxxxxxxxxxx - NEWT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I've exec'd into the container and can ping Google, etc, from within, so I know it's not the DNS itself; rather, it seems to be pointing to this random hostname?

I've updated the machine, docker, etc restarted docker, restarted the machine

Added in the DNS to the docker daemon /etc/docker/daemon.json 8.8.8.8

I've tried installing on a separate machine, but I'm getting the same issue

Environment

• OS Type & Version: (e.g., Ubuntu 22.04): Ubuntu Sever 24.04
• Pangolin Version: Pangolin Cloud
• Gerbil Version: ?
• Traefik Version: ?
• Newt Version: 1.6.0

To Reproduce

Expected Behavior

Should connect

[oschwartz10612]

It seems like the endpoint for your pangolin server is somehow set to "yes". What do you see under base_endpoint in the config.yml file on the server? Is this "yes"? If it is try changing it and restarting.