@Brayvin said: @VirMach ... still waiting... was not addressed above:
Shared Unmetered Hosting on lax2z017.virm.ac is 69 days down beginning 2/12/26, 5:36 PM
I've seen your comments and almost replied to them a few times but it just takes so long to work on that server right now relative to everything else, and when I do, it just ends up getting worse.
For example, the other day when you made this comment I spent a solid 6 hours on it going through and manually fixing and checking every little thing cPanel broke when it ran an autoupdate. Previously, at least websites and everything not directly related to cPanel functioned. I got cPanel back up after manually piecing everything together to push it through small updates at a time, combed through everything, double checked, everything was going fine. I wake back up a few hours later and just cPanel running overloaded/crashed the server. Only other solution at this point is to just set things up on a new server, and migrate customers over. The server itself is relatively fine (as proven by it being more stable with cPanel having broken itself, definitely lasted way longer than like 4 hours.)
I wanted to avoid making it worse, unfortunately that has happened, so I'll try to at least get it to a semi-functional state again and just make sure I get through all the other issues so I can focus on it again, maybe finally do proper migration over to OKC.
@Virmach : I read a couple of things out of this:
1. It apparently is felt the web host is/was working.
2. Worse must be your side; from my side, its the same as it has been for ages (domain pointing at worthless).
3. I'm thankful you have spent time on it; I am also sorry that it is such a hassle.
4. Migration is on the table.
I contest that the web service "is working" on the grounds that my site has been inaccessible for longer than the above implies. Every time the configuration bounces, the monitoring service timer resets. There is no web site at the IP address the domain is pointing to. After my original domain was lost by a hiccup in the Virmach system that was supposed to renew it, I have to maintain the replacement domain myself; without a control panel or webmail, I don't know how to discern the IP it should point at. Perhaps it is "working", but without an IP to point a domain at and confirm, it is actually "not working" from anyone else's perspective.
I am ready for a migration off this horrible system if I have any input on that. That system was the MX for my domain. Webmail has been down. Ok, its on me for using a cheap host as a domain MX, but I'm not sure how this is categorized as being "relatively fine", except perhaps that its not catching on fire...
@NodeSuper said: @VirMach
Ticket #339466
Thank you very much! My first issue has been resolved, and the ticket has been closed!
As you requested, I have created a new ticket to address the second issue. My Dutch VPS cannot connect to the external network properly. It appears to be functioning normally—I can connect via VNC—but in reality, I cannot ping the server or connect via SSH. I have reinstalled the operating system and tried various solutions via VNC, but none of them have resolved the issue.
Thank you very much
Is this on AMSD018?
My VPS there went offline a bit more than 11 hours ago, not sure if it's just mine or the entire host?
@NodeSuper said: @VirMach
Ticket #339466
Thank you very much! My first issue has been resolved, and the ticket has been closed!
As you requested, I have created a new ticket to address the second issue. My Dutch VPS cannot connect to the external network properly. It appears to be functioning normally—I can connect via VNC—but in reality, I cannot ping the server or connect via SSH. I have reinstalled the operating system and tried various solutions via VNC, but none of them have resolved the issue.
Thank you very much
Is this on AMSD018?
My VPS there went offline a bit more than 11 hours ago, not sure if it's just mine or the entire host?
Try now, it was a bug. Seems to have affected a few VMs. If it keeps happening let me kno.
IP changes are going to go out kind of last minute. Announcements were delayed in NYC, and some bugs had to be worked out with the new system (it worked in testing, the bugs were in specific batch operations when multiple subnets and VLAN changes were involved.) Nothing major, it could've technically worked, but the whole point of the new system was for it to be silky smooth at every step.
Even with the short notice these changes should be as painless as possible.
You receive communication with exact IP before and after, and risk of it changing around is much lower since it's mapped out
Everything is updated, including on WHMCS, at every step
The system shows you/verifies it's happening, an active maintenance window is opened. This means you see it on the service page when visited, and you can also see the IP history once it's done. Exact time and date of scheduled changes are available (although I limited it to not include every single time for every single thing to avoid information overload.)
All communication is tracked, everything has an individual checklist on our end and if anything goes wrong for any individual service it's immediately apparent with fixes possible at every step of failure.
"Early Access" feature (when possible) where you can request the system bump up the times for your change. This can/should be able to occur at any step, so even if it's partially completed you can race to the finish sooner when you have time to check it. When this option is used, it pipes to the same system so it's visible on our end that you have it requested and whether it was properly fulfilled.
Everything is validated across multiple systems and also validated for human error before the batch can be submitted/proceed. Like to a crazy level, we keep track of what subnet is supposed to be on what node on our end, not just relying on SolusVM. Failsafes to avoid any weird cycling back to old IP address, keeps track of what the old one is supposed to be, new one, what the current main IP address is on the service.
Reconfigures happen in their own queue and staggered properly, whether or not your service pinged beforehand is saved, and checked several times afterward and if it fails it raises a flag as well. Reconfigure time is included in the total estimated time for all tasks to run properly and included in the maintenance window opened (also viewable under scheduled maintenance on status page.)
Since it's sent to status page, this means customers can add a comment to let us know something is wrong. I don't know how useful this will be if customers start using it to just say it's down (because it's filtered through AI, so it'll just let us know people are incorrectly reporting scheduled maintenance as an outage) but it would definitely potentially be helpful if people actually let us know something is wrong with the maintenance in the comment they add. (Unfortunately I don't think it'll be that helpful based on the report I just received, where someone put in the comment that they want to renew their VPS and then they copy/pasted their entire service details from the service page.)
Tracking which subnet is a replacement, and sorting them differently in our view, keeping track of which ones are being phased out. The system gives us "advisories" based on each step, each situation, just in case I'm stupid and forget something such as "Make sure 85.8.149.0/24 is routed to LAXA005 on the switch." (This is a real advisory note that comes up.)
More improvements will be made, and I'm sure some other bugs introduced/found.
We also have automated helper scripts that makes sure everything is good on the node to avoid human error, and export system to be able to export everything exactly as it is on the system to proceed directly through CLI if necessary.
Other features that are effectively ready but not yet used, related to this:
Auto conflict resolution on IP addresses. The system constantly detects if a virtual server has an IP address it's not supposed to have and can automatically clean it up. Right now it's left on manual mode until we get more data on weird outliers and such.
IP changes returning (paid changes) but the same system will also be used for enabling free changes under certain circumstances. Neither is enabled right now, one of them is just a setting checkbox I need to enable and it's ready to go.
Migrations. These will return in general and in many other ways, but in relation to IP addresses, we currently have it coded out but not finalized/tested to have it migrate customers in emergency situations where IP addresses are exhausted for the change. Right now we're just focusing on making sure it has a low chance of spilling over. Later on it'll be made more seamless but right now it's very much an "emergency" feature where thee alternative is no IP. This means it could mess with the timeline and such.
Our own entire communication system. It's built where it can be used for more than just IP renumbering, but in the future when it's enabled, it'll send notifications on WHMCS, have option for you to customize what type of emails you get (like you can choose to skip out on receiving renumbering emails if you really want.) And later on text message support for certain countries. This also gives us more flexibility for other types of notifications, allowing customers to be able to basically be in a group chat (one way to us with mass replies from us) chained in the same notification/communication. A lot more but I'm getting carried away and going past it being relevant to IP renumbering.
We'll be able to see what's going on in terms of changes in our switch port mapping/server cabinet view tools. Yes the system keeps track of what switches exist, what subnets are for which, what ASN, what subnets have missing VLANs, what switches are in what location groups and associated with what servers, whether it's in trunk mode, what replacement subnets are on our own ASN. Oh wait all these features currently exist the only thing note used yet is more clearly labeling the replacement block on the cabinet view.
Probably a lot more, I haven't talked about most of this, I'll maybe update you guys later once everything is rock solid and closer to how we want it.
These systems are built in a way where they enable us to do a crazy amount of things we couldn't do easily in the past without building an entire separate module. So if you guys have any feature request (other than IPv6) let me know and it might be easier than it would normally seem. It's actually a series of sub-systems, they all correctly communicate to eachother in a way where we don't have to redo a specific function that can get used across many tasks. Here, I just thought of one that's theoretically possible with this system, you could say "I want a feature where I can set a list of locations and if any scheduled maintenance is upcoming for my service that is longer than 30 minutes, I want it to just move my service to another location, but only after notifying me and scheduling it 24 hours in advance. If it's not physically possible, I want you to fire up a secondary service for me ahead of time and copy over my data from thee existing service to it, and only notify me if the data copying over is successful."
Once the bigger things I have planned get finalized, it's going to be pretty awesome.
@bakageta said:
My in-laws are in town, so I get to post my suegra's flan!
I can never think about flan anymore without @imok being referenced in my brain and I think about flan way more than you guys would imagine. And then I remember how his server in Oklahoma still doesn't have a subnet. And then I still don't fix it.
What was I talking about again? Oh yeah I can't wait for everything to fail spectacularly in ways I didn't imagine were possible, after planning it through to this level for the IP changes.
@VirMach said: "Early Access" feature (when possible) where you can request the system bump up the times for your change. This can/should be able to occur at any step, so even if it's partially completed you can race to the finish sooner when you have time to check it. When this option is used, it pipes to the same system so it's visible on our end that you have it requested and whether it was properly fulfilled.
We pressed this button.
It gave new IPv4 in SolusVM.
However, the new IPv4 is unreachable via ping.
When accessed through VNC, the machine receives new IPv4 via DHCP, but it cannot reach the gateway via ping.
@yoursunny said: We pressed this button.
It gave new IPv4 in SolusVM.
However, the new IPv4 is unreachable via ping.
When accessed through VNC, the machine receives new IPv4 via DHCP, but it cannot reach the gateway via ping.
Working on it, sorry for the wait. Another bug is reconfigures aren't going through when early button is used, related to the staggering feature I mentioned.
Only affects some servers that are also switching VLANs for the bridge issue. The IP addresses work, bridge doesn't.
@NodeSuper said: @VirMach
Ticket #339466
Thank you very much! My first issue has been resolved, and the ticket has been closed!
As you requested, I have created a new ticket to address the second issue. My Dutch VPS cannot connect to the external network properly. It appears to be functioning normally—I can connect via VNC—but in reality, I cannot ping the server or connect via SSH. I have reinstalled the operating system and tried various solutions via VNC, but none of them have resolved the issue.
Thank you very much
Is this on AMSD018?
My VPS there went offline a bit more than 11 hours ago, not sure if it's just mine or the entire host?
I'm on: Node ATLZ032 The issue still hasn't been resolved.
@yoursunny said: We pressed this button.
It gave new IPv4 in SolusVM.
However, the new IPv4 is unreachable via ping.
When accessed through VNC, the machine receives new IPv4 via DHCP, but it cannot reach the gateway via ping.
Working on it, sorry for the wait. Another bug is reconfigures aren't going through when early button is used, related to the staggering feature I mentioned.
Only affects some servers that are also switching VLANs for the bridge issue. The IP addresses work, bridge doesn't.
Funny thing is, regardless of whether it takes a while or completes fast fast, as long as you communicate (like you are doing now) people will be a lot happier.
@NodeSuper said: @VirMach
Ticket #339466
Thank you very much! My first issue has been resolved, and the ticket has been closed!
As you requested, I have created a new ticket to address the second issue. My Dutch VPS cannot connect to the external network properly. It appears to be functioning normally—I can connect via VNC—but in reality, I cannot ping the server or connect via SSH. I have reinstalled the operating system and tried various solutions via VNC, but none of them have resolved the issue.
Thank you very much
Is this on AMSD018?
My VPS there went offline a bit more than 11 hours ago, not sure if it's just mine or the entire host?
I'm on: Node ATLZ032 The issue still hasn't been resolved.
I apologize it's dragging out, I'm trying to close out all these issues very soon.
I just realized I don't have a single e-mail about IP address renumbering. I guess I have most of my servers in AMS... and those few left in US of A dodged the bullet. It's strange times for me not being hit by this, it was like a tradition... :-P
@NodeSuper said: @VirMach
Ticket #339466
Thank you very much! My first issue has been resolved, and the ticket has been closed!
As you requested, I have created a new ticket to address the second issue. My Dutch VPS cannot connect to the external network properly. It appears to be functioning normally—I can connect via VNC—but in reality, I cannot ping the server or connect via SSH. I have reinstalled the operating system and tried various solutions via VNC, but none of them have resolved the issue.
Thank you very much
Is this on AMSD018?
My VPS there went offline a bit more than 11 hours ago, not sure if it's just mine or the entire host?
I'm on: Node ATLZ032 The issue still hasn't been resolved.
I apologize it's dragging out, I'm trying to close out all these issues very soon.
Comments
It’s much better now, thanks to @VirMach ’s fix.
Virmach is alive!
@Virmach : I read a couple of things out of this:
1. It apparently is felt the web host is/was working.
2. Worse must be your side; from my side, its the same as it has been for ages (domain pointing at worthless).
3. I'm thankful you have spent time on it; I am also sorry that it is such a hassle.
4. Migration is on the table.
I contest that the web service "is working" on the grounds that my site has been inaccessible for longer than the above implies. Every time the configuration bounces, the monitoring service timer resets. There is no web site at the IP address the domain is pointing to. After my original domain was lost by a hiccup in the Virmach system that was supposed to renew it, I have to maintain the replacement domain myself; without a control panel or webmail, I don't know how to discern the IP it should point at. Perhaps it is "working", but without an IP to point a domain at and confirm, it is actually "not working" from anyone else's perspective.
I am ready for a migration off this horrible system if I have any input on that. That system was the MX for my domain. Webmail has been down. Ok, its on me for using a cheap host as a domain MX, but I'm not sure how this is categorized as being "relatively fine", except perhaps that its not catching on fire...
Is this on AMSD018?
My VPS there went offline a bit more than 11 hours ago, not sure if it's just mine or the entire host?
Try now, it was a bug. Seems to have affected a few VMs. If it keeps happening let me kno.
Yes, I could start it by using On in the panel (not Reset) ... Seems to be online.
Thanks!
@VirMach is now back online, Hooray!
Virmach Deals
My in-laws are in town, so I get to post my suegra's flan!
IP changes are going to go out kind of last minute. Announcements were delayed in NYC, and some bugs had to be worked out with the new system (it worked in testing, the bugs were in specific batch operations when multiple subnets and VLAN changes were involved.) Nothing major, it could've technically worked, but the whole point of the new system was for it to be silky smooth at every step.
Even with the short notice these changes should be as painless as possible.
More improvements will be made, and I'm sure some other bugs introduced/found.
We also have automated helper scripts that makes sure everything is good on the node to avoid human error, and export system to be able to export everything exactly as it is on the system to proceed directly through CLI if necessary.
Other features that are effectively ready but not yet used, related to this:
These systems are built in a way where they enable us to do a crazy amount of things we couldn't do easily in the past without building an entire separate module. So if you guys have any feature request (other than IPv6) let me know and it might be easier than it would normally seem. It's actually a series of sub-systems, they all correctly communicate to eachother in a way where we don't have to redo a specific function that can get used across many tasks. Here, I just thought of one that's theoretically possible with this system, you could say "I want a feature where I can set a list of locations and if any scheduled maintenance is upcoming for my service that is longer than 30 minutes, I want it to just move my service to another location, but only after notifying me and scheduling it 24 hours in advance. If it's not physically possible, I want you to fire up a secondary service for me ahead of time and copy over my data from thee existing service to it, and only notify me if the data copying over is successful."
Once the bigger things I have planned get finalized, it's going to be pretty awesome.
I can never think about flan anymore without @imok being referenced in my brain and I think about flan way more than you guys would imagine. And then I remember how his server in Oklahoma still doesn't have a subnet. And then I still don't fix it.
What was I talking about again? Oh yeah I can't wait for everything to fail spectacularly in ways I didn't imagine were possible, after planning it through to this level for the IP changes.
Apparently his walls of text too. I think it's because I'm genuinely excited I finally pushed an entire project through.
Wall of text VirMach is back.
TRUE VIRMACH IS BACK
REJOICE.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
IP-less VNC-only machine for learning purposes
best of "yoursunny lore" by Google AI 🤣 affbrr
@VirMach, any news on TYOC038 from San Jose? It says maintenance, but are you actively working on it?
There is no mentioin about Ram,Space, nothing.
@VirMach Does the new IP actually work?
I can’t even connect in recovery mode.
We pressed this button.
It gave new IPv4 in SolusVM.
However, the new IPv4 is unreachable via ping.
When accessed through VNC, the machine receives new IPv4 via DHCP, but it cannot reach the gateway via ping.
best of "yoursunny lore" by Google AI 🤣 affbrr
Working on it, sorry for the wait. Another bug is reconfigures aren't going through when early button is used, related to the staggering feature I mentioned.
Only affects some servers that are also switching VLANs for the bridge issue. The IP addresses work, bridge doesn't.
Tomorrow is flan day!
I'm on: Node ATLZ032 The issue still hasn't been resolved.
Cheap VPS Deals List ：www.cheapvpsbox.com
any update from OKC? still waiting /29 block since 2025.07
This did not go well.
Funny thing is, regardless of whether it takes a while or completes fast fast, as long as you communicate (like you are doing now) people will be a lot happier.
Glad to see you are back @VirMach
Services extended by a year as long as we can all pretend it's still 2025.
Except for @Kris, I don't know how I feel about extending it into near the end of 2028, feels weird. We'll figure something out.
I apologize it's dragging out, I'm trying to close out all these issues very soon.
The new IP seems to be working fine!
Thanks @Virmach, hope you get a good night’s sleep
Holy fucking wall of text.
"It's a hard life- to be a stick insect." - Karl Pilkington
The writing capabilities of Virmach should be my goal.
I just realized I don't have a single e-mail about IP address renumbering. I guess I have most of my servers in AMS... and those few left in US of A dodged the bullet. It's strange times for me not being hit by this, it was like a tradition... :-P
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Sigh
I feel left out with them extensions
Oh no.
I got distracted with a terrible movie and this happened
Only 2 and a half portions. This is a bad day.
looks good anyway
Virmach Deals
new i.p doesn't even ping, dead.