How to Send Your First File & Verify Delivery

Now that your Data Store, Sender, and Pipe are configured, you are ready to transmit. Choose any of the transmission methods below to send your first file and confirm that it lands in your cloud storage.

Desktop File Transfer Clients (Cyberduck, FileZilla, WinSCP)

If you want to drag and drop batches from your workstation or laptop:

Setting	FTP Connection	SFTP Connection
Host	ftp.rilavek.com	sftp.rilavek.com
Port	21	2222
Username	SenderName@PipeID	SenderName@PipeID
Mode	Passive (PASV)	Standard SSH Channel

Terminal or Scripting with cURL

To test connectivity in seconds from macOS or Linux terminal:

# Replace credentials with your Sender and Pipe ID:

curl -T sample_file.txt -u "client01@p_9k2a4:your_password" ftp://ftp.rilavek.com/

Hardware Devices, Network Appliances & Cameras

Network scanners, embedded devices, IoT gateways, and modern cameras include built-in FTP clients. You can stream files straight to the cloud:

1.Connect the device to Wi-Fi, Ethernet, or mobile broadband.

2.Open your device network menu and navigate to FTP Transfer Settings.

3.Set Host / Server to ftp.rilavek.com and port to 21.

4.Enter your username as SenderName@PipeID and paste your Sender password.

5.Trigger a test upload or enable automatic background transfer.

Looking for camera-specific walkthroughs? Check out our dedicated guides for Sony Alpha, Canon EOS, and Nikon Z, or explore our CCTV & IP camera cloud storage solutions and surveillance architecture guide.

Web Dashboard & Resumable HTTP / TUS

When HTTP ingress is enabled on your Pipe, you can transfer files directly over the web without needing traditional FTP or SFTP software:

1. Direct Dashboard Upload

Open your Pipe overview in the Rilavek dashboard. You can drop files right onto the built-in uploader or click to browse. It splits files into chunks and streams them directly into your storage bucket with reliable auto-resume.

2. Programmatic HTTP / TUS Ingress

Send files programmatically from frontend apps or backend scripts using the open TUS protocol. Connect client libraries like tus-js-client or uppy to your Pipe endpoint with temporary bearer tokens.

Need token generation steps and chunk size requirements? Read the complete HTTP / TUS source documentation.

Confirming Delivery in Cloud Storage

Because Rilavek streams directly, your cloud bucket registers an S3 PutObject event the instant the upload completes. You can verify arrival in two places:

1. Rilavek Live Logs

Check Transfer Logs in your dashboard. You will see file size, transfer duration, sender identity, and destination response status.

2. Cloud Storage Console

Open your AWS, Cloudflare R2, or Backblaze bucket browser. Your file will be waiting under the configured path or sender directory.

Step 1 of 4:Pipe Ready & Monitoring Transfers

Auto-playing

Rilavek

Dashboard

Billing

Data Stores

Senders

Pipes

Pipes /Production Ingress

Status:

Active

Transfers

Live monitoring

Total Volume

0 B

Zero-disk stream

Pipe Status

Active

FTP :21 ready

Connection Endpoint Ready for Ingress

Host:ftp.rilavek.com:21

Username:client01@p_9k2a4

Primary Storage:AWS S3 (production-archive)

Common Transfer Gotchas

Passive Mode: Ensure desktop clients and scripts use Passive (PASV) mode to pass through cellular and corporate firewalls cleanly.
Client Keepalive: Configure keepalive in your client or disable aggressive hardware sleep modes so large file transfers finish uninterrupted.
Username Formatting: Remember the @ symbol separating your Sender name and Pipe ID.

Up Next

Ingress Sources: FTP / FTPS

Explore protocol endpoints, cipher suites, active/passive ports, and client connectivity settings.

Go to Ingress Sources

Documentation