Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

getaddrinfo ENOTFOUND api.telegram.org

See original GitHub issue

Unhandled rejection Error: getaddrinfo ENOTFOUND api.telegram.org api.telegram.org:443
    at errnoException (dns.js:26:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)

This error every day. I think it’s because long plain. Maybe add live reload when exception?

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:10 (2 by maintainers)

Top GitHub Comments

4reactions

danger89commented, Mar 25, 2022

It’s actually still not solved after 6 years

0reactions

danger89commented, Jul 14, 2022

I also get sometimes getaddrinfo EAI_AGAIN api.telegram.org, often after a system reboot. And yes my DNS resolver is correctly configured.

My guess is that Docker is actually starting-up faster the Docker container than my system network / DNS resolver is ready to handle the requests. Something like that.

My bet is that my systemd is missing requires network dependency (see: Requires:) in the Docker service file:

[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target docker.socket firewalld.service containerd.service
Wants=network-online.target
Requires=docker.socket containerd.service

Although I see that containerd.service requires network.target as dependency. Maybe this isn’t enough or on the wrong level or it should use network-online.target instead of network.target? Or After=network-online.target Wants=network-online.target or maybe better: After=nss-lookup.target should be added.

Restarting the specific docker container manually always fixes the issue.