Forge tunnel not working - Linux Mint - Node22

Hi everybody,

I’m currently having a problem with Forge tunnel. I’m working on an app which uses Custom UI and I use a local server on localhost:3000 for React frontend app which I start with “npm run dev” before starting forge tunnel.

When I deploy and install the app on my site there is no problem and the app works correctly. But when I start “forge tunnel” and reload my app in Jira, Chrome browser throws an error and the loading wheel in my app is stuck turning…

Here is the error from Chrome console :

main.tsx:42 Uncaught (in promise) Error: There was an error invoking the function - Cannot find module '/tmp/forge-dist-61130-USWW6w7cMQ75/bundled/index.js'
Require stack:
- /tmp/forge-dist-61130-USWW6w7cMQ75/__forge_wr... (truncated)
    at invoke (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/async-forge-ui-issue-view-extension.8f99cde1.js:57:112503)
    at async https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/async-forge-ui-issue-view-extension.8f99cde1.js:57:143624

Error: There was an error invoking the function - Cannot find module '/tmp/forge-dist-61130-USWW6w7cMQ75/bundled/index.js'
Require stack:
- /tmp/forge-dist-61130-USWW6w7cMQ75/__forge_wr... (truncated)
    at he.error (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:133263)
    at Object.<anonymous> (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:141036)
    at JSON.parse (<anonymous>)
    at Se.o (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:140895)
    at Se (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:141048)
    at Me.s.on (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:145708)
    at Me (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:145845)
    at https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:151831
    at e.try (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:124315)
    at https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:151628

In my terminal, where tunnel runs, I see the requests from Jira.

It seems like the app tries to reach files in /tmp folder on my disk but doesn’t find “index.js”…

Every time I start forge tunnel, it creates a new folder "/forge-dist--*******/ in my /tmp folder.

There is no errors in my terminal where tunnel runs.

If I stop tunneling, the app works correctly again.

Part of manifest.yml :

resources:
    - key : frontend-resource
    - path : static/frontend/dist
    - tunnel:
        - port:3000
...

runtime:
    - name: nodejs22.x

I created, deployed and installed an other app with UI Kit (hello-world-app from tutorials) and tunnel works ! I don’t understand…

Here is my config :

  • Linux Mint 22.1 (Ubuntu 24.04)
  • Node 22.14.0
  • Forge 11.2.0
  • No Firewall

I read all the other topics about that problem without success.
Is there anyone who had the same problem ??

I think that’s a bug in the latest Forge CLI version. I’ve downgraded to 11.1.0 with npm install -g @forge/cli@11.1.0 because of this error.

Amazing ! You made my day !

I downgraded to 11.1 and it works !! Thank you very much !

Have a nice day

1 Like

Logged a ticket but Needs Triage: Jira

1 Like

Sorry I can’t log in ecosystem:

If anyone has further information about how to reproduce this error, please provide details on FRGE-1751

This is now fixed in v11.3.0 of the Forge CLI - https://developer.atlassian.com/platform/forge/changelog/#CHANGE-2458

4 Likes