May 11, 2026 · Guide

How to Share Files Between Remote Servers Without Cloud Storage

You are SSH'd into a client's production server. The application is throwing errors. You need to share a 47MB log file with a colleague who is on a different VPN network with no direct connectivity to this server. What do you do?

This scenario plays out daily for system integrators, DevOps engineers, and field technicians. The standard answers all have friction: SCP to your laptop, then upload to Google Drive. Email it, if your client's SMTP allows attachments. Use a Jumpbox that both networks can reach — if one exists. Or worse: take a screenshot of the terminal and send it via WhatsApp.

There is a better way.

The Fundamental Problem: Isolated Networks

Industrial environments, financial networks, healthcare systems, and enterprise VPNs are intentionally segmented. Direct file transfer between them is often impossible by design. The tools that could bridge the gap — SFTP, rsync, SMB shares — require open ports, routable IP addresses, or shared credentials that security policies forbid.

The breakthrough realization: HTTP is almost always allowed. Even the most restrictive networks permit outbound HTTPS on port 443. If you can make an HTTPS request, you can upload to a pastebin. And if you control that pastebin, no third party sees the data.

The Self-Hosted Pastebin Pattern

A self-hosted pastebin on Cloudflare Workers creates exactly the right bridge. Here is how it works in practice:

Upload from a Restricted Server

From the client server, upload a file to your pastebin via HTTPS:

curl -X POST https://paste.yourdomain.com/api/files/upload \
  -F "file=@error-log-2026-05-11.txt" \
  -H "X-CSRF-Token: YOUR_CSRF_TOKEN" \
  -b "session_token=YOUR_SESSION"

The pastebin stores the file in your Cloudflare R2 bucket and returns a download URL. No cloud storage provider, no third-party server, no file size limit beyond what you configure.

Share the Link

Send the download URL to your colleague via Slack, email, or any messaging tool. They click it and download the file directly from Cloudflare's edge network.

Real-World Use Cases

Industrial System Debugging

A SCADA system is logging Modbus communication errors. The field technician connects via SSH to the edge gateway (which has no internet browser) and uploads the log to PasteHere. The SCADA engineer at the office downloads it immediately and identifies the register mapping bug.

Multi-Region Config Sharing

A DevOps engineer needs to share an nginx config from a production server in Frankfurt with a colleague debugging a staging environment in Singapore. Neither server can reach the other directly. Both can reach PasteHere.

Client Deliverables

A system integrator generates a commissioning report (PDF) on a customer's air-gapped OT network. They upload it to their self-hosted PasteHere via a management workstation with limited internet access. The client downloads it from their corporate network later.

Security Considerations for Remote File Sharing

When you use a third-party pastebin or file sharing service for this pattern, you are trusting that provider with potentially sensitive data. This is often unacceptable in regulated environments.

A self-hosted solution eliminates this risk entirely:

• Data stays in your Cloudflare account. D1 for metadata, R2 for files. You control retention, encryption at rest, and access policies.
• Password-protected access. Files are not publicly browseable. A workspace password gates all access.
• CSRF and rate limiting. Prevention against automated abuse and brute force attacks.
• Audit trail. Since all operations go through your D1 database, you can trace what was uploaded, viewed, and deleted.

File Types That Matter in the Field

When you are working on remote systems, you are not just sharing text files. The pastebin needs to handle:

• Log files (.log, .txt, .out) — often multi-megabyte, sometimes gigabytes
• Configuration files (.conf, .yaml, .toml, .ini) — small but critical
• Screenshots (PNG, JPEG) — "here is what the dashboard shows"
• Archives (ZIP) — batch exports, database dumps, directory snapshots
• Documentation (PDF, Markdown) — commissioning reports, network diagrams

Frequently Asked Questions

How can I share files between two servers that cannot reach each other directly?

Use a self-hosted pastebin deployed on Cloudflare Workers as a bridge. Upload the file from the first server via curl over HTTPS, then share the download URL with the second server or a colleague. Both endpoints only need outbound HTTPS access to the same domain — no direct network connectivity, VPN peering, or open ports required.

How do I transfer log files from a remote server without cloud storage?

SSH into the remote server and upload the log file to your self-hosted pastebin using curl with a POST request. The file is stored in your Cloudflare R2 bucket and you receive a download URL. Share that URL with your team via Slack, email, or any messaging tool. No Dropbox, Google Drive, or third-party storage involved.

Is it safe to share files from production servers over the internet?

With a self-hosted pastebin on Cloudflare Workers, yes. Files are stored in your own R2 bucket with encryption at rest. Access is gated by a workspace password, all mutations require CSRF tokens, and rate limiting prevents brute-force attacks. The pastebin runs on your domain with your SSL certificate — no third-party provider ever sees the data.

What file types can I share from remote servers?

A self-hosted pastebin on Cloudflare R2 handles any file type: log files (.log, .txt, .out), configuration files (.conf, .yaml, .toml), screenshots (PNG, JPEG), archives (ZIP), database dumps, and PDFs. There is no file size limit beyond what you configure in your R2 bucket settings. Multi-megabyte uploads work reliably over HTTPS.