From b5067bf7e974590ca312e9394b5ec7de127a7baa Mon Sep 17 00:00:00 2001 From: decentral1se Date: Wed, 30 Mar 2022 11:46:45 +0200 Subject: [PATCH] more ssh user/port help --- docs/operators/handbook.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/operators/handbook.md b/docs/operators/handbook.md index c9943ba..3aa9597 100644 --- a/docs/operators/handbook.md +++ b/docs/operators/handbook.md @@ -295,3 +295,15 @@ Also, for more system wide analysis stuff: - `journalctl --disk-usage` - `du -sh /var/log/journal/*` - `man journalctl` / `man systemd-journald` / `man journald.conf` + +## How do I specify a custom user/port for SSH connections with `abra`? + +`abra` uses plain 'ol SSH under the hood and aims to make use of your existing SSH configurations in `~/.ssh/config` and interfaces with your running `ssh-agent` for password protected secret key files. + +The `server add` command listed above assumes that that you make SSH connections on port 22 using your current username. If that is not he case, pass the new values as positional arguments. See `abra server add -h` for more on this. + +```bash +abra server add -p +``` + +Running `server add` with `-d/--debug` should help you debug what is going on under the hood. It's best to take a moment to read [this troubleshooting entry](/abra/trouble/#ssh-connection-issues) if you're running into SSH connection issues with `abra`.