> 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/ko/troubleshooting/access-control-hardware-checks/restart-an-access-controller.md).

# 출입 컨트롤러 재시작

Verkada 출입 컨트롤러를 재부팅하는 방법을 알아보세요

액세스 컨트롤러가 응답하지 않고 제대로 작동하지 않거나 [Verkada 지원팀](/command/ko/need-help/contact-verkada-support.md) 컨트롤러 재부팅을 요청하는 경우, 액세스 컨트롤러를 다시 시작하는 것이 좋습니다.

{% hint style="danger" %}
관리자여야 합니다 [액세스 사이트 관리자](/access-control/ko/getting-started/roles-and-permissions-for-access-control.md) 컨트롤러가 속한 사이트에 대해.
{% endhint %}

{% hint style="warning" %}
컨트롤러에 **오프라인** 상태가 표시되면, Verkada Command를 통해 컨트롤러를 재부팅해도 아무 일도 일어나지 않습니다. 액세스 컨트롤러의 전원을 뽑았다가 다시 직접 연결하여 재시작해야 합니다.
{% endhint %}

{% stepper %}
{% step %}
**Verkada Command에서 모든 제품 > 장치로 이동합니다.**
{% endstep %}

{% step %}
**다시 시작할 컨트롤러를 선택한 다음, 오른쪽의 컨트롤러 이미지를 클릭합니다.**
{% endstep %}

{% step %}
**오른쪽 상단에서 Settings를 클릭합니다.**
{% endstep %}

{% step %}
**Access Control Unit에서 다시 시작을 클릭합니다.**

<div align="left" data-with-frame="true"><img src="https://3458411332-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/ko/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.
