> **Source:** https://knowledge.leegality.com/document-execution/nesl/error-troubleshooting > **Site:** Leegality Knowledge Base — https://knowledge.leegality.com > **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration. > **Navigation:** Every article on this site has a plain-text version at `.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt > **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt --- # NeSL Error Troubleshooting | Error Code | Description | Context | Recommended Action | | :---- | :---- | :---- | :---- | | **ER00P9** | We encountered a temporary issue while processing your request. This may be due to NeSL server downtime. | Temporary outage at NeSL’s end. | **Sender**: Use the **Retry** button on the Details Page after a few minutes. | | **ER00CP** | Your session expired—likely due to extended idle time or a network issue. | Session timeout on the signer’s side. | **Signer**: Reopen the signing link received via email, SMS, or WhatsApp to restart the process. | | **ER00P19** | The certificate configuration appears to be incorrect. | The certificate details stored in Leegality are not mapped correctly with NeSL. | **Sender**: Contact Leegality Support (support@leegality.com) to verify your certificate setup. Support will escalate to NeSL if required. | | **ER00J18** | Invalid PAN format. Ensure it matches the legal constitution (**e.g.**, 'P' for individuals). | PAN/legal constitution mismatch. | **Sender**: Validate PAN and legal constitution of the signer. Re-initiate the signing with corrected details. | | **ER00J101** | Incorrect eSign coordinates detected on the document. | The document is not A4-sized, or the sign coordinates are incorrectly configured. | **Sender**: Re-initiate the document with A4 page size and valid coordinates for all NeSL signers. | | **ER00E9** | Issue during eStamping. This is likely temporary. | Problem at the state eStamping portal (e.g., SHCIL). | **Sender**: Contact Leegality Support (support@leegality.com) | | **ER00E01** | eSign process failed due to a temporary issue with UIDAI. | UIDAI servers are intermittently unresponsive. | **Signer**: Retry after a few minutes. | | **ER00B01** | Insufficient stamp balance in your NeSL wallet. | The state-specific NeSL wallet lacks sufficient balance. | **Sender**: Contact NeSL to check and top up the relevant state account. | | **ER00ST** | Your session expired—likely due to inactivity or a network issue. | Session timeout while on NeSL Signing Pages. | **Signer**: Use the signing link to initiate the signing process. | | **ER00E13** | Maharashtra eStamping is not enabled for your organization. | Your organization isn’t onboarded for Maharashtra eStamping. | **Sender**: Complete onboarding using [this guide](https://nesl.co.in/wp-content/uploads/2023/09/Communique-92-Ease-of-onboarding-documentation-for-Maharashtra-paperless-10D-e-stamp-certificate.pdf). | | **ER500API** | Temporary system issue prevented request completion. | NeSL failed to respond to an API call. | **Sender**: Use the **Retry** button on the Details Page. **Signer:** Retry after some time. | | **ER502** | System issue encountered. Please retry. | NeSL’s systems are temporarily unavailable. | **Sender**: Use **Retry** on the Details Page. **Signer:** Retry after a few minutes. | | **ER00E04** | It appears the Aadhaar card used for signing doesn't have a linked mobile number or email ID. | Aadhaar is not linked with mobile number or email. | **Signer**: Retry using the correct Aadhaar number. | | **ER00J137 / ER00J176** | Duplicate loan number detected. | A previously used loan number is being reused. | **Sender**: Use a unique loan number to re-initiate the transaction. | | **ER00S8** | Duplicate transaction details. | Caused by refreshing the document multiple times. | **Sender**: Use the **Refresh Document** button only once. | | **ER00J1** | Invalid JSON structure. | Payload mismatch; often occurs in sandbox. | **Sender**: - Create a new transaction. - In case of recurrence, contact your tech team to extract payload and escalate to NeSL. - Include complete context: date, time, environment, sender name, transaction ID. | | **Internal server error** | Error on signing link click. | Occurs when F2F Signing is enabled. | **Sender**: Disable the **“Enable Leegality signing link for first invitee”** option under: _*Accounts > Department > eSignature > NeSL > Settings*._ | | **Internal Server Error** | General error during refresh or document creation. | Server/network issue at NeSL. | **Sender**: Retry the action (refresh or create). If the issue persists, escalate to NeSL. | | **ERR\_EMPTY\_RESPONSE** | Signer sees an unresponsive page when clicking the signing link. | NeSL sent a broken eSign URL with a `null` value. | **Sender**: Raise the issue with NeSL, referencing the `Get_Esign_Link` API’s invalid response. | | **ER00P1** - Response URL is Missing **ER00P2** - ClientID is Missing **ER00P3** - Authorization is Missing **ER00P4** - API key is Missing **ER00P5** -MetaData is Missing **ER00P7** - ResponseURL should not be null **ER00P8** - ClientID should not be null **ER00P9** - API-key and client should be valid **ER00P10** - MetaData should not be null **ER00P11** - API-Key should be Valid **ER00P12** - Authorization should not be null **ER00P13** - Invalid ClientID **ER00P14** - Unable to write JSON **ER00P15** - Invalid MetaData **ER00P17** or **ER00P16** - Invalid Authorization | Multiple API configuration errors (e.g., missing keys, metadata, etc.). | Either incorrect API setup or NeSL is experiencing issues. | **New Sender**: Verify API setup in Admin Panel. **Existing Sender:** Raise a ticket with NeSL confirming correct setup. | | **Max limit reached for Submitter Txn ID \+ Loan No.** | Limit exceeded (50) for Refresh API calls. | Too many refresh attempts for the same combination. | **Sender**: 1. Request limit increase from NeSL. 2. Instruct signers not to refresh excessively. 3. Retry once the cap is lifted. | | **Error 1: Successfully updated document** | Temporary issue that resolves automatically. | Minor, transient issue at NeSL’s end. | **Signer**: Retry after some time. |