My previous problems with BlueVM
Massive packet loss at BlueVM Los Angeles: http://ift.tt/1op3Yz3
BlueVM shuts down my VPS with dubious cause, doesn't bother to notify me: http://ift.tt/1xUA5I6
email blacklisted because of Spamhaus Colocrossing listing: http://ift.tt/1op40a2
I have one little VPS on BlueVM that I use. Unfortunately, it's nothing but problems since I first started using them a few months ago.
I really wanted for BlueVM to work out, but it isn't. At all.
Now the issue is that they keep rebooting the host node, or otherwise rebooting my OpenVZ VPS.
List of reboots. The timestamp here is on boot-up, not when it went down.
Sun Aug 3 03:52:13 MST 2014
Sat Aug 2 04:32:42 MST 2014
Fri Aug 1 03:06:47 MST 2014
Fri Jul 25 22:59:07 MST 2014
Tue Jul 22 10:51:17 MST 2014
Sun Jul 20 06:28:07 MST 2014
Sat Jul 19 06:47:36 MST 2014
Fri Jul 18 17:33:55 MST 2014
Sun Jun 15 21:50:42 MST 2014
Fri Jun 13 15:14:51 MST 2014
Sat Jun 7 17:02:54 MST 2014
Sat May 24 17:34:23 MST 2014
In the last three days, they have rebooted this host every day within the same 2-hour window.
Unfortunately, for reasons I'm not sure about, every time they reboot, my node comes up with an empty iptables configruation. I have to log in and manually restore the iptables config, because whatever they are doing is breaking it on restore.
So, I find my host sitting there with no firewall. Awesome.
This is on top of my host being broken and offline for 7-8 hours last Thursday when I couldn't even access the host via the Feathur control panel. It took them 35 hours to finally respond to the ticket I opened. I think it got fixed by accident when they rebooted the host node on Friday morning.
http://ift.tt/1dvHQ0Z
0 comments:
Post a Comment