> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zerogpu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fix common problems connecting Edge devices, getting work, and seeing earnings.

Start with [Verify devices](https://docs.zerogpu.ai/edge/verify.md): it walks through whether a device is connected, eligible for work, and earning. The problems below cover every platform; each platform guide also has its own troubleshooting table.

## Registration and keys

| Symptom | Fix |
| - | - |
| Key rejected, or `401` on registration | Use the SDK key (`zgpu-sdk-…`) of your app or fleet, not an API key (`zgpu-api-…`). Check the app or fleet is **Approved** on **My Apps**. |
| App stuck in **Pending Review** | Review usually takes 24–48 hours. Contact [hello@zerogpu.ai](mailto:hello@zerogpu.ai) if it takes longer. |
| Device registers but the platform isn't accepted | The platform must be one of the app types or device types you registered. Edit your app's setup on **My Apps**. |
| `Registration politely refused` | Normal. The network is declining this device for now, and it retries by itself. |

## Connected, but no work

| Symptom | Fix |
| - | - |
| Device sits ready with no tasks | Work follows network demand, and new devices get less work at first. Keep it running. |
| Device keeps starting over as new | Keep its stored identity: app data on Android and in browsers, `ZG_DATA_DIR` or the `/data` volume for `@zerogpu/worker`, and the agent's state folder. |
| Phone or browser stops contributing | SDKs on phones and in browsers only run while the app is open, and phones pause when the battery is low (below 20% and not charging). |
| Agent machine never serves | Check `--resource-policy`: with `idle-only` or `scheduled`, the machine only serves when idle or inside its schedule. Run `zerogpu-edge doctor`. |
| User turned sharing off | Expected. Your app must give users a way to opt out. |

## Installs and downloads

| Symptom | Fix |
| - | - |
| Windows shows **Windows protected your PC** | The Windows installers aren't Authenticode-signed yet. Check the SHA-256, then select **More info → Run anyway**. See [Windows](https://docs.zerogpu.ai/edge/agent/windows.md). |
| A download looks wrong | Compare its SHA-256 with `SHA256SUMS` on [apps.zerogpu.ai/edge](https://apps.zerogpu.ai/edge). Only download the agent from there. |
| `npm install @zerogpu/…` fails with a `404` | Your `.npmrc` maps `@zerogpu` to another registry. Add `--@zerogpu:registry=https://registry.npmjs.org`. |
| Chrome extension rejected for remote code | Vendor the SDK with `npx zerogpu init` instead of loading it from the CDN. See [Chrome Extension](https://docs.zerogpu.ai/edge/sdk/chrome-extension.md). |

## Earnings

| Symptom | Fix |
| - | - |
| Requests show, earnings don't | Analytics can lag by a few minutes. Check the date range and app filter. |
| Zero earnings for more than a day with connected devices | Contact [hello@zerogpu.ai](mailto:hello@zerogpu.ai) with your app name and platform. |

## Platform guides

> [card] [Windows agent](https://docs.zerogpu.ai/edge/agent/windows.md#troubleshooting)

> [card] [macOS agent](https://docs.zerogpu.ai/edge/agent/macos.md#troubleshooting)

> [card] [Linux agent](https://docs.zerogpu.ai/edge/agent/linux.md#troubleshooting)

> [card] [Android](https://docs.zerogpu.ai/edge/sdk/android.md#troubleshooting)

> [card] [Chrome Extension](https://docs.zerogpu.ai/edge/sdk/chrome-extension.md#troubleshooting)

> [card] [Browser](https://docs.zerogpu.ai/edge/sdk/browser.md#troubleshooting)

> [card] [Telegram Mini Apps](https://docs.zerogpu.ai/edge/sdk/telegram.md#troubleshooting)

> [card] [macOS desktop apps](https://docs.zerogpu.ai/edge/sdk/electron.md#troubleshooting)

> [card] [Server / npm](https://docs.zerogpu.ai/edge/sdk/server.md#troubleshooting)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.