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.
HostSailor - 12.12 Mega Deal: Get Your KVM VPS NVMe at 90% Recurring Discount – Forever!
This discussion has been closed.

Comments
Okay strange, I only see 2 sockets and 2 processors. Trying to run a Geekbench to confirm if those values are just cosmetic
I wanted to check via cpu-z but it always crashed the whole vps, keep me updated
Since 7h node4 is stable, no more connecting issues
My connection issues on node 4 cleared up about a hour ago, but now GB6 is under 1000. I'll take it for now
Apparently the way the hypervisor's cpu topology is configured, makes it appear in windows as 2 sockets 2 virtual processors. Even tho the device manager lists 16 cores, Win 10 pro will not allow more than 2 sockets as part of it's licensing policy.
As windows server editions have a higher socket limit (64), I confirmed the same by upgrading my existing win 10 pro installation to Windows server 2019 standard desktop edition.
All the cores are listed properly
People who are talking about Windows Pro, do they illegally activated it, since we know the host is not part of Microsft Partnership Program or it's just trial license?
HaHa, this is indeed the best bang for the buck!
Pirates at the sea!
Great 😃
Mine is also still offline. SolusVM actions complete successfully (it says it's rebooted, or network reconfigured), but still shows as offline, and it's un-pingable. No route to host.
Hey, network is improving over the time @HostSailor
metoo thanks
Node 6 does not seem to have IPv6 yet.
It looks like your question has already been answered.
I believed they have different default I/O speed for each plan.
Starting from the 12th, I canceled the VPS and sent a tickets that day. From the 12th to today, refund tickets have been sent to three departments, a total of four tickets, but no reply has been received.@HostSailor
Appreciate your time, works.
Gonna be using that script on other servers as well, what a great find
I think it bears repeating that you should change the network card to Virtio in the VPS control panel. Went from being capped at 300mbps to multi gigabit speeds after reboot.
@RichardGrant, you want refund? Let me have that vm, I'll pay to you.
It was already cancelled on the 12th
too bad.
If no reply has been received, you can just close the ticket(s) (and keep the VPS or potentially transfer to @tenpera ).
However if you meant "no refund has been received" then it's a different story~
My vps is on node 6, and they assigned a /64 to me yesterday. After trying to reconfigure the networking through SolusVM, my vps has been offline, since yesterday. It may have just been a coincidence since it was slow and behaving strangely just before that.
I think there's a policy of refunds within the first 14 days, so it would make sense to wait awhile for things to get fixed and stabilize, since it's a good deal.
I do think they'll get things worked out and it will be ok. I'm posting what's going on, not to complain, but because it's probably similar for some others, so they'll know they're not alone.
I'm on node 6 and have IPv6 running just fine on Debian 12. Word of warning though, at the moment I got my /64 with instructions, the instructions said to do a "reconfigure network" from the control panel. That didn't work - but already before that my IPv4 also didn't work. From the console (through the VNC viewer) I manually assigned the /64, rebooted and then everything (IPv4 and IPv6) worked and has been quite stable since then.
I have applied for a refund, but so far he has not replied to me. I cancelled the product as early as the 12th.The product is indeed worth it, but it's not suitable for me.
Good to know. Unfortunately, I'm not able to connect through VNC, either. It just shows as offline and if I try to ping it, it replies with "destination host unreachable."
Had that too, but for some reason a reinstall yesterday afternoon worked. Before that I wasn't able to either reinstall properly or boot. Maybe I've been lucky - but you have to be patient with the commands you send from the control panel. Sometimes it reacts quite fast, sometimes it takes forever and seems to timeout.
I thought about trying a reinstall, but I've already got quite a bit setup and I'd lose that work. If I don't hear back on my ticket I'll probably eventually go that route, though.
I asked @HostSailor for an upgrade to a bigger plan, as they said is possible but they are not allowing me
should have bought the largest one from the getgo