"Twitter outputted an error: ."

Does 2.1.2 work on the local dev server?

Tx for the prompt reply, Bo?tjan, sorry for the delay – I’ve been on other jobs!

yup, both 2.1.2 and 2.1.4 work on the dev server, which is MAMP, PHP 5.4.10.

Production is Centos 6.4 running PHP 5.3.3 with FastCGI… not sure what I can tell you about the reverse proxy – I don’t know much about it! I’ve just updated to Twitget 2.1.4 on Prod, and am still getting the same error.

The production server is: https://nosmokes.com.au/ – for now, I’ve pasted a static copy of the feed from the dev server, and twitget is outputting the error inside a comment which can be see in the source prefixed by ‘twitget: ‘.

Can you recommend any test I can run / steps I can take? I tried to install twitter tools on prod, but I don’t have enough permissions to install ruby ??

Thanks for investigating.. if it’s of interest to you, I can create a wp user for you…

Tx, Tim

Hokay.. maybe this is more useful.. I added another shortcode and a copy of twitter_status_11() in directly.. I can get options, here is what $tmhOAuth = new tmhOAuth returns:

object(tmhOAuth)#312 (6) {
  ["response"]=>
  array(0) {
  }
  ["params"]=>
  array(0) {
  }
  ["headers"]=>
  array(0) {
  }
  ["auto_fixed_time"]=>
  bool(false)
  ["buffer"]=>
  NULL
  ["config"]=>
  array(29) {
    ["user_agent"]=>
    string(56) "tmhOAuth 0.7.2-SSL - //github.com/themattharris/tmhOAuth"
    ["timezone"]=>
    string(3) "UTC"
    ["use_ssl"]=>
    bool(true)
    ["host"]=>
    string(15) "api.twitter.com"
    ["consumer_key"]=>
    string(22) "<deleted>"
    ["consumer_secret"]=>
    string(41) "<deleted>"
    ["user_token"]=>
    string(50) "<deleted>"
    ["user_secret"]=>
    string(41) "<deleted>"
    ["force_nonce"]=>
    bool(false)
    ["nonce"]=>
    bool(false)
    ["force_timestamp"]=>
    bool(false)
    ["timestamp"]=>
    bool(false)
    ["oauth_version"]=>
    string(3) "1.0"
    ["oauth_signature_method"]=>
    string(9) "HMAC-SHA1"
    ["curl_connecttimeout"]=>
    int(30)
    ["curl_timeout"]=>
    int(10)
    ["curl_ssl_verifyhost"]=>
    int(2)
    ["curl_ssl_verifypeer"]=>
    bool(false)
    ["curl_cainfo"]=>
    string(70) "<deleted>nosmokes.com.au/wp-content/plugins/twitget/lib/cacert.pem"
    ["curl_capath"]=>
    string(59) "<deleted>nosmokes.com.au/wp-content/plugins/twitget/lib"
    ["curl_followlocation"]=>
    bool(false)
    ["curl_proxy"]=>
    bool(false)
    ["curl_proxyuserpwd"]=>
    bool(false)
    ["curl_encoding"]=>
    string(0) ""
    ["is_streaming"]=>
    bool(false)
    ["streaming_eol"]=>
    string(2) "
"
    ["streaming_metrics_interval"]=>
    int(60)
    ["as_header"]=>
    bool(true)
    ["debug"]=>
    bool(false)
  }
}

(I’ve deleted sensitive data) – looks like a whole lot of nulls there!

Also, I’ve turned on debug logging, and I’m not getting any relevant errors.

define( 'WP_DEBUG', true );
    // log to wp-content/debug.log
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

For those following along at home, there are debugging scripts for tmhOAuth here: https://github.com/themattharris/tmhOAuth-examples/blob/master/verify.php

when I run:
$code = $tmhOAuth->request('GET', $tmhOAuth->url('1/account/verify_credentials'));

0 (zero) is returned…

also: if i try verify_ssl.php, I get:

Array
(
    [raw] =>
    [code] => 0
    [response] =>
    [info] => Array
        (
            [url] => https://api.twitter.com/1/account/verify_credentials.json
            [content_type] =>
            [http_code] => 0
            [header_size] => 0
            [request_size] => 0
            [filetime] => -1
            [ssl_verify_result] => 0
            [redirect_count] => 0
            [total_time] => 0
            [namelookup_time] => 3.5E-5
            [connect_time] => 0.000841
            [pretransfer_time] => 0
            [size_upload] => 0
            [size_download] => 0
            [speed_download] => 0
            [speed_upload] => 0
            [download_content_length] => -1
            [upload_content_length] => -1
            [starttransfer_time] => 0
            [redirect_time] => 0
            [certinfo] => Array
                (
                )

        )

    [error] => Problem with the SSL CA cert (path? access rights?)
    [errno] => 77
)

I understand that we're explicitly setting curl_ssl_verifypeer to false, I'm just following every lead! Am I reading that right - looks like there is no reply whatsoever, so is the signal even getting out?

I don’t think it can make a difference, but try pasting the contents of this file:

https://github.com/themattharris/tmhOAuth/blob/master/cacert.pem

In your Twitget folder under

lib/cacert.pem

And paste the logs again afterwards.

I’ve asked this question on stackexchange, too:
https://stackoverflow.com/questions/16526325/response-code-0-from-tmhoauth-blocked-by-reverse-proxy

there’s a link to a extended debugging output in there…

Hi Bo?tjan, tx for yr reply – I’ve updated tmhOAuth by pasting the current v0.7.5 files into twitget/lib, including cacert.pem, but no such luck…

the extended debug output is here: https://gist.github.com/ptim/d99c5b0117274b5d91ba

And here is the code I’m using to debug:
https://gist.github.com/ptim/5569544

i have to crash.. working in just a few hours, tx again

I still can’t get round this one. Have you had any luck?

no luck so far Bo?tjan :/

I’m still searching for a solution – twitget is one of three solutions failing on this server ??

Hey memelab, you still there?

Is there any way you can test something for me on your server that’s behind a proxy?

Cheers.

Hi, Bo?tjan

I am having the same problem in 2 websites. I am getting “Twitter outputted an error”.
Using WP version 3.5.2 and Twitget 3.0.
Before upgrade the plugin it is working fine.

One of the websites using it:

https://ipsilondesign.com.br/ (second footer box, between “ultimas noticias” and Vimeo)

Thank you in advance!
Aleph

Hello aozuas,

Are you using any characters that are unicode in your Twitter stream? I’m fixing this issue currently and will commit it in version 3.1.

Update (when it is available) and try it then.

Hey guys!
Any sollution on this?
It was working fine till yesterday, now I notice it dropped.

Not trying to hijack the thread or anything – just adding abit of my knowledge:
“I understand that we’re explicitly setting curl_ssl_verifypeer to false”
There’s no use to try any cacert.pem with above option set to false because it doesn`t matter.

sorry for disturbing – seems it was a temporary error for me – all back to normal now ??

Once again, here’s another thread marked ‘resolved’ that doesn’t appear to be from the posts above – if there was a fix, PLEASE post it so that those of us who are having the same “twitter outputted an error” problem can also find the solution, not just a vague unresolved thread that’s been erroneously marked resolved.