Native Clients and Extenders Showing "Administratively Prohibited" Error

When using native clients in combination with PrivX Extenders, connections may unexpectedly fail with an "Administratively prohibited" error. This issue is typically caused by misconfiguration in PrivX's SSH proxy settings or Extender access controls. The error may also appear if the target address is restricted or session recording is improperly configured.

Potential Solution

Review and adjust the following settings to potentially resolve the issue:

  1. Ensure that your PrivX deployment is correctly configured for proxying native-client connections across all required PrivX components:

    • Extender configuration (/opt/privx/etc/extender-config.toml):

      privx_ssh_proxy_enabled = true
    • Authorizer configuration (/opt/privx/etc/authorizer.toml):

      Ensure the following keywords are present in ssh_default_extensions:

      permit-port-forwarding
      permit-X11-forwarding
    • PrivX GUI→Administration→Settings→SSH Proxy:

      • forwarder_enabled must be set to true
      • If connecting to loopback addresses (localhost, 127.0.0.1, or ::1), enable:
        • allow_connect_to_loopback = true
        • allow_connect_to_local_addresses = true
      • If connecting to local FQDNs or IPs (e.g., front-end FQDNs or IPs), enable only:
        • allow_connect_to_local_addresses = true
      • Ensure the destination address is not listed in target_blacklist
  2. Check Extender Access Permissions:

    • Navigate to PrivX GUI→Administration→Deployment→Deploy VPC/VPN Extenders
    • Under the Extender configuration, confirm that the target host's IP belongs to the allowed subnets
  3. Disable session recording on target host (if needed):

    • Go to PrivX GUI→Administration→Hosts
    • Open the settings for the relevant host and confirm that session recording is disabled if required for compatibility
  4. Verify connectivity and licensing by ensuring the following system-level conditions are met:

    • The SSH proxy component can establish outbound connections to the connection manager
    • Your PrivX license is valid and not expired

Was this page helpful?