CryptoProvider error.

[vgobbo]

When running dx serve, the following error happens since axum-server version 0.7 and rustls version 0.23.13.

thread 'tokio-runtime-worker' panicked at /home/vgobbo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.23.21/src/crypto/mod.rs:249:14:
no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::option::expect_failed
   3: rustls::server::server_conn::ServerConfig::builder_with_protocol_versions
   4: rustls::server::server_conn::ServerConfig::builder
   5: axum_server::tls_rustls::config_from_der
   6: axum_server::tls_rustls::config_from_pem
   7: dx::serve::server::devserver_mainloop::{{closure}}
   8: tokio::runtime::task::core::Core<T,S>::poll
   9: tokio::runtime::task::harness::Harness<T,S>::poll
  10: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  11: tokio::runtime::scheduler::multi_thread::worker::Context::run
  12: tokio::runtime::context::runtime::enter_runtime
  13: tokio::runtime::scheduler::multi_thread::worker::run
  14: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll

As suggested in the bug axum-server#153, the workaround for this is to add feature tls-rustls-no-provider to axum-server, and add ring to rustls (not needed since the top-level Cargo.toml already does this).

[jkelleyrtp]

Thank yoU!

[vgobbo]

I see this was reverted by [1]. Why was it reverted?

dioxus-cli doesn't work without it when using HTTPS, which is pretty much a requirement nowadays with modern browsers even during development.

Can you provide an alternative?

[1] 5d48934

[h0pes]

@vgobbo Sorry to tag you, did you found a workaround or solution for this problem? Thanks a lot

[vgobbo]

@h0pes The workaround was the one in the MR, which got reverted for some reason. I've been using a fork with this patch since then.

[h0pes]

@vgobbo thanks for your reply. I was wondering whether no one is developing with https enabled...
@jkelleyrtp Is there any plan to fix this issue (if it is an issue)? Thanks