Failed to establish local tunnel
err = Error: ngrok is not yet ready to start tunnels
Error: ngrok is not yet ready to start tunnels
Error: ngrok is not yet ready to start tunnels
at Request._callback (E:\Source\Atlassian\jira-getting-started\node_modules\ngrok\index.js:192:30)
at Request.self.callback (E:\Source\Atlassian\jira-getting-started\node_modules\request\request.js:185:22)
at Request.emit (events.js:198:13)
at Request.EventEmitter.emit (domain.js:448:20)
at Request.<anonymous> (E:\Source\Atlassian\jira-getting-started\node_modules\request\request.js:1161:10)
at Request.emit (events.js:198:13)
at Request.EventEmitter.emit (domain.js:448:20)
at IncomingMessage.<anonymous> (E:\Source\Atlassian\jira-getting-started\node_modules\request\request.js:1083:12)
at Object.onceWrapper (events.js:286:20)
at IncomingMessage.emit (events.js:203:15)
at IncomingMessage.EventEmitter.emit (domain.js:448:20)
at endReadableNT (_stream_readable.js:1129:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
I am able to fudge it by first starting ngrok; then running npm start; modding atlassian-connect.json and uploading to my dev site.
Hey, similar experience here. Seems like ngrok made a server side API change which isn’t backwards compatible. There’s a fix released as version 3.2.3, however it doesn’t seem to be back ported to 2.3 - looking at the repo it seems like that development of 2.3 has stopped. Since ACE depends on ngrok 2 will that version stay broken until either the fix is back ported, the server side API is made BC again (unlikely, as they already showed their preference for just releasing a client side fix), ACE migrates to ngrok ^3.2.3 or ACE includes some workaround.