This site cannot be accessed. Disconnect Site

So I’ve continued my research for this issue, by reading up on the Known Issues (none of which apply), the Support Pages & Support Forum.

I’ve also verified the XMLRPC file is correct.

I’ve done an internet search for this issue, and there are quite a few others with the same problem, to which the generic answer and dismissal of “Contact Your Host” is given.

As you can see below, my domain registrar is Google and the domain was registered in November of 2014:

Domain Name: wetakeitlive.com
Registry Domain ID: 1883718473_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: https://domains.google.com/
Updated Date: 2015-11-05T12:48:15.0Z
Creation Date: 2014-11-05T12:47:15.0Z
Registrar Registration Expiration Date: 2016-11-05T12:47:15.0Z
Registrar: Google Inc.
Registrar IANA ID: 895
Registrar Abuse Contact Email: registrar-abuse[at]google.com
Registrar Abuse Contact Phone: +1.877-237-6466
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited

The subdomain manage.wetakeitlive.com has been in place for nearly two weeks and has it’s own “A Record” pointing at its own, dedicated IP Address, to which a valid SSL has already been issued and is working.

Can you please use Jetpack’s Debugger module to send us some more information about your site?

1) Go to the Jetpack page in your dashboard.
2) Click on the Debug link appearing at the bottom of the page.
3) Click the link that says “click here to contact Jetpack support.”
4) Fill in the description box and your name and email address.
5) Click the “Contact Support” button.

Thanks!

Yes Jeremy…

Actually, your support team should have received it before you composed this message. I did as you requested about 5 minutes ago.

Alright. We’ll get back to you soon then!

Just in case you wanted to know,

I’m also having the same problem, with a different site, on a different sever (different Domain and IP Address).

It looks like your site can not communicate properly with Jetpack.
SELF:
	Array
(
    [headers] => Array
        (
            [server] => nginx
            [date] => Sat, 13 Feb 2016 02:23:04 GMT
            [content-type] => text/plain;charset=utf-8
            [connection] => close
            [expires] => Wed, 11 Jan 1984 05:00:00 GMT
            [cache-control] => no-cache, must-revalidate, max-age=60
            [pragma] => no-cache
            [x-hacker] => Jetpack Test
            [x-ac] => 3.dfw _dfw
            [strict-transport-security] => max-age=15552000
        )

    [body] => {"error":"Communication error","error_description":"We were unable to make an XML-RPC request to your website. Please make sure that XML-RPC is turned on and that Jetpack is installed, activated and connected with your WordPress.com account. If the error persists, try disconnecting and connecting Jetpack again."}
    [response] => Array
        (
            [code] => 400
            [message] => Bad Request
        )

    [cookies] => Array
        (
        )

    [filename] =>
)

Again, the domain reflexmedicalmolding.com has been registered for 18 months, has a dedicated IP Address, to which a valid SSL has already been issued (and is working), and is confirmed HTTP/2 valid.

Said domain produces this pingdom DNS Health Check result, which I think clearly shows a fully validated DNS (except IPv6 which doesn't really matter - yet), complete with A Record & Reverse DNS.

So, I have to wonder if there is a special port (or ports) JetPack uses to communicate with WordPress.com, that could potentially be blocked by the firewall config?

I have submitted a second support request for the reflexmedicalmolding.com domain/website as well.

Same issue here. Been losing my mind over this.

I too have submitted a ticket with all of this information, same exact error.

Were you able to get this issue resolved?

I too have submitted a ticket with all of this information, same exact error.

That was the right thing to do. We’ll get back to you soon!

@tnwtech

Go to: Settings > General

Check the following settings:

1. WordPress Address (URL)
2. Site Address (URL)

Does the http/https portion match? Read the following quote, provided as a response to my support ticket?

Jetpack uses your site url settings to look for the xmlrpc.php file in your WordPress installation, to communicate with your site.

If you are using an SSL certificate, but have an https:// URL set in your settings, often the response code Jetpack will receive when attempting to communicate with that xmlrpc.php file, will be a 302 redirection to the https:// version of your site, rather than the 200 status response it is expecting, and the Jetpack connection will fail.

If you are using an SSL certificate, it is best to have the URLs on the Settings > General page of your dashboard match.

– Lisa (Happiness Engineer)

[body] => {“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.”}
[response] => Array

Could you try what I suggested in the other thread where you commented?