@FrankZ said: Doubt this is going to happen as it would probable just screw up the works and the planned migrations already in progress.
does that mean it is being migrated to L.A?
I have no more information on what is going on then what has been published by VirMach. As far as I know Seattle is still up in the air right now, but whatever happens I'll be right there with you as I also have a VM on SEAZ002.
@lesuser said:
NYCB030 and NYCB043 got new IP. I pressed Fix Internet/Configure button but still cannot SSH to both. Looks like need to wait a little for IP to propagate globally.
That fix button keeps breaking my connection. It uses the wrong interface name in /etc/network/interfaces (Debian). Worth checking to see if that's what happened to you. If so, just a quick edit and /etc/init.d/networking restart is all that's needed.
@VirMach Can you update us what is the status of the routing/bgp problems at NY ?
I see in a popup :
"If you are having connectivity issues, this is normal. Since these are new IP addresses, they may take several hours to ping globally."
Range : 46.233.45.xxx
Monitor systems :
Status:
Ongoing
Started at:
2023-09-03 18:58:49
Duration:
3 d, 13 h, 27 m
There is nothing on the status page and no further information here.
I have a VM on this range also. I can get to it via ssh through a jump box I have at VirMach Amsterdam without using VNC. Can ping 8.8.8.8 and 9.9.9.9 from the VM. Most other places I am still waiting for routes to update.
@vgood said: Until now there hasn't been any progress and solutions @VirMach for LAX2Z019
It died. I expect the data recovery got put off because of bigger fish to fry. It was also stated
If you have important data and/or would like a new service brought online in the time being, please contact us.
I also am on LAX2Z019, but I have redundant data on a different VM, so I did not try contacting them for a temp replacement. So I am not really sure how that would go for you.
@vgood said: Until now there hasn't been any progress and solutions @VirMach for LAX2Z019
It died. I expect the data recovery got put off because of bigger fish to fry. It was also stated
If you have important data and/or would like a new service brought online in the time being, please contact us.
> @FrankZ
thank you for helping answer. actually the last VPS was just installed OS and there wasn't any data yet, then the VPS was off and couldn't be used.
I'm confused now, there are more menus for contacting @VirMach , even the request menu for moving nodes can't be used.
I want to create a ticket, it always looks like the picture below, I'm confused
NYCB021 (141.11.XX.XX) here. Routing seems to be completely established now, altough ping times from certain locations are still a bit funky. Atleast I can SSH into the box now
One of the options is direct upgrade from Debian 11.
nano /etc/apt/sources.list
deb http://deb.debian.org/debian bookworm main contrib non-free-firmware non-free
deb http://deb.debian.org/debian bookworm-updates main contrib non-free-firmware non-free
deb http://security.debian.org/debian-security bookworm-security main contrib non-free-firmware non-free
Damn you VirMach! Can you like have a bigger/longer outage so we can get +1 year for free on every VPS?!
This went kinda not bad for emergency migration - I hope other location you can get IP ranges already routed in advance and switch will be almost painless?
@Mumbly said:
One of the options is direct upgrade from Debian 11.
nano /etc/apt/sources.list
deb http://deb.debian.org/debian bookworm main contrib non-free-firmware non-free
deb http://deb.debian.org/debian bookworm-updates main contrib non-free-firmware non-free
deb http://security.debian.org/debian-security bookworm-security main contrib non-free-firmware non-free
Comments
does that mean it is being migrated to L.A?
I have no more information on what is going on then what has been published by VirMach. As far as I know Seattle is still up in the air right now, but whatever happens I'll be right there with you as I also have a VM on SEAZ002.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
That fix button keeps breaking my connection. It uses the wrong interface name in /etc/network/interfaces (Debian). Worth checking to see if that's what happened to you. If so, just a quick edit and
/etc/init.d/networking restartis all that's needed.Yep, definitely don't recommend using the fix network button if you installed from an ISO or have a network interface not named "eth0".
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Deja Vu.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
You need to put that then/than stuff back in your signature. I was using it as a reference, now I am totally lost again.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
NYCB027 is still locked.
@VirMach Can you update us what is the status of the routing/bgp problems at NY ?
I see in a popup :
"If you are having connectivity issues, this is normal. Since these are new IP addresses, they may take several hours to ping globally."
Range : 46.233.45.xxx
Monitor systems :
Status:
Ongoing
Started at:
2023-09-03 18:58:49
Duration:
3 d, 13 h, 27 m
There is nothing on the status page and no further information here.
I have a VM on this range also. I can get to it via ssh through a jump box I have at VirMach Amsterdam without using VNC. Can ping 8.8.8.8 and 9.9.9.9 from the VM. Most other places I am still waiting for routes to update.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
This is still invalid so as long as nothing happen it will not be solved.
RPKI Chain (Invalid)
https://rpki-validator.ripe.net/ui/46.233.44.0/23?validate-bgp=true
We're aware. IP provider has to update it, we're waiting.
I'm sorry teacher! it won't happen again I try to be a better student so I can impress some geek with my English skills
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Until now there hasn't been any progress and solutions @VirMach for LAX2Z019, I haven't been able to use VPS on this node for about 3 weeks.
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
It died. I expect the data recovery got put off because of bigger fish to fry. It was also stated
I also am on LAX2Z019, but I have redundant data on a different VM, so I did not try contacting them for a temp replacement. So I am not really sure how that would go for you.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
>
@FrankZ
thank you for helping answer. actually the last VPS was just installed OS and there wasn't any data yet, then the VPS was off and couldn't be used.
I'm confused now, there are more menus for contacting @VirMach , even the request menu for moving nodes can't be used.
I want to create a ticket, it always looks like the picture below, I'm confused
just opened 200 tickets about my services, hoping to speed up a resolution here
https://tenor.com/bGBAb.gif
Want free vps ? https://microlxc.net
denver and atlanta come online with old ip
I can SSH into following NYCB043 even though it is showing
Invalid RPKIhttps://rpki-validator.ripe.net/ui/141.11.212.0/24?validate-bgp=true
Can't SSH into following NYCB030 even though its
RPKIis valid!https://rpki-validator.ripe.net/ui/45.42.214.0/24?validate-bgp=true
Doing
nano /etc/network/interfacesshows that both VPS have similar configuration with new IPs. Interface iseth0Fast as fuck Core i9 VPS (aff) | Powerful AMD Ryzen VPS (aff)
My VM on NYCB015 that is.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I did
Reconfigure Networkingfrom SolusVM and now getting a different SSH errorConnection refusedPreviously I was getting error
Connection timed outFast as fuck Core i9 VPS (aff) | Powerful AMD Ryzen VPS (aff)
NYCB021 (141.11.XX.XX) here. Routing seems to be completely established now, altough ping times from certain locations are still a bit funky. Atleast I can SSH into the box now
Ok It was my mistake. I was using wrong IP.
By the way does any one know how can I install Debian 12 minimal?
Fast as fuck Core i9 VPS (aff) | Powerful AMD Ryzen VPS (aff)
One of the options is direct upgrade from Debian 11.
nano /etc/apt/sources.list
apt-get update -y && apt-get upgrade -y
apt-get dist-upgrade -y
mount netboot.xyz and manually install it?
Damn you VirMach! Can you like have a bigger/longer outage so we can get +1 year for free on every VPS?!
This went kinda not bad for emergency migration - I hope other location you can get IP ranges already routed in advance and switch will be almost painless?
// 204.10.X.X seems to be fully routing now too
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
That was very easy. Took a few minutes.
Fast as fuck Core i9 VPS (aff) | Powerful AMD Ryzen VPS (aff)
Your IP xxx.xx.xx.xx has been banned
Ban Reason: Banned for 46 login attempts.
Ban Expires: 09/07/2023 (21:00)
Hello, Los Angeles Vps inaccessible, showing Operation Timed Out After 90001 Milliseconds With 0 Bytes Received? Why are there no failure reports?