"Error: control/stats | Couldn't get statistics data

hl2guide commented 2 weeks ago

Prerequisites

[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Windows, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.54

Action

visiting main index page.

Expected result

Page loads without error.

Actual result

red message appears:

Error: control/stats | Couldn't get statistics data | 500

Additional information and/or screenshots

My browser's console output:

(I have hidden my actual IP using '#########')

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. #########
react-i18next:: It seems you are still using the old wait option, you may migrate to the new useSuspense behaviour. main.d279be67d6cfecf586fe.js:2:2637998
Error: control/stats | Couldn't get statistics data
 | 500
    makeRequest http://#########/main.d279be67d6cfecf586fe.js:2
main.d279be67d6cfecf586fe.js:2:2601316
Error: control/stats | Couldn't get statistics data
 | 500
    makeRequest http://#########/main.d279be67d6cfecf586fe.js:2
main.d279be67d6cfecf586fe.js:2:2601316
Error: Promised response from onMessage listener went out of scope ExtensionMessagingService.js:89:34
Error: control/stats | Couldn't get statistics data
 | 500
    makeRequest http://#########/main.d279be67d6cfecf586fe.js:2
main.d279be67d6cfecf586fe.js:2:2601316

Rootax commented 1 week ago

Same thing here, Windows 11. No problem on Debian.

Rootax commented 1 week ago

It's a file system permission problem. After a reboot, Adguard doesn't even start (access denied). I have to change the ntfs permissions to something that make sense for the service to start. Worse thing, permissions don't stuck after a reboot for whateever reason. Pretty sure it's caused by the "improvement" of safety for the windows version from last version.

Fanatic9 commented 1 week ago

It's a file system permission problem. After a reboot, Adguard doesn't even start (access denied). I have to change the ntfs permissions to something that make sense for the service to start. Worse thing, permissions don't stuck after a reboot for whateever reason. Pretty sure it's caused by the "improvement" of safety for the windows version from last version.

same thing happened to me, had to completely remove adguard as it wasn't functioning normally anymore EDIT: reverted back to AdGuard Home v0.107.52 and everything seems to back to normal , no more query log errors , cmd services works again and no more perm check errors. will never be updating again until this issue is fixed but thankfully older build is available and still works.

AdguardTeam / AdGuardHome