Forum

Hello,

We have checked your server (GCP Taipei 2C 2GB), and K3s is actually running normally (status active, node Ready). The server just started about 2 minutes ago, and the Zeabur system components are still being deployed; it will take a few minutes for everything to be ready. Please wait a moment, and the K3s offline status on the Dashboard should automatically update to normal.

However, a reminder: your server only has 2GB of RAM, and the currently available memory is about 1.2GB. K3s and the Zeabur system components themselves require about 1-1.5GB, leaving very limited memory for your services. If you plan to deploy OpenClaw or other resource-intensive services, we recommend upgrading to at least 4GB of RAM, otherwise, K3s may crash due to insufficient memory.

If it still shows as offline after waiting a few minutes, please let us know.

K3s Offline

Your server's K3s cluster is currently unreachable. Here are some common reasons:

• Resource usage is near the limit — Try restarting the machine or stopping some services.
• Firewall is blocking port 6443 — Please check your firewall and port settings.
• K3s service has stopped — Try restarting K3s on the server.

If resources are insufficient, you can try upgrading your server specifications, or restart the server to reboot K3s and all services.

Just typing won't solve the problem.

1 server requires attention

CTCPA_Server

• Unable to connect

Recommended action: Check if the Zeabur System is operating normally, or verify firewall and port settings.

I have double-checked, and I apologize that my previous response was not accurate. Here is the actual situation:

Your server CTCPA_Server has restarted 9 times in the last 30 minutes (from 09:29 to 09:55, restarting almost every 2-3 minutes). This restart loop is because 2 GB of RAM is insufficient to complete the initialization of Zeabur system components—the system components hit OOM during the bootstrap process, the kernel kills the process, triggering a restart, and it hits the same limit upon the next boot.

Currently on the server:

• K3s itself is running, but the Zeabur system components (ingress-controller, nats, zeabur-dns, zeabur-log-api, etc.) have not started successfully at all, which is why the Dashboard continues to show K3s as offline.
• This is not an issue that will resolve by waiting—as long as the RAM remains at 2GB, every bootstrap will hit OOM again.

Solution: You need to upgrade the RAM to at least 4GB. Please go to Dashboard → Servers → CTCPA_Server → Resize and select a specification of 4GB or more. Once the upgrade is complete, the system components will have enough memory to finish bootstrapping, and the K3s offline status on the Dashboard will automatically disappear.

I apologize again for the previous response; this assessment is supported by complete data.

I've started other machines, this can be closed.

Alright, this case is now closed. If you encounter any issues with the new machine, please feel free to open a new ticket at any time.