We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.)
Custom (please mention in the description)
Docker
On one machine
v0.107.34
Since the last update of adguard, my docker container status shows "warning" Platform: Synology Docker (container Manager)
Stauts "OK" instead of warning
Stauts "warning" instead of ok
No response
The text was updated successfully, but these errors were encountered:
Nope, you didn't search. The issue is literally pinned at the top of the issues list …
See: #6003
Sorry, something went wrong.
sorry, didnt see this :(
No branches or pull requests
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)
Custom (please mention in the description)
Installation
Docker
Setup
On one machine
AdGuard Home version
v0.107.34
Action
Since the last update of adguard, my docker container status shows "warning"
Platform: Synology Docker (container Manager)
Expected result
Stauts "OK" instead of warning
Actual result
Stauts "warning" instead of ok
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered: