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).
I previously mentioned one of our IPv4 providers being upset regarding abuse reports. It seems like the situation is continuing to escalate even though we're doing everything we can to prevent it. We have increased minimum plan prices as you may have noticed on our site, to reduce abusive signups. We've had someone go through orders manually. Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups. We've replied to every abuse report, even the many duplicates that people like sending.
The provider is re-selling Cogent IPv4 which we were not initially aware of and implemented an abuse fee, I assume after Cogent did and with Cogent forwarding reports to this provider who forwards it to us, it slows down the process and adds in additional frustrating work for everyone I'm sure. We've paid for the fees even though initially we were told there'd be no other fees, which is fine.
Over the last 31 days, we've received a total of 40x IPv4 addresses reported, with the majority being poorly secured servers sending out attacks, with 59 additional duplicate emails. So this is 40 reported out of 32,768 IP block. I don't know if they truly believe 40 reports in a month on a /17 IPv4 block is excessive compared to other leases.
They've continued to threaten termination, usually after an abuse report they particularly do not like (something more serious, a few of these have occurred.)
I'm going to try to speed up IPv6 deployments and I'm hoping they are reasonable. I'm just providing this for the sake of transparency. It's obviously going to be very very bad if they decide to terminate that many IPv4 addresses and it would be difficult to replace them on short notice. I personally do not feel like this would be fair and we would of course have another company we would have to take to court over but I just wanted to paint a full picture/update for you guys here.
@VirMach said: Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups.
That is interesting. Some years ago providers were leery of crypto payments but a few took a chance on them and were pleasantly surprised to find very little abuse. I guess that didn't last. Thanks for keeping us informed.
@VirMach said: Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups.
That is interesting. Some years ago providers were leery of crypto payments but a few took a chance on them and were pleasantly surprised to find very little abuse. I guess that didn't last. Thanks for keeping us informed.
They stopped doing business in the US and pretty much force closed our account in any case, but with that news, it means they're in some way possibly legally in trouble (this is just speculation) with the US compliance. And of course it's not that cryptocurrency is inherently bad or abusive, we've just noticed with Coinbase at least some criminals stopped using it as I assume that's in some way better logged and investigated for crimes (once again just speculation.)
I believe it's possible that we became one of the providers people preferred, and Coinpayments was ones of the payment methods they preferred, and it kind of combined together to create a negative situation.
@mayiprint said: @VirMach VPS has not been available since June. There is no information to know the progress of the processing.
Node: LA10GKVM14
The plan for the old nodes that failed is to at the very least refund everyone for the unused time since it went offline. We were discussing internally how we wanted to proceed in the coming days and once it's finalized, an announcement will be made, most likely via e-mail.
These were the nodes:
LAKVM9, LAKVM26, LA10GKVM14.
As far as I remember, they were all part of a mass power failure event that caused PSU to die and data was lost from RAID controller and other failures and/or human error by datacenter techs. Since these occurred at the worst possible time while we were doing everything else at peak workloads, and were already falling behind, it wasn't possible to work them into the schedule and I do apologize for it having taken such a long time (and the lack of official updates) but we have been working on it more recently. We haven't forgot about them.
TYOC035 - online but having disk issues, attempting to recover disk
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 Purely being nosy, approx. how many Tickets are open, since the latest merging & closing?
(Might put things in perspective for some.)
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 Purely being nosy, approx. how many Tickets are open, since the latest merging & closing?
(Might put things in perspective for some.)
This is an estimate as I don't have an exact figure for this anymore, but 2600-5000 tickets were "merged" into 1300-1500 tickets (as in some people made 2 tickets, some people made way more.)
We made approximately 5000 replies over the last 30 days, and approximately 5000 tickets were created over the last 30 days.
2,500 tickets were left over as of yesterday, and about 150 tickets created over the last 12 hours.
100 priority tickets were left over as of yesterday.
The majority of tickets are created between 6PM-8AM PST (Pacific Standard Time), which is between 1AM-3PM GMT (Greenwich Mean Time), or 9AM-11PM CST (China Standard Time.)
The following numbers match these keywords for remaining tickets:
550 "Migration" (Mostly Tokyo paid migration requests.)
300 "Offline" or "Outage" (Mostly reporting outages already discussed.)
160 "Refund" (Mostly refund requests for migration request.)
350 "Connection" (Mostly older already-resolved IP or network issues.)
We're going to try to clear out migration related tickets today, and refund requests. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
@VirMach said:
We're going to try to clear out migration related tickets today, and refund requests. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
Exclude Tokio = 5k more tickets with people crying? 😬
Bloody Hell! That's some amount of work orders Tickets.
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).
No kidding.Although my 8.88 Phoenix was deleted.Maybe they've forgotten and I'm still waiting for their reply.
The migration failed I just want a refund.
@VirMach said:
** We're going to try to clear out migration related tickets today, and refund requests**. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
@VirMach said: We're going to try to clear out migration related tickets today, and refund requests. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
@Daevien said:
My lost old Chicago location vps has materialized in Miami, I guess it wanted to visit the beach.
did your data survive? still hoping hope isn't lost for my data...
It did actually, though I'm not exactly sure how old of a backup it went back to now that you mention it. I don't do a ton directly on that one (it's one of the 1 core, 512mb ram, 5gb, 2tb bandwidth ones we had asked for one black friday so it's just used as a proxy for the most part) so I basically just checked it over quickly and did an update for the os.
I also had what little was on their for config backed up as well as daily restic backups of all servers, so I could rebuild it quickly and wasn't worried about that.
All* templates have been re-syncing all day and should be done by tomorrow. Templates also have been changed to the correct group on SolusVM (previously completed) and most if not all services on WHMCS should also now have the correct templates selected for the re-install tool. Please feel free to report if your service still has any incorrect or non-functional templates after tomorrow. We'd need the following information for your report to be completed: [1] service package name such as "SSD1G", [2] service node name such as "LAXA024", [3] whether it's on SolusVM and/or WHMCS, [4] the full template name exactly as it appears.
Hello, I initiated a migration ticket for LA to Tokyo on July 25th, and successfully paid $3, but it keeps showing waiting, so can you process the refund for invoice#1462469？ Thank you.@VirMach
"Connection Issue - Network Down" tickets have been mostly handled. The majority (200+) of these were people who immediately reported it as a VPS-related network issue when their VPS was going through migration, followed by people attempting to use their old IP address, and then people who did not click the reconfigure button and did not read instructions for the department.
There were about 10~ that were in a glitched state where the callback didn't put the correct IP on WHMCS, and then maybe 5 or so where the IP address actually needed to be changed (it was stuck on the old.) Finally, 10-20 needed manual configuration at the OS level and are still being worked on where the password is provided. These do not include "Packet Loss" tickets, most of which will most likely just be closed as they appear to all be either related to previous packet loss issues that have already been resolved or for not including MTR but we'll take a look at any with troubleshooting data.
Comments
YABS?
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
quadranet LAX
I bench YABS 24/7/365 unless it's a leap year.
Posting a ticket instead of BM. The latter to follow upon resolution. Consider this a "BM in the (Low End) Spirit"
Cheers
Ticket #189699
blog archives
NYC Metro (AKA New Jersey): Dedipath@INAP NJ1
Risky!
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).
Business
Have you tried turning it off and on again?Risks will be have been taken.
(h/t to OGF a recent memefest)
blog archives
All the service in TYOC035 is still offline now?
I previously mentioned one of our IPv4 providers being upset regarding abuse reports. It seems like the situation is continuing to escalate even though we're doing everything we can to prevent it. We have increased minimum plan prices as you may have noticed on our site, to reduce abusive signups. We've had someone go through orders manually. Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups. We've replied to every abuse report, even the many duplicates that people like sending.
The provider is re-selling Cogent IPv4 which we were not initially aware of and implemented an abuse fee, I assume after Cogent did and with Cogent forwarding reports to this provider who forwards it to us, it slows down the process and adds in additional frustrating work for everyone I'm sure. We've paid for the fees even though initially we were told there'd be no other fees, which is fine.
Over the last 31 days, we've received a total of 40x IPv4 addresses reported, with the majority being poorly secured servers sending out attacks, with 59 additional duplicate emails. So this is 40 reported out of 32,768 IP block. I don't know if they truly believe 40 reports in a month on a /17 IPv4 block is excessive compared to other leases.
They've continued to threaten termination, usually after an abuse report they particularly do not like (something more serious, a few of these have occurred.)
I'm going to try to speed up IPv6 deployments and I'm hoping they are reasonable. I'm just providing this for the sake of transparency. It's obviously going to be very very bad if they decide to terminate that many IPv4 addresses and it would be difficult to replace them on short notice. I personally do not feel like this would be fair and we would of course have another company we would have to take to court over but I just wanted to paint a full picture/update for you guys here.
Please do not harass this company.
@VirMach ; i have a billing ticket #975541 , i will appreciate if it can be looked after soon. Thank you.
When will the migration plan of SJCZ004 be implemented. Can you help me with this order if it takes a long time. Thanks!
Ticket #461588
@VirMach
That is interesting. Some years ago providers were leery of crypto payments but a few took a chance on them and were pleasantly surprised to find very little abuse. I guess that didn't last. Thanks for keeping us informed.
They stopped doing business in the US and pretty much force closed our account in any case, but with that news, it means they're in some way possibly legally in trouble (this is just speculation) with the US compliance. And of course it's not that cryptocurrency is inherently bad or abusive, we've just noticed with Coinbase at least some criminals stopped using it as I assume that's in some way better logged and investigated for crimes (once again just speculation.)
I believe it's possible that we became one of the providers people preferred, and Coinpayments was ones of the payment methods they preferred, and it kind of combined together to create a negative situation.
@VirMach VPS has not been available since June. There is no information to know the progress of the processing.
Node: LA10GKVM14
The plan for the old nodes that failed is to at the very least refund everyone for the unused time since it went offline. We were discussing internally how we wanted to proceed in the coming days and once it's finalized, an announcement will be made, most likely via e-mail.
These were the nodes:
LAKVM9, LAKVM26, LA10GKVM14.
As far as I remember, they were all part of a mass power failure event that caused PSU to die and data was lost from RAID controller and other failures and/or human error by datacenter techs. Since these occurred at the worst possible time while we were doing everything else at peak workloads, and were already falling behind, it wasn't possible to work them into the schedule and I do apologize for it having taken such a long time (and the lack of official updates) but we have been working on it more recently. We haven't forgot about them.
@VirMach How about the TYOC035?
https://billing.virmach.com/serverstatus.php
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 Purely being nosy, approx. how many Tickets are open, since the latest merging & closing?
(Might put things in perspective for some.)
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).
This is an estimate as I don't have an exact figure for this anymore, but 2600-5000 tickets were "merged" into 1300-1500 tickets (as in some people made 2 tickets, some people made way more.)
We made approximately 5000 replies over the last 30 days, and approximately 5000 tickets were created over the last 30 days.
2,500 tickets were left over as of yesterday, and about 150 tickets created over the last 12 hours.
100 priority tickets were left over as of yesterday.
The majority of tickets are created between 6PM-8AM PST (Pacific Standard Time), which is between 1AM-3PM GMT (Greenwich Mean Time), or 9AM-11PM CST (China Standard Time.)
The following numbers match these keywords for remaining tickets:
We're going to try to clear out migration related tickets today, and refund requests. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
What provider (or at least what location(s)) so we will know that IP change is still on the cards there ;')
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
@VirMach what is the typical billing "refund in title" ticket response time?
Exclude Tokio = 5k more tickets with people crying? 😬
Bloody Hell! That's some amount of work orders Tickets.
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).
I have an order migration failure and no refund yet.
Do I need to create a ticket with “Refund”or ”Request Refund“ in the title?
Correct spelling is
“Refound”
No wonder you haven’t received it yet
blog archives
“Refound”
No kidding.Although my 8.88 Phoenix was deleted.Maybe they've forgotten and I'm still waiting for their reply.
The migration failed I just want a refund.
@Virmach any progress on being able to install an OS on Dedicated Servers?
@Virmach Any news at all on TYOC025? I haven't seen it mentioned anywhere, but the networking on it has been down since late July.
I really don't know what to say，node: RYZE.LAX-A031.VMS
But some neighbors is online now...
Perfect person to quote and make a grammatical error!
blog archives
Online is the most important thing at this monent.
Focus!Please!
Ticket #434240 Can I get a refund for my Phoenix not connecting to SSH for months?
that good to hear.
Negative.
Grammar trumps uptime.
In fact there would be no uptime without grammar. The tragedy!!
(Not to be confused with @uptime)
blog archives
refund received， Thanks.
refund received， Thanks.
I bench YABS 24/7/365 unless it's a leap year.
In Fact.
You are the tragedy.
(a)Greek,
(b)Elizabethan,
or
(c)Shakespearean tragedy?
Being specific helps.
blog archives
Faustian
My lost old Chicago location vps has materialized in Miami, I guess it wanted to visit the beach.
did your data survive? still hoping hope isn't lost for my data...
It did actually, though I'm not exactly sure how old of a backup it went back to now that you mention it. I don't do a ton directly on that one (it's one of the 1 core, 512mb ram, 5gb, 2tb bandwidth ones we had asked for one black friday so it's just used as a proxy for the most part) so I basically just checked it over quickly and did an update for the os.
I also had what little was on their for config backed up as well as daily restic backups of all servers, so I could rebuild it quickly and wasn't worried about that.
Just received my $1.68 credit from Virmach for a merged ticket (2 tickets) from July 6th 2022. Ticket was closed though.
https://microlxc.net/
@VirMach
Hello,
Can you check Ticket #454958 ?
I have paid a Invoice through WeChat, but it still shows "unpaid"
All* templates have been re-syncing all day and should be done by tomorrow. Templates also have been changed to the correct group on SolusVM (previously completed) and most if not all services on WHMCS should also now have the correct templates selected for the re-install tool. Please feel free to report if your service still has any incorrect or non-functional templates after tomorrow. We'd need the following information for your report to be completed: [1] service package name such as "SSD1G", [2] service node name such as "LAXA024", [3] whether it's on SolusVM and/or WHMCS, [4] the full template name exactly as it appears.
*Excludes servers currently offline.
Full list of templates:
AlmaLinux 8
CentOS 7
CentOS Stream 8
Debian 10
Debian 11
Ubuntu 18.04
Ubuntu 20.04
Windows 2022 Eval**
Full List of ISO:
AlmaLinux 8.4
AlmaLinux 8.5
CentOS 6.8
CentOS 7
CentOS 8
FreeBSD 12
OpenBSD 6.4
Rocky 8.5
TinyCore
Windows 2019
Alpine 3.10.3
Cd140201 (Boot Repair Disk?)
Clonezilla Live 2.6.0
CoreOS
Debian 10
Debian 11.2
Debian 8.2
Debian 9.1
Gparted Live 1.0.0
Netboot.xyz
Rancheros
Systemrescuecd
Ubuntu 20.04
Ubuntu 21.04
**May be partially or fully broken at this time and we are trying to re-template this to fix the problems.
Hello, I initiated a migration ticket for LA to Tokyo on July 25th, and successfully paid $3, but it keeps showing waiting, so can you process the refund for invoice#1462469？ Thank you.@VirMach
Ubuntu 21.04 is EOL.
Ubuntu 22.04 (latest LTS) is missing.
Netboot.xyz is not a solution as it needs 2GB RAM to start Ubuntu 22.04 installer.
We accept Karma donations for the last flan. 🍮 affbrr
"Connection Issue - Network Down" tickets have been mostly handled. The majority (200+) of these were people who immediately reported it as a VPS-related network issue when their VPS was going through migration, followed by people attempting to use their old IP address, and then people who did not click the reconfigure button and did not read instructions for the department.
There were about 10~ that were in a glitched state where the callback didn't put the correct IP on WHMCS, and then maybe 5 or so where the IP address actually needed to be changed (it was stuck on the old.) Finally, 10-20 needed manual configuration at the OS level and are still being worked on where the password is provided. These do not include "Packet Loss" tickets, most of which will most likely just be closed as they appear to all be either related to previous packet loss issues that have already been resolved or for not including MTR but we'll take a look at any with troubleshooting data.
Added to list. I'll probably work on this when we fix the Windows and proxy templates.
I don't usually do Ubuntu on servers, but is there a low memory option for it like there is for debian installer? Might be fix for now