Skip to main content
NetApp Knowledge Base

Cluster not reporting to ActiveIQ - Received HTTP code 403 from proxy after CONNECT

  1. Last updated
    Jun 25, 2025
  2. Save as PDF
Views:
26
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
solidfire
Last Updated:
6/25/2025, 9:23:23 AM

Applies to

  • NetApp Element Software
  • Management Node (mNode)

Issue

  • Element cluster is not reporting to Active IQ  with the proxy server configured
  • Error reported in mnode-svc-aiq-collector.log

ERROR FAILED to fetch ListAPIMethodsToFetch : (56) Received HTTP code 403 from proxy after CONNECT

  • From mNode  connectivity to Active IQ server monitoring.solidfire.com failed with error
admin@mnode01-New ~ $ curl --proxy <proxy_hostname>:8080 -v https://monitoring.solidfire.com:443
* Trying xx.xx.xx.xx:8080...
* Connected to <proxy_hostname>:8080 (xx.xx.xx.xx) port 8080 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to monitoring.solidfire.com:443
> CONNECT monitoring.solidfire.com:443 HTTP/1.1
> Host: monitoring.solidfire.com:443
> User-Agent: curl/7.74.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 403 Forbidden

 

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.