Hello, No I haven't changed anything in the code wrt new relic, but it is really hard to pinpoint any other changes since it happened during a deploy to a staging environment after quite a bit of development. Either way, this is not the first time I have encountered weird net/http related problems surrounding the twitter auth callbacks, (like "no server/node given" even when it clearly is), so I'm not 100% sure new relic is the culprit. I will see it it stabilizes now and then do some more experiments. Thanks, Michel -- Posted via http://www.ruby-forum.com/.