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 handshake error from x.x.x.x: EOF #992

Closed
alexandrst88 opened this issue Jul 14, 2017 · 6 comments
Closed

http: TLS handshake error from x.x.x.x: EOF #992

alexandrst88 opened this issue Jul 14, 2017 · 6 comments

Comments

@alexandrst88
Copy link

alexandrst88 commented Jul 14, 2017

Hi, this is my first issue in this project, if I missed to add information, please let me know.
I'm getting this error in dex logs:

2017/07/14 12:02:01 http: TLS handshake error from 100.71.36.0:50261: EOF
2017/07/14 12:02:01 http: TLS handshake error from 100.110.213.130:25122: EOF
2017/07/14 12:02:01 http: TLS handshake error from 100.74.197.192:6610: EOF

Dex Version: quay.io/coreos/dex:v2.4.1
Kubernetes Version: 1.6.2
Also, I see the same error in kube-api logs.

I0714 11:59:02.545732       5 logs.go:41] http: TLS handshake error from 172.22.95.22:30431: EOF
I0714 11:59:02.839669       5 logs.go:41] http: TLS handshake error from 172.23.95.214:1508: EOF

Also, I'm using LDAP connector.

@ericchiang
Copy link
Contributor

Something is probably sending an HTTP request to a port that dex is expecting an HTTPS request at. Maybe a health check?

There's not enough information here for us to know what's going on. What were you expecting to happen? What actually happened?

@ericchiang
Copy link
Contributor

Closing for lack of info. Please open another issue if you think you've hit a dex bug.

@alexandrst88
Copy link
Author

Sorry, indeed it was going from elb health check.

@yawboateng
Copy link

@alexandrst88 how did you fix this? im also seeing the same in my logs. not sure what is sending this http req

@alexandrst88
Copy link
Author

In my case it was LB, that was trying to reach https.

@yawboateng
Copy link

gotcha. i manually updated in aws from TCP to SSL. k8s seems to only use TCP for the elb

FYI: kubernetes/kubernetes#45746

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

3 participants