@Brayvin said: @VirMach How can I verify what my web host IP address is when the control panel is broken and not working?
just start going through them, you will find it eventually, its the one that works with your password.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
@tulipyun said: Today marks six months since SJC went offline. Would you be willing to share any stories, information or future plans regarding SJC with everyone?
>
I am on the same server node SJCZ012 as you. I am also eagerly awaiting the official virmach announcement.
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
Poor Paddington, he must be very angry.
Sounds like it's going the same way as the UK for similar and different reasons
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
Sorry to hear that things are so bad. What may be the worst part is when people lose the expectation that things will get better and instead expect it will get worse as time goes on.
@lesuser said:
My VPS in NYCB043 is not accessible ever since its IP was changed a month ago. It is up and I can connect via VNC though.
I've extended service duration by a month since we're still getting this node mentioned. I've already (2-3 weeks ago) resolved the initial problem affecting the node. I saw the reports here and took a look and could not find another issue. I have looked into it again, this time reading and responding to a few tickets and so far I have confirmed it appears that anyone left still having issues on NYCB043 needs to manually configure the networking within their operating system.
I'll update you guys here if I notice anything else. Given everything I have reviewed though, I am fairly confident in this assessment.
One quick way to verify this for yourself so you do not waste a long time fixing the configuration only to find out it was an issue on our end would be to mount an ISO, boot into it, and see if connectivity works there.
I'll give a quick example. Pick System Rescue CD, change boot order to CD ROM, reboot, then type in startx on VNC, open terminal, and add route: ip route add default via 185.213.18.1 as well as your IP address: ip addr add 185.213.18.xx/24 dev ens3 and make sure the link is up (ip link set ens3 up) and then open Chrome or ping 8.8.8.8; if you're able to do that, it means it's most definitely an issue with your operating system's network configuration and that the automatic reconfiguration is not working.
@ahnlak said:
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
Which node is this on? I vaguely remember I spoke with you some time ago and you must have been on NYCB043, 44, or 45. And I addressed issues with those nodes at that time. So it's highly likely if you are still facing an issue, my comment above should also be helpful to you.
I'm here, I'm just not in a very "random walls of text" mood. There should have been one comment I made around June 12th which I don't see, so that means I wrote it out and didn't click post or though I did. That was in response to msatt and someone else. I definitely saw the comment about Amazon pay being broken after that, I saw the comment about LAX1Z020 being down, about Oklahoma. I saw Brayvin's comment asking about webhosting and did not have time to look into that (and saw Anthony's joke.) I saw tulipyun's 6 month anniversary post about SJC and the few comments after it and it's been kind of quiet other than that.
I will admit though I did not see your comment and the ones after it (so I've 100% been gone from LES around June 22nd to today.) I just haven't had time this past week to check.
My next reply will likely be about San Jose, hopefully this week.
@ahnlak said:
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
Which node is this on? I vaguely remember I spoke with you some time ago and you must have been on NYCB043, 44, or 45. And I addressed issues with those nodes at that time. So it's highly likely if you are still facing an issue, my comment above should also be helpful to you.
I'm on NYCB045 - and no, the network config is correct and booting into System Rescue also can't reach the gateway (185.213.19.1, as the box is a .19.xx address, although for a laugh it also can't see .18.1).
I'm pretty sure it's not an OS config (especially given that System Rescue test) and even your AI support bot thinks "the possibility of an issue at the virtualization level on the host node NYCB045" - that ticket has sat awaiting technical review all month, FWIW.
The other box that got a new IP went flawlessly, so it can work even in NY but this one seems especially cursed.
@ahnlak said:
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
Which node is this on? I vaguely remember I spoke with you some time ago and you must have been on NYCB043, 44, or 45. And I addressed issues with those nodes at that time. So it's highly likely if you are still facing an issue, my comment above should also be helpful to you.
I'm on NYCB045 - and no, the network config is correct and booting into System Rescue also can't reach the gateway (185.213.19.1, as the box is a .19.xx address, although for a laugh it also can't see .18.1).
I'm pretty sure it's not an OS config (especially given that System Rescue test) and even your AI support bot thinks "the possibility of an issue at the virtualization level on the host node NYCB045" - that ticket has sat awaiting technical review all month, FWIW.
The other box that got a new IP went flawlessly, so it can work even in NY but this one seems especially cursed.
This should be resolved today. I've credited everyone affected in this particular case.
@VirMach I'd like to know the status of the TYOC027 node. It's been down for almost a year. Can the services on this node be transferred to a usable node?
Comments
Magic!
just start going through them, you will find it eventually, its the one that works with your password.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Hello, @VirMach
Today marks six months since SJC went offline. Would you be willing to share any stories, information or future plans regarding SJC with everyone?
May SJC will be reborn soon.
>
I am on the same server node SJCZ012 as you. I am also eagerly awaiting the official virmach announcement.
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
VirMach has disappeared again.
And also @FrankZ
Someone called ?
Is @VirMach back too?
My VPS in NYCB043 is not accessible ever since its IP was changed a month ago. It is up and I can connect via VNC though.
Powerful AMD Ryzen VPS (aff)
Maybe
How is life in Peru these days ?
Difficult.
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
My NY VPS lost connectivity in the Great IP Change too; given we're back to radio silence and ignored tickets, I've just kind of written it off.
Poor Paddington, he must be very angry.
Sounds like it's going the same way as the UK for similar and different reasons
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Sorry to hear that things are so bad. What may be the worst part is when people lose the expectation that things will get better and instead expect it will get worse as time goes on.
Will @virmach save us?
Magic 8 ball says ....
I am at SF again and I miss @uptime
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I've extended service duration by a month since we're still getting this node mentioned. I've already (2-3 weeks ago) resolved the initial problem affecting the node. I saw the reports here and took a look and could not find another issue. I have looked into it again, this time reading and responding to a few tickets and so far I have confirmed it appears that anyone left still having issues on NYCB043 needs to manually configure the networking within their operating system.
I'll update you guys here if I notice anything else. Given everything I have reviewed though, I am fairly confident in this assessment.
One quick way to verify this for yourself so you do not waste a long time fixing the configuration only to find out it was an issue on our end would be to mount an ISO, boot into it, and see if connectivity works there.
I'll give a quick example. Pick System Rescue CD, change boot order to CD ROM, reboot, then type in startx on VNC, open terminal, and add route: ip route add default via 185.213.18.1 as well as your IP address: ip addr add 185.213.18.xx/24 dev ens3 and make sure the link is up (ip link set ens3 up) and then open Chrome or ping 8.8.8.8; if you're able to do that, it means it's most definitely an issue with your operating system's network configuration and that the automatic reconfiguration is not working.
Which node is this on? I vaguely remember I spoke with you some time ago and you must have been on NYCB043, 44, or 45. And I addressed issues with those nodes at that time. So it's highly likely if you are still facing an issue, my comment above should also be helpful to you.
I'm here, I'm just not in a very "random walls of text" mood. There should have been one comment I made around June 12th which I don't see, so that means I wrote it out and didn't click post or though I did. That was in response to msatt and someone else. I definitely saw the comment about Amazon pay being broken after that, I saw the comment about LAX1Z020 being down, about Oklahoma. I saw Brayvin's comment asking about webhosting and did not have time to look into that (and saw Anthony's joke.) I saw tulipyun's 6 month anniversary post about SJC and the few comments after it and it's been kind of quiet other than that.
I will admit though I did not see your comment and the ones after it (so I've 100% been gone from LES around June 22nd to today.) I just haven't had time this past week to check.
My next reply will likely be about San Jose, hopefully this week.
I'm on NYCB045 - and no, the network config is correct and booting into System Rescue also can't reach the gateway (185.213.19.1, as the box is a .19.xx address, although for a laugh it also can't see .18.1).
I'm pretty sure it's not an OS config (especially given that System Rescue test) and even your AI support bot thinks "the possibility of an issue at the virtualization level on the host node NYCB045" - that ticket has sat awaiting technical review all month, FWIW.
The other box that got a new IP went flawlessly, so it can work even in NY but this one seems especially cursed.
I also wish I could ping the gateway on one of my servers, but it does not worky.
(-:
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
This should be resolved today. I've credited everyone affected in this particular case.
my free4Life tokyo VPS is still working strong. the node is idling too much!
https://browser.geekbench.com/v4/cpu/19747095
the network speeds have improved too
I bench YABS 24/7/365 unless it's a leap year.
@VirMach, Is this "Migration queued" script even working? I've run it for 10 hours, nothing, just spins.
@VirMach I'd like to know the status of the TYOC027 node. It's been down for almost a year. Can the services on this node be transferred to a usable node?
@VirMach Is there any event on July 4th?
Anyone else at SF wanna meet for a coffee?
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
@FAT32 we have followed you to LES.
If you wanna travel a tad bit to the East, say 3000 or so miles, I can meet you there...
Coffee and craft beer 🍺