-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
IDN support #331
Comments
I have used acme.sh to register my IDNs, it works perfectly! What I didn't try is the readable domain name, just the punycode version. |
@noplanman I have checked in a branch idn : https://github.com/Neilpang/acme.sh/tree/idn which is able to process readable idn domain names, instead of your punycode version. I'm still testing this branch, it will be merged once testing is finished. You may have a try:
|
Great stuff, will have a look when I add a new domain 👍 |
IDN supported now. it relies on a new tool It's available on Linux/Freebsd/Openbsd etc. |
I get this error message: How am I supposed to call the Must I install I'm on Debian Jessie. |
Yes, on debian install idn is enough.
|
I don't see any extra helpful messages using Is there any output from the FYI. special character in my case is an |
@noplanman |
It seems that here is something wrong with the char let me check and fix. |
Doesn't seem to help. I get more output (obviously), but the core issue is the same one. Any other ideas? Edit: Just saw your reply. |
@noplanman |
@noplanman |
@Neilpang Perfect, works like a charm now! Thanks a lot 😃 |
@Neilpang According to the bug I reported to LE, The IDN support of the CA Software (Known as Boulder) still has some critical bugs on PSL list identifying to solve. You had better to reopen the issue and wait until the bug solved. Log for Reference:
|
I noticed that the signed certificate has the CN set to the punycode domain name anyway, so what is the advantage of using the readable one instead of the punycode one? |
@noplanman I was trying to know if there is bugs in Boulder. |
@wangqiliang Thanks. |
Right. Sorry if my comment came out wrong. It's more of a general question. |
@Neilpang Get it, and Thanks a lot. |
The advantage is to simplify the process to the normal non-professional user. They don't even need to know what punycode code is. It's our goal to make it simple to more users. |
Ok, got you. Awesome viewpoint, making easier for everyone! |
@wangqiliang you are genius to find that bug 👍 |
Hey, I have a domain ù.eu.org exhibiting the same behavior: Create new order error. Le_OrderFinalize not found. {"type":"urn:ietf:params:acme:error:malformed","detail":"Error creating new order :: Invalid character in DNS name","status": 400} |
@justmwa Have you tried it with the punycode version of the domain name? In your case it would be: |
@noplanman yes, then it's dns_cf that complains about domain not found. |
It seems that idn is enabled.
We need to support soon.
https://community.letsencrypt.org/t/idn-support-enabled/21469
The text was updated successfully, but these errors were encountered: