---
title: "Configure Autify Settings when using a Proxy Server | Autify Guide"
slug: "configuration-when-using-a-proxy-server"
description: "Optimize Testing with Proxy Server: Learn How to Configure Autify Settings to use with your Proxy Server. Start your Free Trial!"
updated: 2024-05-16T08:13:22Z
published: 2024-05-16T08:13:22Z
canonical: "help.autify.com/configuration-when-using-a-proxy-server"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.autify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration when using a Proxy server

## Options to specify when using a proxy server

Even if you are using a proxy server, you can use Autify Connect by specifying options.

### Using a proxy server for the traffic between the Autify Connect client and Autify Connect server

The server running the Autify Connect client must be able to communicate with the Autify Connect server. However, the Autify Connect server is a server provided by Autify and exists on a public network. Therefore, if the server running the Autify Connect client needs to go through a proxy server to access the Autify Connect server, please use the following option:

```
--tunnel-proxy [Proxy server address(e.g. http://host:port)]
```

#### Proxy server fails to resolve the value of the Host header in the outgoing request by DNS

If your proxy server fails to resolve the value of the host header in the outgoing requests from the Autify Connect client to the Autify Connect server by DNS, the Autify Connect startup will fail.

In some cases, you may encounter errors similar to the following:"

```
Your requested host "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.connect.autify.com" could not be resolved by DNS.
```

In such cases, using the following option may resolve the issue:

```
--experimental-x-host-header
```

#### Disabling SSL certificate verification to establish tunnel connections

If it's necessary to disable SSL certificate verification to establish tunnel connections, you can disable it by using the following option:

```
--experimental-no-ssl-verify
```

#### Example of command with options

The following is an example command using previously mentioned options:

```
autifyconnect --experimental-no-ssl-verify --experimental-x-host-header --tunnel-proxy http://host:port --key your-key-here
```

### When using a proxy server for the traffic between the Autify Connect Client and the application under test

The server running the Autify Connect client must be able to communicate with the application under test. Therefore, if the server running the Autify Connect client needs to go through a proxy server to access the application under test, please use the following option:

```
--sut-proxy [Proxy server address(e.g. http://host:port)]
```

### Use options in combination

You can use the `--tunnel-proxy` and the `--sut-proxy` options together. Please set up both options if you want both the Autify Connect client and server traffic to go through the proxy server.

![en-sut-tunnel-proxy-image.png](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/en-sut-tunnel-proxy-image.png?sv=2026-02-06&spr=https&st=2026-11-01T09%3A15%3A37Z&se=2026-11-01T10%3A15%3A37Z&sr=c&sp=r&sig=1ANDgVQvOvOfoSw%2B09TyzGPcwvmLXqh8ZNO5WSrKVko%3D)

## If basic authentication is configured on the proxy server

The basic authentication information for the proxy server can be configured from the "Basic auth credentials" in the workspace. For more information, see [**Basic authentication**](/docs/en/basic-authentication).