config: clarify host/port for bitcoind config

Nobody has claimed this yet.

Running the `frcli audit` command fails somehow arbitrarily. For some start/end times it works fine, for some it doesn't and returns a 401 error.

I can audit reports for any time of the year (months, quarter of, half of and full year).

Running `frcli audit --loop-category --start_time 1672527600 --end_time 1680299999` for the first quarter of 2023 works just fine. But `frcli audit --loop-category --start_time 1680300000 --end_time 1688162399` for the second quarter fails with the error:
`[frcli] rpc error: code = Unknown desc = status code: 401, response: ""`

Running it without `--loop-category` has the same behavior.

But running just `frcli audit` works just fine.

See above. We are running faraday in Kubernetes.

Standalone.

-

CLI

We build our own image, currently we are using `0.2.11-alpha`

Runs on a kubernetes cluster.

Runs on a kubernetes cluster.

I can't find a `faraday.log` file, where do I get it?

Start at the `frcli audit` command and compare the successful and failing `--start_time`/`--end_time` ranges, including the effect of `--loop-category`. Then trace the request and authentication path in the Kubernetes deployment and inspect the available logs around the 401 response. Done means identifying why some date ranges fail and documenting or fixing the behavior so equivalent audit ranges work consistently.

Written by the indexing model from the issue text.