EkDrishti logoEkDrishti

DSC Signer Not Detecting Your Token? A Complete Fix Checklist

Driver order, browser trust settings, the emSigner/epass service, and the exact sequence that makes IREPS and eProcurement portals detect your digital signature certificate.

Last updated: 2 August 2026

USB digital signature token connected to a laptop with a security certificate icon

A digital signature token that worked yesterday and refuses to appear today is almost always a service, driver or browser-trust problem — not a faulty token. Work through the checklist below in order; stop as soon as the portal lists your certificate.

1. Confirm the token is seen by Windows first

Before blaming the portal, verify the operating system can read the token. If the token utility cannot list the certificate, no browser will.

  1. Plug the token directly into a rear USB port — avoid hubs and extension cables.
  2. Open the token utility (ePass2003 Token Manager, ProxKey Utility, mToken, WD Manager as applicable).
  3. Click Login, enter the token PIN and confirm the certificate is listed with a valid expiry date.
  4. If the utility shows nothing, reinstall the driver supplied by the token vendor and reboot.

2. Install drivers in the correct order

Mixed drivers from two vendors are the single most common cause of detection failure. Remove everything, then install only what you need.

  1. Control Panel → Programs → uninstall all old token drivers and signer utilities.
  2. Reboot the machine (this releases locked smart-card services).
  3. Install the driver for your current token vendor only.
  4. Install the signer application (emSigner / NIC Signer / portal-specific signer) afterwards, never before.

3. Make sure the signer service is actually running

Signer utilities run a small local service, usually on 127.0.0.1 with a fixed port. The portal talks to that service over HTTPS.

  1. Look for the signer icon in the system tray; if absent, launch it manually as Administrator.
  2. Open Task Manager → Services and confirm the signer / smart card service shows Running.
  3. In the browser open the local signer address the utility prints (for example https://127.0.0.1:<port>) and accept the self-signed certificate once.
  4. Return to the portal and refresh the page.

4. Browser trust and compatibility settings

Modern browsers block the local signer connection until its self-signed certificate is trusted. Chrome and Edge behave slightly differently.

  1. Allow the localhost certificate exception once, then restart the browser completely.
  2. Add the portal domain to trusted sites in Internet Options → Security.
  3. Disable aggressive antivirus HTTPS scanning temporarily to test — it frequently intercepts the localhost handshake.
  4. Try an InPrivate / Incognito window with extensions disabled.

5. Still not detected?

Test the token on a second machine. If it works there, the problem is local configuration; if it fails on both, the certificate may be expired, revoked or the token locked after repeated wrong PIN attempts. Contact the issuing Certifying Authority in that case.

This article is informational guidance from personal experience and is not an official instruction from any department.

Informational guidance only — not official instructions from RDSO, Indian Railways or NIC. See our disclaimer. Back to all articles