If you cannot start up the Link Agent or have trouble running tests over mabl Link, this article offers steps to troubleshoot and isolate the issue.
To get started, choose the issue that you're experiencing:
Starting the Link Agent
If you can't start up the Link Agent, it may be due to one of the following reasons:
Invalid startup command
Make sure the Link Agent startup command uses the proper API key and a valid name:
- The API key must be a "Link Agent" API key
- The name must be between 1 and 24 characters long that consists of lowercase letters, numbers, and dashes.
Incorrect directory
If you see the message Bad command or file name, make sure you are in the link-agent/bin directory when you run the startup command.
Connection issues
Issues with connecting to mabl Link can occur if your company has specific network restrictions. The Link Agent host must be able to connect to api.mabl.com and *.link.mabl.com over port 443.
To test connectivity, run a curl command on the Link Agent host to the following endpoints: api.mabl.com and *.link.mabl.com. If you cannot connect to these endpoints, consult with your networking team to understand why this is happening:
- If your corporate firewall blocks outgoing traffic, ask your networking team to add
*.link.mabl.comandapi.mabl.comto an allowlist so that mabl Link traffic can connect to the mabl cloud. - If your corporate network blocks outgoing connections to port 443, contact your networking team about putting an exemption in place for the Link Agent.
- If your company network uses forward proxies, make sure you add the appropriate forward proxy options to the Link Agent startup command.
Unsupported Java version
If you see the error unrecognized option: --add-opens when starting up the Link Agent, you're running an unsupported Java version. Upgrade to a Java version supported by the Link Agent or use the Docker Link Agent container.
Connecting to the application under test
If your tests are configured to run over mabl Link but cannot connect or lose connection to the application under test, use this checklist to isolate the possible cause:
Ensure proper environment configuration
Confirm that the environment you're running tests against is configured to use mabl Link. The Link Agent selected for the environment must match one of the active Link Agents in your workspace.
An environment configured to use mabl Link
Check the Link Agent status
Make sure the Link Agent is currently active on the networking page: Settings > Networking.
Check the Link Agent logs
If the Link Agent isn't active or wasn't active when tests were running, find the person who maintains the Link Agent for your team and ask them for a copy of the Link Agent logs. Link Agent logs can help find the reason why the Link Agent disconnected. They are located on the machine where the Link Agent was installed in the following location: logs/agent.log.
Some reasons why a Link Agent can shut down include:
- The Link Agent host rebooted when tests were scheduled to run.
- The Link Agent host logged out due to inactivity and shut down the Link Agent process.
- The volume of test traffic on the Link Agent is too high. If this is the case, consider creating several Link Agent instances with the same name to act as a load balancer. For more information, see the section on high availability configuration in the Link Agent requirements article.
For minimal disruptions, run the Link Agent on a machine or VM that is on as much as possible. See the article on Link Agent requirements for more information.
Confirm access
When tests run over mabl Link, DNS resolution occurs on the machine hosting the Link Agent. As long as the Link Agent is running on a host that can access the application under test, your tests running in the mabl cloud can connect to the environment.
In most circumstances, if the Link Agent host can connect to the application under test using curl, mabl Link should work as well. If the curl call fails, your network isn't properly configured for the device that is hosting mabl Link.