Lightsail Seoul server K3s offline, unable to restart service

Waiting for author response

Oobededom2007-cloudFREE23h ago

Hello, my Lightsail Seoul 2C 2GB server (server-69f73a537288e85b945bbd9e, IP 13.125.136.222) currently shows K3s as offline, and the website twfirelaw.tw is unreachable (ERR_TIMED_OUT).

Clicking "Restart current version" and "Redeploy" from the Dashboard both result in an Internal Server Error / Please try again later (see error message field).

Please assist with:

Restarting the K3s cluster or VM
Confirming service recovery

Service name: firelaw-xai Project: untitled (project-69f7764...)

Thank you!

1 Reply

BCBohan ChenEMPLOYEE16h ago

Hello, the server restart was completed today at 03:00 UTC. K3s is currently running normally, all services have been restored, and twfirelaw.tw is accessible.

After checking the K3s logs, the failure occurred at 5/21 13:41 UTC (approx. 21:41 Taiwan time). The internal K3s database (kine) experienced severe SQL query latency (8-27 seconds per query), causing the API server to time out, node status updates to fail, and eventually leading to K3s becoming completely unresponsive. The server recovered after the restart at 5/22 03:00 UTC, with a total downtime of approximately 13 hours.

Your server specification is 2C 2GB, which is tight for K3s plus your services. It is prone to such issues under high load. If you encounter this frequently in the future, I recommend upgrading to the 2C 4GB plan for better stability.

Add a Reply

Forum

1 Reply