Skip to main content
NetApp Knowledge Base

BlueXP UI fails to load and displays a 502 error

  1. Last updated
  2. Save as PDF
Views:
73
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
netapp_console
Last Updated:

Applies to

  • BlueXP
  • Amazon Web Services (AWS)

Issue

 
  • After updating BlueXP to version 3.9.53, the system became inaccessible and displayed a 502 Bad Gateway error.
  • The AWS health checks for the Connector VM failed, indicating that the load balancer was unhealthy.
    • Log output included errors such as:

2025-06-09 11:25:18,562 UTC ERROR [Standalone][T4qOTeSt][][System] failed to get metadata request with error java.net.UnknownHostException: metadata.google.internal: Name does not resolve

2025-06-09 11:25:21,693 UTC WARN [Standalone][sKiT0hGm][][System] Unable to retrieve the requested metadata (/latest/meta-data/public-ipv4). The requested metadata is not found at http://169.0.0.0/latest/meta-data/public-ipv4 com.amazonaws.SdkClientException: The requested metadata is not found at http://169.0.0.0/latest/meta-data/public-ipv4

2025-06-09 11:39:30,299 UTC ERROR [IsHealthy][bj7ex6mK][][Anonymous] Could not connect to address=(host=mysql)(port=3306)(type=master): Socket fail to connect to host: mysql, port: 3306. Connection refused (Connection refused)

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.