New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.
Comments
Now you have me curious if I can pay for a port so I can have internal networking between my (eventual) storage VM and one of my ryzen VPS Still holding on to a few hosthatch VMs because of this.
And if you allow @LiliLabs to pay for the internal networking port on a NVMe and a storage node, can I migrate to his NVMe node for free? /j
300 tickets inbound.
EDIT: Seriously though VirMach if you had one NVMe node with a 40gb local network to the storage server you could have this as an add on and I think some people would go for it.
1gb local not so much.
It seems that the network of TYOC029 is getting worse again.
Ps:Take your time. No rush for me.
Crossposting since it's more useful here:
@VirMach made some edits to this on the other green forum, I'll update and clarify here, along with a bit of detective work on the networking Networking results might not be 100% accurate, but I have a VM in every active location and everything I say appears to be backed up by the network on those VMs. @VirMach can feel free to add this to the site if it helps. Test IP are not VirMach subnets, just ones directly from the upstreams.
Node TYOC029
larger image
Redacted original post since @LiliLabs posted a better update above.
Yep, VirMach was wrong about a few locations so I fixed it for them + added more detail.
You didn't get a "get off my lawn" vibe?
Looks like TYOC029 is definitely crashing and rebooting, I'd need to look into it further.
I just did some benchmark of VirMach deals with all the other deals I have, I am surprised by VirMach is still one of the best for the price with good enough IO
Only thing missing in Singapore location
I purchased a BF-SPECIAL-2021 on 12/01/2021, and it has not been activated for 5 months, can you help me take a look, Transaction
ID 2021113022001363371439845905 Invoice #1340061
I purchased a BF-SPECIAL-2021 on 12/01/2021, and it has not been activated for 5 months, can you help me take a look, Transaction
ID 2021113022001363371439845905 Invoice #1340061
If you or anyone else wants to suggest a viable partner for Singapore, we can definitely look into it.
Something like this:
42U/46U
2x20Ax230V A+B w/ 3.68kWh usable
2Gbps 95th @ 40Gbps port
Multi-homed/good blend
<$USD 4,000/MO
Hint: FrankZ is not an employee of VirMach
Ah, I went straight to Debian 11 in the main panel IIRC.
And HK
Anyone else having problems signing in, since updating Firefox (100.0) ?
GEThttps://billing.virmach.com/templates/vtwenty-one/src/disk/slidercaptcha.css
[HTTP/3 404 Not Found 199ms]
The resource from “https://billing.virmach.com/templates/vtwenty-one/src/disk/slidercaptcha.css” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
index.php
GEThttps://billing.virmach.com/templates/vtwenty-one/src/disk/longbow.slidercaptcha.js
[HTTP/3 404 Not Found 196ms]
The resource from “https://billing.virmach.com/templates/vtwenty-one/src/disk/longbow.slidercaptcha.js” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
index.php
Uncaught (in promise) Timeout
[Edit] May have found a workaround.. clearing cookies.
Some cookies are misusing the recommended “SameSite“ attribute 3
Cookie “cf_chl_rc_m” has been rejected because it is already expired.
[Edit2]
Yup, I'm a muppet. Now logged in.
Some (slightly) interesting warnings with the login page though.
@VirMach
I didn't do anything~
then i was suspended
I have absolutely no idea what's going on
please help me check
thanks
View Ticket #565410
Will dogecoin rise?
Sounds like you probably got hacked. What was your password? I mean no need to say it here but think about it.
Right now for unsuspensions we're only accepting ones where password is provided on the ticket, looks secure, and we can log in and see what happened. Too many of these, I guess a lot of people setting up their VM and then not securing it since it's new.
I just did look at your ticket since you're Elon Musk, and it doesn't look like you were hacked based on the usual abuse that goes on when people are but it's even worse, 50%+ I/O util for a day plus. Your VM was the one causing major problems on TYOC036. So I'll let other people on TYOC036 chime in on if you should be unsuspended but normally in this case it would be permanent because the $25 abuse fee is greater than the plan cost and no one usually wants to pay that.
So you are saying that you did not take any hacker-prevention?
It's almost always pointless to explain that "I didn't do anything". Instead, it is better to explain exactly what you did.
@VirMach Any updates on NYC and LAX?
P.S. Did you find any service that signed up for Chicago? If not can you also change the status of that to "Not part of sale"?
Vampire @Virmach, would you mind taking a wee look at the stalled AMS migration again? Or is that a developer on Monday task? Ticket #660783
I think I get it, my password is simple: 12345678
Can you help me recover?
thanks
FFS :facepalm:
@VirMach
See ticket #355723, I've paid for bandwidth overage and I haven't used my instance for a month. thanks
Yep, I guess that usually works with other hosts so we get that a lot but it indicates the complete opposite of what people think.
Actual mistakes/misunderstandings that can usually be resolved have a very detailed explanation and that's the type of unsuspension that has lowest risk of re-abuse. Highest risk is always the "I didn't do anything" crowd. I mean of course I still feel bad for them but ...
12345678
This password without SSH CA or Pubkey auth? That's simpler than my home smart lock entry password lmao
I really need to go through and make some time for updating templates to set password requirements and change default SSH port. We do always then have to deal with a ton of tickets "SSH doesn't work" and people locking themselves out and even then it's possible for people to set insecure passwords like AAaaaaabc12# but hey at least that takes 30 minutes to crack instead of 12345678, which is:
We've though about running a bruteforcer ourselves to do it first and notify customers but who wants that in their logs plus it'd kind of be strange and perhaps ethically wrong to some people.
But I mean if we notify all customers and let the ones who know how to block it (kind of like a minimal test to ensure they know how to use a computer) to go ahead and "opt out" it might work.
Maybe Musk is too kind