connor
0156055d64
42c4277 split the ssh config into common plus a host layer and restored
system76's aliases verbatim, but stubbed nas and mainframe out as having no
machine-specific aliases. Those are the two machines that run restic, and
RESTIC_REPOSITORY is sftp:storagebox:/home/restic -- so the NAS backup failed
every night from 2026-09-15 with "Could not resolve hostname storagebox",
three nights with no offsite copy.
mainframe was unaffected only by accident: its job runs as root and reads
/root/.ssh/config, which dotbot does not manage. Worth remembering before
assuming an ssh change here reaches every backup.
sub2, not sub1 -- the hosts share one Storage Box account but are chrooted
into separate sub-account homes.
20 lines
1017 B
Plaintext
20 lines
1017 B
Plaintext
# Hetzner Storage Box. Port 23, not 22 -- that is the usual first stumble.
|
|
#
|
|
# This alias is what restic-backup's RESTIC_REPOSITORY (sftp:storagebox:...)
|
|
# resolves through, so losing it takes the nightly backup down with it. It was
|
|
# dropped on 2026-09-14 by "Split ssh config into common plus a host layer",
|
|
# which restored system76's aliases verbatim but stubbed nas and mainframe out
|
|
# as having none -- the two machines that actually run restic. The NAS backup
|
|
# then failed every night from 2026-09-15 with "Could not resolve hostname
|
|
# storagebox". mainframe was unaffected only because its job runs as root and
|
|
# reads /root/.ssh/config, which is not managed by dotbot.
|
|
#
|
|
# sub2, not sub1: the two hosts share one Storage Box account but are chrooted
|
|
# into separate sub-account homes, so mainframe cannot see this repo.
|
|
Host storagebox
|
|
HostName u491382.your-storagebox.de
|
|
User u491382-sub2
|
|
Port 23
|
|
IdentityFile ~/.ssh/id_storagebox
|
|
PreferredAuthentications publickey
|