If switch back the 1.17.3 image, everything starts without any issues with exactly the same configuration. The periphery service on 1.17.4 seems to start without any issues as far as I can see when using PERIPHERY_SSL_ENABLED=true
I'm not entirely sure what to troubleshoot....has anyone else come across this and resolved it, or is this an issue with 1.17.4?
Thanks!
Originally created by @jsworks on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/469
After upgrading to 1.17.4, the Komodo core service fails to start when using `KOMODO_SSL_ENABLED=true`.
Here is the output from the console prior to the core (eventually) exiting:
```
thread 'tokio-runtime-worker' panicked at bin/core/src/main.rs:106:8:
komodo-core | failed to install default rustls CryptoProvider: CryptoProvider { cipher_suites: [TLS13_AES_256_GCM_SHA384, TLS13_AES_128_GCM_SHA256, TLS13_CHACHA20_POLY1305_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256], kx_groups: [X25519, secp256r1, secp384r1], signature_verification_algorithms: WebPkiSupportedAlgorithms { all: [ .. ], mapping: [ECDSA_NISTP384_SHA384, ECDSA_NISTP256_SHA256, ED25519, RSA_PSS_SHA512, RSA_PSS_SHA384, RSA_PSS_SHA256, RSA_PKCS1_SHA512, RSA_PKCS1_SHA384, RSA_PKCS1_SHA256] }, secure_random: Ring, key_provider: Ring }
```
If switch back the 1.17.3 image, everything starts without any issues with exactly the same configuration. The periphery service on 1.17.4 seems to start without any issues as far as I can see when using `PERIPHERY_SSL_ENABLED=true`
I'm not entirely sure what to troubleshoot....has anyone else come across this and resolved it, or is this an issue with 1.17.4?
Thanks!
GiteaMirror
added the bug label 2026-07-13 13:51:24 -05:00
Thanks for pointing this out, I think there is an issue with change I made in 1.17.4, like you mentioned only Core ssl will break, periphery is fine. TBH I never run core with ssl in favor of using a reverse proxy, so I missed it breaking
<!-- gh-comment-id:2845287956 -->
@mbecker20 commented on GitHub (May 1, 2025):
Thanks for pointing this out, I think there is an issue with change I made in 1.17.4, like you mentioned only Core ssl will break, periphery is fine. TBH I never run core with ssl in favor of using a reverse proxy, so I missed it breaking
A reverse proxy like Caddy (which is almost trivial to set up) can get you SSL without having to depend on Komodo for it. That was you'll never have to worry about this breaking again.
<!-- gh-comment-id:2904405468 -->
@mpkossen commented on GitHub (May 23, 2025):
> Issue is still present for me in 1.17.5.
This was not fixed in 1.17.5.
A reverse proxy like Caddy (which is almost trivial to set up) can get you SSL without having to depend on Komodo for it. That was you'll never have to worry about this breaking again.
Yes It is expected to still be broken for now. The docs still say this: https://komo.do/docs/setup#https
It may be fixed in the future but is not exactly a priority
<!-- gh-comment-id:3232224188 -->
@mbecker20 commented on GitHub (Aug 28, 2025):
Yes It is expected to still be broken for now. The docs still say this: https://komo.do/docs/setup#https
It may be fixed in the future but is not exactly a priority
<!-- gh-comment-id:3634084330 -->
@Gavitron commented on GitHub (Dec 9, 2025):
is this the underlying cause of the issue?
https://github.com/rustls/rustls/issues/1877
I also found a reference to this same issue in a rust-internals feature proposal:
https://internals.rust-lang.org/t/pre-rfc-mutually-excusive-global-features/19618/48
which looks like it is at least being considered for inclusion in 0.24:
https://github.com/rustls/rustls/issues/2396
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jsworks on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/469
After upgrading to 1.17.4, the Komodo core service fails to start when using
KOMODO_SSL_ENABLED=true.Here is the output from the console prior to the core (eventually) exiting:
If switch back the 1.17.3 image, everything starts without any issues with exactly the same configuration. The periphery service on 1.17.4 seems to start without any issues as far as I can see when using
PERIPHERY_SSL_ENABLED=trueI'm not entirely sure what to troubleshoot....has anyone else come across this and resolved it, or is this an issue with 1.17.4?
Thanks!
@mbecker20 commented on GitHub (May 1, 2025):
Thanks for pointing this out, I think there is an issue with change I made in 1.17.4, like you mentioned only Core ssl will break, periphery is fine. TBH I never run core with ssl in favor of using a reverse proxy, so I missed it breaking
@smarthome-enthusiast commented on GitHub (May 20, 2025):
Hi, was this fixed in 1.17.5?
@jsworks commented on GitHub (May 20, 2025):
Issue is still present for me in 1.17.5.
@mpkossen commented on GitHub (May 23, 2025):
This was not fixed in 1.17.5.
A reverse proxy like Caddy (which is almost trivial to set up) can get you SSL without having to depend on Komodo for it. That was you'll never have to worry about this breaking again.
@mbecker20 commented on GitHub (Aug 28, 2025):
Yes It is expected to still be broken for now. The docs still say this: https://komo.do/docs/setup#https
It may be fixed in the future but is not exactly a priority
@Gavitron commented on GitHub (Dec 9, 2025):
is this the underlying cause of the issue?
https://github.com/rustls/rustls/issues/1877
I also found a reference to this same issue in a rust-internals feature proposal:
https://internals.rust-lang.org/t/pre-rfc-mutually-excusive-global-features/19618/48
which looks like it is at least being considered for inclusion in 0.24:
https://github.com/rustls/rustls/issues/2396