Proxies and Firewall

Proxies

LexActivator automatically detects the proxy settings of the machine. So, in most cases, you don't need to worry about whether your user is behind a proxy server.

To detect proxy settings, it uses the standard methods available for each operating system. On Windows, it checks the system proxy settings; on macOS, it reads proxy settings from the system internet settings; and on Linux, it reads proxy settings from the environment variable http_proxy.

Custom proxy settings

You can allow the user to set the proxy settings to be used by LexActivator with the following LexActivator function:

SetNetworkProxy("http://username:password@host:port/");

The proxy format should be:

[protocol://][username:password@]machine[:port]

Some examples of valid proxy strings:

  • http://127.0.0.1:8000/
  • http://user:pass@127.0.0.1:8000/
  • socks5://127.0.0.1:8000/

Firewall whitelisting

If the security policy at your customer's end blocks access to external IP addresses and websites, license and trial activations will fail unless the Cryptlex IP addresses and Web API URL are whitelisted in the firewall.

Access through firewall

Ask your customer to whitelist the IP addresses and Web API URL for the data center your account uses.

Data centerIP addresses to whitelistWeb API URL to whitelist
US (default)52.223.22.71
35.71.188.31
https://api.cryptlex.com:443
EU75.2.113.112
99.83.149.57
https://api.eu.cryptlex.com:443
Licensing via Web APISandbox Environments
Last updated: