Setting up your network for mabl

Network requirements for using mabl

Some organizations may need to take additional steps to make mabl compatible with their network. This guide outlines the permissions required for using mabl and how to exclude mabl test traffic from site analytics.

Using the mabl Desktop App and mabl Trainer

Depending on your network settings, you may need to take additional steps to use the mabl Desktop App and mabl Trainer.

Adding domains to a firewall allowlist

If your company deploys a firewall to block outgoing requests, you may not be able to access all of the settings and functionality in the mabl Desktop App. In this case, ask the person or team who manages your company's firewall settings to add the following domains to your firewall allowlist:


Configuring proxy settings

If your company uses a proxy, mabl may not work with your proxy without some additional configuration. You can check by going to Help > Troubleshooting > Check connection to mabl services in the Desktop App.

Modal showing successful connection to mabl

Checking your connection to mabl services

If the connection check failed, reach out to the person or team who manages your company's proxy security and review options for configuring proxy settings in the mabl Desktop App. If you plan to use the mabl CLI, you can find instructions on configuring mabl CLI proxy settings here.


Organizations with strict security policies may need to add the mabl application to an allow list within their antivirus or anti malware.

Checking Chrome policies

The mabl Trainer uses the version of Chrome installed on your local machine to train tests. If you can launch the mabl Trainer but cannot record or play steps in the mabl Trainer, check your Chrome policies by visiting chrome://policy in a Chrome window.

If your Chrome policy includes the DeveloperToolsAvailability policy set to 0, the mabl Trainer cannot record or play back steps. Reach out to your networking team about updating the value of DeveloperToolsAvailability to 1. Learn more about this Chrome policy here.

Running tests

Mabl provides the ability to run your tests locally and on the cloud. Cloud runs provide mabl's full range of test artifacts, comprehensive results, and auto-healing capabilities. If mabl cannot access your applications from the open Internet, you can set up mabl Link or add static IP addresses to an allowlist.

Mabl Link

Mabl Link establishes a secure tunnel between the mabl cloud and your private environment. If you set up mabl Link to access private environments, mabl Link should have an "always on" configuration so that it runs continuously in the background.

To learn more, check out our documentation on mabl Link

Static IPs

If your environment does not use mabl Link, all mabl test traffic originates from a set of dedicated egress IPs. You can view the list of static IPs on the Networking page: go to Settings > Networking and check the section called Static Mabl Traffic IPs.

As an alternative to mabl Link, you may add mabl's static IP addresses to a firewall allowlist to grant access to private testing environments. Read our documentation on static IP addresses for more information..


Mabl's egress IPs are hosted on Google Cloud’s architecture. If your tests still have issues accessing your environments after configuring mabl Link or allowlisting static IPs, mabl may be blocked by your CDN or web aware firewall.

Excluding mabl traffic from site analytics

Mabl browser test traffic adds the following headers for traffic identification:

  • All requests feature the X-Mabl-Agent header. For example: X-Mabl-Agent: Mabl/0.1
  • All user agent strings have a custom operating system property that contains mabl. For example: User-Agent:...mabl(contains)



API and performance tests do not include these headers.