Skip to content

Connection problems

If something fails when connecting a service, look for what you see in the first column.

What you see What happened What to do
redirect_uri_mismatch (Google) or redirect_uri did not match (Slack) The callback URL is missing in the app, or was added a moment ago Check the callback URL in Organization → Connectors. Google can take a few minutes to apply it
invalid_client when authorizing The Client ID or the secret aren’t from the same app, or the secret was deleted in the provider Paste the pair again in nouter
The redirect_uri is not associated with this application (GitHub) The OAuth App’s callback URL is from another workspace Use an OAuth App with this workspace’s callback URL
redirect_uri_mismatch on a Salesforce page The callback URL isn’t in the app, or was added less than 10 minutes ago Check it and wait about 10 minutes. Start a new connection
Salesforce error when authorizing (app not found or no access) The Consumer Key is mistyped, or the user isn’t enabled in the app’s policies Check the Key in nouter and Permitted users in Salesforce
“Couldn’t set it up” on the connector’s row The workspace update failed, or the saved secret can’t be read anymore Save again (and paste the secret if it asks)
“Needs setup” doesn’t change Less than 30 seconds passed since you saved Wait half a minute; if it stays, save again

Your connectors are in Customize → Connectors: the Yours tab shows the ones you already connected, and Discover is the catalog to add a new one.

What you see What happened What to do
The service doesn’t appear under Discover An admin hasn’t loaded your company’s app Ask the admin to set it up (Managing connectors)
“Could not connect … Dynamic Client Registration rejected” The custom MCP server doesn’t accept automatic registration, or doesn’t have nouter’s callback URL in its whitelist The admin edits it and loads the OAuth client (Adding custom MCP servers)
A Google resource fails when used (say, Chat) The API isn’t enabled in your company’s Google project The admin enables it, or turns that resource type off
After changing the Salesforce Key, one person’s connection fails Their account had the old Key Reconnect: the new connection takes the new Key
A connector says “Everyone will have to connect it again” The admin changed the URL or the Client ID Reconnect the service