-
Notifications
You must be signed in to change notification settings - Fork 318
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
ngrok.disconnect not closing http tunnel (only https) #54
Comments
hey @nojiek, great catch! :) as a possible workaround, you can close all tunnels with ngrok.kill() - it shots down the whole ngrok process.. and you can ngrok.connect after it again |
Hello @bubenshchykov - I work with @nojiek and we have a workaround. We just wanted to let you know about the problem. Thanks! |
@bubenshchykov Thanks! Our work around is to just to not use "both" for now. |
fixed and covered by test ngrok/test/ngrok.guest.spec.js Line 76 in 125c540
if you create default bind_tls=true tunnel (two tunnels) and get let's say https://123.ngrok.io - then you can
PS what we can also do is to make bind_tls=false by default.. because it's a bit confusing and requires some reading of ngrok docs :) or we can kill both tunnels even if you just ask to kill one so i'll leave it as it is for now, and see how it goes :) |
When two tunnels are opened simultaneously (
bind_tls: both
(this is default)), ngrok fails to close both tunnels when using the disconnect command.Steps to Reproduce:
Results in:
Error Message: null
Ngrok URL: https://030927d2.ngrok.io
Port: 3599
This opens TWO tunnels: one at http and one at https
Results:
URL: https://030927d2.ngrok.io has been killed.
{ [Error: socket hang up] code: 'ECONNRESET' }
Note that the http tunnel remains open.
The text was updated successfully, but these errors were encountered: