Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-5421

Activation Failed: GitHub Copilot could not connect to server

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = GitHub Copilot could not connect to server

      Before this update, the GitHub Device Authentication was not available in the command palette. This resulted in the following GitHub Copilot error: "Copilot could not connect to server. Extension activation failed: "Request failed with status code 401". With this update, the issue is fixed.
      Show
      = GitHub Copilot could not connect to server Before this update, the GitHub Device Authentication was not available in the command palette. This resulted in the following GitHub Copilot error: "Copilot could not connect to server. Extension activation failed: "Request failed with status code 401". With this update, the issue is fixed.
    • Bug Fix
    • Done

      Description of problem:

      With DS 3.10 we can use GitHub Copilot extension. For that we need to follow below steps:

       

      1. Authenticate to GitHub using the new "Device Authentication" command.
      2. Install the GitHub Copilot extension by uploading the VSIX file. You must repeat the upload for every new workspace.    

      But, in the Proxy environment, the `GitHub: Device Authentication` command is missing from command palette. And if we go further without that it throws below error.

       

       

      GitHub Copilot could not connect to server. Extension activation failed: "Request failed with status code 401" 

       

      Prerequisites (if any, like setup, operators/versions): DS 3.10

       

            ivinokur-1 Igor Vinokur
            rhn-support-sburhade Satyam Burhade
            Maksym Musienko Maksym Musienko
            Jana Vrbkova Jana Vrbkova
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: