Why is Hetzner so stingy with server quotas?
I started migrating my servers from Linode to Hetzner Cloud this month, but noticed that my quota only gave me ten instances.
I need many more, probably on the order of 25 right now and probably more later. I'd also like the ability to create test servers, etc.
I asked for an increase with all of that in mind, and Hetzner replied:
"As we try to protect our resources we are raising limits step by step and on the actuall [sic] requirement. Please tell us your currently needed limit."
I don't understand. Does Hetzner not have enough servers to accommodate me? Wouldn't knowing the size of the server be relevant if it's an actual resource question?
I manage a very large OpenStack cluster for my day job and we just give people what they pay for. I'm having a hard time wrapping my head around this unless Hetzner might not be able to give me what I ultimately want to pay for, and if that's the case, I wonder if they're the right solution for me after all.
It also makes me worry about cloud elasticity.
Does anyone have any insights that can help me understand why keeping a low limit matters?
Just answer them with a little explanation like you did here, you will be fine. Done that, been there.
They just want to protect against people buying lots of servers for a short time, then not paying or doing ddos shit.
Thank you. I hadn't considered the payment part. The cloud system that I manage is in education, so everyone pays in advance.
This makes sense, and I'll start with a lower number and ask it to go up later. It will take a couple of months to migrate everything from Linode anyhow, so I don't need them all at once.
Hetzner has been used for ddos attacks and spam runs, so they're cautious. You pay afterwards, I get the bill the 3rd of the month.
Also, be advised, sending email out is blocked by default and can be unblocked 30d after creating the 1st vps when the 1st invoice is paid. BTW blocking is pretty simply a block on port 25 and 465, so rerouting to anothe rport to a relay works when you need it the 1st 30 days. (for say monitoring)