Hi, my webserver runs Nginx. Obtaining certificates for the other domains that I run there also works fine with Certbot. I have one German .de Domain with an Umlaut (ä, ö, ü, ß). This one is also configured correctly, with the punycode name in the Nginx config, DNS works, I can access it over HTT…

[image] s3b: I see the request incoming via IPV6 in the Nginx access.log and error.log. It ends in a 404 because the files are not served. So IPV6 works. IPv6 may be "working". But that is only proof of the networking part of the equation. The appearance in the logs may be misleading. If t…

I believe Certbot checks to ensure the file is served before continuing, and it cleans up afterwards. [image] s3b: So it looks like Certbot does not find the server root and could not write the file in .well-known/acme-challenge/. If it would have Can I supply it manually? I think the issue …

You might want to check the syntax of the domain name itself [image] Domain name contains invalid character Help A…

[image] jvanasco: I think the issue is due to LetsEncrypt not being able to hit the domain via IPv6 routing. A lot of things could cause that. I would try dropping the host to IPv4 during setup if possible. I see the request incoming via IPV6 in the Nginx access.log and error.log. It ends in …

And from here What are the valid characters for a domain name and how long can a domain name be? - Knowledgebase - Save On Hosting and here as well https://www.nic.sl/domain/html/rules "The only symbol character domain names can include is a hyphen (-) although the domain name cannot start or end w…

That's just an example encoded with punycode, as Certbot requests it. This domain would not even have a hyphen. xn--exampledomainwithan-obc.de = exampledomainwithanü.de It's encoding the Ü.

[image] Bruce5051: Your example is showing consecutive hyphens. First, that resource is not entirely correct and misleading. The OP shared the punycode encoding of an Internationalized Domain Name (IDNA), which is slightly related to Emoji Domains. Domain names are locked to the ASCII chara…

Thanks @jvanasco :slight_smile:

[image] s3b: I see the request incoming via IPV6 in the Nginx access.log and error.log. Are you sure the IP is external? Certbot does have a --manual flag, which will prompt you to manually enter the challenge file. You could do that to bugtest your setup against the staging server and see …

[image] Bruce5051: Thanks @jvanasco :slight_smile: NP. Themoreyouknow Star GIF - Themoreyouknow Star Rainbowstreak - Discover & Share GIFs I got tripped up on the same things too the first time I hosted a punycode domain. "WTF? Two Dashes? AM I HACKED? THIS IS IMPOSSIBLE!"

Kind of seems like ASCII - Wikipedia already had the concept of shifting In and Out of character set. 000 1110 016 14 0E SO ␎ ^N Shift Out 000 1111 017 15 0F SI ␏ ^O Shift In 001 1011 033 27 1B S3 ESC ␛ ^[ \e Escape

Certbot with Nginx and IDN domain

Help

Bruce5051 February 2, 2023, 5:43pm 3

You might want to check the syntax of the domain name itself

Topic		Replies	Views
Challenge failed for domain while creating certbot. Tried common solutions Help	11	1372	December 5, 2020
Certbot failed to authenticate some domains (authenticator: nginx) Help	9	3154	May 8, 2022
Requesting a certificate fails with "Some challenges have failed." Help	3	122	October 5, 2024
"Domain name contains an invalid character" for some IDN TLDs Help	5	119	March 25, 2026
Obtaining a certificate Help	2	342	January 11, 2024

Certbot with Nginx and IDN domain

Related topics