My twitter login stopped working since July! Is my server blocked?

login

#1

My twitter login stopped working since July! Can someone help me spot what is wrong? Is my server IP blocked?

Below is part of the dump that I see

object(TwitterOAuth)#38 (14) {
[“http_code”]=>
int(403)
[“url”]=>
string(336) “https://api.twitter.com/oauth/request_token?oauth_callback=https%3A%2F%2Fwww.meritmeter.com%2Fusers%2Ftwitter_process&oauth_consumer_key=xxxxx0&oauth_signature=xxxo%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=xxx&oauth_version=1.0
[“host”]=>
string(28) “https://api.twitter.com/1.1/
[“timeout”]=>
int(30)
[“connecttimeout”]=>
int(30)
[“ssl_verifypeer”]=>
bool(false)
[“format”]=>
string(4) “json”
[“decode_json”]=>
bool(true)
[“http_info”]=>
array(23) {
[“url”]=>
string(336) “https://api.twitter.com/oauth/request_token?oauth_callback=https%3A%2F%2Fwww.meritmeter.com%2Fusers%2Ftwitter_process&oauth_consumer_key=xxxx&oauth_signature=xxxx%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=xxx&oauth_version=1.0
[“content_type”]=>
string(29) “application/xml;charset=utf-8”
[“http_code”]=>
int(403)
[“header_size”]=>
int(968)
[“request_size”]=>
int(405)
[“filetime”]=>
int(-1)
[“ssl_verify_result”]=>
int(0)
[“redirect_count”]=>
int(0)
[“total_time”]=>
float(0.286006)
[“namelookup_time”]=>
float(0.03426)
[“connect_time”]=>
float(0.065566)
[“pretransfer_time”]=>
float(0.238211)
[“size_upload”]=>
float(0)
[“size_download”]=>
float(203)
[“speed_download”]=>
float(709)
[“speed_upload”]=>
float(0)
[“download_content_length”]=>
float(203)
[“upload_content_length”]=>
float(0)
[“starttransfer_time”]=>
float(0.285977)
[“redirect_time”]=>
float(0)
[“redirect_url”]=>
string(0) “”
[“primary_ip”]=>
string(13) “104.244.42.66”
[“certinfo”]=>
array(0) {
}
}
[“useragent”]=>
string(25) “TwitterOAuth v0.2.0-beta2”
[“sha1_method”]=>
object(OAuthSignatureMethod_HMAC_SHA1)#39 (0) {
}
[“consumer”]=>
object(OAuthConsumer)#40 (3) {
[“key”]=>
string(25) “xxxx”
[“secret”]=>
string(50) “xxxx”
[“callback_url”]=>
NULL
}
[“token”]=>
object(OAuthConsumer)#41 (3) {
[“key”]=>
NULL
[“secret”]=>
NULL
[“callback_url”]=>
NULL
}
[“http_header”]=>
array(20) {
[“cache_control”]=>
string(62) “no-cache, no-store, must-revalidate, pre-check=0, post-check=0”
[“content_length”]=>
string(3) “203”
[“content_type”]=>
string(29) “application/xml;charset=utf-8”
[“date”]=>
string(29) “Thu, 29 Nov 2018 18:08:44 GMT”
[“expires”]=>
string(29) “Tue, 31 Mar 1981 05:00:00 GMT”
[“last_modified”]=>
string(29) “Thu, 29 Nov 2018 18:08:44 GMT”
[“ml”]=>
string(1) “A”
[“pragma”]=>
string(8) “no-cache”
[“server”]=>
string(5) “tsa_b”
[“set_cookie”]=>
string(100) “guest_id=xxxxx; Expires=Sat, 28 Nov 2020 18:08:44 GMT; Path=/; Domain=.twitter.com
[“status”]=>
string(13) “403 Forbidden”
[“strict_transport_security”]=>
string(17) “max-age=631138519”
[“x_connection_hash”]=>
string(32) “xxxx”
[“x_content_type_options”]=>
string(7) “nosniff”
[“x_frame_options”]=>
string(10) “SAMEORIGIN”
[“x_response_time”]=>
string(2) “15”
[“x_transaction”]=>
string(16) “xxx”
[“x_twitter_response_tags”]=>
string(16) “BouncerCompliant”
[“x_ua_compatible”]=>
string(16) “IE=edge,chrome=1”
[“x_xss_protection”]=>
string(54) “1; mode=block; report=https://twitter.com/i/xss_report”
}
}


#2

Can’t tell anything from your dump, but there was this change in June, perhaps that’s your issue?


#3

Thanks @Connexinet

@danix4u - I suggest for you to read through our doc on callback urls