It looks like your support ticket is still open and active, so hopefully you’re able to find a solution there. If not, I can walk you through some debugging steps to find out exactly why Akismet says that your site can’t connect.
Hi,
It’s still open and slowly going nowhere. Their latest reply was still on SSL, telling me that HTTPS: Fail clinches it (for Jetpack). But in their advanced debug log it shows HTTP and HTTPS as fail with curl 28 error – a timeout:
SERVER_PORT: 443
HTTPS: on
REMOTE_ADDR: 128.206.136.189
PROTECT_TRUSTED_HEADER: {“trusted_header”:”REMOTE_ADDR”,”segments”:1,”reverse”:false}
TEST RESULTS:
HTTP: FAIL
HTTPS: FAIL
IDENTITY_CRISIS: PASS
SELF: FAIL
RAW TEST RESULTS:
HTTP
cURL error 28: Resolving timed out after 5514 milliseconds
HTTPS
cURL error 28: Resolving timed out after 5513 milliseconds
Followed by these:
[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
(
[code] => 400
[message] => Bad Request
)
I just can't believe that this is SSL related if it thinks HTTP is also failing.
Again, all of the above was specific to Jetpack, but surprisingly from Akismet support. I had a ticket open with both of them and they closed the Jetpack one. I have no idea if Akismet has its own debugging or anything, it just tells me that outbound HTTPS isn't working.
Thanks for the extra details. Those Jetpack tests are helpful. I also found the emails you exchanged with my colleagues, and will reply very soon. Hopefully we can get this all fixed so you can use the 2 plugins!
