Forge tunnel stuck before calling lint

Forge
1

I’m trying to use forge tunnel to improve the development experience in designing the UI for my new app.

I’m using the UI Kit and followed the tunneling page, but after calling forge tunnel all I see is

Tunnel redirects requests you make to your local machine. This occurs for any Atlassian site where your app is installed in the specific development environment. You will not see requests from other users.
Press Ctrl+C to cancel.

Adding the --verrbose option doesn’t produce any additional output.
I also disabled the Rosetta option in Docker as listed here but still cannot get tunneling to work. also following this post doesn’t help.

I’m running on a 2012 M1 Max Macbook.

What am I doing wrong?

2

What is the Forge runtime of your app is using?

It is the value of runtime in your forge manifest file

app:
  runtime:
3

Hi @KhanhNguyen

I have nodejs18.x as runtime, was generated this way by executing the forge create command.

4

Hi there @markrekveld, are you able to provide us with the version of the Forge CLI that you are using (command: forge --version) and can you please also run forge tunnel --verbose, this will give us some extra logs and hopefully, some clues.

5

Hi @BoZhang

I’m using forge cli 10.0.1.
running forge tunnel --verbose gives the same output.

6

Hi @markrekveld, apologies, I didn’t read your initial post thoroughly enough.

If you don’t get any extra logs with the --verbose command, then the only things happening before additional logs are emitted are some file IO to read the app manifest (which I assume should be fine because you were able to create and deploy your app) and the spawning of a Node server process, which will serve tunnelled requests. The step after this would be to start the Ngrok tunnel, but this step generates logs.

Things that we can try:

  • Can you see if running the tunnel creates any listening Node processes (using lsof -i -P -n | grep node ).
  • You could use something like ktrace to trace system calls and what makes it hang.

I’ll ask my team for more advice tomorrow when they come online.

1 Like
7

No worries @BoZhang your tip to look at the processes triggered my memory that I need to add ngrok to the virusscanner exclusion list. And its not a smart list by any means so if ngrok is “installed” twice then it will silently block the second ngrok executable.

Adding the ngrok executable in the node_modules dir of the cli to the scanner exclude list got it working.

3 Likes