Configure a network proxy

Some network architectures may need a network proxy between the AVEVA Events to CONNECT and the egress endpoint. The process for configuring the agent to egress data through a network proxy varies depending on the proxy type.

HTTPS forward proxy

For the AVEVA Events to CONNECT to use an HTTPS forward proxy while egressing, configure the https_proxy environment variable. For information on how to configure Windows system environment variables, refer to setx.

The value of this environment variable must contain the URL of the proxy server, beginning with http. The format of the string is [user[:password]@]http://hostname[:port].

HTTPS proxy environment variable:

Note: Usage of the https_proxy environment variable may affect other .NET or .NET Core applications. If you set this environment variable, it will affect the agent egress endpoints and the agent health endpoints.

Examples:

myUser@http://192.168.2.2

myUser:myPassword@http://proxymachine.domain:3128

http://proxymachine.domain

In Windows, this may look something like:

Example of an architecture with an https forward proxy:

Reverse proxy

For the AVEVA Events to CONNECT to use a reverse proxy while egressing, you must configure the reverse proxy as an egress endpoint. For information on how to configure an egress endpoint, see Egress endpoints.

Example:

[{

"Id": "CONNECT Web API Through Proxy",

"Endpoint": "https://<reverseProxy>:<port>/<CONNECT data services endpoint>",

"ClientId": "<clientid>",

"ClientSecret": "<clientsecret>"

}]

Example of an architecture with a reverse proxy:

No proxy

For the agent to exclude a specific endpoint from using the proxy (i.e. do not use the proxy in `https_proxy` or `http_proxy`), then configure the `no_proxy` environment variable. `no_proxy` can contain a comma-separated list of hostnames.

Note: Usage of the no_proxy environment variable may affect other .NET or .NET Core applications.

Example:

192.168.2.1

some.host.com

In Windows, this may look something like: