AdguardTeam / AdguardTeam/AdGuardDNS

AdGuard DNS Issue⁩ With QR In Windows

未關閉
#1,058 6 則留言 0 個 reaction 已指派 1 人 已被 @Chinaski1 認領 在 GitHub 檢視
bug Priority: P4 waiting for data
主要語言
Go
星號
952
分支
82
PR 合併指標
30 天內沒有已合併 PR

描述

Hello,

I am facing a persistent issue where QR code-based authentication (such as web service logins) consistently fails and hangs when my Windows device uses my customized AdGuard DNS-over-HTTPS (DoH) profile.

Here are the technical details:
The issue immediately disappears as soon as l disable the DoH profile and revert to a standard connection.

During the failed QR login attempts, the AdGuard Query Log shows no blocked domains (all related requests are marked as "Processed" or do not appear at all).

This indicates that a backend WebSocket, persistent session handshake, or real-time API endpoint required for session synchronization is either being silently dropped, ignored, or affected by the filtering rules.

![](https://adguard.zendesk.com/attachments/token/pVspve7mtALtpFdWf7o8FVOla/?name=image0.png)

### Platform

Windows

### Protocol

DNS-over-HTTPS

### Do you use AdGuard app?

Yes I am

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。