# Impossible to get SSL with https for my non-ASCII domain name even when use Punny code **URL:** \ **Category:** Help\ **Created:** [October 15, 2024, 1:41pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367 "2024-10-15T13:41:03Z")\ **Posts on this page:** 8\ **Page:** 2
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [October 15, 2024, 4:29pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/21 "2024-10-15T16:29:07Z")
> [@Loran](#): > > sudo certbot certonly --manual --preferred-challenges=dns --email admin@ciao.lv --server [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory) --work-dir=. --config-dir=. --logs-dir=. --agree-tos -d "xn--au-dma.lv" > > because you say this is wrong I don’t believe I said that command is wrong, I don’t think I said anything about the command. I believe your web server is not properly configured, I don’t know the LiteSpeed server. Thus I am unable to provide step by step assistance. Sorry! 🙁 ---
**Author:** ![Loran](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/loran/32/83307_2.png) [@Loran](https://community.letsencrypt.org/u/Loran)\ **Post date:** [October 15, 2024, 4:40pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/22 "2024-10-15T16:40:05Z")
yes, of course i have root access on my VPS server ---
**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\ **Post date:** [October 15, 2024, 4:48pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/23 "2024-10-15T16:48:25Z")
Perhaps it would help to clarify that there are two distinct operations that need to happen: (1) you need to obtain a cert, and (2) you need to configure your web server to use that cert. We can help with the first, but you don't need help with the first--you've obtained several certs from Let's Encrypt, the most recent about three weeks ago. They're being issued every 60 days (since November of last year), as would be expected of an automated system. Your problem is with the second part: configuring your web server to use the certs you already have. And that's something we can't help you with. You'll need to use whatever support channels exist for whatever web server or control panel software you're using. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [October 15, 2024, 4:58pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/24 "2024-10-15T16:58:11Z")
> [@danb35](#): > > configuring your web server to use the certs you already have. And that's something we can't help you with. You'll need to use whatever support channels exist for whatever web server or control panel software you're using. Indeed. Most volunteers on this Community only have experience with Apache and/or nginx. Experience with other webservers is very sparse and we're probably not the correct Community to help with those. ---
**Author:** ![Loran](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/loran/32/83307_2.png) [@Loran](https://community.letsencrypt.org/u/Loran)\ **Post date:** [October 15, 2024, 5:13pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/25 "2024-10-15T17:13:17Z")
so, shortly, the problem is not from Let's Encrypt, 100%, right? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [October 15, 2024, 5:14pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/26 "2024-10-15T17:14:20Z")
Correct. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [October 15, 2024, 5:24pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/27 "2024-10-15T17:24:53Z")
Let's Encrypt only issues certificates, nothing more. If issuance is not the problem (which would have resulted in some kind of error), the problem is not with Let's Encrypt. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [November 14, 2024, 5:25pm UTC](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367/28 "2024-11-14T17:25:29Z")
Closed on November 14, 2024, 5:25pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. [Previous page](https://community.letsencrypt.org/t/impossible-to-get-ssl-with-https-for-my-non-ascii-domain-name-even-when-use-punny-code/227367.md?page=1)