-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Need to bundle ngrok binary in the npm package, or make it optional #69
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
Comments
I don't think this is a problem with your self-signed cert or ssl, the url simple isn't available.
@dikaiosune can we bundle those tgz's in the app itself so it doesn't depend on downloading them from a 3rd party with flaky uptime? @inconshreveable anyway you can get those binaries hosted on npm? Looks like Cloudflare is down which is probably causing this issue.
|
Definitely. There are a few things that need to happen. We need to make ngrok an optional dep in one of the underlying deps (xdl), since CRNA doesn't even make use of it, and for Expo's stuff we probably also need to provide npm-based distribution of the actual binary (although I haven't looked into the licensing consequences since ngrok 2 is closed source). |
The link is working, but the postinstall.js script is not. I still get the error above. |
the fixes still do not fix the SSL certificate error that I get.
|
We don't have any plans to allow disabling TLS, but you can specify the We are planning to provide a cached version of these files by default in the near future, just needs to be implemented. |
export NODE_TLS_REJECT_UNAUTHORIZED=0 fixes the issue. |
Uh oh!
There was an error while loading. Please reload this page.
We use a corporate man in the middle to decrypt network traffic. Our installed cert is self-signed and servers throw a big fit about it. When trying to run
I get the following error:
I've also set these options these commands:
npm config set strict-ssl false
yarn config set ssl strict-ssl false
The text was updated successfully, but these errors were encountered: