SSH

SSH (Secure Shell) is the primary way to access your seedbox from the command line. You get your server address, username, and password in the welcome email after signup.

Your SSH address follows this pattern:

ssh USERNAME@SERVERNAME.pulsedmedia.com

For example, if your username is alice and your server is lt5-1-86volturno:

ssh alice@lt5-1-86volturno.pulsedmedia.com

You can find your server name in the client area under your active service, or in your welcome email.

Permissions

On shared seedboxes (V-series, M-series, Dragon-R), you have a standard user account. You do not have sudo or root access — this protects other users on the shared server. Your files live under /home/USERNAME/.

VPS and dedicated server customers get full root access to their own machine.

SSH Clients

Linux and macOS

SSH is built into the terminal. Open a terminal and connect:

ssh USERNAME@SERVERNAME.pulsedmedia.com

You will be prompted for your password. Nothing appears on screen while you type — that is normal.

Windows

Windows 10 and 11 include OpenSSH in PowerShell and Command Prompt:

ssh USERNAME@SERVERNAME.pulsedmedia.com

For a graphical client, PuTTY is free and widely used. Enter your server address in the Host Name field and click Open.

See also: WinSCP for graphical file transfers over SSH.

SSH Key Authentication

SSH keys let you log in without typing a password each time.

Generate a key pair on your local machine:

ssh-keygen -t ed25519

This creates ~/.ssh/id_ed25519 (private key) and ~/.ssh/id_ed25519.pub (public key). Never share the private key.

Copy the public key to your seedbox:

ssh-copy-id USERNAME@SERVERNAME.pulsedmedia.com

After that, SSH logins use the key instead of your password.

On Windows with PuTTY, use PuTTYgen to generate keys. Export the public key in OpenSSH format and append it to ~/.ssh/authorized_keys on the server.

SSH Config File

If you connect to your seedbox frequently, add an entry to ~/.ssh/config on your local machine:

Host seedbox
    HostName SERVERNAME.pulsedmedia.com
    User USERNAME
    Port 22

Then connect with just:

ssh seedbox

File Transfers

SFTP

SFTP runs over SSH and is available on all seedboxes. Most graphical FTP clients (FileZilla, WinSCP) support SFTP — connect on port 22 using your SSH credentials.

From the command line:

sftp USERNAME@SERVERNAME.pulsedmedia.com

SCP

Copy a file from your seedbox to your local machine:

scp USERNAME@SERVERNAME.pulsedmedia.com:/home/USERNAME/file.torrent ./

Copy a file to your seedbox:

scp localfile.txt USERNAME@SERVERNAME.pulsedmedia.com:/home/USERNAME/

For bulk downloads, Rclone or Rsync are faster. See Downloading from seedbox.

Persistent Sessions

SSH sessions end when you disconnect. For long-running commands, use screen or tmux — both are available on all seedboxes.

Start a screen session:

screen -S mysession

Detach without stopping it: press Ctrl+A then D.

Reattach later:

screen -r mysession

List running sessions:

screen -ls

tmux works the same way:

tmux new -s mysession
tmux attach -t mysession

SSH Tunneling

SSH tunneling forwards a remote port to your local machine. Useful for accessing web interfaces on non-standard ports that are not exposed publicly.

Forward remote port 8080 to your local port 8080:

ssh -L 8080:localhost:8080 USERNAME@SERVERNAME.pulsedmedia.com

Then open http://localhost:8080 in your browser while the SSH session is active.

Troubleshooting

Problem	Likely cause	Fix
Connection refused	Server name typo or wrong port	Verify server address from client area; default is port 22
Permission denied (password)	Wrong password	Reset password in client area; check Caps Lock
Connection timeout	Firewall blocking port 22	Try from a different network; some ISPs or corporate firewalls block SSH
Host key changed warning	Server was reinstalled	Verify server address is correct, then clear old key: `ssh-keygen -R SERVERNAME.pulsedmedia.com`