NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

jsochacki's avatar
jsochacki
Aspirant
Jan 11, 2021

SSL: certificate subject name does not match target host name

I have some git repos on my readyshare drive connected to my CAX80 nighthawk modem that I am trying to clone from with SSL on and i get the following error when trying to clone from them with SSL on:

 

fatal: unable to access 'https://my-domain/shares/git/office.git/': SSL: certificate subject name (08:36:C9:3E:94:E8) does not match target host name 'my-domain.com'

 

I am able to clone from them with SSL off just fine so it is an issue with the ssl certificate as indicated above.  I have readyshare set up with port 443 open and access through https

 

I get the certificate from the modem using the following

```

openssl s_client -showcerts -servername git.mycompany.com -connect git.mycompany.com:443 </dev/null 2>/dev/null | sed -n -e '/BEGIN\ CERTIFICATE/,/END\ CERTIFICATE/ p'  > git-mycompany-com.pem

```

 

which I found here https://fabianlee.org/2019/01/28/git-client-error-server-certificate-verification-failed/

 

which i add to my global git config with 

 

```

git config --global http."https://git.mycompany.com/".sslCAInfo ~/git-mycompany-com.pem

```

 

When I go to clone I get the error at the top.

 

I am using no -ip with netgear natively to get dynamic dns and all that works fine as well.

2 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    Something to contact NG support for additional help and information. 

    Thank you. 

    • jsochacki's avatar
      jsochacki
      Aspirant

      Are you going to contact them and share the result here?  It costs money for me to contact them which is ludacris so I'm not going to be able to contact them at least by those means.

       

      I spent more time on it and made sure to upgrade all my ca certificates and even add the certificate that I get from openssl s_client connecting to it to the trusted keys list but the issue with the name of the key still but its fixable since I cant make the name of the host that I am connecting to the same as the name of the cert which is a set of octets.