Impossible to get SSL with https for my non-ASCII domain name even when use Punny code

Hi,
i tried everything, and i don't udnerstand how to set a SSL and get the HTTP¨S URL for my domain name with non ASCII caracter. even with Punny code is not working. i tried from Cyber panel, and with SSH and Certbot too, but anyway: i never get the HTTPS.
if someone have the solution, will be really great.

THANK YOU

My domain is: čau.lv (punnycode = xn--au-dma.lv)

The operating system my web server runs on is (include version):Ubuntu 22.04 with OpenLiteSpeed and Node.js

My hosting provider, if applicable, is: Hostinger

We would need the actual error messages or more details about the exact failure.

But, you should review your DNS records.

Your DNS A record for IPv4 points to a LiteSpeed server. But, you have two IPv6 AAAA records pointing to a Hostinger service.

You need to have just one correct AAAA address or remove them both if you do not support IPv6.

Any client trying to use IPv6 will connect to that Hostinger service instead of your server.
Let's Encrypt favors IPv6 when an AAAA record is present.

See Hostinger article here: How to manage AAAA records | Hostinger Help Center

And use this site to test connections (use your punycode domain name)
https://letsdebug.net

4 Likes

i just removed the two AAAA records, but anyway, not help: the same issue

What is the error exactly?

You said you tried Certbot. Can you show the Certbot command and the error message?

Or the error you get from Cyber panel?

4 Likes

error = just open "čau.lv" in your browser and you will understand imediatly (not HTTPS as iexplained)
Command Cerbot = sudo certbot certonly --manual --preferred-challenges=dns --email admin@ciao.lv --server https://acme-v02.api.letsencrypt.org/directory --work-dir=. --config-dir=. --logs-dir=. --agree-tos -d "xn--au-dma.lv"
PS: i am sure that comamand Cerbot is OK, problem is not from here, and anyway i tried with Cyber panel too, witch is the same final resultat by the way.
and Cyber panel there is not error when i install the SSL, the same if i do with SSH Cerbot.
but the resultatc is not ok = site is not HTTPS

I resume one more time so:
when i install the SSL , everything is ok, no error (i already done with success, for others websites on my server, with normal ASCII caracter, and i get the normal HTTPS) . problem is HTTPS not work.

the problem, i am almost sure, is because the domain name is non-ascii . but from my cloud server Hostinger the same domain name, the HTTPS works. only on my VPS with Cyber panel, the HTTPS not work.

i hope is more clear now

No, because you have not shown any error message as of yet. You say installation of "SSL" , everything is OK, but it isn't. That doesn't make much sense.

By the way, in the past you've got multiple Let's Encrypt certificates and also a Sectigo cert issued today: crt.sh | xn--au-dma.lv

  • how did you get those previous LE certs?
  • what's wrong with your Sectigo cert issued today?
4 Likes

it seems i was not clear, so listen please:
you ask for any error messages: but i repeat : THERE IS NO ERROR MESSAGE
i hope is more clear now
myproblem is easy to understand: open my URL "čau.lv" with your browser, and you will see that the website is not HTTPS
that it
PS: and again, i repeat this: when i install the SSL (with Cyber panel or SSH, doesn't matter) : it not displaying any error message, that a green emssage that OK is done
its more clear ?
if not, i can send screenshots so, for you see that no error and SSL installed.
and yes, i installed many time the SSL because still not HTTPS

you ask: how i get LE cert? = cyberpanel, i click on add SSL, and you ask what wrong = again one more time: nothign wrong during SLL install: just not HTTPS when i open the website

And this is what I see

1 Like

exactly: so you understand the problem or still not?
you don't see that the website is not HTTPS?

And here SSL Server Test: xn--au-dma.lv (Powered by Qualys SSL Labs)
Shows the certificate name isn’t matching

Edit

Also see the certificate being served here https://decoder.link/sslchecker/xn--au-dma.lv/443
Showing

2 Likes

Then your question is probably better suited for the Cyberpanel support channels.

I would not have a clue why Cyberpanel would install a self-signed certificate instead of the recently issued Sectigo cert :man_shrugging:

4 Likes

ok, but what i have to do for solve it?
because i know that something wrong, because if everything was OK, it will open my website with HTTPS
but i need help for solve this issue, and understand what i need to to concretly for fix it

thank you

1 Like

@Loran also look here Hardenize Report: čau.lv
As there are also DNS Zone issues as well.
I don’t believe the issue(s) your have has much to deal with Punny code.

Kindly wait to see if there are more knowledgeable Let's Encrypt community volunteers willing to assist.

1 Like

i am not sure issue is with Cyberpanel, because as i explained, i tried to add SSL certificat too with SSL and Certbot. and the same issue
so, i was thinking issue is with Let's encrypt...

yes, i think too that somethign wrong
but i wait some concret helps, and how to solve it

thanks

1 Like

Also here is a list of issued certificates crt.sh | xn--au-dma.lv (side note: Osiris did previously also pointed this out as well).
It seems that there was a switch away from Let’s Encrypt on 2024-10-15, and before that seems like it was working fine. So I suggest looking at everything that changed from that point on.

1 Like

if issue is not with Let's encrypt for sure, so someone can describe me steps by steps with details how to do with SSL directly and not through Cyber panel so?
like this, normally, it have to work if you are sure sisue is not with Let's encrypt

thank you

1 Like

it was never worked

and what was wrong so in my comamnd SSH?:
Command Cerbot = sudo certbot certonly --manual --preferred-challenges=dns --email admin@ciao.lv --server 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, error there and there, but you don't explain what is wrong and how to fix it

thanks

1 Like

If there is an issue with Let's Encrypt, there would be an error. If Certbot did not work properly, there would be an error.

But as you have no error message(s) to show, I must conclude that there is no problem with Let's Encrypt nor with Certbot.

Using the current working directory for all those directory options would not be something I'd recommend.

Also, using the manual plugin is also not something we'd recommend, as it's not easily automatable (it requires custom scripts to automate).

But luckily everything worked just fine with that command, as there were no errors as you said.

If there were no errors, as you claim, then the problem wouldn't be at Let's Encrypt, nor Certbot, but somewhere else. E.g., the installation of the issued cert in the webserver. Which is outside of the control of LE and, depending on the webserver and how Certbot is configured, outside of the control of Certbot. The certonly subcommand also means you need to manually install the issued cert in the webserver.

Also, you've removed most of the questions from the questionnaire, making it much harder (and more frustrating) for us to help you. E.g., do you have root access to your server?

3 Likes