Hello, I’m trying to figure out why forge tunnel
fails on a brand new UI Kit 2 app using the new native node.js runtime.
I created a new plugin using the following steps:
forge create
… selectingUI kit 2 (Preview)
andjira-issue-panel
- Add
runtime:\n\tname: nodejs18.x
tomanifest.yml
underapp
. forge deploy
forge install
- Verify that the Issue Panel renders in my Jira test site.
forge tunnel --verbose
- appears to spawn correctly, but my app no longer renders and just shows the loading card animation perpetually:
The output of forge tunnel --verbose
shows that it is receiving heartbeats, but somehow the app itself is not loading in the Jira UI and I never see Invocation ...
log messages:
✔ Resources bundled.
Listening for requests on local port 45717...
t=2023-11-29T02:15:03+0000 lvl=dbug msg="heartbeat received" obj=tunnels.session obj=csess id=b28c73d48eee clientid=c97a8757de46e10070eeb7ac0cf3080c latency_ms=85
t=2023-11-29T02:15:13+0000 lvl=dbug msg="heartbeat received" obj=tunnels.session obj=csess id=b28c73d48eee clientid=c97a8757de46e10070eeb7ac0cf3080c latency_ms=84
What am I doing wrong or missing here? Thanks!