Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Since v7.15, the service cannot start normally if it fails to connect to 20.189.79.72:123 via UDP #4868

@SpeedPartner

Description

@SpeedPartner

AdGuard version

7.15 (4385) (build 4385, CL 1.12.78)

Browser version

Microsoft Edge (118.0.2088.61)

OS version

Windows 11 / 22H2 / 22621.2428

What filters do you have enabled?

No response

What Stealth Mode options do you have enabled?

No response

Support ticket ID

822784 (Closed) / 827765

Issue Details

My network provider may have blocked port 123, which prevents me from starting the Adgurd service normally after updating to v7.15, but it works fine when I roll back to v7.14;

I found out through network diagnosis that Adguard tries to connect to 20.189.79.72:123 via UDP when starting (possibly resolved from api.adguard.org), and if the connection fails, it cannot start the Adgurd service successfully;

After testing, I can solve this issue by using port forwarding, or changing the network environment (network proxy).

Expected Behavior

Change or cancel this behavior of Adguard at startup; to solve the issue of being unable to start the service normally when Adguard fails to connect to 20.189.79.72:123 via UDP.

Screenshots

No response

Additional Information

No response

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions