Terms of service are being updated. We put revision dates as usual on the page, but here is the changelog for anyone interested. The changes are meant to make everything more clear, not more restrictive. We've discussed this several times in the past in this community and OGF, so these are mainly changes to cases that had some ambiguity. This allows us to go with the actual figures here more, rather than have to use other portions of the terms that are more related to general misuse. A lot of it has also been updated to essentially represent the same thing but using different figures that are more widely used now.
For example, there are "additional" restrictions on network usage, but enforcement makes it the same. Whereas we may have used the "in order to avoid congestion and/or disrupting the performance of other customers" we can now use the specific figures given, which should be less confusing.
There are also changes with increased fees. These definitely are increases. Our fees were mainly unchanged since 2014 but it's reached a point where bandwidth overages as well as dispute/chargeback fees have essentially gone up since we've shifted toward more premium blend and PayPal's made modifications, and we're representing actual cost of dealing with certain situations such as backup recovery.
Finally some changes to more specifically address multi-accounts and refunds but there's also others. So anyway, changelog:
Administration Fees: $25 --> $40
Any other $25 Fees/Addons: $25 --> $40
Premium Support: $15 per 15 minutes --> $20 per 15 minutes
Additional CPU: $10 Fair Use core --> $15 Fair Use core.
BW Overages: $5/10/30/50 --> $10/20/100/200
Additional BW: $5/35 --> $10/50
Custom Billing Fee: $5 --> $10
Additional IP Address ---> Additional IPv4 Address
Blacklisting fee is changed to Blacklisting or valid abuse report.
Administration fee for returned payment merged with disputes/holds/chargebacks.
Added to fee schedule:
New portion for maintaining approved multiple accounts.
Added to refund section: No refunds are given for ANY services (account-wide) in cases where service is purchased on a secondary account, per household.
Added to invoices section: VirMach has no obligation to provide this grace period, and service may be terminated immediately after invoice is overdue.
AUP section:
High CPU: Customer’s Service cannot burst to 95-100% usage for more than five (5) minutes and cannot average higher than 50% usage within any two (2) hour period. Packages advertised to include dedicated CPU, Services with the high CPU option, and any customized Service plans that include high CPU option may burst to 100% at all times.
High CPU: Customer’s Service cannot burst to 95-100% usage for more than fifteen (15) minutes and cannot average higher than 50% usage within any two (2) hour period. Packages advertised with additional fair use restrictions cannot average higher than the advertised amount (usually 25% or 33%) within any (6) hour period. Packages originally sold at lower clock rate or processing power may be scaled accordingly. Packages advertised to include dedicated CPU may burst to 100% at all times. High I/O: Customer’s Service cannot average more than 80 IOPS within any two (2) hour period, cannot burst above 300MB/s disk write average for more than ten (10) minutes, cannot average more than 300 write operations per second for more than 1 hour, and cannot be above 20% average utilization within any six (6) hour period.
High I/O: Customer’s Service cannot average more than 80 IOPS per 10GB of allocated disk space within any two (2) hour period, cannot burst above 300MB/s disk write average for more than ten (10) minutes, cannot average more than 300 write operations per second for more than one (1) hour, and cannot be above 0.25% average utilization per 10GB of allocated disk space within any twelve (12) hour period. High Network Usage: Customer’s Service cannot have more than 50,000 conntrack sessions at any given time, and cannot use more than the allocated bandwidth. Customer understands that the network is shared and utilizing maximum network speed will not always be possible.
High Network Usage: Customer’s Service cannot have more than 50,000 conntrack sessions at any given time, and cannot use more than the allocated bandwidth. Customer's Service cannot burst to 80% or above total port speed for more than five (5) consecutive minutes or more than a total of twenty-four (24) hours per month. Customer's Service cannot use more than 50% of the monthly allocated bandwidth in under fourteen (14) days, or more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours. Customer understands that the network is shared and utilizing maximum network speed will not always be possible. High Load: Customer’s Service cannot have a 15-minute load average higher than the number of full logical cores assigned and cannot have a 1-day load average higher than 70% of the number of full logical cores assigned.
High Load: Customer’s Service cannot have a 15-minute load average higher than the number of full logical cores assigned and cannot have a 1-day load average higher than 70% of the number of full logical cores assigned. Customer's Service cannot contribute to more than 10% of total load at any time.
Let me know if you have any questions or concerns, or suggestions. Some additional notes:
Bandwidth rates have gone up but this will not affect any package sold at a lower rate per 1TB, and so on. As in, we can still sell it for lower but this is what you can definitely buy more at in any situation. This concept also applies to many other fee changes.
I/O abuse has been made more lax to better represent how we've actually been enforcing it, we'll still have additional leniencies at usual but it's no longer just written as 80 IOPS per plan. The total % utilization has been more tuned toward disk size and longer duration to allow for more bursting that usually does occur.
CPU has a lot more sections added to represent the special types of plans we've been selling and the Ryzen CPU change more officially discussed. The 5 minute timer for 100% burst has been changed to something more realistic, although this section is still far off from how we actually do things, I may rewrite it later.
Portion with blacklisting changed to valid abuse report, I know there may be some concerns that we're going to start charging $40 for every reported abuse but "valid" and "illegal" (edit: I took illegal out because it could cause some problems) report means determined to actually be abusive/intended and we're not going to start charging these randomly for everyone. It just allows us to go harsher on people specifically signing up to host phishing sites, botnets, or to send out bulk spam.
Portion with $5 monthly fee per account, this is more officially acknowledging the people purchasing the extra support package to do that. We do still technically need to approve it so if you'd like you can create a ticket for acknowledgement.
(edit) Oh and for some time we'll still go by everything how it used to be until we update all portions of our site, basically at our discretion, if it's lower or beneficial to you to go with the old published rates or policies we'll basically do that for several months if you're an old customer. Although I don't see it affecting many people in any case.
(edit2) And in cases where it positive affects people, we'll definitely go with the new policy. So no 5 minute powerdown for CPU, which honestly never happened anyway. But at least now it's a written guarantee.
@yoursunny this means you can officially rest easy with the 80 IOPS thing as well. I guess unless you have a 10GB package.
@VirMach, there are "ipv6 request" buttons, I requested, automatically merged into one request, after that, nothing happened, no ipv6, nothing...was this just a joke? Or you want to see whether button's working. Also, it says, if I cancelled, there will be a refund button, I did try one and no button was shown, what're these buttons for anyway?
Contrack thing is mostly outdated. Old monitoring for OpenVZ related mostly to denial of service attacks. So if you get attacked, it still would technically not be safe but limiting it would help out in other cases.
I don't know how well the system.slice works, I haven't done any testing but someone else may be able to answer you better there. Thing is, a lot of times you may be causing high I/O or high CPU if for example the system goes into kernel panic or crashes/reboots and gets stuck and obviously in those cases it doesn't matter what settings you have set.
I wouldn't be worried and wouldn't recommend setting anything until at least your first warning. It won't just randomly be immediately suspended, you'll first get a warning/powerdown in those cases for I/O and CPU.
@VirMach said: Customer's Service cannot use more than 50% of the monthly allocated bandwidth in under fourteen (14) days, or more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
If you are a new 'storage' customer this could be a problem when populating the VM ?
@VirMach said: Customer's Service cannot use more than 50% of the monthly allocated bandwidth in under fourteen (14) days, or more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
If you are a new 'storage' customer this could be a problem when populating the VM ?
Might be an issue with some of the tiny plans too. Have to look but I think I have an old instance with only 250GB bandwidth.
@VirMach said: @yoursunny this means you can officially rest easy with the 80 IOPS thing as well.
I won't sleep well until I know how to measure IOPS.
Professional providers simply restrict usage from hypervisor side, without hanging a suspension hammer on customer's head.
We accept Karma donations for the last flan. 🍮 affbrr
@Jab said: I was using it, for 2nd day... first time in like 6 months >.>
Yeah, my "268.61 MB of 1.5 TB Used" idler at FFME004 is down.
It died exactly one hour ago. Who's brave enough to open priority support ticket to notify them about outage?
Customer's Service cannot use more than 50% of the monthly allocated bandwidth in under fourteen (14) days, or more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
If you are a new 'storage' customer this could be a problem when populating the VM ?
Might be an issue with some of the tiny plans too. Have to look but I think I have an old instance with only 250GB bandwidth.
Does anyone know a way to configure tthe 10%/24 limit in nginx or with Linux traffic shaping?
10% of 1024GB would be 100GB - assume a 1GB file exists, that'd only take 100 requests.
Even reducing max transfer speed to 5MB/s, 100GB is still doable in ~6 hours.
I suppose a script that checks for close to the limit in daily transfers and changes nginx to block the site with a low-bandwidth error-page would be the way to go?
please, please help, I can't enter the member panel @VirMach because it's blocked by 2FA, can't reinstall or transaction, please follow up on ticket # 261273 (I don't have my old cell phone and no backup code either)
Customer's Service cannot use more than 50% of the monthly allocated bandwidth in under fourteen (14) days, or more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
If you are a new 'storage' customer this could be a problem when populating the VM ?
Might be an issue with some of the tiny plans too. Have to look but I think I have an old instance with only 250GB bandwidth.
Does anyone know a way to configure tthe 10%/24 limit in nginx or with Linux traffic shaping?
10% of 1024GB would be 100GB - assume a 1GB file exists, that'd only take 100 requests.
Even reducing max transfer speed to 5MB/s, 100GB is still doable in ~6 hours.
I suppose a script that checks for close to the limit in daily transfers and changes nginx to block the site with a low-bandwidth error-page would be the way to go?
you can set max speed with nginx.conf limit_rate 5120k;
or speedlimiting your whole linux easily with Wondershaper which is available in quite many distros nowdays wondershaper -a eth0 -d 5120 -u 5120
and to remove limits wondershaper -c -a eth0
I'm interested in purchasing an unmanaged dedicated server on your LA2 Digital Reality (https://lax2.lg.virmach.com/) location. However, I noticed that on the location selection page, there is no option to manually select LA2. The closest selection available is "US West San Jose & Los Angeles". Does that mean the server location will be randomly assigned between San Jose and Los Angeles? I need to ensure I get the LA2 Digital Reality location because I've conducted ping tests and found it has the best latency.
Additionally, on the disk selection page, there is an option for "First Available (120GB SSD or 1TB HDD)". I prefer to have an SSD and not an HDD. Can you please confirm how I can ensure that I receive an SSD upon checkout?
Lastly, I would like to checkout with my preferred location and storage type. Can you please provide guidance on how to do this?
@virtuous003 said:
I'm interested in purchasing an unmanaged dedicated server on your LA2 Digital Reality (https://lax2.lg.virmach.com/) location. However, I noticed that on the location selection page, there is no option to manually select LA2. The closest selection available is "US West San Jose & Los Angeles". Does that mean the server location will be randomly assigned between San Jose and Los Angeles? I need to ensure I get the LA2 Digital Reality location because I've conducted ping tests and found it has the best latency.
Additionally, on the disk selection page, there is an option for "First Available (120GB SSD or 1TB HDD)". I prefer to have an SSD and not an HDD. Can you please confirm how I can ensure that I receive an SSD upon checkout?
Lastly, I would like to checkout with my preferred location and storage type. Can you please provide guidance on how to do this?
Not necessarily randomly assigned, depends on configuration, but mostly, not 100%
We did it this way to avoid having to make so many different configurations and to keep it simple. If you want guaranteed SSD, you have to purchase the more expensive version that's guaranteed to be that type. No guarantees one way or the other otherwise. The $35 unmanaged is essentially a "grab bag" special.
Higher likelihood of it being SSD than HDD. Higher likelihood of it being San Jose than LAX3.
This will not go on LAX2 in any case. It's LAX3 (INAP, El Segundo) for LAX dedicated. If you want LAX2, you'll have to order Ryzen custom dedi and wait time on that is unpredictable right now.
@Jab said:
Oh, good idea, let's try that same day response new click a lot of buttons feature!
I guess I select all 3?
bruh.
It's because it's technically online. The answers are still not very well tuned but it would make mostly sense if the main node is online. But it's overloading so it's effectively not really online.
@cold said:
anyone else having problems with FFME004 ?
Down foe me. But status page says all is good.
I've been working probably 30 hours straight on NYCB034X, still haven't gotten to FFME004 although I'm trying to work it in now with probably a reboot. Since it's overloading I've just been getting kicked off a lot and I want to confirm a couple things before blindly rebooting it.
It's just that we know NYCB034X is a ticking time bomb at this point and I don't want it to turn into an NYCB041 scenario.
you can set max speed with nginx.conf limit_rate 5120k;
Yup. Mentioned this.
This doesn't help because even at this lower data rate, the daily quota can be exceeded in 6 hours.
So unless I rate limit to much lower than this, and then I can't burst.
Nginx doesn't have a 'limit_rate 100GB/day' as far as I can find.
or speedlimiting your whole linux easily with Wondershaper which is available in quite many distros nowdays
Which has exactly the same problem -- it's a fixed limit, not a dynamic limit based on how much has been transferred already ..
I'm hoping someone has a clever script that does something like proportionally adjusting the traffic shapper based on the traffic in the last 15 minutes or so
@atomi said:
or speedlimiting your whole linux easily with Wondershaper which is available in quite many distros nowdays
Which has exactly the same problem -- it's a fixed limit, not a dynamic limit based on how much has been transferred already ..
I'm hoping someone has a clever script that does something like proportionally adjusting the traffic shapper based on the traffic in the last 15 minutes or so
you could do it with vnstat + wondershaper combo for example. I'm pretty sure that there are some scripts already made for that but I would count longer period than 15 mins
Anyone else with a CHIZ001? Mine's been flapping for most of today (6 times so far). :'(
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).
Comments
where's that guy who keeps calling virmach
yo chad?
I bench YABS 24/7/365 unless it's a leap year.
Hey virmach, any ETA on when the change location button will start to work?
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
You mean @Flying_Chinaman
MOOOORRRRE
Yo gonna be hectic recently since found another shitty job.
See ya chaps next year, may us meet in the land of free.
Ontario Dildo Inspector
good luck with income!
I bench YABS 24/7/365 unless it's a leap year.
Terms of service are being updated. We put revision dates as usual on the page, but here is the changelog for anyone interested. The changes are meant to make everything more clear, not more restrictive. We've discussed this several times in the past in this community and OGF, so these are mainly changes to cases that had some ambiguity. This allows us to go with the actual figures here more, rather than have to use other portions of the terms that are more related to general misuse. A lot of it has also been updated to essentially represent the same thing but using different figures that are more widely used now.
For example, there are "additional" restrictions on network usage, but enforcement makes it the same. Whereas we may have used the "in order to avoid congestion and/or disrupting the performance of other customers" we can now use the specific figures given, which should be less confusing.
There are also changes with increased fees. These definitely are increases. Our fees were mainly unchanged since 2014 but it's reached a point where bandwidth overages as well as dispute/chargeback fees have essentially gone up since we've shifted toward more premium blend and PayPal's made modifications, and we're representing actual cost of dealing with certain situations such as backup recovery.
Finally some changes to more specifically address multi-accounts and refunds but there's also others. So anyway, changelog:
Administration Fees: $25 --> $40
Any other $25 Fees/Addons: $25 --> $40
Premium Support: $15 per 15 minutes --> $20 per 15 minutes
Custom setup on Dedis: $20/30 --> $40/60
Datacenter Hands: $80/Half Hour --> $180/Half Hour or $160/Hour pre-scheduled. Minimum 2 hours.
Backup Retrieval: $15 --> $40
Additional CPU: $10 Fair Use core --> $15 Fair Use core.
BW Overages: $5/10/30/50 --> $10/20/100/200
Additional BW: $5/35 --> $10/50
Custom Billing Fee: $5 --> $10
Additional IP Address ---> Additional IPv4 Address
Blacklisting fee is changed to Blacklisting or valid abuse report.
Administration fee for returned payment merged with disputes/holds/chargebacks.
Added to fee schedule:
New portion for maintaining approved multiple accounts.
Added to refund section: No refunds are given for ANY services (account-wide) in cases where service is purchased on a secondary account, per household.
Added to invoices section: VirMach has no obligation to provide this grace period, and service may be terminated immediately after invoice is overdue.
AUP section:
High CPU: Customer’s Service cannot burst to 95-100% usage for more than five (5) minutes and cannot average higher than 50% usage within any two (2) hour period. Packages advertised to include dedicated CPU, Services with the high CPU option, and any customized Service plans that include high CPU option may burst to 100% at all times.
High CPU: Customer’s Service cannot burst to 95-100% usage for more than fifteen (15) minutes and cannot average higher than 50% usage within any two (2) hour period. Packages advertised with additional fair use restrictions cannot average higher than the advertised amount (usually 25% or 33%) within any (6) hour period. Packages originally sold at lower clock rate or processing power may be scaled accordingly. Packages advertised to include dedicated CPU may burst to 100% at all times.
High I/O: Customer’s Service cannot average more than 80 IOPS within any two (2) hour period, cannot burst above 300MB/s disk write average for more than ten (10) minutes, cannot average more than 300 write operations per second for more than 1 hour, and cannot be above 20% average utilization within any six (6) hour period.
High I/O: Customer’s Service cannot average more than 80 IOPS per 10GB of allocated disk space within any two (2) hour period, cannot burst above 300MB/s disk write average for more than ten (10) minutes, cannot average more than 300 write operations per second for more than one (1) hour, and cannot be above 0.25% average utilization per 10GB of allocated disk space within any twelve (12) hour period.
High Network Usage: Customer’s Service cannot have more than 50,000 conntrack sessions at any given time, and cannot use more than the allocated bandwidth. Customer understands that the network is shared and utilizing maximum network speed will not always be possible.
High Network Usage: Customer’s Service cannot have more than 50,000 conntrack sessions at any given time, and cannot use more than the allocated bandwidth. Customer's Service cannot burst to 80% or above total port speed for more than five (5) consecutive minutes or more than a total of twenty-four (24) hours per month. Customer's Service cannot use more than 50% of the monthly allocated bandwidth in under fourteen (14) days, or more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours. Customer understands that the network is shared and utilizing maximum network speed will not always be possible.
High Load: Customer’s Service cannot have a 15-minute load average higher than the number of full logical cores assigned and cannot have a 1-day load average higher than 70% of the number of full logical cores assigned.
High Load: Customer’s Service cannot have a 15-minute load average higher than the number of full logical cores assigned and cannot have a 1-day load average higher than 70% of the number of full logical cores assigned. Customer's Service cannot contribute to more than 10% of total load at any time.
Let me know if you have any questions or concerns, or suggestions. Some additional notes:
(edit) Oh and for some time we'll still go by everything how it used to be until we update all portions of our site, basically at our discretion, if it's lower or beneficial to you to go with the old published rates or policies we'll basically do that for several months if you're an old customer. Although I don't see it affecting many people in any case.
(edit2) And in cases where it positive affects people, we'll definitely go with the new policy. So no 5 minute powerdown for CPU, which honestly never happened anyway. But at least now it's a written guarantee.
@yoursunny this means you can officially rest easy with the 80 IOPS thing as well. I guess unless you have a 10GB package.
@VirMach, there are "ipv6 request" buttons, I requested, automatically merged into one request, after that, nothing happened, no ipv6, nothing...was this just a joke? Or you want to see whether button's working. Also, it says, if I cancelled, there will be a refund button, I did try one and no button was shown, what're these buttons for anyway?
New IOPS & High CPU on AUP is great, more precise
now i know how to time my YABS better.
I bench YABS 24/7/365 unless it's a leap year.
Refund button does not show on specials as those have always stated "No Refunds" in the terms. It shows on regular packages.
~~~~
Update: I misunderstood, there is no problem.
Yes VirMach go check all transfer within last week to see if anyone of them is broken.
No server ID, no ticket ID, nothing allowing to identify you.
Good luck Mr VirMach.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Will my VPS be safe after doing this setting?
VirMach: Customer’s Service cannot use more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
https://virmach.com/terms-conditions/#aup
Contrack thing is mostly outdated. Old monitoring for OpenVZ related mostly to denial of service attacks. So if you get attacked, it still would technically not be safe but limiting it would help out in other cases.
I don't know how well the system.slice works, I haven't done any testing but someone else may be able to answer you better there. Thing is, a lot of times you may be causing high I/O or high CPU if for example the system goes into kernel panic or crashes/reboots and gets stuck and obviously in those cases it doesn't matter what settings you have set.
I wouldn't be worried and wouldn't recommend setting anything until at least your first warning. It won't just randomly be immediately suspended, you'll first get a warning/powerdown in those cases for I/O and CPU.
If you are a new 'storage' customer this could be a problem when populating the VM ?
Get your FREE VPS if you develop Open Source software
Might be an issue with some of the tiny plans too. Have to look but I think I have an old instance with only 250GB bandwidth.
I won't sleep well until I know how to measure IOPS.
Professional providers simply restrict usage from hypervisor side, without hanging a suspension hammer on customer's head.
We accept Karma donations for the last flan. 🍮 affbrr
I was using it, for 2nd day... first time in like 6 months >.>
Fuck you Murphy('s law)
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Yeah, my "268.61 MB of 1.5 TB Used" idler at FFME004 is down.
It died exactly one hour ago. Who's brave enough to open priority support ticket to notify them about outage?
Oh, good idea, let's try that same day response new click a lot of buttons feature!
I guess I select all 3?
bruh.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
i would like to see a button for
Oh boi @VirMach you need to increase z-index on the submit button... you troll. This needs
z-index: 2at least.CHECK THIS ONE SIMPLE TRICK THAT VIRMACH USES TO DIG OUT OF THE TICKETS PILE.
https://streamable.com/b6kzgw
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Does anyone know a way to configure tthe 10%/24 limit in nginx or with Linux traffic shaping?
10% of 1024GB would be 100GB - assume a 1GB file exists, that'd only take 100 requests.
Even reducing max transfer speed to 5MB/s, 100GB is still doable in ~6 hours.
I suppose a script that checks for close to the limit in daily transfers and changes nginx to block the site with a low-bandwidth error-page would be the way to go?
anyone else having problems with FFME004 ?
Down foe me. But status page says all is good.
Yep, down for me too
FFME004 is down.
please, please help, I can't enter the member panel @VirMach because it's blocked by 2FA, can't reinstall or transaction, please follow up on ticket # 261273 (I don't have my old cell phone and no backup code either)
Ontario Dildo Inspector
yooo chadddd
I bench YABS 24/7/365 unless it's a leap year.
Yo chaaaaad, any suggestion for IELTS writing?
Ontario Dildo Inspector
Yo chaaad, migrating?
I bench YABS 24/7/365 unless it's a leap year.
Yep, one more year if things go well.
Maybe one day I would request Chad Franz to change my name to Flying_Canadian
Ontario Dildo Inspector
all the best! hopefully things will ease up after the next presidential election.
I bench YABS 24/7/365 unless it's a leap year.
thats the trick ! if status page says its good, they wont investigate
)
you can set max speed with nginx.conf
limit_rate 5120k;or speedlimiting your whole linux easily with Wondershaper which is available in quite many distros nowdays
wondershaper -a eth0 -d 5120 -u 5120and to remove limits
wondershaper -c -a eth0I'm interested in purchasing an unmanaged dedicated server on your LA2 Digital Reality (https://lax2.lg.virmach.com/) location. However, I noticed that on the location selection page, there is no option to manually select LA2. The closest selection available is "US West San Jose & Los Angeles". Does that mean the server location will be randomly assigned between San Jose and Los Angeles? I need to ensure I get the LA2 Digital Reality location because I've conducted ping tests and found it has the best latency.
Additionally, on the disk selection page, there is an option for "First Available (120GB SSD or 1TB HDD)". I prefer to have an SSD and not an HDD. Can you please confirm how I can ensure that I receive an SSD upon checkout?
Lastly, I would like to checkout with my preferred location and storage type. Can you please provide guidance on how to do this?
Not necessarily randomly assigned, depends on configuration, but mostly, not 100%
We did it this way to avoid having to make so many different configurations and to keep it simple. If you want guaranteed SSD, you have to purchase the more expensive version that's guaranteed to be that type. No guarantees one way or the other otherwise. The $35 unmanaged is essentially a "grab bag" special.
Higher likelihood of it being SSD than HDD. Higher likelihood of it being San Jose than LAX3.
This will not go on LAX2 in any case. It's LAX3 (INAP, El Segundo) for LAX dedicated. If you want LAX2, you'll have to order Ryzen custom dedi and wait time on that is unpredictable right now.
It's because it's technically online. The answers are still not very well tuned but it would make mostly sense if the main node is online. But it's overloading so it's effectively not really online.
I've been working probably 30 hours straight on NYCB034X, still haven't gotten to FFME004 although I'm trying to work it in now with probably a reboot. Since it's overloading I've just been getting kicked off a lot and I want to confirm a couple things before blindly rebooting it.
It's just that we know NYCB034X is a ticking time bomb at this point and I don't want it to turn into an NYCB041 scenario.
FFME04 back!
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Yup. Mentioned this.
This doesn't help because even at this lower data rate, the daily quota can be exceeded in 6 hours.
So unless I rate limit to much lower than this, and then I can't burst.
Nginx doesn't have a 'limit_rate 100GB/day' as far as I can find.
Which has exactly the same problem -- it's a fixed limit, not a dynamic limit based on how much has been transferred already ..
I'm hoping someone has a clever script that does something like proportionally adjusting the traffic shapper based on the traffic in the last 15 minutes or so
I guess @VirMach developer can create working code, when they have enough incentive. 🫣
you could do it with vnstat + wondershaper combo for example. I'm pretty sure that there are some scripts already made for that but I would count longer period than 15 mins
@VirMach Its seem OS debian 11 templates in solusvm disappear.
Can you enable it back?
why idiot system keep mergeing every unrelated ticket into one
@VirMach any changes on those EPYC?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
This node doesn't look good
I'm getting the dreaded "No bootable device" error on my $2.22/yr special on TYOC007.
Good thing I was just idling it.
Anybody else on TYOC007 having issues ?
According to Hetrixtools, down at 2023-03-13 1:22 (UTC)
Anyone else with a CHIZ001? Mine's been flapping for most of today (6 times so far). :'(
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).