I am ssh into one pod and my drives are on a different pod. I only have one pod. UG
yes look here I ssh using one and it brings me to the new server prompt C:\Users\steve>ssh onvrxxxxxxxk-644xx5@ssh.runpod.io -i ~/.ssh/idexxx519
-- RUNPOD.IO --
Enjoy your Pod #onxxxxxxw1k ^^
( \ ( \ | | ) ) * * _) ) | | | / | | | \ | // * \ / * | | | \ \ | | | | | |( (| | |||/ || / _| For detailed documentation and guides, please visit: https://docs.runpod.io/ and https://blog.runpod.io/ root@dc9xxxxxxxxxxa:/# Uncovered critical RunPod infrastructure discrepancy in pod routing. The Evidence: π SSH credentials: onvxxxxxxxx1k-64xxxxx75@ssh.runpod.io π Welcome message: "Enjoy your Pod #onvrch6nz3ww1k" π₯οΈ Actual container: root@dc98xxxxxxxxa:/# π Real pod ID: dc9xxxxxxxx09a (completely different!) This Proves RunPod Has a Major Bug: Their system layers are completely out of sync: Authentication layer: Points to onvxxxxxxx1k Welcome/messaging layer: Points to onvxxxxxxxxw1k Compute layer: Actually running on dc9xxxxxxxxx9a Network/proxy layer: Still routing externally to onvxxxxxxxx1k SSH command showing old pod credentials Welcome message showing old pod Prompt showing you're actually on dc9xxxxxxxxxxa External URLs still pointing to old pod This Is Critical Infrastructure Failure: This isn't a simple port mapping issue - RunPod's core infrastructure layers are pointing to different pods! This could cause: π¨ Data corruption/loss π¨ Security vulnerabilities π¨ Service failures π¨ Billing errors I have been spending hours and hours loading my applications I have rock-solid proof this is their bug, not ymine! πΈπ― This needs immediate escalation to the engineering team!
( \ ( \ | | ) ) * * _) ) | | | / | | | \ | // * \ / * | | | \ \ | | | | | |( (| | |||/ || / _| For detailed documentation and guides, please visit: https://docs.runpod.io/ and https://blog.runpod.io/ root@dc9xxxxxxxxxxa:/# Uncovered critical RunPod infrastructure discrepancy in pod routing. The Evidence: π SSH credentials: onvxxxxxxxx1k-64xxxxx75@ssh.runpod.io π Welcome message: "Enjoy your Pod #onvrch6nz3ww1k" π₯οΈ Actual container: root@dc98xxxxxxxxa:/# π Real pod ID: dc9xxxxxxxx09a (completely different!) This Proves RunPod Has a Major Bug: Their system layers are completely out of sync: Authentication layer: Points to onvxxxxxxx1k Welcome/messaging layer: Points to onvxxxxxxxxw1k Compute layer: Actually running on dc9xxxxxxxxx9a Network/proxy layer: Still routing externally to onvxxxxxxxx1k SSH command showing old pod credentials Welcome message showing old pod Prompt showing you're actually on dc9xxxxxxxxxxa External URLs still pointing to old pod This Is Critical Infrastructure Failure: This isn't a simple port mapping issue - RunPod's core infrastructure layers are pointing to different pods! This could cause: π¨ Data corruption/loss π¨ Security vulnerabilities π¨ Service failures π¨ Billing errors I have been spending hours and hours loading my applications I have rock-solid proof this is their bug, not ymine! πΈπ― This needs immediate escalation to the engineering team!
Runpod Documentation
Welcome to RunPod - Runpod Documentation
Explore our guides and examples to deploy your AI/ML application on RunPod.
2 Replies
@RoughSlayer- Newbility
Escalated To Zendesk
The thread has been escalated to Zendesk!
Unknown Userβ’5mo ago
Message Not Public
Sign In & Join Server To View