Questions about SSL certificates

weatherguy
edited October 2016 in SecuritySpy
I've reviewed the information provided on the website regarding obtaining a certificate from NameCheap.com I've done all the steps and have received the certificate back.

I'm still getting errors when logging in with my SecuritySpy secure server. I'm a newbie with certs and I would appreciate some help.

First, when I created the .crt file using terminal, I used my own location and email address information to create the .crt, not the information (e.g. "bensoftware" "London" etc.,) that is on the website as an example. Was that correct?

I renamed the received SSL certificate "server.crt" and placed it in Documents/SecuritySpy folder.

When using the name I chose "https:// xxxx.view.me" in my web browser ("xxxx" being used for this post only), my browser says the site can't be found.

---> How long does it take for name I chose (xxxx.view.me) to propagate through the DNS channels?

When trying to access the site directly through my outside IP address (eg. http://172.xxx.xxx.xxx:8001) I still get an error that says that the certificate is configured improperly and that it can only be used with xxxx.view.me.

----> Is that correct behavior for a browser if the secure website is accessed through the direct IP address?

I don't know if I did something incorrect with the cert or if I'm just not waiting long enough for things to work through the DNS system. Would appreciate any help. Thanks so much.

Comments

  • Hi - the domain is viewcam.me, not view.me.

    So you need to be using xxx.viewcam.me, and this should be the domain name you used when creating the certificate.

    If you connect to SecuritySpy using a different domain name (or an IP address), the web browser will complain about a name mismatch (this is a security check to make sure the server is authentic).

    As for DDNS propagation time, this will be maximum 10 minutes.
  • Ooops. That was just a posting error on my part here. I did apply for and receive a viewcam.me certificate. And it is working now. Thanks, Ben.