From 7c0508120abf4dc8e4ef3e44637c5a9b7433b573 Mon Sep 17 00:00:00 2001 From: "fryorcraken.eth" Date: Wed, 29 Nov 2023 10:37:47 +1100 Subject: [PATCH] Use certbot certonly letsencrypt only work if a webserver is installed. We can assume if someone installed a webserver, they know what they are doing. Someone just using the docker-compose needs certbot --- docs/guides/nwaku/configure-nwaku.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/nwaku/configure-nwaku.md b/docs/guides/nwaku/configure-nwaku.md index f4fb4cd..20ea802 100644 --- a/docs/guides/nwaku/configure-nwaku.md +++ b/docs/guides/nwaku/configure-nwaku.md @@ -151,7 +151,7 @@ Consider a `nwaku` node that enabled Secure WebSocket (encrypted) using its key You can use [Let's Encrypt](https://letsencrypt.org/) or [Certbot](https://certbot.eff.org/) to generate a valid certificate for your `nwaku` node: ```shell -sudo letsencrypt -d +sudo certbot certonly -d ``` ::: @@ -255,4 +255,4 @@ When using a reverse proxy server for SSL/TLS encryption, you only want to annou :::info The `ext-multiaddr-only` option takes precedence over the `nat` and `dns4-domain-name` options, using the values provided by the `ext-multiaddr` option instead. -::: \ No newline at end of file +:::