You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the service or the ingress is expecting a TLS connection, but the client is connecting over plain HTTP, this error will occur.
Ensure that the client is using HTTPS when connecting to a service that expects TLS.
2. Misconfigured Ingress or Service:
The NGINX ingress may be configured to use TLS for one or more ports (9200/9201), but the underlying service or the worker process is not configured to handle TLS connections.
Double-check if the Boundary worker or controller expects plain HTTP and whether the NGINX ingress is incorrectly terminating TLS, or if it's expected to pass through TLS connections.
3. Incorrect Target Port:
If the ingress is terminating the TLS connection (decoding HTTPS into HTTP) but forwards the traffic to the worker or controller on a port expecting HTTPS, this mismatch can cause the issue.
Ensure that when the ingress handles TLS, it sends HTTP traffic to the service's backend.
The text was updated successfully, but these errors were encountered:
Potential Causes:
1. TLS Configuration Mismatch:
2. Misconfigured Ingress or Service:
3. Incorrect Target Port:
The text was updated successfully, but these errors were encountered: