SSL certificate problem, verify that the CA cert is OK.

Gastalver,
First, I'm very sorry for the delayed response.

I'm not sure why our servers aren't validating your SSL certificate properly. There have been only a few reports of this over the last few years, and we generally can get our server's root certificate store updated in a few days. It's not a systemic problem with all SSLStore certificates as we use one of their certs for our backend servers and validate many sites that use them. They are simply a broker of certs, and sell from a variety of vendors. It's possible we don't support a specific type of SSL key, yet, but will.

As for the results of that.. right now, Autotune and the Social Debug tool won't be able to scan your https pages. I've gone ahead and manually just checked your page for the issues that the Autotune Error Check tool would look for and didn't find anything.

For Social Debug, similar results that verify that tags have been added, though without some of the extra information we provide, can be found using Facebook's own Open Graph Debug tool:
developers.facebook.com/tools/debug

Again, we'll look into what cert you have and getting our root store updated soon, but wanted to get back to you with the above info now.

Thanks,
Alex

Sorry for the delay. We're working with our hosting company to get the certs updated. It's a pain in the rear, in all honesty, and something we're trying to be able streamline easier on our end... it's rare enough though that we haven't taken the time to do it yet though.

As for the Open Graph issues, it doesn't look like you created that thread. In general, I ran a few pages of your site through the linter. For articles, I see some warnings like:

The meta tag on the page was specified with name 'author', which matches a configured property of this object type. It will be ignored unless specified with the meta property attribute instead of the meta name attribute.

Those are perfectly normal and really not anything to worry about. It's not something to be fixed.

The other values I see for your articles look like the title, description and image tags are being properly set and look good in all honesty. Of course, if you're still having issues, just let us know, and we'll gladly help however we can.

Thanks,
Alex

Good timing on your post. The SSL root certificates should be updated today, and I've included your site in the testing as well. Hopefully, by the end of the day, both issues will be resolved.

We'll keep you posted.

Thanks,
Alex

Alright, the root certs were validated on our end. However, there's still issues connecting to your servers for 2 separate, yet similar, reasons. You may need to contact your hosting providers about what could be happening here.

In both cases, I'm running the following command from my Mac terminal prompt, from our server and from another remote location. In all cases, your servers are returning an invalid certificate when being called from the cURL command line utility. The certs do work in the browser, but it seems like there's a mis-configuration problem when an automated connect (non-browser) tries to connect to your sites. The command I'm running (which you can try or pass along to your hosting provider) is:
Miguel,
In your case, curl is responding with:

SSL connection using DHE-RSA-AES256-SHA
* Server certificate:
* subject: /C=US/ST=Virginia/L=Herndon/O=Parallels/OU=Parallels Panel/CN=Parallels Panel/[email protected]
* start date: 2014-10-08 15:38:49 GMT
* expire date: 2015-10-08 15:38:49 GMT
* common name: Parallels Panel (does not match 'www.forovivienda.com')
* issuer: /C=US/ST=Virginia/L=Herndon/O=Parallels/OU=Parallels Panel/CN=Parallels Panel/[email protected]

That error is indicating that the Parallels Panel SSL certificate is being returned, and not the actual site SSL cert. This is recreate-able from multiple different computers.

Edfel,
When I run the above for your site, I'm getting the following response *only from our server*:

SSL connection using DHE-RSA-AES256-SHA
* Server certificate:
* subject: /C=US/ST=Puerto Rico/L=San Juan/O=politicaboricua.com/CN=politicaboricua.com/[email protected]
* start date: 2014-10-12 06:32:48 GMT
* expire date: 2015-10-12 06:32:48 GMT
* common name: politicaboricua.com (does not match 'www.prepperspr.com')
* issuer: /C=US/ST=Puerto Rico/L=San Juan/O=politicaboricua.com/CN=politicaboricua.com/[email protected]

In that case, the SSL looks to be for politicaboricua.com and not your site. Is that a site you're affiliated with? This could be a stale certificate that we need to expunge, but if you know any other information, that would help.

Again, with the above info, it may be worth contacting your hosting providers to run the same command to see if they are getting the same error. If so, they may be able to correct things on their end.

Thanks,
Alex

Ahhhh. Thanks for that info, it really helps. It seems like your servers are using SNI, which is a newer (last few years), but not too common (yet) method of using multiple SSL certificates on a single IP address. We're working with our host to upgrade our version of OpenSSL which should support SNI and hopefully get things going for you.

Thanks again for your patience and feedback and, hopefully, this will be resolved within the next 24 hours.

Alex