# Problems using Lock Widget (Preflight CORS and 404s)

**URL:** <https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314>\
**Category:** Get Help\
**Tags:** lockjs, lock-inline, lock-modal, lock\
**Created:** [January 27, 2018, 4:56am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314 "2018-01-27T04:56:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![srees](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@srees](https://community.auth0.com/u/srees)\
**Post date:** [January 27, 2018, 4:56am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314/1 "2018-01-27T04:56:27Z")

</div>

I’m using the Lock Widget on a custom page. I’ve added [mydomain].org to the Allowed Web Origins for my client.vHowever I’m getting the following console error when attempting to login with a username and password:

`Failed to load https://[mytentantid].auth0.com/usernamepassword/login: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://[mydomain].org' is therefore not allowed access.`

I am also getting 404’s for the following url at initial load of the page:  
https://[mytenantid].auth0.com/user/ssodata/

Thank you in advance for your help.

---

<div class="post-metadata">

**Author:** ![JG\_Coding](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jg_coding/32/19861_2.png) [@JG\_Coding](https://community.auth0.com/u/JG_Coding)\
**Post date:** [February 2, 2018, 1:35am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314/2 "2018-02-02T01:35:16Z")

</div>

I am experiencing the same issue, same error. I am getting this with localhost:8080 and that has been in my CORS list for many months.

---

<div class="post-metadata">

**Author:** ![JG\_Coding](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jg_coding/32/19861_2.png) [@JG\_Coding](https://community.auth0.com/u/JG_Coding)\
**Post date:** [February 2, 2018, 1:42am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314/3 "2018-02-02T01:42:53Z")

</div>

UPDATE: Just like that, everything is fine. jeez!

---

<div class="post-metadata">

**Author:** ![srees](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@srees](https://community.auth0.com/u/srees)\
**Post date:** [February 2, 2018, 4:48am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314/4 "2018-02-02T04:48:39Z")

</div>

For me it ended up being the version of lock I was using. I upgraded from version 10 (apparently the default when pulling ‘auth-lock’ from npm) to version 11, and my errors went away. Hope this helps someone else.

---

<div class="post-metadata">

**Author:** ![JG\_Coding](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jg_coding/32/19861_2.png) [@JG\_Coding](https://community.auth0.com/u/JG_Coding)\
**Post date:** [February 2, 2018, 5:37am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314/5 "2018-02-02T05:37:00Z")

</div>

thanks for the response! My issue apparently “self-corrected”. The issue persisted for an hour or so and then just worked. I likely do need to upgrade though.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [July 25, 2019, 9:54am UTC](https://community.auth0.com/t/problems-using-lock-widget-preflight-cors-and-404s/9314/6 "2019-07-25T09:54:11Z")

</div>


