Thank you pupi. So nice to see a reply from you :)
So, I suppose this is already fixed in Q2A1.8. I can wait for it. Actually I had disabled ipv6 on my server but when the login is via social-login, they are using ipv6 and hence the issue- is this correct?