# Unix socket does not exist (Linux)

Error: `No such file or directory (os error 2)` when trying to connect to a location.

The socket at `/var/run/defguard.socket` is created by the `defguard-service` background service. If this service is not running, the socket does not exist and the GUI client cannot establish a connection.

### Fix

Run the following to enable and start the background service:

```sh
# Reload systemd to pick up the service file
sudo systemctl daemon-reload

# Enable the service to start on boot
sudo systemctl enable defguard-service

# Start it immediately
sudo systemctl start defguard-service
```

Verify the service is running:

```sh
systemctl status defguard-service
```

If the service fails to start, check its logs:

```sh
journalctl -u defguard-service -n 100
```


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.defguard.net/support-1/troubleshooting-guides/desktop-client/unix-socket-does-not-exist-linux.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.