> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/support/troubleshooting.md).

# Troubleshooting

### Fix connection issues on Linux

You may encounter connection issues when trying to connect to your workspace with your Personal Security Device device on a Linux environment. The following steps will help you solve this issue.

#### Step 1. Add udev rules

Create a set of udev rules to allow device access. Refer to the [Chrome USB API documentation](https://developer.chrome.com/apps/app_usb#caveats) for details. Use the following command and retry to access the application.

`wget -q -O - https://raw.githubusercontent.com/LedgerHQ/udev-rules/master/`

`add_udev_rules.sh | sude bash`

#### Step 2. Add user to plugdev group

Modify the above **/etc/udev/rules.d/20-hw1.rules** rule to match your group or add the **OWNER="username"** parameter to each line, where **username** is your Linux user name. This adds your user to the **plugdev** group. Retry once you've done this.


---

# 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.enterprise.ledger.com/support/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.