@vgood said:
please, please help, I can't enter the member panel @VirMach because it's blocked by 2FA, can't reinstall or transaction, please follow up on ticket # 261273 (I don't have my old cell phone and no backup code either)
>
please help me @VirMach
the old ticket was closed virmach, but the problem is still the same. please help me on new ticket Ticket #300350 (03/29/2023)
Thank You
@vgood said:
please, please help, I can't enter the member panel @VirMach because it's blocked by 2FA, can't reinstall or transaction, please follow up on ticket # 261273 (I don't have my old cell phone and no backup code either)
>
please help me @VirMach
the old ticket was closed virmach, but the problem is still the same. please help me on new ticket Ticket #300350 (03/29/2023)
Thank You
@rockinmusicgv said:
NYCB009 has been down for about a day and seems to be on a different IP block. Is there any indication when that node might be restored?
Yeah, it didn't come back long enough for us to be able to complete the planned emergency migration. It's difficult to get back online too, we've been working on that for a long time. Still speaking with RAID controller manufacturer but now it seems like there's a whole set of other issues.
Copying this from the network status page for Frankfurt and Amsterdam.** New IP addresses as follows for Frankfurt & Amsterdam.**
Please go to your service details page, and check the "node" name, and the last portion of your IPv4 address (the bolded number in this example) 47.87.yy.xx and place that portion (.xx) as it matches on the below list for your new IP address. We are still modifying these & still need to change them on the VPS control panel but this is a quick way to know what your new IPv4 address will become.
I got new IP but when i reconfigure network it say unknown system detected, even if I ping the server i get few pings while reconfiguring and then it stop again
VNC is shot screen is corrupted and I am not sure how to fix it without googling
Is it possible to do emergency-login when I disabled password auth entirely? This made me realize that if I can't reach my servers over SSH directly I can't log in because I can't do key auth.
@MallocVoidstar said:
Is it possible to do emergency-login when I disabled password auth entirely? This made me realize that if I can't reach my servers over SSH directly I can't log in because I can't do key auth.
You would need to boot into recovery mode and reset the root password. Then log in via console.
Simple and secure Borg Backup hosting from $2/month: BorgBase.com
@MallocVoidstar said:
Is it possible to do emergency-login when I disabled password auth entirely? This made me realize that if I can't reach my servers over SSH directly I can't log in because I can't do key auth.
@MallocVoidstar said:
Is it possible to do emergency-login when I disabled password auth entirely? This made me realize that if I can't reach my servers over SSH directly I can't log in because I can't do key auth.
"disabled password auth entirely" how?
Wait, I think I forgot what password I set. Well, how awkward, guess I know what I'm doing when the network is back...
@Mumbly said: The same. "Reconfigure network" on 025 and 028 doesn't do anything so far.
Should be fixed now for that particular error.
Had to do with the IP steal protection, it uses another table for that which I just finished updating. Unfortunately if you're early to the reconfiguring I can't promise it won't go down for a mass reconfigure as the script that pings first to reconfigure isn't working great and developer's not around so we're using a different method. Could mean one last VM reboot.
Lost my additional IPs after the IP change (FFME004 flash sale server), hopefully this is just temporary
Also, the same VPS: clicking on 'VPS Control Panel' still results in 'Invalid vserverid or username' - I hope this issue will be dealt with eventually.. :<
Using this as an opportunity to soft remove the custom ticket option at the bottom of ticket creation page, to encourage people to use the new "Contact Us" button. As that will greatly help us in this case and in the future, since we'll get the IP address and node names immediately so we'll be able to know which of the various tickets created can be referred to the network status page and which ones are unrelated.
I say soft remove because you can obviously technically get to it in one way or another, just the visible link on the step one of creating a ticket page.
@chimichurri said: Also, the same VPS: clicking on 'VPS Control Panel' still results in 'Invalid vserverid or username' - I hope this issue will be dealt with eventually.. :<
This should be an unrelated issue which you need to create a ticket for to fix at this point if it didn't get fixed automatically already. I know @FrankZ mentioned this at some point as well, just tagging you in case you're in the same boat still.
@chimichurri said: Lost my additional IPs after the IP change (FFME004 flash sale server), hopefully this is just temporary
Unfortunately it's a side effect of trying to complete this quickly on an emergency basis. I'll see what we'll do about it, or if I need to tell everyone to contact us again using missing IPs button.
@SeaScoot said:
What's the timeline for servers with that IP range in the US?
I have no timeline, but I'm going to begin preparing for mass changes should that be necessary. We're still awaiting a response from the IP lessor.
FFME001, FFME004 and AMSD030 are back for me.
AMSD026 network re config is giving an error. (FFME004 was giving the same error so I'm sure it'll work soon)
Tickets are out of control. I'm going to try to mass clear them up again without incorrectly flagging the wrong tickets unrelated to 47.87.xx.xx issue but apologies in advance if you get one for something unrelated. The ones with lower confidence I'll flag for recreation using the new button, the ones with higher confidence will get the mass issue reply. I want to avoid having another long backlog.
@soulchief said: AMSD026 network re config is giving an error. (FFME004 was giving the same error so I'm sure it'll work soon)
Should already work now, if it still doesn't work definitely let me know.
@VirMach said:
Tickets are out of control. I'm going to try to mass clear them up again without incorrectly flagging the wrong tickets unrelated to 47.87.xx.xx issue but apologies in advance if you get one for something unrelated. The ones with lower confidence I'll flag for recreation using the new button, the ones with higher confidence will get the mass issue reply. I want to avoid having another long backlog.
@soulchief said: AMSD026 network re config is giving an error. (FFME004 was giving the same error so I'm sure it'll work soon)
Should already work now, if it still doesn't work definitely let me know.
Just tried again and is still returning:
An Error Occurred!
Unknown Error
Edit: booted up in VNC and it's getting the Failed to mount error so that's probably why it's not working.
It's a combination of two third party software. Our chat software (https://crisp.chat) and server monitoring software (https://nixstats.com/) and the on/off button for the sidebar is courtesy of someone on JsFiddle.
@soulchief said: Edit: booted up in VNC and it's getting the Failed to mount error so that's probably why it's not working.
Oh make sure to unmount any ISO. But I'll also check and make sure there's not a combo coincidental issue of a disk missing or something like that. (edit: confirmed no disk issue.)
Comments
It'll keep dying right after a service is checked due to timeouts but otherwise it'll be up, it's not on the same infrastructure.
Your ticket would be closed as "mass issue" and there's no SLA credits.
This was what happened to my MIAZ011 ticket last week.
We accept Karma donations for the last flan. 🍮 affbrr
I have opened and closed the work order. I don't know when TYOC007 will be restored, at least there are currently no plans for repairs
Thanks for sharing.
NYCB009 has been down for about a day and seems to be on a different IP block. Is there any indication when that node might be restored?
NYCB030 is also not accessible
Powerful AMD Ryzen VPS (aff)
It's time to screw the IPv4 and assign native IPv6 subnet to every service.
We accept Karma donations for the last flan. 🍮 affbrr
testically strong people don't throw IPv4 but scale with IPv6
>
please help me @VirMach
the old ticket was closed virmach, but the problem is still the same. please help me on new ticket Ticket #300350 (03/29/2023)
Thank You
so now i can see my AMS VPS panel, original IP 47.87....with no second IP, its "live" on solusvm and whmcs, but cant SSH in
I bench YABS 24/7/365 unless it's a leap year.
Native IPv6 work - if you have it :P
Review this new page:
https://virmach.com/security/
We'll begin accepting 2FA reset requests on 5/21/2023 and there's a 2 week lockout period for phone.
Yeah, it didn't come back long enough for us to be able to complete the planned emergency migration. It's difficult to get back online too, we've been working on that for a long time. Still speaking with RAID controller manufacturer but now it seems like there's a whole set of other issues.
I don't have any more information at the time.
Copying this from the network status page for Frankfurt and Amsterdam.** New IP addresses as follows for Frankfurt & Amsterdam.**
Please go to your service details page, and check the "node" name, and the last portion of your IPv4 address (the bolded number in this example) 47.87.yy.xx and place that portion (.xx) as it matches on the below list for your new IP address. We are still modifying these & still need to change them on the VPS control panel but this is a quick way to know what your new IPv4 address will become.
78.142.228.xx AMSD030
78.142.229.xx AMSD029
78.142.230.xx AMSD028
78.142.231.xx AMSD027
147.78.240.xx AMSD026
147.78.241.xx AMSD025
213.232.112.xx FFME007
213.232.113.xx FFME006
213.232.114.xx FFME005
213.232.115.xx FFME004
88.214.20.xx FFME003
88.214.21.xx FFME002
88.214.23.xx FFME001
Let me try to think of a good way of making sure this doesn't happen, but after everything else I have to look at today.
back online with new IP.
I bench YABS 24/7/365 unless it's a leap year.
by far the most trashy provider I ever used
How about LA? Sadly have 5 vms with 47.87 prefix.
chil , have a break
have a kitkat
stroll
this one
im more into plants
If you're gonna post a bike picture at least post a pretty one.
I got new IP but when i reconfigure network it say unknown system detected, even if I ping the server i get few pings while reconfiguring and then it stop again
VNC is shot screen is corrupted and I am not sure how to fix it without googling
Back online on AMSD029.
"The imitator dooms himself to hopeless mediocrity." — Ralph Waldo Emerson
Seeing a new IP for AMSD028, but no networking yet.
Simple and secure Borg Backup hosting from $2/month: BorgBase.com
The same. "Reconfigure network" on 025 and 028 doesn't do anything so far.
tightvnc, turbovnc, vnc viewer all get garbled screen
Is it possible to do emergency-login when I disabled password auth entirely? This made me realize that if I can't reach my servers over SSH directly I can't log in because I can't do key auth.
In vnc should work fine. I have only 1 allowed user on ssh but from vnc i can login with root without problems.
ServerStatus , slackvpn , linux mirrors
Recommended Providers: Servarica(aff) | HostBRR(aff) | SolidVPS(aff) | RackNerd(aff) | KuroIT(aff) | AlphaVPS(aff) | HostDare(aff)
You would need to boot into recovery mode and reset the root password. Then log in via console.
Simple and secure Borg Backup hosting from $2/month: BorgBase.com
"disabled password auth entirely" how?
For me i got networking for 10 seconds while doing reconfiguring and when its finished im losing again networking. Probably its not ready yet.
ServerStatus , slackvpn , linux mirrors
Recommended Providers: Servarica(aff) | HostBRR(aff) | SolidVPS(aff) | RackNerd(aff) | KuroIT(aff) | AlphaVPS(aff) | HostDare(aff)
My uptime report says the same for one of .nl VPSes. Networking appeared online for some short time and died right after that.
They are coming back now.
Wait, I think I forgot what password I set. Well, how awkward, guess I know what I'm doing when the network is back...
Still no sign of VMs in Buffalo
Powerful AMD Ryzen VPS (aff)
My VPS in Amsterdam is up and running for over an hour now; did the reconfiguring by hand through the VNC terminal.
Should be fixed now for that particular error.
Had to do with the IP steal protection, it uses another table for that which I just finished updating. Unfortunately if you're early to the reconfiguring I can't promise it won't go down for a mass reconfigure as the script that pings first to reconfigure isn't working great and developer's not around so we're using a different method. Could mean one last VM reboot.
What's the timeline for servers with that IP range in the US?
Lost my additional IPs after the IP change (FFME004 flash sale server), hopefully this is just temporary
Also, the same VPS: clicking on 'VPS Control Panel' still results in 'Invalid vserverid or username' - I hope this issue will be dealt with eventually.. :<
Contribute your idling VPS/dedi (link), Android (link) or iOS (link) devices to medical research
Using this as an opportunity to soft remove the custom ticket option at the bottom of ticket creation page, to encourage people to use the new "Contact Us" button. As that will greatly help us in this case and in the future, since we'll get the IP address and node names immediately so we'll be able to know which of the various tickets created can be referred to the network status page and which ones are unrelated.
I say soft remove because you can obviously technically get to it in one way or another, just the visible link on the step one of creating a ticket page.
Me too, online on AMSD028 and AMSD029
This should be an unrelated issue which you need to create a ticket for to fix at this point if it didn't get fixed automatically already. I know @FrankZ mentioned this at some point as well, just tagging you in case you're in the same boat still.
Unfortunately it's a side effect of trying to complete this quickly on an emergency basis. I'll see what we'll do about it, or if I need to tell everyone to contact us again using missing IPs button.
I have no timeline, but I'm going to begin preparing for mass changes should that be necessary. We're still awaiting a response from the IP lessor.
FFME001, FFME004 and AMSD030 are back for me.
AMSD026 network re config is giving an error. (FFME004 was giving the same error so I'm sure it'll work soon)
There's no VMs in Buffalo. They stopped existing in early 2022.
Tickets are out of control. I'm going to try to mass clear them up again without incorrectly flagging the wrong tickets unrelated to 47.87.xx.xx issue but apologies in advance if you get one for something unrelated. The ones with lower confidence I'll flag for recreation using the new button, the ones with higher confidence will get the mass issue reply. I want to avoid having another long backlog.
Should already work now, if it still doesn't work definitely let me know.
Yeah you are right, may be they not in Buffalo. I am talking about NYCB030
Powerful AMD Ryzen VPS (aff)
https://statusbot.virm.ac/en/ looks nice af. Kudos to whoever made it.
Just tried again and is still returning:
An Error Occurred!
Unknown Error
Edit: booted up in VNC and it's getting the Failed to mount error so that's probably why it's not working.
It's a combination of two third party software. Our chat software (https://crisp.chat) and server monitoring software (https://nixstats.com/) and the on/off button for the sidebar is courtesy of someone on JsFiddle.
Oh make sure to unmount any ISO. But I'll also check and make sure there's not a combo coincidental issue of a disk missing or something like that. (edit: confirmed no disk issue.)