<?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 Appvolumes v4 and AWS ELB in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Appvolumes-v4-and-AWS-ELB/m-p/2837175#M8387</link>
    <description>&lt;P&gt;Hey All,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;We have a horizon deployment on Vmware on AWS, we have 2 appvolumes v4 servers and we are currently load balancing but we are having some issues.&lt;/P&gt;&lt;P&gt;We have a Application Elastic load balancer setup in AWS. have a security group on the ELB to only accept 443 incoming from the internal networks using it. There is 1 listener on the ELB for 443, we are using a wildcard cert so all good there, we are forwarding to a "target group" with the 2 ip addresses of the Appvolumes servers, both show as healthy. We have the following attributes configured (stickyness : Enabled, Stickyness type: lb_cookie, Deregistration delay: 10 seconds, Stickyness duration:20 hours, slow start duration:0 seconds).&lt;/P&gt;&lt;P&gt;now it seems to work about 80% of the time, but every so often we get a user who gets the "connection error/Virtualization is disabled" message and no volumes attach.&lt;/P&gt;&lt;P&gt;The relevant part of the logs show this&amp;nbsp;&lt;/P&gt;&lt;P&gt;[2021-02-10 19:15:31.033 UTC] [svservice:P1576:T6068] HttpSendRequest: WinHttpQueryHeaders returned status code 401&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] ReadHTTPResponseHeader: WinHttpQueryHeaders failed (WWW-Authenticate) header not found&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] HttpSendRequest: WWW-Authenticate header could not be read&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] User login over HTTP failed&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] HttpUserLogin: failed (user login)&lt;/P&gt;&lt;P&gt;Im wondering if anyone is using a ELB in AWS and what configuration you are using?. im currently just pointing the Cname for the server (which was previously the ELB) to just one server now till i get this fixed. ive pointed it at each server for a few weeks each and both are fine when not going via ELB.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Mar 2021 05:13:10 GMT</pubDate>
    <dc:creator>Brendan1100</dc:creator>
    <dc:date>2021-03-22T05:13:10Z</dc:date>
    <item>
      <title>Appvolumes v4 and AWS ELB</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Appvolumes-v4-and-AWS-ELB/m-p/2837175#M8387</link>
      <description>&lt;P&gt;Hey All,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;We have a horizon deployment on Vmware on AWS, we have 2 appvolumes v4 servers and we are currently load balancing but we are having some issues.&lt;/P&gt;&lt;P&gt;We have a Application Elastic load balancer setup in AWS. have a security group on the ELB to only accept 443 incoming from the internal networks using it. There is 1 listener on the ELB for 443, we are using a wildcard cert so all good there, we are forwarding to a "target group" with the 2 ip addresses of the Appvolumes servers, both show as healthy. We have the following attributes configured (stickyness : Enabled, Stickyness type: lb_cookie, Deregistration delay: 10 seconds, Stickyness duration:20 hours, slow start duration:0 seconds).&lt;/P&gt;&lt;P&gt;now it seems to work about 80% of the time, but every so often we get a user who gets the "connection error/Virtualization is disabled" message and no volumes attach.&lt;/P&gt;&lt;P&gt;The relevant part of the logs show this&amp;nbsp;&lt;/P&gt;&lt;P&gt;[2021-02-10 19:15:31.033 UTC] [svservice:P1576:T6068] HttpSendRequest: WinHttpQueryHeaders returned status code 401&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] ReadHTTPResponseHeader: WinHttpQueryHeaders failed (WWW-Authenticate) header not found&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] HttpSendRequest: WWW-Authenticate header could not be read&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] User login over HTTP failed&lt;BR /&gt;[2021-02-10 19:15:31.166 UTC] [svservice:P1576:T6068] HttpUserLogin: failed (user login)&lt;/P&gt;&lt;P&gt;Im wondering if anyone is using a ELB in AWS and what configuration you are using?. im currently just pointing the Cname for the server (which was previously the ELB) to just one server now till i get this fixed. ive pointed it at each server for a few weeks each and both are fine when not going via ELB.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Mar 2021 05:13:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Appvolumes-v4-and-AWS-ELB/m-p/2837175#M8387</guid>
      <dc:creator>Brendan1100</dc:creator>
      <dc:date>2021-03-22T05:13:10Z</dc:date>
    </item>
  </channel>
</rss>

