Note |
---|
Make sure the connector is updated to the most recent version: 3.5.14 |
Check your version here: https://vo-connector.keysign.eu/
For help uninstalling an older version and installing the newest, go here: KeySign Connector - (Re)installation
For debugging through the received JSON, consult KeySign Connector Report - JSON debugging
Issue description | Detection | Fix | Workaround | ||
---|---|---|---|---|---|
The KeySign Connector is currently not installed in user space |
| Let the installer be run by the end user (download link in SigningHub error message) | |||
The Sandbox service is not started |
| Install the new Middleware version 3.2.5 or higherUpdate the KeySign Connector to the newest version on https://vo-connector.keysign.eu/ | |||
A wrong version of the KeySign Connector has been installed |
| Ask the user to install the latest KeySign Connector V3 version via the link in SigningHub or the link on https://vo-connector.keysign.eu/ | |||
Card not connected error |
|
| |||
Citrix / RDC / Terminal server | The Client system is on an RDC / Citrix / Terminal environment | In case users have already installed the KeySign connector before the proxy was installed they will have to re-install the connector Follow the guide KeySign Connector Remote Installation | |||
Reverse Proxy | If the Client system uses proxy, the KeySign Connector will not be recognized | Create Ask your environment administrator to create an exception in your organisations organization's proxy for: ksc.keysign.eu:52183 | |||
ksc url reroute problem | browsing to https://ksc.keysign.eu:52183/info gives an error message | add the following line to the hosts file (C:\Windows\System32\Drivers\Etc\Hosts)
|