Fixing Common GST Portal Errors
Most problems on gst.gov.in are one of a small set of recurring issues. This is a reference to the common ones — what causes them and how to clear them — grouped by where they show up. For the filing steps themselves, see the walkthroughs for GSTR-1 and GSTR-3B.
Login and browser
- “Invalid username or password” / account locked. After several wrong attempts the account locks for a short period. Wait, or use Forgot Password — it needs OTPs to the registered email and mobile, so both must be current.
- Pages not loading, buttons not responding, “session expired”. Use one tab only, on a current version of Chrome, Firefox or Edge. Clear cached files and cookies for gst.gov.in, disable ad-blockers and script blockers for the site, and switch off any VPN or proxy.
- OTP not arriving. Check the number/email under My Profile. Wait a minute before requesting a resend; repeated quick requests are throttled.
Digital signature (DSC) and emSigner
- “Failed to establish connection to the server. Kindly restart the Emsigner.” The signing helper is not running or is blocked. Fixes, in order:
- Close the browser. Right-click the emSigner utility and Run as administrator.
- Open https://127.0.0.1:1585 in a new tab and accept the security warning so the browser trusts the local certificate. Try 1586 / 2074 / 2083 if 1585 is busy, and pick the matching port in the DSC dropdown on the portal.
- Make sure a supported Java runtime is installed, and that antivirus or a firewall is not blocking the local port.
- DSC not listed when signing. Register it first: My Profile → Register / Update DSC. The token must be plugged in and its drivers installed.
- “PAN mismatch” on signing. The PAN encoded in the DSC must match the PAN of the authorised signatory selected on the return, not the business PAN.
- If the DSC will not cooperate and you are not a company or LLP, file with EVC (OTP) instead.
Return filing error codes
| Code / message | Meaning and fix |
|---|---|
| RET191106, RET191113, RET191114 and similar | Generic processing errors on the portal's side. Save again after a few minutes; if it repeats, re-open the return and re-enter the affected table, then save. |
| “Processed with error” after a JSON upload | Download the error report the portal generates, correct the rows it flags in the Offline Tool, regenerate the JSON and re-upload. |
| “Checksum validation failed” / “Invalid summary payload” | The JSON was generated for a different GSTIN or period. Re-select the correct GSTIN and period in the Offline Tool and regenerate — never hand-edit the JSON. |
| “Summary not generated” / totals blank on the payment screen | Click Generate Summary (GSTR-1) or Save then Proceed to Payment (GSTR-3B), and wait — it queues. |
| “Previous period return not filed” | Returns are sequential. File the earlier pending return first. GSTR-3B is also blocked until the same period's GSTR-1 is filed. |
| “You have already filed the return for this period” | An earlier attempt succeeded. Check the status on the Returns Dashboard before retrying. |
Input tax credit and ledgers
- GSTR-2B not available. It is generated on the 14th of the month for the previous period. Do not file GSTR-3B expecting Table 4 to auto-fill before then.
- Table 4 ITC does not match your books. The figure is from GSTR-2B. Reconcile invoice by invoice, edit “all other ITC” downward for anything not being claimed, and keep a working. A small difference within the tolerance limit only produces a warning, not a block. The Rule 42 calculator helps where common credit is involved.
- Challan paid but cash ledger not updated. Net-banking payments are near-instant; NEFT/RTGS can take a working day. Check Services → Payments → Challan History. If it is stuck beyond that, raise a grievance under the payment category with the CIN / CPIN.
- Negative liability (composition). Caused by leaving Table 6 of GSTR-4 blank. Fill Table 6 with rate-wise outward supplies; a stuck negative entry needs a grievance ticket to reverse.
Registration and profile
- Amendment stuck at “Pending for processing” or “Pending for clarification”. A core-field change (legal name, principal place of business, promoters) goes to an officer. If clarification is sought, respond within 7 working days or the application is rejected.
- Changing email or mobile. Done under the authorised-signatory details; both the new email and new number must be verified by OTP.
- “GSTIN not registered on the e-invoice portal”. If your turnover has crossed the e-invoicing threshold, enable it at einvoice1.gst.gov.in — it is a separate registration from the main portal.
Raising a grievance
When a genuine portal fault blocks you, use the self-service grievance system at grievance.gst.gov.in (also reachable from the portal footer). Pick the most specific category, quote the exact error text and code, attach a screenshot, and note the date, time and what you were doing. Keep the ticket number — filing due dates are not automatically extended, but a logged grievance is your record if a late fee is later disputed.
Key takeaways
- Most “errors” are transient — save again after a few minutes before assuming something is broken.
- emSigner problems are almost always the local helper not running as administrator or the 127.0.0.1 certificate not trusted; EVC is the fallback for non-companies.
- JSON upload failures mean the file was built for the wrong GSTIN or period — regenerate, don't edit.
- GSTR-2B lands on the 14th; ITC and negative-liability issues almost always trace back to a reconciliation or a blank table.
- Log a grievance with the exact error and a screenshot when a real fault stops you filing.
Frequently asked questions
Close the browser and run emSigner as administrator. Open https://127.0.0.1:1585 and accept the certificate warning so the browser trusts the local helper, and select the matching port on the portal. Make sure Java is installed and no firewall or antivirus is blocking the port. If you are not a company or LLP, file with EVC instead.
They are generic processing errors on the portal's side, usually temporary. Save again after a few minutes; if it repeats, re-open the return, re-enter the affected table and save.
The JSON was generated for a different GSTIN or return period. Re-select the correct GSTIN and period in the Offline Tool and regenerate the file - do not edit the JSON by hand.
It is generated on the 14th of the month for the previous tax period. Table 4 of GSTR-3B will not auto-populate before then.