Appearance
Troubleshooting Guide
Common issues and solutions when working with ASI:Chain DevNet.
Connection Issues
Node Cannot Connect to Network
Symptoms:
- Node fails to sync
- No peer connections
- Timeout errors
Solutions:
Verify Bootstrap Connection
bashping 54.152.57.201 telnet 54.152.57.201 40400Check Firewall Rules
bashsudo ufw status sudo ufw allow 40400:40405/tcpRestart Node
bashdocker compose -f validator.yml restartCheck Logs
bashdocker logs validator -f
Node Won't Start
Symptoms:
- Container exits immediately
- Docker compose fails
Solutions:
Check Configuration
- Verify
.envfile exists and is correct - Check
validator.confsyntax - Ensure private key is valid
- Verify
Check Port Conflicts
bashnetstat -tulpn | grep 40400View Container Logs
bashdocker logs validatorRemove and Recreate
bashdocker compose -f validator.yml down rm -rf data/ docker compose -f validator.yml up -d
Synchronization Problems
Node Not Synchronizing
Symptoms:
- Stuck at old block height
- No new blocks appearing
Solutions:
Check Peer Connections Look for
Peers: Xin logs - should be 3+Verify Network Connectivity
bashcurl http://54.152.57.201:40453/statusReset Blockchain Data
bashdocker compose -f validator.yml down rm -rf data/ docker compose -f validator.yml up -d
Slow Synchronization
Causes:
- Network bandwidth limitation
- Slow disk I/O
- High network congestion
Solutions:
- Use SSD for storage
- Increase allocated resources
- Check network speed
- Wait for sync to complete
Wallet Issues
Wallet Won't Load
Solutions:
Clear Browser Cache
- Chrome: Settings > Privacy > Clear browsing data
- Firefox: Settings > Privacy & Security > Clear Data
Try Incognito/Private Mode
- Eliminates extension conflicts
- Fresh start without cache
Check JavaScript
- Ensure JavaScript is enabled
- Disable blocking extensions
Try Different Browser
- Chrome, Firefox, Safari, Edge
Cannot Connect to Network
Solutions:
Check Network Selection
- Verify correct network is selected
- Try switching networks
Verify Endpoints
- DevNet:
54.152.57.201 - Check Settings page
- DevNet:
Test Connectivity
bashcurl http://54.152.57.201:40453/status
Balance Not Showing
Solutions:
Refresh Balance
- Click "Refresh Balance" button
- Wait a few seconds
Check Transaction Status
- Verify faucet transaction completed
- Check on Block Explorer
Clear Cache and Reload
- Hard refresh: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac)
Transaction Issues
Transaction Failed
Common Reasons:
Insufficient Balance
- Need balance for amount + fees
- Request more from faucet
Invalid Address
- Check recipient address format
- Must be 50-54 characters
- Starts with "1111"
Network Issues
- Check network connectivity
- Retry transaction
Transaction Pending Too Long
Solutions:
Wait for Confirmation
- Average: 20-60 seconds
- Network may be busy
Check Explorer
- Verify transaction exists
- Check block confirmations
Check Node Status
- Ensure network is operational
- Visit Explorer
Validator Issues
Validator Not Proposing Blocks
Causes:
Not Fully Synchronized
- Check sync status in logs
- Wait for full sync
Insufficient Peer Connections
- Need 3+ peers
- Check network connectivity
Configuration Issues
- Verify private/public keys
- Check validator.conf
Solutions:
Check Logs
bashdocker logs validator -fVerify Peers Look for:
Peers: 4or moreRestart Validator
bashdocker compose -f validator.yml restart
High Resource Usage
Solutions:
Increase Allocated Resources
yamldeploy: resources: limits: cpus: '8.0' memory: 32GUse SSD Storage
- Much faster I/O
- Critical for validators
Monitor Performance
bashdocker stats validator
Docker Issues
Permission Denied Errors
Solution:
bash
sudo usermod -aG docker $USER
newgrp dockerOut of Disk Space
Solutions:
Clean Docker
bashdocker system prune -aCheck Disk Usage
bashdf -hRemove Old Containers
bashdocker container prune
Image Pull Failed
Solutions:
Check Internet Connection
Retry Pull
bashdocker pull public.ecr.aws/f6y9h6x4/asi-chain/node:latestClear Docker Cache
bashdocker system prune -a
API Issues
Cannot Access HTTP API
Solutions:
Check Node is Running
bashdocker ps | grep validatorVerify Port Mapping
bashdocker port validatorTest Endpoint
bashcurl http://localhost:40403/statusCheck Firewall
bashsudo ufw allow 40403/tcp
gRPC Connection Failed
Solutions:
Verify Port
- Internal: 40402
- External: 40401
Test Connection
bashgrpcurl -plaintext localhost:40401 list
Network Issues
DNS Resolution Failed
Solution:
bash
# Use IP directly
54.152.57.201Timeout Errors
Causes:
- Slow network
- Server overload
- Firewall blocking
Solutions:
- Check internet speed
- Try different network
- Wait and retry
Smart Contract Issues
Deployment Failed
Common Issues:
Syntax Errors
- Check Rholang syntax
- Use IDE validation
Insufficient Phlo
- Increase phlo-limit
- Default: 10000000
Invalid Private Key
- Verify key format
- Check key is correct
Contract Not Executing
Solutions:
Check Logs
bashdocker logs validator -fVerify Deployment
- Check DeployId
- Search on Explorer
Propose Block
bashcargo run -- propose --private-key <key> -H localhost -p 40402
CLI Issues
Rust Client Not Found
Solution:
bash
git clone https://github.com/singnet/rust-client.git
cd rust-client
cargo build --releaseCommand Failed
Solutions:
Check Syntax
bashcargo run -- deploy -f ./contract.rho --private-key <key> -H <host> -p <port>Verify Node Running
bashcurl http://localhost:40402Check Private Key
- Must be 64 hex characters
- No prefix or suffix
Getting More Help
If issues persist:
Check FAQ
- FAQ Section
- Common questions answered
Review Logs
- Docker logs provide clues
- Share relevant logs when asking for help
GitHub Issues
- Create an issue
- Provide details and logs
Documentation
Diagnostic Commands
Quick Health Check
bash
# Docker status
docker ps -a
# View logs
docker logs validator --tail 50
# Check resources
docker stats validator
# Test API
curl http://localhost:40403/status
# Check network
ping 54.152.57.201Collect Debug Information
bash
# System info
uname -a
docker --version
# Container info
docker inspect validator
# Full logs
docker logs validator > validator.log
# Network status
netstat -tulpn | grep 404Remember: Most issues can be resolved by checking logs, verifying configuration, and restarting services. Don't hesitate to ask for help if stuck!