@FrankZ said: @VirMach said: Around 500~ tickets of backlogs recently processed. About 700 or so still left.
About 350 left. Some abusers took up a lot of time, and then planning for some IPv4 changes and power maintenances. It's not going too well on the planning side, so the notices are going to end up being shorter than I wanted. IP change notices were supposed to go out early June and give everyone an entire month, so yeah...
I really don't want to jinx it but it looks like the last final final final patch that went out made everything silky smooth finally, so that's some amazing news there. It'll end up freeing up so much time for everything else.
NYCB027 should be good to go this weekend, sorry for the delay.
Requests have been mostly fixed, so like IP changes and migrations, they were throwing errors this week.
Controls have been fully restored as of a few days ago for MIAZ014 and whatever other(s) that had problems.
Missing LVMs have been mostly corrected, a few handful left but all nodes with significant previous issues where someone may have re-installed and made it go away have been cleaned up, and new script pushed out to most of them to try to prevent that from happening moving forward.
Disaster recovery backups have had to be paused. We have to do a full revamp, we've been having a lot of trouble with these, it hasn't been playing well with previous backups we kept from migrations as we paused pruning on those and then a handful of other problems. We're going to be fixing them to where they're much more reliable.
**IPv6* we can begin talking about this again soon, I'm just really not loving how it's currently implemented into SolusVM and we've already begun running into minor issues with those that already have IPv6. Basically it's going to definitely create a headache for any migrations, there's no API, etc.
rDNS on SolusVM may have broken, I haven't had time to look into it but I see a few reports. So that's on the list.
Dedicated servers are still a big mess. There's a big backlog of requests on these, and setups. We're going to try to clean these up and then just stop selling dedicated servers for the time being and phase them out, most likely, until we have a much better system. I'd say we would wait until we deploy our own but that's not going to happen any time soon.
@VirMach said: IPv6 we can begin talking about this again soon, I'm just really not loving how it's currently implemented into SolusVM and we've already begun running into minor issues with those that already have IPv6. Basically it's going to definitely create a headache for any migrations, there's no API, etc.
Virtfusion.
Proxmox
We accept Karma donations for the last flan. 🍮 affbrr
@virmach, about RYZE.PHX-Z001.VMS, Debian template is there at Solus, but after re-install, it comes back to old one. Nothing happens, even though it says re-installation began, and passwd is such, but after 3-4 min. it just comes back to as it was.
I have 2 vms in same node, same thing happens, if it's not fixable, can you migrate/re-provision to somewhere I don't care?
@foitin said:
can you add port 23 to sshd listening port and see if you can connect to your FFME001?
I guess it's either virmach or upstream xtom blocked it?
That's a different way to connect then in your first post, but sure.
Opening port 23 on FFME001 and connecting from anywhere is not working, blocked.
However opening port 23 on FFME006 (because I have two machines there in same subnet and node) allows me to connect from the same subnet/different VM on the same node, however outside of that (like even from FFME001 - different node/subnet) is blocked.
So something further than vmnode limiting 23
Trying to connect to port 23 from [FFME001/6] to my GreenCloud is blocked. However that random service aardmud.org 23 is working... so I guess there is some kind of whitelist in play, kinda meh, especially for testing.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
I wanted to migrate some of my VMs a while back but the location dropdown on the migration popup was showing up as empty. Now the migrate button is gone altogether.
Is it still possible to migrate any VM to a different location?
@mbk said:
I wanted to migrate some of my VMs a while back but the location dropdown on the migration popup was showing up as empty. Now the migrate button is gone altogether.
Is it still possible to migrate any VM to a different location?
@foitin said:
can you add port 23 to sshd listening port and see if you can connect to your FFME001?
I guess it's either virmach or upstream xtom blocked it?
That's a different way to connect then in your first post, but sure.
Opening port 23 on FFME001 and connecting from anywhere is not working, blocked.
However opening port 23 on FFME006 (because I have two machines there in same subnet and node) allows me to connect from the same subnet/different VM on the same node, however outside of that (like even from FFME001 - different node/subnet) is blocked.
So something further than vmnode limiting 23
Trying to connect to port 23 from [FFME001/6] to my GreenCloud is blocked. However that random service aardmud.org 23 is working... so I guess there is some kind of whitelist in play, kinda meh, especially for testing.
I thought connecting from frankfurt to port 23 was blocked at first then i found out i couldn't connect from other to port 23 on virmach frankfurt either. the aardmud service being whitelisted doesn't make a lot sense, more likely hetnzer being blocked.
can @VirMach explain what's going on here? and unblock it if possible?
@foitin said: I thought connecting from frankfurt to port 23 was blocked at first then i found out i couldn't connect from other to port 23 on virmach frankfurt either. the aardmud service being whitelisted doesn't make a lot sense, more likely hetnzer being blocked.
can @VirMach explain what's going on here? and unblock it if possible?
I have no idea. Can I get a summary of all the details? It'd need to be confirmed to account for all possibilities at all stages.
Requirements: one service on a Frankfurt node with us, another server on a Frankfurt node with us with a different IP subnet (so like 88.214.xx.xx and 213.232.xx.xx), as well as two services with two different other providers (so like Hetzner, GreenCloud.) Let's call these service A, B, C, D, respectively. And then yes/no on whether it works for all of them.
A to B
A to C
A to D
B to A
B to C
B to D
C to A
C to B
C to D
D to A
D to B
D to C
(edit) I'm just trying to get @Jab to buy another service with us.
(edit) I'm just trying to get @Jab to buy another service with us.
tryin to have people review permutations and combinations??
from other providers connecting to frankfurt virmach port 23, every provider i tried is blocked.
from frankfurt virmach to port 23 of other providers. i found hetzner and buyvm luxembourg not working.
anyone has vps service with @xTom 's v.ps in frankfurt? maybe it's blocked by them?
Requirements: one service on a Frankfurt node with us, another server on a Frankfurt node with us with a different IP subnet (so like 88.214.xx.xx and 213.232.xx.xx), as well as two services with two different other providers (so like Hetzner, GreenCloud.) Let's call these service A, B, C, D, respectively. And then yes/no on whether it works for all of them.
I can help with some of this. A=nl.n5tnl.com, C=dollar.n5tnl.com, D=van.n5tnl.com. Don't have anything on the 213.232 subnet.
IPv4:
A-C: no connection
A-D: ok
C-A: no connection
C-D: ok
D-A: no connection
D-C: ok
IPv6 (nl.n5tnl.com is using a he.net tunnel for IPv6, not native virmach IPv6):
A-C: ok
A-D: ok
C-A: ok
C-D: ok
D-A: ok
D-C: ok
If you want to hit this endpoints, the connection should succeed then reply with a short message: "Connection accepted, bye now."
IPv6 (nl.n5tnl.com is using a he.net tunnel for IPv6, not native virmach IPv6):
A-C: ok
A-D: ok
C-A: ok
C-D: ok
D-A: ok
D-C: ok
If you want to hit this endpoints, the connection should succeed then reply with a short message: "Connection accepted, bye now."
edit: A is on FFME003.
Thanks for sharing your result but since you're using HE tunnel, the IPv6 result depends on HE's firewall settings and it seems they didn't block it.
I tried to connect to 88.214.xx.xx from 213.232.xx.xx, both virmach frankfurt, not working.
from 88.214.xx.xx in tokyo to 88.214.xx.xx in frankfurt, not working either.
@AuroraZero said:
I wonder if this has to with being with CC for awhile. People could just be banning anything from the provider period by association.
Interesting. Let's add E, atl.n5tnl.com, at RN with whois showing as CC. IPv6 at E is through a he.net tunnel.
IPv4:
A-E: ok
C-E: ok
D-E: ok
E-A: no connection
E-C: ok
E-D: ok
IPv6:
A-E: ok
C-E: ok
D-E: ok
E-A: ok
E-C: ok
E-D: ok
@AuroraZero said:
I wonder if this has to with being with CC for awhile. People could just be banning anything from the provider period by association.
Interesting. Let's add E, atl.n5tnl.com, at RN with whois showing as CC. IPv6 at E is through a he.net tunnel.
IPv4:
A-E: ok
C-E: ok
D-E: ok
E-A: no connection
E-C: ok
E-D: ok
IPv6:
A-E: ok
C-E: ok
D-E: ok
E-A: ok
E-C: ok
E-D: ok
No idea's left from me on this one. Seems not to be the case.
Thank you for checking it out though as I tend to avoid CC like the plague.
O'lord Virm Ach
all Tokyo storage VPS are cramped on a single node.
Once that node goes dung, all lads are screwed.
Besides, don't ya think there is additional buck ya could squeeze?
Also new control panel UI is rather inconvenient,
the serf who modified that should be hanged
my whole service is down! I also can't open my service page in control panel, I don't know what node it is! the location is NYC.
my service ID: 691792
man your support system is a mess @VirMach can you check?
@cyforex said:
my whole service is down! I also can't open my service page in control panel, I don't know what node it is! the location is NYC.
my service ID: 691792
man your support system is a mess @VirMach can you check?
If you don't know the node name, but know it's NYC, and there is currently around the same time a node down in NYC which is NYCB028, you can at that point probably safely assume it's likely that one.
Update: unfortunately, the datacenter in Dallas has broken access to our out of bound management without notifying us previously, and then powered down the wrong server (DALZ005) causing a second outage during our maintenance request. We're still waiting for them to correct our access to DALZ004 so we can complete the reboot.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Update: unfortunately, the datacenter in Dallas has broken access to our out of bound management without notifying us previously, and then powered down the wrong server (DALZ005) causing a second outage during our maintenance request. We're still waiting for them to correct our access to DALZ004 so we can complete the reboot.
@cyforex said:
my whole service is down! I also can't open my service page in control panel, I don't know what node it is! the location is NYC.
my service ID: 691792
man your support system is a mess @VirMach can you check?
If you don't know the node name, but know it's NYC, and there is currently around the same time a node down in NYC which is NYCB028, you can at that point probably safely assume it's likely that one.
It looks like NYCB022 has also dropped by this time.
@JoeMerit said: Every NYC server is down. Dedipath offline?
The outage seems bigger than just VirMach. My VMs from another provider in the same DC when down at the same time as my VirMach VMs, and are still down.
The datacenter is experiencing a fire and is in emergency power off.
The other shoe definitely just dropped on this one. I hope everything gets sorted quickly with minimal damage to all parties involved, especially no one was, or is hurt.
Comments
Virtfusion.
I bench YABS 24/7/365 unless it's a leap year.
You guys selling Mumble Voice Servers? since when?
https://billing.virmach.com/cart.php?a=add&pid=116
Free NAT KVM | Free NAT LXC
Proxmox
We accept Karma donations for the last flan. 🍮 affbrr
It was part of a combo for paid Minecraft servers and I think we also tried doing Counter Strike servers back then too, maybe.
VirmAche holly tits, there is a control panel company literally called Virtfusion
Yo @VirMach can ya'do math?
Yor victims customers can wait,
they deserve it nevertheless.
Cuz they are all masochists nevertheless
Ontario Dildo Inspector
Oh I thought I replied to you. I think I wrote it all out then deleted it and didn't hit send.
Yo go to drain your clogged ticket queue then,
those are daily obstruction and more toxic than me I presume
Ontario Dildo Inspector
Why is outgoing port 23 blocked in Frankfurt??
Hetzner storage box uses port 23 for ssh all ssh based tools.
They use the telnet port? Why? ( smh )
MOOAR
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
200.
Seems to work here to random telnet service, so maybe not port block. Maybe it's Hetzner ;')
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Same here @foitin . Telnet connects just fine from FFME001 and FFME006.
But telnet port is not accessible inbound to FFME001
@virmach, about RYZE.PHX-Z001.VMS, Debian template is there at Solus, but after re-install, it comes back to old one. Nothing happens, even though it says re-installation began, and passwd is such, but after 3-4 min. it just comes back to as it was.
I have 2 vms in same node, same thing happens, if it's not fixable, can you migrate/re-provision to somewhere I don't care?
I can connect to this as well.
can you add port 23 to sshd listening port and see if you can connect to your FFME001?
I guess it's either virmach or upstream xtom blocked it?
MOOAN
Yo Tokyo new deal when
Ontario Dildo Inspector
That's a different way to connect then in your first post, but sure.
Opening port 23 on FFME001 and connecting from anywhere is not working, blocked.
However opening port 23 on FFME006 (because I have two machines there in same subnet and node) allows me to connect from the same subnet/different VM on the same node, however outside of that (like even from FFME001 - different node/subnet) is blocked.
So something further than vmnode limiting 23
Trying to connect to port 23 from [FFME001/6] to my GreenCloud is blocked. However that random service
aardmud.org 23is working... so I guess there is some kind of whitelist in play, kinda meh, especially for testing.Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
I wanted to migrate some of my VMs a while back but the location dropdown on the migration popup was showing up as empty. Now the migrate button is gone altogether.
Is it still possible to migrate any VM to a different location?
no except maybe Tokyo
I bench YABS 24/7/365 unless it's a leap year.
I thought connecting from frankfurt to port 23 was blocked at first then i found out i couldn't connect from other to port 23 on virmach frankfurt either. the aardmud service being whitelisted doesn't make a lot sense, more likely hetnzer being blocked.
can @VirMach explain what's going on here? and unblock it if possible?
I have no idea. Can I get a summary of all the details? It'd need to be confirmed to account for all possibilities at all stages.
Requirements: one service on a Frankfurt node with us, another server on a Frankfurt node with us with a different IP subnet (so like 88.214.xx.xx and 213.232.xx.xx), as well as two services with two different other providers (so like Hetzner, GreenCloud.) Let's call these service A, B, C, D, respectively. And then yes/no on whether it works for all of them.
(edit) I'm just trying to get @Jab to buy another service with us.
tryin to have people review permutations and combinations??
from other providers connecting to frankfurt virmach port 23, every provider i tried is blocked.
from frankfurt virmach to port 23 of other providers. i found hetzner and buyvm luxembourg not working.
anyone has vps service with @xTom 's v.ps in frankfurt? maybe it's blocked by them?
I can help with some of this. A=nl.n5tnl.com, C=dollar.n5tnl.com, D=van.n5tnl.com. Don't have anything on the 213.232 subnet.
IPv4:
A-C: no connection
A-D: ok
C-A: no connection
C-D: ok
D-A: no connection
D-C: ok
IPv6 (nl.n5tnl.com is using a he.net tunnel for IPv6, not native virmach IPv6):
A-C: ok
A-D: ok
C-A: ok
C-D: ok
D-A: ok
D-C: ok
If you want to hit this endpoints, the connection should succeed then reply with a short message: "Connection accepted, bye now."
edit: A is on FFME003.
Thanks for sharing your result but since you're using HE tunnel, the IPv6 result depends on HE's firewall settings and it seems they didn't block it.
I tried to connect to 88.214.xx.xx from 213.232.xx.xx, both virmach frankfurt, not working.
from 88.214.xx.xx in tokyo to 88.214.xx.xx in frankfurt, not working either.
I wonder if this has to with being with CC for awhile. People could just be banning anything from the provider period by association.
Just a theory is all.
The Yeti has left the building.
Interesting. Let's add E, atl.n5tnl.com, at RN with whois showing as CC. IPv6 at E is through a he.net tunnel.
IPv4:
A-E: ok
C-E: ok
D-E: ok
E-A: no connection
E-C: ok
E-D: ok
IPv6:
A-E: ok
C-E: ok
D-E: ok
E-A: ok
E-C: ok
E-D: ok
No idea's left from me on this one. Seems not to be the case.
Thank you for checking it out though as I tend to avoid CC like the plague.
The Yeti has left the building.
Same here. This was a giveaway freebie.
Oh okay. Got it. Thanks for the info.
@VirMach will ya send new Tokyo storage?
Ontario Dildo Inspector
TYOC007 in virmach had been offline for a long time
Is there any repair progress or recovery plan?
No deals for that ever planned again.
O'lord Virm Ach
all Tokyo storage VPS are cramped on a single node.
Once that node goes dung, all lads are screwed.
Besides, don't ya think there is additional buck ya could squeeze?
Also new control panel UI is rather inconvenient,
the serf who modified that should be hanged
Ontario Dildo Inspector
Yo @VirMach ,
What is the average HDD lifespan on your colocations? Will ya purchase cheap SMR to cut cost?
Which PCIe gen and brand Nvme SSD are ya using? How much IO it will fall after exceed its TBW?
Ontario Dildo Inspector
also when will we colonize Mars?
I bench YABS 24/7/365 unless it's a leap year.
And while your at it how can we resolve hunger in the Americas and establish world peace ?
Mars is very close. I need an IPv69 VPS on Kepler-442b.
NYCB028
Operation Timed Out After 90000 Milliseconds With 0 Bytes Received
Ya, NYCB028 is kaput.
my whole service is down! I also can't open my service page in control panel, I don't know what node it is! the location is NYC.
my service ID: 691792
man your support system is a mess
@VirMach can you check?
If you don't know the node name, but know it's NYC, and there is currently around the same time a node down in NYC which is NYCB028, you can at that point probably safely assume it's likely that one.
Seems fun?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
When it rains, it pours it seems.
The Yeti has left the building.
It looks like NYCB022 has also dropped by this time.
Every NYC server is down. Dedipath offline?
NYCB040 is down here
Operation Timed Out After 90000 Milliseconds With 0 Bytes Received
Ny Nodes are all offline, Operation Timed Out After 90000 Milliseconds With 0 Bytes Received
I guess it's this
https://status.dedicated.com/
aka
The datacenter is experiencing a fire and is in emergency power off.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
The outage seems bigger than just VirMach. My VMs from another provider in the same DC when down at the same time as my VirMach VMs, and are still down.
The other shoe definitely just dropped on this one. I hope everything gets sorted quickly with minimal damage to all parties involved, especially no one was, or is hurt.
The Yeti has left the building.