How-to · DSC & GST portal

Your DSC just broke GST filing. Here's the fix for each of the ten documented problems

The short answer

A GST-portal DSC error usually matches one of ten problems the portal's own troubleshooting guide documents — a missing token, a dead emSigner server, a missing Java runtime, a non-PAN or unregistered certificate, or a browser refusing the local emSigner WebSocket are the common ones — each with its own fix. Rule 26 of the CGST Rules no longer requires a DSC of anyone — the proviso that once made it mandatory for company filers was omitted, along with every other proviso to the Rule, from 1 November 2021 (Notification 32/2021-Central Tax). So if your return-filing screen offers EVC (OTP-based), switching is often faster than debugging the DSC. The registration application is different — FORM GST REG-01's own instructions require companies and LLPs to sign it with a DSC. And a DSC failure on the return-filing side typically does not block e-invoicing/IRN generation, which runs through a separate system entirely.

Digital Signature Certificate errors on the GST portal all look the same from the outside — a dialog box, a red line, filing stuck — but the portal's own troubleshooting guide documents ten genuinely distinct causes, from a token that isn't plugged in to a WebSocket a browser refuses to open. Treating all ten as "the DSC is broken" wastes the most time. Here is the guide read scenario by scenario, plus two questions it doesn't answer: who actually has to use a DSC at all, and whether the same failure is quietly blocking your e-invoicing too.

Register or re-register the DSC before troubleshooting anything else

If filing has never worked with this certificate, start here rather than at the error message. Per the GST portal's own user guide, a DSC usable on the portal needs four things in place first: emSigner installed on the machine, the DSC vendor's own software installed, a hardware token (dongle) plugged in, and — this is where a working DSC still gets rejected — the certificate itself has to be PAN-based, Class II or Class III. The portal's guide is explicit: "The GST Portal accepts only PAN based Class II and III DSC." A non-PAN certificate, or a Class I certificate, will be refused here even if it works elsewhere.

To register or re-register: log in, click your name (top right) > My Profile, then Register/Update DSC under Quick Links. Attach the dongle and open the emSigner utility, select your PAN from the dropdown — it only lists PANs of authorised signatories, so if your own PAN isn't listed, that's a signatory-authorisation issue to fix before a certificate issue — pick the certificate in emSigner, and enter the certificate's password to confirm. That's the whole registration flow; nothing else needs touching unless one of the ten errors below shows up along the way.

The ten DSC/emSigner problems the portal's guide documents, and the fix for each

These ten are summarised from the GST portal's own troubleshooting reference, not a third-party guess at what each message means — though the guide states the error text and little else, so the Cause column below is partly our own inference from it. Eight of the ten are error messages; the other two cover first-time Mac setup and verifying the signature on your Registration Certificate. Match the exact wording first — several of these look alike at a glance but have unrelated fixes.

Error / symptomCauseFix
"Digital Signature Certificate Missing... Please plugin the token"DSC not installed, or token not plugged inInstall the DSC / plug in the token. Still failing with the token connected? Uninstall emSigner before installing any other version, then in that certificate's Details > Key Usage, confirm it reads "Digital Signature, Non-Repudiation" — if it instead reads "Key Encipherment," remove that specific certificate from the Windows certificate store
"Failed to establish connection to the server. Kindly restart the Emsigner"emSigner's local server isn't running, or is in a bad stateIf it's running, stop and restart it as Administrator. If it isn't running, start it as Administrator
"This application requires a Java Runtime Environment 1.6.0"No JRE installedClick OK and install the Java version from the page it redirects to
"PAN No verification failed, Please select the valid certificate to sign"The DSC's embedded PAN doesn't verifyEnter the correct PAN details, or confirm the correct PAN with the DSC vendor; re-select the right certificate
"Selected certificate is not a PAN based certificate..."Non-PAN-based DSCProcure a PAN-based Class 2 or Class 3 DSC (the guide's own wording), then register it (see above) — a non-PAN DSC cannot be made to work here
"The DSC you are trying to affix is not registered at the portal.."Valid DSC, never registered on this portal — including a newly issued or renewed certificate replacing an expired oneMy Profile > Register/Update DSC, and register it before filing. In practice, a renewed certificate is a new certificate as far as the portal is concerned and needs registering again from scratch, not just re-selecting
WebSocket won't open in the browser (Firefox especially)Browser hasn't accepted the local emSigner server's certificateOpen the emSigner URL (https://127.0.0.1:<port>) directly in the browser and add a security exception; confirm the port matches emSigner's. Running emSigner v1.2? Uninstall it via Programs and Features and install v2.6
An error appears after clicking PROCEED; WebSocket not visibleemSigner isn't actually runningClick the emSigner icon in the taskbar to confirm the WebSocket is open; if not, restart the emSigner server
Setting up emSigner on MacNot an error — first-time setupUninstall any existing emSigner, unzip the installer, then run ./startserver.sh from its folder in a terminal; a success message and a taskbar icon confirm it started
Registration Certificate (RC) PDF shows "Signature not Verified/Validity Unknown"The signer's certificate isn't in the PDF reader's trusted listIn the PDF reader, open the signature's properties, show the signer's certificate, add it under Trusted Identities (check every box), then re-verify. An RC generated before 21 June 2021 may still show "Validity Unknown" because the old trust certificate it relied on has since expired — that alone isn't a sign anything is wrong with the RC itself
These ten are the GST portal's own list, and none of them is specific to an expired certificate as such — if your DSC has genuinely expired, the practical path is the same as a fresh certificate: get it renewed or reissued by your Certifying Authority, then register the new certificate via Register/Update DSC above before trying to sign anything with it; a certificate the portal has never registered behaves identically whether it's brand new or a renewal of an old one. If an error doesn't match any of the ten documented causes — different wording, a code instead of a message — that may be coming from somewhere else: a WAF block or an expired API session, not the certificate. A near-identical problem shows up on the GST portal's separate API-access screen, with its own four unrelated causes.

Who actually has to use a DSC — and it's not what most guidance says

Before spending an afternoon on emSigner, it's worth checking whether a DSC is even the only option. Rule 26(1) of the CGST Rules sets the general rule: returns, applications and similar documents can be authenticated "with digital signature certificate or through e-signature... or verified by any other mode of signature or verification as notified by the Board" — EVC is one such Board-notified mode (Notification 6/2017-Central Tax, as amended by 11/2017-Central Tax). DSC, e-signature and EVC are co-equal options under Rule 26 itself — though, as the note below shows, a form's own instructions can still require a DSC for a particular application.

Rule 26 didn't always read this way. Until 1 November 2021 it carried a proviso making DSC mandatory specifically for "a registered person registered under the provisions of the Companies Act, 2013," with a string of dated, pandemic-era windows layered on top that briefly let such companies use EVC instead for GSTR-3B and GSTR-1 (2020, then again in April–May 2021, with the deadline twice pushed back). That proviso is gone, not just the temporary relief from it. Notification 32/2021-Central Tax, dated 29 August 2021, states plainly: "with effect from the 1st day of November, 2021, all the provisos shall be omitted." CBIC's consolidated Rule 26 still prints the old provisos, but inside brackets footnoted "Vide Notification No. 32/2021 - CT dated 29.08.2021 (w.e.f. 01.11.2021), all the provisos shall be omitted" — and it carries no replacement. As of 11 November 2026, Rule 26 itself mandates a DSC for nobody.

That's not the whole story, because Rule 26 isn't the only place a DSC gets required — and the clearest exception is written into the Rules themselves, not just a portal screen. The instructions to FORM GST REG-01, the registration application (as substituted by Notification 05/2026-Central Tax, in force from 1 November 2026), say an application filed by a private or public limited company, public sector undertaking, unlimited company, LLP, foreign company or foreign LLP "shall be signed digitally" with a "Digital Signature Certificate (DSC)- Class-2 and above". LLPs are named there even though they never were in Rule 26's old proviso, and GSTN's registration user guide says the same: "Digitally signing using DSC is mandatory in case of LLP and Companies." That guide also limits the Aadhaar e-Sign route for filing returns to taxpayers "other than companies / LLP," so don't count on e-Sign as a company's or LLP's fallback. For returns, GSTN's GSTR-3B filing guide offers "FILE GSTR-3B WITH DSC" and "FILE GSTR-3B WITH EVC" as parallel buttons with no restriction by constitution stated (both guides checked 11 November 2026). So a company or LLP registering needs a working DSC; one stuck on a DSC error while filing a return should check the screen in front of it for an EVC option before assuming none exists.

Practically: if a DSC is giving you trouble on a return and the screen in front of you offers EVC, the faster fix is often not fixing the DSC at all — switch to EVC and skip the token/emSigner/Java stack entirely.

Does a DSC failure also block your e-invoicing?

Usually not, and conflating the two wastes time looking in the wrong place. The return-filing DSC covered above authenticates documents you submit to the GST portal — GSTR-1, GSTR-3B, appeals. The invoice itself is covered by a separate rule: a proviso to Rule 46 of the CGST Rules (inserted by Notification 74/2018-Central Tax, before e-invoicing began) states that the supplier's signature or digital signature "shall not be required in the case of issuance of an electronic invoice in accordance with the provisions of the Information Technology Act, 2000". Generating the Invoice Reference Number (IRN) happens at an Invoice Registration Portal (IRP). GSTN's own e-invoicing overview describes onboarding there as "a one-time verification of the taxpayer's registered mobile number and email through an OTP", and says that on reporting the "IRP returns a signed e-Invoice" — the supplier's own DSC is not what's checked at either step.

Treat the IRP-side detail as the general pattern rather than a guarantee for every IRP/ASP-GSP combination and every screen: we could not independently re-verify the current state of the e-invoice portal's own DSC-related screen at einvoice1.gst.gov.in as of 11 November 2026 (it returned a server error rather than loading), so if your specific filing tool or GSP flags a DSC issue at the e-invoicing step specifically, confirm with that tool or the e-invoice portal directly rather than assuming it's the same return-filing certificate problem.

Practically: if GSTR-1/GSTR-3B filing is stuck on a DSC error but your e-invoices are still generating IRNs fine, that's expected, not a coincidence — IRN generation runs on your IRP login (or your software's connection to the IRP), not on your return-filing DSC, so fixing the DSC won't change anything on the e-invoicing side. What a stuck filing does eventually affect is your customers: until your GSTR-1 (or, for a quarterly filer, the IFF) is actually filed, your invoices — IRN or not — don't reach your buyers' GSTR-2B, and ITC on those invoices depends on their being furnished in that filing, not just reported to the IRP (Section 16(2)(aa), CGST Act, read with Rule 36(4) and Rule 60(7), CGST Rules).

How Recoup fits in

Recoup doesn't manage your DSC or your portal authorisation — those are yours to fix, on the government's own screens, the way this guide walks through. Where it fits is the other side of the same problem: your vendors hit these errors too. A vendor whose GSTR-1 is stuck behind a broken DSC hasn't furnished your invoices yet, so they don't reach your GSTR-2B, and you can't claim the credit on them until they do (Rule 36(4), CGST Rules). Recoup matches your books against IMS and GSTR-2B invoice by invoice and names the exact vendor and invoice blocking your credit — continuous checking that's painful to do manually — so you know which vendor to chase.

Know which vendor's stuck filing is blocking your credit

When a vendor's GSTR-1 stalls — a DSC error is one way it happens — their invoices don't land in your GSTR-2B until they file. Recoup matches your books against IMS and GSTR-2B invoice by invoice and names the vendor and invoice to chase.

Book a demo →

Related guides