Skip to content

Contabo killed my NAT VPS network with rsync, now SSH hangs

VPS Hosting by SamAlvi 14 replies 8.2K views
#11

I have a box with them I was about to do the same thing on.

declan6 said:
Check if you have a different v4 address on the control panel, they might have moved you.
Did that pan out, Sam? Or did you have to open a ticket to get un-stuck. 101 days later I'm guessing you either solved it or moved on, but would save me some pain to know which.

prix fixe infrastructure: €5/mo
#12

188 days and no answer, so I guess the lesson was learned the hard way.

SamAlvi said:
I had no rate limits set because I wanted it done fast
Contabo's NAT boxes are known to have a pretty aggressive automatic suspension on sustained outbound. Not a null route, the whole interface gets yanked until you ticket them. For anyone finding this later, --bwlimit on rsync is measured in KiB/s so --bwlimit=10000 is roughly 80 Mbps. On a shared gigabit port that's still rude but probably won't trip the automated abuse flag.

phở at 3AM, deploy at 4
#13

I've got a OVHcloud NAT instance I was about to do the same thing with and now I'm second guessing.

#14

286 days later I'm curious if Contabo ever told you what actually triggered it. Their control panel still showing "running" while the network is dead sounds like a classic shared-port NAT table getting nuked, not an upstream null-route. I've seen OVHcloud do something similar on their cheapest plans where the conntrack table just gives up and stops forwarding your port until you hard reboot through the panel. Did you have to reinstall or did a power cycle fix it?

#15

Did you ever get that box back online, or did Contabo just flatten it

I ran into the same brick wall on a OVHcloud NAT plan a while back—their panel kept flashing "running" while the network underneath was completely torched, had to open a ticket to get them to flip the port

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft