Apply Let's Encrypt To Website & Jetpack Cannot Acces Site

Hi there:

The issue doesn’t appear to be with your SSL certificate, but that your site isn’t properly connected at the moment.

Before we troubleshoot further, can I have you disconnect and reconnect Jetpack to your WordPress.com user account? To disconnect/reconnect Jetpack, go to Jetpack -> Jetpack in your site’s dashboard. Then, click the My Jetpack button and on the next screen, click the “Disconnect site from WordPress.com” button as shown here: https://d.pr/i/1leC0

Click that, then reconnect to WordPress.com when you see the prompt to do so.

Then, let me know if that works or if you see any errors and I’ll check things again on our end.

Let me know if you have any questions.

Hi, I’ve carefully followed your advice.

It seems to connect absolutely fine. However, if I log out of wordpress.com and login again … the sites are showing the red alarm error – the site cannot be accessed.

I have 16 sites in WordPress.com > My Sites
14 connect fine
2 have the connection problem … they are the two that I have recently applied the Let’s Encrypt SSL

I would bet my house that if I applied the SSL to another site … that would follow the same pattern. The evidence is strong from a diagnostic point of view.

Many Thanks.

Regards Mark

It seems to connect absolutely fine. However, if I log out of wordpress.com and login again … the sites are showing the red alarm error – the site cannot be accessed.

Actually, your site is not connected, at least not on our end. If it’s not properly connected to our servers you also won’t be able to use the WordPress.com My Sites manager.

Can you contact your hosting provider and explain to them that we are unable to access your blog via cURL, which is needed in order to use Jetpack on your site.

You can let them know we tested the following:

1. Check for access to xmlrpc.php via browser:
https://clearlinebc.co.uk/xmlrpc.php?for=jetpack

That test returned “XML-RPC server accepts POST requests only.” which is a valid result.

2. Check for access via cURL by running the following command from the command prompt:
curl -A "Jetpack by WordPress.com" -is -H 'Content-Type: text/xml' --data '<?xml version="1.0"?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>' 'https://clearlinebc.co.uk/xmlrpc.php?for=jetpack' && echo

The cURL test returned the following invalid result:

HTTP/1.1 400 Bad Request
Server: nginx
Date: Fri, 11 Mar 2016 21:11:29 GMT
Content-Type: text/html
Content-Length: 1393
Connection: keep-alive
Last-Modified: Wed, 25 Jun 2014 08:34:14 GMT
ETag: "6208dc-571-4fca4f0f0ed80"
Accept-Ranges: bytes
Host-Header: 192fc2e7e50945beb8231a492d6a8024

Please provide the information above to your hosting provider so that they can correct the server settings to allow cURL access.

Just to check, I checked the other sites on your account and the two other sites that are using SSL, the ad*************es.com site is connected and working properly, but the other site tester.ad*******-**mo.com has the exact same errors as I outlined above, so it’s not the SSL, but more a server access issue.

I have same problem this case.

I think that. jetpack server didn’t support SNI(Server Name Indication) connect.

SNI makes be a lot of sites use to same 443 port.
also curl didn’t support SNI connect.

I tested curl call on same server.

curl -A "Jetpack by WordPress.com" -is -H 'Content-Type: text/xml' --data '<?xml version="1.0"?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>' 'https://wp.enteroa.kr/xmlrpc.php?for=jetpack' && echo

then get this result.

HTTP/1.1 200 OK
Date: Sat, 12 Mar 2016 07:48:38 GMT
Server: Apache
Set-Cookie: session=;Max-Age=0;path=/
Connection: close
Cache-Control: max-age=2592000
Expires: Mon, 11 Apr 2016 07:48:38 GMT
Cache-Control: no-cache
Set-Cookie: session=;Max-Age=0;path=/
Strict-Transport-Security: max-age=86400
Content-Length: 435
Content-Type: text/xml; charset=UTF-8

However other server didn’t connecting it then result is empty. also access_log is empty.

i think SNI is not wrong setting. it’s modern technology.

Sorry my bad.
I solved own

when I up https on my webserver(apache)
just do “firewall restart”.

will be update /etc/pki/tls/certs/ca-bundle.crt and /etc/pki/nssdb

CentOS : yum update ca-certificates nss
iptables -F

after “firewall restart” then work fine.

I don’t know “how https work on browsers” before.

Thankyou,
problem resolved.
How? I hadn’t set the https:// in the wordpress General > Settings
Once done … works.
Thanks for all yuor help. sorry about the red herring.
Regards Mark