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
Its probably the hypervisor
I recall similar issues earlier and support said:
It seems that your Boot-Image does not support UEFI. On BHYVE the VNC console only works with UEFI images. To solve this we switched the hypervisor from BHYVE to KVM. The VNC console now works as expected.So switch to something that supports UEFI/ request change to KVM.
I tried several UEFI images from the provided list without success. I chose this service specifically because it uses BHYVE, so I would prefer to stick with this hypervisor if possible. l’ll give it another shot later.
hmm, yeah sure - maybe talk with support. they may be able to find a solution faster.
Hm, mine Dus storage-1 has "tsc" by default (and I have 1G upload speed)
I encountered the same problem as you. The Debian template of UltraVPS seems to have this problem. It can be solved by switching to Ubuntu, and VNC will be normal.
FYI) I'm installing Debian 13 from the Ubuntu Template (NOT IMAGE)
When I click "Order," the first two options redirect me to a blank page with "No such category."
And there's no available payment method listed. Can I use crypto?
25Y-Special-* are sold out.
It's bcs of GRUB config.
Try this:
SHOWS below
choose vda3⬇️
update-grub
reboot
Check the VNC output, It should work.
Thanks for the solution, it works well.
VNC is very slow but anyway but at least install is done
I still don't quite grasp why the serial port output from the Grub of the current virtual machine affects the serial port output when booting the Boot Image into noVNC or jsVNC, but it seems this step is fine as it stands.
I initially tried to manually install a new LVM system by loading Alpine into RAM via the UltraVPS rescue mode, but since its rescue system kernel was too old (it was Linux 3.x, I believe), I ended up following [this guide] https://m.zsh.moe/memos/33shoX2rGFnUepyckCJmNh to manually hot-migrate the partitions and set up LVM logical partition migration. Currently, it seems to be working out without issues.
I'm not entirely sure if this step is perfectly correct, but at least on my Debian 13 system, it has been working smoothly for several days now.
I try several boot iso images, only the ubuntu 24.04 works, I guess it's stucked at bootloader page; So I try to put the netboot.xyz.efi to the EFI partition, and reboot into the EFI shell, then run the netboot.xyz.efi, it's works.
Hello mjj, just to use the EFI shell to run the netboot.xyz.efi
Thanks\
Anyone else have their VNC console break? (Just always
Failed to connect to server (code: 1006)). Serial console is working fine. I installed my VPS using a custom iso (with netboot). Yesterday the VNC console was working fine, today somehow it stopped. I first had this a couple of days ago, opened a ticket, support asked me to reinstall because the couldn't find anything, but now it's happening again. Not a huge deal, but it does seem like a bug to me.Edit: to clarify: it's working for me as well on one of my other servers, it's really specific to this server somehow.
It works for me.
But in my opinion, their VNC console is still pretty buggy, given how many issues I've had with it.
It's a shame, because other than that, their control panel is actually quite good.
I can't place any orders, it seems I'm too late :')
Not buggy in my opinion.
It's bcs of FreeBSD which has very different technical architectures.(with PVE, VMware)
I really like the stable VMs I have right now. It would be even better if it provides a /64 subnet.