The one thing to understand first
Turning Remote access ON on a device only makes that device reachable. It does not hand you a link or command to type somewhere else, and it does not install or start an SSH server for you. You actually connect from another of your own Foldpair devices, and the device you’re reaching must already be running an SSH server. Both steps are below.
What it is (and isn’t)
- It is a private, relayed SSH pipe between two devices signed into the same Foldpair account. Both devices make outbound connections to Foldpair’s relay; Foldpair does not require you to expose an SSH port to the internet.
- It isn’t a way to SSH in from a random computer that doesn’t have Foldpair. The machine you connect from must be running Foldpair and signed into the same account. There’s no public hostname or password to hand to an outsider.
- The relay still forwards SSH (port 22) only. The desktop app can also generate a Remote Desktop Bridge command that keeps VNC or Screen Sharing inside end-to-end encrypted SSH. VNC is never sent directly through the relay.
Before you begin — two things you need
1. A second Foldpair device
You connect from one of your devices to another. Both must be signed into the same Foldpair account and running the app.
2. An SSH server on the device you’re reaching
Foldpair bridges to that device’s own SSH server on port 22 — it does not start one for you. Turn it on there:
| Device you’re reaching | How to turn on its SSH server |
|---|---|
| macOS | System Settings → General → Sharing → turn on Remote Login. Note the line “Users can access this Mac at name@…” — that name is your SSH username. |
| Windows | Find Optional features in Windows Settings and install OpenSSH Server if needed. Then open Services and start OpenSSH SSH Server. The Settings path varies by Windows version. |
| Linux | Install your distribution’s OpenSSH server package. On Debian or Ubuntu, enable the installed openssh-server service with sudo systemctl enable --now ssh. Package and service names can differ on other distributions. |
Step 1 — On the device you want to reach
- Turn on that device’s SSH server. See the table above. On macOS that’s Sharing → Remote Login.
- In Foldpair, open Settings and turn Remote access ON. It applies immediately — the device switches to reachable.
- Leave Foldpair running. Connect from another device in your account using the steps below.
Step 2 — On the device you connect from
- Open Foldpair and go to the Devices tab.
- Find the device you want to reach and click Connect. Foldpair opens the tunnel and provides an SSH command in the connection dialog and clipboard. For example:
ssh -p 52345 -l 'admin' 127.0.0.1 - Check the username in the command. If it contains
REMOTE_USERNAME, the tunnel is ready but the remote computer did not report a username. Replace that placeholder with the remote computer’s operating-system login name, or update Foldpair on that computer. If no tunnel opens, check that the remote computer is online, Foldpair is running, and Remote access is enabled. - Paste it into a terminal on this same connecting device and press Enter. The
127.0.0.1port exists only on the computer where you clicked Connect, so run the command on that computer. Running it on the remote computer or a third device will not use this tunnel. Foldpair accepts a new SSH host key on first use and rejects a changed key. Then sign in with the target device’s password or SSH key.
That’s it. From SSH’s point of view it’s a normal login to 127.0.0.1; Foldpair carries the bytes to your other device behind the scenes.
Remote Desktop Bridge (Windows, macOS, and Linux)
The same connection dialog shows a Remote desktop · VNC inside SSH command. Select the remote service preset and its actual loopback port separately from the viewer on this device. Windows currently defaults to the existing VNC display :8 at 127.0.0.1:5908; macOS Screen Sharing and Linux VNC default to 127.0.0.1:5900. Edit the port when the target uses another VNC display.
- Run the generated
ssh -N -Lcommand on the connecting computer and keep its terminal open. - Use TigerVNC Viewer on Windows, macOS, or Linux at the shown address, such as
127.0.0.1::15908, or choose macOS Screen Sharing and open the shownvnc://127.0.0.1:15900address. - Close that terminal to stop the desktop bridge. Press Disconnect in Foldpair to close the underlying relay endpoint.
Use Standard Screen Sharing over this bridge. Apple High Performance Screen Sharing also requires UDP and is not carried by the TCP-only ssh -L forward.
VNC never crosses the relay by itself. Foldpair still allows only SSH port 22, and the screen/input stream remains inside end-to-end encrypted SSH.
The port changes every time
The port number (-p 52345) is assigned fresh each time you click Connect. If you reconnect later, use the new command Foldpair gives you — not an old one.
If it won’t connect
| What you see | What it means & how to fix it |
|---|---|
Connection closed right after you type yes to the host-key prompt — on the first connection |
The tunnel may have timed out while you checked the host key. If you verified and accepted the key, run the command again. If the connection still closes, check that the remote computer’s SSH server and Foldpair are running. |
kex_exchange_identification: Connection closed by remote host, or it closes with no login prompt |
The connection closed before SSH sign-in. Check that the remote computer’s SSH server is running (macOS: Remote Login; Windows: OpenSSH Server service; Linux: sshd). This error alone does not identify the cause; also check Foldpair’s connection status. |
| It hangs, or Foldpair says the device “did not respond” | The other device isn’t reachable. Make sure Remote access is ON and Foldpair is running on the device you’re reaching. |
Permission denied after a login prompt appears |
The tunnel works; SSH sign-in failed. Use the correct username for that device and its password or SSH key. Foldpair only carries the connection — it doesn’t manage SSH credentials. Windows sign-in checks → |
| No Connect button on a device | That’s this device (you can’t connect to yourself), or it isn’t a device on your account. Use it from a different device in your account. |
Windows rejects the SSH password
If SSH asks for a password and then shows Permission denied, the connection has reached an SSH server. Check the Windows sign-in details first:
- Check the username on the Windows PC you are connecting to. Open Command Prompt or PowerShell as the intended user and run
whoami. For a local account,desktop-example\alexmeans the username isalex. Use the actual account name, even if it is shorter than the display name. Domain accounts may need the fulldomain\username. - Use the account password. A Windows Hello PIN, fingerprint, or face sign-in is not an SSH password. For a Windows account linked to a Microsoft account, use that Microsoft account’s password for password authentication.
- If there is no usable password, use a configured SSH key or ask the PC administrator for help. Windows blocks remote password sign-in with a blank local-account password by default. Keep that protection enabled.
Microsoft documentation: whoami · OpenSSH.
What keeps it private
By design
- · No inbound port forwarding required — both devices connect outward to the relay.
- · The local listener binds to
127.0.0.1only, so nothing else on your network can use it. - · Same-account only — the relay brokers a pipe only between two devices on your account, and only to SSH (port 22).
- · The relay never inspects or decrypts the stream — SSH stays end-to-end between your two devices.
Good to know
- · Turning Remote access off on the remote computer closes its remote-access relay connection immediately.
- · SSH still enforces its own login (password or key). Foldpair decides who can reach the port; SSH decides who can log in.
- · Related reading: how Foldpair encryption works.
How it works underneath
You never touch any of this — the app does it for you — but if you like knowing what’s happening:
- Reachable device (Remote access ON): the Foldpair agent holds a long-lived control connection open to the relay, marking the device online for remote access. It opens no listening port.
- Connecting device (clicks Connect (SSH)): the agent binds a loopback-only TCP listener on
127.0.0.1:<random port>and prints thesshcommand. - On your first SSH byte, the relay brokers an opaque byte pipe between the two agents; the reachable agent dials its own
127.0.0.1:22(the SSH server) and bridges the bytes. The relay never terminates or reads the SSH stream.