> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/setup-docs/cms-configuration-and-integration/configure-wake-on-lan.md).

# Configure Wake on LAN

Wake on LAN is supported if the media player hardware supports it and if the signage Player is addressable by the CMS

{% hint style="success" %}
In this case, “addressable” means that there is a clear network route between the CMS and the Player hardware.
{% endhint %}

{% hint style="warning" %}
Wake on LAN is not supported with Docker installations as the CMS will be running on a different network to the host machine
{% endhint %}

Assuming the hardware and network supports Wake on LAN, it is configured in the **CMS** using the **Display Edit Form**.

* Click on **Displays** from the main CMS menu.
* Use the row menu for the chosen **Display** and select **Edit**.
* Use the **Wake on LAN** tab to configure:

![Wake on LAN](https://2149703612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOD5P6BGYveuzkbhjZRsq%2Fuploads%2Fgit-blob-477371d2495a2c4eb0eae684f38f8412426b550b%2Fwake_on_lan_edit.png?alt=media)

{% hint style="success" %}
An immediate WOL message can be sent to the **Display** for testing purposes using the Display row menu and selecting **Wake on LAN**.
{% endhint %}

{% hint style="warning" %}
The [maintenance module](/setup-docs/cms-installation/cms-maintenance.md) must be correctly configured for a timed WOL message to be sent.
{% endhint %}

{% hint style="success" %}
There are a few different options for putting the Player to sleep - such as a **Scheduled Task** or [Shell Command](https://xibo.org.uk/docs/setup/command-functionality)
{% 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 dynamically by asking a question.

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

```
GET https://docs.xibosignage.com/setup-docs/cms-configuration-and-integration/configure-wake-on-lan.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 `build a script that syncs our docs to a CMS` 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.