# Forge App Access Issue After Closing Tunnel **URL:** \ **Category:** Forge\ **Tags:** jira-cloud, forge\ **Created:** [June 28, 2026, 6:01am UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508 "2026-06-28T06:01:34Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ankitjangid](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ankitjangid/32/55191_2.png) [@ankitjangid](https://community.developer.atlassian.com/u/ankitjangid)\ **Post date:** [June 28, 2026, 6:01am UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508/1 "2026-06-28T06:01:34Z")
Hi everyone, I’m running into a frustrating issue with my Forge app. Whenever I close the tunnel and then try to visit my app, I get the error: **“localhost refused to connect.”** The problem is that it takes a long time before I can get things working again, so I end up waiting too long just to test my deployed version. Has anyone else faced this behavior? Is there a reliable fix or workaround to avoid the long wait time after closing the tunnel? Any guidance or shared experiences would be really appreciated. Thanks in advance! ---
**Author:** ![BoZhang](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/bozhang/32/51055_2.png) [@BoZhang](https://community.developer.atlassian.com/u/BoZhang)\ **Post date:** [June 29, 2026, 12:48am UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508/2 "2026-06-29T00:48:25Z")
Hi @ankitjangid, thanks for reporting the issue. Could you please provide a bit more information to help me diagnose the issue? - What modules are you noticing the delay in? - If the modules are UI modules, are you using UI kit or Custom UI? - Can you please define “long time”? Are you experiencing delays of seconds/minutes? Thanks, Bo ---
**Author:** ![rcsr](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/rcsr/32/50184_2.png) [@rcsr](https://community.developer.atlassian.com/u/rcsr)\ **Post date:** [June 29, 2026, 1:19am UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508/3 "2026-06-29T01:19:22Z")
I think this is not uncommon. I haven’t experienced it recently but I’ve also come across this issue in the past. Other developers have also posted about this issue e.g. [Forge tunnel / forge deploy cache issues](https://community.developer.atlassian.com/t/forge-tunnel-forge-deploy-cache-issues/93553) ---
**Author:** ![ankitjangid](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ankitjangid/32/55191_2.png) [@ankitjangid](https://community.developer.atlassian.com/u/ankitjangid)\ **Post date:** [June 29, 2026, 5:53am UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508/4 "2026-06-29T05:53:17Z")
@ I’m facing this issue across multiple modules in my Forge app, including the **Issue panel** , **Admin page** , and **Project Settings page**. My app uses **Custom UI** , and whenever the problem occurs, the delay is roughly **5 minutes** (I don’t recall the exact duration, but it’s consistently long). I’ve already tried the following troubleshooting steps: - Emptying the cache - Performing a hard refresh - Disabling cache in the browser’s Network tab Unfortunately, none of these actions resolved the issue. ---
**Author:** ![scott.dudley](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/scott.dudley/32/53884_2.png) [@scott.dudley](https://community.developer.atlassian.com/u/scott.dudley)\ **Post date:** [June 30, 2026, 1:04am UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508/5 "2026-06-30T01:04:11Z")
If you’re running the Forge tunnel as part of a script that runs other processes (such as with “concurrently” in npm), and you then ^C the main process, the SIGTERM may not be propagated as expected to the Forge tunnel process (leaving the tunnel partially open). If this applies to you, you can try running `forge tunnel` once again directly from the command line (not as part of a script). After starting it, you can ^C that process directly to ensure that the tunnel is closed. ---
**Author:** ![ankitjangid](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ankitjangid/32/55191_2.png) [@ankitjangid](https://community.developer.atlassian.com/u/ankitjangid)\ **Post date:** [July 6, 2026, 5:34pm UTC](https://community.developer.atlassian.com/t/forge-app-access-issue-after-closing-tunnel/101508/6 "2026-07-06T17:34:24Z")
I’m not running the Forge tunnel as part of a script. I always start it directly from the terminal, and I use ^C there to stop it — so the issue I’m seeing isn’t related to SIGTERM not propagating through another process.