Sean, I was just able to log into TweetPhoto using my basic auth credentials with no problem. Please test again and provide any of the additional details that you can:
*Copying from Alex email to make sure its consistent 1. The IP of the machine making requests to the Twitter API. If you're behind NAT, please be sure to send us your *external* IP. 2. The IP address of the machine you're contacting in the Twitter cluster. You can find this on UNIX machines via the "host" or "nslookup" commands, and on Windows machines via the nslookup" command. 3. The Twitter API URL (method) you're requesting and any other details about the request (GET vs. POST, parameters, headers, etc.). 4. Your host operating system, browser (including version), relevant cookies, and any other pertinent information about your environment. 5. What kind of network connection you have and from which provider, and what kind of network connectivity devices you're using. </copy> Best, Ryan On Mon, Aug 17, 2009 at 3:33 PM, Sean Callahan<[email protected]> wrote: > Hi Ryan, > > I just replied to your email and also will post here in case you read > this first. Maybe others will have an idea too as why basic auth is > not working. Long story short - we were down for 3 days, up for the > last 3 hours, and now down once again - no one can login using basic > auth on our site http://tweetphoto.com. > > It so happens when I responded to your email about 3 hours ago > everything was working fine - meaning I was able to login to > TweetPhoto as were other users. Since replying to your second email > basic authentication on http://tweetphoto.com is not working an no one > can login to their account on our domain. > > I'm not sure why basic auth is not working when you said only OAuth > should have been affected. With that said, I have an idea as I've > spoken to a few Rackspace customers. Is it possible that a range of > IPs at Rackspace are being blocked/throttled preventing users from > logging in through basic auth? > > I'm not sure why basic authentication came back online this morning > and now it does not work. You asked me to respond to an email Alex > sent, but I have not seen that. Please let me know what information > you need to better troubleshoot this issue so we can resume service. > > As I mentioned in my email to you, I am willing to pay a monthly > service fee as I'm sure other Twitter Developers are, to keep service > running to TweetPhoto.com up 100% of the time. > > Please advise. > > Best Regards, > > Sean Callahan > > On Aug 16, 11:40 am, bosher <[email protected]> wrote: >> Thanks for the update Chad.. >> >> On Aug 16, 10:52 am, Chad Etzel <[email protected]> wrote: >> >> >> >> > Hi all, >> >> > The API team is actively debugging the OAuth issues as we speak. >> > Please be patient as we nail down the problems. >> >> > Thanks, >> > -Chad >> >> > On Sun, Aug 16, 2009 at 1:43 PM, Andrew Badera<[email protected]> wrote: >> >> > > On Sun, Aug 16, 2009 at 1:40 PM, bosher<[email protected]> wrote: >> >> > >> How is it that all the oAuth apps out there are down, but others like >> > >> TweetMeMe are not? TweetMeMe works just fine, how is that possible? >> >> > > HTTP Basic Auth still works I believe, as do any pre-problem OAuth >> > > tokens issued. >> >> > > ∞ Andy Badera >> > > ∞ This email is: [ ] bloggable [x] ask first [ ] private >> > > ∞ Google >> > > me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)- Hide >> > > quoted text - >> >> - Show quoted text - >
