This message was deleted.

It seems likely that your issue is caused by a mismatch between the client and server authentication settings, or by a misconfigured endpoint/protocol. The error

error reading server preface: http2: frame too large

often indicates that the client is trying to use HTTP/2 (gRPC, often with TLS/auth) while the server is serving plain HTTP/1.1, or vice versa. If you previously enabled OAuth2/OIDC and then disabled it, but your

flytectl

config or CLI flags still specify an auth mode (like

Pkce

), this can cause such errors. Also, ensure your endpoint is set to the correct protocol and port (e.g., use

http://

and the correct port if TLS/auth is disabled) and that

insecure

is set appropriately in your config. You may want to check and update your

flytectl

config file (usually

~/.flyte/config.yaml

) to ensure

authType

is not set to

Pkce

or any other auth mode, and that the endpoint matches your current Flyte deployment (e.g.,

http://flyte.test.k8s.daiger.ru:8089

if using the default non-TLS gRPC port). Remove any authentication-related fields if auth is disabled. This pattern of errors and solutions is discussed in several Flyte issues, such as this one and this one. Would you like more detail on how to reset your client configuration or further troubleshoot this error? Sources: - this one - this one 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.