When encountering the error “Error in establishing connection with traces WebSocket e-Signer,” it is usually due to improper setup of the Digital Signature Certificate (DSC) environment or configuration issues with the e-Signer software. Here is a step-by-step guide to resolve the issue.

Steps to Resolve the Connection Issue

1. Download the Latest EMSIGNER from the TRACES Website

Ensure you have the latest version of the EMSIGNER software from the official TRACES website. Always download software from authentic sources to avoid compatibility or security issues.

2. Install DSC Software

Install the DSC software for signing certificates. Follow the installation steps provided with the software package.

3. Install the Latest Java Version

• Visit Java’s Official Website and download the latest version.
• Uninstall any older versions of Java that might be installed on your system. This avoids conflicts between versions.

4. Configure Google Chrome for JavaScript

1. Open Google Chrome.
2. Navigate to Settings > Security and Privacy > Site Settings > JavaScript.
3. Enable the option: Sites can use JavaScript.
4. Under the "Allowed to use JavaScript" section, add the following URLs:
   http://120.0.0.1:1565

   http://120.0.0.1

   https://127.0.0.1:1585

   http://127.0.0.1:1585

   http://127.0.0.1

   https://127.0.0.1

5. Update the Java Security Settings

1. Open the Java Control Panel:
   • On Windows, search for "Configure Java" in the Start Menu.
   • On macOS, find it in System Preferences.
2. Go to the Security tab.
3. Click on Edit Site List under Exception Site List.
4. Add the following URLs to the list:
   http://120.0.0.1:1565

   http://120.0.0.1

   https://127.0.0.1:1585

   http://127.0.0.1:1585

   http://127.0.0.1

   https://127.0.0.1
5. Save the changes and close the Java Control Panel.

6. Restart Your System

After making the changes, restart your computer to ensure all configurations take effect.

Testing the Setup

1. Open the EMSIGNER application and ensure it is running.
2. Navigate to the TRACES website in Google Chrome.
3. Try signing documents with the DSC. If configured correctly, the error should no longer appear.