-
Notifications
You must be signed in to change notification settings - Fork 15
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 fails to launch itself on the system startup #864
Comments
A similar issue is also discussed on AdGuard Forum. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue does still exist on 10.14.6. It seems to be "solved" by disabling DNS protection. I filed two support requests yesterday. On first occurring I got a dialog box warning that Adguard hadn't started properly. I had no connection and at first I simply re-entered Cloudflare DNS in System Prefs > Network > Advanced. After a reboot Adguard started up but I could connect to the Internet only disabling DNS protection. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The problem is still occurring with MacOS 12.2.1 and AdGuard Application version 2.7.0.1094 release (CL-1.8.276, DNS-1.6.72), where the problem occurs on one of three identically configuration systems. Notable is that when LittleSnitch is loaded the problem presents on boot. It appears there is a conflict with LittleSnitch. If AdGuard is set to not load on boot, but is started after the machine is stable AdGuard loads without issue. While I have tried to find why only one of the three systems has this issue, nothing in the logs points to an answer. Additionally debugging is difficult given debug logging is always disabled on boot, even if enable prior to a reboot. Thus detailed logging, as required by AdGuard, has not been provided. I should add resetting AdGuard's preferences to default doesn't help. Nor does cleaning out AdGuard and doing a clean install. Finally using the nightly yields the same results. Perhaps it would be helpful if there was a way to force AdGuard debug logging at boot.... |
Hello @vsc42 OS version: 12.3 Beta / 11.6 BigSur The issue is not reproduced. In any case, you can send logs we tried to figure out the causes of the issue. (apple@adguard.com) |
Steps to reproduce
Expected behavior
AdGuard should start as always
Actual behavior
AdGuard fails to autostart, but after that it launches fine by a user
Customer ID/logs
Collecting.
Spotted on macOS versions:
10.12.6
10.14.6
11.3
The text was updated successfully, but these errors were encountered: