Closed kdubb closed 7 months ago
Weird... I can't say I know what to do about it :)
I just submitted a PR to bump to the latest NGROK client so maybe its a client related bug that has been fixed.
@kdubb can you try 1.3.0 please and let us know if you still get this issue?
@kdubb will close for now. Report back if its still happening and I can reopen
@all-contributors add @kdubb for bug
@melloware
I've put up a pull request to add @kdubb! :tada:
Sometimes exiting from dev mode will leave the ngrok process running.
I am not sure what the trigger is, it may be due to abnormal exits (e.g. CTRL+C) but it is intermittent. After this happens you usually get an error when the next dev mode is started; but even then sometimes it manages to get more than one ngrok started and prints no message.