fix rustls 0.23 CryptoProvider panic on Windows

Rustls 0.23+ no longer auto-selects a crypto backend when both
aws-lc-rs and ring are compiled in. Explicitly install ring as the
default provider at startup for cross-platform compatibility.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: neckaros

.gitignore

@@ -26,3 +26,4 @@ yt-dlp
 .redseat/**.*
 ffmpeg.exe
 ffprobe.exe
+.cache/

Cargo.lock

@@ -19,6 +19,7 @@ path = "src/main.rs"
 [dependencies]
 axum = {version = "0.7", features = ["query", "macros", "multipart"]}
 axum-server = { version = "0.7", features = ["tls-rustls"] }
+rustls = { version = "0.23", default-features = false, features = ["ring"] }
 tokio = { version = "1", features = ["full"] }
 tower-http = { version = "0.5.0", features = ["cors","trace", "normalize-path", "fs"] }
 serde = { version = "1", features = ["derive"] }

Cargo.toml

@@ -63,6 +63,12 @@ mod tools;
 
 #[tokio::main(flavor = "multi_thread")]
 async fn main() -> Result<()> {
+    // Rustls 0.23+ requires an explicit crypto provider when both aws-lc-rs and ring are available.
+    // Ring is used here for cross-platform compatibility (aws-lc-rs has build issues on Windows).
+    rustls::crypto::ring::default_provider()
+        .install_default()
+        .expect("Failed to install rustls crypto provider");
+
     let os = std::env::consts::OS;
     let arch = std::env::consts::ARCH;
     log_info(