Troubleshooting
Solutions for common issues when renting and accessing GPUs.
Payment issues
Section titled “Payment issues”Wallet connection problems
Section titled “Wallet connection problems”Wallet won’t connect:
Check browser compatibility:
- Chrome/Brave: Best support
- Firefox: Good support
- Safari: Limited support
- Edge: Basic support
Clear browser data:
# Clear cache and cookies for gpuflow.app# Browser settings > Privacy > Clear browsing data# Select "Cookies and site data" and "Cached images and files"MetaMask specific issues:
- Update to latest version
- Disable other wallet extensions temporarily
- Reset account in MetaMask settings
- Try incognito/private browsing mode
Transaction failures
Section titled “Transaction failures”Payment stuck pending:
Check transaction status:
- Open wallet and find transaction hash
- Search on Polygonscan (mainnet) or Amoy Explorer (testnet)
- Wait for network confirmation (usually <2 minutes)
- Retry if transaction fails
Insufficient funds error:
Error: "Insufficient funds for gas * price + value"Solutions:
- Ensure wallet has MATIC for gas fees (minimum 0.01 MATIC)
- Check total cost includes both rental payment and gas
- Wait for previous transactions to confirm
- Increase gas price if network is congested
Wrong network error:
Switch to correct network:
- Click network dropdown in wallet
- Select “Polygon” or “Polygon Amoy”
- Approve network switch request
- Retry payment
Add network manually if missing:
Network Name: Polygon AmoyRPC URL: https://rpc-amoy.polygon.technologyChain ID: 80002Currency: MATICBlock Explorer: https://amoy.polygonscan.comToken approval issues
Section titled “Token approval issues”ERC-20 token approval failed:
Reset token allowance:
// In browser console (advanced users only)// This resets USDC allowance to zero, then set new amountAlternative solutions:
- Use MATIC instead of ERC-20 tokens
- Try smaller approval amounts first
- Check token contract address matches network
- Verify sufficient token balance
Connection issues
Section titled “Connection issues”VPN connection failures
Section titled “VPN connection failures”WireGuard won’t connect:
Verify configuration:
# Check configuration file syntaxcat rental-config.conf | grep -E "(Address|Endpoint|PublicKey)"
# Test basic connectivity to providerping provider-ip-addressCommon configuration issues:
- Expired configuration (15-minute download window)
- Incorrect private key format
- Missing endpoint information
- Invalid allowed IPs range
Connection drops frequently:
Network stability issues:
- Check internet connection stability
- Switch from WiFi to ethernet if possible
- Disable power saving on network adapter
- Try different WireGuard client
Provider-side issues:
- Provider internet connection unstable
- Provider hardware maintenance
- Network routing problems
- Firewall blocking VPN traffic
Service access problems
Section titled “Service access problems”Cannot reach web interfaces:
Verify VPN connection:
# Test tunnel connectivityping 10.77.0.1
# Check assigned IPip addr show  # Linux/macOSipconfig      # WindowsService status checks:
# Test specific servicescurl -I http://10.77.x.2:8888  # Jupytercurl -I http://10.77.x.2:7860  # Stable Diffusiontelnet 10.77.x.2 22            # SSHServices not responding:
Wait for deployment:
- Initial deployment takes 1-3 minutes
- Check deployment status in dashboard
- Provider may need time to start services
Alternative access methods:
- Try SSH if web interfaces fail
- Use direct IP access instead of hostnames
- Check for typos in URLs
- Verify correct ports
Access method issues
Section titled “Access method issues”SSH connection problems
Section titled “SSH connection problems”SSH connection refused:
# Test basic connectivitytelnet 10.77.x.2 22
# Try verbose SSH for debuggingCommon causes:
- SSH service not started yet
- Firewall blocking SSH port
- Incorrect username (use rental)
- VPN tunnel not established
Authentication failed:
Password authentication:
- Use password provided in rental credentials
- Check for caps lock or special characters
- Try copy/paste to avoid typing errors
Key-based authentication:
# Verify key file permissionschmod 600 ~/.ssh/gpuflow_key
# Test key authentication
# Check if key is loaded in agentssh-add -lWeb terminal issues
Section titled “Web terminal issues”Terminal won’t load:
Browser compatibility:
- Update browser to latest version
- Disable ad blockers for gpuflow.app
- Enable JavaScript if disabled
- Try different browser
Network issues:
- Check VPN connection established
- Verify terminal URL correct
- Try refreshing page
- Clear browser cache
Terminal commands not working:
Environment issues:
# Check shell and environmentecho $SHELLecho $PATHwhich pythonwhich nvidia-smiPermission issues:
# Check user permissionswhoamigroupsls -la /workspaceVNC desktop problems
Section titled “VNC desktop problems”VNC won’t connect:
Connection testing:
# Test VNC port accessibilitytelnet 10.77.x.2 5901
# Check VNC server statusVNC client configuration:
- Server: 10.77.x.2:5901or10.77.x.2::5901
- Password: From rental credentials
- Color depth: 16-bit for better performance
- Compression: Enable for slower connections
Desktop appears frozen:
Resource constraints:
# Check system resources via SSHhtop              # Check CPU/memory usagenvidia-smi        # Check GPU usagedf -h             # Check disk spaceDesktop environment issues:
- Right-click desktop for context menu
- Open terminal from desktop
- Restart desktop environment if needed
- Switch to lighter desktop environment
Performance issues
Section titled “Performance issues”Slow response times
Section titled “Slow response times”High latency connections:
Network optimization:
# Test latency to providerping -c 10 10.77.x.2
# Trace network routetraceroute 10.77.x.2
# Test bandwidthiperf3 -c 10.77.x.2Connection tuning:
- Use wired internet instead of WiFi
- Close bandwidth-heavy applications
- Choose geographically closer providers
- Consider time-of-day network congestion
GPU performance issues:
Monitor GPU utilization:
# Real-time GPU monitoringwatch -n 1 nvidia-smi
# Check GPU memory usagenvidia-smi --query-gpu=memory.used,memory.total --format=csv
# Monitor temperature and throttlingnvidia-smi --query-gpu=temperature.gpu,clocks.gr,clocks.mem --format=csvPerformance optimization:
# Verify GPU accessibility in Pythonimport torchprint(f"GPU available: {torch.cuda.is_available()}")print(f"GPU name: {torch.cuda.get_device_name()}")print(f"GPU memory: {torch.cuda.get_device_properties(0).total_memory}")
# Check CUDA version compatibilityprint(f"CUDA version: {torch.version.cuda}")Memory issues
Section titled “Memory issues”Out of memory errors:
GPU memory management:
# Monitor GPU memory in PyTorchimport torchprint(f"Allocated: {torch.cuda.memory_allocated() / 1024**3:.2f} GB")print(f"Reserved: {torch.cuda.memory_reserved() / 1024**3:.2f} GB")
# Clear GPU cachetorch.cuda.empty_cache()
# Use gradient accumulation for large modelsaccumulation_steps = 4for i, batch in enumerate(dataloader):    loss = model(batch) / accumulation_steps    loss.backward()    if (i + 1) % accumulation_steps == 0:        optimizer.step()        optimizer.zero_grad()System memory issues:
# Check system memory usagefree -hps aux --sort=-%mem | head -10
# Clear system cache if neededsudo syncsudo echo 3 > /proc/sys/vm/drop_cachesEnvironment-specific issues
Section titled “Environment-specific issues”Jupyter Lab problems
Section titled “Jupyter Lab problems”Jupyter won’t start:
Service management:
# Check Jupyter status
# Restart Jupyter
# Check logsConfiguration issues:
# Check Jupyter configuration
# Reset Jupyter settingsKernel issues:
Kernel not starting:
# List available kernels
# Install missing kernels
# Test kernel manuallyPackage import errors:
# Check Python environment
# Install missing packagesStable Diffusion issues
Section titled “Stable Diffusion issues”WebUI won’t load:
Service status:
# Check Stable Diffusion WebUIcurl -I http://10.77.x.2:7860
# Check service logsModel loading problems:
# Check model files
# Check disk space
# Test model loadingssh [email protected] 'cd /workspace/stable-diffusion-webui && python -c "from modules import shared; print(shared.opts.sd_model_checkpoint)"'Generation errors:
CUDA out of memory:
# Reduce image resolution# Use `--medvram` or `--lowvram` flags# Enable `--xformers` for memory optimizationModel compatibility:
- Verify model format (.ckpt,.safetensors)
- Check model architecture compatibility
- Ensure sufficient VRAM for model size
- Try different sampling methods
Mining software issues
Section titled “Mining software issues”Miner won’t start:
Configuration verification:
# Check miner configuration
# Test GPU detection
# Check pool connectivityPermission issues:
# Check file permissions
# Fix permissions if neededLow hashrate performance:
GPU optimization:
# Check current GPU settingsnvidia-smi -q -d CLOCK,POWER
# Monitor during miningwatch -n 1 'nvidia-smi --query-gpu=clocks.gr,clocks.mem,temperature.gpu,power.draw --format=csv'Mining optimization:
- Verify optimal algorithm selection
- Check memory clock settings
- Monitor temperature and throttling
- Ensure adequate power supply
Data transfer issues
Section titled “Data transfer issues”Upload/download failures
Section titled “Upload/download failures”Large file transfer problems:
Alternative transfer methods:
# Use rsync for resume capability
# Split large filessplit -b 1G large_file.zip file_part_# Transfer parts individually# Reassemble: cat file_part_* > large_file.zipNetwork optimization:
# Compress before transfertar -czf archive.tar.gz data_directory/# Transfer compressed file# Extract on remote: tar -xzf archive.tar.gzTransfer interrupted:
Resume transfers:
# Rsync with resume
# SCP alternative with resume capability# Note: SCP doesn't support resume, use rsync insteadVerify integrity:
# Generate checksums before transfersha256sum file.zip > file.zip.sha256
# Verify after transferGetting help
Section titled “Getting help”Diagnostic information
Section titled “Diagnostic information”Before contacting support, collect:
System information:
# Browser information# - Browser name and version# - Operating system# - Extensions installed
# Network informationping -c 5 gpuflow.appnslookup gpuflow.appRental details:
- Rental ID from dashboard
- Provider wallet address
- GPU model and specifications
- Error messages (exact text)
- Screenshots of issues
Connection information:
# WireGuard statussudo wg show
# Network configurationip route showip addr showSupport channels
Section titled “Support channels”Community support:
- Discord server - Real-time help
- Community forum - Searchable knowledge base
Official support:
- Email: [email protected]
- Response time: 24-48 hours for technical issues
- Include diagnostic information above
Emergency issues:
- Payment processed but no access after 10 minutes
- Suspected security compromise
- Provider completely unresponsive
- Data loss during active rental
Self-help resources
Section titled “Self-help resources”Documentation:
- Review relevant use case guides
- Check provider troubleshooting documentation
- Verify wallet and network setup
Community resources:
- Search Discord for similar issues
- Check GitHub issues and discussions
- Review provider community forums
Testing steps:
- Try different browser/incognito mode
- Test with different wallet if available
- Attempt connection from different network
- Verify issue persists across multiple rentals
- Test with different provider if possible