Google OAuth2 sign ins suddenly stopped working

582 views
Skip to first unread message

Angelo Borsoi Ross

unread,
Nov 4, 2020, 9:17:20 AM11/4/20
to Google Cloud Developers

This one is a weird one.

I had setup an internal network with a few applications, including a self hosted instance of Gitlab and WikiJS. Where I could, I also setup Google Sign in so my users could just use their regular Google Workspace account.

The project is marked as internal and everything was working for about a month. Then, suddenly, none of those services could use Google Sign In anymore. WikiJS just complains about not being able to get a token while GitLab gives a "Execution Expired" error. It should be noted that anyone already logged in can keep working normally, but I have to guess that when that OAuth token expires they will have the same issue.

The OAuth consent screen only shows an unhelpful "There are currently service interruptions, and quota information cannot be provided." (this may not be a 100% correct translation). Other projects also have a similar message, but they still seem to be working fine.

We thought it may have been a billing issue, but even after adding the billing account (and it shows we have a 0.00 bill), nothing changes.

I can't see anything special on the project's logs and I can't imagine a bunch of services, running stably on docker images for a month, would all stop working at the same time, which means there's either an issue with my project I cannot diagnose or there's something weird going on with Google. Is there anything I can do to further investigate this problem? At this point I am out of ideas.

Este e-mail pode conter informação confidencial ou privilegiada, sendo seu sigilo protegido por lei. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não pode usar, copiar ou divulgar as informações nela contidas ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor, avise imediatamente ao remetente, respondendo o e-mail e em seguida apague-a. A Hi Technologies agradece sua cooperação.


This e-mail may contain confidential or privileged information and its confidentiality is protected by law. If you are not the addressed or authorized person to receive this message, you must not use, copy, disclose or take any action based on it or any information herein. If you have received this message by mistake, please advise the sender immediately by replying the e-mail and then deleting it. Hi Technologies thank you for your cooperation.

Elliott (Google Cloud Platform Support)

unread,
Nov 4, 2020, 4:54:45 PM11/4/20
to Google Cloud Developers
Hello,

I cannot find common issues at this time relating to OAuth. Perhaps the best way to move forward is to investigate your project. Maybe we can uncover something. Please open a Google issue Tracker, depending on the focus of your problem. We will assist you then as Google Groups is meant for general discussions.

Reply all
Reply to author
Forward
0 new messages