Skip to content
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

Closed
lolka4toli opened this issue Apr 29, 2021 · 7 comments
Closed

AdGuard fails to launch itself on the system startup #864

lolka4toli opened this issue Apr 29, 2021 · 7 comments

Comments

@lolka4toli
Copy link

Steps to reproduce

  1. Restart your Mac
  2. Log into your profile
  3. Face a crash

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

@Chinaski1
Copy link
Member

Chinaski1 commented Apr 30, 2021

A similar issue is also discussed on AdGuard Forum.
One of the users sent the log files.
Archive attached to the task

@stale
Copy link

stale bot commented Sep 19, 2021

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.

@stale stale bot added the Wontfix label Sep 19, 2021
@Chinaski1 Chinaski1 removed the Wontfix label Sep 20, 2021
@LesterJitsi
Copy link

LesterJitsi commented Nov 4, 2021

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.

@stale
Copy link

stale bot commented Mar 2, 2022

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.

@stale stale bot added the Wontfix label Mar 2, 2022
@vsc42
Copy link

vsc42 commented Mar 6, 2022

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....

@Chinaski1
Copy link
Member

Hello @vsc42

OS version: 12.3 Beta / 11.6 BigSur
AdGuard for macOS: 2.7.0.1094 release (CL-1.8.276, DNS-1.6.72)
Little snitch version: Version 5.3.2 (6229)

The issue is not reproduced.
Please specify in what mode Little Snitch works.
Maybe there are some other features to consider?

In any case, you can send logs we tried to figure out the causes of the issue. (apple@adguard.com)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@LesterJitsi @adguard-bot @vsc42 @Chinaski1 @lolka4toli and others