Cryptlex Documentation
  • Welcome to Cryptlex!
  • Getting Started
    • Overview
    • Licensing Models
  • License Management
    • License Templates
    • Implementing License Models
    • Creating Licenses
    • License Subscriptions
    • Custom License Fields
    • Meter Attributes
    • Suspending Licenses
    • Revoking Licenses
    • Maintenance Policies
  • Feature Management
    • Overview
    • Features and Entitlement Sets
    • License Feature Entitlements
    • Accessing Feature Entitlements
    • Use Cases
  • User Management
    • Roles
    • Creating Users
    • Authenticating Users
    • Organizations
    • Resellers
    • Customer Portal
    • Reseller Portal
    • Google SSO
    • SAML SSO
  • Release Management
    • Overview
    • Creating Releases
    • Distributing Releases
  • Node Locked Licenses
    • Overview
    • Using LexActivator
      • Using LexActivator with C, C++ and Objective C
      • Using LexActivator with C#
      • Using LexActivator with VB.NET
      • Using LexActivator with Java
      • Using LexActivator with Delphi
      • Using LexActivator with Python
      • Using LexActivator with Go
      • Using LexActivator with Node.js
      • Using LexActivator with Ruby
      • Using LexActivator with Android
      • Using LexActivator with iOS
      • Using LexActivator with Flutter
    • Using Web API
    • Offline Activations
    • Proxies and Firewall
  • Floating Licenses
    • Overview
    • Hosted Floating License Server
    • On-Premise Floating Licenses
      • LexFloatServer
      • Using LexFloatClient
        • Using LexFloatClient with C, C++ & Objective C
        • Using LexFloatClient with C#
        • Using LexFloatClient with VB.NET
        • Using LexFloatClient with Java
        • Using LexFloatClient with Delphi
        • Using LexFloatClient with Python
        • Using LexFloatClient with Node.js
        • Using LexFloatClient with Go
        • Using LexFloatClient with Android
        • Using LexFloatClient with iOS
      • Offline Floating License
  • Named User Licenses
  • Timed Trials
    • Verified Trials
    • Unverified Trials
  • Licensing Docker Apps
  • Webhooks
  • Automated Emails
  • Web Integration
    • Personal Access Tokens
    • Using Web API
    • Using Zapier
    • Using FastSpring
    • Custom Development
  • Changelog
    • Web API
    • LexActivator
    • LexFloatClient
    • LexFloatServer
  • Legal
    • Terms of Service
    • Privacy Policy
    • Subprocessors
    • Data Processing Addendum
    • Service Level Agreement
    • Security, Privacy, and Compliance
    • Open Source Licenses
  • Cryptlex On-Premise
    • Overview
    • System Requirements
    • Server Layout
    • Installation Guide
      • Docker Compose
      • Kubernetes
    • Configuring Client Libraries
    • Monitoring and Error Reporting
Powered by GitBook
On this page
  • Proxies
  • Custom proxy settings
  • Firewall Whitelisting
  • Access Through Firewall
  1. Node Locked Licenses

Proxies and Firewall

Proxies

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

To detect proxy settings, it uses 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. Simply use the following LexActivator API function:

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

The proxy format should be:

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

Following are some examples of the 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

To enable LexActivator license and trial activations through your firewall, it's essential to whitelist Cryptlex IP addresses. This ensures smooth operation even if your customer's policy restricts access from external IP addresses and websites.

Access Through Firewall

If the security policy at your customer's end denies access from external IP addresses and websites, you will need to whitelist specific IP addresses. A whitelist permits access to designated IP addresses and sites that would otherwise be blocked by your security policy.

For Our US Data Center:

  • IP Addresses to Whitelist:

    • 52.223.22.71

    • 35.71.188.31

  • Web API URL to Whitelist:

    • https://api.cryptlex.com:443

For Our EU Data Center:

For customers utilizing our EU data center, the following IP addresses and URL should be whitelisted:

  • IP Addresses to Whitelist:

    • 75.2.113.112

    • 99.83.149.57

  • Web API URL to Whitelist:

    • https://api.eu.cryptlex.com:443

PreviousOffline ActivationsNextFloating Licenses

Last updated 10 months ago