# Fixing the jq parse error

If you encounter the following error while running the `helmut-snapshot` command:

```
jq: parse error: Invalid numeric literal at line 1, column 10
```

this may be caused by a **missing local proxy bypass configuration (`no_proxy`)**.\
Without this configuration, requests to `localhost` may be routed through a corporate proxy instead of directly to the local service.

{% hint style="success" %}
For detailed instructions on configuring proxy settings for both the host system and Docker, please refer to the article “[Docker & Ubuntu Proxy](/helmut4-releases/getting-started/additional-configurations/communication-ssl-proxy-and-ports/docker-and-ubuntu-proxy.md)”**.**
{% endhint %}

***

### 1. Verify the Current Proxy Configuration

Run the following command to check whether a `no_proxy` configuration is present:

```bash
env | egrep -i 'http_proxy|https_proxy|no_proxy'
```

Example output:

```
https_proxy=http://proxy.company.de:8081
http_proxy=http://proxy.company.de:8081
```

As shown above, **no `no_proxy` entry is configured**, meaning even local connections may be sent through the proxy.

***

### 2. Add a Local `no_proxy` Configuration

Create a profile script to define the local proxy bypass:

```bash
cat >/etc/profile.d/no_proxy_local.sh <<'EOF'
export NO_PROXY="127.0.0.1,localhost,::1"
export no_proxy="$NO_PROXY"
EOF
```

This ensures that connections to local services (`localhost`, `127.0.0.1`, IPv6 `::1`) bypass the proxy.

***

### 3. Apply the Configuration

Disconnect and reconnect your **SSH session** so the new environment variables are loaded.

***

### 4. Verify the Updated Configuration

Run the verification command again:

```bash
env | egrep -i 'http_proxy|https_proxy|no_proxy'
```

Expected output:

```
no_proxy=127.0.0.1,localhost,::1
https_proxy=http://proxy.company.de:8081
NO_PROXY=127.0.0.1,localhost,::1
http_proxy=http://proxy.company.de:8081
```

Once `NO_PROXY` / `no_proxy` is configured, the `helmut-snapshot` command should work correctly.


---

# 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.helmut.de/helmut4-releases/support/debug-or-log-collection/helmut4-server/fixing-the-jq-parse-error.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.