5. Support

The Support page is opened from Support in the top menu of TrustView. It brings together the documentation, the API documentation, sending log files to Cryptomathic’s Technical support, and our contact details.

5.1. TrustView documentation

A link to this documentation, for information on the different modules.

5.2. TrustView API documentation

The API documentation for the current API, in three forms:

  • TrustView-swagger.json - the API in Swagger (OpenAPI) format, as JSON.

  • TrustView-swagger.yaml - the same, as YAML.

  • Test our API via Swagger UI - opens Swagger UI, where API calls can be tried out directly.

See API for how to authorize Swagger UI with an API key.

5.3. Send log files to Technical support

Instead of finding the TrustView log files on the server and sending them by e-mail, they can be sent securely to Cryptomathic directly from TrustView:

  1. Open Send log files to Technical support on the Support page. TrustView lists the log files from the last 30 days (.log, .txt and .zip files in its logs folder), newest first.

  2. Select the files that cover the time of the problem. The files changed within the last 7 days are selected already.

  3. Click Send to Technical support.

TrustView packs the selected files into one zip file and sends it to Cryptomathic, and then tells you whether it succeeded:

  • Success - the files have been sent. Let our Support know, so we can link them to your case.

  • Error - the files were not sent, and the message says why:

    • TrustView could not connect to Cryptomathic, or the connection timed out - check that TrustView can reach api.trustskills.com on port 443, see Network Requirements.

    • The upload was rejected by Cryptomathic, with a status code.

    • An unexpected error occurred while packing or sending the files.

    Try again, or locate the files on the server and send them by e-mail instead.

  • No log files were selected - select at least one file and try again.

If no files are listed, TrustView could not read its log folder. Locate the files on the server instead, see TrustView log file.

Note

  • Sending log files requires a role with write access - Global administrator, Superuser, User, or a custom role with write permission. Read-only user and Certificate requestor cannot send log files. See Users, Groups and Roles.

  • The section is available in TrustView on-premises and in the cloud edition, but not in TrustView Lite.

Tip

The logs of the other TrustView components, such as the ADCS module, scan agents and ACME clients, are not included. See Logs for where to find them, and for which log to check for which problem.

5.4. Contact support

To help us help you quickly, include:

  • Your TrustView version - shown under Systeminfo in Settings, and on the System status page.

  • What happened, when it happened, and what you expected to happen - including the time, so the right part of the log can be found.

  • The relevant log files - sent from TrustView or attached to the e-mail.

  • For a problem with a single certificate, SSL endpoint, automation task or integration: its Event log, for example as a screenshot.