Search code examples
githubgithub-copilot

GitHub Copilot - please login to github and try again


For Intellij plugin, GitHub Copilot shows error please login to github and try again.

I have already done the following:

  • Authenticated GitHub Copilot with my GitHub user and password.
  • Allowed GitHub Copilot in GitHub account profile.
  • Restarted the IDE multiple times after the plugin installation.
  • I have license for Github Copilot.

What should I do to resolve this error?


Solution

  • Debanjan Basu suggests in the comments:

    logout, restart IDE and login again.
    You might have signed up for copilot after the session was initiated


    You have multiple discussion reporting this error.

    discussions 18132 includes:

    Behind corporate proxy. Used latest stable version with CLion 1.1.28.1744 and added -Dcopilot.agent.disabled=true to Custom VM properties.

    Also delete github-copilot.local.xml and github-copilot.xml in .config/JetBrains/CLion2022.2/options.


    This has since been answered by GitHub staff member Benjamin Muskalla (Aug. 11th, 2022):

    We’re happy to announce that the latest release of Copilot for Visual Studio Code and Copilot for IntelliJ contains preliminary support for connecting through HTTP proxy servers.

    The current version supports basic HTTP proxy setups, with and without basic authentication.

    For Jetbrains IntelliJ

    • Ensure you have Copilot for IntelliJ 1.1.29.1869 or higher installed in your IDE.
    • Setup the HTTP proxy in your Preferences.
    • Restart your editor so the proxy configuration is applied correctly to all components requiring connections via the proxy.

    IntelliJ -- Screenshot 2022-08-03 at 20 24 31

    For Visual Studio Code

    Ensure you have Copilot for VS Code 1.39.6432 or higher installed in your editor.

    • To set up your proxy, go to your VSCode Settings and ensure your HTTP proxy configuration is set up properly.
      Alternatively, Copilot uses the http_proxy and https_proxy variables from your environment.
      VScode -- Screenshot 2022-08-11 at 10 18 49

    • Restart your editor so the proxy configuration is applied correctly to all components requiring connections via the proxy.