# Attributes file path not set

### Problem

If you try to update labels are tags over the API or the user interface, you might get the “error client error: attributes file path not set”.

Updating attributes remotely requires that you enable this feature once in the `rport.conf` file on the client. This can't be done remotely. 

<figure><img src="/files/XTEwezgFiNepqoLz4K4c" alt="" width="563"><figcaption><p>Error on changing labels and tags</p></figcaption></figure>

### Solution

Make sure the client runs rport version 0.9.12 or higher.

Log in to the client via SSH or Remote Desktop and open `/etc/rport/rport.conf` on Linux or `C:\Program Files\rport\rport.conf` on Windows with a text editor.&#x20;

Inside the `[client]` section, insert or activate the following lines. Depending on the version, the lines are already present but disabled.&#x20;

```
  ## A list of of tags and labels to give your clients attributes maintained in a separate file.
  ## See https://oss.rport.io/advanced/attributes/
  #attributes_file_path = "/var/lib/rport/client_attributes.json"
  #attributes_file_path = "C:\Program Files\rport\client_attributes.json"
  ## Alternatively you can specify tags with the line below if {attributes_file_path} is not set.
  #tags = ['win', 'server', 'vm']
```

Make sure one of the line starting with `attributes_file_path` is active (no hash sign `#` in front of it). Make sure the line starting with `tags` is disabled by putting a hash sign.

Restart the rport client after making the changes. Use `service rport restart` on Linux or `restart-service` on Windows.

{% hint style="danger" %}
Be careful when **restarting rport if you are connected through an rport tunnel**. The restart would kill the tunnel and rport will not come up afterwards.&#x20;

👉 Follow [these instruction](/need-help/troubleshoot-common-problems/restart-rport-through-a-tunnel.md) to restart rport safely.
{% endhint %}


---

# 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://kb.rport.io/need-help/troubleshoot-common-problems/attributes-file-path-not-set.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.