@Jab said: @VirMach copy-paste from LET, I am to stupid to understand it, but maybe important
@jtk said: I saw reports of intermittent reachability. I suspect, a problem now is that QuadraNet is announcing a /20 in this prefix, but there are only ROAs with Alibaba's origin ASes published in the RPKI for the covered address space, which means many nets will be invalidating and rejecting the QuadraNet announcement. Let's see how long it takes people in the LES thread to figure this out. :-)
That was me. In a nutshell, I suspect some of those who were reporting partial connectivity (e.g., through a VPN, but not from their home cable provider), were able to temporarily reach their systems, because their VPN provider accepted a /20 route from QuadraNet, while their cable provider did not. The reason for some providers not accepting the route was due to a missing, corresponding ROA (route object authorization) published into the RPKI.
In a nutshell, the RPKI is to routing what DNSSEC is for DNS. A ROA is an attestation that a particular origin AS is authorized to announce a particular prefix. If a BGP announcement is made with an origin AS not in a corresponding ROA, many providers will drop the route, and this is known as enforcing ROV (route origin validation). There are now associated ROAs to authorize QuadraNet, among others, to originate prefixes in the /17. This was not the case yesterday.
From what I can tell, Virmach has nothing to do with this process and it is probably all more-or-less automated by Alibaba. My guess is that was probably the last thing Alibaba had to update to restore full connectivity.
Patiently waiting to be able to set rDNS for new NL.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
@shallow said: Inorite? I'm getting tired of my friends seeing my vps' ip address in our private irc room. I have silly vanity domains that need to be put to use.
That's where IPv6 tunnel come handy :P
Oh, and don't dare to join my channel just to say "Ciao a tutti" (in colours!) and then immediately leave.
Oddly enough after reading most of the thread I had to go over and check them out. Tried to buy a hosting plan, well because reasons, and could not create an account or even buy the vps.
Should I actually contact support or should I just wait a couple months? This server is in Los Angeles; I've got one in Seattle that's still 'on hold' for IPv6, so not sure it's worth bothering support if they're not deploying IPv6 in LA yet.
@ehab said: @VirMach should we open tickets if the vps is missing IP's ? this was from the recent change.
We're working on a solution, we've already flagged down how many IPs each plan should have and will use that to auto clean them up. But you can also use the missing IP button if it's there.
Should I actually contact support or should I just wait a couple months? This server is in Los Angeles; I've got one in Seattle that's still 'on hold' for IPv6, so not sure it's worth bothering support if they're not deploying IPv6 in LA yet.
If it fails and you contact support make sure you make it more about the function not working rather than mentioning you want IPv6 or it will probably be closed/told to use button.
That way we can see what's going on with that so you can make the request.
But at this point the request button isn't really how people think it is, we're basically using it as a voting system to know which ones we should do first in bulk node by node.
(edit) Actually don't even mention the button not working, you should definitely make a ticket for the virtual server missing error as that will cause other problems too.
About 20% of missing IP addresses added back, this also includes anyone who didn't previously use the button now that we're cleaning it up. Only one person so far didn't get it added because the node was out of IPv4 addresses (so that's pretty rare right now.) I assume that may become a problem only for Tokyo and San Jose, maybe Los Angeles.
@VirMach said:
About 20% of missing IP addresses added back, this also includes anyone who didn't previously use the button now that we're cleaning it up. Only one person so far didn't get it added because the node was out of IPv4 addresses (so that's pretty rare right now.) I assume that may become a problem only for Tokyo and San Jose, maybe Los Angeles.
Thanks I can confirm my 2019 BF deal now has the extra IP that was gone from 2022 Colocrossing fiasco.
@VirMach said:
About 20% of missing IP addresses added back, this also includes anyone who didn't previously use the button now that we're cleaning it up. Only one person so far didn't get it added because the node was out of IPv4 addresses (so that's pretty rare right now.) I assume that may become a problem only for Tokyo and San Jose, maybe Los Angeles.
what button is it? all i can see is this "Ryzen Fix IP"
@VirMach said:
About 20% of missing IP addresses added back, this also includes anyone who didn't previously use the button now that we're cleaning it up. Only one person so far didn't get it added because the node was out of IPv4 addresses (so that's pretty rare right now.) I assume that may become a problem only for Tokyo and San Jose, maybe Los Angeles.
Sir I have missing IPs since months, when you get time please check Ticket #340971
@VirMach said:
About 20% of missing IP addresses added back, this also includes anyone who didn't previously use the button now that we're cleaning it up. Only one person so far didn't get it added because the node was out of IPv4 addresses (so that's pretty rare right now.) I assume that may become a problem only for Tokyo and San Jose, maybe Los Angeles.
Sir I have missing IPs since months, when you get time please check Ticket #340971
We haven't made it to the backlogs yet for tickets created by previously multi-account flagged people and such.
@rockinmusicgv said: I am wondering if you've managed to debug the RAID issues you were having with the NYCB009SH node. Have there been any updates in that regard?
Unfortunately no update, it's gotten worse and worse. There have since been like 3-4 attempts to get access to it again, as in remote hands power cycled it, etc. Trying to decide wat to do but what we can do is limited.
The goal is to still get everyone back online as soon as possible but it's a situation where we also need to make sure we retrieve data. We do have backups, but as you can imagine with the server crashing multiple times, they're scattered all over the place and unreliable so it's best to get to the data directly on the node, if we can just get it online and stable for a few hours. Then we need to move everyone to another node, except we've already had to deal with multiple other issues in this location and are low on deployed servers.
@ehab said: what button is it? all i can see is this "Ryzen Fix IP"
No button, automatic in the background.
@fan said:
TYOC040 is at it again, I/O error - reboot - no bootable device.
Reporting system hasn't caught this yet, will take a look. I think we mostly need to send everyone an email explaining not to mass re-install, reboot, whatever else. It won't fix it and it'll just make it worse pretty much every time. We could lock it off after maintenance and it'll be stable for however long but we can only do that for so long and deal with the mass tickets and of course people do need controls.
It's just otherwise going to be a domino effect, no matter how healthy the disk. All it takes is one particularly busy Friday or Saturday and then weeks of repeat.
Missing IPs all done except super super old BF-OVZ and BF-KVM plans, so I think basically the first year we did flash sales. Only reason I didn't update you earlier was because of those two products but those still aren't done.
rDNS is functional for Frankfurt, Tokyo, and Amsterdam now, although I'm just saying that and haven't tested it yet.
Tickets mostly caught up to and number of tickets created normalized since the IP fiasco.
I had a longer post for these that I just cleared and didn't send but I patched a lot of the nodes that have had recent issues again, and going through and doing it for nodes with under 100 days or so uptime soon.
NYCB009 (Shared hosting) is still very much dead, but I got it to the point where some progress was made on it. All like... 2 hours it stayed around. I think we've probably made like a dozen hands request for it by now, I should just fly to New York or send it back if we don't make some major progress in next few days.
Comments
Finally, all VPS are back!
AMS
LAX
SEA
above are up
SJO seems down
I bench YABS 24/7/365 unless it's a leap year.
That was me. In a nutshell, I suspect some of those who were reporting partial connectivity (e.g., through a VPN, but not from their home cable provider), were able to temporarily reach their systems, because their VPN provider accepted a /20 route from QuadraNet, while their cable provider did not. The reason for some providers not accepting the route was due to a missing, corresponding ROA (route object authorization) published into the RPKI.
In a nutshell, the RPKI is to routing what DNSSEC is for DNS. A ROA is an attestation that a particular origin AS is authorized to announce a particular prefix. If a BGP announcement is made with an origin AS not in a corresponding ROA, many providers will drop the route, and this is known as enforcing ROV (route origin validation). There are now associated ROAs to authorize QuadraNet, among others, to originate prefixes in the /17. This was not the case yesterday.
From what I can tell, Virmach has nothing to do with this process and it is probably all more-or-less automated by Alibaba. My guess is that was probably the last thing Alibaba had to update to restore full connectivity.
Dataplane.org's current server hosting provider list
Patiently waiting to be able to set rDNS for new NL.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
GLWRDNS
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
It's gonna happen... this time.
Inorite? I'm getting tired of my friends seeing my vps' ip address in our private irc room. I have silly vanity domains that need to be put to use.
That's where IPv6 tunnel come handy :P
Oh, and don't dare to join my channel just to say "Ciao a tutti" (in colours!) and then immediately leave.
Weekly check whether Virmach ran away.
No yet, see yor chaps next week
Ontario Dildo Inspector
This is one of the reasons why I check if Virmach has gone out of business once a day.
Hey @VirMach had a decent amount of sleep?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Weed, beers and hookers!
Ontario Dildo Inspector
Laxa032 is timeout right now
I have 2 or 3 vps with extra IP's per vps and after the change have only main IP! did any get the extra IP's visible in the the cp?
it's still time out.
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
Can't connect via ssh either.
But it shows green on this page: https://statusbot.virm.ac/en/
No one on the same node?
Oddly enough after reading most of the thread I had to go over and check them out. Tried to buy a hosting plan, well because reasons, and could not create an account or even buy the vps.
Should I actually contact support or should I just wait a couple months? This server is in Los Angeles; I've got one in Seattle that's still 'on hold' for IPv6, so not sure it's worth bothering support if they're not deploying IPv6 in LA yet.
TYOC031 is down.
Yeah, just woke up.
rDNS/PTR for Frankfurt, Amsterdam, and Tokyo should be done soon (available on SolusVM.)
These got cleaned up. Not down, just overloading. Ran the newest patch for them yesterday, hopefully will prevent future overloading.
Have you updated the IP Geo info?
https://microlxc.net/
Thanks for quoting my post, I love random notifications.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
that's quite a long sleep
I bench YABS 24/7/365 unless it's a leap year.
@VirMach should we open tickets if the vps is missing IP's ? this was from the recent change.
Yes.
https://microlxc.net/
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
It's been put in, now it's up to them (main few companies) to process it or however long it'll take.
We're working on a solution, we've already flagged down how many IPs each plan should have and will use that to auto clean them up. But you can also use the missing IP button if it's there.
If it fails and you contact support make sure you make it more about the function not working rather than mentioning you want IPv6 or it will probably be closed/told to use button.
That way we can see what's going on with that so you can make the request.
But at this point the request button isn't really how people think it is, we're basically using it as a voting system to know which ones we should do first in bulk node by node.
(edit) Actually don't even mention the button not working, you should definitely make a ticket for the virtual server missing error as that will cause other problems too.
https://microlxc.net/
About 20% of missing IP addresses added back, this also includes anyone who didn't previously use the button now that we're cleaning it up. Only one person so far didn't get it added because the node was out of IPv4 addresses (so that's pretty rare right now.) I assume that may become a problem only for Tokyo and San Jose, maybe Los Angeles.
FREEEEEEE IPS, someone wanna sell those server?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Thanks I can confirm my 2019 BF deal now has the extra IP that was gone from 2022 Colocrossing fiasco.
Its available in SolusVm to change rDNS, also update it when you press update, but its not actually change it yet. Thats on 213.232.11x.xxx subnet.
ServerStatus , slackvpn , linux mirrors
Recommended Providers: Servarica(aff) | HostBRR(aff) | SolidVPS(aff) | RackNerd(aff) | KuroIT(aff) | AlphaVPS(aff) | HostDare(aff)
Weekly check whether Virmach ran away.
Yeah Virmach is still very much alive
Whaaaaaaaaaaaaaaaagh
If all of them are in the 47.87.0.0/16 block, wa'z the meaning of multiple IP?
Ontario Dildo Inspector
Good morning.
Have a Virmach day.
I am wondering if you've managed to debug the RAID issues you were having with the NYCB009SH node. Have there been any updates in that regard?
what button is it? all i can see is this "Ryzen Fix IP"
thanks for anyone can tell where to find a button
TYOC040 is at it again, I/O error - reboot - no bootable device.
Sir I have missing IPs since months, when you get time please check Ticket #340971
We haven't made it to the backlogs yet for tickets created by previously multi-account flagged people and such.
Unfortunately no update, it's gotten worse and worse. There have since been like 3-4 attempts to get access to it again, as in remote hands power cycled it, etc. Trying to decide wat to do but what we can do is limited.
The goal is to still get everyone back online as soon as possible but it's a situation where we also need to make sure we retrieve data. We do have backups, but as you can imagine with the server crashing multiple times, they're scattered all over the place and unreliable so it's best to get to the data directly on the node, if we can just get it online and stable for a few hours. Then we need to move everyone to another node, except we've already had to deal with multiple other issues in this location and are low on deployed servers.
No button, automatic in the background.
Reporting system hasn't caught this yet, will take a look. I think we mostly need to send everyone an email explaining not to mass re-install, reboot, whatever else. It won't fix it and it'll just make it worse pretty much every time. We could lock it off after maintenance and it'll be stable for however long but we can only do that for so long and deal with the mass tickets and of course people do need controls.
It's just otherwise going to be a domino effect, no matter how healthy the disk. All it takes is one particularly busy Friday or Saturday and then weeks of repeat.
Just wanted to report that my missing IPs @ FFME004 are back, thank you!
Contribute your idling VPS/dedi (link), Android (link) or iOS (link) devices to medical research
EPYC?!
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
where??!?!
I bench YABS 24/7/365 unless it's a leap year.
Buffalo??!?!??!?!
🦬
We accept Karma donations for the last flan. 🍮 affbrr
Yo the old fart said EPYC in Tokyo approximately 1 year ago I suppose,
Don't expect its coming in the near future I dare say
Ontario Dildo Inspector