Trusted & associated with
ICEGATE Troubleshooting
Beyond the well-known PKI component error, here are the other common reasons ICEGATE signing fails.
| If you see this | Try this |
|---|---|
| "No PKI Applet Found" or PKI connection error | Reinstall the ICEGATE PKI component matching your system's bit version, and run your browser as Administrator. |
| Certificate is Signing-only, not Combo | ICEGATE requires encryption. Upgrade to a Combo DSC, a Signing-only certificate cannot complete encrypted submission. |
| Token detected but signing still fails | Confirm your token drivers are current, and that no other DSC utility (from another portal) is conflicting on the same local port. |
| Browser blocks local PKI connection | Similar to GST's 127.0.0.1 issue, manually allow the local connection your browser is blocking, check the exact error message for the port number. |
| Signature valid but rejected by ICEGATE | Confirm your DSC is registered on ICEGATE specifically, a valid, working DSC still needs portal-specific registration. |
We offer remote troubleshooting for ICEGATE signing issues, and can issue a correctly configured Combo DSC if yours needs replacing.
Common causes include a recent browser update blocking local connections, a Windows update affecting drivers, or your DSC expiring, check each in turn.
The PKI component and signing tools are primarily built for Windows, Mac compatibility can be inconsistent, check current ICEGATE system requirements.
It resolves some, but not all, issues, particularly config-related ones. Check the specific error message first to identify the actual cause.