VirMach
VirMach
Comments
-
This guy definitely has a twisted logic, he's opened over 100 tickets so far. He thinks it's probably super inconveniencing to us because he doesn't know I can run one script in a second now and merge them all. In fact, he is the reason we had this coded out. I think it all started when he made some ticket and it got…
-
Alright, hands down funniest ticket title of the week. I just love how he went through the extra effort to censor himself in case we found the f word offensive but not the rest of it, and the "3" at the end indicating he made at least 2 others that he titled 1 and 2 and got merged into this one.
-
Processing some refunds now, including from this sale. Usually I'd close the tickets but I'm going to process refunds because we have more orders and less space than I thought immediately available on Tokyo. So if you created a ticket before this message about "still pending" service in Tokyo, it will most likely result in…
-
If it's from this sale and you are requesting a refund, then you shouldn't have made a ticket for a refund. If it's from another sale where you're eligible for a refund, then it may have been closed by mistake.
-
I recommend you do not read any of my updates and instead replace it with a vague but very well thought out PR response by a company executive. There's no bugs, nothing wrong, everything is going as expected and your service will be activated soon. We apologize for any delays, etc. But what do I know, that was just another
-
All services outside of maybe 5 of them have been recreated for SJCZ003 and SJCZ007 issue. Most TYOC038 have been recreated. Some still need to be created if they never created properly in the first place on TYOC038. And SEAZ001 is still having issues, I'm trying to look at that again next.
-
So most people should have their extra month now, even if you recreated already.
-
If you recreate/migrate it will be hard for us to track, just wait until everything cools off a bit and then create a ticket for the addition with a clear explanation. I'll see if I can add these now for any future recreations to cut down on ticket numbers though.
-
At this point anyone having those kind of issues will already be resolved and there's room for those people already set aside, so migrating will not help in this situation but thank you for your kind thinking.
-
Yeah, I reported this to our developer already. I need to start going in manually and fixing these but I tasked our developer with fixing these manually. To be fair though it's not his fault, it's an old bug with our provisioning module liking to reset bandwidth levels to 1GB because the coder for the module (which is…
-
This would be a case of:
-
In this case you would just do nothing right now. After 30 days, you can create a ticket for refund, if it takes that long for us to resolve it on our own.
-
I do want to mention something else important: we specifically built the Ryzen migrate button to where it can be used by Ryzen plans to re-create so we do encourage if you are on SJCZ003 and SJCZ007 or any other node where you are having issues to use this button if you do not have important data, and you'll be re-created…
-
Sorry, I can't keep up with the manual activations here. I'm switching the sale to immediate activations which should also still fall in line with the exclusivity period for LES exclusive sales, I believe it's something like at least a week exclusive? Still trying to keep up with all the re-creations, doing my best to…
-
Hi guys, if you're stuck on a node with a broken VM it might be worth a try to do the Ryzen migrate option for faster re-create, I'll try to add it for SJC but it'll work for TYOC038 problem. That was basically my creating our own message board idea. It was just going to be you and a bunch of angry customers in a single…
-
We just closed a ton of tickets related to accounts that are either [1] marked as problematic, [2] special offer related, [3] multi-account. We realize this may have some false positives so if you had an important ticket, please re-create it in the priority department. Otherwise please consider waiting some time to…
-
Sorry, haven't had a chance to review all the new orders here. I'm finally gearing up to recreate everyone affected on SJCZ007 and SJCZ003. It didn't help that the Tokyo maintenance was less than ideal, and TYOC038 has another disk having problems so that has to be queued for recreations as well as we can't handle all…
-
This is the default behavior when a node is down. It's on the list to try to get this to display a better error but it's just how it was coded out (not by us.) I believe I remember you being on SJCZ003 which is part of the outage I described on page 24. It's been an extremely hectic day, I haven't had time to post an…
-
I can understand why some people are freaking out based on how strictly I worded everything on the original post (on purpose, to encourage people to do it correctly.) Order ID allows me to quickly deploy them. I can of course make an exception and look everything up via the other information but I'm not going back and…
-
Can I get more info on this problem again? Is it the rate limits?
-
SJCZ003 has regressed to the same point SJZC007 did earlier. It crashed right as my plane took off, really bad timing. I'm the one handling these right now and no one else so it's been difficult to do anything with the spotty WiFi. There's about 18 people on SJCZ007 and 39 or so people on SJCZ003 right now. Basically even…
-
By Wednesday as I mentioned. It's possible it could be available sooner or perhaps later if we run into problems. I'll activate in San Jose now. You need to come back here to request it be moved since it's not being tracked anywhere else.
-
SJCZ003 seems more stable and just needs RAM replacement. It seems to be error correcting itself better now after BIOS and firmware updates, whether or not that's a coincidence. SJCZ007 however seems completely broken. Luckily there's not that many people on it. Seems to be stuck in a reboot loop so migrations can't…
-
Since everyone has already been warned of a migration and I assume expects a powerdown and the node may face further issues, I'm powering down SJCZ003 for a BIOS update. SJCZ007 was stuck in a loop still and I'm having DC hands take a look. (edit) After a little more digging, it looks like at least SJCZ003 is having memory…
-
SJCZ007 is not looking good, it's going into reboot loops right now. I'm trying to migrate everyone per the email I sent out but migration function is also suffering.
-
You have to use the billing area for re-installs.
-
This seems to be having the same issue SJC007 recently had. I'm trying to remember what batch of hardware this was that sent out because it could start coming up as an issue with the entire San Jose batch if it's not just isolated to a single machine. I may modify BIOS settings and mess with something software side because…
-
Cancelled & refunded. This is a storage offer from another website. Sorry but I can't have people migrating here to spam their order IDs from that.
-
I replied to this above, this looks like it had CPU lockups potentially. Still looking.
-
I missed your original post so I apologize for that but yes, it's normal behavior for manual activation.
-
Replying to you since there was a discussion about this on page 20. It's not just you benchmarking that's the issue, it's everyone at once. There's a good number of people on these nodes now so even if 5% of them are benchmarking constantly it's enough to cause that level of CPU steal. It's calmed down since your post…
-
I think Nginx went down, taking a look. We don't yet have ALL the notifications configured for these new nodes so I do apologize for this not being handled sooner. (edit) Uhoh, looks worse. Looks like it froze. Rebooting and checking logs.
-
Case #5 Recurring price has been increased $5 for the last ticket created and $5 more for the other three tickets, I've discounted the increase by $5 (you were previously charged $5 for one of them, so total three instead of four increases.)
-
I'm going to start adding these renewal increases. I'll try to post them all here so there can be some kind of tribunal if you guys would like or at least some transparency so people don't think we're just randomly doing it just to be unfair or to make money. I'll start making notes and post these in batches. Case #1 We're…
-
May I ask how you're 100% sure? It's possible it's related but this is the first report of this I've seen (the 100% correct username and password triggering a login error.)
-
I've thought about this and I assume the exclusive offers are meant to have this effect, since you can see the enticing titles as a guest. I'm new here though so someone could probably explain the actual intention better. I did personally feel that it could be a good nudge in the right direction. If it doesn't appear it…
-
I can increase your renewal fee if you keep posting your invoice ID here, that's about it.
-
Did you post your order ID here before? Maybe I missed it, I'll take a look now.