WARN [MX:PROXY:] "\nERROR REPORT:\nOriginal Error:

I had this error while setting up again, it’s due to running Teleport behind a GCP Load Balancer and not running it in --insecure-no-tls

WARN [MX:PROXY:] "\nERROR REPORT:\nOriginal Error: *trace.BadParameterError failed to detect protocol by prefix: [71 69 84]\nStack Trace:\n\t/home/benarent/go/src/github.com/gravitational/teleport/lib/multiplexer/multiplexer.go:318 github.com/gravitational/teleport/lib/multiplexer.detectProto\n\t/home/benarent/go/src/github.com/gravitational/teleport/lib/multiplexer/multiplexer.go:260 github.com/gravitational/teleport/lib/multiplexer.detect\n\t/home/benarent/go/src/github.com/gravitational/teleport/lib/multiplexer/multiplexer.go:197 github.com/gravitational/teleport/lib/multiplexer.(*Mux).detectAndForward\n\t/snap/go/3739/src/runtime/asm_amd64.s:1338 runtime.goexit\nUser Message: failed to detect protocol by prefix: [71 69 84]\n" logrus/entry.go:140

Solution: Start Teleport with --insecure-no-tls When using a cloud lb.

Plan: Should update to give a better debug message for customers.