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
Same server, same situation
FFME003 works really well..
... through VNC only because the network is borked, but there HAS to be a way to implement IP-over-VGA through VNC, right?
My instance on NYCB019 has just been unbootable for 3 days...
No response from virmach support.
You're not alone with your experience at NYCB019 if that's any consolation. I've not contacted support since they say they're going through and fixing these sorts of issues one-at-a-time.
Timing was unfortunate. I made some big changes to my icinga2 config (this was my master host) and my nightly backup hadn't run yet by the time the migration happened, so I'm 50/50 on whether I should redo that work or wait to get access to those configs again. Just trying to be patient as I can only imagine what they're going through over there.
I am migrated to NYCM103 and NYCB57. The service I purchased included 10gbps. So far not experiencing any of this and it freaking keeps disconnecting multiple times throughout the day. Every commands responds super slow if at all. Why are you not fixing issues first before continuing the migration. It seems about 75% of the migrations all have problems that are still being investigated or being prioritized to be fixed.
Didn't think I'd end up posting a complaint since everything was going so smoothly...
Is there any chance we can get our old IP back? I've got a server on TYOC039 that was working fine until the arbitrary IP change yesterday. Normally I'd just update the DNS settings, but I don't have direct access to the domain it is hosting services for and getting it changed is going to be more of a hassle then just asking here.
Also tried looking back into this thread as to why the IPs are being arbitrarily changed but couldn't seem to find any real information and the post on the network status page doesn't really explain much other than "it's happening".
Migrations are happening from one data center to another. New IPs are going to be used. Your choice to make switch or wait for @virmach to reply the same
Some Ryzen IPs are changing due to going from large subnets to small (/24) subnets. This is being done to resolve the network (arp) issues that people have been complaining about.
You really should figure out a way to change the DNS as the only way you could get that IP back is to be moved to the node that currently has that /24. This is not likely to be done in a timely fashion at the moment.
I feel for you and the problem that this may be causing you. I've had seven of my Ryzen IPs changed and yes it is a bit of a PITA, but it will be better in the end.
Thanks for the attempt, but it doesn't really answer the question.
Darn, that's unfortunate. Well, time to pull some teeth.
The lesson is, whenever you use a domain controlled by others:
I'll remember this for next time, but the underlying issue is that the IT department of the organization I'm working with doesn't understand "please set the A record of the domain to a.b.c.d". I guess asking them for a CNAME from the get go would have been the ideal play, but TBH I've never had the need to before.
@VirMach
Node Name SJCZ008
my ip is unavailable 194.33.39.19
productdetails id:637647
always offline
VNC doesn't work either / can't ping
Please help to solve it. Thanks
MJJ is invincible
I'm thinking that I spend a lot of time every day looking for comments on the forum to see if you have fixed it. Your ticket system is directly paralyzed
Main IP pings: false
Node Online: false
Service online: online
Operating System: windows-2012-r2-virtio-x86_64
Service Status:Active
Registration Date:2019-12-05
It's been 2 days and DALZ009 still showing that status...
So I've moved my database replication to AMSD025.
Wanna bet how long it's gonna be online? ^.-
https://i.ping.pe/r/8/img_r8f3d1C4.png How long will this situation last?

@jholycloud - Can you access via VNC? but have no networking?
Some VMs in Dallas changed IPs a couple of days ago.
You might need to change your IP address in windows.
@VirMach
Well, how much can you?!
At the end of June, VDS forcedly migrated from Amsterdam to FFME004.VIRM.AC. Everything worked for a couple of days, but then "Boot failed: could not read the boot disk." A few days later, VDS generally switched to offline status. Yesterday everything was fixed and VDS worked fine. Today, in a day, VDS is offline again. It started up through the panel, but now again "Boot failed: could not read the boot disk."!
Ticket created on June 30 (#416057), no response.
Another working VDS was forcibly migrated to RYZE.PHX-Z002.VMS a few days ago. Since then the status is offline. I can’t create a new ticket, because you will simply close the previous one.
Well, have a conscience...
@VirMach you are right, i was UP for almost 24 h now its gone again...good work
@cold - TYOC039 is not down. My VM on the node is doing fine.
That has been the best node of the three I have in Tokyo.
come to 27 or 28
Already there.

@DanSummer is your server having a connection to the internet now?
Two of my servers are on those LAXAxxx nodes and still cannot connect to the internet.
im talking about Amsterdam FFME004
Any ideas, why my LibreNMS monitors show much more CPU usage with Ryzen migrated VPS? For example my email-server, at Xeon node CPU usage was about 10% average, Max 20%. Now average is 29% with Ryzen. YABS benchmark is much better with Ryzen node.
Same is also almost all migrated VPS's. Last migrated Dallas DALZ004 idling Debian 11, was about 3% at Xeon, now average is 11%.
Could be steal, could be iowait, could be this fucking arp packets. Check
topoutput at least.Can you see IPv6 address in SolusVM?
Yes, you can see your IPV6 address in SolusVM on FFME001

-placeholder address, of course-
My dead server on FFME has slept more than a week but finally woke up some hours ago.
Still observing.
Hope it'll not have i/o issue anymore.
I have one in Frankfurt but not FFME001. I still cannot see IPv6 in SolusVM.
Seems it's still not setup for me.
Yes, I have no IPv6 on FFME002.VIRM.AC. I think FFME001 was testing node for those IPv6s and I guess they simply run out of time for rest due to Amsterdam emergency migration. I guess matter of time.