Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,216
Community Members
 
Community Events
176
Community Groups

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

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)

1 answer

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

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events