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
While I'm here: is there a way to allow an insecure certificate for an app without making the auth server connection insecure too? (e.g. appliances with self-signed certs)
The text was updated successfully, but these errors were encountered:
While I'm here: is there a way to allow an insecure certificate for an app without making the auth server connection insecure too? (e.g. appliances with self-signed certs)
The error you're seeing here is just teleport trying to connect directly and failing, which is expected, before successfully connecting over proxy. I made PRs to reduce this to a small debug log to reduce confusion, thanks for pointing this out.
Description
What happened:
Logs have a TLS error about teleport.cluster.local
What you expected to happen:
No TLS errors about teleport.cluster.local
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
teleport start --config=config.yaml
Server Details
teleport version
):Teleport v6.1.0-beta.1 git:v6.1.0-beta.1-0-g693576f98 go1.15.5
/etc/os-release
): Ubuntu 20.10Client Details
N/A
Debug Logs
Please include or attach debug logs, when appropriate. Obfuscate sensitive information!
teleport --debug
)tsh --debug
)teleport config
While I'm here: is there a way to allow an insecure certificate for an app without making the auth server connection insecure too? (e.g. appliances with self-signed certs)
The text was updated successfully, but these errors were encountered: