# Certbot with Nginx and IDN domain **URL:** \ **Category:** Help\ **Created:** [February 2, 2023, 5:14pm UTC](https://community.letsencrypt.org/t/certbot-with-nginx-and-idn-domain/192132 "2023-02-02T17:14:36Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jvanasco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jvanasco/32/55900_2.png) [@jvanasco](https://community.letsencrypt.org/u/jvanasco)\ **Post date:** [February 2, 2023, 5:41pm UTC](https://community.letsencrypt.org/t/certbot-with-nginx-and-idn-domain/192132/2 "2023-02-02T17:41:38Z")
I believe Certbot checks to ensure the file is served before continuing, and it cleans up afterwards. > [@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 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. The first "fix" i would try, is just to ensure it's not an IPv6 issue by dropping that down to IPv4. Some ways to do that are in this thread: > [@Certbot, force IPv4?](https://community.letsencrypt.org/t/certbot-force-ipv4/102102/8): > > I… If that doesn't work, the easiest way to handle this is to deal with 2 minutes of downtime and shutdown nginx, then run Certbot in "--standalone" mode on port 80. Certbot will bind to 80, run it's own server, and you can just copy the configuration from a working domain to this one -- referencing the correct domains. You'll still need to address the cause of this (which i do think is ipv6 related; many people have similar issues) before renewal time - but dropping to ipv4 or running certbot in standalone mode should get your site secured in the interim. --- _[View the full topic](https://community.letsencrypt.org/t/certbot-with-nginx-and-idn-domain/192132)._