---
title: "HTTP proxy configuration | WebhookRelay"
meta:
  "og:description": "How to configure relay or webhookrelayd agent to work behind a proxy"
  "og:title": "HTTP proxy configuration"
  description: "How to configure relay or webhookrelayd agent to work behind a proxy"
---

![Stripes](https://webhookrelay.com/docs/installation/behind-proxy/images/stripes.svg)

Documentation

**Fundamentals**

# **HTTP proxy configuration**

How to configure relay or webhookrelayd agent to work behind a proxy

When using `relay` CLI (`webhookrelayd` container also respects these variables) to specify a proxy that the application should use to connect, set environment variables:

```
export HTTP_PROXY=http://hostname:port/
export HTTPS_PROXY=http://hostname:port/
```

If the proxy will be performing MITM for HTTPS with untrusted certificate, specify **RELAY_INSECURE** variable to turn **off** TLS verification:

```
export RELAY_INSECURE=true
```

## [Forwarding webhooks behind a proxy](#forwarding-webhooks-behind-a-proxy)

If your proxy cannot forward [GRPC](https://grpc.io) traffic, supply **--ws** flag to `relay forward` command:

```
relay forward --ws
```

This command will switch webhook transport from **GRPC** to **WebSocket**. The only downside of using WebSocket transport is that you will not be able to view response status code through the web UI as they are not returned. This will be changed in future and underlying protocols will offer same funcionality.

## [Tunneling behind a proxy](#tunneling-behind-a-proxy)

When using tunnel, `relay` CLI and `webhookrelayd` Docker container will create a TCP connection to either `tunnel.webrelay.io:9800` or other hosts based on the tunnelling region. Ensure that this URL is reachable.

Did this page help you?