<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Avi on Why did IT fail</title><link>https://www.why-did-it.fail/tags/avi/</link><description>Recent content in Avi on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Wed, 02 Feb 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/avi/index.xml" rel="self" type="application/rss+xml"/><item><title>TKGS failing to authenticate with the NSX ALB (AVI)</title><link>https://www.why-did-it.fail/blog/2022-01-tkgs-avi-basicauth/</link><pubDate>Wed, 02 Feb 2022 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2022-01-tkgs-avi-basicauth/</guid><description><![CDATA[While rebuilding my lab from scratch with
vSphere 7.0 U3c NSX Advanced (AVI) Load Balancer 21.1.3 I hit a situation where my TKGS installation would not continue with an error, it was stuck for hours:
The control plane VM &lt;ID&gt; was unable to authenticate to the load balancer (Avi - https://&lt;NSX ALB Controler IP&gt;:443/api/cluster) with the username &#39;&lt;user&gt;&#39; and the supplied password. Validate the Supervisor cluster load balancer&#39;s authentication configuration. To make a long story short, while user, password and connectivity check out it looks like the AVI defaults changed along the way.]]></description></item></channel></rss>