-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Snap service fails to start on boot but can be started manually #7081
Comments
More context, it makes not diff if U purge and fresh install under another port, ip etc boot log
manual snap service start adguard-home
|
Some additional questions:
|
Version v0.107.51 And yes the ip is static for the server. Adguard is running and active. I tried setting different ports for the web console seems to be a race condition at the interface because if I expose 0.0.0.0:53 instead of 192.168.1.2:53 udp this does not happen. Although I do not want to expose :53 in all interfaces I only want to use services over eno1 or other enoX but not docker, local or any other virtual vpn etc. |
The problem only happens when selecting both web console and 53 UDP over eno1 |
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)
Ubuntu 24
Installation
Snapcraft
Setup
On one machine
AdGuard Home version
latest-snap
Action
Expected result
service to start on boot
Actual result
fails
Additional information and/or screenshots
ubuntu 24.0
The text was updated successfully, but these errors were encountered: