Connect to your Pi remotely and learn the essential commands for managing Field Day Commander.
SSH (Secure Shell) lets you control your Pi from another computer over the network. Instead of plugging a monitor and keyboard into the Pi, you open a terminal on your laptop, type a command, and you're in. Everything you type runs on the Pi. This is how you'll install Field Day Commander, check on the server, and fix things if something goes wrong during the event.
In the examples below, $ represents the terminal prompt. Type the command after it, without the $.
Windows 10 and 11 have SSH built in. Open PowerShell or Command Prompt (search for either in the Start menu) and type:
ssh your-username@fd-commander.local
Replace your-username with the account you created in Raspberry Pi Imager, and fd-commander with your Pi's hostname.
If you prefer a graphical tool, PuTTY is a free SSH client. Enter your Pi's hostname or IP address, make sure the port is 22 and the connection type is SSH, then click Open.
Open Terminal (on Mac it's in Applications > Utilities, or search for it with Spotlight). The command is the same:
ssh your-username@fd-commander.local
The first time you connect, you'll see a message about the host's authenticity:
The authenticity of host 'fd-commander.local' can't be established.
ED25519 key fingerprint is SHA256:xxxxxxxxxxxxxxxxxxx.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
Type yes and press Enter. This is normal. Your computer is recording the Pi's identity so it can verify it next time. Your computer remembers this identity for future connections.
Then enter your password. The cursor won't move while you type it. That's a security feature, not a bug. Press Enter when done.
If .local doesn't resolve, use the Pi's IP address directly: ssh your-username@192.168.1.42. You can find the IP on your router's admin page under connected devices.
Once you're connected, you're sitting in your home directory on the Pi. Here's what you need to know.
pwd /home/your-username
pwd prints the current directory. Think of directories like folders on your computer. The / separates levels, like C:\Users\You on Windows but with forward slashes.
ls fielddaycommander ls -la total 12 drwxr-xr-x 3 pi pi 4096 Jun 25 09:00 . drwxr-xr-x 3 root root 4096 Jun 25 08:45 .. drwxr-xr-x 15 pi pi 4096 Jun 25 09:02 fielddaycommander
ls lists files and folders. Add -la to see hidden files (ones starting with a dot) and details like permissions and dates.
cd fielddaycommander # go into a folder cd .. # go up one level cd ~ # go back to your home directory cd /var/log # go to an absolute path
You don't need to memorize a lot. These are the commands you'll actually use with Field Day Commander.
| Command | What It Does |
|---|---|
| ls | List files in the current directory |
| cd folder | Change into a directory |
| pwd | Print the current directory path |
| cat file.txt | Display the contents of a file |
| nano file.txt | Open a file in a simple text editor (Ctrl+O to save, Ctrl+X to exit) |
| cp file.txt backup.txt | Copy a file |
| mv old.txt new.txt | Rename or move a file |
| rm file.txt | Delete a file (no undo, be careful) |
| sudo command | Run a command as administrator |
| clear | Clear the screen |
| exit | Disconnect from SSH |
Some commands need administrator access, like installing software or restarting services. Put sudo in front of the command and enter your password when prompted. Don't use sudo for everything. Only use it when a command tells you "permission denied" or the instructions specifically say to.
Once Field Day Commander is deployed, here are the commands you'll reach for most often.
sudo systemctl status fdcommander ● fdcommander.service - FD Commander Web Server (FrankenPHP/Octane) Active: active (running) since Sat 2025-06-28 17:55:00 EDT
If it says active (running), you're good. If it says inactive or failed, restart it:
sudo systemctl restart fdcommander
The web server is one of four services the deploy script sets up. The other three are fdcommander-queue (background jobs like notifications), fdcommander-scheduler (timed tasks, including keeping external logger listeners running), and fdcommander-reverb (live updates in the browser). To check all four at once:
systemctl is-active fdcommander fdcommander-queue fdcommander-scheduler fdcommander-reverb active active active active
Each line should say active. If dashboards stop updating on their own, look at fdcommander-reverb first. Any of them can be restarted with sudo systemctl restart and the service name.
df -h / Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 29G 4.2G 24G 15% /
This shows how much space is left on the SD card. If you're uploading a lot of photos during the event, keep an eye on this.
free -h total used free Mem: 1.8Gi 512Mi 1.1Gi Swap: 99Mi 0B 99Mi
sudo journalctl -u fdcommander --since "1 hour ago" --no-pager
This shows the last hour of web server logs. Swap in another service name, like fdcommander-queue, to see that one instead. Application errors go to Field Day Commander's own log file:
sudo tail -50 /var/www/fd-commander/storage/logs/laravel.log
Sometimes you need to pull a file off the Pi (like a log file or database backup) or push one to it. Use scp from your local computer, not from the SSH session.
scp your-username@fd-commander.local:/path/to/file.log .
The . at the end means "put it in my current directory."
This only works for files your user can read. Field Day Commander's backups in /var/backups/fd-commander are readable by root only, so a plain scp of them will fail with "permission denied." The Back Up and Restore guide shows how to copy them off.
scp myfile.txt your-username@fd-commander.local:~/
The ~/ means "put it in my home directory on the Pi."
scp works in PowerShell and Command Prompt on Windows 10+. If you're using PuTTY, the equivalent tool is called WinSCP, which gives you a drag-and-drop file browser.
If your SSH connection drops after sitting idle, your terminal or SSH client may be timing out. On Mac/Linux, add this to ~/.ssh/config on your local machine:
Host *
ServerAliveInterval 60
This sends a keepalive message after 60 seconds without data from the server. See OpenSSH’s ServerAliveInterval reference for the setting and related timeout controls. In PuTTY, go to Connection and set "Seconds between keepalives" to 60.
If you need to run a long command (like a system update) and don't want it to die if your SSH connection drops, use tmux:
tmux # start a new session # run your long command here # press Ctrl+B, then D to detach tmux attach # reconnect to the session later
The command keeps running even if you close your laptop. When you SSH back in, tmux attach picks up right where you left off. The official tmux getting-started guide explains sessions, detaching, and reattaching.
You don't need to be a Linux expert to run Field Day Commander. These commands cover connecting, checking status, and basic troubleshooting. If something comes up that isn't covered here, the full documentation has more detail.
Ready to deploy? Follow Install Field Day Commander for the hostname checks and installation steps.