Docker error: Failed to run: Failed to send query data

[URBANsUNITED]

Hi!

I am running the latest docker and the latest adguard home version (0.107.29) and can't get it working:

Log:

Welcome to AdGuardian Terminal Edition!
Terminal-based, real-time traffic monitoring and statistics for your AdGuard Home instance
For documentation and support, please visit: https://github.com/lissy93/adguardian-term
Starting initialization checks...
ADGUARD_IP is set to 192.168.0.251
ADGUARD_PORT is set to 3003
ADGUARD_USERNAME is set to xxx
ADGUARD_PASSWORD is set to ******
Verifying connection to your AdGuard instance...
AdGuard connection successful!
Failed to run: Failed to send query data
Error: Failed to run: Failed to send query data

Any idea what it could be?

Thanks

URBANsUNITED

[Ellargo333]

Same issue!

[Lissy93]

Could you confirm what version of AdGuard Home you're running? I know that prior that v0.107.29 they had a different API schema

[Ellargo333]

Using latest Version: v0.107.29

[URBANsUNITED]

Yeah! Me too on v0.107.29
Issue stays with 1.3 release

[louispires]

Exact same issue here.

Also running the latest version of AdGuard Home

[PsHyC0]

same issue. Running latest version.

[louispires]

I have multiple AdGuards (Unraid Docker and Proxmox Container)

Could it be due to my AdGuard running on Port 80?

Both throw the same error:

Starting initialization checks...
ADGUARD_IP is set to 10.0.0.10
ADGUARD_PORT is set to 80
ADGUARD_PROTOCOL is set to http
ADGUARD_USERNAME is set to louis
ADGUARD_PASSWORD is set to ******
Verifying connection to your AdGuard instance...
AdGuard (v0.107.29) connection successful!
Failed to run: Failed to send query data
Error: Failed to run: Failed to send query data

[PsHyC0]

Got all excited when I saw a new release....still have same problem.

[mariushosting]

@Lissy93 There is any update on this? :-)

[sochartgit]

Any update please, same problem here ?

[sochartgit]

Is this project still alive ? Most issues signaled months ago, no replies.

[frostworx]

I recently found this project and unfortunately can confirm this old problem.

Does anybody use an alternative solution and wants to share? :)

I only found this hint (likely some of you did so a long time ago ;)):

https://www.reddit.com/r/Adguard/comments/15zckqs/comment/jxiwpw9/

 Looks like the default configuration stores the last 1000 query log entries in memory before writing it to a file, so that's why the difference in the data.

To remove this and get query logs updated as soon as there's a new query you need:

    Stop AdGuard by doing ./AdGuardHome -s stop

    Edit AdGuardHome.yaml

    Change size_memory: 1000 to size_memory: 0 inside the querylog: section

    Save file and start AdGuard again ./AdGuardHome -s stop

With this you will get the querylog.json file updated to the second 

Likely a good idea to have the file on a ram disc then :)

Not really a fully fledged alternative to this project, but maybe a neat option for a quick cmdline check.

[frostworx]

sorry for the noise :)

adding

      - type: bind
        source: /dev/shm/querylog.json
        target: /opt/adguardhome/work/data/querylog.json
        read_only: false

to volumes:
in the docker-compose.yml works fine (when the file /dev/shm/querylog.json exists; I simply (re)create it with a touch when (re-)starting the container)

(mounting
- ./data/work:/opt/adguardhome/work
before works fine as well):

    volumes:
      - ./data/config:/opt/adguardhome/conf # app configuration
      - ./data/work:/opt/adguardhome/work # app working directory
      - type: bind
        source: /dev/shm/querylog.json
        target: /opt/adguardhome/work/data/querylog.json
        read_only: false

now you can simply tail -f the file from shm on the host and pipe it through jq

tail -f /dev/shm/querylog.json | jq -r '[(.T[0:19]|tostring|gsub("T"; " ")), .IP, .CP, .Result.IsFiltered, .QT, .QH]|@tsv'

I shamelessly copied the jq args from

AdguardTeam/AdGuardHome#1428

kudos to @JoseGalRe :)