The OAuth 2.0 callback URL appears to be timing out when adding a credential to our n8n instance, running from a Docker image via AWS ECS in Fargate.
For example, when attempting to connect to Microsoft/Azure via OAuth 2.0, after inputting the correct authorization and token URL’s; the client ID and secret; and the scope, as well as authorizing the callback URL listed in the Azure App Registration, the pop-up window meant to consent to access is blank and hangs until finally indicating that the connection timed out.
When the callback URL is deauthorized in the Azure App Registration, it will go through the consent process before indicating that the callback URL was not authorized.
The same procedure was previously done on n8n Desktop, and was successful.
There is initially no error message but just a white screen. After the pop-up window meant to consent to access hangs for about 30 seconds, it is replaced with:
Hmmm… can’t reach this page
n8n.[domain].comtook too long to respond
- n8n version: 0.220.1
- Database you’re using: SQLite
- Running n8n via: Docker, on AWS ECS Cluster