# Troubleshoot Looper setup

## There is no download, or the installer says pending

Check [release status](https://looper.fyi/release.json). `status: pending` means public installation is not available yet. A missing archive or checksum is a release issue; do not substitute an unverified mirror or guessed download URL.

## The Linux installer rejects my computer or version

This path supports Linux x86_64 only. Check `uname -s` and `uname -m`. Install the prerequisites listed in [Linux setup](https://looper.fyi/docs/linux). An explicit `--version` must match the published Linux asset's version; the installer never silently switches versions.

## A checksum does not match

Stop. Do not execute or extract the failed download. The bootstrap installer cleans up its temporary files automatically. Compare the asset and checksum information with the official [release metadata](https://looper.fyi/release.json), and report persistent mismatch with the version and filename.

## macOS blocks the app

Check that the release came from the exact asset URL in Looper's [release metadata](https://looper.fyi/release.json) and that your Mac meets [the requirements](https://looper.fyi/docs/macos). Record the exact macOS message and release version. Do not disable Gatekeeper, remove quarantine, or bypass signing errors to make an unverified build run.

## The Linux user service is unavailable

```sh
~/.local/bin/looper-linux status
~/.local/bin/looper-linux logs
systemctl --user status looper.service
```

Use a logged-in user session with a working user service manager. A headless session may need administrator-managed lingering. An inactive desktop-notification companion is expected unless you opted in. Review logs for private session text and credentials before sharing them.

## The phone cannot find the computer

Check that the computer is awake and Looper's local server is ready. Confirm a reachable LAN or Tailscale route, and use the current pairing flow. Do not expose an unauthenticated server publicly or share a pairing code to troubleshoot. A healthy connection alone does not prove that a session's data is current; open the same session on both devices and compare its latest activity.

## Report an installation problem

Include your OS version, CPU architecture, Looper release version, the exact failing step, and the error text in [a GitHub issue](https://github.com/heyAyushh/loopndroll/issues). Redact tokens, pairing codes, environment secrets, and private prompts. Keep existing configuration and session data intact while diagnosing.

[Installation overview](https://looper.fyi/docs/install)