> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/replays/replay-servers/managing-replay-servers.md).

# Managing Replay Servers

Replay Servers are managed from the **Replay Servers** section in the admin dashboard.

***

## Device Status

Each device reports one of the following statuses:

* **Pending** - Device has connected but has not been approved yet
* **Approved** - Device is paired and operational
* **Revoked** - Device access has been revoked by an admin

***

## Pairing a New Device

When a new Replay Server is installed at a location:

1. The device is set up using the install script (`install.sh`)
2. The device connects to the PodPlay API and appears as **Pending**
3. Navigate to **Replay Servers** in the admin dashboard
4. Find the pending device and click to open it
5. Assign it to the correct **Area** (location)
6. Click **Approve** to pair the device

***

## Viewing Device Details

Click on any approved Replay Server to see:

* **Status** - Current device status
* **Device ID** - Unique hardware identifier
* **Hostname** - Device hostname on the network
* **Area** - The location the device is assigned to
* **Server URL** - External URL for remote access (if configured)
* **Local IP** - The device's local network IP address
* **Last Seen** - Timestamp of the most recent heartbeat
* **Paired At** - When the device was approved

***

## Restarting the Service

If a device is experiencing issues:

1. Open the Replay Server detail view
2. Click **Restart Service**
3. Confirm the action

The service will restart within a few seconds. It may briefly appear offline before reconnecting.

***

## Unpairing a Device

To remove a device from a location:

1. Open the Replay Server detail view
2. Click **Unpair Device**
3. Confirm the action

The device record will be revoked and permanently removed from the system. The physical device is not affected and can be re-paired to a different area by running a fresh install.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/replays/replay-servers/managing-replay-servers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.