Error: “Not found when authorizing X” When Setting Up Credentials

Questions
1

Hi everyone, I’m encountering an issue while trying to authorize X credentials in n8n. After clicking the “Authorize App” button for a new credential (OAuth2-based), I get the following error:

“Not found”

image
image524×152 7.32 KB

Here’s some context:

  • The credential is for X
  • I’ve double-checked the client ID, secret, and scopes
  • The redirect URI seems correct: https://n8n-[xxxx].onrender.com/rest/oauth2-credential/callback (or n8n Cloud’s default)
  • I’ve tried refreshing the page, deleting/recreating the credential, and rechecking third-party app settings

Has anyone encountered this or have ideas for resolving it?
Would appreciate any help or direction — thanks in advance!

2

Hi @JR_Bao Welcome to n8n :n8n: community :tada:

Are you sure you filled out your app configuration something like this?

image
image480×809 23.8 KB

3

Yes, I’ve already tried several times — I even deleted and recreated the app, and updated the client ID and secret, but the issue still persists.

4

Hmm, did you also try revoking the app’s permission from the account?

image
image438×247 2.65 KB

Try deleting it and starting the process again.

I connected the app and tested it without any issues, so there must be something missing in your setup.

Also, are you sure the account isn’t suspended or rate-limited?

5

I also revoked the n8n app’s permissions and tried connecting again, but unfortunately, the problem is still there.

Just to add — the X account I’m trying to connect was only created last week, in case that’s relevant.

6

Hmm, did you try using an incognito window if you were signed in with more than one account?

7

Yes, I’m still encountering the same issue even after trying those steps.

Would you happen to have a step-by-step reference I could use to verify if I missed any part of the setup process?

8

For additional context, we’re using a Developer (Self-hosted) account, and our OAuth Redirect URL is set to:
https://n8n-[xxxx].onrender.com/rest/oauth2-credential/callback

9

Given that, I’d suggest testing with your main account just to confirm that you’ve configured everything correctly…

The required Client ID and Client Secret are the ones shown here.

image
image699×239 6.75 KB

I suspect the issue might be due to being signed in with multiple accounts…
Try signing out of all of them, including your developer account and X itself, then try again.

10

I’ve already tried that. Could the issue be related to the different OAuth Redirect URL we’re using? Ours is https://n8n-[xxxx].onrender.com/rest/oauth2-credential/callback, whereas the common redirect URL for n8n Cloud is typically https://oauth.n8n.cloud/oauth2/callback.

11

I use https://n8n.example.site/rest/oauth2-credential/callback without any issues…

12

This has been really tough to figure out, and I haven’t found any helpful answers so far. Is there a way to contact n8n support directly?

13

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.