Move Files To or From a Server When Copy/Paste Is Blocked

TL;DR — If copy and paste is blocked in your remote desktop, bastion host, or browser console, do not fight the clipboard. Move the file with a file transfer method instead: your hosting provider's File Manager if it has one, or SFTP/SCP if it does not. The single most common fix is to use SFTP with the server's hostname, port 22, your username, and either your password or SSH key. Reading time: ~5 min

Goal

When you finish, the file will be on the server in the folder you chose, or on your computer if you are downloading it, and you will be able to confirm its size and name from both sides.

Prerequisites

• Your server login details: hostname or IP address, username, and either password or SSH key (a login file used instead of a password)
• Access to your hosting provider's dashboard or control panel, if your provider offers a File Manager
• A file transfer app on your computer if you are not using the dashboard:
  • Windows: WinSCP or FileZilla Client
  • macOS or Linux: Terminal app for scp, or FileZilla Client
• If using scp, OpenSSH installed:
  • Check with:

ssh -V

• The exact source file path and destination folder path
• Enough free space on the destination system for the file

Steps

Step 1: Try the provider dashboard File Manager first

Open your provider's dashboard and look for a file browser. Common menu paths are one of these:

• Hosting Dashboard → File Manager
• Server → Files
• Website → File Manager
• Control Panel → File Manager
• In cPanel: Files → File Manager
• In Plesk: Websites & Domains → File Manager

If you are uploading a file, click the destination folder, then click Upload and select the file from your computer.

If you are downloading a file, select the file, then click Download.

What you should see when this succeeds: the file appears in the folder list with the expected name and size, or your browser downloads the file to your computer.

Step 2: Use SFTP if the dashboard does not have file upload/download

SFTP (SSH File Transfer Protocol, a secure file transfer method) is the best general option when clipboard transfer is blocked.

Open your SFTP app and enter these exact connection values:

If you use an SSH key instead of a password, add your private key file in the app's login settings.

In FileZilla Client, the menu path is:

• File → Site Manager → New Site
• Protocol: SFTP - SSH File Transfer Protocol
• Host: your-server-hostname-or-ip
• Port: 22
• Logon Type: Normal or Key file
• User: your-username
• Password: your-password if using password login
• Click Connect

In WinSCP, the menu path is:

• New Tab → File protocol: SFTP
• Host name: your-server-hostname-or-ip
• Port number: 22
• User name: your-username
• Password: your-password
• Click Login

Then drag the file:

• From your computer pane to the server pane to upload
• From the server pane to your computer pane to download

What you should see when this succeeds: the transfer queue shows Successful transfers: 1, and the file appears in the destination folder.

Step 3: Use scp from Terminal if you prefer commands

If you have Terminal access on your computer, scp (secure copy) is the fastest command-line option.

To upload a file from your computer to the server:

scp /path/to/local-file.txt your-username@your-server-hostname-or-ip:/path/to/remote-folder/

Example:

scp ~/Downloads/report.pdf deploy@example.com:/var/www/uploads/

To download a file from the server to your computer:

scp your-username@your-server-hostname-or-ip:/path/to/remote-file.txt /path/to/local-folder/

Example:

scp deploy@example.com:/var/www/uploads/report.pdf ~/Downloads/

If your SSH key is required:

scp -i ~/.ssh/id_ed25519 ~/Downloads/report.pdf deploy@example.com:/var/www/uploads/

If your server uses a non-standard SSH port such as 2222:

scp -P 2222 ~/Downloads/report.pdf deploy@example.com:/var/www/uploads/

What you should see when this succeeds: a progress line reaches 100%, and the command returns to the prompt without an error.

Step 4: Confirm the file is in the right place on the server

If your provider dashboard has a File Manager, open the destination folder and check the file name and size.

If you have SSH access, run:

ls -lh /path/to/remote-folder/

To check one specific file:

ls -lh /path/to/remote-file.txt

What you should see when this succeeds: the file is listed with the expected filename and a non-zero size.

Step 5: If the file is blocked by permissions, upload to your home folder first

⚠️ If you move files into system folders such as /etc, /usr, or a live web root, you can cause downtime or overwrite production files. Upload to your home folder first, verify the file, then ask your administrator to move it if you do not normally manage that path.

Upload the file to your home directory first.

With scp:

scp ~/Downloads/report.pdf your-username@your-server-hostname-or-ip:~/

Then verify it:

ssh your-username@your-server-hostname-or-ip
ls -lh ~/

What you should see when this succeeds: the file appears in your home directory, usually /home/your-username/ on Linux servers.

Verify it works

Use one of these checks, depending on how you transferred the file.

If you uploaded to the server and have SSH access:

ls -lh /path/to/remote-file.txt

Expected result: the exact filename appears, with the expected size and current timestamp.

If you downloaded from the server to your computer:

ls -lh /path/to/local-file.txt

Expected result: the file exists on your computer and the size matches the server copy.

If you used a File Manager only:

• Open the destination folder in the dashboard
• Refresh the page once
• Confirm the file name and size are visible

If the file is meant to be used by a website or app, do one end-to-end check after transfer. For example, if you uploaded logo.png into a public web folder, open its URL in your browser and confirm it loads.

Common pitfalls

Wrong protocol selected

Mistake: choosing FTP instead of SFTP.

Symptom: login fails, or the app asks for plain FTP settings and cannot connect securely.

Fix: set Protocol or File protocol to SFTP and use port 22.

Wrong port number

Mistake: using port 21 for SFTP, or forgetting a custom SSH port.

Symptom: connection timeout or Connection refused.

Fix: use port 22 unless your provider gave you a different SSH port, then enter that exact port.

Uploading to a folder you cannot write to

Mistake: trying to upload directly into /var/www, /etc, or another restricted folder.

Symptom: Permission denied, Failure, or the transfer starts and then stops.

Fix: upload to ~/ first, then move it later with the correct admin account.

Using the wrong remote path

Mistake: copying a path from documentation that does not exist on your server.

Symptom: No such file or directory in scp, or the file seems to disappear after upload.

Fix: connect with SFTP or SSH and list the folder first with:

ls -lh /path/to/parent-folder/

SSH key not loaded or wrong key file selected

Mistake: selecting the wrong private key file, or not selecting one at all when password login is disabled.

Symptom: Permission denied (publickey).

Fix: select the exact private key your provider or admin gave you, then reconnect.

Browser remote console blocks clipboard by design

Mistake: trying different paste shortcuts inside a web terminal or remote desktop session.

Symptom: nothing pastes, or only plain text appears and files never transfer.

Fix: stop using the clipboard for file movement and switch to File Manager, SFTP, or scp.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.