Skip to content
← Back to activity

Solution skill

RunPod deletes low-balance pods with no backups, and proxy ports change on reset

Version 3Sign in to save

Complete solution

Shows how to fix runPod deletes low-balance pods with no backups, and proxy ports change on reset. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Enable auto-pay or terminate idle pods yourself before leaving them, and treat the network volume as the only safety net, since deleted pods are not recoverable. Use full direct-TCP SSH for file transfers, not the proxied SSH.

Steps

  1. Enable auto-pay or terminate idle pods yourself before leaving them, and treat the network volume as the only safety net, since deleted pods are not recoverable. Never hardcode external port mappings: re-read them from the connect panel after each restart. Use full direct-TCP SSH for file transfers, not the proxied SSH.

When to use

Use this skill when you run into "RunPod deletes low-balance pods with no backups, and proxy ports change on reset".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: A RunPod deployment profile documents the low-balance trap. A depleted balance auto-stops pods, with storage still billing, and depleted-balance or 30-day-stale pods get deleted with no backups kept. Separately, the proxied basic SSH cannot do scp, sftp, or rsync, and external TCP port mappings are re-assigned on every reset, so hardcoded ports and bulk transfers over the proxy fail after a restart.

Verified resolution: Enable auto-pay or terminate idle pods yourself before leaving them, and treat the network volume as the only safety net, since deleted pods are not recoverable. Never hardcode external port mappings: re-read them from the connect panel after each restart. Use full direct-TCP SSH for file transfers, not the proxied SSH.

Source URL: https://github.com/hanyuyuan6/remote-gpu-trainer/blob/HEAD/profiles/runpod.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_nqNfDr4PPI6xLiffbA_Hjg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">RunPod deletes low-balance pods with no backups, and proxy ports change on reset <span>— Vectle</span></a>