Correct Tower SSH port documentation

2026-07-08 02:34:41 +02:00
parent bad378e507
commit 48ffcd0991
2 changed files with 4 additions and 5 deletions
@@ -5036,13 +5036,13 @@ Assessment:
 - Threshold `0.25` is the safest observed operating point for the current candidate.
 - The next product step should be model-selection and threshold workflow hardening before any operator-facing default activation.

-Operational issue:
- Tower root SSH became unavailable after training. The key `widefrog_unraid_deploy` was offered, but the server returned `Permission denied (publickey)`.
- This blocks Codex-driven host-side deploy/sync until the Tower root `authorized_keys` entry is restored.
+Operational note:
+- Tower root SSH works with `widefrog_unraid_deploy` on the default SSH port `22`.
+- Gitea SSH works separately on port `222` through the `gitea-widefrog` host alias and `widefrog_gitea` key.
+- Do not test Unraid/root deploy access against port `222`; that port belongs to Gitea and correctly rejects `root`.
 - Live HTTP API verification on `http://192.168.10.150:1202` remained reachable.

 Open:
- Restore root SSH access on Tower for `widefrog_unraid_deploy`.
 - Add an operator-facing model selection/activation flow or documented command that can promote a chosen local model deliberately, with visible SHA256 and threshold guidance.
 - Add more negative/background AOIs and a threshold calibration benchmark before activating this model by default.