Persistent Issue with forge tunnel Command and Docker Image Pull Failure

Forge Forge Platform and Tools
, ,
4

Hello Atlassian Developer Community,

I wanted to provide an update on the issue I previously posted about regarding the forge tunnel command in the Forge CLI. With the assistance of Atlassian Support, particularly Nicolas Grunberg, and through further troubleshooting on my end, I’m pleased to report that the issue has been resolved.

Resolution Summary:

  • The initial problem was with the forge tunnel command, which consistently failed with errors related to Docker image pulling and an incorrect ngrok configuration file path.
  • Despite the ngrok configuration path being correctly set in Forge settings, the Forge CLI was attempting to read the configuration file from an incorrect path.
  • The issue persisted even though the forge deploy and forge lint commands worked without issues, and the Docker image for atlassian/forge-tunnel:latest could be manually pulled.

Key Steps to Resolution:

  • A crucial step that led to the resolution was the modification of the ngrok.yml configuration file. I added a region field to the existing version and authtoken configuration, resulting in the following setup:
version: "2"
authtoken: [My Ngrok Auth Token]
region: us
  • After this change, the forge tunnel command started functioning correctly again. It’s worth noting that previously, the region field was not specified, yet the tunnel worked fine.

Acknowledgment:

  • I’d like to extend my gratitude to Nicolas Grunberg and the Atlassian Developer Support team for their guidance and support during this troubleshooting process.

Insights for the Community:

  • If you’re facing similar issues with the forge tunnel command, consider verifying your ngrok configuration, especially the region field.
  • This solution might not be universal but could be a starting point for others experiencing similar difficulties.

I hope this update is helpful to anyone who might encounter a similar problem. If there are any further insights or explanations about why specifying a region in the ngrok config resolved the issue, I’d be very interested to hear them.

Thank you all for your support and assistance!

Best regards, Oday Rafeh

3 Likes