-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected ssl.sigalgs error in version 1.17 #14708
Comments
See https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.17.0:
CC @PiotrSikora |
Thank you |
@htuch that's not it at all. It's a bug in #14534, fixed in #14703, and hopefully released soon in 1.171. |
I can confirm that this bug hasn't solved yet.
conf: - name: envoy.filters.network.tcp_proxy
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
stat_prefix: ingress
cluster: amqps
transport_socket:
name: envoy.transport_sockets.tls
typed_config:
"@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
common_tls_context:
tls_certificates:
- certificate_chain: { filename: "tls-gen/basic/result/server_certificate.pem" }
private_key: { filename: "tls-gen/basic/result/server_key.pem" }
....
transport_socket:
name: envoy.transport_sockets.tls
typed_config:
"@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
common_tls_context:
tls_params:
tls_minimum_protocol_version: "TLSv1_2" the
Thank you for working on it |
Title: I got unexpected ssl.sigalgs error in version 1.17
Description:
When I upgrade envoy from 1.16.2 to 1.17.0 I got this message.
Didn't have in version 1.16.2
I think this is related to UpstreamTlsContext because when I switch to non-ssl upstream and delete transport socket conf everything is fine
CDS
Error Log
The text was updated successfully, but these errors were encountered: