The Jetpack server was unable to communicate with your site

I think you get this error because SSL v3 is disabled on your end.

Could you try the solution mentioned here, or forward this link to Dreamhost so they can take a look?

Let me know how it goes.

Jeremy, we can’t do that on his server but since when did you guys start blocking TLS1.0? I swear we’ve talked about this before and it was okay that we have TLS.

SSL-Session:
Protocol : TLSv1
Cipher : AES128-SHA
Session-ID: REDACTED
Session-ID-ctx:
Master-Key: REDACTED
Key-Arg : None
Start Time: 1417540278
Timeout : 300 (sec)
Verify return code: 20 (unable to get local issuer certificate)

I think the verify is what’s the issue here.

Jeremy, we can’t do that on his server but since when did you guys start blocking TLS1.0? I swear we’ve talked about this before and it was okay that we have TLS.

I’ll ask our sysadmin team and get back to you as soon as I have some news.

Alright, I have more info from someone who knows a lot more about SSL certificates than I do. ??

First, we do not block TLS1.0, no worries there.

There is no problem with the SSL certificate itself, but there is an issue with the server configuration. It’s currently set to only support RC4 ciphers, which are considered insecure and disabled in newer versions of libcurl.
GD would consequently need to fix their server configuration to support more ciphers.

You can see the problem here:
https://www.ssllabs.com/ssltest/analyze.html?d=timesofassam.com

I hope this helps.

Just to be sure I understand that, it’s an issue with the SSL server and not the apache (webhost) server?

GoDaddy is the SSL cert, DreamHost is the webhost. It’s so confusing so fast :/

it’s an issue with the SSL server and not the apache (webhost) server?

GoDaddy is the SSL cert, DreamHost is the webhost.

Right, that’s correct. I should have been more precise, sorry. By GD, I meant GoDaddy.

Jeremy when I run “openssl s_client -connect timesofassam.com:443” command on DreamPress SSH I get the following error:

—
No client certificate CA names sent
—
SSL handshake has read 4914 bytes and written 435 bytes
—

DreamHost says that DreamPress is on VPS – but they don’t support TLSv1.1 & TLSv1.2 – neither they allow to edit apache httpd.conf.

DreamHost’s shared hostings have no issue with the same GoDaddy SSL. Have a look here: https://www.ssllabs.com/ssltest/analyze.html?d=rbizsolutions.biz

While – in case of timesofassam.com – you will see this: https://www.ssllabs.com/ssltest/analyze.html?d=timesofassam.com

Jeremy – can you figure out the differences in DreamHost??

DreamHost shared hostings are not having issue with same Godaddy SSL – but DreamPress are having issue with the same Godaddy SSL.

How you people can convince me?

Both timesofassam.com & rbizsolutions.biz are having Godaddy SSL and hosted on DreamHost – both are having same SSL from Godaddy.

But rbizsolutions.biz is hosted on DreamHost shared hosting and timesofassam.com is hosted on DreamPress.

I smell an war between Godaddy & DreamHost.