-
Notifications
You must be signed in to change notification settings - Fork 228
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
Not caught Error: Client network socket disconnected before secure TLS connection was established #277
Comments
Probably an error with node-fetch as seen on this tangentially related issue: node-fetch/node-fetch#892 |
Actually I get it with node:https too, also not being caught by |
passing const agent = new HttpsProxyAgent( process.env.PROXY_STRING, { rejectUnauthorized: false }); stops this error specifically, but the issue is still that it doesn't throw the error. |
Having the same issue here! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's normal that some proxied requests fail, so I have simple error handling, the issue is that the error is not being caught and instead crashing the script,
Crashes with this error:
It doesn't get caught in the catch statement.
The text was updated successfully, but these errors were encountered: