Common Errors
Connection Issues
Connection Timeout
Symptom: Stuck on "Connecting" status for a long time
Possible causes:
- Target service is not running or port is incorrect
- Machine cannot reach the public gateway
- Firewall is blocking WebSocket connections
Solutions:
- Verify target service is running:
telnet <ip> <port> - Check connectivity to
console.yishield.com - Ensure firewall allows outbound connections on port 62888
Authentication Failed (401)
Symptom: Authentication failure or 401 error
Possible cause:
- Local credentials are expired or corrupted
Solution:
bash
shield cleanClear credentials and reconnect — new credentials will be generated automatically.
Target Service Auth Failed
Symptom: Tunnel established successfully, but browser shows an authentication error
Possible causes:
- Wrong username or password
- SSH private key mismatch
Solutions:
- Verify username and password are correct
- For private keys, confirm the file path is correct and permissions are
600
Port Already in Use
Symptom: shield start fails to launch
Possible cause:
- Port 8181 is already in use by another program
Solution:
bash
shield start 9090 # Use a different portInstallation Issues
Homebrew Install Failed
Solution:
bash
brew update
brew tap fengyily/tap
brew install shield-cliIf it still fails, try the one-liner script:
bash
curl -fsSL https://raw.githubusercontent.com/fengyily/shield-cli/main/install.sh | shPermission Denied
Symptom: Permission denied when running on Linux
Solution:
bash
chmod +x ./shield