From 020f5d321fed46f99b3cad27f6e532f38f2aa490 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= Date: Tue, 18 Jan 2022 12:24:22 +0100 Subject: [PATCH] pveproxy: improve TLS key override description MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit by explicitly stating that this only applies to the 'custom' certificate key, not the built-in self-signed one.. Signed-off-by: Fabian Grünbichler --- pveproxy.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pveproxy.adoc b/pveproxy.adoc index 8fc6195..663b069 100644 --- a/pveproxy.adoc +++ b/pveproxy.adoc @@ -178,8 +178,9 @@ pveproxy uses `/etc/pve/local/pveproxy-ssl.pem` and `/etc/pve/local/pve-ssl.pem` and `/etc/pve/local/pve-ssl.key`. The private key may not use a passphrase. -It is possible to override the location of the certificate private key by -setting `TLS_KEY_FILE` in `/etc/default/pveproxy`, for example: +It is possible to override the location of the certificate private key +`/etc/pve/local/pveproxy-ssl.key` by setting `TLS_KEY_FILE` in +`/etc/default/pveproxy`, for example: TLS_KEY_FILE="/secrets/pveproxy.key"