FAQs for Crypto Express Network API for Secure Execution Enclaves

  1. Rsyslog server can't receive logs from Crypto Express Network API for Secure Execution Enclaves

    If you don't receive logs from the Rsyslog server, see Preparing Rsyslog server for log collection.

  2. API returns with non 200 error

    • If status code is not 200, the web server on the Crypto Express Network API for Secure Execution Enclaves might be unavailable. Check the detailed error logs from the configured Rsyslog server, and fix any errors you might find, then retry the API.
    • If you see format error messages, input the parameters in the correct format.
  3. Certificate verification failure

    You might encounter an error like

    SSL routines:tls_process_server_certificate:certificate verify failed
    

    Ensure that you prepare mTLS certs for c16 as well as for grep11 correctly and add the certificates to the correct path.

  4. Log level setting

    Log level is set to "info" by default, which is recommended, and "debug" is used only when the request frequency is low.