Encountering a cryptic 'Connection Refused' error when your automation stops? ๐ Don't panic; diagnosing platform hiccups requires a structured approach.
Here is a step-by-step guide to troubleshooting common issues:
1. **Initial Diagnostics:** Always start by running the built-in diagnostic tool from your terminal: `wolfbot doctor`. This checks installation integrity without making changes. โ
2. **Installation Errors:** Be ready to address specific issues like insufficient disk space (needs 2GB+), permission denials (run as Administrator), or missing dependencies (e.g., Visual C++ Redistributable). โ ๏ธ
3. **Connection Checks:** Verify multiple external factors:
* Is your API key valid and does it have the required permissions (e.g., Trade โ , Withdrawal โ)?
* Is your IP address restricted?
* Is the target exchange's API status page operational?
4. **Persistent Issues:** Manually check your local internet connection. Also, consider if the exchange might be geo-blocking your region, potentially requiring a VPN.
5. **Performance Bottlenecks:** If you see high CPU usage, reduce active trading pairs or increase the bot's interval. High memory usage often just needs a restart, especially after running for over seven days.
6. **Corruption:** If you suspect configuration loss or database corruption, try restoring from a backup archive, or run the repair command: `wolfbot repair`.
7. **Reporting Bugs:** When reporting complex bugs, gather detailed logs from the specified directories (Windows: `C:\Program Files\WolfBot\logs\`; Linux: `~/.wolfbot/logs/`) and attach them to a new GitHub issue, remembering to redact sensitive credentials. ๐ต๏ธ
For a comprehensive, step-by-step reference guide covering these and more scenarios, visit https://community.wolfbot.io/docs/troubleshooting. ๐
#WolfBot #TradingAutomation #CryptoTroubleshooting #BotSetup #Crypto
Here is a step-by-step guide to troubleshooting common issues:
1. **Initial Diagnostics:** Always start by running the built-in diagnostic tool from your terminal: `wolfbot doctor`. This checks installation integrity without making changes. โ
2. **Installation Errors:** Be ready to address specific issues like insufficient disk space (needs 2GB+), permission denials (run as Administrator), or missing dependencies (e.g., Visual C++ Redistributable). โ ๏ธ
3. **Connection Checks:** Verify multiple external factors:
* Is your API key valid and does it have the required permissions (e.g., Trade โ , Withdrawal โ)?
* Is your IP address restricted?
* Is the target exchange's API status page operational?
4. **Persistent Issues:** Manually check your local internet connection. Also, consider if the exchange might be geo-blocking your region, potentially requiring a VPN.
5. **Performance Bottlenecks:** If you see high CPU usage, reduce active trading pairs or increase the bot's interval. High memory usage often just needs a restart, especially after running for over seven days.
6. **Corruption:** If you suspect configuration loss or database corruption, try restoring from a backup archive, or run the repair command: `wolfbot repair`.
7. **Reporting Bugs:** When reporting complex bugs, gather detailed logs from the specified directories (Windows: `C:\Program Files\WolfBot\logs\`; Linux: `~/.wolfbot/logs/`) and attach them to a new GitHub issue, remembering to redact sensitive credentials. ๐ต๏ธ
For a comprehensive, step-by-step reference guide covering these and more scenarios, visit https://community.wolfbot.io/docs/troubleshooting. ๐
#WolfBot #TradingAutomation #CryptoTroubleshooting #BotSetup #Crypto
