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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Is it possible to set up more than one ssh-key in the control panel ?
Technically its designed for infinite SSH keys per user, but right now you can only add/update one.
So yea would be possible.
34f3-5f8d-afec-134e
1f38-9ded-651e-8003
962f-fb54-c9a4-8969
I been on LET for 2 years, and I just found this
962f-fb54-c9a4-8969
Hello.
I have detected a Tokyo Equinix server down.
What would have happened?
Hi,
I don't know, it went down 30 minutes ago.
If its longer out, I am gonna ticket them.
Email from WH.
We have sent you this email to inform you of a recent downtime that we have had in one of our Japan nodes (TYO-K3).
Our monitoring services detected connectivity issue at 2025-12-06 04:21:09 UTC. We started checking and trying to resolve the issue immediately and at 05:11:49 UTC the downtime resolved.
Unfortunately, we had to reboot the affected servers to restore the connectivity which we apologize greatly.
We are still investigating to find the main cause of the issue and prevent future interruptions.
I have confirmed the recovery of this server. Thank you for your response.
f00f-4f10-3694-b315
Islamabad has gotten a new subnet, the old subnet will stop functioning on 18 December 2025.
The new IP has been already added in the Panel, I will reconfigure the network on the weekend to run dual stack if possible, so you have time until the 18th to switch.
Regarding NZ, currently we got a software bug, that brings the primary interface down, at random times.
I still have no idea whats causing it, I duct taped it right now with a cronjob, to prevent bigger downtimes.
Still looking into it.
67c2-3ce1-f223-673c
thankyou in advance
b8c5-748f-6ebd-a36f
Done.
Maintenance announcement
Sandefjord and Helsinki gonna get migrated to Incus next Friday.
Expect up to 60 minutes of downtime, should be way shorter but will see.
I am targeting 21:00 CET, subject to change though.
Is SG node having some trouble? Can't deploy to SG, other locations are fine.
Looks like it got "stuck" at creating network? Then "Deployment failed Deployment of the container failed, please try again."
Any spare stock in Auckland?
How many hours ago? The Tokyo Equinix server is also losing its response.
We don't provide any SLA, if you are unhappy, you are free to buy you a server.
I will look into it, same reason, Auckland is OOS because the node is currently unstable.
SG was affected by the same bug that triggered the network outages in NZ and JP.
I disabled new deployments on SG, NZ and JP for now.
Something causes some kind of desync with network dispatcher which than for some reason shuts down the primary interface. Why now? I have no idea.
Prob. its a recent update, if that keeps killing the network, deplyoment will be disabled for all nodes, no ETA.
Oh, I also use NanoKVM and so on, so I don't care about that.
However, this time I waited for several hours for the possibility of automatic recovery.
Again, we don't offer any SLA, if you need HA or an SLA, this is the wrong service for you.
This bug doesn't recover on its own, once trigger it takes down the entire node.
Expect a few reboots, I found a potential fix for this.
Should be fixed on all nodes, except 2.
Lemme know if you have any issues.
Hello @Neoon , I was DM you about quota thing, if you have time please check the DM, thank you so much.
I am aware that you send me a DM, but as you can tell, I have been quite busy, fixing the issues.
Accepting new account's wasn't a priority, tagging me doesn't make it faster.
Melbourne appears to have some bug where apt stucks at "Processing triggers for shared-mime-info". This is on Debian 13 image, no issues at other locations. Server doesn't appear to be hung, can still type into the console.
Auckland appears to have broken port forwarding on ipv4. I don't have access to ipv6 at the moment to test that, but SSH doesn't work on default port or any other ports assigned. This is on Debian 13 image. SSH works fine at other locations once the package is installed.
I have absolutely no issue with the Alpine image @ Melbourne!