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.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.

Comments
Ok I found out that the problem was
ufw. Even though ports 80, 443, 21, 53, 465 and 587 are open but it seems this speedtest works on a different port. Once I disabledufwit worked.holy moly CPU steal
Glad to hear that
I just tried to press boot button again and still no luck. My VM still in offline state.
Below is from troubleshoot button :
Main IP pings: false
Node Online: false
Service online: offline
Operating System: windows-2016-virtio-x86_64
Service Status:Active
Registration Date:2018-11-25
@VirMach , please check if there are any un-lucky VMs in node AMSD026 that cannot boot. Maybe one of them is mine...
Did you try to unmount any iso you might have? as that is one of the issues
@VirMach Problems here too, at RYZE.DEN-Z001.VMS node. Various weeks no booting
Main IP pings: false
Node Online: true
Service online: offline
Operating System: linux-ubuntu-18-x86_64-legacy-gen2-v1
Service Status:Active
Registration Date:2016-11-15
@VirMach LAXA024 has no internet for more than a week, looks like the gateway has not plugged in.
no problem at all with laxa024. my vps has 9 days uptime
Tokyo ipv6 seems to be gone, no ipv6 network now
Sir, please add it back, please...
Yea, same here. I'm pretty sure they're on it though. @VirMach
Virmach's service is rotten, it's a cowboy operation, they migrate everyone's services trashing a bunch of stuff in the process and customer support is non-existent. And the $15 charge threats while submitting a ticket that they never answer for weeks on end is a joke.
Since the network improvement, the upload speed of my VPS on node JP27 does not exceed 10Mb/s.
iperf3 testing from Hong Kong
[ ID] Interval Transfer Bitrate
[ 5] 0.00-2.00 sec 1.98 MBytes 8.29 Mbits/sec
[ 5] 2.00-4.00 sec 1.68 MBytes 7.05 Mbits/sec
[ 5] 4.00-6.00 sec 1.82 MBytes 7.65 Mbits/sec
[ 5] 6.00-8.00 sec 2.07 MBytes 8.70 Mbits/sec
[ 5] 8.00-10.00 sec 2.74 MBytes 11.5 Mbits/sec
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.05 sec 12.9 MBytes 10.7 Mbits/sec 20 sender
[ 5] 0.00-10.00 sec 10.3 MBytes 8.64 Mbits/sec receiver
If you don't know how to fix these problems, contact the relevant technical experts instead of trying to fix the problems by yourself while learning.
And what what percentage of these problems are due to us dumb end users?
IMO this is a rather naive comment. You do realize don't you, that many of these issues were the result of DC hands, hardware manufacturer, and industry leading software. "experts" ? Besides what good is it really going to do if you try to make yourself feel better by taking a dump on VirMach?
@donb
I am on DENZ001 and have not had any issues at all, so the node is up and working well.
Lets see if we can get you going regarding your VM...
Have you gone into SolusVM* panel and made sure that no ISOs are mounted?
This will keep your VM from booting.
Have you tried installing a "Ryzen Compatible" template version of ubuntu also from the SolusVM panel, not the billing panel.
Does your VM show online in the billing panel ? If so what errors do you show when you access via VNC ?
*The SolusVM panel can be accessed by clicking the "VPS Control Panel" button from your VM in the billing panel.
Echoing this^. My Denver VPS works fine and control panel also does not disconnect...
@VirMach Have been using the server in Buffalo for the past 2 years with no significant issues, but yesterday got suddenly locked out of the panel with the message "The node is currently locked". Not sure where to check the exact node number, but it's been locked for over 24 hours now, so I can't do absolutely anything with my server.
I made ticket #166564, but I am mostly curious as to how much longer I will be locked out, and will my data be preserved? Due to me not subscribing for migration and not getting any warning in advance, I am hoping that I won't have to wait for weeks like some other people here.
https://www-jifengba-com.translate.goog/135458?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US
@TimesAndPlaces I would expect that your VM is being migrated with data and will probably be finished in ~48 to 60 hrs based on what I have seen in the past. (The time to migrate the whole node, not just your VM) You will get a new IP and will need to update your network configuration. If you have any issues after the migration is finished, feel free to ask them here. Tickets are not really a thing right now.
--
I guess that explains a lot of these recent posts.
I've been down for 16 days with no communication from VirMach whatsoever, my ticket has been unanswered for 15 days now. I'm fairly confident I'm down due to the Ryzen migration, but my node (DALZ004) has never been mentioned and I never actually got the "you are going to be migrated" email.
@VirMach I'm begging you for at least a status update.
Hey @FrankZ , you're usually paying more attention than I am. One of my NY boxes got migrated and afterward has the dreaded "No bootable media." Tried to reinstall from ISO and fdisk spits a bunch of errors trying to access /dev/vda. I'm thinking my sync went poorly and my disk didn't get created properly. Is that one of the ones that @Virmach cleans up automagically or do I need to ticket it? Appreciate any clues you can pass me. Was a redundant node so I can wait. Just want to make sure I'm waiting for a purpose.
@VirMach my ip:185.97.146.236, Can't access control center,
The page says "Operation Timed Out After 90001 Milliseconds With 0 Bytes Received",
@TimesAndPlaces that would indicate that you're getting your free migration to a Ryzen server (free 2x/3x CPU and IO upgrade in the process)
Difficult to predict exactly how long it will take, usually only a couple of hours or a day or maybe 2 or so if all goes well.
And if all goes well yes, all your data will be preserved and migrate with you.
With a few VM's, there are at times some glitches that occur if you are unlucky and then it might take longer, but they do their best to then resolve it ASAP.
I'd advise you first close the ticket, as to not overwhelm their ticketing system.
And if things aren't up and running again within 24 hours from now, then you ask here again and someone would be able to tell you whether you should open a ticket for your case.
BUT, if all goes well, you'll be up and fine and running Soon™
Go back few pages here and you should find a solution to your issue. In most cases you'll just need to reboot the VM or reconfigure the network.
@Ademan - If you are on DALZ004 you are already on Ryzen and are probably not being migrated. There were some issues with Dallas Ryzen (DALZ003 & DALZ008) for me more then a week ago, but that has been resolved. What issues are you having?
@skorous - If you are getting the "No Bootable Disk" after migration, and you have done all the normal things to get it to work, your VM probably did not create correctly and that is something that VirMach will take care of eventually. I expect that he makes the rounds to fix these every week to ten days bases on when they have been fixed for me in the past. I do not ticket for this, and they do get fixed anyway.
@Totti - The billing panel is not connecting to the SolusVM on your node. There can be various reasons for this. It will get fixed, but may take a few days or more. No need to ticket for this one, VirMach already knows, but is probably waiting on DC hands because if you can't access it via the billing panel probably he can't as well.
If you are on NYCM101 as I am, we have been having this issue since the 18th
Thanks I've been a bit cautious about randomly pressing buttons without knowing the actual status of my VM, but I have tried rebooting. I just tried reconfigure network, and it fails with "Networking could not be reconfigured. Unknown operating system". I'm using the very obscure Ubuntu 20.04 LTS server ISO that VirMach provides.
Thanks for the response. My VM is offline, can't boot/reboot it (it says succeeded but never comes online). I still have the "Migrate" option in the ("Client Area") panel up there with "rDNS" and "Switch IP", not sure if that has anything to do with the Ryzen migration, though. As far as I know, my VM never actually said "Locked" in the panel, but I could have just missed it.
VNC from solus fails with "Failed to connect with downstream server". Admittedly I haven't tried pointing my own VNC client at it, the html5 one has always worked fine for me in the past.
Reconfigure Networking fails and it seems like that's just a consequence of my choice of guest OS unfortunately.
Can I (safely) share my ticket number here in case @VirMach notices me?
EDIT: May as well include
This is normal stuff and has nothing to do with migration.
Go to SolusVM from the billing panel by hitting the "VPS Control Panel" button
and make sure that you do not have any ISO mounted, your VM will not boot with an ISO mounted.
Also from SolusVM hit the "Power off" button, not the "Shutdown", wait 5 minutes and then hit the "Boot" button. This only works rarely, but it is worth a shot.
The reconfigure networking is not going to work right because your network interface for this ISO install is not eth0. Once the VM is online you will need to reconfigure the networking manually by editing what I expect to be
/etc/netplan/01-network-manager-all.yamlbut you should double check by editing what file is shown byls /etc/netplanYou can share it safely, but it will not make anything go faster, so I would not.
@FrankZ - you wrote:
Please let me know if you have a working VPS on DALZ008.
Or if anyone has a working VPS on DALZ008 please post here.
Thanks, doesn't appear to have worked unfortunately, but worth trying.
I'm not positive how to read this, but I'm inferring that "Node Online: false" indicates DALZ004 itself is offline? I'm presuming "Service online: offline" is referring to my VM. Either way the troubleshooter summary says at the top that "the host node" (DALZ004) is down, and presumably has been this whole time.
Thanks, tbh I can't keep up with the network management changes, take me back to
ifupdownlolEDIT: formatting
EDIT EDIT: formatting!
EDIT EDIT EDIT: Clarified question/comment about the troubleshooting output