Skip to main content
NetApp Knowledge Base

Connector deployment to AWS fails when HTTPS is specified as proxy URL

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

Applies to

  • BlueXP
  • Amazon Web Services (AWS)
  • Specifying HTTPS URL as HTTP Proxy on 3. Network screen during connector deployment

Issue

  • Connector deployment to AWS fails with error and appears as Inactive on blueXP.

Instance is ready
Waiting for agent to be active...
Polling connector status...
Polling connector status...
Polling connector status...
Polling connector status...
.....
Failed to deploy connector.
Connector is not ready. Attempts exhausted.
Error: Connector is not ready. Attempts exhausted. at n.project

  • Even after attempting to apply the proxy settings to the connector via CLI, it remains Inactive.
  • When running sudo docker ps on the connector, only a few containers are displayed

Note: Depending on the version, around 30 containers should be displayed under normal conditions

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.