error fix
n8n OAuth Callback Error: Redirect URL Checklist
Copy the OAuth redirect URL from the n8n credential, add it exactly to the provider app, confirm HTTPS and public domain settings, then re-check scopes and credential type.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Copy the OAuth redirect URL from the n8n credential, add it exactly to the provider app, confirm HTTPS and public domain settings, then re-check scopes and credential type.
Problem Pattern
OAuth callback errors usually happen when the app provider has a redirect URL that does not exactly match n8n's callback URL, or when self-hosted public URL and proxy settings are wrong.
Key Facts
- Redirect dependency
- OAuth apps must send the user back to the redirect URL expected by n8n.
- Credential context
- HTTP Request credentials support OAuth2 for services that use it.
- Provider-specific
- Google, Linear, and other services each have their own OAuth app settings and scopes.
- Self-hosted risk
- Wrong public URL or reverse proxy configuration can produce an unusable callback URL.
Recommended Steps
- Open the failing n8n credential and copy the OAuth redirect or callback URL shown by n8n.
- Paste that exact URL into the provider's OAuth app settings.
- Confirm the public domain, HTTPS, and reverse proxy route reach the n8n instance.
- Check required scopes and whether the provider expects a single-service or generic OAuth credential.
- Reconnect the credential from n8n and test a low-risk read operation.
Verification
- The OAuth provider accepts the exact n8n callback URL.
- The browser returns to n8n after authorization.
- The credential test or a low-risk node operation succeeds.
- The callback URL uses the intended public HTTPS domain.
Warnings
- Do not manually guess the callback URL when n8n displays one in the credential setup.
- Changing public domain or proxy settings can break existing OAuth credentials.
- A successful OAuth login can still fail later if scopes are missing for the node operation.
Common Mistakes
- Using localhost in a provider OAuth app for a public self-hosted instance.
- Copying only the domain and not the full callback path.
- Missing required scopes for the selected node operation.
- Changing WEBHOOK_URL or public domain after creating credentials.
Examples
n8n displayed callback URL: copied exactly
Provider app redirect URI: exact match
Public domain uses HTTPS: yes
Reverse proxy reaches n8n: yes
Scopes cover operation: yes
Credential reconnect succeeds: yesFAQ
Why does OAuth work on n8n Cloud but not self-hosted?
Self-hosted instances must expose a correct public HTTPS URL and configure the provider app with the exact callback URL.
Is this a credential password problem?
Usually no. OAuth callback errors are more often redirect URL, domain, proxy, or scope configuration problems.