27 Dec
2016
27 Dec
'16
11:53 p.m.
b) After at least 21 days of sending email alerts to
the main
contact and the emergency contact and receiving no response, the
VPS's networking will be suspended. Networking will be re-enabled
when contact is re-established and a plan for securing the
problem service is agreed by both BitFolk and the customer.
I have already broached this question on IRC and basically no one
was in favour of (a) because they did not feel that surprise
invoices would go down well.
I actually got a problem with b).
My home (personal) contact stuff goes almost exclusively via bitfolk.
That includes email/sms/jabber/phone[voip], so if my VPS gets shut down
it's difficult to contact me. (There is some redundancy but not in the
frontend really and I can't be bothered to create automatic fail-overs
etc..)
When there are problems and I don't respond, it's usually because I'm
not receiving the messages and are thus not in a position to do anything
about it.
Cutting off the server makes the matter worse for me.
For me, keeping the service going is top-most priority.
Could I "elect" to to be invoiced rather than shutdown? For example, as
an option on the Panel?