Skip to content

Conversation

@sejongk
Copy link

@sejongk sejongk commented Feb 13, 2022

Bug description

Below errors were occurred after following the tutorial.
On client side,
time="2022-02-13T16:17:40Z" level=error msg="Get \"https://172.17.0.4:22211/discover\": x509: certificate relies on legacy Common Name field, use SANs instead"
On server side,
2022/02/13 16:17:40 http: TLS handshake error from 172.17.0.5:45394: remote error: tls: bad certificate

Root cause

After golang 1.15, we should use SANS or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0.
See https://stackoverflow.com/questions/64814173/ how-do-i-use-sans-with-openssl-instead-of-common-name.

Solution description

I added a guideline that describes how to add SANS in server's certificate.
If there is any problem, please tell me. I'm willing to fix it.

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

Successfully merging this pull request may close these issues.

1 participant