ssl certificate

• 

  gdledsan · Member · Jul 27, 2015 at 11:19 pm

  • Copy link
  • Add topic to favorites

  https://sanaconarte.com is showing a security error related to the certificate, this was not happening a week ago, please help.

  The blog I need help with is: (visible only to logged in users)

• 

  auxclass · Member · Jul 28, 2015 at 12:20 am

  • Copy link

  I have flagged this for the staff –

  you have a mapped domain name to a blog here – that is the same as my site but I just checked my site and have no error on my site

• 

  auxclass · Member · Jul 28, 2015 at 12:35 am

  • Copy link

  http://sanaconarte.com/ – loads fine
  https://sanaconarte.com/ – has an error – note the https – WordPress.COM does not yet support https linking for Domain Mapping

• 

  rachelmcr · Member · Jul 28, 2015 at 11:55 am

  • Copy link

  Hi there,

  The link auxclass gave you here is correct:

  http://sanaconarte.com/

  You can read more on our HTTPS support page about https and custom domain names. Please let me know if I can do anything more to help with that. :)

• 

  beckyleethompson · Member · Jul 29, 2015 at 10:45 am

  • Copy link

  The website I’m an admin on “beeforeitsaquilt.com” is also showing the website security certificate error. Please have your tech guys renew the encryption cert on the web server.

• 

  rachelmcr · Member · Jul 29, 2015 at 10:58 am

  • Copy link

  Hi Becky,

  Please be sure you are using this link to access that website: http://beeforeitsaquilt.com/

  If you still get an error while using that link, let me know.

• 

  beckyleethompson · Member · Jul 29, 2015 at 3:12 pm

  • Copy link

  Yes, that works. Is the ssl cert issue only on the development server?

• 

  rachelmcr · Member · Jul 29, 2015 at 3:21 pm

  • Copy link

  Hi Becky,

  You will get an SSL certificate error if you try to access that website at the address starting with https:// (with an “s” at the end) instead of http://. That’s because WordPress.com currently does not support HTTPS for custom domain names.

  As long as you use the address starting with http:// for that site, you won’t get that error there.

• 

  beckyleethompson · Member · Jul 29, 2015 at 11:08 pm

  • Copy link

  Thanks for the response. Pardon the geek speak but I can’t resist… I work in Cyber Security and actually, the reason the error shows up is because when an SSL certificate is installed on a server (obtained from a certified Certificate Authority (CA)), it is so the server can be trusted that the encrypted traffic (https), is actually going to WP vs some other host. (Somebody spoofed FaceBook’s http page a couple of years ago and hijacked thousands of its users so they now use https for all FB logins and posts.) And server encryption certs are only good for 3 years. Shortly before the expiration of the certificate, the server system administrator is supposed to request a new SSL cert from the CA and replace the old one. If they don’t, the certificate expiration error message shows. Not a big deal except that the user can’t trust the server to actually be a wp server. Click on the little padlock up in the URL bar of this page to see that the CA is GoDaddy and if you click on the View Certificate link, you can see that the server this forum is hosted on is definitely is a wp server and the cert expires Feb 21, 2018.

  Please pass this this note to your server admin team. I just typed in the https address on my laptop it re-directed to the http site without the error message. When I view it on my Surface tablet, I still see it and same goes for when I view it on my Windows phone. This tells me that one or more of the servers in the cluster supporting beeforeitsaquilt.com have expired certificates or…the load balancer that handles your mobile traffic has an expired cert vs. the web servers themselves. In that case, put on your Network Ops hat. :) thanks

• 

  rachelmcr · Member · Jul 30, 2015 at 10:57 am

  • Copy link

  Hi Becky,

  Thanks for explaining your background — The issue is that WordPress.com currently does not support SSL certificates for custom domain names. The security certificate error appears because our certificate is signed for http://wordpress.com/ and is only valid on *.wordpress.com subdomains. When your site uses a custom domain name, your browser alerts you that the SSL certificate does not match your site’s URL. (If you have disabled the alert in your browser, for example by telling your browser to always trust SSL certificates signed for *.wordpress.com, you won’t see the alert.)

• 

  florentmorin · Member · Aug 20, 2015 at 2:41 pm

  • Copy link

  I have the same problem because my website is displayed on Google with “https”, like it was before migrating to WordPress.com.

  I think it can be a useful solution for advanced users to use SNI with HTTPS for custom domains. It also improves SEO.