wayne.r.whitten

Disregard. WP added code tags and I didn’t see them until I came up for air. Once removed, worked fine.

Yes, unfortunately I need plugin(s) for the commenting and subscriptions. So it looks like I’ll have to go with other plugins that work locally (behind the firewall). Thanks to Jeremy and everyone else who helped. At least we tried and know for sure.

Sorry for the delay. I just submitted the results to the support site using the form above. Hope they are not hopeless. I’m adding what I believe are the highlights below.

HTTP Connection: Could not open handle for fopen() to https://jetpack.wordpress.com/jetpack.test/1/

HTTPS Connection: There are no HTTP transports available which can complete the requested request.

Test Self Connection:
[date] => Wed, 19 Feb 2014 18:47:47 GMT
[server] => Apache/2.2.17 (Win32) mod_ssl/2.2.17 OpenSSL/0.9.8o PHP/5.3.4 mod_perl/2.0.4 Perl/v5.10.1
[x-powered-by] => PHP/5.3.5
[content-length] => 42
[connection] => close
[content-type] => text/plain

XML-RPC server accepts POST requests only.

I don’t see the bottom line that contains the link for Jetpack support. The content stops at #4 with the second item “If you get a 404 message…”

Hope this works. I couldn’t figure out a better service or URL shortener to use.

What’s the URL of that support link? Maybe I can just go directly to it.

I sent this same response via email a few days ago, but didn’t add it here. I thought it might be connected or automatic.

As for the allow_url_fopen…
It was already On. (allow_url_fopen = On)

As for the debugger, I can’t get to step three. I get the following…

Jetpack Debugging Center
Testing your site’s compatibily with Jetpack…

There seems to be a problem with your site’s ability to communicate with Jetpack!

Your site isn’t reaching the Jetpack servers.
Your site isn’t securely reaching the Jetpack servers.
It looks like your site can not communicate properly with Jetpack.

Based on the documentation, I don’t seem to have any known conflicts.
I didn’t test the other plugins or theme yet for conflicts, but I doubt that’s it.
I checked the XMLRPC in my browser and it reads correctly.