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
Seems to be back -- I guess that I was impatient (and 20+ minutes seemed long, especially since I was in the middle of rebooting)
Edit: I spoke too soon -- down/unreachable again
Oh, well
mine, in LA and NY, are both working smoothly. the portal, the vps management, the vnc.
My VPS is in NY
I can't reliably reach their panel at https://cloud.colocrossing.com/ (but I can reach their main site)
For the past 3 months it has been semi-unreachable depending on the time of the day
I wouldn't even have noticed except that I was rebooting my VPS when I lost contact with the panel, and as a result, my VPS is down and I can't boot it -- unlucky timing on my part
You can try leaving the browser tab open loading the page in the background, but it may timeout. In the early morning I noticed it works better.
And I thought that ColoCrossing was "Dedicated to Uptime" -- see their front page
I have a $10/y with them and it's reachable when I need it. Did not install any uptime monitoring and I will keep an eye on this thread
For clarity and fairness, I should say that the uptime of my two VPSes (in NY) at ColoCrossing has been good
What has had less-than-good uptime is ColoCrossing's customer/VPS panel
What happened to one of my VPSes now well over an hour ago is that I had done an OS update and wanted to reboot the VPS, which I usually do via the customer/VPS panel. Several seconds after I clicked on "Reboot" in the customer/VPS panel, the panel became unreachable
Unfortunately, what happened to my VPS is that the panel had already started to reboot it, but somehow the VPS couldn't complete the reboot and simply halted
As a consequence, my practical problem is that I can't access my VPS in order to boot it
(It was an unlucky collision of factors)
@ColoCrossing
I didn't tag them right away because I was hoping that the problem was very temporary, but perhaps I should have tagged them
(I may need to open a ticket)
There’s your problem. One must only host ColoCrossing services in Buffalo. Need that low cost hydropower.
That’s like going to a gyro place and ordering a slice of pizza.
My problem is that my VPS is with ColoCrossing or that my VPS is with ColoCrossing in NY?
My b, I read,“I should say that the uptime of my two VPSes (in NY) at ColoCrossing has been good,” as implying the issue in context was outside of NY; without seeing your comment above it. Continue on. 🦬🦬🦬
Just to clarify, I have a total of two VPSes with ColoCrossing, both in NY, and their uptime has been good
It's ColoCrossing's customer/VPS panel that isn't always reachable, but I'm not sure where their panel is located (though probably in NY as well)
From what I understand the developers of the panel are aware of the issue and are working to implement a software fix.
Is there a benefit to rebooting from the panel instead of "sudo reboot" from within the server? I do see the benefit of 24/7 working VNC and monitoring the reboot over VNC to watch for hiccups. I equate panel reset the same as physically pressing the reset button on a real PC. Which I would only do for nonresponding cases.
Never heard of them. Must be a typical summer host.
We apologize about any inconvenience. The cause of the panel issue is a bug in virtualizor. We have been working with them to resolve this which they say they will releasing a bug fix soon. To be clear customer VPS are not down. We have bumped virtualizor again regarding the issue.
Nowadays, decent VPS panels execute a graceful reboot as opposed to a hard reset, but I believe that this functionality depends on ACPI's being activated in the panel (which it usually is by default)
In any case, ColoCrossing use Virtualizor, which has this functionality, and so a reboot is graceful
It's more simply a habit of mine to reboot via the panel after a kernel update in the OS, which was my case today. And yes, an advantage of doing it this way is that one can view the booting of the OS in VNC to check whether everything seems okay
All that said, earlier today, I would have done better to have done
sudo rebootinstead, because then I probably would have succeeded in rebooting my VPS. As things stand, my VPS is still down after 14+ hours and the panel is of no help, having lost contact with the VPSI submitted a ticket some hours ago and the agents said that they're looking into the matter
Unfortunately, in my case, my VPS really is down (as a result of the panel bug), and there's no way that I can (re)boot it via the panel
virtfusion when? virtualizor is hands down the worst VM panel option on the market right now, pure spaghetti code.
Before current UI, it was not bad. With current UI updated, Virtualizor get really bad. Worse than even Solusvm. If you have multiple vms, you may have problems.
Can you dm us your ticket id if theres still an issue?
This is something we are exploring. Virtualizor has gotten pretty bad recently.
time for Virtfuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuusion
@ColoCrossing and my dm...?
Huh?
If you were rebooting the server, unless you broke your OS, it should just reboot, no?
Why do you need the panel to reboot your VPS? What am I missing?
Nothing to see here folks. Just colocrossing normalities. I feel like I would prefer Virmach and yea. That’s it
I never said that I needed the panel to reboot, but rather that on this occasion, I decided to use the panel to reboot
In any case, I'd rather not repeat everything that I've written above
It's an unusual/bizarre case -- that of the panel losing contact with the VPS during the rebooting of the VPS -- and one that I can't fix on my side (because the VPS is down and the panel no longer has contact with VPS)