Jetpack bug (resolve DNS)

Hi,
We’ve found a bug in jetpack plugin.

We’re using a wordpress with multisite. For security reasons we have wordpress behind an nginx proxy (all websites are served as https with trusted letsencrypt certificates), and wordpress is hosted with apache without https.

First we tried to activate both configurations in wp-config.php

define( ‘JETPACK_SIGNATURE__HTTPS_PORT’, 80 );
#$_SERVER[‘SERVER_PORT’] = 443;

The one worked some times was the first (we’ve read not to activate both at time). But this solution worked only some times, and we found that jetpack plugin got troubles to connecting to our blogs.

Finally we have meet the problem:

# curl -v “https://jetpack.wordpress.com/jetpack.testsite/1/?url=https://wp.lamardebits.org/xmlrpc.php”
* Hostname was NOT found in DNS cache
* Trying 192.0.78.26…
* Connected to jetpack.wordpress.com (192.0.78.26) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* Server certificate:
* subject: OU=Domain Control Validated; CN=*.wordpress.com
* start date: 2015-09-06 16:52:41 GMT
* expire date: 2018-10-14 11:29:26 GMT
* subjectAltName: jetpack.wordpress.com matched
* issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=https://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority – G2
* SSL certificate verify ok.
> GET /jetpack.testsite/1/?url=https://wp.lamardebits.org/xmlrpc.php HTTP/1.1
> User-Agent: curl/7.38.0
> Host: jetpack.wordpress.com
> Accept: */*
>
< HTTP/1.1 400 Bad Request
* Server nginx is not blacklisted
< Server: nginx
< Date: Sun, 13 Nov 2016 19:26:30 GMT
< Content-Type: text/plain;charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Expires: Wed, 11 Jan 1984 05:00:00 GMT
< Cache-Control: no-cache, must-revalidate, max-age=60
< X-hacker: Jetpack Test
< X-ac: 3.lhr _dca
< Strict-Transport-Security: max-age=15552000
<
* Connection #0 to host jetpack.wordpress.com left intact
{“error”:”Can not resolve your domain \”A record\””,”error_description”:”We were unable to resolve the A record for your domain. It is likely that you have recently registered your domain name. It takes several hours for new or transferred domain names to start working, so please come check back later. If you’re still having the same error after 48 hours, please contact your web hosting provider.”}

How we resolved? so putting our subdomain as A, not as CNAME.

So, I don’t know it’s a bug or is needed to ask for allow CNAME subdomains, for allowing domains in multisite wordpress as CNAME. I think this will be helpful to other users behind proxy and insite a multisited wordpress.

Thanks you much