<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PVWA Load Balancing Configuration and API Connectivity Issues (through the load balancer) in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-configuration-and-api-connectivity-issues/m-p/1419704#M87698</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have multiple PVWA instances in our environment. Currently, they are configured in a round-robin setup, but only one instance is active at a time due to priority settings.&lt;/P&gt;&lt;P&gt;Our goal is to have traffic balanced across all PVWA instances (for example, using a least-connections method, without prioritizing a single instance, similar to how PSMP (PSM for SSH is configured)).&lt;/P&gt;&lt;P&gt;After reviewing the documentation, it seems there are no specific guidelines for PVWA load balancing. Is this because there is no recommended method for PVWA, unlike PSM/PSMP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/Load-Balancer-Implementation-with-PVWA-General-Guidelines&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pas%20inst/pvwa-install-multiple-pvwa-env.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/00003551&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pas%20cloud/aws-loadbalancer-for-pvwa.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, our users cannot access CyberArk PVWA directly, they must go through the load balancer. However, API calls fail because the load balancer returns a simple HTML response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this case, would it be better to reconfigure the load balancer so it accepts API calls, or to create a certificate that includes all PVWA instances and their IPs as FQDNs/SANs, so that API calls can be properly handled when redirected to a specific PVWA instance?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/RESTAPI-call-is-not-working-load-balancer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2026 20:51:18 GMT</pubDate>
    <dc:creator>A.ElSheredi582594</dc:creator>
    <dc:date>2026-04-27T20:51:18Z</dc:date>
    <item>
      <title>PVWA Load Balancing Configuration and API Connectivity Issues (through the load balancer)</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-configuration-and-api-connectivity-issues/m-p/1419704#M87698</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have multiple PVWA instances in our environment. Currently, they are configured in a round-robin setup, but only one instance is active at a time due to priority settings.&lt;/P&gt;&lt;P&gt;Our goal is to have traffic balanced across all PVWA instances (for example, using a least-connections method, without prioritizing a single instance, similar to how PSMP (PSM for SSH is configured)).&lt;/P&gt;&lt;P&gt;After reviewing the documentation, it seems there are no specific guidelines for PVWA load balancing. Is this because there is no recommended method for PVWA, unlike PSM/PSMP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/Load-Balancer-Implementation-with-PVWA-General-Guidelines&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pas%20inst/pvwa-install-multiple-pvwa-env.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/00003551&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pas%20cloud/aws-loadbalancer-for-pvwa.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, our users cannot access CyberArk PVWA directly, they must go through the load balancer. However, API calls fail because the load balancer returns a simple HTML response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this case, would it be better to reconfigure the load balancer so it accepts API calls, or to create a certificate that includes all PVWA instances and their IPs as FQDNs/SANs, so that API calls can be properly handled when redirected to a specific PVWA instance?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/RESTAPI-call-is-not-working-load-balancer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 20:51:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-configuration-and-api-connectivity-issues/m-p/1419704#M87698</guid>
      <dc:creator>A.ElSheredi582594</dc:creator>
      <dc:date>2026-04-27T20:51:18Z</dc:date>
    </item>
    <item>
      <title>Re: PVWA Load Balancing Configuration and API Connectivity Issues (through the load balancer)</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-configuration-and-api-connectivity-issues/m-p/1419705#M87699</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You should have a single certificate that includes the load balancer address and the PVWA servers in the pool. I would use the FQDN vs IP addresses for subject alternative names. There might be a need to review the load balancer configuration to ensure you have sticky sessions or session persistence set.&lt;/P&gt;&lt;P&gt;Worst case you could setup a separate PVWA with its own load balancer and use it only for API calls, however that requires a new server, LB, and certificate so might not be reasonable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What errors are you seeing in the logs? Are you sure the initial PVWA is being used during redirection activities? Is the API token generated on one PVWA and then actions attempted to perform on a different PVWA?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 11:38:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-configuration-and-api-connectivity-issues/m-p/1419705#M87699</guid>
      <dc:creator>D.Demshock823557</dc:creator>
      <dc:date>2026-04-28T11:38:20Z</dc:date>
    </item>
  </channel>
</rss>

