OAuth login code failing when moved to AWS

oauth

#1

I have a standard set of Twitter user authentication scripts that I’ve been using for years based on Jaisen Mathai’s Twitter-async library. It has worked on every server I’ve tried up until an EC2 instance on AWS. When I get to the line where I get an authentication token, the code hangs:
$url = $twitterObj->getAuthorizeUrl(null, array(‘force_login’ => ‘false’));

I’m certain this is where it stops with nothing returned. The same set of code with the same application tokens works fine elsewhere. The only difference is running it on AWS. Any suggestions?


#2

Sounds very odd, since I’m aware of folks who run code that hit our API on AWS. The only thing I can think of is perhaps a network routing issue. Are there any lines of code that attempt to hit the Twitter API before that one?