TRACES eMSigner Not Working in Chrome — Complete Fix Guide
TRACES eMSigner (by NSDL e-Governance) relies on a local Java service running on port 1585. Chrome’s security restrictions often block this. Here’s how to fix every common failure scenario.
Diagnosis Table
| Symptom | Likely Cause |
|---|---|
| eMSigner window doesn’t open | Java service not running |
| “Connection refused” on localhost:1585 | eMSigner utility not started |
| Extension grayed out / not detected | Chrome extension disabled or outdated |
| Mixed content blocked | Chrome blocking HTTP on HTTPS page |
| DSC not detected | Driver or token issue |
Fix 1 — Start the eMSigner Utility Manually
- Download the latest eMSigner setup from tdscpc.gov.in.
- Run
eMSigner.jaror the installed shortcut as Administrator. - Confirm the system tray icon appears and shows Service Running.
- Open Chrome and retry TRACES login.
Fix 2 — Install / Enable the Chrome Extension
- Open Chrome → address bar →
chrome://extensions. - Search for eMSigner extension. Enable it if it exists.
- If missing, install from the Chrome Web Store (search “NSDL eMSigner”).
- Reload the TRACES page.
🔌 Get eMSigner Chrome Extension
Also Read : Bell Error 2000: How to Fix Bell Internet & TV Error Code 2000
Fix 3 — Allow Insecure Content (localhost exception)
- In Chrome address bar go to:
chrome://flags/#unsafely-treat-insecure-origin-as-secure - Enter
http://localhost:1585in the text box. - Set the flag to Enabled and relaunch Chrome.
Fix 4 — Use Internet Explorer Mode in Edge
If Chrome continues to block the plugin, open Microsoft Edge, enable IE Mode in Settings → Default browser, then open the TRACES URL in IE Mode.
Fix 5 — Update Java & DSC Token Driver
- Download latest JRE from java.com/download.
- Reinstall your DSC USB token driver (ePass2003, WD, Gemalto etc.).
- Reboot and retry.
