mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-25 19:29:21 -07:00
Updated Running a private bitwarden_rs instance with Let's Encrypt certs (markdown)
@@ -111,12 +111,12 @@ You should now be able to reach your bitwarden_rs instance at https://bwrs.examp
|
|||||||
|
|
||||||
## Getting certs using the `lego` CLI
|
## Getting certs using the `lego` CLI
|
||||||
|
|
||||||
In the DuckDNS example above, Caddy used the [`lego`](https://github.com/go-acme/lego) library to get certs via DNS challenge.
|
In the DuckDNS example above, Caddy used the `lego` library to get certs via DNS challenge.
|
||||||
`lego` also has a CLI that you can use to get certs directly, e.g. if you want to a reverse proxy other than Caddy.
|
`lego` also has a CLI that you can use to get certs directly, e.g. if you want to use a reverse proxy other than Caddy.
|
||||||
|
|
||||||
Here's an example of how to do this:
|
Here's an example of how to do this:
|
||||||
|
|
||||||
1. Download a pre-built `lego` binary for your system from https://github.com/go-acme/lego. Extract the contents to some directory, say, `/usr/local/lego`.
|
1. Download a pre-built `lego` binary for your system from https://github.com/go-acme/lego/releases. Extract the contents to some directory, say, `/usr/local/lego`.
|
||||||
2. From that directory, run `DUCKDNS_TOKEN=<token> ./lego -a --dns duckdns -d my-bwrs.duckdns.org -m me@example.com run`,
|
2. From that directory, run `DUCKDNS_TOKEN=<token> ./lego -a --dns duckdns -d my-bwrs.duckdns.org -m me@example.com run`,
|
||||||
substituting appropriate values for the token, domain, and email address. This registers you with Let's Encrypt and
|
substituting appropriate values for the token, domain, and email address. This registers you with Let's Encrypt and
|
||||||
fetches a certificate for your domain.
|
fetches a certificate for your domain.
|
||||||
|
|||||||
Reference in New Issue
Block a user