# \#certbot

**URL:** https://community.nginx.org/tag/certbot/179.md

[Latest](https://community.nginx.org/latest.md) · [Categories](https://community.nginx.org/categories.md) · [Tags](https://community.nginx.org/tags.md)

---

## [Handle dir with trailing dot](https://community.nginx.org/t/handle-dir-with-trailing-dot/7610)

<div class="topic-metadata">

**Author:** [@HGA](https://community.nginx.org/u/HGA)\
**Replies:** 3\
**Last updated:** [October 20, 2025, 2:46pm UTC](https://community.nginx.org/t/handle-dir-with-trailing-dot/7610 "2025-10-20T14:46:14Z")

</div>

I figured out that I have a problem with getting an certificate from Let’s Encrypt, via certbot. They are trying to generate a dir “.well-known” and read it via URL. So i generated this directory an in the Configuration…

---

## [Organizing common configs in multiple server blocks](https://community.nginx.org/t/organizing-common-configs-in-multiple-server-blocks/3189)

<div class="topic-metadata">

**Author:** [@sodhia.rohit](https://community.nginx.org/u/sodhia.rohit)\
**Replies:** 1\
**Last updated:** [May 19, 2025, 10:53pm UTC](https://community.nginx.org/t/organizing-common-configs-in-multiple-server-blocks/3189 "2025-05-19T22:53:39Z")

</div>

I’ve got a domain that largely got setup by certbot: server { root /var/www/mydomain.com; index index.html; server\_name mydomain.com www.mydomain.com; location / { try\_files $uri $uri/ =404; …

---

## [Uncertain non-www https redirect is right](https://community.nginx.org/t/uncertain-non-www-https-redirect-is-right/1373)

<div class="topic-metadata">

**Author:** [@thumos](https://community.nginx.org/u/thumos)\
**Replies:** 5\
**Last updated:** [March 21, 2025, 9:53am UTC](https://community.nginx.org/t/uncertain-non-www-https-redirect-is-right/1373 "2025-03-21T09:53:49Z")

</div>

My web server is Nginx 1.22.1, run on Debian 12 virtual server, accessed over ssh. Below is the relevant part of my config for all server blocks. It was created by Certbot, except I added www. to the line return 301 ht…