From 0dcdbb3cb1a8749df3f12c3f0a636ddd63f624d1 Mon Sep 17 00:00:00 2001 From: On Freund Date: Mon, 24 Jun 2024 17:02:55 +0300 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Nicolas Mowen --- docs/docs/configuration/tls.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docs/configuration/tls.md b/docs/docs/configuration/tls.md index 18227ed84..89e79410e 100644 --- a/docs/docs/configuration/tls.md +++ b/docs/docs/configuration/tls.md @@ -31,6 +31,7 @@ frigate: Within the folder, the private key is expected to be named `privkey.pem` and the certificate is expected to be named `fullchain.pem`. Note that certbot uses symlinks, and those can't be followed by the container unless it has access to the targets as well, so if using certbot you'll also have to mount the `archive` folder for your domain, e.g.: + ```yaml frigate: ... @@ -40,6 +41,7 @@ frigate: ... ``` + Frigate automatically compares the fingerprint of the certificate at `/etc/letsencrypt/live/frigate/fullchain.pem` against the fingerprint of the TLS cert in NGINX every minute. If these differ, the NGINX config is reloaded to pick up the updated certificate. If you issue Frigate valid certificates you will likely want to configure it to run on port 443 so you can access it without a port number like `https://your-frigate-domain.com` by mapping 8080 to 443.