This page describes configuration items to tweak how inbound and outbound requests are handled within the application.


For details on how to set the below configuration items, please read Environment Variables.

Configuring Trusted Redirect Hosts

When logging into the application, sometimes a redirect URI is specified to take the user back to the page that they were previously viewing. The redirect URI is validated for security reasons, and by default, only the help desk domain is permitted.

Trusted hosts can be configured using a comma delimited list of host names via the TRUSTED_REDIRECT_HOSTS environment variable. For example,, To trust all hosts, use *.,

Configuring Trusted Proxies

When running the application behind a load balancer that terminates TLS / SSL certificates, you may notice the application sometimes does not generate HTTPS links correctly. Typically, this is because the application is being forwarded traffic from your load balancer on port 80 and does not know it should generate secure links.

To solve that, you can configure a comma delimited list of proxy addresses (IP addresses and hostnames) via the TRUSTED_PROXY_IPS environment variable. For example,,


Trusting All Proxies

If you are using Amazon AWS, Cloudflare, or another "cloud" load balancer provider, you may not know the IP addresses of your actual balancers. In this case, you may use * to trust all proxies.


Configuring an Outbound Proxy

The application makes several external network connections, for example to our licensing server, to download emails, and so on. If necessary, this traffic can be sent through an outbound proxy.

The outbound proxy can be configured via the OUTBOUND_PROXY_URI environment variable and accepts a valid URI.


The following schemes are supported: