-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adguard log error [info] auth: invalid Basic Authorization value #6357
Comments
The message itself most likely means that someone is trying to hack into your AGH. These auth messages should also show the remote address so that it's easier for admins to ban them, but for some reason this one doesn't. @schzhn, please make sure that all logging in the auth unit includes the remote address. There is already the |
Updates #6357. Squashed commit of the following: commit 0d37544 Merge: 61858bd 52713a2 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Nov 3 14:47:10 2023 +0300 Merge branch 'master' into 6357-auth-log-remote-ip commit 61858bd Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Nov 3 14:44:58 2023 +0300 all: upd chlog commit 1eef672 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Thu Nov 2 19:20:41 2023 +0300 home: imp code commit 2956aed Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Thu Nov 2 16:10:07 2023 +0300 home: imp docs commit ca0f53d Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Tue Oct 31 15:08:37 2023 +0300 home: imp code commit 6b11b46 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Oct 27 19:45:55 2023 +0300 home: auth log remote ip
We've pushed the edge release containing the improved logging. |
@lordraiden, now the auth log messages should contain the remote address. |
Updates AdguardTeam#6357. Squashed commit of the following: commit 0d37544 Merge: 61858bd 52713a2 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Nov 3 14:47:10 2023 +0300 Merge branch 'master' into 6357-auth-log-remote-ip commit 61858bd Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Nov 3 14:44:58 2023 +0300 all: upd chlog commit 1eef672 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Thu Nov 2 19:20:41 2023 +0300 home: imp code commit 2956aed Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Thu Nov 2 16:10:07 2023 +0300 home: imp docs commit ca0f53d Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Tue Oct 31 15:08:37 2023 +0300 home: imp code commit 6b11b46 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Oct 27 19:45:55 2023 +0300 home: auth log remote ip
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
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)
Linux, AMD64 (aka x86_64)
Installation
Docker
Setup
On one machine
AdGuard Home version
Version: v0.107.40
Action
Expected result
Shouldn't get errors in the logs
Actual result
2023/10/26 17:31:21.105993 [info] AdGuard Home, version v0.107.40
2023/10/26 17:31:21.110687 [info] tls: using default ciphers
2023/10/26 17:31:21.111453 [info] safesearch default: disabled
2023/10/26 17:31:21.120349 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
2023/10/26 17:31:21.120456 [info] auth: initialized. users:1 sessions:1
2023/10/26 17:31:21.120482 [info] AdGuard Home updates are disabled
2023/10/26 17:31:21.120496 [info] web: initializing
2023/10/26 17:31:21.242427 [info] dnsproxy: cache: enabled, size 4096 b
2023/10/26 17:31:21.242461 [info] dnsproxy: max goroutines is set to 50
2023/10/26 17:31:21.242575 [info] AdGuard Home is available at the following addresses:
2023/10/26 17:31:21.242595 [info] go to http://10.10.40.5:80
2023/10/26 17:31:21.242624 [info] clients: processing addresses
2023/10/26 17:31:22.312598 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:22.367718 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:22.425836 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:22.484493 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:22.550269 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:24.268098 [info] dnsproxy: starting dns proxy server
2023/10/26 17:31:24.268118 [info] Ratelimit is enabled and set to 20 rps
2023/10/26 17:31:24.268121 [info] The server is configured to refuse ANY requests
2023/10/26 17:31:24.268123 [info] dnsproxy: cache: enabled, size 8388608 b
2023/10/26 17:31:24.268128 [info] dnsproxy: max goroutines is set to 50
2023/10/26 17:31:24.268138 [info] dnsproxy: creating udp server socket 10.10.40.5:53
2023/10/26 17:31:24.268212 [info] dnsproxy: listening to udp://10.10.40.5:53
2023/10/26 17:31:24.268218 [info] dnsproxy: creating tcp server socket 10.10.40.5:53
2023/10/26 17:31:24.268245 [info] dnsproxy: listening to tcp://10.10.40.5:53
2023/10/26 17:31:24.268324 [info] dnsproxy: entering udp listener loop on 10.10.40.5:53
2023/10/26 17:31:24.268345 [info] dnsproxy: entering tcp listener loop on 10.10.40.5:53
2023/10/26 17:31:29.238197 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:29.290646 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:29.343979 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:29.395334 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:29.446601 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:39.240820 [info] auth: invalid Basic Authorization value
2023/10/26 17:31:39.293832 [info] auth: invalid Basic Authorization value
Additional information and/or screenshots
I have a similar instance, the compose is exactly the same and I don't get those errors in the logs.
The text was updated successfully, but these errors were encountered: