> 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.md).

# 문제 해결

- [출입 컨트롤러 하드웨어 점검](https://help.verkada.com/access-control/ko/troubleshooting/access-control-hardware-checks.md): Verkada 출입 컨트롤러 문제를 해결하기 위한 물리적 점검 수행 방법을 알아보세요
- [오프라인 작동](https://help.verkada.com/access-control/ko/troubleshooting/access-control-hardware-checks/verkada-access-offline-operation.md): 인터넷 장애 발생 시 출입 컨트롤러 기능에 어떤 일이 일어나는지 알아보세요
- [도어 즉시 재잠금 문제 해결](https://help.verkada.com/access-control/ko/troubleshooting/access-control-hardware-checks/troubleshoot-an-immediate-door-relock.md): 도어의 잠금 해제 시간이 예상보다 짧을 때 문제를 해결하는 방법을 알아보세요
- [출입 컨트롤러 재시작](https://help.verkada.com/access-control/ko/troubleshooting/access-control-hardware-checks/restart-an-access-controller.md): Verkada 출입 컨트롤러를 재부팅하는 방법을 알아보세요
- [리더 연결 상태](https://help.verkada.com/access-control/ko/troubleshooting/reader-connectivity-status-on-command.md): 리더 연결 상태를 사용해 리더의 정상 동작을 확인하세요
- [카드 리더 LED 동작](https://help.verkada.com/access-control/ko/troubleshooting/reader-connectivity-status-on-command/verkada-card-reader-led-behavior.md): Verkada 카드 리더의 LED 표시 동작에 대해 알아보세요
- [AC41 상태 LED](https://help.verkada.com/access-control/ko/troubleshooting/verkada-ac41-status-led.md): Verkada AC41 LED 코드 상태를 알아보세요
- [AC41 테스트 버튼 사용](https://help.verkada.com/access-control/ko/troubleshooting/verkada-ac41-status-led/use-the-ac41-test-buttons.md): 설정 및 문제 해결을 위해 AC41 테스트 버튼을 사용하는 방법을 알아보세요
- [AC41에서 드라이 락 구성](https://help.verkada.com/access-control/ko/troubleshooting/verkada-ac41-status-led/configure-dry-lock-on-an-ac41.md): 예상대로 잠기거나 잠금 해제되지 않는 AC41에서 드라이 락을 설정하는 방법을 알아보세요
- [Verkada 도어락의 걸쇠 고착 문제 해결](https://help.verkada.com/access-control/ko/troubleshooting/verkada.md): Verkada 도어 하드웨어에서 걸쇠가 고착되었을 때 이를 안전하게 식별하고 문제를 해결하는 방법을 알아보세요


---

# 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.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.