UNAS: SSH key auth + git-tracked config repo #5

New Issue

2026-05-23T09:22:15Z

fkrebs commented

2026-05-23 09:22:15 +00:00

Goal

Track UNAS Pro (192.168.1.31) configuration in Gitea, like the other config repos (zoraxy-conf, adguard-conf, etc.). Also needed for NFSv4 automation.

Blocker

SSH on UNAS Pro requires key-based auth. Nuc pubkey has NOT been added to UNAS yet.

Step 1 (manual — needs UNAS web UI):

Open UNAS admin UI (http://192.168.1.31 or UniFi app)
Go to Settings → SSH Keys
Add contents of /root/.ssh/id_rsa.pub from nuc

Step 2 — verify:

ssh root@192.168.1.31 "uname -a"

Step 3 — create sync script on nuc:

mkdir -p /tmp/sync-unas
ssh root@192.168.1.31 "cat /etc/exports; nfs-status; showmount -e" > /tmp/sync-unas/nfs-exports.txt
# + any other relevant UNAS config

Create Gitea repo fkrebs/unas-conf and add to sync-config-repos cron.

Step 4 — NFSv4 check/enable:
Once SSH works, verify UNAS NFSv4 status and enable if off. Update /etc/fstab on nuc to vers=4. Add watchdog timer per memory/unas-ssh-rsync.md plan.

## Goal Track UNAS Pro (192.168.1.31) configuration in Gitea, like the other config repos (zoraxy-conf, adguard-conf, etc.). Also needed for NFSv4 automation. ## Blocker SSH on UNAS Pro requires key-based auth. Nuc pubkey has NOT been added to UNAS yet. **Step 1 (manual — needs UNAS web UI):** 1. Open UNAS admin UI (http://192.168.1.31 or UniFi app) 2. Go to Settings → SSH Keys 3. Add contents of `/root/.ssh/id_rsa.pub` from nuc **Step 2 — verify:** ```bash ssh root@192.168.1.31 "uname -a" ``` **Step 3 — create sync script on nuc:** ```bash mkdir -p /tmp/sync-unas ssh root@192.168.1.31 "cat /etc/exports; nfs-status; showmount -e" > /tmp/sync-unas/nfs-exports.txt # + any other relevant UNAS config ``` Create Gitea repo `fkrebs/unas-conf` and add to `sync-config-repos` cron. **Step 4 — NFSv4 check/enable:** Once SSH works, verify UNAS NFSv4 status and enable if off. Update `/etc/fstab` on nuc to `vers=4`. Add watchdog timer per memory/unas-ssh-rsync.md plan. ## Related - fkrebs/docs #2 (NFS v3→v4 on nuc fstab side) - Memory: unas-ssh-rsync.md (SSH password: stored in memory for manual UI login)

fkrebs closed this issue

2026-05-23 09:28:36 +00:00

fkrebs commented

2026-05-23 09:28:36 +00:00

Resolved:

SSH key auth: added nuc public key to UNAS /root/.ssh/authorized_keys via password SSH (old creds from memory). Key-based auth now works from nuc.
Gitea repo fkrebs/unas-conf created with initial snapshot: nfs-exports.conf, nfs-shares.json, nfs-versions.txt, disk-usage.txt, exportfs-active.txt, cron.txt, os-version.txt.
Daily cron at 03:20 on nuc (/etc/cron.d/sync-unas-conf).

NFSv4 upgrade (issue #2) is a separate item: UNAS Pro already has NFSv4 kernel support but no fsid=0 root export configured. The export path is managed by UniFi OS JSON — cannot safely add fsid=0 without risk of overwrite. Leaving as backlog.

Resolved: - SSH key auth: added nuc public key to UNAS `/root/.ssh/authorized_keys` via password SSH (old creds from memory). Key-based auth now works from nuc. - Gitea repo `fkrebs/unas-conf` created with initial snapshot: nfs-exports.conf, nfs-shares.json, nfs-versions.txt, disk-usage.txt, exportfs-active.txt, cron.txt, os-version.txt. - Daily cron at 03:20 on nuc (`/etc/cron.d/sync-unas-conf`). NFSv4 upgrade (issue #2) is a separate item: UNAS Pro already has NFSv4 kernel support but no `fsid=0` root export configured. The export path is managed by UniFi OS JSON — cannot safely add fsid=0 without risk of overwrite. Leaving as backlog.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fkrebs/docs#5