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

http TLS bad handshake from ip: bad certificate #9

Open
Romeren opened this issue Mar 16, 2021 · 5 comments
Open

http TLS bad handshake from ip: bad certificate #9

Romeren opened this issue Mar 16, 2021 · 5 comments

Comments

@Romeren
Copy link

Romeren commented Mar 16, 2021

Hello good people of cert-manager-webhook-transip

Im trying to use this chart for as a integration with Transip for DNS01 challenge to enable wildcard certificates.

So, what i did:

I have a installation of cert-manager (version cert-manager-v1.2.0-alpha.1) running in my cluster. And i can confirm that it is working. (i have created a issuer for http-01 challenge type and managed to create a valid certificate)

I followed the instructions and have deployed the chart with helm 3.

I have created a secret with the my credentials for transip.

The error im getting

When looking at the logs of the pod I seem to be getting a steady stream of errors:

I0316 14:58:35.976213       1 log.go:172] http: TLS handshake error from 10.164.0.12:34678: remote error: tls: bad certificate
I0316 14:58:36.198807       1 log.go:172] http: TLS handshake error from 10.164.0.14:59010: remote error: tls: bad certificate
I0316 14:58:36.228736       1 log.go:172] http: TLS handshake error from 10.164.0.20:59360: remote error: tls: bad certificate
I0316 14:58:39.136329       1 log.go:172] http: TLS handshake error from 10.164.15.198:37438: remote error: tls: bad certificate
I0316 14:58:39.800156       1 log.go:172] http: TLS handshake error from 10.164.15.237:41270: remote error: tls: bad certificate
I0316 14:58:52.488458       1 log.go:172] http: TLS handshake error from 10.164.15.237:41302: remote error: tls: bad certificate

And i was wondering what that meant, and how i can fix it.....

I imagine that its something silly that i have over looked....

Thanks in advance.

@Romeren
Copy link
Author

Romeren commented Mar 16, 2021

Quick update with additional info...
So the IPs of 10.164.0.XXX corresponds to kube-proxy
And the 10.164.15.XXX are for ip-masq-agent

@Romeren
Copy link
Author

Romeren commented Mar 16, 2021

Digging through the logs.... There also seems to be an additional error:

E0316 13:57:46.588481       1 webhook.go:199] Failed to make webhook authorizer request: Post https://10.67.0.1:443/apis/authorization.k8s.io/v1/subjectaccessreviews: context canceled          
E0316 13:57:46.588770       1 errors.go:77] Post https://10.67.0.1:443/apis/authorization.k8s.io/v1/subjectaccessreviews: context canceled

@Romeren
Copy link
Author

Romeren commented Mar 16, 2021

Investigating if this is related to: #4
.....

Though the error messages i have are slightly different than the ones described in this issue, i do believe that the root cause is the same.....

Since the other issue does not describe a solution, ill add a solution here so that the next person knows what to do....

@dannyspijker
Copy link

@Romeren Have you already find a solution? I have the same issue.

@dannyspijker
Copy link

dannyspijker commented May 20, 2021

I fixed the issue by manually change changes from this pull request
#6

@robbietjuh can you merge the pull request?

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

No branches or pull requests

2 participants