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
@VirMach> @VirMach said:
@VirMach
please help me to see what's problem,thx!
What abou the SEAZ005 QAQ
Failed to connect almost 3 weeks
Or am I need to use Ryzen Migrate from SEA to SEA?
IP: 149.57.132.*
node: LAXA010
template: [Ryzen Compatible] Debian 10 (64-Bit)
Has nothing to do with the node most likely, I can't help you here, you'd need a ticket.
RYZE.LAX-A011.VMS
Does this look like ryzen?
check the tickets: #404227 #753443
I have the same problem,no ryzen mirgation button,paid migration always stuck.I have used virmach for five years,I never create useless tickets,I am confused about the differential treatment 。
Like I said before Virmach is a petty and mean company who always take things personally and never admit their own mistakes. I was a very quiet user until the failed migration, then I created a few tickets about the migration thing and then I became a problem customer, where is the fairness? If the migration is smooth why should I creat any tickets in the first place?
I have post ticket almost 2 weeks before
My ticket id: #837953
My server doesn't got the new ip and keeps the old cc ip.
Also there are some people in this node have the same problem
check here
Maybe you are right,I never created tickets about migration problem.The latest ticket that I created is more than one year ago.I don't know why I became a problem user.
The effective gateway in Los Angeles is not on the same network segment as the host IP. This is the reason of some network issues.
Sorry was there a list of looking glasses for the new Ryzen servers? Is there a deadline on when I have to migrate off my legacy VPS?
Trying to see if there's a deadline coming up soon or I can migrate whenever I please, as I have to restore everything back to the VPS afterwards...
Why not let Migration Special migrate?
Virmach's support is as confusing as their servers.A total mass!He should give us a reasonable explanation for this,otherwise we have the right to let the whole forum to know how unreasonable and discriminatory Virmach is to some individual users!We don't give up easily
@VirMach Unable to migrate to Seattle, other areas are normal, please check the reason! Thanks for providing this feature!
Ticket created for a week without any response, maybe it's time to solve the VPS offline issue on node 026
@VirMach Thanks for the ryzen migration. I have migrated the vps to where I want to migrate.
I just migrated using the Ryzen migrate button the following VPS:
From Amsterdam to Dallas Ryzen Node: DALZ003, no issues.
From Amsterdam to Amsterdam Ryzen Node: AMSD026, no issues.
From San Jose to San Jose Ryzen Node: SJCZ008, no issues.
From Los Angeles to Los Angeles Ryzen Node:LAXA009, had some issues when installing from [Ryzen Compatible] CentOS 7 Latest template in SolusVM and from Linux Centos 7.1503.01 X86 64 Minimal Gen2 V1 template in billing panel.
Fixed by Installing from CentOS 7 minimal ISO in SolusVM no issues other then I had to manually set the netmask to 255.255.248.0 as DHCP was trying to set it to 255.255.255.0 when gateway was not on the same /24.
All transfer allotments show correctly.
The ones that I had tried to migrate previously, and were assigned an IP, ended up with two new IPs. I have removed the second IP from networking in the associated VPS.
@VirMach is there space in NYC to migrate my 8GB RAM Buffalo to NYC, I don't want to get that one stuck, so I wanted to ask before hand.
Tried "your" one:
Perhaps it's the already assigned (Skits?) IP - 149.57.191.xxx - that's screwing it up.
Same issue,8GB RAM Buffalo can't be migrated.
Maybe haven't enough space.
i sent a ticket for technical support a week ago,but no response.could you please check it?the ticket number is #704391
i sent a ticket a week ago,and now i build a new ticket,no one answered me.it keeps showing awaiting technical review for a week.i have no idea how to deal it,so i ask for your help here.the new ticket is #580695.i run the troubleshoot,the result is :
Main IP pings: false
Node Online: false
Service online: offline
Operating System: linux-debian-11-x86_64-gen2-v1
Service Status:Active
Registration Date:2022-03-13
Out of curiosity I clicked Ryzen Migrate button on KVM-Special-512.
I got new 2 IPs.
SolusVM panel provides Ryzen Compatible OS, while billing panel provides older OS.
I don't think it was intended so I'd like to test it to provide more information, but I don't have the time...
On my vps7 in Atlanta, last time the button gave me a (supposedly) New Jersey IP.
Now I'm (wishfully) waiting for Miami, and not pressing the button again.
migrate to AMS from NY Buffalo
Do it. Do it!
IIRC VirMach said he was low on space in NYC until next week, that is why I asked about moving my 8GB. If you can't move your 8GB to NYC, then I can't move my 8GB to NYC yet. Thanks for answering my question.
My vps on SEAZ003 (that was moved from 1 on last downtime) was down for more than 12 hours. There is no mention in status page. Anyone else on that node have any problem?
once asked for a refund, the machine only replied, after 1 week the ticket automatically closed itself, had sent a ticket several times only the machine replied and it automatically closed. Have you asked for a migration and have already paid 3$, the ticket automatically closes and the VPS still doesn't move, have you ever commented on this group there is no response and clarity, how is this??? should be 6TB why only 2TB?? confused what to do?? internet speed is also still fluctuating and unstable. confused. @VirMach Invoice #1404808
--
I was on SEAZ001 moved to SEAZ004 and I am getting:
So it looks like the node is still down from the maintenance to me.