You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
Hi,
I'm getting this error in the latest VS Code and Grammarly Pre-Release extension:
[Error - 3:07:54 PM] Server initialization failed. Message: Request initialize failed with message: request to https://js.grammarly.com/[email protected] failed, reason: getaddrinfo ENOTFOUND js.grammarly.com Code: -32603
My first thought was an issue with the configured corporate proxy in VS Code, but VS Code functionality (check for new VS Code version, extension download, etc.) works fine, also other extensions communicating to the outside world work fine.
Also, I can open that URL from the error message in my browser configured with the same proxy just fine:
Could you please take a look? Thanks.
Richard
The text was updated successfully, but these errors were encountered:
rbukovansky
changed the title
Extension unable to start due getaddrinfo ENOTFOUND js.grammarly.com
Extension unable to start due getaddrinfo ENOTFOUND js.grammarly.com error
Sep 5, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I'm getting this error in the latest VS Code and Grammarly Pre-Release extension:
[Error - 3:07:54 PM] Server initialization failed. Message: Request initialize failed with message: request to https://js.grammarly.com/[email protected] failed, reason: getaddrinfo ENOTFOUND js.grammarly.com Code: -32603
My first thought was an issue with the configured corporate proxy in VS Code, but VS Code functionality (check for new VS Code version, extension download, etc.) works fine, also other extensions communicating to the outside world work fine.
Also, I can open that URL from the error message in my browser configured with the same proxy just fine:
Could you please take a look? Thanks.
Richard
The text was updated successfully, but these errors were encountered: