> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/troubleshooting/access-control-hardware-checks/restart-an-access-controller.md).

# Restart an Access Controller

Learn how to reboot your Verkada access controller

If your access controller becomes unresponsive and is not working properly or [Verkada Support](/command/need-help/contact-verkada-support.md) requests to reboot the controller, we recommend that you restart your access controller.

{% hint style="danger" %}
You must be an [Access Site Admin](/access-control/getting-started/roles-and-permissions-for-access-control.md) for the site the controller belongs to.
{% endhint %}

{% hint style="warning" %}
If the controller show’s an **Offline** status, rebooting the controller via Verkada Command doesn’t do anything. You need to unplug the access controller and manually plug it back in to restart it.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Devices.**
{% endstep %}

{% step %}
**Select the controller you want to restart, and click the controller’s image on the right.**
{% endstep %}

{% step %}
**At the top right, click Settings.**
{% endstep %}

{% step %}
**On Access Control Unit, click Restart.**

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-b1225800afbacfd0b3be4dbbf1651ae08ed3a437%2Fa1e99886119e736c5844ddd9930d9e47bed38e00.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}


---

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

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

```
GET https://help.verkada.com/access-control/troubleshooting/access-control-hardware-checks/restart-an-access-controller.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 `automate deployments from our CI pipeline` 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.