New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I found the network-status page (via the client panel): "There are no Network Issues Currently"
So it seems to be a node-specific issue
My VPSs in NY-Cloud-19 and NY-Cloud-15 are all working fine
Unfortunately, their first reply (by ticket) is to ask whether they can recreate the server! Not very encouraging ...
Wasnt it the forum admin's company? Maybe reach out to him and ask for some help...
I've been 10 years with ChicagoVPS, if I'm not mistaken it is part of the same portfolio of brands; with them I always got that question in every ticket. And past the second reply, they would always lose cognitive context of the remainder of the conversation.
My VPS dates from last Saturday -- I wanted to give ColoCrossing a chance!
It was his company, but it no longer is
I had nearly finished setting up the VPS (I got it last Saturday), so it's a pain if that effort was for nothing ...
Well... if you wanna migrate, I can throw in a (PMX) backup service for any plan in the two locations from my signature.
Not going to help you now but i've found that storing compressed disk images whenever i've setup something more complex pays off as whatever happens restoring is always just one dd invocation away and it's also super convenient for migrating VMs.
Poor man's snapshot
I’m guilty of this
That's an idea
I usually just set up a backup plan for the crucial directories, but restoring/recovery is still an effort, of course
In the present case, I hadn't yet set up a backup plan (I got the VPS last Saturday), but fortunately, I hadn't yet begun to use the VPS beyond some tests
But it's disappointing as a first VPS experience at ColoCrossing
Yeah, there also seems to be a bit of a pattern. I vaguely remember that the last time i read about their VPSs it also involved the regular occurrence of rebuilds.
they seem pretty ok at dedicated servers but I really wouldn't trust their VPS lineup
Yes, over ssh it's really simple and fast, here a few tips for those interested: optimally freeze the filesystem before creating the image (fsfreeze) if you don't want to/can't u(n)mount it. And if you want to compress it, use fstrim before to fill unused space with zeros.
And regarding setting up a VPS, I recommend using (shell) scripts as manual installations are very prone to forget something.
A shell script that sets up git, a docker registry (and docker itself), pulls the repos and starts the containers, that is😃👍
Amd I weird for hating docker and prefer to do all manually ?
I'm not much of a docker fan either (slight understatement). Using VCS for system setup is quite nice though, even if i'd rather fossil thx
Weird or old, up to you
Both are terribly tempting to choose...
My $7 a-year colocrossing VPS pushes 80-100TB a month of bandwidth and it rarely has issues I dunno why my cheap ass service rarely has issues compared to people who pay a lo more at colocrossing lol.
Their second ticket response is that they've encountered some "technical challenges" with my VPS and that recreating my server would be "the most effective solution"
I guess that something catastrophic happened to this node (NY-Cloud-40)
That sounds like a very positive experience
sounds like you shouldn't pay more than $7/yr for a CC VPS.
And I imagined that by paying more, I would be put on a better node!
$7 a year VPS my second cheapest ipv4 VPS but def still a very good deal for being able to push a petabyte per year - I think the people on my node are quite or something because I still get 1500 geekbench score.
We apologize for this can you please DM us your ticket ID to check into this?
move him to the node where u put all the blackfriday yearly $6.50 VPS - its pristine
I personally generally don't like very big program which do 1000 things (I also hate systemd) and prefer to either do all unisolated, or simply use namespaces (pid, user, mount, utc, ipc, time, ...) and cgroups and chroot.
Registered just to say I'm on the same node, and it went down around 11:30AM EDT on the 16th. I received the exact same support response. Fortunately, the node came back up around 9:30PM EDT that evening and I used the opportunity to back up my configs. We'll see what happens going forward. The downtime is what it is, but insisting that the VPS has to be recreated when the node is just temporarily offline is bad.