aws
AmazonQ VSCode Extension Recent Update Doesn't Work Behind Proxy
Problem
Hello,
Amazon Q VSCode extension started to have issues with connectivity to Codewhipser endpoints using "https" scheme. Chat window enters infinite loop.
VSCode supports only "http.proxy" variable, however it doesn't get used by some of the extensions that rely on "https" connection scheme.
The issues wasn't experienced in previous versions of the extension.
Steps to reproduce the issue
Use case: Extension Amazon Q tries to connect to remote HTTPS endpoint such as "codewhisper".
Not working:
- VSCode has "override" proxy support setting
- VSCode has "http.proxy" variable defined
- System doesn't have "http.proxy" or "https.proxy" environment variables
- Outcome: Extension cannot connect to remote host using "https" scheme.
Error: "Error fetching profiles from us-east-1: UnknownEndpoint: Inaccessible host: codewhisperer.us-east-1.amazonaws.com' at port 443'. This service may not be available in the `us-east-1' region.
2025-05-07 13:33:14.121 [info] [2025-05-07T17:33:14.118Z] Amazon Q Token Service Manager: Error updating profiles: Error: Failed to retrieve profiles from all queried regions".
Working:
- VSCode has "override" proxy support setting
- VSCode has "http.proxy" variable defined
- System does define "http.proxy" or "https.proxy" environment variables. VSCode is started from terminal having these properties as part of environment.
- Outcome: Extension successfully connects to remote host using "https" scheme and chat functions properly.
Expected behavior
Amazon Q extension must respect the "http.proxy" variable defined by VSCode IDE even though no other proxy environment variables exist.
System details (run AWS: About and/or Amazon Q: About)
- OS: MacOS
- Visual Studio Code version: 1.99.3
- AWS Toolkit version: N/A
- Amazon Q version: 1.65.0
related:
- https://github.com/aws/aws-toolkit-vscode/issues/7247
- https://github.com/aws/aws-toolkit-vscode/issues/185
I'm on Windows - It worked for me after rollback to version 1.62.0 Any version after that throws below issues
2025-05-12 09:32:46.685 [info] [Error - 9:32:46 AM] [2025-05-12T14:32:46.684Z] Error fetching profiles from us-east-1: NetworkingError: unable to get local issuer certificate 2025-05-12 09:32:46.686 [info] [2025-05-12T14:32:46.684Z] Amazon Q Token Service Manager: Error updating profiles: Error: Failed to retrieve profiles from all queried regions
Other interesting find is: With latest 1.66.0 version, only /dev code generation is working.
Same issue with version 1.68.0
2025-05-19 16:00:21.251 [info] [Error - 4:00:21 PM] [2025-05-19T21:00:21.250Z] {
"code": "QModelResponse",
"name": "Error",
"message": "unable to get local issuer certificate",
"cause": {
"code": "UNABLE_TO_GET_ISSUER_CERT_LOCALLY",
"$metadata": {
"attempts": 1,
"totalRetryDelay": 0
}
}
}
2025-05-19 16:00:21.252 [info] [Info - 4:00:21 PM] Error occurred during chat request: Error: unable to get local issuer certificate
2025-05-19 16:00:21.252 [info] [Info - 4:00:21 PM] Last result from langauge server: {
"type": "answer",
"body": "",
"messageId": "error-message-id-acf28d0d-bee1-48b0-b237-8d073f02247b",
"buttons": []
}
Upgrading to 1.72.0 resolved it. Looks like certain versions of VSCode extension are experiencing this issue.
Try downgrading the Amazon Q extension in VS Code, or updating to the latest version if available. May need to experiment with different versions until you find on that works.
Extension may be silently upgraded in the background, disable the Auto Update option in VS Code Extension for Amazon Q.
Hi everyone,
Thank you for a prompt and dedicated support. I verified the behavior on the latest v1.78.0 of the Q extension and it behaves as expected.
Vitaly