Hello,
My apologies in advance if this is a prime example of PEBKAC. I discovered this tool/repo today, and tried to get it running on two different machines (Windows/WSL, Linux/Omarchy). Both behaved exactly the same way, throwing the following error:
scanning 1 hosts...
thread 'tokio-rt-worker' (123831) panicked at /home/jkovacs/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustls-0.23.37/src/crypto/mod.rs:249:14:
Could not automatically determine the process-level CryptoProvider from Rustls crate features.
Call CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the 'aws-lc-rs' and 'ring' features is enabled.
See the documentation of the CryptoProvider type for more information.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
task error: task 10 panicked with message "\nCould not automatically determine the process-level CryptoProvider from Rustls crate features.\nCall CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the 'aws-lc-rs' and 'ring' features is enabled.\nSee the documentation of the CryptoProvider type for more information.\n "
cert-patrol fleet report | 0 hosts scanned | 2026-04-20 11:56:16 UTC
valid: 0 expiring: 0 expired: 0 warnings: 0 errors: 0
No results to display.
Version of cargo is 1.94.1 (29ea6fb6a 2026-03-24) (Arch Linux rust 1:1.94.1-1)
Thank you for your help in advance, kind regards,
Julius
Hello,
My apologies in advance if this is a prime example of PEBKAC. I discovered this tool/repo today, and tried to get it running on two different machines (Windows/WSL, Linux/Omarchy). Both behaved exactly the same way, throwing the following error:
Version of
cargois 1.94.1 (29ea6fb6a 2026-03-24) (Arch Linux rust 1:1.94.1-1)Thank you for your help in advance, kind regards,
Julius