🛑 Limited Mode
Limited Mode may appear in rare cases on sites protected by DataUnlocker, typically due to network issues.
This screen does not appear during normal browsing, even if VPN, network or ad blockers are enabled. Limited Mode may show up in rare cases when blocker software explicitly attempts to bypass DataUnlocker Defender itself, or due to tech or network glitches.
What can I do?
Try disabling your blocker software or adding the website or web app to exceptions.
Error codes
If you're a developer or webmaster, the following error codes table can help you to identify the specific issue why DataUnlocker Defender isn't happy with your session.
| Code | Description |
|---|---|
1-11 | Low-level cryptography errors Various errors related to low-level cryptography used by DataUnlocker Defender. |
31 | Unable to load the DataUnlocker Defender dynamic script Regardless of the setup, DataUnlocker Defender requests a cryptographic proof and its configuration via the transport endpoint. It appears as a call to a script resource type. If this request fails, the web app won't start. |
32 | DataUnlocker Defender dynamic script load timeout Regardless of the setup, DataUnlocker Defender requests a cryptographic proof of the network connection and its configuration via the transport endpoint. This error means the request wasn't completed within the reasonable timeout. |
33 | DataUnlocker Defender bridge connection has been already attempted DataUnlocker uses a bridge protocol to establish connection between its "bundled" and "dynamic" scripts. This error means that the bridge connection was already attempted, for example, if you installed DataUnlocker Defender multiple times. |
34 | Unexpected DataUnlocker Defender bridge connection issue DataUnlocker uses a bridge protocol to establish connection between its "bundled" and "dynamic" scripts. This error means that the bridge connection didn't work out as expected. |
35-40 | DataUnlocker Defender bridge communication error DataUnlocker uses a bridge protocol to establish connection between its "bundled" and "dynamic" scripts. These errors signal that there's a problem in communication:
|
41 | DataUnlocker Defender bridge connector missing DataUnlocker uses a bridge protocol to establish connection between its "bundled" and "dynamic" scripts. This error means inability to establish the bridge connection as no connector was exposed. |
42 | DataUnlocker Defender bridge connection failure DataUnlocker uses a bridge protocol to establish connection between its "bundled" and "dynamic" scripts. This error signals that the bridge connection was attempted but failed. |
43-47 | DataUnlocker Defender bridge serialization errors DataUnlocker uses a bridge protocol to establish connection between its "bundled" and "dynamic" scripts. These errors signal that there's a problem in serializing or deserializing encrypted data passed through the bridge:
|
61 | Dynamic Defender's script is expired DataUnlocker Defender requested a dynamic script which is expired. It may happen if blockers attempt to stub the script. Mind checking your transport endpoint health check as well. |
62 | Dynamic Defender's script public key mismatch DataUnlocker Defender requested a dynamic script which includes the invalid public key. It may happen if blockers attempt to stub the script, or wrong proxy endpoint is used. Mind checking your transport endpoint health check as well. |
63 | Dynamic Defender's script signature is invalid DataUnlocker Defender requested a dynamic script which includes the invalid signature. It may happen if blockers attempt to stub the script, or wrong proxy endpoint is used. Mind checking your transport endpoint health check as well. |
80 | The first transport endpoint request loading problem or timeout Defender's code in the patched JS file wasn't able to load the served Defender script on your transport endpoint in time, most likely due to the network error or the transport endpoint being blocked. Try opening the Network tab in dev tools and see if the first request to your transport endpoint succeeds. Try to figure out why it doesn't. |
81 | The clock is desynchronized DataUnlocker Defender validates that This error code means that DataUnlocker Defender has detected the clock desynchronization. |
91 | Dynamic Defender's script init failure DataUnlocker Defender requested a dynamic script which failed to initialize. |
92 | DataUnlocker Defender was health checked during this session DataUnlocker Defender health check stops the web app once triggered. This is used only by DataUnlocker itself. |
93 | Secure enclave code invocation has failed This denotes errors during the secure enclave code invocation, typically, JavaScript errors in your code. |
94 | Delayed blocker detection error If DataUnlocker Defender notices the ad blocker after its initialization (after onload handler is invoked and the Secure Enclave code is executed), it would refresh the page. If something prevents the page refresh, users will observe this error. |
95 | End to end request validation failed DataUnlocker Defender validates some of its responses using cookies. If browser has cookies disabled, or there are network failures and cookie isn't delivered, this error will appear. Cookies are enabled in all browsers by default. Do not confuse this with the user's cookie consent you may see on websites: DataUnlocker doesn't use cookies to identify or distinct users, only to validate specific requests made via the network. |
96 | End to end request signature is invalid DataUnlocker Defender "signs" requests end to end and validates the server-generated signature delivered in the response with cookies to ensure all requests are genuine. If the signature is invalid, DataUnlocker Defender enables Limited Mode with code 96. |
97-98 | Challenges or self-checks failure DataUnlocker runs "challenges" and self-checks to ensure its integrity. The following error codes apply:
|