From 49ed1ba89566f5682a51b02031479e29968f5b10 Mon Sep 17 00:00:00 2001 From: Blake Bryant Date: Wed, 28 Feb 2024 00:20:28 -0800 Subject: [PATCH] Add final step to enabling https on home server (#322) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sounds like I'm not the only one that has run into this issue 😄 --------- Co-authored-by: Matiss Janis Aboltins --- docs/config/https.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/config/https.md b/docs/config/https.md index 0b36e3a9ae..cdd5bf48aa 100644 --- a/docs/config/https.md +++ b/docs/config/https.md @@ -28,3 +28,5 @@ Once you have the certificate, you’ll need to configure Actual to use it. Ther } ``` 2. **Configuring with environment variables**: If you can’t easily create new files, you can also configure HTTPS using environment variables. Set the `ACTUAL_HTTPS_KEY` and `ACTUAL_HTTPS_CERT` environment variables to the contents of the `.key` and `.crt` files, respectively. If you’re unable to include newlines in the environment variable values, you can replace any newlines with `\n` and Actual will automatically convert them back to newlines. + +Once one of the above configuration methods have been applied, make sure to access your instance using `https` instead of refreshing the web page.