-
-
Notifications
You must be signed in to change notification settings - Fork 602
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
More explicit error message when certificate requested for IP address #3610
Comments
Thanks for clearing it up. |
@mgrep Both Let's Encrypt and Certbot support IPv6. Let's Encrypt does not support issuing a certificate for the IPv6 or IPv4 address directly - you need to have a domain name that points to the IPv4/IPv6 address. Please open a thread on the community forum if you need help with the above. This issue is specifically about improving the Boulder error message :-) Thanks! |
Now you lost me I have all that and it still did not work, I opened an issue and the answer is that I should have a domain name pointing to IPv4 and IPv6. host maikel.greppie.nl I will open a thread in forum as it seem we do not understand each other. |
Thanks! That's the best place to get help. It sounds like I'm missing some context. |
The boulder team has decided to close this issue. |
The issue at
certbot/certbot#5816
suggests that Boulder's error message, at least for IPv6 addresses, is somewhat confusing because it doesn't make explicit that Boulder has understood the request and refused it for policy reasons. Could we perhaps detect when a certificate request refers to an IP address and put "Can't issue certificate for IP address" or something similar in the error detail field?
The text was updated successfully, but these errors were encountered: