
SCP File Transfer Client - Technical Support Information
Technical Support Guide
Thank you for choosing SCP File Transfer Client, your secure and reliable file transfer solution. This guide will help you set up secure connections and resolve common transfer issues.
Using SCP File Transfer Client:
- Connection Setup – Configure your server connection:
- Host: Enter server IP address or domain name
- Port: Default is 22 (SSH standard port)
- Username: Your server account username
- Authentication: Choose between Password or SSH Key authentication
- Authentication Methods:
- Password Auth: Enter your server password (not stored locally for security)
- Key Auth: Select your private key file (supports RSA, DSA, ECDSA, Ed25519 formats)
- File Transfer Operations:
- Upload: Select local file to upload to remote server
- Download: Select remote file path and choose local save directory
- Real-time progress monitoring with transfer speed display
- Connection Testing – Use "Test Connection" to verify credentials before file transfer
Troubleshooting:
- Connection Failed:
- Verify host address and port number are correct
- Check if server allows SSH connections on specified port
- Ensure firewall isn't blocking outbound connections
- Try connecting via terminal:
ssh username@hostname -p port
- Authentication Issues:
- Password Auth: Verify username and password are correct
- Key Auth: Ensure key file has correct permissions (chmod 600)
- Check if server accepts your public key (add to ~/.ssh/authorized_keys)
- Verify key format compatibility with your server
- Transfer Failures:
- Check remote path exists and has proper write permissions
- Ensure sufficient disk space on destination
- Verify file isn't locked or in use by another process
- For large files, check network stability and timeout settings
- Permission Denied:
- Verify user has read/write access to specified directories
- Check SELinux or similar security policies on server
- Ensure remote path uses absolute paths (e.g., /home/user/file.txt)
Important Security Notes:
- All connections use encrypted SSH protocol (industry standard)
- Passwords are never stored locally for your security
- SSH keys should be kept secure with proper file permissions