@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.
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?
Comments
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.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Same here @foitin . Telnet connects just fine from FFME001 and FFME006.
But telnet port is not accessible inbound to FFME001
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@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
smartass shitposting satirist
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.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
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.
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
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.
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Same here. This was a giveaway freebie.
Oh okay. Got it. Thanks for the info.
@VirMach will ya send new Tokyo storage?
smartass shitposting satirist
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
smartass shitposting satirist
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?
smartass shitposting satirist
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 ?
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
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?