# BizNode Pro -- Troubleshooting Guide

This guide covers common issues specific to BizNode(TM) Pro. For general issues (dashboard not loading, Qdrant not starting, Ollama connection errors), refer to the Basic troubleshooting guide first.

---

## 1. BizChannel /bo Commands Not Working

**Symptom:** Bot does not respond to `/bo` commands, or returns an error.

**Solution:**

- Confirm the `bizchannel/client/` folder exists in your installation directory.
- Restart the bot: `python service_manager.py restart bot`
- Check that `NODE_TIER=pro` is set in your `.env` file.
- Review bot logs for BizChannel-related errors.

---

## 2. USB License Not Detected

**Symptom:** Pro features are disabled. Dashboard shows Basic tier.

**Solution:**

- Verify the USB license device is physically plugged in.
- Run the license check: `python services/license_validator.py --check`
- Try a different USB port.
- On Windows, check Device Manager to confirm the device is recognized.
- If the device was recently connected, restart the bot and dashboard.

---

## 3. Crypto Payments Not Processing

**Symptom:** BZeUSD or MATIC payments are not being detected or confirmed.

**Solution:**

- Verify `POLYGON_WALLET` is set correctly in `.env` (must be a valid Polygon address starting with `0x`).
- Verify `POLYGON_RPC_URL` is set to a working Polygon RPC endpoint.
- Check that the sender used the correct wallet address and network (Polygon, not Ethereum mainnet).
- Test RPC connectivity: confirm the endpoint responds to requests.
- Review logs in the dashboard for payment processing errors.

---

## 4. Stripe Webhook Errors

**Symptom:** Stripe payments succeed on the Stripe dashboard but are not reflected in BizNode.

**Solution:**

- Confirm `STRIPE_WEBHOOK_SECRET` in `.env` matches the webhook signing secret in your Stripe dashboard.
- Confirm `STRIPE_SECRET_KEY` is correct and not a test key (unless testing).
- Check that your webhook endpoint URL is correctly configured in Stripe.
- Review Stripe webhook delivery logs in the Stripe dashboard for failed attempts.
- Restart services after changing Stripe settings: `python service_manager.py restart`

---

## 5. Multi-Bot Not Starting

**Symptom:** Only one bot starts, or additional bots fail to launch.

**Solution:**

- Pro supports up to 5 bots. Each bot needs a unique `TELEGRAM_BOT_TOKEN` in `.env`.
- Ensure tokens are numbered: `TELEGRAM_BOT_TOKEN`, `TELEGRAM_BOT_TOKEN_2`, `TELEGRAM_BOT_TOKEN_3`, etc.
- Each token must belong to a different Telegram bot (created via @BotFather).
- Verify your USB license is valid -- multi-bot requires an active Pro license.
- Check logs for each bot instance to identify which one is failing.

---

## 6. Affiliate Links Not Generating

**Symptom:** The `/affiliate` bot command does not return a link, or the link is invalid.

**Solution:**

- Run the `/affiliate` command in your Telegram bot.
- Check that the affiliate service is running: review `affiliate_service.py` logs.
- Verify the database has the affiliate tables seeded (run setup wizard if needed).
- Confirm `NODE_TIER=pro` is set in `.env`.

---

## 7. DataVault Plugins Not Loading

**Symptom:** Plugins do not appear in the dashboard, or plugin commands fail.

**Solution:**

- Confirm the `datavault/` folder exists in your installation directory.
- Verify `plugin_runner.py` is present inside `datavault/`.
- Check that plugin files follow the expected format (see DataVault documentation).
- Restart services after adding new plugins.
- Review dashboard logs for plugin loading errors.

---

## 8. Update Packets Not Processing

**Symptom:** OTA updates are received but not applied.

**Solution:**

- Confirm the `updates/` folder exists in your installation directory.
- Verify `email_receiver.py` is running (it processes incoming update packets).
- Check that the email account configured for receiving updates is accessible.
- Review logs for packet validation errors (packets are signed and verified).

---

## 9. Pro Features Showing as Disabled

**Symptom:** Dashboard or bot reports features as disabled despite having a Pro license.

**Solution:**

- Verify the USB license device is connected.
- Run: `python services/license_validator.py --check`
- Run: `python services/tier_manager.py --status` to see which features are enabled.
- Confirm `NODE_TIER=pro` is set in `.env`.
- If the license was recently activated, restart all services: `python service_manager.py restart`

---

## 10. General Tips

- Always restart services after changing `.env` settings.
- Check the dashboard at `http://localhost:7777` for service health status.
- Use `python service_manager.py status` to verify all services are running.
- Logs are stored in the `logs/` folder -- check there for detailed error messages.

---

## Support

Pro users receive priority support.

- **Email:** biznodesupport@1bz.biz
- **Response time:** Priority handling for Pro license holders
- **Include in your support request:** your license reference number, a description of the issue, and relevant log output.
