SSL NOMATCH issue when using proxies in HTTP request

     This warning may be caused by using an IP address or a hostname that differs from that found in the certificate.
      WinVerifyTrustWarning: CERT_E_CN_NO_MATCH
      Status = 0x800b010f
      (warning) SSL Server Certificate not verified.


Basically, the IP in the SSL certificate is not the same as the IP of the proxy that it is going through... This causes the SSL certificate to go unverified when communicating with webg services.

I am using the CHILKAT HTTP class.

I would love to find out why this is happening. It always happens when connecting to any SSL HTTPS link.
Dim prxip As String = proxinf(0)
        Dim prxport As String = proxinf(1)
        If RadSocks.Checked = True Then
            http.SocksHostname = prxip
            http.SocksPort = prxport
            http.ConnectTimeout = Me.NumTim.Value
            http.ProxyPort = Nothing
        Else
            http.ProxyDomain = prxip
            http.ConnectTimeout = Me.NumTim.Value
            http.ProxyPort = prxport
        End If
 
        If Me.ChkSSL.Checked = True Then
            Dim req As New HttpRequest()
            Dim resp As New HttpResponse()
            resp = http.SynchronousRequest("https://www.google.com", 443, True, req)
        Else
            http.QuickGetStr("http://www.google.com/")
        End If

Open in new window

Idkfawin32Asked:
Who is Participating?
 
jfer0x01Connect With a Mentor Commented:
Hello,

according to

http://msdn.microsoft.com/en-us/library/bb648706(VS.85).aspx

Match the CN and the device address. For example, if the operating system is connecting to https://mydevice.contoso.com:5358/, then the CN of the server certificate must be mydevice.contoso.com.

Also

this issue is further discussed in

http://stackoverflow.com/questions/799272/why-cant-one-ssl-certificate-be-used-for-multiple-machines

it seems to me, your proxy servers must probably have a root certificate installed, ex. blah.com instead of host.blah.com

Hope this helps

Jfer
0
 
jfer0x01Commented:
any luck?
0
 
Idkfawin32Author Commented:
No luck, I just switched my entire application over to normal .Net HTTPWebRequests
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
jfer0x01Commented:
Did switching to .Net Web Requests improve your situation?
0
 
Idkfawin32Author Commented:
Yes, it resolved the issue. It was a huge pain but it solved everything.
0
 
jfer0x01Commented:
Ok,

i guess you can close question then

Jfer
0
 
Idkfawin32Author Commented:
The solution wasn't exactly a solution but it did lead me to the answer and that is good enough for me.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.