Common DSC errors: why signing fails, and how to fix it
A digital signature that will not sign is one of the most frustrating things in front of a filing deadline. The good news is that almost every DSC error comes down to one of a handful of causes — a driver, a utility, a browser or a PIN. Here is how to diagnose and fix each.
Typical reply within minutes during office hours.
What ₹0 gets you right now
A free eligibility check and an exact written quote — our fee and government fee shown separately. You decide after you see the numbers.
No pressure follow-ups. No commitments. Just clarity.
Almost every DSC error is one of four things
When a DSC "does not work", it feels mysterious, but the chain from token to portal is short, and problems live at one of four points along it: the token driver that lets your computer see the certificate, the portal signing utility that lets a government site use it, the browser that connects the two, and the token PIN that unlocks the signing. Work through them in that order and you will find the cause.
Nothing here requires deep technical skill — it is mostly installing the right piece of software and making sure it is running. This page is the diagnostic companion to our step-by-step DSC installation guide; if you are setting up for the first time, start there, and use this page when something specifically breaks. For the device at the centre of it all, see USB token explained.
"Token not detected" — the driver is almost always the cause
This is the most common error, and the fix is usually simple: the token's driver or middleware is not installed, not running, or is the wrong one. Your computer and browser can only see the certificate through that driver, so without it the token is invisible even though it is plugged in.
- Install the driver that matches your token model. Feitian ePass2003 uses the ePass2003 token manager; Watchdata ProxKey uses the ProxKey PKI client; other tokens have their own middleware. Using the wrong vendor's driver is a frequent trap.
- Reconnect the token after installing, ideally into a different USB port directly on the machine rather than through a hub.
- Check the token manager sees the certificate. Open the token utility — the certificate should be listed there. If it is, the token is fine and the problem is downstream.
- Rule out hardware. A failing USB port or cable can mimic a driver problem; try another port before assuming software.
Nine times out of ten, installing the correct driver and reconnecting the token brings it straight back to life.
The portal will not sign, even though the token is detected
Here the token driver is working, but the government portal's own signing utility is missing or outdated. Portals do not sign directly with the token driver — each has its own utility that does the signing:
| Portal | Signing utility |
|---|---|
| GST portal | emSigner |
| Income tax e-filing | emBridge / emsigner |
| MCA21 (V3) | MCA DSC utility |
| DGFT | eMudhra-provided utility |
The fixes are consistent: install the utility the portal specifies, make sure it is the current version, and confirm it is running — many utilities need to be open in the background for signing to work. If you renewed recently and signing suddenly fails, an outdated utility is a common culprit alongside the need to re-register the new certificate, which we cover in DSC renewal explained. Portal-specific setup is on our GST DSC and income tax DSC pages.
Browser-side failures
Signing utilities usually run a small local service on your computer that the browser talks to when you click "sign". Browser security settings and updates sometimes block that connection, which produces a signing failure that looks like a token problem but is not.
- Use the browser the portal recommends. Portals test against specific browsers; an untested one may not connect to the local signer.
- Allow the local signer service. When the browser asks whether to allow a connection to a local service or a specific port, permit it — that is the signing utility.
- Clear the cache and reload. A stale page can hold on to an old, failed connection state.
- Confirm the utility is actually running. If the background service has closed, the browser has nothing to connect to.
- Temporarily check security software. Aggressive antivirus or firewall settings can block the local port; a controlled check helps isolate the cause.
These browser issues are among the most common last-minute panics, and almost all of them come down to letting the browser reach the local signing service.
PIN lockouts and very old tokens
The token PIN protects your signing key, and it is deliberately unforgiving. Repeated wrong PIN attempts lock the token. Depending on the model, a locked user PIN can be reset using an administrator PIN through the token's management utility — but the admin attempts are also limited, and once they are exhausted the token can become permanently locked. Because the key is non-exportable, a permanently locked token means obtaining a fresh certificate on a new token.
Stop before you run out of attempts
If you are unsure of the PIN, do not keep guessing. Each wrong attempt brings the token closer to a permanent lock. Pause, find the correct PIN or the admin PIN, and use the token utility deliberately. A moment's caution here can save the cost and time of a whole new certificate.
Separately, a very old token can stop working after a renewal if its firmware does not support the newest certificate. Vendors publish token upgrade or CSP update tools for this; occasionally a very old device needs replacing. If you have just moved to a new computer and nothing signs, remember the driver and utility live on the machine, not the token — reinstall them and the certificate on the token works again.
What a fix can and cannot do
Many DSC problems are driver, utility or browser issues we can talk you through, and we regularly get a client's token detected and signing again the same day. But a genuinely locked token or an unsupported old device is not a "fix" situation — it needs a fresh certificate, and we will tell you that plainly rather than have you chase a repair that cannot work. Send us the exact error message and we will tell you which case you are in.
The bottom line
We built this page to be useful even if you never hire us. If you do, you get the same thing this page gave you — straight answers — plus a team that files, follows up and finishes. The quote is free and binding.
DSC error questions, answered plainly
Why is my DSC token not being detected?
Which driver do I need for my DSC token?
Why does the government portal not recognise my signature?
Why does my DSC not work in the browser?
What happens if I enter the wrong token PIN too many times?
My old token stopped working after I renewed — why?
Do I need to reinstall everything on a new computer?
Can you fix DSC errors remotely?
Stuck with a DSC error before a deadline?
Send us the exact error message and the portal you are on. We will help you get the token detected and signing again where it is a driver, utility or browser issue — and tell you honestly if it is a case that needs a fresh certificate. Fixed quote before any paid work begins.