Troubleshooting Node

Halaman ini buat admin yang ngurus infrastruktur AryaPanel. Kalau lo user biasa, skip ke Troubleshooting Server.

Node status "Offline"

Gejala

Di menu Admin → Nodes, node muncul dengan indikator merah / offline.

Cek 1: Wings service jalan?

SSH ke node, jalanin:

sudo systemctl status wings

Kalau inactive atau failed:

sudo systemctl start wings
sudo journalctl -u wings -n 100 --no-pager

Baca log 100 baris terakhir. Cari ERROR atau panic.

Cek 2: Konfigurasi Wings valid?

sudo wings --debug

Kalau ada error unable to load configuration, cek /etc/pterodactyl/config.yml. Jalanin ulang Configuration Command dari menu Node → tab Configuration.

Cek 3: Konektivitas panel ↔ node

Dari node, tes ping ke panel:

curl -I https://panel.aryapanel.xyz

Harus 200 OK. Kalau timeout:

• Firewall blocking?
• DNS resolve bener?

Cek 4: SSL sertifikat expired?

sudo openssl x509 -in /etc/letsencrypt/live/node1.aryapanel.xyz/fullchain.pem -noout -dates

Kalau expired:

sudo certbot renew
sudo systemctl restart wings

Server stuck di "Installing"

Gejala

Bikin server baru → progress bar Installing gak progress selama > 10 menit.

Solusi

1. Cek log installer di node:

sudo docker logs $(sudo docker ps -a --filter "name=install" --latest -q)

2. Kemungkinan penyebab:

• Egg install script bermasalah (cek script di panel admin)
• Node gak bisa akses URL download (firewall, DNS)
• Disk space penuh — df -h
• Docker image gagal pull — docker pull ghcr.io/pterodactyl/yolks:java_17

3. Force cancel dan retry:

• Admin → Server → Force Reinstall
• Atau hapus server, bikin ulang

Wings sering crash

Gejala

Wings running tapi restart terus-terusan.

Diagnosis

sudo journalctl -u wings --since "1 hour ago"

Cari pola: apakah crash setelah operasi tertentu (backup, install, resize)?

Kemungkinan

• Memori habis di host node — cek free -h, tambah RAM atau kurangi over-allocation.
• Docker daemon issue — sudo systemctl restart docker, terus restart wings.
• Corrupted database SQLite Wings — di /var/lib/pterodactyl/, backup dulu, restart Wings, kalau parah restore dari snapshot.

Server tidak bisa start di node baru

Gejala

Provision berhasil, tapi start server → langsung offline.

Diagnosis

1. Docker jalan?

sudo systemctl status docker

2. Image tersedia?

sudo docker images | grep yolks

Kalau kosong, pull manual:

sudo docker pull ghcr.io/pterodactyl/yolks:java_17

3. Port bentrok?

sudo ss -tlnp | grep :25565

Kalau port dipake proses lain, ganti port server atau kill proses.

Backup gagal di sisi node

Gejala

User bikin backup → gagal, log panel gak jelas.

Diagnosis di node

sudo tail -f /var/log/pterodactyl/wings.log

Coba trigger backup lagi, watch log real-time.

Kemungkinan

• Storage backup penuh — cek df -h /var/lib/pterodactyl/backups
• Permission salah — pastikan folder owned by pterodactyl:pterodactyl
• File yang di-backup lock — biasanya database, konfigur backup buat skip

SFTP tidak bisa connect

Gejala

User dapet error connection refused / auth failed.

Cek

1. Port SFTP terbuka? Default 2022. Cek di firewall node dan cloud provider.

sudo ufw status
sudo ss -tlnp | grep 2022

2. Wings jalan? — SFTP handled by Wings, bukan OpenSSH.

3. Log SFTP:

sudo journalctl -u wings | grep -i sftp

Update Wings

Kalau Wings ada update, cara aman:

sudo systemctl stop wings
sudo curl -L -o /usr/local/bin/wings "https://github.com/pterodactyl/wings/releases/latest/download/wings_linux_amd64"
sudo chmod u+x /usr/local/bin/wings
sudo systemctl start wings

Cek versi:

wings --version

Update di jam sepi

Update Wings menyebabkan semua server di node itu restart. Jadwal di jam sepi user.

Node kepanjangan idle → koneksi drop

Gejala

Node online tapi actions (start/stop server) lambat responnya.

Solusi

• Naikin keepalive di Nginx config panel
• Cek network latency antara panel ↔ node — kalau > 200ms konsisten, mungkin perlu pindah datacenter

Pantau kesehatan node

Setup monitoring dasar:

• Netdata — real-time metrics gratis
• Uptime Kuma — ping monitor, alert Discord/Telegram
• Grafana + Prometheus — untuk fleet besar

Kontak eskalasi

Kalau semua di atas gagal:

1. Backup config: /etc/pterodactyl/config.yml
2. Screenshot log terakhir
3. Hubungi upstream (kalau pake Pterodactyl community support) atau developer tim internal