GitHub Copilot could not connect to server. "getaddrinfo ENOTFOUND api.github.com"

[nghiacanhtran]

Hi all
I get big issue with github copilot.I get an message "GitHub Copilot could not connect to server. Extension activation failed: "getaddrinfo ENOTFOUND api.github.com" when install new extension github copilot for vs code

[davecheney]

Hello, I'm sorry you are having difficulties. We've found that the copilot icon may not show up if copilot is not able to contact our servers. Are you behind a firewall, vpn, or other technology that may be intercepting your network connections?

[AlexanderLanin]

I have the same issue. My setup is:
Local: Windows 10, VPN, local proxy (px) which redirects to corporate proxy. Local proxy configured everywhere (VS Code, http(s)_proxy).
Remote: Ubuntu, local proxy (px) which redirects to corporate proxy. Local proxy configured (http(s)_proxy).

Everything but copilot works fine. Copilot reports:

GitHub Copilot could not connect to server. Extension activation failed: "getaddrinfo ENOTFOUND api.github.com"

[Dhamo2005]

I have tried this following steps. It works for me.

• Make sure you've connected to internet
• Reopen Or Restart your vs code window
• If these steps are not working then reinstall Copilot extension

[Gtstride]

What happened in my case, I needed to open the Github Copilot extension on VScode and I could notice it required me to upgrade to the latest version. After which my VScode reloaded and it worked just fine.
Hope this helps someone.

[TarunavBA]

So, does anyone has a workaround for this until @github solves this issue?

[ecyrbe]

I have the exact same issue when behind a corporate proxy "getaddrinfo ENOTFOUND api.github.com" :

• vs code 1.62
• windows 10

The error is really odd, since dns resolution works fine on the host.

[N4SIRODDIN3]

I could resolve this issue by resetting the Network Adapter and the DNS using Command Prompt.
Here you find the detailed steps for this issue:

1. Run as Administrator Command Prompt

2. Type the following commands, pressing enter after finishing each one:

• netsh winsock reset

• ipconfig /release

• netsh int ip reset

• ipconfig /flushdns

• ipconfig /renew

3. Exit Command Prompt

4. Restart your PC.

[sagoez]

This worked for me

[lennartdeknikker]

I have the same issue, both on my home network as well as on the vpn. Might be happening since I upgraded macOS to Monterey last week. VS code version 1.62.3 (Universal)

[ERROR] [default] [2021-11-24T07:18:19.110Z] GitHub Copilot could not connect to server. Extension activation failed: "getaddrinfo ENOTFOUND api.github.com"

[xiezhifeng]

I have same problem, same version of vscode and macOs

[lennartdeknikker]

Reinstalling the extension fixed it for me though!

[BobbySingle]

Try disable and enable again

[davecheney]

Quick suggestion, disabling and reenabling usually involves a restart of vscode. It is likely the restart is resolving the temporary networking issue; not uninstalling/reinstalling the extension.

[nghiacanhtran]

It doesn't work for me

[BruneXX]

it worked for me, uninstall, reload then install again..

[miozus]

It doesn't work for me and I cry for a while 😭

[jdbruxelles]

I get the same issue when I lose the internet connexion. I have to restart the workspace/editor to make Copilot work again.

[riandroraul]

means most of the problem is internet connection

[ctsstc]

I went to try reinstalling the extension and noticed it had a pending update, after the update it started working again.

[lveillard]

It happens to me each time after I've used VScode offline.
When coming back to online i have to uninstall copilot and restart VSC
Btw i'm saving a lot of time with Copilot, well done guys!

[sNok3]

I had the same issue. I tried to reproduce it and it only happens when an internet connection is absent. In my case restarting VSCode fixed the issue.

[shaantanu9]

It happens when you start the VS Code and if there is some issue with the internet in the beginning so for that if you think your net is working fine not just restart the VS Code.
A simple Answer to solve the issue is
Restart VS code