Using CLI Behind 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:
1
export HTTP_PROXY=http://hostname:port/
2
export HTTPS_PROXY=http://hostname:port/
Copied!
If the proxy will be performing MITM for HTTPS with untrusted certificate, specify RELAY_INSECURE variable to turn off TLS verification:
1
export RELAY_INSECURE=true
Copied!
Forwarding webhooks behind a proxy
If your proxy cannot forward gRPC traffic, supply –ws flag to relay forward command:
1
relay forward --ws
Copied!
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 functionality.
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.

Platform - Previous

CLI Basics

Next - Platform

Self-hosting Server

Last modified 7mo ago

Copy link

Contents

Forwarding webhooks behind a proxy

Tunneling behind a proxy