Coming Soon

Provider troubleshooting guide will be available soon

We're working hard to bring you this documentation. In the meantime, check out our overview or contact us if you need immediate assistance.

Provider Troubleshooting Guide BETA

Step-by-step solutions for common provider issues and error messages.

Troubleshooting Overview

This guide provides detailed troubleshooting steps for the most common issues providers encounter. Each section includes symptoms, diagnostic commands, and proven solutions. For urgent issues, contact provider support at provider-support@slyd.com or use the dashboard chat.

Common Issues

Connection Issues Performance Problems Instance Failures Storage Problems Payment Issues Error Codes

Connection Issues

Provider Cannot Connect to SLYD Network

Symptoms:

Provider service shows "disconnected" status
Cannot reach api.slyd.com
Authentication failures in logs

Diagnostic Steps:

# Check service status
sudo systemctl status slyd-provider

# Test network connectivity
curl -v https://api.slyd.com/health

# Check DNS resolution
nslookup api.slyd.com

# Verify firewall rules
sudo ufw status verbose

# Check provider logs
sudo journalctl -u slyd-provider -n 100

Solutions:

Fix DNS Issues:

# Add reliable DNS servers
echo "nameserver 8.8.8.8" | sudo tee -a /etc/resolv.conf
echo "nameserver 1.1.1.1" | sudo tee -a /etc/resolv.conf

Check Provider Key:

# Verify provider key
sudo cat /etc/slyd/provider.conf | grep key

# Re-register if needed
sudo slyd-provider register --key YOUR_PROVIDER_KEY

Fix Firewall Rules:

# Allow outbound HTTPS
sudo ufw allow out 443/tcp

# Restart provider service
sudo systemctl restart slyd-provider

Instances Cannot Access Internet

Symptoms:

Instances show "No internet connection"
Cannot reach external websites from instances
DNS lookups fail inside containers

Diagnostic Steps:

# Check NAT rules
sudo iptables -t nat -L -n -v

# Verify bridge configuration
ip addr show lxdbr0

# Test from inside container
lxc exec instance-name -- ping 8.8.8.8
lxc exec instance-name -- nslookup google.com

Solutions:

Fix IP Forwarding:

# Enable IP forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward

# Make permanent
echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf
sysctl -p

Rebuild NAT Rules:

# Restart LXD to rebuild rules
sudo systemctl restart lxd
sudo systemctl restart slyd-provider

Performance Problems

High CPU Usage / System Slow

Symptoms:

System load average above CPU count
Instances reporting poor performance
High CPU wait time

Diagnostic Steps:

# Check system load
uptime
top -b -n 1

# Identify high CPU processes
ps aux --sort=-%cpu | head

# Check instance resource usage
slyd-provider instances stats --all

# Monitor CPU frequency
watch -n 1 "grep MHz /proc/cpuinfo"

Solutions:

Fix CPU Governor:

# Set performance mode
for gov in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
    echo performance > $gov
done

Reduce Overcommit:

# Lower CPU overcommit ratio
slyd-provider config set cpu.overcommit 1.2

# Restart to apply changes
sudo systemctl restart slyd-provider

Memory Pressure / OOM Kills

Symptoms:

Out of Memory (OOM) kills in logs
High swap usage
System becoming unresponsive

Diagnostic Steps:

# Check memory usage
free -h
vmstat 1 5

# View OOM kills
dmesg | grep -i "killed process"

# Check memory limits
slyd-provider resources memory --detailed

Solutions:

Adjust Memory Limits:

# Reduce available memory
slyd-provider resources set memory 90%

# Enable memory balloon
slyd-provider config set memory.balloon true

Configure Swap:

# Add swap file
sudo fallocate -l 8G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

Instance Failures

Instances Failing to Start

Symptoms:

Instance stuck in "Starting" state
Error messages about resource allocation
Container creation failures

Diagnostic Steps:

# Check instance logs
slyd-provider instances logs INSTANCE_ID

# View LXD logs
sudo journalctl -u lxd -n 50

# Check available resources
slyd-provider resources available

# List failed instances
lxc list --format json | jq '.[] | select(.status != "Running")'

Solutions:

Clear Failed Instances:

# Remove stuck instances
slyd-provider instances cleanup --failed

# Reset LXD if needed
sudo lxd init --auto

Fix Storage Pool:

# Check storage pool
lxc storage info default

# Increase storage if full
slyd-provider storage expand /dev/sdc

Storage Problems

Storage Pool Full

Symptoms:

Cannot create new instances
"No space left on device" errors
Storage usage at 100%

Diagnostic Steps:

# Check disk usage
df -h
du -sh /var/lib/slyd/*

# View storage pools
lxc storage list
lxc storage info default

# Find large files
find /var/lib/slyd -type f -size +1G -exec ls -lh {} \;

Solutions:

Clean Up Storage:

# Remove old instance data
slyd-provider storage clean --older-than 7d

# Clear image cache
lxc image list | grep -v ALIAS | awk '{print $2}' | xargs -n1 lxc image delete

# Remove unused volumes
lxc storage volume list default | grep -v used | xargs -n1 lxc storage volume delete default

Add Storage:

# Add new disk to pool
slyd-provider storage add /dev/sdd

# Or expand existing filesystem
sudo resize2fs /dev/sdc1

Payment Issues

Missing or Delayed Payments

Symptoms:

Payment not received by expected date
Earnings not showing in dashboard
Payment method errors

Solutions:

Verify Payment Setup:

Check payment method is configured correctly
Ensure minimum payout threshold is met ($100)
Verify tax information is complete

Contact Support:

Email provider-payments@slyd.com with:

Provider ID
Expected payment amount
Payment method details

Common Error Codes

Provider Service Error Codes

Error Code	Description	Solution
`PRV-001`	Invalid provider key	Re-register with correct key
`PRV-002`	Network unreachable	Check internet connection and firewall
`PRV-003`	Insufficient resources	Free up resources or reduce allocation
`PRV-004`	Storage pool error	Check storage configuration
`PRV-005`	LXD not responding	Restart LXD service

Instance Error Codes

Error Code	Description	Solution
`INS-001`	Container creation failed	Check LXD logs and storage
`INS-002`	Network allocation failed	Restart network service
`INS-003`	Resource limits exceeded	Adjust resource allocation
`INS-004`	Image download failed	Check network and retry
`INS-005`	Instance timeout	Increase timeout or check performance

Emergency Support

Critical Infrastructure Issues

For urgent issues affecting multiple instances or complete outages:

Email: provider-emergency@slyd.com
Dashboard: Use the "Critical Issue" button
Response Time: Within 30 minutes for critical issues

Include your Provider ID, affected server details, and impact scope.

Diagnostic Tools

Run Full System Diagnostic

Comprehensive System Check

# Run SLYD diagnostic tool
sudo slyd-provider diagnose --full

# Generate support bundle
sudo slyd-provider support-bundle --output /tmp/support.tar.gz

# Test all components
sudo slyd-provider test all

The diagnostic tool will check all components and generate a report that can be shared with support for faster issue resolution.