From a4c062923954945e4eb855eb9dc4e57f34b723d7 Mon Sep 17 00:00:00 2001 From: Jeremy Lin Date: Sun, 7 Feb 2021 13:16:11 -0800 Subject: [PATCH] Updated Running a private bitwarden_rs instance with Let's Encrypt certs (markdown) --- ...-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Running-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs.md b/Running-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs.md index 22eb813..070e140 100644 --- a/Running-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs.md +++ b/Running-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs.md @@ -5,7 +5,7 @@ This article demonstrates how to create such a setup using the [Caddy](https://c Two DNS providers are covered: * [Duck DNS](https://www.duckdns.org/) -- This gives you a subdomain under `duckdns.org` (e.g., `my-bwrs.duckdns.org`). This option is simplest if you don't already own a domain. -* [Cloudflare](https://www.cloudflare.com/) -- Note that you can use Cloudflare as just a DNS provider (i.e., without the proxying functionality that Cloudflare is best known for). If you don't currently own a domain, you may be able to get a free one at [Freenom](https://www.freenom.com/). +* [Cloudflare](https://www.cloudflare.com/) -- This lets you put your bitwarden_rs instance under a domain you own or control. Note that Cloudflare can be used as just a DNS provider (i.e., without the proxying functionality that Cloudflare is best known for). If you don't currently own a domain, you may be able to get a free one at [Freenom](https://www.freenom.com/). It's certainly possible to create a similar setup using other combinations of web server, [ACME client](https://letsencrypt.org/docs/client-options/), and DNS provider, but you'll have to work out the differences in details.