VirMach
VirMach
About
- Username
- VirMach
- Joined
- Visits
- 137
- Last Active
- Roles
- Member, Hosting Provider
- Thanked
- 4232
Comments
-
(Quote) I definitely need more details like your plan name and what functions you performed such as Ryzen migrate.
-
(Quote) We're going to reach out to some top users especially around Saturday night and figure out how it's being used and how it could potentially be optimized. That probably means anyone who noticed it today might be one of the top users as that's…
-
(Quote) Yeah they were ready for some time on some of them and not for others, and the older ones we had to go back and reorganize them because they didn't have all the information and by then we had more of them to fill. It's expected for some. It…
-
(Quote) You said Dedipath LA. We don't use Dedipath in LA. I was only replying to that part. (edit) Sorry I thought you were talking about the QN LA network issue today we posted. Any network problem for the servers is going to be a longer wait rig…
-
Windows templates almost finished syncing, syncing rest now and then looking into nodes that still have template issues. They should mostly already be good Linux-wise.
-
(Image) If anyone got it let me know.
-
For science, can a few people try resetting their passwords on WHMCS? I remember one of the versions had a bug that we patched, then it's possible they did or didn't patch and I'm getting a few reports (of it not working, but I couldn't replicate th…
-
(Quote) You're the closest right now because I haven't done any in 7 hours. But I just fixed a couple major things in the background with our template syncs and finally got a functional Windows template so I can search "windows" now and qu…
-
(Quote) Doesn't exist (at least not with us)
-
(Quote) Don't worry there's plenty of people taking care of that for you right now.
-
(Quote) Sorry I'm not sure what you mean. Actually funny enough the first thing I did is order some coffee with a snack and the delivery guy forgot my coffee so it's very clear I'm being sabotaged.
-
(Image)
-
(Quote) It was between these two numbers. (Quote) Yeahhhhh I was pretty motivated to do a lot but things fell apart quickly after noon. Then it looks like I did my last ticket at 3:42PM and fell asleep shortly after and woke back up at 11:50PM. I t…
-
(Quote) My favorite part is how every queued email just got added to our bill even though it didn't technically actually send out. It's going to be a fun $500 overage.
-
Jesus christ I just fixed the email piping on WHMCS and it decided to queue something like half a million emails to be sent out. Luckily I caught it early so only a small number of them sent but I guess if you were a customer from 2015 through 2017 …
-
(Quote) We were going to just mess with the buttons but for now we just locked off all those nodes. Always possible one or two was missed but we'll fix it in post.
-
(Quote) On our end at least make sure you have a ticket in explaining this as you'd definitely at the very least get a refund going back to April. Sorry about that. I know it doesn't fix what happened but obviously if you've had problems since April…
-
(Quote) Most of these were completed. I don't know what state yours is in right now, this isn't something where we could help you out more quickly here but I'm definitely going through these daily still and working to fix OS and IPMI requests mostly.
-
(Quote) A little hint on this for those that want to participate. It's at 19 right now and it's 7:32AM.
-
(Quote) I was going to do your spin the other day but the wheel is in about 16 pieces. I think I rolled over it with a bunch of heavy servers.
-
(Quote) Yeah as much as I want to do that right now I think we're finally gotten to the point where it's counterproductive to do. Really trying to get to the finish line today in terms of tickets. We'll see but unlikely if servers keep going down. …
-
Phoenix will be 31.222.200.0/22 because I really like how it looks & it was the longest contract term I could find on IPXO for it. We'll send out the tickets for those later today. These should also be the first ones to be "ready" to …
-
(Quote) Glad you like it, as I said now that we actually have the time we can go back to trying to notify everyone to the best of our ability. I hope this reduces other grievances as well since people can reply to the ticket. To be honest I'm still…
-
About 12% of tickets may still be sending. About 3% are stuck and have to be requeued. 85% already sent out. Looks like the 12% either completed or some will get added to the "stuck" tally.
-
(Quote) We'll clean them up as we did the last time around as long as they're on blacklists that are legitimate and understand IPv4 addresses change leases. Obviously though if we're switching from one provider that has Cogent's $20 per abuse report…
-
(Quote) The plan was to originally provide 1 x /64 IPv6 but we decided to also provide a single IPv6 which both facilitates using it through SolusVM and is more user friendly. Adding in the 1x IPv6 is easier than adding the /64 IPv6 so a long time a…
-
Phoenix has been notified of IP address change. The emails have been sent from SolusVM. This location is not yet getting the new IP address. We're preparing to send in the tickets (emails will come from WHMCS) for the other locations. These will hav…
-
(Quote) We'll definitely get it figured out in terms of credit. I'm not saying we won't provide any, just that it may be done later so we can focus on the outage.
-
IPv4 Update - We signed the contract with the new provider and working to get it done within our timeline. I know we're behind by a day so we'll push the notice into the change officially happening on Thursday instead of next Wednesday. We've teste…
-
(Quote) The issue will require several reboots and potentially hard power off and reseating. One of the disks fully disappeared and for some reason the system isn't throwing errors which makes... no sense really but I think I've seen it happen maybe…
-
(Quote) IPv6 will be in all locations except potentially some delay in Hivelocity. Their IPv4 pricing is crazy so I'm not sure how it's going to be for IPv6 but I can't imagine it'd be too terrible. We already have large blocks with everyone else. Q…
-
(Quote) I didn't do anything, sorry, lol. I'm actually surprised it works, it shouldn't but I guess it probably does on one node still. May I know which node it is so we can try to preserve it?
-
(Quote) For probably years at this point we've been trying to streamline the process. It obviously hasn't happened. It's just very easy for these tickets to stay indefinitely in limbo because everyone other than myself is essentially afraid to do it…
-
(Quote) I believe we can share this information but I'll just say it based on what we had planned to potentially do rather than what we actually have done. We wanted to give them a chance to consider powering these on, any servers that were paid fo…
-
(Quote) I'm not sure if you're speaking of us or ColoCrossing in your comment but if it's us then the timeline doesn't correlate and it's possible you're facing some other layer of issues.
-
Currently 22.5% of TYOC035 is potentially impacted. Currently 40% of TYOC040 is potentially impacted. That means 77.5% of TYOC035 isn't and 60% of TYOC040 isn't. Even with this, we've still been getting so many tickets about them when there's alrea…
-
(Quote) SolusVM bug in this case. There's a lot of different bugs. This instance happened to have more than one. Basically at any given time it's possible for it to skip one of the rules or assignments for whatever reason and it creates a chain reac…
-
(Quote) This ticket is going to take a while to resolve at this point as a lot of miscommunication appears to have occurred and now it's in a state where it involves a problem we're having with the Windows 2022 template as well as requiring we dig f…
-
IPv4 Changes - about half the existing Ryzen customers will be affected. We're sending out emails or tickets today, so you'll (1) know if your service is affected and (2) will have our best guess for what your next IPv4 will be and a general timelin…
-
(Quote) I want to make a comment on that guess by providing you a terrible business decision we made specifically because we wanted to treat everyone equally. We lost the highest quantity of customers in the segment that was the highest paying (MSR…