# Error: An error occurred when fetching client data for Lock: https://cdn.auth0.com/client/redacted timed out

**URL:** <https://community.auth0.com/t/error-an-error-occurred-when-fetching-client-data-for-lock-https-cdn-auth0-com-client-redacted-timed-out/8935>\
**Category:** Get Help\
**Tags:** client, data, error, timeout-error\
**Created:** [December 10, 2017, 3:37pm UTC](https://community.auth0.com/t/error-an-error-occurred-when-fetching-client-data-for-lock-https-cdn-auth0-com-client-redacted-timed-out/8935 "2017-12-10T15:37:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ben.sarmiento](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@ben.sarmiento](https://community.auth0.com/u/ben.sarmiento)\
**Post date:** [December 10, 2017, 3:37pm UTC](https://community.auth0.com/t/error-an-error-occurred-when-fetching-client-data-for-lock-https-cdn-auth0-com-client-redacted-timed-out/8935/1 "2017-12-10T15:37:51Z")

</div>

A lot of our mobile users encounters a timeout error when accessing the URL. I checked it on my end and the URL is accessible. Is it possible for client data to have a fallback when a user encounters this error?

---

<div class="post-metadata">

**Author:** ![ben.sarmiento](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@ben.sarmiento](https://community.auth0.com/u/ben.sarmiento)\
**Post date:** [December 10, 2017, 3:39pm UTC](https://community.auth0.com/t/error-an-error-occurred-when-fetching-client-data-for-lock-https-cdn-auth0-com-client-redacted-timed-out/8935/2 "2017-12-10T15:39:02Z")

</div>

Another variation of this error:

Error: An error occurred when fetching client data for Lock: [https://cdn.auth0.com/client/redacted](https://cdn.auth0.com/client/redacted) **could not be loaded.**

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [December 11, 2017, 9:54pm UTC](https://community.auth0.com/t/error-an-error-occurred-when-fetching-client-data-for-lock-https-cdn-auth0-com-client-redacted-timed-out/8935/3 "2017-12-11T21:54:51Z")

</div>

To my knowledge, although the possibility to obtain that information from another source has been discussed it is not yet available so a failure to fetch that data is only recoverable by retrying until success.

The timeout value changed in Lock with [this PR](https://github.com/auth0/lock/pull/961) so I would make sure if you’re using a Lock version that already includes the increase in timeout as otherwise the probability of facing that issue would be significantly larger.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/error-an-error-occurred-when-fetching-client-data-for-lock-https-cdn-auth0-com-client-redacted-timed-out/8935/4 "2018-03-02T05:57:43Z")

</div>


