Skip to main content

Coming Soon: Binary signing errors and solutions for GitLab CI/CD

The following errors may occur during Binary signing for GitLab CI/CD.

Certificate not found

Error message

No .p12 certificate found in .secure_files

Solution

  1. Verify certificate is uploaded to Settings > CI/CD > Secure Files.

  2. Ensure file has .p12 extension.

  3. Alternatively, set SM_CLIENT_CERT_FILE variable with the path.

SMCTL not found

Error message

smctl not found in PATH

Solution

  1. Change CACHE_VERSION variable to force re-download.

  2. Check runner has internet access to DigiCert CDN.

  3. Verify runner OS is supported (Linux, macOS, and Windows)

PKCS#11 Library Missing

Error message

PKCS#11 library not found

Solution

  1. Use traditional-signingt emplate (not .simple-signing).

  2. Ensure smtools are downloaded correctly

  3. Check runner has sufficient permissions to install tools

Signing Failed - Invalid Credentials

Error message

Signing failed with authentication error

Solution

  1. Verify SM_HOST, SM_API_KEY and SM_CLIENT_CERT_PASSWORD are correct.

  2. Check certificate is not expired.

  3. Ensure API key has signing permissions.

  4. Verify KEYPAIR_ALIAS exists in your DigiCert account.

Runner Out of Space

Error message

Runner fails with disk space issues 

Solution

  1. Clear GitLab runner cache.

  2. Adjust artifact expiration times.

  3. Use CACHE_VERSION to manage tool caching.

本节内容如下: