New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FetchError: request to https://example.com/check failed, reason: certificate has expired #358
Comments
So I did a little digging and came across this issue on node-fetch that might provide some insight: node-fetch/node-fetch#568 Looks like it might be an electron issue. I'm leaving this open for now and will try to do a little more digging over the weekend, but ultimately I don't think it's an issue with this extension specifically. |
Thanks! Maybe it is worth updating node-fetch? It is on 3.0 now. https://www.npmjs.com/package/node-fetch |
Oh definitely. Dependabot already opened PR #328 for updating, but I have to make some significant changes to use it since it's changed to an ESM only package. I'm working through it, but it's slow going due to other life priorities. |
The node-fetch people seem to also maintain the 2.x branch as well. Bumping to 2.6.5 might also solve the issue without larger rework? https://www.npmjs.com/package/node-fetch/v/2.6.5 |
Updated to node-fetch 2.6.6. Still leaving the issue open for awareness. |
This is still happening in version 0.19.0: |
This is probably not related to vscode-languagetool-linter, but a general problem concerning letsencrypt certificates in vscode, as discussed here. |
I run a custom instance of LanguageTool on Docker. It used to work fine. But now I get these errors from the plugin:
The SSL certificate is up-to-date. Is there something I can do to fix this?
The text was updated successfully, but these errors were encountered: