# ReelPing — Support

## Before asking

1. Read [TROUBLESHOOTING.md](TROUBLESHOOTING.md) and match your **Test
   connection** classification.
2. Check the [CONFIGURATION.md](CONFIGURATION.md) reference.
3. Download **Diagnostics** (Settings → Data) — it contains **no secrets**.

## Where to get help

- **Bugs:** open a [bug report](https://github.com/BGriffin63/reelping/issues/new?template=bug_report.yml).
- **Feature ideas:** open a [feature request](https://github.com/BGriffin63/reelping/issues/new?template=feature_request.yml).
- **Setup help:** open a [support request](https://github.com/BGriffin63/reelping/issues/new?template=support_request.yml).
- **Unraid users:** open a [GitHub issue](https://github.com/BGriffin63/ReelPing/issues) (a dedicated Unraid forum support thread may be added later).

## Please always

- **Never** paste your Plex token or Discord webhook URL. Redact secrets.
- Include your ReelPing version (Diagnostics), where ReelPing runs, and where
  Plex runs.
- Include the failing **classification** and any sanitized logs/diagnostics.

## Security issues

Do **not** open a public issue. Follow
[.github/SECURITY.md](../.github/SECURITY.md) (private vulnerability reporting).

## Scope & expectations

ReelPing is a volunteer-maintained community project provided under the MIT
license with no warranty. Response times are best-effort. Requests that fall
outside v1 scope (e.g. controlling Plex, adding telemetry) will be declined with
an explanation.