Failed to Request New Token #30

New Issue

2025-11-19T07:12:24-06:00

GiteaMirror commented

2025-11-19 07:12:24 -06:00

Originally created by @rhpeZ on GitHub (May 30, 2025).

Issue with Newt that has randomly appeared after working for a few days, have recreated site and nothing seems to work. Site is showing offline and in Newt logs I get the below error.

"ERROR: 2025/05/30 19:28:46 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.domain.tld/api/v1/auth/newt/get-token": dial tcp: lookup pangolin.domain.tld on 127.0.0.11:53: server misbehaving. Retrying in 10s..."

Unsure what is causing it and cannot find anything on the issues on here or on google about it.

Originally created by @rhpeZ on GitHub (May 30, 2025). Issue with Newt that has randomly appeared after working for a few days, have recreated site and nothing seems to work. Site is showing offline and in Newt logs I get the below error. "ERROR: 2025/05/30 19:28:46 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.domain.tld/api/v1/auth/newt/get-token": dial tcp: lookup pangolin.domain.tld on 127.0.0.11:53: server misbehaving. Retrying in 10s..." Unsure what is causing it and cannot find anything on the issues on here or on google about it.

GiteaMirror closed this issue

2025-11-19 07:12:24 -06:00

GiteaMirror commented

2025-11-19 07:12:25 -06:00

@oschwartz10612 commented on GitHub (May 31, 2025):

This very likely is a DNS issue on your local computer. The log is saying dial tcp: lookup pangolin.domain.tld on 127.0.0.11:53: server misbehaving - basically that it tried to look up the dns name pangolin.domain.tld on localhost but it did not work.

You should test your local DNS and make sure it is working. For example you can use dig on linux with dig @127.0.0.11 pangolin.domain.tld and see if it returns a valid response. If not your DNS does not work.

@oschwartz10612 commented on GitHub (May 31, 2025): This very likely is a DNS issue on your local computer. The log is saying `dial tcp: lookup pangolin.domain.tld on 127.0.0.11:53: server misbehaving` - basically that it tried to look up the dns name `pangolin.domain.tld` on localhost but it did not work. You should test your local DNS and make sure it is working. For example you can use dig on linux with `dig @127.0.0.11 pangolin.domain.tld` and see if it returns a valid response. If not your DNS does not work.

GiteaMirror commented

2025-11-19 07:12:25 -06:00

@rhpeZ commented on GitHub (May 31, 2025):

Hi, did the dig command and it does resolve a valid answer with the correct IP of my VPS. Below is an image of the command results

@rhpeZ commented on GitHub (May 31, 2025): Hi, did the dig command and it does resolve a valid answer with the correct IP of my VPS. Below is an image of the command results ![Image](https://github.com/user-attachments/assets/cea08b20-0ae6-49b6-8893-7c83390fbd93)

GiteaMirror commented

2025-11-19 07:12:26 -06:00

@oschwartz10612 commented on GitHub (Jun 2, 2025):

Hum good to know. Are you running newt in docker?

@oschwartz10612 commented on GitHub (Jun 2, 2025): Hum good to know. Are you running newt in docker?

GiteaMirror commented

2025-11-19 07:12:26 -06:00

@rhpeZ commented on GitHub (Jun 2, 2025):

Hi, managed to fix it. Was a DNS issue, my resolv.conf file on my ubuntu VM had corrupted and was missing. Has happened before on a different VM, so just generated it and now the site is showing online and Newt logs look healthy.

@rhpeZ commented on GitHub (Jun 2, 2025): Hi, managed to fix it. Was a DNS issue, my resolv.conf file on my ubuntu VM had corrupted and was missing. Has happened before on a different VM, so just generated it and now the site is showing online and Newt logs look healthy.