Proxy Authentication failures between components prevent services from registering and starting properly in vRealize Automation.
search cancel

Proxy Authentication failures between components prevent services from registering and starting properly in vRealize Automation.

book

Article ID: 345662

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • Services become unavailable or fail to start or fail to register themselves to the Component Registry.
     
  • Accessing the WAPI url https://<IaaS_web1_node>/WAPI/api/status returns an error similar to:

    <HEAD><TITLE>Proxy Authorization Required</TITLE></HEAD>
    <BODY BGCOLOR="white" FGCOLOR="black"><H1>Proxy Authorization Required</H1><HR>
    <FONT FACE="Helvetica,Arial"><B>
    Description: Authorization is required for access to this proxy</B></FONT>
    <HR>
    <!-- default "Proxy Authorization Required" response (407) -->
    </BODY>
     
  • Accessing the Repository url https://<IaaS_web1_node>/repository/Data/MetaModel.svc returns an error similar to:

    Server Error in '/Repository' Application.
    The remote server returned an error: (407) Proxy Authentication Required.


Environment

VMware vRealize Automation 7.3.x
VMware vRealize Automation 7.0.x
VMware vRealize Automation 7.2.x
VMware vRealize Automation 7.1.x

Cause

This issue occurs when proxy communication is required between vRealize Automation nodes. Proxy communications are not supported between components in vRealize Automation.

Resolution

To resolve this issue, allow the non-proxied communication between vRealize Automation appliances and servers.

Additional Information

To receive an be alerted when this article is updated, click Subscribe to Article in the Actions box.

Powered by Wolken Software