topic Re: Could not connect to ********** on port 443 for protocol HTTPS in Active IQ and AutoSupport Discussions

Could not connect to ********** on port 443 for protocol HTTPS

karim_elgamil_1 — Thu, 05 Jun 2025 07:04:36 GMT

=== CLIENT ===
Version:      1.1R1
Build:        1.1.0.464
User:         KarimEL-Gamil\Karim EL-Gamil
Host:         KarimEL-Gamil (fe80::70b0:1945:e981:88ee%11)
Date:         11/27/2010 11:54 AM
OS Version:   6.1
OS Name:      Windows 7 Ultimate
Service Pack:
.NET Version: v2.0.50727
Memory Used: 27,256.00 KB
Memory Total: 4,194,304.00 KB

=== ERROR ===
NetApp.Library.UserControls.Error.DefaultErrorDetails

=== MESSAGE ===
Could not connect to sakr-shelf1.sakrgroup on port 443 for protocol HTTPS. Unable to connect to the remote server A socket operation was attempted to an unreachable network 192.168.0.124:443

=== DETAILS ===
Could not connect to sakr-shelf1.sakrgroup on port 443 for protocol HTTPS. Unable to connect to the remote server A socket operation was attempted to an unreachable network 192.168.0.124:443

=== CORRECTIVE ACTION ===
No corrective action found

=== STACK TRACE ===
   at NetApp.Ontapi.NaServer.send(Object req)
   at NetApp.Ontapi.NaServer.Invoke(Object req, Type resultType)
   at NetApp.Ontapi.NaApi`1.Invoke(INaServer server)
   at NetApp.SSM.StorageSystem.StorageSystem.InvokeOntapApi[T](NaApi`1 api, Boolean isAsync)
   at NetApp.SSM.StorageSystem.StorageSystem.InvokeONTAPIReal[T](NaApi`1 api, Boolean isAsync, Boolean showLoginDialog)
   at NetApp.SSM.StorageSystem.StorageSystem.VerifyCredentials(Boolean showLoginDialogIfNecessary)
   at NetApp.SSM.StorageSystem.StorageSystem.VerifyCredentials()

=== INNER STACK TRACE ===
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at NetApp.Ontapi.NaServer.send(Object req)

=== INNER STACK TRACE ===
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

Re: Could not connect to ********** on port 443 for protocol HTTPS

ekashpureff — Sat, 27 Nov 2010 14:10:29 GMT

Lots of err message logging from your client, but what is the background information ?

Did you ever enable SSL on the filer using 'secureadmin' ?

I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff
ekashp@kashpureff.org
Fastlane NetApp Instructor and Independent Consultant
http://www.fastlaneus.com/ http://www.linkedin.com/in/eugenekashpureff

(P.S. I appreciate points for helpful or correct answers.)

Re: Could not connect to ********** on port 443 for protocol HTTPS

ern — Sat, 27 Nov 2010 17:22:22 GMT

This doesn't look to be something that is happening on Data ONTAP but with a Windows product maybe DFM?

The error messages indicate it can't connect to a server using a particular port.

I suggest trying to use a web browser on that Windows machine and typing in //hostname:443 to see if it can't connect or gives some other error. If it can't connect I would figure out if the hostname is up with ping and then proceed accordingly with figuring out what should and shouldn't be working.

Re: Could not connect to ********** on port 443 for protocol HTTPS

FrostByte — Thu, 07 Apr 2011 20:52:56 GMT

Did you ever find an answer? I'm having the same problem on Windows 7 sp1 64bit connecting to the 8.01p2 filers. It still connects fine to the 7.3.x filers. I can't connect to https://filer or https://filer:443 on any of the filers so that didn't help. If I try to telnet to them on this port, the connection fails in one second for 7.3 machines and it takes about 10 seconds for it to fail on 8.x machines.

Re: Could not connect to ********** on port 443 for protocol HTTPS

ern — Thu, 05 May 2011 15:23:50 GMT

I can comment on AutoSupport inside of Data ONTAP making outgoing connections via SMTP, HTTP and HTTPS to proxy web servers, mail servers and over the internet to netapp.com.

I don't have too much information about incoming HTTP and HTTPS to Data ONTAP for management and file access. I am aware that HTTP/HTTPS infrastructure is different in 8.0 depending on whether it is 7-mode or Cluster-mode.

Re: Could not connect to ********** on port 443 for protocol HTTPS

FrostByte — Thu, 05 May 2011 17:05:18 GMT

We had to to set the following option.

httpd.admin.ssl.enable on

After that, everything works fine, except now the annoying filer view warnings about the invalid certificate since it's not properly signed

Re: Could not connect to ********** on port 443 for protocol HTTPS

shaunjurr — Thu, 05 May 2011 21:12:31 GMT

Hi,

If these messages mean what they say, then the problem is just that the user can't reach the network...

This would be less of a filer problem than perhaps a firewall/routing problem. The client may, of course, be emitting relatively bogus messages.

Re: Could not connect to ********** on port 443 for protocol HTTPS

rorzmcgauze — Wed, 13 Jul 2011 09:58:48 GMT

I was getting a similar message when trying to add a FAS2040 upgraded to ONTAP 8.0.2 to System Manager:

Could not connect to XXXX on port 443 for protocol HTTPS. Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond XXXX:443

I did the following to get it to work:

secureadmin setup ssl

then

options httpd.admin.ssl.enable on

now I am able to connect