RIFT CONDUIT 2.0 · OFFICIAL CONNECTION GUIDE

Your connection,
step by step.

Set up access on your Windows server, choose a client for your other computer, and connect to your own files over encrypted SFTP.

Save a complete HTML copy to read offline. Published by AI Creations Now Software Development.

One connection. Two computers.

Know which side you’re setting up.

Your login details are in the separate Desktop credentials file created on the server. Keep that file secure: it contains the account password.

The server · where your files live

Run Rift Conduit here.

On the Windows computer holding your files, set Allowed IP to the client’s source IPv4 address. For direct internet access, this is usually the public IPv4 address of the location you connect from.

The client · where you connect from

Install your SFTP client here.

On your other computer, set the client’s Host / Server to the server’s reachable IPv4 address. Use the server’s Tailscale IPv4 when connecting through a separately configured Tailscale network.

Make the connection

From ready status to your files.

  1. Prepare the server.

    Open Rift Conduit on the server and enter the client’s source IPv4 in Allowed IP. Leave the Tailscale option checked if you use it. Select Turn On and wait for the ready status.

    Setup prepares OpenSSH from its bundled local Windows feature source. Turn On checks those components without installing or downloading them. If OpenSSH is missing, repair the signed Rift Conduit installation first.

  2. Choose a client for your other computer.

    Install a client using one of the official vendor links below. A file browser such as WinSCP or FileZilla Client lets you manage files in a separate window. A remote-drive application such as RaiDrive can make the server available through your computer’s file manager.

    WinSCP is a simple Windows file browser. FileZilla Client works on Windows, Mac and Linux. RaiDrive can show the server as a drive in Windows File Explorer.

  3. Add an SFTP connection.

    Use the connection settings below. Enter the server account from your Desktop credentials file, or an authorized existing local account. Use the account’s password, not a Windows Hello PIN.

    If using an existing local administrator account, complete the one-time account authorization first. Administrator membership alone does not authorize SFTP access.

  4. Confirm the server’s host key.

    Before accepting the first connection, compare the host-key fingerprint shown by your client with the fingerprint in your credentials file. If using an existing account, obtain the matching fingerprint from the server administrator through a trusted channel.

    Check any unexpected host-key change before accepting it. Once the key matches, connect and work with the files your Windows account can access.

Your connection details

The same settings, whichever client you choose.

Field names vary between clients. These are the values to use for a Rift Conduit connection.

SFTP client settings
ProtocolSFTP — SSH File Transfer Protocol.
Host / ServerThe server’s reachable IPv4 address. For Tailscale, use the server’s Tailscale IPv4 address.
Port22 (TCP).
Username / PasswordThe server account in your separate Desktop credentials file, or your authorized existing local account. Use the account password, not a Windows Hello PIN.
Remote path/C:/ if your client requests a starting path.
Drive letterAn unused letter, such as Z:, if you are mounting a remote drive in Windows.
Host-key fingerprintVerify it against the credentials file, or a matching fingerprint supplied by the server administrator through a trusted channel, before accepting the first connection.

Use an account you already have

Authorize an existing local administrator.

Accounts created through Rift Conduit retain SFTP access through upgrades, Turn Off and reinstalls unless an administrator changes their membership. For a different existing local administrator account, authorize it once using these steps.

On the Windows server

Official client downloads

Connect the way you work.

These are separate third-party applications. Use the same SFTP settings with each client. Mac and Linux clients can access your Windows server. Confirm each vendor’s current system requirements, pricing, licensing and terms.

File browsers

Copy and manage files in a dedicated window.

WinSCP

Windows

Free/open source

A dedicated file browser for your SFTP connection.

Get WinSCP

FileZilla Client

Windows · Mac · Linux

Free/open source

Browse and transfer files using the Client application.

Get FileZilla Client

SecureFX

Windows · Mac · Linux

Paid/trial

A separate file-transfer client for an SFTP workflow.

Get SecureFX

Termius

Windows · Mac · Linux

Free option

Use its SFTP browser to access your files. Rift Conduit provides SFTP access, not an SSH terminal.

Get Termius

Transmit

Mac

Paid/trial

A Mac file-transfer application with SFTP connections.

Get Transmit

Remote drives

Open remote files through your computer’s file manager. Rift Conduit provides the server connection; your chosen client mounts the drive.

RaiDrive

Windows · Linux CLI

Free option with ads

Make a supported SFTP connection available as remote storage.

Get RaiDrive

ExpanDrive

Windows · Mac · Linux

Free personal use, paid business plans

Connect SFTP storage through your computer’s file manager.

Get ExpanDrive

WebDrive

Windows · Mac

Paid/trial

Use a remote-drive client for your SFTP storage.

Get WebDrive

SFTP Drive / Callback Drive

Windows · Linux

Paid/trial

Access SFTP storage using the vendor’s remote-drive software.

Get SFTP Drive

rclone

Windows · Mac · Linux

Free/open source

An advanced command-line option. Apply the SFTP-only settings below and review its platform-specific mount requirements.

Get rclone

Reachability & everyday use

A few checks keep the connection clear.

  • Connecting through TailscaleSet up Tailscale on both computers separately. Use the server’s Tailscale IPv4 in your client. Rift Conduit’s Tailscale checkbox allows 100.64.0.0/10; it does not install or configure Tailscale.
  • Connecting over the internetA direct internet connection may need router forwarding for TCP port 22 and a restricted cloud-firewall rule. Confirm the server is reachable and the client’s source IPv4 matches Allowed IP.
  • If login failsCheck both IP addresses, port 22, the account password and the account’s SFTP access-group membership. Confirm that Rift Conduit shows its ready status.
  • Working with server filesWindows file permissions still apply. Remote edits change the real files on the server, so use an account with appropriate access and protect its credentials.
  • Closing the windowExit Application leaves the listener running. Closing the GUI is not the same as turning off SFTP access.
  • Stopping accessSelect Turn Off to stop this app’s service and remove its own firewall rules. Your accounts and settings remain.