Failed by cors - correct client

I have a website (landing page) where people can sign up from. Sometimes when I check the dashboard logs, I see ‘failed by cors’ errors which is strange. I’m using the correct client-id (i’ve double checked many times) and it always says origin not allowed, then it lists something weird, instead of listing the allowed origins for the client, it says the following:

"allowedOrigins": [
      "https://manage.auth0.com",
      "https://auth0.com/docs",
      "https://login.auth0.com",
      "https://docs.auth0.com",
      "https://manage.auth0.com"
    ],

“originalUrl”: “/dbconnections/signup”

I’m having trouble figuring out what’s going on. I’ve tested the signup many times and it works (I’m not talking about local testing, I tested the actual landing page). And there are people that have signed up, but when do I see these failed by cors logs sometimes?

1 Like

Hi
I’m having the same problem. Did you manage to solve this @liquidsphere0?

Thanks!

1 Like

Yea the issue for me was that the page performing requests had ‘www’ as part of the URL, but the allowed origins only had naked urls (no ‘www’)

Not my case, but thanks anyway!