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
We bought this new node a week or so ago and decided not to go with Virtpanel anymore so we installed SolusVM on the new node.
The other node ran on Virtpanel with 100+ VM's on it, we will change this the 28th to SolusVM when we are in the datacenter.
@ContraWeb VirtPanel?? Wow, sorry about the pain lol
I'm not passing judgement on what long enough looks like, but if you're asking, I personally would never recommend a host unless I'd had at least one month of excellent service, and generally I'd be looking at 3 months. I also wouldn't make a recommendation unless I'd actually used the server to a reasonable degree so I can vouch for the fact I could use the resources I'd paid for.
The reason being is that I'd feel guilty if I recommended a host after a short period of not really using them, people bought off the strength of that recommendation and they received shit service. But, not everyone feels that way, and it's arguable that people should do their own due diligence and not buy based on a forum recommendation alone. Just the way I feel.
I do feel that reviewing a host after a few days and recommending them is a bit like recommending someone take a trip to the cinema to see a film after you've watched the first 20 minutes.
To be clear, I've no issue with anyone posting an initial impression (particularly of a new provider), I do have an issue with the language used around that (pet peeve of mine), but that's my issue, and I'm interested in the viewpoints of others on the subject.
Nekki has a valid point here. It is another thing to bring a good or, even interesting offer under the spotlight, and another to recommend the service when you have tested it only for a couple of days.
OP could avoid the work "recommended", but to be fair, he clearly stated that he was using the service only for 2 days. So, it is common sense for a reader to understand that the "recommendation" was based on the first impression and not after a heavy test of the service.
Wake up,my vps gone:(
Unhappy
Just checked, my VPS is still there
Did you contact them via ticket, @lingting ?
@mfs
Yes, I made a ticket,But has not yet been resolved!
Mine is there but rebooted 19h15m ago, and has a mysterious root shell connected. Hmm.
Interesting
well, I didn't check the uptime... same here
there's ttyS0 connected since 2017-02-19 14:18 CET but it's vnc/serial console isn't it
Any idea how to figure out where the other end of that shell is? netstat -pt 22 only shows my connection, plus repeated short ones from China Telecom that look like a normal brute force attempt. Person has been trying for quite a long time.
Added: controlling tty of that root shell is TTYS0 (serial console?) rather than a pty, weird. I blocked the China Telecom address with iptables on general principle.
yes it is, at least that is for the VMs on the first node (with virtpanel). those shell has been there before, you most probably just didn't noticed it.
if you feel uncomfortable you can get rid of it at least on debian by editing grub.cfg , watch out for the line(s) containing console=ttyS0 and remove that part of the line (should be in GRUB_CMDLINE_LINUX or something like that...)
run update-grub afterwards and reboot. for sure inside virtpanel the serial console won't work after making these changes.
my VM also rebooted, so most probably the whole node did. that wouldn't bother me much besides virtpanel obviously changing the root password back to the one saved and set there as default. looking forward to the planned migration to solus for getting rid of such interferences ;-)
@willie ss -t show only my connection as well; is the other shell a ttyS0? No chinese guy bruteforcing port 22, since I always move sshd away from there to remove some noise
@Falzo I already did remove console=ttyS0 and GRUB_SERIAL_COMMAND in grub but to no avail.. KVM over VNC was still there, at least on the first node, and both serial console and VNC. And to be honest I needed it because of a little bug (sometimes on reboot connectivity wasn't there, hence I had to reboot again from vncviewer/console)
Oh ok, the ttys0 is from virtpanel, fine. That's crappy about it resetting root password though. I always lock the root password. If I turn off password login in sshd config will it stop that?
Added: Well I turned ssh password auth off, will see if that gets reset. Will figure out later what if anything to do about vnc. Will also think about whether to switch the port: have to figure out if that will break anything like my ansible scripts.
I remember something now about the node crashing due to a ddos attack, so that would explain the reboot.
Thanks for the help!
My vms (on old and new node) both havent rebooted.
I did that right after setting up the whole box... if I remember correctly I did some things more, most probably deleting every service from systemd related to it. something like systemctl disable [email protected] and/or removing the files from /lib/systemd/system like [email protected] or so, also commented out the uart/ttySx devices in /etc/securetty ...
no, that won't change anything... while I am looking further into it, there is an init-script /etc/init.d/virtpanel which seems to mount a floppy containing settings for IPs, nameserver and obviously a password.txt etc.
will see what happens if we get rid of it ^^
edit: I'd guess, that's at all just a thing related to the given pre-made templates through virtpanel. shouldn't happen at all, if one would setup the system via VNC and regular netinst iso...
ah right, the almighty systemd AI ; good catch
[email protected] is masked but system-getty.slice is loaded and has activated another S0, for all the poetterings
edit: masked [email protected] as well, commented /etc/securetty, rebooted, ttyS0 is still there but serial console seems not working any more (KVM over vnc is still working)
edit2: well no, I've casually tried again to connect a serial console via virtpanel... and it still worked
I'll eventually rm those services... I thought masking would have been enough
Wait what? You don't have control over the system/cp you use? Sounds unprofessional and not to be trusted in my perspective.
Hosted panels are a pretty standard thing... buyshared uses hosted cpanel iirc. And Contraweb is working on moving away from virtpanel so it all seems cool.
you might want to have a look here: https://www.virtpanel.com/
the panel itself is an SaaS solution, so he can not make much changes or adaptions to the panel software/scripts. I wouldn't call that untrustworthy per se , it's just another approach... after all it should not mean that he is not able to interfere with the system/hostnode itself ;-)
Not to be trusted, mmh?
This is KVM, or?
VirtPanel wasn't the best sollution for us, thats why we are moving away, that you barely have any control over the panel is one of the reasons.
Now that you're using SolusVM, you should have chat with @AnthonySmith about "having any control over the panel"
jk
We are out of stock again, it may take a while before your VPS is delivered.
Perhaps it would be a good idea then to change it to out of stock in your billing panel?
Dunno- mine lasted a couple days (without use or ability to use).
Thanks for the tip, done. :-)
wat