Oauth2 API results in error 500

Questions
1

Hi community,

I am having trouble with connecting/securing my workflow via Oauth2. I am using n8n-cloud environment and have set up the redirect-URL properly, I tried it with trailing slash and without, I have tried it in different networks as well as with private mode/removed cookies - the error is always the same:

When I try to connect my account, I am being redirected to the suppliers page where I can consent/allow the access. After that I am being redirected to the page…

https://mycompany.app.n8n.cloud/rest/oauth2-credential/callback?code=XYZ

… where “mycompany” is pointing to my cloud-instance correctly.

The result is a white page stating

  • Error: Request failed with status code 500
  • More details
  • Failed to connect. The window can be closed now.

… and the “more details” section is empty.

I don’t know if it is worth to mention that I am still on trial-plan, it would be pretty odd if this was the reason. However, using Postman for exactly the same connection is succesful right away.

What could be the reason for this behaviour, has anybody experienced something similar? For me it looks like this is a problem related to n8n-cloud environment?

If anyone is interested in the API-supplier documentation:
Erste Developer Portal

Thanks in advance for any hint…
_j_

2

It may not be the issue, but sometimes when copying from the OAuth2 provider and into n8n, I would accidentally add a space as the first character.

If postman is working, it could be something similar; n8n will not lock this because of a trial

3

Thanks for the idea, just double-checked everything, but I dont see any blanks or other typos…

4

Hi,
any other ideas or any workarounds possible? Thank you in advcance!

5

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