Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › General
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

microLXC Public Test

1…484950515254»

Comments

  • NeoonNeoon Community Contributor, Veteran

    @zejjnt said:
    @neeoon Hey, stupid question perhaps but rule 2.III for NAT KVM says "attempt to decompile or reverse engineer any software contained on NanoKVM's website" - that just means that I'm not allowed to touch your software - ie. if I decompile some FOSS stuff that is not a rule violation? Just want to be 100% sure :)

    EDIT: Oh, f3b051a038665b397caf89c3238860a8a5b941b2. I want to play around with customizing the Debian kernel with zero risk of losing data from any of my prod machines

    wrong thread?

  • zejjntzejjnt Member

    @Neoon said:

    @zejjnt said:
    @neeoon Hey, stupid question perhaps but rule 2.III for NAT KVM says "attempt to decompile or reverse engineer any software contained on NanoKVM's website" - that just means that I'm not allowed to touch your software - ie. if I decompile some FOSS stuff that is not a rule violation? Just want to be 100% sure :)

    EDIT: Oh, f3b051a038665b397caf89c3238860a8a5b941b2. I want to play around with customizing the Debian kernel with zero risk of losing data from any of my prod machines

    wrong thread?

    all work no pause makes brain BSOD :(

  • NeoonNeoon Community Contributor, Veteran

    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    Thanked by 2Starnberg youandri
  • youandriyouandri Member

    @Neoon said:
    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    It's okay. Can we delete the vm on panel? because it's allocated quota. So we can try another location.

    Thank you. :)

  • jcn50jcn50 Member
    edited May 23

    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

  • NeoonNeoon Community Contributor, Veteran
    edited May 23

    @youandri said:

    @Neoon said:
    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    It's okay. Can we delete the vm on panel? because it's allocated quota. So we can try another location.

    Thank you. :)

    You can't delete anything when the Node is down.
    Deleting it manually creates desync's, I hate desync's.
    So sadly you have to wait.

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    I check on that in a bit, currently I am too high to do any technical stuff.

    Thanked by 3youandri jcn50 reikuzan
  • youandriyouandri Member

    @Neoon said:

    @youandri said:

    @Neoon said:
    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    It's okay. Can we delete the vm on panel? because it's allocated quota. So we can try another location.

    Thank you. :)

    You can't delete anything when the Node is down.
    Deleting it manually creates desync's, I hate desync's.
    So sadly you have to wait.

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    I check on that in a bit, currently I am too high to do any technical stuff.

    I see. I appreciate it. :)

  • NeoonNeoon Community Contributor, Veteran

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    You can recreate your container.
    I did break something on this node with the images, fixed.

    Thanked by 2jcn50 jwg29859
  • jcn50jcn50 Member

    @Neoon said: You can recreate your container.
    I did break something on this node with the images, fixed.

    Thank you: all resolved!

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    So I got a reply about 14 hours ago, however no resolution yet.
    The VM's remain fucked, since a reboot from the provider.

    Currently I have zero clues to be honest, probably the filesystem got fucked.
    The Reboot broke something.

    Thanked by 2jcn50 Starnberg
  • jwg29859jwg29859 Member

    @Neoon said:

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    You can recreate your container.
    I did break something on this node with the images, fixed.

    Hello @Neoon my server on the node tokyo equinix cannot be managed after a reinstall failure. I got the error message below when I click the Manage button.
    https://microlxc.net/index.php?p=manage&machine=4f08-eb20-d9e8-bb13
    Failed to contact Node, please try again later.
    Could you please take a look at it whenever you are free? Thank you.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:

    @Neoon said:
    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    So I got a reply about 14 hours ago, however no resolution yet.
    The VM's remain fucked, since a reboot from the provider.

    Currently I have zero clues to be honest, probably the filesystem got fucked.
    The Reboot broke something.

    NZ Restored

    Thanked by 2jcn50 youandri
  • NeoonNeoon Community Contributor, Veteran

    @jwg29859 said:

    @Neoon said:

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    You can recreate your container.
    I did break something on this node with the images, fixed.

    Hello @Neoon my server on the node tokyo equinix cannot be managed after a reinstall failure. I got the error message below when I click the Manage button.
    https://microlxc.net/index.php?p=manage&machine=4f08-eb20-d9e8-bb13
    Failed to contact Node, please try again later.
    Could you please take a look at it whenever you are free? Thank you.

    When did you reinstall? I just recently fixed the issue with the templates on the node.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:

    @Neoon said:
    Still no Ticket reply on Johannesburg and New Zealand, neither any ETA.

    So I got a reply about 14 hours ago, however no resolution yet.
    The VM's remain fucked, since a reboot from the provider.

    Currently I have zero clues to be honest, probably the filesystem got fucked.
    The Reboot broke something.

    NZ and SA is restored, thanks to @Zappie

    Thanked by 5SwordfishBE fadedmaple jcn50 Starnberg youandri
  • jwg29859jwg29859 Member

    @Neoon said:

    @jwg29859 said:

    @Neoon said:

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    You can recreate your container.
    I did break something on this node with the images, fixed.

    Hello @Neoon my server on the node tokyo equinix cannot be managed after a reinstall failure. I got the error message below when I click the Manage button.
    https://microlxc.net/index.php?p=manage&machine=4f08-eb20-d9e8-bb13
    Failed to contact Node, please try again later.
    Could you please take a look at it whenever you are free? Thank you.

    When did you reinstall? I just recently fixed the issue with the templates on the node.

    I reinstalled it on the 22nd and got the error "Failed to contact Node". Since @jcn50 reported the issue on this thread, I just follow it. When you confirmed the issue was sorted out, I tried to click on Manage button again but no luck.

  • StarnbergStarnberg Member

    @Neoon said:
    NZ and SA is restored, thanks to @Zappie

    Thanks @Neoon and @Zappie!!

  • NeoonNeoon Community Contributor, Veteran

    @jwg29859 said:

    @Neoon said:

    @jwg29859 said:

    @Neoon said:

    @jcn50 said:
    @Neoon help I got a reinstall failure @ Tokyo Equinix for lxc37cc9fc6 (10.0.12.82) I can't manage it anymore Failed to contact Node, please try again later ; it seems that the problems started from 04/MAY/2026

    You can recreate your container.
    I did break something on this node with the images, fixed.

    Hello @Neoon my server on the node tokyo equinix cannot be managed after a reinstall failure. I got the error message below when I click the Manage button.
    https://microlxc.net/index.php?p=manage&machine=4f08-eb20-d9e8-bb13
    Failed to contact Node, please try again later.
    Could you please take a look at it whenever you are free? Thank you.

    When did you reinstall? I just recently fixed the issue with the templates on the node.

    I reinstalled it on the 22nd and got the error "Failed to contact Node". Since @jcn50 reported the issue on this thread, I just follow it. When you confirmed the issue was sorted out, I tried to click on Manage button again but no luck.

    Nah, you have to reach out to get your container unstuck.
    You can deploy yours again.

    The issue was templates where missing, hence the failed reinstall.
    This doesn't individual containers being stuck though.

    Thanked by 1jwg29859
  • jwg29859jwg29859 Member

    I reinstalled it on the 22nd and got the error "Failed to contact Node". Since @jcn50 reported the issue on this thread, I just follow it. When you confirmed the issue was sorted out, I tried to click on Manage button again but no luck.

    Nah, you have to reach out to get your container unstuck.
    You can deploy yours again.

    The issue was templates where missing, hence the failed reinstall.
    This doesn't individual containers being stuck though.

    My bad. I thought it was a backend error of the microlxc website. Thank you for your help.

  • hormigo97hormigo97 Member

    7b5c-53fe-0997-3209

  • NeoonNeoon Community Contributor, Veteran
    edited June 7

    The frontend currently is sleeping, I forgot to announce the maintenance.
    My bad.

    ​Start Time: Sunday, June 7, 2026, at 20:00 CEST (18:00 UTC)
​End Time: Monday, June 8, 2026, at 06:00 CEST (04:00 UTC)
​Expected Impact: Your VPS services are expected to be offline or unavailable for several hours within this window.

    The Frontend should be back in a few hours.

    Thanked by 1jcn50
  • GanonkGanonk Member

    thankyou

  • NeoonNeoon Community Contributor, Veteran

    Heads up for the India Node.

    A few days ago, I got a email saying WH is gonna discontinue their old IPv4 subnet.
    I just read this email today, I wasn't send to the correct mailbox, my bad.

    Hence we have to change the IPv4 today, since its gonna stop working tomorrow.
    I wish we had more time but seems to be urgent, its just a week.

    New IP is displayed in the Panel, so you can update your DNS.
    Will be swapped out later today.

    Thanked by 1Void
  • daviddavid Member

    @Neoon said:
    Heads up for the India Node.

    A few days ago, I got a email saying WH is gonna discontinue their old IPv4 subnet.
    I just read this email today, I wasn't send to the correct mailbox, my bad.

    Hence we have to change the IPv4 today, since its gonna stop working tomorrow.
    I wish we had more time but seems to be urgent, its just a week.

    New IP is displayed in the Panel, so you can update your DNS.
    Will be swapped out later today.

    I get connection refused on the ssh port for the new IP address (I can still connect on IPv6). I get connection refused on the other ports/services I've got running, also. I tried to reconfigure the networking and rebooted, but it didn't help. Any ideas?

  • NeoonNeoon Community Contributor, Veteran

    @david said:

    @Neoon said:
    Heads up for the India Node.

    A few days ago, I got a email saying WH is gonna discontinue their old IPv4 subnet.
    I just read this email today, I wasn't send to the correct mailbox, my bad.

    Hence we have to change the IPv4 today, since its gonna stop working tomorrow.
    I wish we had more time but seems to be urgent, its just a week.

    New IP is displayed in the Panel, so you can update your DNS.
    Will be swapped out later today.

    I get connection refused on the ssh port for the new IP address (I can still connect on IPv6). I get connection refused on the other ports/services I've got running, also. I tried to reconfigure the networking and rebooted, but it didn't help. Any ideas?

    Something broke last reboot, should be fixed now.
    I did disabled cloud-init however for some reason a new network config was pushed despite that and caused a conflict, so network never fully went up.

    Thanked by 2blanehol david
  • daviddavid Member

    @Neoon said:

    @david said:

    @Neoon said:
    Heads up for the India Node.

    A few days ago, I got a email saying WH is gonna discontinue their old IPv4 subnet.
    I just read this email today, I wasn't send to the correct mailbox, my bad.

    Hence we have to change the IPv4 today, since its gonna stop working tomorrow.
    I wish we had more time but seems to be urgent, its just a week.

    New IP is displayed in the Panel, so you can update your DNS.
    Will be swapped out later today.

    I get connection refused on the ssh port for the new IP address (I can still connect on IPv6). I get connection refused on the other ports/services I've got running, also. I tried to reconfigure the networking and rebooted, but it didn't help. Any ideas?

    Something broke last reboot, should be fixed now.
    I did disabled cloud-init however for some reason a new network config was pushed despite that and caused a conflict, so network never fully went up.

    All good now, thanks.

Sign In or Register to comment.