After upgrading to ServiceStack to 4.0.24.0, I started receiving this below error when trying to login using Google OAuth.

[vijaysirigiri]

The same works locally on my dev machine. Has anything changed since the 4.0.21.0?

--The site is hosted on Azure as you can see from the address bar. --I've the licensed version of SS --Google OAuth Callback url is correctly registered http://somesite.azurewebsites.net/auth/GoogleOAuth --Using ServiceStack.Authentication.OAuth2 4.0.24.0

[mythz]

A 502 Gateway error says that an upstream server had a problem, unfortunately this doesn't provide any info on what the error is or which server it was. Can you provide any error logs from Azure about what the error is?

I've tested Google OAuth2 both locally and when deployed on AWS at: https://httpbenchmarks.servicestack.net with the latest version of ServiceStack, and they're both working as before.

[vijaysirigiri]

Yes. I could not find any info in the failed trace logs. I'll attach the logs for your reference. Thanks!

On Fri, Aug 8, 2014 at 12:18 AM, Demis Bellot notifications@github.com wrote:

A 502 Gateway error says that an upstream server had a problem, this doesn't provide any info on what the error is or which server it was. Can you provide any error logs from Azure about what the error is?

I've tested Google OAuth2 and it's still working both locally and when deployed on AWS: https://httpbenchmarks.servicestack.net with the latest version of ServiceStack and they're both working as before.

— Reply to this email directly or view it on GitHub https://github.com/ServiceStack/Issues/issues/124#issuecomment-51514792.

Vijay Sirigiri.

[malat]

Hi, Its probably a transient error, on Azure you need to have some retry policy ....

http://www.asp.net/aspnet/overview/developing-apps-with-windows-azure/building-real-world-cloud-apps-with-windows-azure/transient-fault-handling

[mythz]

need more info to be able to continue on this.

[Formator]

Hi guys,

We are having the same issue here and it has to do with IIS integrated pipeline mode. When switching to classic mode GoogleOAuth works.

Now, in our situation we need to be running in integrated mode as there are advantages and plus we want to run run SignalR! It would be a bummer if ServiceStack that we carefully selected as our platform technology simply fails on this point.

I would consider this an important issue, or we are simply overlooking something and would really appreciate any help resolving it.

Thanks

[mythz]

@Formator Please open a new issue with a link to stand-alone project that can be run locally to repro the issue.

[Formator]

@mythz Thank you for your replay, I will setup new project to reproduce this error on Azure, because it can't be reproduce on local.