Skip to content
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

Investigate TLS #107

Open
tallen-hashicorp opened this issue Oct 15, 2024 · 0 comments
Open

Investigate TLS #107

tallen-hashicorp opened this issue Oct 15, 2024 · 0 comments

Comments

@tallen-hashicorp
Copy link

Potential Causes:

1. TLS Configuration Mismatch:

  • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant