Skip to content

Configuring outbound proxy

Your server might sit behind an outbound web proxy, where connections to the outside internet must go through a proxy server. This can affect features that call external HTTPS APIs, such as Azure AD authentication, OIDC authentication, and the PGM Solutions update check. It does not affect SMTP (sending emails uses the SMTP protocol directly, not HTTPS).

Configuring the proxy

Set the HTTPS_PROXY environment variable to your proxy's URL before starting Apleno Server, for example:

HTTPS_PROXY=http://proxy.example.com:8080
  • On Linux (systemd), add it to the service's environment: see the Linux installation guide.
  • In Docker, pass it with -e HTTPS_PROXY=http://proxy.example.com:8080 or under environment: in your docker-compose.yml. See the Docker guide.

Note

The lowercase https_proxy is also recognized, matching the common convention used by many other command-line tools.

Restart Apleno Server after setting the variable for it to take effect.

Testing the proxy

Once Apleno Server is restarted, verify outgoing connections work correctly:

  1. Log in to Apleno Server with an administrator account and click on your name in the top right navigation bar, then Admin panel.
  2. On the second navigation bar, click on Server then Settings.
  3. Under Network & SMTP, use the Outgoing connections test: pick a target (Azure API or PGM Solutions API) and click Test. A result will show whether the connection succeeded or failed through your proxy.

You can also run this test from the command line:

apleno-server test net azure
apleno-server test net pgm