Phil Nash

@dkundel Ah, @craigsdennis told me that the quick start itself was getting a design makeover so was going to wait that out.

Are you working with the [python wrapper for ngrok](https://pypi.org/project/pyngrok/)? Because this is the repo for the Node.js wrapper. You can find the [docs for pyngrok here](https://pyngrok.readthedocs.io/en/latest/index.html).

I'm going to close this issue as it seems that it is an issue with [pyngrok](https://pypi.org/project/pyngrok/).

Hi @jamesaduncan, this module [waits 200ms between each attempt to connect](https://github.com/bubenshchykov/ngrok/blob/833e1d9ada4fdb17cd3ca9ed47ee3030f021ab05/index.js#L35) and tries up to 100 times. Is there some underlying problem, like an error being thrown that isn't expected....

It seems that one of the tests is failing too.

Do you reckon you can write a test for when the error handling was failing before, the error from #229? I am not sure what that that situation is, so...

If someone can provide a way to reproduce the error, I'd be happy to look into what is going on here too. I've just not seen this yet myself.

Thanks for that @zaccolley. I will try to reproduce that myself. I can suggest a workaround though, rather than have ngrok restart when nodemon restarts you can set up your...

My guess right now, until I get some time for this, is that there's something going wrong with closing the process such that when it is started quickly again it...

My theory is that we need to listen for signals that get sent and kill the ngrok child process there and not during the "exit" event. The Node docs say...