Skip to main content
NetApp Stage KB

Proxy configuration set up screen endlessly displays, which prevents it from logging into NetApp Cloud Manager

Views:
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
CLOUD
Last Updated:

Applies to

  • OnCommand Cloud Manager (OCCM)
  • Proxy Server

Issue

  • By default, when you first deploy OCCM, it prompts you to enter a proxy server if the system does not have internet access.
  • Input the proxy server information into the following area correctly and hit the "Save" and "Close" button, but it doesn't redirect to the screen where NetApp Cloud Central account could be entered to continue to OCCM.

  • The message on the screen is
An error occurred while retrieving configuration values from server: Failed to extract Access Token from Authorization header
Server Communication Error
Unable to contact server
Try to refresh the browser or to update proxy settings
Set up Proxy configuration to allow Cloud Manager and Cloud Volumes ONTAP instances to access the Internet. Enter an empty value to disable the proxy.
  • Refresh the browser or reboot OCCM instance, it's repeatedly asking for the proxy server information and never moves forward.

 

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.
Case Citation
d77e73cb-dff4-4d34-a4e9-6030e7244375