@VirMach 23.95.68.151 is always offline a long time,can you help me to slove the problem?In additionally,the migration of Ticket #160581 is also handled together,thank a lot.
By the way,is there time compensation for being offline for too long?
@hmx27 said: @VirMach 23.95.68.151 is always offline a long time,can you help me to slove the problem?In additionally,the migration of Ticket #160581 is also handled together,thank a lot.
These are being planned out and done very soon. We just want to make sure we do it properly at this point, to where people go on a stable node, have functional networking, operating systems, and we communicate it properly and credit everyone accordingly.
I almost sent out an email a few days ago outlining everything but it wasn't clear enough so I didn't send it out yet. I'm trying to get everything down 100% because people have already waited so long, I want to make sure we do a perfect job and don't confuse people further or drag it out by providing incorrect dates, vague information, etc.
@haynhat said: @VirMach
Is SJCZ004 still facing partial outage (no more outage message in network status)? I have 6 servers there but 2 of them still remaining offline.
@VirMach said: If you genuinely believe you created specifically a ticket marked as a connection issue with packet loss, and you were one of the very few people that genuinely followed all instructions before creating the ticket, and you are still facing said issues, then give me your ticket # and I'll take a look.
My concern with that statement is that my ticket is about no public network and I don't ever remember marking my recent ticket as being about packet loss.
I've already done the troubleshooting, from reinstalling the system, setting IP configurations manually, and using reconfigure networking on a fresh install (which is its present state). Ticket #677100.
At this point, if there's no resources to look into it, I'd rather just the cost of the service refunded as account credit so I can just consolidate what services that are still functional.
@VirMach
My Ticket also got closed without any proper response,
Ticket #262275
My Node: FFME001.VIRM.AC
I know you already mentioned the node is up in one of your replies here. But still my vps is down. Unable to connect. Earlier I didn't had solusvm panel control access for this node. So I thought it must have been panel's fault but now the panel is up and I am able to browse it. Still it's offline, I tried to reboot/reconfigure network but no success.
I thought it was just me but one of my friend who is on same node facing exact same issue.
@Kaito said: @VirMach
My Ticket also got closed without any proper response,
Ticket #262275
My Node: FFME001.VIRM.AC
I know you already mentioned the node is up in one of your replies here. But still my vps is down. Unable to connect. Earlier I didn't had solusvm panel control access for this node. So I thought it must have been panel's fault but now the panel is up and I am able to browse it. Still it's offline, I tried to reboot/reconfigure network but no success.
I thought it was just me but one of my friend who is on same node facing exact same issue.
This isn't closed. If it was closed it already got unclosed and re-flagged. I see the title's also changed so it's marked correctly for us to include it in the proper queue for that specific fix.
That would be these:
Generally what would happen after an outage like that is any VMs that were semi-broken before it would not have been fixed. It's in our queue to redo the fixes we did for any broken VMs for the nodes we skipped due to them being offline. It's very possible your offline services are part of those.
There are nodes in bursts of times where it may have had a specific problem that caused the VMs not to generate properly and that's what you're facing an issue on, for FFME001.
I've already cleared a few of these up today. We might get to FFME001 today as well.
Looks like SJC2008 is reachable from billing panel again, which is great, it had been unreachable before. Is this node still having network issues? Billing and control panels say my VPS is offline, attempting reboot doesn't change it, it's unreachable in rescue system, and VNC address refuses connections. It does say it's a Ryzen node, i.e. the VPS got migrated from the old Intel hardware. I guess that is nice.
@willie said:
Looks like SJC2008 is reachable from billing panel again, which is great, it had been unreachable before. Is this node still having network issues? Billing and control panels say my VPS is offline, attempting reboot doesn't change it, it's unreachable in rescue system, and VNC address refuses connections. It does say it's a Ryzen node, i.e. the VPS got migrated from the old Intel hardware. I guess that is nice.
I'm going to just make a wild guess based on all your previous terrible luck & experiences and say that you're probably one of the 10 people affected on this node by a missing disk. I have no idea what happened and won't know without looking back at all our logs later. They're all back to back, just 10 VMs that don't have a proper disk.
Right now they're on the queue to get created (the LVMs.)
@haynhat said: @VirMach
Is SJCZ004 still facing partial outage (no more outage message in network status)? I have 6 servers there but 2 of them still remaining offline.
I got an email [Emergency Migration] Your service on TYOC040.
which location has the least problem? I want to move it there.
looks like Amsterdam rarely has problems
@umzak said:
I got an email [Emergency Migration] Your service on TYOC040.
which location has the least problem? I want to move it there.
looks like Amsterdam rarely has problems
i got it too, and believe they are migrating to an empty node in Japan if maintenance doesn't work.
@umzak said:
I got an email [Emergency Migration] Your service on TYOC040.
which location has the least problem? I want to move it there.
looks like Amsterdam rarely has problems
@VirMach Sorry to bug you: I still don't get 2FA email and for some reason my backup code doesn't work (got locked out for a day). :'( Was working no problem until approx. 5 days ago.
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).
@VirMach said: SJCZ008 all set. If you still have a problem it may be something else.
Same thing as before, can't seem to reboot from panel. Should I assume the disk is trashed, and reinstall the OS? It's a slight nuisance if the old data is lost, but I can deal with it.
Aha, I was able to connect with VNC, which didn't work before. It said hard disk is not bootable and there was no CD/DVD mounted. I will try rescue mode and if that doesn't help, will reinstall. Glad to see this VM at least somewhat alive again.
Update: no luck with rescue mode so I reinstalled, and that seems to have worked. Nice to have this machine back. It would be nice to transfer its resources to the new one instead of having two. Probably too much hassle to think about right now though.
@vyas said: @virmach Tech support promptly closed the ticket, no explanation offered, some kind soul here on LES tried to suggest I try what I had already tried, and nearly 3 weeks later, no mas.
It's an outage report ticket. All we do for those is read the title and decide if a network status needs to be opened for it or if anything needs to be done and we're already working on it. We didn't add it to outage report because it's not actually offline, it's just a panel issue, and the outages on network status page are already very cluttered so we're reserving it just for actual outages right now.
Also you're not in Amsterdam, it's in Frankfurt, unless I looked at it wrong? Anyway FFME001 has uptime of 49 days and most VMs are running. Yours may potentially be offline and controls are broken though still but I'm just answering on why the report outage ticket was closed.
Indeed, VPS is in Frankfurt, (FFME001 prefix).
it's just a panel issue
I ask out of genuine curiosity and not disdain- can this be fixed at user level (ie from my side)? Or do I have to raise another ticket highlighting this specific issue? Thanks-
@willie said:
Looks like SJC2008 is reachable from billing panel again, which is great, it had been unreachable before. Is this node still having network issues? Billing and control panels say my VPS is offline, attempting reboot doesn't change it, it's unreachable in rescue system, and VNC address refuses connections. It does say it's a Ryzen node, i.e. the VPS got migrated from the old Intel hardware. I guess that is nice.
I'm going to just make a wild guess based on all your previous terrible luck & experiences and say that you're probably one of the 10 people affected on this node by a missing disk. I have no idea what happened and won't know without looking back at all our logs later. They're all back to back, just 10 VMs that don't have a proper disk.
Right now they're on the queue to get created (the LVMs.)
Thanks, after your response, my earlier FFME001 vm got replaced by FFME007 and now it doesn't have the disk.. and the ticket got renamed with LVM.
Hoping to get this also resolved soon 🥺
"ISO" and "Re-install OS" on my BF-SPECIAL-2020 have been fixed, but "VPS Control Panel" button still shows "Invalid vserverid or username". However, I hesitate to reply to the ticket just for that reason. https://i.imgur.com/viDVJKy.png
@VirMach I created a ticket a month ago and today you just closed it without any resolution, stating this excuse: "Your ticket has been marked as having a bad title, missing information, or improper use of a custom ticket department."
My ticket clearly stated that my VPS has no Internet connection. I've also tagged you here at least two times and mentioned that TYOC025 has this type of connectivity problem, but you've evaded answering my posts twice.
If sending support tickets on your platform doesn't result in a solution... if replying on a 3rd party website doesn't get a solution, then what else am I supposed to do? By closing tickets that we have been waiting months in queue for, in good faith, then you are making an already frustrating situation ten times worse.
I have opened a new ticket and followed all of your requirements. Please check my new ticket here and fix the connection issue. #634655 Thanks.
@VirMach said:
Does 2TB work or does it have to be 2x1TB?
Has there been any update to when a replacement server would be deployed? Its been beyond 6 weeks now. I already accepted the 2TB drive over 2x1TB and other US Datacenter besides West coast. Once again for your reference Ticket #342867
@willie said:
Looks like SJC2008 is reachable from billing panel again, which is great, it had been unreachable before. Is this node still having network issues? Billing and control panels say my VPS is offline, attempting reboot doesn't change it, it's unreachable in rescue system, and VNC address refuses connections. It does say it's a Ryzen node, i.e. the VPS got migrated from the old Intel hardware. I guess that is nice.
I'm going to just make a wild guess based on all your previous terrible luck & experiences and say that you're probably one of the 10 people affected on this node by a missing disk. I have no idea what happened and won't know without looking back at all our logs later. They're all back to back, just 10 VMs that don't have a proper disk.
Right now they're on the queue to get created (the LVMs.)
Thanks, after your response, my earlier FFME001 vm got replaced by FFME007 and now it doesn't have the disk.. and the ticket got renamed with LVM.
Hoping to get this also resolved soon 🥺
OS needs a re-install assuming the person handling it did it correctly. I'll try to check back on their work and make sure they created the LVMs properly but they should have done so.
@umzak said: which location has the least problem?
Mines are in PHXZ002 and TYOC033. While in Tokyo there were some problem at the beginning its quite stable for the last 2-3 months. PHXZ002 had been with me from 2015, and had done 2 migrations (1st one on better server, 2nd one on Ryzen CPU ) in same loc and i did not had single issue since 2015.
Yes, of course Not exactly among my favourite bands from Norway, but still among the biggest still active BM bands around. I never saw them live, but I saw Ihsahn (singers solo career) live in 2013 if this count
...and this part where Fenriz (Darkthrone) says "big sunglasses, not Emperor (small) sunglasses, very important, big sunglasees = cool band" always cracks me up
I think we're finally ready to start offering free migrations with data for a limited time. This is so people can end up where they really want without the hassle of having to load everything back in, especially for those people that ended up getting forcefully moved to an undesired location. We got the migration tool working again and figured out what's causing it to break so we can do these in daily batches.
There's a few caveats:
We're going to try and code something out where you pick three preferred locations. We will try to move you to your first preference, but may move you to your 2nd or 3rd preference. We'll allow you to pick your existing location as a preference if you'd rather it just be cancelled and not completed if your first preference isn't available (you pick it as second preference.) If we don't do this and it's just one preference selected, we'll reply back and say it's going to go in an indefinite queue to migrate when available. You can cancel this if you'd like by just closing the ticket.
We'll move you to a server with an IP block that may be swapped out in the future. So before you begin the process, there will be a warning that your IP address may be changed at a future date. We'll of course try our best to give you ample notice but if you migrate using this free feature, please expect worst case scenario for your IP address to be changed with minimal notice, so be prepared for this potentially occurring.
We'll try to complete migration within 72 hours so you have a 72 hour window where you know your service may go offline for migration. We'll also put a notice that in some cases it may take up to 24 hours to migrate if it runs into issues, so you're signing up for a potential 24 hour outage. We'll organize this to where if after 24 hours it is still not migrated, by default we'll just move you back, power it on, and say it failed.
You need to confirm that you have your data backed up. In rare cases there may be data loss when we're processing so many of these at once so at the very least, even if it's an unpleasant outcome, we want to make sure people understand this potential risk. I highly doubt we'll get too many of these in a state where there is data loss.
You need to confirm that you understand how to configure the network manually and confirm that you understand you may need to manually click the reconfigure button in case we're unable to get it to reconfigure properly the first time around. Since we're doing these in bulk there will be cases where the first reconfigure fails, and potentially a case where you must manually configure the networking within your operating system. We cannot assist everyone quickly when it comes to this so you need to essentially confirm that you will not require support related to the network configuration within your operating system.
Does this sound good? Does anyone have any suggestions or requests that you'd like us to implement to make the process more appealing?
@yoursunny@FrankZ tagging you specifically as we kind of discussed this a little bit in the past and I'm interested in hearing your feedback if you're around.
The plan for migration seems good to me. Personally, I can rebuild my stuff pretty quickly and have good backups, so even a no data option if it made it easier for you guys (though time to code and test and stuff I guess prob makes it more work) would work too.
One thing I haven't really seen updated in a while would be a list of IPs for each location so people can figure out where they do want to be? Or which providers they want to avoid shifty eyes
Virmach, you really like piling on troublesome functionality? In theory, it should be good but I predict more work orders.
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).
@Virmach is there a specific reason that you don't allow rDNS to be set in SolusVM? A bug in your particular version? It'd take one item off your plate if we could set it ourselves.
[Not that it'll help me 'cos I still don't get the 2FA email :'( Has your billing email server got on blacklists? ]
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).
@AlwaysSkint said: @Virmach is there a specific reason that you don't allow rDNS to be set in SolusVM? A bug in your particular version? It'd take one item off your plate if we could set it ourselves.
We have various providers and IP leases that all handle it differently. The largest provider won't really provide us with the basic functionality we desire and a lot of IP leasers are hesitant to provide full functionality. It was already difficult enough even locating a provider and getting IPv4 in time.
Some prefer going the route of manually involving humans at every step and with the problems we've already had where they've threatened to end service, it wouldn't exactly be the best idea to flood them with a thousand rDNS requests at once and if they set PTR records and it turns out the person was a spammer, it'll be a really bad look.
There are some blocks where allowing it to be set on SolusVM would be possible, but it would be very clustered and we'd have to organize it and build a system that either takes people to SolusVM to set it or to submit a manual request depending on the provider.
Adding onto this, we still haven't finalized all IPv4 and we could process all of them only to have to re-process it again if an IPv4 provider drops out at this early stage.
Finally, assuming we could theoretically set this up for ALL blocks on SolusVM which is a huge assumption to make, it wouldn't exactly help with abuse if everyone can freely set and change it without some kind of anti-abuse system in between to ensure we're not just making it easier on spammers. There's just a lot of thought and meticulous planning that has to be done and we haven't been in a position where I'd feel comfortable rushing it out right now.
[Not that it'll help me 'cos I still don't get the 2FA email :'( Has your billing email server got on blacklists? ]
Message me your e-mail address so I can make sure the email isn't being suppressed. If an email bounces, the way it works is it's permanently suppressed to avoid it from being mass blacklisted for sending unwanted emails.
@Daevien said: One thing I haven't really seen updated in a while would be a list of IPs for each location so people can figure out where they do want to be? Or which providers they want to avoid shifty eyes
I've been intentionally vague here. It'd be easy for us to share this list but it's not easy thinking through all the reasons why it'd be a bad idea and why we should not do it. If we publish a list where people can determine what they want to avoid, that creates a desire for something we may or may not be able to provide accommodation for when it comes to preferences. Myths will be started and then we'll have a thousand requests of people asking to be placed on specific servers.
I do want to at least build out our system where people, where available, do get a choice between two datacenters if we have any locations with multiple providers. And it would probably also be beneficial if we can place people on certain IPv4 addresses based on their use cases. For example, if one provider is hypersensitive regarding phishing reports, those could end up being somehow marked as limited port access servers for 80/443 and that way we can funnel those to providers that don't care as much as we can reduce any potential restrictions.
All of this would be a lot easier if we didn't have to accommodate the weird preferences of each provider but we don't live in a world where we can go based off our own principles right now. That would require a multi-million dollar IPv4 purchase and if we want to get super technical we'd also have to run our own facilities and transit because providers don't really go based off what I believe they should go by which is the law. This reminds me of the time we were contacted by a host who shall not be named, pestering us about a specific porn site being hosted that they didn't appreciate even though it was completely legal.
@Daevien said: The plan for migration seems good to me. Personally, I can rebuild my stuff pretty quickly and have good backups, so even a no data option if it made it easier for you guys (though time to code and test and stuff I guess prob makes it more work) would work too.
After essentially having to migrate every single virtual server over the last year or two we've gotten pretty good at processing these in bulk as long as they come in an organized fashion.
If you can rebuild your stuff and want to make it easier on us, the go-to should be the existing Ryzen migrate button. We can still work on fixing these for specific cases where it's not letting you do it so feel free to discuss that (just let me know your plan name, the node it's currently on, where you're trying to move it, and the error displayed.)
I think in my lifetime I clock in as having used the SolusVM migration tool well over 100,000 times so what's another 10,000?
@risturiz said:
So Ryzen migrate without data is working again?
I tried "Ryzen Migrate" button from San Jose to Miami, and it still fails.
@VirMach said:
It's working well enough that a bunch of people from HostLoc decided to edit elements and add in a Tokyo option which it validated on payment.
Tokyo will be nice.
@VirMach said: I think we're finally ready to start offering free migrations with data for a limited time. This is so people can end up where they really want without the hassle of having to load everything back in, especially for those people that ended up getting forcefully moved to an undesired location. We got the migration tool working again and figured out what's causing it to break so we can do these in daily batches.
No problem with the plan.
The only part I dislike is: "We'll move you to a server with an IP block that may be swapped out in the future."
@VirMach said: Quick update on XPG drives: I haven't had a chance to take them to the post office
Still waiting.
Maybe 2024 ?
We accept Karma donations for the last flan. 🍮 affbrr
Comments
@VirMach 23.95.68.151 is always offline a long time,can you help me to slove the problem?In additionally,the migration of Ticket #160581 is also handled together,thank a lot.
By the way,is there time compensation for being offline for too long?
I think they mentioned credits for being offline for too long
These are being planned out and done very soon. We just want to make sure we do it properly at this point, to where people go on a stable node, have functional networking, operating systems, and we communicate it properly and credit everyone accordingly.
I almost sent out an email a few days ago outlining everything but it wasn't clear enough so I didn't send it out yet. I'm trying to get everything down 100% because people have already waited so long, I want to make sure we do a perfect job and don't confuse people further or drag it out by providing incorrect dates, vague information, etc.
These just got fixed.
These got fixed.
Thanks for the nice surprise this morning @Virmach .
@VirMach
My Ticket also got closed without any proper response,
Ticket #262275
My Node: FFME001.VIRM.AC
I know you already mentioned the node is up in one of your replies here. But still my vps is down. Unable to connect. Earlier I didn't had solusvm panel control access for this node. So I thought it must have been panel's fault but now the panel is up and I am able to browse it. Still it's offline, I tried to reboot/reconfigure network but no success.
I thought it was just me but one of my friend who is on same node facing exact same issue.
This isn't closed. If it was closed it already got unclosed and re-flagged. I see the title's also changed so it's marked correctly for us to include it in the proper queue for that specific fix.
That would be these:
There are nodes in bursts of times where it may have had a specific problem that caused the VMs not to generate properly and that's what you're facing an issue on, for FFME001.
I've already cleared a few of these up today. We might get to FFME001 today as well.
Looks like SJC2008 is reachable from billing panel again, which is great, it had been unreachable before. Is this node still having network issues? Billing and control panels say my VPS is offline, attempting reboot doesn't change it, it's unreachable in rescue system, and VNC address refuses connections. It does say it's a Ryzen node, i.e. the VPS got migrated from the old Intel hardware. I guess that is nice.
I'm going to just make a wild guess based on all your previous terrible luck & experiences and say that you're probably one of the 10 people affected on this node by a missing disk. I have no idea what happened and won't know without looking back at all our logs later. They're all back to back, just 10 VMs that don't have a proper disk.
Right now they're on the queue to get created (the LVMs.)
Ah ok, I will check again in a few days I guess. Thanks.
Thanks @VirMach . They are back up.
I got an email [Emergency Migration] Your service on TYOC040.
which location has the least problem? I want to move it there.
looks like Amsterdam rarely has problems
benchmark score of the vps I've ever had
i got it too, and believe they are migrating to an empty node in Japan if maintenance doesn't work.
I bench YABS 24/7/365 unless it's a leap year.
Poor TYOC035.He was ignored.
Not ignored.
SJCZ008 all set. If you still have a problem it may be something else.
@VirMach Sorry to bug you: I still don't get 2FA email and for some reason my backup code doesn't work (got locked out for a day). :'( Was working no problem until approx. 5 days ago.
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).
Same thing as before, can't seem to reboot from panel. Should I assume the disk is trashed, and reinstall the OS? It's a slight nuisance if the old data is lost, but I can deal with it.
Aha, I was able to connect with VNC, which didn't work before. It said hard disk is not bootable and there was no CD/DVD mounted. I will try rescue mode and if that doesn't help, will reinstall. Glad to see this VM at least somewhat alive again.
Update: no luck with rescue mode so I reinstalled, and that seems to have worked. Nice to have this machine back. It would be nice to transfer its resources to the new one instead of having two. Probably too much hassle to think about right now though.
My servers at SJCZ008 are missing all information as below screenshot:
Thank you, looks like resolved!
blog archives
Looks like they were fixed already, all are working now. Thank you.
My VPS after Ryzen migration is running smoothly. Quite stable and fast. I am using it to host a WooCommerce site.
Powerful AMD Ryzen VPS (aff)
But TYOC40 is In Progress now.TYOC035 still Outage.
Thanks, after your response, my earlier FFME001 vm got replaced by FFME007 and now it doesn't have the disk.. and the ticket got renamed with LVM.
Hoping to get this also resolved soon 🥺
You should lookup the definition of "ignored".
"ISO" and "Re-install OS" on my BF-SPECIAL-2020 have been fixed, but "VPS Control Panel" button still shows "Invalid vserverid or username". However, I hesitate to reply to the ticket just for that reason.
https://i.imgur.com/viDVJKy.png
@VirMach I created a ticket a month ago and today you just closed it without any resolution, stating this excuse: "Your ticket has been marked as having a bad title, missing information, or improper use of a custom ticket department."
My ticket clearly stated that my VPS has no Internet connection. I've also tagged you here at least two times and mentioned that TYOC025 has this type of connectivity problem, but you've evaded answering my posts twice.
If sending support tickets on your platform doesn't result in a solution... if replying on a 3rd party website doesn't get a solution, then what else am I supposed to do? By closing tickets that we have been waiting months in queue for, in good faith, then you are making an already frustrating situation ten times worse.
I have opened a new ticket and followed all of your requirements. Please check my new ticket here and fix the connection issue. #634655 Thanks.
If you don't mind indulging my curiosity, what was the title and contents of the last ticket?
Should be "Refund" xD
Has there been any update to when a replacement server would be deployed? Its been beyond 6 weeks now. I already accepted the 2TB drive over 2x1TB and other US Datacenter besides West coast. Once again for your reference Ticket #342867
OS needs a re-install assuming the person handling it did it correctly. I'll try to check back on their work and make sure they created the LVMs properly but they should have done so.
Mines are in PHXZ002 and TYOC033. While in Tokyo there were some problem at the beginning its quite stable for the last 2-3 months. PHXZ002 had been with me from 2015, and had done 2 migrations (1st one on better server, 2nd one on Ryzen CPU ) in same loc and i did not had single issue since 2015.
ServerStatus , slackvpn , linux mirrors
Recommended Providers: Servarica(aff) | HostBRR(aff) | SolidVPS(aff) | RackNerd(aff) | KuroIT(aff) | AlphaVPS(aff) | HostDare(aff)
@emperor every time see you post - i recall the band emperor
maybe @Mumbly @lapua knowns them.
Ihsahn is great musician
ServerStatus , slackvpn , linux mirrors
Recommended Providers: Servarica(aff) | HostBRR(aff) | SolidVPS(aff) | RackNerd(aff) | KuroIT(aff) | AlphaVPS(aff) | HostDare(aff)
I thought that too
Yes, of course
Not exactly among my favourite bands from Norway, but still among the biggest still active BM bands around. I never saw them live, but I saw Ihsahn (singers solo career) live in 2013 if this count 
For me, it reminds me of something from my childhood days
"The imitator dooms himself to hopeless mediocrity." — Ralph Waldo Emerson
...and this part where Fenriz (Darkthrone) says "big sunglasses, not Emperor (small) sunglasses, very important, big sunglasees = cool band" always cracks me up
(complete interview https://www.youtube.com/watch?v=2u7RwDQZv0c)@FrankZ , well attempted getting Biloh to even tangentially address his own part in events. Sad to see him ignore you completely. :-/
I think we're finally ready to start offering free migrations with data for a limited time. This is so people can end up where they really want without the hassle of having to load everything back in, especially for those people that ended up getting forcefully moved to an undesired location. We got the migration tool working again and figured out what's causing it to break so we can do these in daily batches.
There's a few caveats:
Does this sound good? Does anyone have any suggestions or requests that you'd like us to implement to make the process more appealing?
@yoursunny @FrankZ tagging you specifically as we kind of discussed this a little bit in the past and I'm interested in hearing your feedback if you're around.
The plan for migration seems good to me. Personally, I can rebuild my stuff pretty quickly and have good backups, so even a no data option if it made it easier for you guys (though time to code and test and stuff I guess prob makes it more work) would work too.
One thing I haven't really seen updated in a while would be a list of IPs for each location so people can figure out where they do want to be? Or which providers they want to avoid shifty eyes
Virmach, you really like piling on troublesome functionality? In theory, it should be good but I predict more work orders.
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).
@Virmach is there a specific reason that you don't allow rDNS to be set in SolusVM? A bug in your particular version? It'd take one item off your plate if we could set it ourselves.
[Not that it'll help me 'cos I still don't get the 2FA email :'( Has your billing email server got on blacklists? ]
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).
We have various providers and IP leases that all handle it differently. The largest provider won't really provide us with the basic functionality we desire and a lot of IP leasers are hesitant to provide full functionality. It was already difficult enough even locating a provider and getting IPv4 in time.
Some prefer going the route of manually involving humans at every step and with the problems we've already had where they've threatened to end service, it wouldn't exactly be the best idea to flood them with a thousand rDNS requests at once and if they set PTR records and it turns out the person was a spammer, it'll be a really bad look.
There are some blocks where allowing it to be set on SolusVM would be possible, but it would be very clustered and we'd have to organize it and build a system that either takes people to SolusVM to set it or to submit a manual request depending on the provider.
Adding onto this, we still haven't finalized all IPv4 and we could process all of them only to have to re-process it again if an IPv4 provider drops out at this early stage.
Finally, assuming we could theoretically set this up for ALL blocks on SolusVM which is a huge assumption to make, it wouldn't exactly help with abuse if everyone can freely set and change it without some kind of anti-abuse system in between to ensure we're not just making it easier on spammers. There's just a lot of thought and meticulous planning that has to be done and we haven't been in a position where I'd feel comfortable rushing it out right now.
Message me your e-mail address so I can make sure the email isn't being suppressed. If an email bounces, the way it works is it's permanently suppressed to avoid it from being mass blacklisted for sending unwanted emails.
I've been intentionally vague here. It'd be easy for us to share this list but it's not easy thinking through all the reasons why it'd be a bad idea and why we should not do it. If we publish a list where people can determine what they want to avoid, that creates a desire for something we may or may not be able to provide accommodation for when it comes to preferences. Myths will be started and then we'll have a thousand requests of people asking to be placed on specific servers.
I do want to at least build out our system where people, where available, do get a choice between two datacenters if we have any locations with multiple providers. And it would probably also be beneficial if we can place people on certain IPv4 addresses based on their use cases. For example, if one provider is hypersensitive regarding phishing reports, those could end up being somehow marked as limited port access servers for 80/443 and that way we can funnel those to providers that don't care as much as we can reduce any potential restrictions.
All of this would be a lot easier if we didn't have to accommodate the weird preferences of each provider but we don't live in a world where we can go based off our own principles right now. That would require a multi-million dollar IPv4 purchase and if we want to get super technical we'd also have to run our own facilities and transit because providers don't really go based off what I believe they should go by which is the law. This reminds me of the time we were contacted by a host who shall not be named, pestering us about a specific porn site being hosted that they didn't appreciate even though it was completely legal.
After essentially having to migrate every single virtual server over the last year or two we've gotten pretty good at processing these in bulk as long as they come in an organized fashion.
If you can rebuild your stuff and want to make it easier on us, the go-to should be the existing Ryzen migrate button. We can still work on fixing these for specific cases where it's not letting you do it so feel free to discuss that (just let me know your plan name, the node it's currently on, where you're trying to move it, and the error displayed.)
I think in my lifetime I clock in as having used the SolusVM migration tool well over 100,000 times so what's another 10,000?
So Ryzen migrate without data is working again?
Sorry, but I'm worried about the buses.
It's working well enough that a bunch of people from HostLoc decided to edit elements and add in a Tokyo option which it validated on payment.
Just a asking: is Ryzen Migrate available on all VPS?
Welcome Back Virmach
I tried "Ryzen Migrate" button from San Jose to Miami, and it still fails.
Tokyo will be nice.
No problem with the plan.
The only part I dislike is: "We'll move you to a server with an IP block that may be swapped out in the future."
Still waiting.
Maybe 2024 ?
We accept Karma donations for the last flan. 🍮 affbrr