I’m new to Forge and want to use it to create a plugin using UI Kit on jira-issue-panel on M4 Macbook Pro.
When I’m trying to do `forge tunnel`, it does tunnel in and reflect the frontend changes but throws `Error loading data` from the backend side. There are no console.logs visible in the CLI, and moreover, if i refresh this page, the issue stops reflecting the local changes all together.
There are times when the tunnel automatically worked and was accepting backend changes as well, but after i took a break, it again started behaving like this
These are the related logs -
```
[cloudflared]: 2025-10-01T19:39:37Z INF Starting tunnel tunnelID=afd9b5f7-40c0-455d-b6ff-4ea5fc1cabb2
2025-10-01T19:39:37Z INF Version 2025.9.1 (Checksum 0c20739ccab70c804e97b824a048e2028869c01e8c795b0033dd66b61962d491)
2025-10-01T19:39:37Z INF GOOS: darwin, GOVersion: go1.24.2, GoArch: arm64
2025-10-01T19:39:37Z INF Settings: map[p:http2 protocol:http2 token:***** url:localhost:49424]
2025-10-01T19:39:37Z INF Environmental variables map[TUNNEL_LOGLEVEL:debug]
2025-10-01T19:39:37Z INF Autoupdate frequency is set autoupdateFreq=86400000
2025-10-01T19:39:37Z INF Generated Connector ID: c9632d88-02e5-4b47-b3ba-955b7613cc31
2025-10-01T19:39:37Z DBG Fetched protocol: quic
2025-10-01T19:39:37Z INF Initial protocol http2
2025-10-01T19:39:37Z INF ICMP proxy will use 192.168.1.83 as source for IPv4
2025-10-01T19:39:37Z INF ICMP proxy will use fe80::4bc:f7b8:1896:71c1 in zone en0 as source for IPv6
2025-10-01T19:39:37Z INF Created ICMP proxy listening on 192.168.1.83:0
2025-10-01T19:39:37Z DBG failed to create ICMPv6 proxy, only ICMPv4 proxy is created error=“bind: can’t assign requested address”
2025-10-01T19:39:37Z DBG edge discovery: looking up edge SRV record domain=_v2-origintunneld._tcp.argotunnel.com event=0
GraphQL
Request ID: 5f67298c-8574-4876-91b5-1eac2b46bf9b
Result: {
“createAppTunnels”: {
“success”: true,
“errors”: null,
“keepAlive”: “1759349617395”
}
}
=== Running forge lint…
No issues found.
=== Bundling code…
Resources bundled.
Functions bundled.
Listening for requests on local port 49424…
[cloudflared]: 2025-10-01T19:40:12Z DBG edge discovery: resolved edge addresses addresses=[“2606:4700:a0::2”,“2606:4700:a0::6”,“2606:4700:a0::8”,“2606:4700:a0::3”,“2606:4700:a0::10”,“2606:4700:a0::7”,“2606:4700:a0::5”,“2606:4700:a0::1”,“2606:4700:a0::9”,“2606:4700:a0::4”,“198.41.192.27”,“198.41.192.37”,“198.41.192.107”,“198.41.192.67”,“198.41.192.227”,“198.41.192.47”,“198.41.192.167”,“198.41.192.7”,“198.41.192.77”,“198.41.192.57”] event=0
[cloudflared]: 2025-10-01T19:40:12Z DBG edge discovery: resolved edge addresses addresses=[“2606:4700:a8::6”,“2606:4700:a8::9”,“2606:4700:a8::7”,“2606:4700:a8::3”,“2606:4700:a8::2”,“2606:4700:a8::10”,“2606:4700:a8::4”,“2606:4700:a8::8”,“2606:4700:a8::5”,“2606:4700:a8::1”,“198.41.200.63”,“198.41.200.73”,“198.41.200.33”,“198.41.200.43”,“198.41.200.23”,“198.41.200.113”,“198.41.200.193”,“198.41.200.233”,“198.41.200.53”,“198.41.200.13”] event=0
[cloudflared]: 2025-10-01T19:40:12Z ERR Cannot determine default origin certificate path. No file cert.pem in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]. You need to specify the origin certificate path by specifying the origincert option in the configuration file, or set TUNNEL_ORIGIN_CERT environment variable originCertPath=
[cloudflared]: 2025-10-01T19:40:12Z INF ICMP proxy will use 192.168.1.83 as source for IPv4
2025-10-01T19:40:12Z DBG edge discovery: looking up edge SRV record domain=_v2-origintunneld._tcp.argotunnel.com event=0
[cloudflared]: 2025-10-01T19:40:12Z INF ICMP proxy will use fe80::4bc:f7b8:1896:71c1 in zone en0 as source for IPv6
[cloudflared]: 2025-10-01T19:40:12Z INF Starting metrics server on 127.0.0.1:20241/metrics
[cloudflared]: 2025-10-01T19:40:32Z DBG edge discovery: resolved edge addresses addresses=[“2606:4700:a0::2”,“2606:4700:a0::6”,“2606:4700:a0::8”,“2606:4700:a0::3”,“2606:4700:a0::10”,“2606:4700:a0::7”,“2606:4700:a0::5”,“2606:4700:a0::1”,“2606:4700:a0::9”,“2606:4700:a0::4”,“198.41.192.27”,“198.41.192.37”,“198.41.192.107”,“198.41.192.67”,“198.41.192.227”,“198.41.192.47”,“198.41.192.167”,“198.41.192.7”,“198.41.192.77”,“198.41.192.57”] event=0
[cloudflared]: 2025-10-01T19:40:32Z DBG edge discovery: resolved edge addresses addresses=[“2606:4700:a8::6”,“2606:4700:a8::9”,“2606:4700:a8::7”,“2606:4700:a8::3”,“2606:4700:a8::2”,“2606:4700:a8::10”,“2606:4700:a8::4”,“2606:4700:a8::8”,“2606:4700:a8::5”,“2606:4700:a8::1”,“198.41.200.63”,“198.41.200.73”,“198.41.200.33”,“198.41.200.43”,“198.41.200.23”,“198.41.200.113”,“198.41.200.193”,“198.41.200.233”,“198.41.200.53”,“198.41.200.13”] event=0
[cloudflared]: 2025-10-01T19:40:32Z DBG edge discovery: giving new address to connection connIndex=0 event=0 ip=198.41.200.53
[cloudflared]: 2025-10-01T19:40:32Z DBG Updating DNS local resolver: [fe80::1%en0]:53
[cloudflared]: 2025-10-01T19:40:32Z DBG Tunnel connection options connIndex=0 event=0 features=[“support_quic_eof”,“management_logs”,“allow_remote_config”,“serialized_headers”,“support_datagram_v2”] ip=198.41.200.53
2025-10-01T19:40:32Z DBG Connecting via http2 connIndex=0 event=0 ip=198.41.200.53
[cloudflared]: 2025-10-01T19:40:32Z DBG Registering tunnel connection connIndex=0 event=0 ip=198.41.200.53 protocol=http2
[cloudflared]: 2025-10-01T19:40:33Z INF Registered tunnel connection connIndex=0 connection=a59ce6bc-5845-4ab0-aeeb-e4ecec2bb2ba event=0 ip=198.41.200.53 location=del04 protocol=http2
[cloudflared]: 2025-10-01T19:40:33Z DBG edge discovery: giving new address to connection connIndex=1 event=0 ip=198.41.192.37
[cloudflared]: 2025-10-01T19:40:33Z DBG Tunnel connection options connIndex=1 event=0 features=[“allow_remote_config”,“serialized_headers”,“support_datagram_v2”,“support_quic_eof”,“management_logs”] ip=198.41.192.37
2025-10-01T19:40:33Z DBG Connecting via http2 connIndex=1 event=0 ip=198.41.192.37
[cloudflared]: 2025-10-01T19:40:33Z DBG Registering tunnel connection connIndex=1 event=0 ip=198.41.192.37 protocol=http2
[cloudflared]: 2025-10-01T19:40:33Z INF Registered tunnel connection connIndex=1 connection=77213e0a-f54d-48ac-bbad-e81bf6b3870b event=0 ip=198.41.192.37 location=del06 protocol=http2
[cloudflared]: 2025-10-01T19:40:34Z DBG edge discovery: giving new address to connection connIndex=2 event=0 ip=198.41.200.33
[cloudflared]: 2025-10-01T19:40:34Z DBG Tunnel connection options connIndex=2 event=0 features=[“allow_remote_config”,“serialized_headers”,“support_datagram_v2”,“support_quic_eof”,“management_logs”] ip=198.41.200.33
2025-10-01T19:40:34Z DBG Connecting via http2 connIndex=2 event=0 ip=198.41.200.33
[cloudflared]: 2025-10-01T19:40:34Z DBG Registering tunnel connection connIndex=2 event=0 ip=198.41.200.33 protocol=http2
[cloudflared]: 2025-10-01T19:40:34Z INF Registered tunnel connection connIndex=2 connection=2db2069b-7712-4898-83f5-60092e705316 event=0 ip=198.41.200.33 location=del05 protocol=http2
[cloudflared]: 2025-10-01T19:40:35Z DBG edge discovery: giving new address to connection connIndex=3 event=0 ip=198.41.192.227
[cloudflared]: 2025-10-01T19:40:35Z DBG Tunnel connection options connIndex=3 event=0 features=[“management_logs”,“allow_remote_config”,“serialized_headers”,“support_datagram_v2”,“support_quic_eof”] ip=198.41.192.227
2025-10-01T19:40:35Z DBG Connecting via http2 connIndex=3 event=0 ip=198.41.192.227
[cloudflared]: 2025-10-01T19:40:35Z DBG Registering tunnel connection connIndex=3 event=0 ip=198.41.192.227 protocol=http2
[cloudflared]: 2025-10-01T19:40:36Z INF Registered tunnel connection connIndex=3 connection=30d2bdfc-32e9-45ed-a971-80acc0bd672b event=0 ip=198.41.192.227 location=del06 protocol=http2
```
I’ve cross-checked the env is correct (DEV), and I’m using the UI Kit template for jira-issue-panel and haven’t changed anything in the manifest.yml (cross-checked everything seems fine). Also the app is able to run perfectly when i deploy it.
