# Support

> Get help with Muxr: contact support@muxr.app, file a bug on GitHub, or check the FAQ for pairing, TLS fingerprint, connection, and read-only token issues.

Source: https://muxr.app/support.html

Contact us, file a bug, or check the FAQ below for pairing, TLS, and connection issues.

## Contact us

> **Email support**
>
> Write to [support@muxr.app](mailto:support@muxr.app) for anything — pairing trouble, connection errors, account-less deletion requests, or general questions. It's a monitored inbox and a real person replies.

Found a bug in the server, `muxrctl`, or the wider source-available [muxr-core](https://github.com/f0x-it-llc/muxr-core) project? File it on [GitHub Issues](https://github.com/f0x-it-llc/muxr-core/issues) — that's the fastest way to get eyes on a reproducible server-side problem, and lets other self-hosters find it too.

## Quick links

- [Getting Started](https://muxr.app/docs.html) — install `muxrd`, mint a token, and pair your device via QR.
- [Usage Guide](https://muxr.app/guide.html) — gestures, the command center, keyboard bar, and read-only mode.
- [muxr-core README](https://github.com/f0x-it-llc/muxr-core#readme) — the source-available server repository on GitHub.

## FAQ

### Pairing fails, or the QR code won't scan

- Confirm `muxrd` is actually running — check with `muxrd status`, or start it with `muxrd start`.
- Make sure the phone can reach the server — over your tailnet (see [Reach it over Tailscale](https://muxr.app/docs.html#tailscale)), or, if you chose the LAN route, on the same Wi-Fi (see [LAN instead of a tailnet](https://muxr.app/advanced.html#lan)).
- Check that the token hasn't been revoked — run `muxrd list-tokens` on the server to confirm it still exists.
- QR codes are shown once, right when a token is minted — `muxrctl` stores only a hash of the secret, so the code cannot be shown again for a token you have already dismissed (see [token secrets can't be retrieved after creation](https://muxr.app/advanced.html#tokens)). If you missed the scan: in `muxrctl` press `t`, choose **Revoke…** on that token, then **Create…** a new one and press **Show pairing QR** on the minted-secret dialog; or run the setup wizard again (`w`) and scan at its last step.
- If the camera won't focus or read the code, try the [manual fallback](https://muxr.app/docs.html#pair) — entering the server URL and token by hand on the Connect screen.

### "TLS fingerprint mismatch"

When you pair by QR against a self-signed server, the app pins trust to that exact certificate's SHA-256 fingerprint. This error means the fingerprint the app has stored no longer matches what the server presents — almost always because the server's self-signed certificate was regenerated (for example, after running `muxrd init` again to add a LAN SAN).

> **Re-pair to pin the new certificate**
>
> If you know the certificate changed intentionally, remove the saved server in the app and pair again by QR to pin the new fingerprint. If you did **not** regenerate the certificate and see this warning unexpectedly, treat it as a possible interception attempt and do not proceed until you've confirmed the server's certificate out-of-band.

### Connection refused, or the connection times out

- `muxrd` binds `127.0.0.1:50051` by default, which only accepts connections from the same machine. To reach it from a phone or tablet, start it with a LAN bind address (`muxrd start --bind 0.0.0.0:50051`) and add that address as a certificate SAN — see [LAN instead of a tailnet](https://muxr.app/advanced.html#lan).
- Confirm the server is listening on port `50051` (or whatever port you configured) and that the address you entered in the app matches it exactly.
- Check your firewall — both the host OS firewall and any router-level rules — allows inbound connections to that port from your phone's network.

### My read-only token can't modify sessions

This is by design. Mutating RPCs — creating, renaming, or closing sessions, tabs, and panes, and server-side pane fullscreen — fail closed on read-only tokens; the app also hides those affordances entirely when connected read-only. If you need to make changes, mint a read-write token instead: `muxrd create-token --name mobile` (omit `--read-only`).

### Does Muxr send push notifications?

Push notifications are not available in the app yet; they are coming soon. See the [roadmap](https://muxr.app/roadmap.html) for where they stand.

## Before you write in

These three things let us diagnose most issues on the first reply:

- **App version** — found in the app's Settings screen.
- **Server version** — run `muxrd --version`, or check the Connection info panel in the app's Settings, which shows the connected server's version.
- **A relevant `muxrd` log snippet** — copy the lines around when the problem occurred. If you ran the server in the foreground with `muxrd start`, this is in your terminal; as a daemon, check `muxrd status` for the log location. Skim the snippet before sending and redact anything sensitive — hostnames, tokens, or session content.

Questions about data instead of a technical issue? See the [Privacy Policy](https://muxr.app/privacy.html) and the [Terms of Use](https://muxr.app/terms.html).
