StorageGRID AutoSupport Delivery Through Proxy Fails After Upgrading to StorageGRID 12.1

• NetApp StorageGRID 12.1
• Admin Proxy enabled (HTTP CONNECT proxy)

• Event-Triggered, User-Triggered, and Weekly AutoSupport (ASUP) messages fail to be sent over HTTPS/HTTP when AutoSupport delivery is configured through a proxy.
• The following error is observed in nms.log:

ERROR   Connection to autosupport destination https://support.netapp.com:443 failed with error Connection reset by peer - SSL_connect

• The issue began after upgrading to StorageGRID 12.1 and is reproducible across all Primary and non-Primary Admin Nodes.
• E-Series AutoSupport messages generated by StorageGRID appliance storage nodes continue to be sent successfully.
• Connectivity to the AutoSupport destination through the configured Admin Proxy is verified successfully using curland telnet.

root@Primary_admin_node_name# curl -v -x http://proxy_server:port https://support.netapp.com
* Host xxx.xxxxxx.xxx:80 was resolved.
* IPv6: (none)
* IPv4: xxx.xx.xxx.xx
*   Trying xxx.xx.xxx.xx:xx...
* CONNECT tunnel: HTTP/1.1 negotiated
* allocate connect buffer
* Establish HTTP proxy tunnel to support.netapp.com:443
> CONNECT support.netapp.com:443 HTTP/1.1
> Host: support.netapp.com:443
> User-Agent: curl/8.14.1
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection Established
< Proxy-Agent: xxxxxx/xx
<
* CONNECT phase completed
* CONNECT tunnel established, response 200
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / secp256r1 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=xx; ST=xxxxx; O=xxxx; CN=support.netapp.com
*  start date: Nov 25 00:00:00 2025 GMT
*  expire date: Nov 25 23:59:59 2026 GMT
*  subjectAltName: host "support.netapp.com" matched cert's "support.netapp.com"
*  issuer: C=xx; ST=xxxxx xxxx; L=xxx; O=xxxx xxxx; CN=xxxx xxx xxx xxx xxxx xxx xx
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* Connected to xxx.xxxxxx.xxx (xxx.xx.xxx.xx) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: support.netapp.com
> User-Agent: curl/8.14.1
> Accept: */*
>
* Request completely sent off
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
< HTTP/1.1 301 Moved Permanently
< Content-Type: text/html
< Content-Length: 185
< Connection: keep-alive
< Date: Mon, 17 Aug 2026 02:02:13 GMT
< Location: https://mysupport.netapp.com/
<
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>xxxxxxxx/</center>
</body>
</html>
* Connection #0 to host xxx.xxxx.xxx left intact 

root@Primary_admin_node_name# telnet <Proxy_server_ip> <Port>
Trying xxx.xx.xxx.xx...
Connected to xxx.xx.xxx.xx.
Escape character is '^]'.