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.

Sign up for GitHub

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

Jump to bottom

Let's encrypt retrieving certificate from wrong IP #962

Closed
MihaMarkic opened this issue Dec 11, 2016 · 1 comment
Closed

Let's encrypt retrieving certificate from wrong IP #962

MihaMarkic opened this issue Dec 11, 2016 · 1 comment
Labels
area/acme status/5-frozen-due-to-age

Comments

@MihaMarkic
Copy link

MihaMarkic commented Dec 11, 2016 •
edited

Hi guys,

I have a domain XY.com with default server (IP:193...) and I'm setting up another server with docker and traefik (runs in its official latest container).
I'm testing with subdomain tubo.XY.com which points to new server (IP:46...)
Now, the odd thing is that traefik gets challenge for tubo.XY.com but fails because of the other address (159...), debug log:
traefik_1 | time="2016-12-11T20:40:19Z" level=debug msg="Challenge GetCertificate tubo.XY.com"
traefik_1 | 2016/12/11 20:40:19 h2_bundle.go:3223: http2: server: error reading preface from client 193....:22828: remote error: tls: unknown certificate authority

How is that possible? Any idea?
@MihaMarkic
Copy link
Author

Nevermind, the IP in question is IP of the client requesting the cert and it is correct since I used staging Let's Encrypt.

@ldez ldez added the area/acme label Jun 11, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/acme status/5-frozen-due-to-age
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MihaMarkic @ldez @traefiker