Skip to main content
NetApp Knowledge Base

Enabling HTTP Proxy for connector fails with error "Wrong status code 403"

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

Applies to

  • NetApp BlueXP
  • Microsoft Azure

Issue

Even if allowlist on proxy server includes all endpoints in Create a Connector in Azure from BlueXP, enabling proxy for BlueXP connector from HTTP Proxy Configuration fails with error:
failed to update client infra proxy - response: {"error":"Failed validating network prerequisites","message":".-----------------------------------------------------------------------------------------------------------.\n| URL | status |\n|------------------------------------------------------------+----------------------------------------------|\n| https://support.netapp.com | \u001b[1m\u001b[31mWrong status code 403, expected one of [200]\u001b[39m\u001b[22m |\n|------------------------------------------------------------+----------------------------------------------|\n| https://cloudmanager.cloud.netapp.com/tenancy/health | \u001b[32mOK\u001b[39m |\n|------------------------------------------------------------+----------------------------------------------|\n| https://stream.cloudmanager.cloud.netapp.com | \u001b[32mOK\u001b[39m |\n|------------------------------------------------------------+----------------------------------------------|\n| https://cloudmanagerinfraprod.azurecr.io | \u001b[32mOK\u001b[39m |\n|------------------------------------------------------------+----------------------------------------------|\n| https://production-artifacts.cloudmanager.cloud.netapp.com | \u001b[32mOK\u001b[39m |\n'-----------------------------------------------------------------------------------------------------------'","data":[{"success":false,"requiredUrl":{"url":"https://support.netapp.com","expectedStatus":[200]},"status":403,"text":"Wrong status code 403, expected one of [200]"},{"success":true,"requiredUrl":{"url":"https://cloudmanager.cloud.netapp.com/tenancy/health","expectedStatus":[200]},"status":200,"text":"OK"},{"success":true,"requiredUrl":{"url":"https://stream.cloudmanager.cloud.netapp.com","expectedStatus":[200,403]},"status":403,"text":"OK"},{"success":true,"requiredUrl":{"url":"https://cloudmanagerinfraprod.azurecr.io","expectedStatus":[200,404]},"status":404,"text":"OK"},{"success":true,"requiredUrl":{"url":"https://production-artifacts.cloudmanager.cloud.netapp.com","expectedStatus":[200,401]},"status":401,"text":"OK"}]}

Note:
The content of rewritten the message part above:

.-----------------------------------------------------------------------------------------------------------.
| URL                                                        | status                                       |
|------------------------------------------------------------+----------------------------------------------|
| https://support.netapp.com                                 | Wrong status code 403, expected one of [200] |
|------------------------------------------------------------+----------------------------------------------|
| https://cloudmanager.cloud.netapp.com/tenancy/health       | OK                                           |
|------------------------------------------------------------+----------------------------------------------|
| https://stream.cloudmanager.cloud.netapp.com               | OK                                           |
|------------------------------------------------------------+----------------------------------------------|
| https://cloudmanagerinfraprod.azurecr.io                   | OK                                           |
|------------------------------------------------------------+----------------------------------------------|
| https://production-artifacts.cloudmanager.cloud.netapp.com | OK                                           |
'-----------------------------------------------------------------------------------------------------------'

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.