Перейти к основному содержимому

Connectivity Issues

This guide helps diagnose and resolve common network connectivity problems with Autonomys Network.

Quick Diagnosis​

Check Your Connection Status​

In Space Acres Interface:

  • Look for peer count in the status bar
  • Check sync progress indicator
  • Review any error messages in logs

Healthy indicators:

  • Peer count > 40
  • Steady sync progress
  • No network error messages

Problem indicators:

  • Peer count < 40
  • Stuck sync at specific block

Common Issues and Solutions​

Issue 1: Zero or Very Few Peers​

Symptoms:

  • Peer count stays very low and does not grow to at least 40 peers
  • No sync progress

Step-by-step diagnosis:

# 1. Check if service is running and listening
netstat -tuln | grep -E "30333|30433|30533"
# Expected: Shows LISTEN state on ports

# 2. Test local connectivity
telnet localhost 30333
# Expected: Connected message

# 3. Get your public IP
curl -s https://api.ipify.org
# Or visit whatismyip.com

# 4. Test external connectivity (from another network)
# Have friend run: nc -zv YOUR_PUBLIC_IP 30333
# Or use online port checker

Issue 2: Intermittent Connection Loss​

Symptoms:

  • Peer count fluctuates wildly
  • Frequent reconnections
  • Sporadic farming rewards

Diagnosis and fixes:

# 1. Check network stability
ping -c 100 8.8.8.8 | grep "packet loss"
# Expected: 0% packet loss

# 2. Monitor bandwidth usage
# Linux: iftop or nethogs
# Windows: Resource Monitor
# Look for bandwidth saturation

# 3. Check system resources
# CPU usage
top -p $(pgrep subspace)

# Memory usage
free -h

# Disk I/O
iostat -x 1 10

Common causes:

  • Insufficient bandwidth
  • WiFi instability (use ethernet)
  • System resource exhaustion
  • ISP throttling P2P traffic

Issue 3: Can't Connect to Local Node (CLI)​

Error: "Cannot connect to node RPC at ws://..."

# 1. Verify node is running
ps aux | grep subspace-node

# 2. Check RPC is enabled
grep "rpc" /path/to/node/startup/command

# 3. Test RPC endpoint
curl -H "Content-Type: application/json" \
  -d '{"id":1, "jsonrpc":"2.0", "method": "system_health"}' \
  http://127.0.0.1:9944

# Expected: JSON response with result

Issue 4: Slow Synchronization​

Symptoms:

  • Sync speed < 10 blocks/second
  • Estimated time keeps increasing
  • High network latency

Optimization steps:

# 1. Check latency to network
ping 1.1.1.1
# Good: < 100ms, Acceptable: < 200ms

# 2. Increase peer connections
./subspace-node run \
  --in-peers 512 \
  --out-peers 512

# 3. Use warp sync for faster initial sync
./subspace-node run --sync warp

# 4. Check disk performance
# Linux:
dd if=/dev/zero of=test bs=1GiB count=1 oflag=direct
# Should be > 100 MB/s for SSD

Network Diagnostics Tools​

Port Testing​

# Comprehensive port test script
#!/bin/bash
echo "Testing Autonomys Network Ports..."

# Get public IP
PUBLIC_IP=$(curl -s https://api.ipify.org)
echo "Public IP: $PUBLIC_IP"

# Test each port
for PORT in 30333 30433 30533; do
    echo -n "Testing port $PORT: "
    if timeout 2 bash -c "echo > /dev/tcp/localhost/$PORT" 2>/dev/null; then
        echo "PASS - Listening locally"
    else
        echo "FAIL - Not listening"
    fi
done

echo ""
echo "Have someone external run:"
echo "nc -zv $PUBLIC_IP 30333"

Connection Monitoring​

# Monitor active connections
watch -n 2 'netstat -ant | grep -E "30333|30433|30533" | grep ESTABLISHED | wc -l'

# Track peer IPs
netstat -ant | grep -E "30333|30433|30533" | grep ESTABLISHED | \
  awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -rn

# Monitor bandwidth per connection
sudo iftop -P -n -f "port 30333 or port 30433 or port 30533"

Advanced Diagnostics​

# Trace network path issues
traceroute 1.1.1.1
# Look for high latency hops or timeouts

# Check DNS resolution
nslookup 1.1.1.1
# Should resolve quickly

# Test MTU size
ping -M do -s 1472 8.8.8.8
# Reduce size if fragmentation occurs

# Packet capture for deep analysis
sudo tcpdump -i any -w autonomys.pcap \
  'port 30333 or port 30433 or port 30533'
# Analyze with Wireshark

When to Seek Help​

Gather Information First​

Before asking for help, collect:

# System information
uname -a  # Linux/macOS
systeminfo  # Windows

# Network configuration
ip addr show  # Linux
ipconfig /all  # Windows

# Autonomys logs (last 100 lines)
tail -n 100 /path/to/node.log > debug.log

# Port status
netstat -tuln | grep -E "30333|30433|30533" >> debug.log

# Peer count over time
grep -i "peers" /path/to/node.log | tail -20 >> debug.log

Where to Get Help​

  1. Discord: Autonomys Discord

    • #farming-support channel
    • Include debug.log contents

  2. Forum: Autonomys Forum

    • Network category
    • Include system specs and configuration