Jira Activity Tutorial Generates "Failed to establish local tunnel" Error

[Nathan Stout]

Trying to follow the tutorial here:  https://developer.atlassian.com/cloud/jira/platform/project-activity/

When I get to the step to start the application and run "npm start" within the tutorial directory, I get the following log output:

C:\dev\jira-activity>npm start

> my-app@0.0.1 start
> node -r esm app.js

morgan deprecated default format: use combined format node_modules\esm\esm.js:1:278827
Watching atlassian-connect.json for changes
App server running at http://localhost:3000
Failed to establish local tunnel
err = Error: spawn UNKNOWN
Error: spawn UNKNOWN
Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:413:11)
at spawn (node:child_process:743:9)
at startProcess (C:\dev\jira-activity\node_modules\ngrok\process.js:39:16)
at getProcess (C:\dev\jira-activity\node_modules\ngrok\process.js:23:20)
at Object.connect (C:\dev\jira-activity\node_modules\ngrok\index.js:16:22)
at C:\dev\jira-activity\node_modules\atlassian-connect-express\lib\internal\registration\register-jira-conf.js:22:34
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:64:3)
at C:\dev\jira-activity\node_modules\esm\esm.js:1:34535
at C:\dev\jira-activity\node_modules\esm\esm.js:1:34176
at process.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:34506)
at Function.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:296856)
at Function.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:296555)
at Function.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:284879)
at Object.apply (C:\dev\jira-activity\node_modules\esm\esm.js:1:199341)
at node:internal/main/run_main_module:23:47
Unhandled error: Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:413:11)
at spawn (node:child_process:743:9)
at startProcess (C:\dev\jira-activity\node_modules\ngrok\process.js:39:16)
at getProcess (C:\dev\jira-activity\node_modules\ngrok\process.js:23:20)
at Object.connect (C:\dev\jira-activity\node_modules\ngrok\index.js:16:22)
at C:\dev\jira-activity\node_modules\atlassian-connect-express\lib\internal\registration\register-jira-conf.js:22:34
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:64:3)
at C:\dev\jira-activity\node_modules\esm\esm.js:1:34535
at C:\dev\jira-activity\node_modules\esm\esm.js:1:34176
at process.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:34506)
at Function.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:296856)
at Function.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:296555)
at Function.<anonymous> (C:\dev\jira-activity\node_modules\esm\esm.js:1:284879)
at Object.apply (C:\dev\jira-activity\node_modules\esm\esm.js:1:199341)
at node:internal/main/run_main_module:23:47

Any idea why this error is thrown?

Things I've checked:

• Tested with ngrok 2.3.40 and 3.1.0 (same error)
• The app server is running and responds via https://localhost:3000
• I'm running Node.js v18.12.1
• I'm running npm v.9.2.0
• I can MANUALLY start an ngrok tunnel successfully and access it externally
• I have verified my credentials.json settings (url, username, api key)

[Frederik Vilhelmsen]

Downgrading to Node.js v16.16.0 and running npm ci resolved this issue for me.

[Nathan Stout]

Unfortunately, this didn't solve the problem for me. Still running into the same issue.

[Robz Stha]

@Nathan Stout Any solutions so far? I am stuck on same issue but my error shows:

err = Error: spawn Unknown system error -88
Error: spawn Unknown system error -88
Error: spawn Unknown system error -88

[Theis Helth Stensgaard]

I'm getting the exact same issue, are you by any chance running it on a mac, possibly an M1/2 chip? I'm thinking that might create issues as my partner can run it without issues on their windows. I've been trying a lot of things, but nothing seems to fix it.

[Cole Nelson]

I also have the same issue but I'm on Windows so I don't think it's an apple problem