Auth0 Support Center - Error "There was an error. Please try again later. That’s all we know" Seen when Using the Google-Oauth2 Connection with Google Production Keys

Error "There was an error. Please try again later. That’s all we know" Seen when Using the Google-Oauth2 Connection with Google Production Keys

Sep 10, 2025

Overview

Users are seeing a 500 error message when using the Google Social Connection to login. The 500 error message is from the Google /signin/oauth/consent/ endpoint. The client is using their own Google Production keys for this connection.

Applies To

Google Social Connection

Cause

The status of the Google app in use is not "In Production". If the Google app is pending verification from Google, then this app will also not be available to external users. Read more about the publishing and verification statuses here.

Solution

Implementation of the Google Social connection should follow this guide. Confirm that the consent page has been published for External users or only users belonging to a Google Workspace will be able to consent. The same also goes for the Testing publishing status as this would mean only Google Test users would have access to this app. If a custom image has been added to the Google app, make sure that the status of the app is not "Ready for verification". Google must first verify the app for this app to be available for External users. Since the verification process can take weeks, here is a simple workaround:

Leave the current project as is so that the verification process can proceed.
From the top left dropdown, create a new project and go through the setup process again, this time without adding the custom logo.
Update the Google Social Connection with the new client_id and client_secret. Once the original app has been verified, the client credentials can be modified.