PrivX Extender can be used to route traffic to VPNs that are otherwise unreachable. The Extender initializes the connection to the PrivX API endpoint, and all connections via the Extender are then tunneled through this open socket.
If, for some reason, the public load balancer is unreachable from the Extender host or if the same Extender is used from multiple PrivX locations, it is possible to configure the Extender to connect to multiple endpoints separately:
privx_public_endpoint = "https://privx.example.com" privx_instance_endpoints = [ "wss://hanode1.privx.example.com/extender-service/api/v1/ws/extender", "wss://hanode2.privx.example.com/extender-service/api/v1/ws/extender" ]
Note that for Extender to work properly, it needs to be able to connect to each PrivX node in an HA installation. This can be achieved either by connecting to PrivX using an HTTPS load balancer with sticky sessions enabled (recommended), or by setting the instance endpoints for each HA node separately in the Extender configuration file.
If the same Extender network needs to be reachable via completely separate PrivX installations, multiple Extenders can run on the same host. For this purpose, you can define the location of the Extender configuration file by using the "-config" configuration flag.
When running multiple Extenders, it is recommended to write a separate systemd file for each additional Extender.
Custom configuration files need to be located at the /opt/privx/etc/ directory.
/opt/privx/bin/privx-extender -run -config "custom-config.toml" /opt/privx/bin/privx-extender -run -config "/opt/privx/etc/custom-config.toml"
For additional configuration options, see Extender Configuration
Updated 7 months ago