Getting ETIMEDOUT error on login

I have started getting the following error message on every login attempt:

{"error":"access_denied","error_description":"Error: ETIMEDOUT"}

I am using angular-auth0: "^3.0.0" to directly call angularAuth0.client.login(...).

This behaviour seems to have only started happening because I just migrated the whole underlying web application from one AWS service to another (from just an EC2 to an ECS). This involved changing the Route 53 DNS pointers to point to the new underlying system.

However, the actual host name of the application has not changed, so I am not sure how this has affected Auth0 at all.

Looking for pointers.

Here is the redacted error

{
  "date": "2020-11-13T19:53:48.137Z",
  "type": "fepft",
  "description": "Error: ETIMEDOUT",
  "connection": "Username-Password-Authentication",
  "connection_id": "xxx",
  "client_id": "xxx",
  "client_name": "XXX",
  "ip": "xxx",
  "client_ip": "xxx",
  "user_agent": "Chrome 86.0.4240 / Mac OS X 10.15.7",
  "hostname": "xxx",
  "user_id": "",
  "user_name": "xxx",
  "audience": "xxx",
  "scope": "openid offline_access",
  "auth0_client": {
    "name": "angular-auth0",
    "version": "3.0.6",
    "env": {
      "auth0-js": "9.14.0",
      "auth0.js": "9.14.0"
    }
  },
  "log_id": "90020201113195349102000076982296181365863559863451254834",
  "_id": "90020201113195349102000076982296181365863559863451254834",
  "isMobile": false
}

Never mind, the problem was with a rule on the tenant that was using the wrong URL.