Name HOST2 by the hostname the key derivation actually uses, not its Tailscale spelling

This commit is contained in:
Gmer4Lfe
2026-08-16 13:07:10 -04:00
parent 0fe3435033
commit 1d4dc44668
+7 -1
View File
@@ -12,7 +12,13 @@
# #
# Key named after this server: hostname lowercased, unraid- prefix stripped. # Key named after this server: hostname lowercased, unraid- prefix stripped.
# unRAID-Gmer4Lfe → gmer4lfe_rsync_automation # unRAID-Gmer4Lfe → gmer4lfe_rsync_automation
# unRAID-Jayred365 → jayred365_rsync_automation # unRAID-Jayred36 → jayred36_rsync_automation
#
# The name comes from the OS hostname, never from Tailscale. HOST2 answers to both
# `unRAID-Jayred36` (hostname -s — Unraid truncates Server Name to the 15-char NetBIOS limit)
# and `unraid-jayred365` (its Tailscale peer name), and only the first one decides this filename.
# api/setup.php derives the same path independently when it pulls master.conf, from the same
# source — so a key created under the Tailscale spelling is a key neither of them will find.
# #
# Idempotent — skips generation if the key already exists (--force to regenerate). # Idempotent — skips generation if the key already exists (--force to regenerate).
# Updates host*.conf with the key path on success. # Updates host*.conf with the key path on success.