Forge tunnel not working from past 1hour

Forge Forge Platform and Tools
,
1

This error is coming when i ran forge tunnel.
Iam using latest forge cli version.

Tunnel provider: Cloudflare
Press Ctrl+C to cancel.

▶️  GraphQL https://api.atlassian.com/graphql
Query:
      mutation forge_cli_setupApplicationTunnel($input: RegisterTunnelInput!) {
        registerTunnel(input: $input) {
          success
          errors {
            message
            extensions {
              errorType
              statusCode
            }
          }
          tunnelId
          tunnelToken
          tunnelUrl
        }
      }

Variables: {
  "input": {
    "appId": "ari:cloud:ecosystem::app/dad66015-bfba-4bfd-93b8-20baea4b7040",
    "environmentKey": "default"
  }
}
▶️  GraphQL https://api.atlassian.com/graphql
Query:
      mutation forge_cli_deleteApplicationTunnels($input: DeleteAppTunnelInput!) {
        deleteAppTunnels(input: $input) {
          success
          errors {
            message
            extensions {
              errorType
              statusCode
            }
          }
        }
      }

Variables: {
  "input": {
    "appId": "ari:cloud:ecosystem::app/dad66015-bfba-4bfd-93b8-20baea4b7040",
    "environmentKey": "default"
  }
}

Error: The underlying service call failed. The underlying service xen_invocation_service status code is: 502 (requestId: a93e4d64297149f7a46f526f534e3369)

Error: The underlying service call failed. The underlying service xen_invocation_service status code is: 502 (requestId: a93e4d64297149f7a46f526f534e3369)
    at MinimalGraphQLRunner.rawRequestWithoutClientError (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/graphql/minimal-graphql-runner.js:109:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MinimalGraphQLRunner.run (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/graphql/minimal-graphql-runner.js:61:47)
    at async DebuggingGraphqlRunner.run (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/graphql/debugging-graphql-runner.js:20:41)
    at async MutationAwareGraphQLClient.mutate (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/graphql/mutation-aware-graphql-client.js:38:41)
    at async TunnelGraphqlClient.setupTunnel (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/tunnel/out/graphql/tunnel-graphql-client.js:56:116)
    at async RegisterTunnelServiceImpl.setupTunnel (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/tunnel/out/services/register-tunnel-service.js:21:16)
    at async StartTunnelCommand.startFaaSTunnelServer (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/tunnel/out/command/start-tunnel-command.js:46:36)
    at async StartTunnelCommand.execute (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/node_modules/@forge/tunnel/out/command/start-tunnel-command.js:89:38)
    at async InProcessTunnelService.run (/home/jeevan/.nvm/versions/node/v20.11.1/lib/node_modules/@forge/cli/out/service/tunnel-service.js:66:28)

Any help is much appreciated.

Thanks.

1 Like
2

Hi,

This may be happening due to a network issue or a firewall blocking the ports needed for the tunnel connection.
Could you try testing it on another network to see if that makes a difference.

Hope this helps!

1 Like
3

facing same issue too, I’m using forge remote and my remote backend is not receiving requests made

4

Hi all,

I wanted to first apologise for the inconvenience caused.
There was an incident overnight that impacted Forge Invocations and Forge Tunnel for ~17% of traffic.

You can review the details on the support page: https://developer.status.atlassian.com/