WP to Twitter Error

If you’ve had problems since 10th December, then your issue is definitely related to HTTPS issues, as also indicated by the unrecognized response code. This problem means that your server is not able to make a query across an HTTPS connection. You’ll need to talk to your hosting service to get help with this; it’s a server issue.

This used to be readily solvable by using an HTTP connection, but that option is what went away with Twitter’s API changes.

You may also want to consider updating WordPress; the WordPress HTTP request system has changed on occasion, and updates since 3.6 may handle this better for you.

Do I need ssl for the domain?

No, but you did need a server that is able to place requests over SSL.

If you enable OAuth debugging, you’ll see more detailed information when you attempt to connect to Twitter, which you can send to your host for support.

Best,
Joe

I enabled OAuth debugging but don’t see any more detailed information anywhere on a test post I just made. Where would this information be?

Next I contacted my host. ‘Openssl is already available in server. It will be handling ssl requests’. It’s running https service on a certain port.

Any help fixing this would be greatly appreciated.

I seem to be very stuck at this point. Any help really appreciated!

I am stuck with the similar problem. I spoke to the admin guys in my company and according to them ssl is already enabled on the server.

Any help is much appreciated.

As I said, the OAuth debugging is visible when you connect to Twitter, and only when you connect to Twitter. You need to disconnect your account from Twitter and reconnect it to see the results of that debugging.

This I did. It resulted in a big error. Here it is (I replaced my keys with ****):

Summary Connection Response:
WP to Twitter was unable to establish a connection to Twitter.
Account Verification Data:

Full Connection Response:
jd_TwitterOAuth Object
(
[http_code] =>
[url] =>
[host] => https://api.twitter.com/1.1/
[format] => json
[decode_json] =>
[last_api_call:private] =>
[http_header] =>
[sha1_method] => WPOAuthSignatureMethod_HMAC_SHA1 Object
(
)

[consumer] => WPOAuthConsumer Object
(
[key] => ********************
[secret] => ********************
[callback_url] =>
)

[token] => WPOAuthConsumer Object
(
[key] => ********************
[secret] => ********************
[callback_url] =>
)

[useragent] => WP to Twitter https://www.joedolson.com/articles/wp-to-twitter
)

I disconnected and then reconnected as you suggest. This is the result (keys replaced by ****):

Summary Connection Response:
WP to Twitter was unable to establish a connection to Twitter.
Account Verification Data:

Full Connection Response:
jd_TwitterOAuth Object
(
    [http_code] =>
    [url] =>
    [host] => https://api.twitter.com/1.1/
    [format] => json
    [decode_json] =>
    [last_api_call:private] =>
    [http_header] =>
    [sha1_method] => WPOAuthSignatureMethod_HMAC_SHA1 Object
        (
        )

    [consumer] => WPOAuthConsumer Object
        (
            [key] => **********************
            [secret] => **********************
            [callback_url] =>
        )

    [token] => WPOAuthConsumer Object
        (
            [key] => **********************
            [secret] => **********************
            [callback_url] =>
        )

    [useragent] => WP to Twitter https://www.joedolson.com/articles/wp-to-twitter
)

That’s kind of what I expected. It’s a total failure to connect. That means its not an SSL transport issue, it’s a complete inability on your server to communicate with Twitter. There’s really nothing I can do about this;.

Install the plugin Query Monitor and you’ll be able to see where the transport is failing, but ultimately it’s a server issue that you’ll have to work with your host to resolve.

OK, I have ascertained that SSL is all up and running with the host.

I have also upgraded WP and the plugin. I shall let you know if the problem persists.