TestCloud Tunnel does not work when running a test from Katalon Studio

I am trying to run a test from Katalon Studio using TestCloud as a runner, but the test targets on-premise applications, which means I will need to set up a tunnel.
I have set up a tunnel (which is also working when you run the test from TestCloud), but it fails when you run the test from Katalon Studio

Here are my tunnel configs:

And the error in Katalon Studio:

2 Likes

Hi @lmmuchiri,

Thank you for sharing your issue.

SessionNotCreatedException: Could not start a new session. Response code 500. Message: Either tunnel is not running or disconnected.

This means Katalon Studio could not detect an active tunnel session, even though the TestCloud panel says “Tunnel is available.”

While your config is correct, I would like to suggest some steps for workaround that:

  1. Double-check that the tunnel is started before you click “Run” in Katalon Studio by using the tunnel CLI with your config file: katalon-tunnel -c path/to/your/config.file. Console should return Tunnel is active and connected to your organization

  2. KS needs to detect the active tunnel via the same API key and organization ID Please double-check

  • The org ID in the config matches your Studio’s signed-in org
  • You’re using the latest version of the Katalon Tunnel binary

More information in doc here: Local testing with TestCloud | Katalon Docs

  1. If you’re behind a proxy (as seen in your config), and your tunnel only works from the CLI but not through Studio, so try removing proxy_host and proxy_port from the tunnel config temporarily and see if it works without proxy
    If your proxy requires authentication, include:
proxy_username = 'yourUsername'
proxy_password = 'yourPassword'

Please let us know if you still face it.

Thanks for your detailed response. Indeed, this helped with the troubleshooting. I ultimately found out that the problem was that my VPN connection was blocking Katalon Studio from using the tunnel (I was testing this with a VPN connection active on my machine). Therefore switching from VPN to the internet connection resolved the issue