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

LE cert failed to issue with route53 #371

Closed
tamalsaha opened this issue Aug 10, 2017 · 3 comments · Fixed by #375
Closed

LE cert failed to issue with route53 #371

tamalsaha opened this issue Aug 10, 2017 · 3 comments · Fixed by #375
Assignees
Milestone

Comments

@tamalsaha
Copy link
Member

@tamalsaha tamalsaha commented Aug 10, 2017

There is a set of NS-s for a domain example.com . A separate hosted zone and NS-s for a subdomain qa.example.com . Voyager is trying to issue cert for web.qa.example.com . The problem is ACME challenge TXT record is created the root domain . So, the DNS record is not found and voyager times out.

The interesting situation is that user was able to use lego cli to issue the same cert from laptop at that time.

Somehow voyager's lego library and lego clis is not working the same way.

@tamalsaha

This comment has been minimized.

Copy link
Member Author

@tamalsaha tamalsaha commented Aug 11, 2017

@greg-jaunt, I believe I know why this is happening.

I added a commit https://github.com/xenolf/lego/pull/336/files to fix go-acme/lego#330 issue. The public-suffix package is returning the root domain. I have an idea how to fix for both these cases.

@tamalsaha

This comment has been minimized.

Copy link
Member Author

@tamalsaha tamalsaha commented Aug 11, 2017

We were able to reproduce this issue and test that fix is working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.