> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/byod/grandfathered-byod-diy-info/byod-troubleshooting.md).

# BYOD troubleshooting

Start with [Station troubleshooting](https://docs.wingbits.com/general-help/stations/station-troubleshooting.md) on the main docs. Those checks only need the dashboard. Come back here for problems that only affect BYOD (self built) stations.

After any fix, allow about 20 minutes for your station to show "Online" again.

### 1. Check the power first

Underpowered stations are the most common BYOD problem, and they rarely look like a power problem. The SDR stick draws a lot of power through the Pi, so the USB devices are the first thing to fail. Signs:

* Your SDR isn't detected, or comes and goes
* Your station restarts on its own ("Client Uptime" keeps resetting)
* "Data Input Connected" flips between Yes and No on the "Statistics" tab

To check, SSH into the device and run:

```bash
vcgencmd get_throttled
```

`0x0` means healthy. Anything else means the Pi has been throttled or underpowered, which almost always means the power supply. This command only works on a Raspberry Pi.

What we recommend:

* A good 5V 4A power supply for the Pi
* A 3A powered USB hub, with the SDR plugged into the hub instead of the Pi

{% hint style="warning" %}
On an underpowered Pi, unplugging and replugging the SDR often seems to fix things and then fails again later. If you keep doing that, check the power instead.
{% endhint %}

### 2. Check the receiver is detected

```bash
lsusb
```

Your SDR should be listed, plus your GeoSigner if you have one. If the SDR isn't there:

* `get_throttled` is not `0x0`: treat it as a power problem (step 1).
* `get_throttled` is `0x0`: reseat the dongle, try another USB port and check the cable.

### 3. Run the debug script

```bash
curl -sL https://gitlab.com/wingbits/config/-/raw/master/debug.sh | sudo bash
```

See [Debug your station](https://docs.wingbits.com/byod/grandfathered-byod-diy-info/debug-your-station.md) if this doesn't run.

### 4. Check your client version

```bash
sudo wingbits -v
```

If it shows v1.9.x or lower, or a long string of letters and numbers instead of a version, your client is too old to connect or update itself. Restarting won't help. Contact us with your station ID and the version you see.

### 5. GPS problems

Your station needs a GPS position for its data to count. With a GeoSigner fitted, run `sudo wingbits geosigner info`, or open the Station Monitor page at `http://<your-station-ip>:8088` and watch the GPS fields over a few refreshes.

* Healthy: "GPS TIME" matches the real time and ticks forward.
* Faulty: it is frozen, or hours away from the real time.
* No fix: check the antenna has a clear view of the sky and the cable is sound.

For a frozen or wrong GPS time, unplug the station at the wall, wait 30 to 60 seconds and plug it back in. A soft reboot doesn't reset the GPS. If it is still wrong after that, contact us.

### 6. Network and ports

Your station needs outbound access on ports 443, 123, 53, 2201 and 2500.

On the Station Monitor page, "CONNECTIVITY TESTS" checks each of our servers for you. The important one is `ingest.wingbits.com` on port 443. If ours fail but `www.google.com` passes, your network is blocking us. A wrong time from `date -R` usually means port 123 is blocked.

### Still stuck?

Run these and paste the output when you contact us. They only read information and change nothing.

```bash
cat /etc/os-release
lsusb
vcgencmd get_throttled
uptime
date -R
sudo wingbits -v
cat /etc/wingbits/device
sudo wingbits status --verbose
sudo wingbits geosigner info
```

Also include your station ID, your hardware (board, SDR, power supply, powered hub or not) and what you have tried. We may ask for your station's logs, and will give you the commands to run if so.

{% hint style="danger" %}
We will never ask for your password, wallet seed phrase or private key. Don't share them with anyone who asks.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wingbits.com/byod/grandfathered-byod-diy-info/byod-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
