Connection¶

Settings → Connection sets how ROMKADE Manager reaches the console. The first setup is described step by step in Connecting your console; this page covers the details and later changes.

Fields¶

Field	Default	Notes
IP address or hostname	—	Can change after the router restarts: reserve it in the router (DHCP reservation).
SSH port	`22`
User	—	Often `root` on handheld firmwares.
Authentication	Password	Password or SSH key. The last field changes accordingly.
ROMs folder	depends on the firmware	`/mnt/mmc/Roms` on Anbernic. Settings → System offers the folder found on the console.

Password or SSH key¶

Password: saved with Save to keychain (with Docker, in the data volume; otherwise in the system keychain). It is never displayed again; Replace the password changes it.
SSH key: enter the path of the private key (for example ~/.ssh/id_ed25519 from the source code). Its public key must be in ~/.ssh/authorized_keys on the console:
```
ssh-copy-id -i ~/.ssh/id_ed25519.pub root@192.168.1.42
```

SSH key with Docker¶

ROMKADE Manager runs in a container: it only sees its data volume, not your computer's ~/.ssh folder. Copy the private key into the volume once, from the romkade folder (macOS, Linux, or WSL on Windows):

docker compose exec -T romkade sh -c 'cat > /data/id_ed25519 && chmod 600 /data/id_ed25519' < ~/.ssh/id_ed25519

Then enter /data/id_ed25519 as Private key path. The key stays in the volume, readable only by the container's account. On Windows without WSL, the password is simpler.

Console identity¶

The console's SSH key is checked at every connection. The first time, you compare its fingerprint and approve it. If it changes later, the connection is blocked: ROMKADE Manager will not talk to a device it does not recognize.

To approve a new key after a legitimate change (firmware reinstalled, new card), check the fingerprint again with ssh-keyscan as on first setup, then approve it.

Each console has its own identity: favorites are attached to it.

Connection test¶

Settings → Connection test → Test checks, in order:

Step	Checks	Typical fix
Network (port 22)	The console answers on the network	Console on, same Wi-Fi, correct address
SSH server	An SSH server answers	Turn SSH on in the console's settings
Console key	The key is the approved one	Approve it (step 2) or check why it changed
Credentials	User and password or key are accepted	Update the password or the key
Command on the console	A simple command runs	—
ROMs folder	The folder exists	Fix the path; check the card is in place

When a step fails, the next ones are not tested, and the page says what to do. Nothing is changed on the console.

Connection behavior¶

A single SSH connection is shared by all features and kept open 90 seconds after its last use. If the console stops answering, the following requests fail right away for 15 seconds instead of each waiting for a timeout.