Huge problems on Pods
There are so many problems when you are trying to transfer YOUR data from the old pod to a new pod that gave me the sensation that this website offers SH** services...They are not offering good services at all.....I have spent days trying to connect 2 pods between them, and every time I find a solution, it does not work, just giving me the sensation that they only want your money without giving you good services instead. Is so frustrating ........ Anyone is online to help me resolve these problems???????
11 Replies
anyone online ????????
Unknown User•5w ago
Message Not Public
Sign In & Join Server To View
the connection berween the old pod and the new one it fails every damn time....I tried different ways each time and....failed every damn time ! I just waht to transfer content from the old pod to the new one , so basically both inside the same website, the same server
Here's a summary of what we've tried and why transfers have failed:
OBJECTIVE:
Transfer 277GB of data from old RunPod pod to new L40 pod.
METHODS ATTEMPTED:
1. Direct SSH/SCP Transfer
Tried: Multiple SSH connections using both regular SSH and SSH over exposed TCP
Commands: ssh user@host, rsync -avzP, scp -P port
Failed because:
Port numbers keep changing (17031 → 31697 → 51458)
"Connection refused" errors
Public key authentication issues between pods
Username mismatches (root internally vs. generated username externally)
2. HTTP Server Method
Tried: Python HTTP server on ports 8000, 8888, 9999
Commands: python3 -m http.server [port]
Failed because:
Firewall blocking connections between pods
"Connection refused" from L40 pod to old pod IP (213.181.111.2)
3. External Transfer Services
Tried: tmpfiles.org, transfer.sh
Failed because:
File size limits (100MB max on tmpfiles.org)
transfer.sh connection refused (port 443 blocked)
4. Key Exchange Attempts
Generated: Both ed25519 and RSA keys on both pods
Failed because:
Directory structure issues (.ssh didn't exist)
Key authentication still rejected
Complex username/authentication system in RunPod
CURRENT SITUATION:
Old pod has 277GB in /workspace
Both pods are isolated from each other network-wise
Now attempting Google Drive as intermediary (rclone)
ROOT CAUSE ANALYSIS:
RunPod's security model appears to heavily restrict direct pod-to-pod communication, with dynamic port allocation and strict firewall rules preventing standard transfer methods.
Would Network Volume or a RunPod-specific transfer solution be available?
?
Unknown User•5w ago
Message Not Public
Sign In & Join Server To View
I tried everything...... guided by an AI
Unknown User•5w ago
Message Not Public
Sign In & Join Server To View
I know that, seen that and I did not restarted...
Hey, thanks for trying to help! Here's what happened:
Setup:
- Old Pod: 277GB data in /workspace
- New Pod: L40 with 350GB storage
- Goal: Transfer everything to the new pod
What we tried:
1. Direct SSH/SCP between pods:
- Generated SSH keys on old pod
- RunPod shows different usernames:
- In Web Terminal: root@8e3f8c1b02a4
- For SSH: 9hcfvmio7pe2w0d4kvvo@ssh.runpod.io
- Added public keys to authorized_keys
- Result: "Permission denied (publickey)" every time
2. Python HTTP Server:
- Tried ports 8000, 8888, 9999 on old pod
- From new pod: wget http://213.181.111.2:9999/file
- Result: "Connection refused" on all ports
3. The weird part:
- SSH ports keep changing randomly
- Connection methods don't match between what RunPod shows and what works
- Pods seem completely network-isolated from each other
Current solution:
Uploading 278GB to Google Drive then downloading to new pod (will take forever)
Question:
Is there a better way? Can RunPod pods talk to each other directly? Or is there a shared storage option?
Unknown User•5w ago
Message Not Public
Sign In & Join Server To View
try use OhMyRunPod on both pods
thanks, will try these !
runpodctl also has a method to transfer between 2 pods
https://github.com/runpod/runpodctl?tab=readme-ov-file#transferring-data-file-sendreceive
GitHub
GitHub - runpod/runpodctl: 🧰 | RunPod CLI for pod management
🧰 | RunPod CLI for pod management. Contribute to runpod/runpodctl development by creating an account on GitHub.