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

Error to access UI using port-forward #5539

Closed
danilorsilva opened this issue Mar 29, 2021 · 5 comments · Fixed by #5550
Closed

Error to access UI using port-forward #5539

danilorsilva opened this issue Mar 29, 2021 · 5 comments · Fixed by #5550
Assignees
Labels

Comments

@danilorsilva
Copy link

Summary

Error when i try to access UI using port-forward

Diagnostics

What Kubernetes provider are you using?

GKE 1.18.15

What version of Argo Workflows are you running?

Latest - Using namespaced installation

LOG:

When i try to access:

https://localhost:2746

Service Unavailable: connection error: desc = "transport: authentication handshake failed: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0"
http:https://localhost:2746

Do not work
@alexec
Copy link
Contributor

alexec commented Mar 29, 2021

try starting using --secure=false

@danilorsilva
Copy link
Author

Thanks @alexec

I need to set --secure=false, --auth-mode=server and change de readness probe from https to http.

@alexec alexec reopened this Mar 30, 2021
@alexec
Copy link
Contributor

alexec commented Mar 30, 2021

Service Unavailable: connection error: desc = "transport: authentication handshake failed: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0"

@alexec alexec self-assigned this Mar 30, 2021
@alexec
Copy link
Contributor

alexec commented Mar 30, 2021

@alexec
Copy link
Contributor

alexec commented Mar 30, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants