# Problem with Punycode Domains **URL:** \ **Category:** Help\ **Created:** [April 12, 2017, 9:56am UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912 "2017-04-12T09:56:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Sm3rT](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sm3rt/32/12694_2.png) [@Sm3rT](https://community.letsencrypt.org/u/Sm3rT)\ **Post date:** [April 12, 2017, 9:56am UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/1 "2017-04-12T09:56:32Z")
Hi Community, i have a Problem with a Punycode Domain, so i searched in this Community how to solve it. I seen i had a outdated version of certbot (certbot 0.8.1) and Punycode Domains should be supported after version 0.9.2, so i updated my version with yum update certbot, now i have the new version certbot 0.9.3, but still cant verify punycode domains. My domain is: [süsse-engel.com](http://xn--ssse-engel-9db.com) Punycode is: [süsse-engel.com](http://xn--ssse-engel-9db.com) I ran this command: /usr/bin/certbot --non-interactive --expand certonly --webroot -w $documentroot -d [www.süsse-engel.com](http://www.xn--ssse-engel-9db.com),[m.süsse-engel.com](http://m.xn--ssse-engel-9db.com),[ds.süsse-engel.com](http://ds.xn--ssse-engel-9db.com),[süsse-engel.com](http://xn--ssse-engel-9db.com) It produced this output: Punycode domains are not presently supported: [www.süsse-engel.com](http://www.xn--ssse-engel-9db.com) My operating system is (include version): CentOS Linux release 7.2.1511 (Core) My web server is (include version): Apache/2.4.6 (CentOS) My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don’t know): yes I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no My Version of Certbot is: certbot 0.9.3 ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [April 12, 2017, 5:49pm UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/2 "2017-04-12T17:49:12Z")
Hi @Sm3rT, If you're running 0.9.3, the error that should have been displayed is > Non-ASCII domain names not supported. To issue for an Internationalized Domain Name, use Punycode. In this case, Certbot is asking you to explicitly request the Punycode form of your domain name. Version 0.9.3 should be willing to submit this request. If you're still getting the "Punycode domains are not presently supported" error, you're probably still unintentionally running 0.8.1 even if you also have 0.9.3 installed. ---
**Author:** ![Sm3rT](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sm3rt/32/12694_2.png) [@Sm3rT](https://community.letsencrypt.org/u/Sm3rT)\ **Post date:** [April 13, 2017, 9:45am UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/3 "2017-04-13T09:45:25Z")
Hi @schoen, i looked for my version of certbot and i only see the 0.9.3 version on my system. rpm -qa | grep certbot python2-certbot-0.9.3-1.el7.noarch certbot-0.9.3-1.el7.noarch i run this command: /usr/bin/certbot --non-interactive --expand certonly --webroot -w $documentroot -d [www.süsse-engel.com](http://www.xn--ssse-engel-9db.com),[m.süsse-engel.com](http://m.xn--ssse-engel-9db.com),[ds.süsse-engel.com](http://ds.xn--ssse-engel-9db.com),[süsse-engel.com](http://xn--ssse-engel-9db.com) But still the same error: Punycode domains are not presently supported: [www.süsse-engel.com](http://www.xn--ssse-engel-9db.com) ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [April 13, 2017, 6:11pm UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/4 "2017-04-13T18:11:01Z")
@erica @bmw, wasn’t this restriction (and error message) already removed in 0.9.3? How could it be displaying this message? ---
**Author:** ![bmw](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmw/32/7797_2.png) [@bmw](https://community.letsencrypt.org/u/bmw)\ **Post date:** [April 14, 2017, 3:45pm UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/5 "2017-04-14T15:45:07Z")
No. Support for this landed in 0.10.0 ([source](https://github.com/certbot/certbot/blob/master/CHANGELOG.md#0100---2017-01-11)). Luckily, Certbot 0.12.0 is available in EPEL 7 on CentOS so if you upgrade your Certbot version this problem should go away. ---
**Author:** ![Sm3rT](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sm3rt/32/12694_2.png) [@Sm3rT](https://community.letsencrypt.org/u/Sm3rT)\ **Post date:** [April 25, 2017, 2:51pm UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/6 "2017-04-25T14:51:02Z")
@bmw@schoen Thanks a lot, with new version (certbot-0.12.0-4) is all good 🙂 IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/www.xn–ssse-engel-9db.com/fullchain.pem. greetz Sm3rT ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [May 25, 2017, 2:57pm UTC](https://community.letsencrypt.org/t/problem-with-punycode-domains/31912/7 "2017-05-25T14:57:11Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.