From 7c426448f04efbb7b97f3e4598bf00aaafea04af Mon Sep 17 00:00:00 2001 From: docgalaxyblock Date: Sun, 10 Mar 2024 21:45:37 +0100 Subject: [PATCH] Updated Private CA and self signed certs that work with Chrome (markdown) --- ...e-CA-and-self-signed-certs-that-work-with-Chrome.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Private-CA-and-self-signed-certs-that-work-with-Chrome.md b/Private-CA-and-self-signed-certs-that-work-with-Chrome.md index aee337b..a8a2155 100644 --- a/Private-CA-and-self-signed-certs-that-work-with-Chrome.md +++ b/Private-CA-and-self-signed-certs-that-work-with-Chrome.md @@ -1,6 +1,10 @@ -:warning: :poop: :warning: This method is for testing and development only. The vast majority of users should not use this method, as it requires loading a cert on each of your devices, which is both error-prone and requires future maintenance. Instead, focus your energy on obtaining real certs via [Let's Encrypt](https://letsencrypt.org/getting-started/). This can even work if your vaultwarden instance is not on the public Internet ([[example|Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs]]). - -:skull_and_crossbones: :skull_and_crossbones: :skull_and_crossbones: This method is not supported. Please do not open GitHub issues or post on the discussion forums asking about how to get this to work. +> [!WARNING] +>

⚠️ 💩 ⚠️

+> +>

This method is for testing and development only.
The vast majority of users should not use this method, as it requires loading a cert on each of your devices, which is both error-prone and requires future maintenance.
Instead, focus your energy on obtaining real certs via Let's Encrypt.
This can even work if your vaultwarden instance is not on the public Internet (example).

+> +>

☠️ ☠️ ☠️

+>

This method is not supported.
Please do not open GitHub issues or post on the discussion forums asking about how to get this to work.

---