Forge tunnel does not pick up on requests


The app is deployed yet when I make a change, it does not pick it up anymore.
Last time I’ve touched this project was october 2020. I also can’t seem to find the Forge Slack anymore.

Were there any changes made that could have influenced this?

1 Like

What version of the CLI are you running? You should be able to check via:

npm -v @forge/cli

I’m certain some things have changed since October 2020. Maybe try uninstalling and re-installing so that you have the most up-to-date CLI:

1 Like

Thanks for your reply!

I’ve just uninstalled and reinstalled forge CLI, it’s running 6.14.5 now yet changes still aren’t picked up unfortunately, I gotta keep searching.

Also, did they discontinue the forge Slack community?

As far as I know the forge Slack workspace was closed, yes.

Do you have dependencies on @forge in your package.json? If yes, did you make sure they are on the newest version available? Also did you try all redeploying, uninstalling, and reinstalling your forge app?


You might also want to check your firewall so that ngrok (used in the docker container) is able to make and keep an outbound connection.

I’ve had issues with the custom ui proxy but that’s due to me running on a unsupported platform (so that might be another thing to check):

Yes, we wanted to consolidate the community under this umbrella. This is the right place for questions around Forge.

1 Like

Thank you everyone for contributing. Really appreciate it.

I’ve tried uninstalling and reinstalling the application and also updating all the npm packages, yet to no avail, no events are picked up :confused:
Docker is also up-to-date and has worked in the past without me making changes since last tunnel

Can you share more on the file structure of your app and which files you’re making changes to?

Certainly! The bottomline is: when the status of an issue is changed to ‘Done’, the app checks if the issue has a ticketnumber which corresponds to a tcket in our ticketing system.
If it has a ticketnumber, it updates said ticket in our system with information from JIRA.
If it doesn’t, it creates a ticket and updates the issue in JIRA with the ticketnumber.

Currently I’m using an overkill of permissions so I’m gonna go over each of them and remove them one by one to see if this changes anything (trial and error, amiright)

As for the filestructure, it’s a basic confluence app that I’ve built on

And just to be sure, the file that you’re saving changes to and not seeing forge tunnel pickup is src/index.jsx, yeah?

Oh sorry if I worded the problem incorrectly, changes in the index file are picked up by forge tunnel but changing the status of an issue is not picked up nor logged, without me changing the code from last time it did pick up the change of status of an issue