Discord broken on IOS VPN #1718
Comments
|
This broke around January im wondering if its related to DNS over Quic. Also see thread https://forum.adguard.com/index.php?threads/adguard-dns-blocks-discord.41689/ |
|
@kenjiwing |
|
Mine does same thing. But it works sometimes. But I get the connecting hang thing sometimes also. Would a regular log help find the problem or is it need debug log |
|
@jordanelliott23 |
|
For me it takes awhile when it shows connecting then it eventually connects. But here is a log idk if it will show anything to help. But here https://ufile.io/arxv7x93 |
|
was trying to report via the submission form but it wouldn't let me click next after selecting dns filter. I too having lots of issues trying to connect to Discord with the vpn enabled |
|
I'm having this issue too even when just using the DNS profile, hope they fix this soon! Also, it only seems to happen on iOS. |
|
I have this issue as well. I can try and gather any logs that may help resolve the issue as well. I've found that sometimes clearing the app to restart it fixes the issue but not always. |
|
The "best" and easiest workaround I found was to simply disable the DNS profile in iOS settings (Settings > VPN & Network > DNS) which would allow the messages to load. This is obviously not ideal |
Requiring users to enable and disable the DNS filtering feature would be a poor fix. Ideally they update the app or DNS filters to work correctly. |
|
Quick question - does it depend on which DNS server you choose or is it happening with any DNS server (even with the System one)? |
It's hard to tell because swapping DNS choices in the app refreshes the network connection and causes Discord to reload. I've done a bit of back and forth switching with some of the larger chat groups that would require loading and it does seem that while connected to the adguard DNS servers it doesn't load but switching to system DNS it will then load. To be clear my method of testing is the following:
It's seems like there is some sort of throttling or request timeout happening while connected to the adguard DNS servers. As stated before, while staying connected to the adguard DNS servers sometimes I can clear Discord from recent applications and open it again and messages will load again. That is hit or miss though as sometimes it will just show "connecting" or not load messages. |
|
What if you choose a different server, not just AG DNS (try Cloudflare or Google for instance)? |
I tried that a few times and the same result as before. Messages begin to load one switching off the AdGuard DNS to any of the alternatives. |
Yeah, switching makes the messages load. Specially cloud-flare in my case |
|
And hopefully the last question - does it make a difference if you choose "AdGuard DNS Non-Filtering" configuration? The one that doesn't block anything. Sorry for that many questions, we just cannot reproduce it on our side. |
|
I'll switch mine over now and let you know if it hiccoughs at some time today (using app based dns vpn) |
|
it hasn't locked up on me all day on the no filtering adguard server, will try tommorrow too |
|
I had 1 lock up today however it also lined up with me leaving wifi and switching to 4G which was prone to bugger discord up for a bit anyway. Possibly safe to assume the issue is with the filtering versions in some way |
|
Next time this happens, could you please export AG logs and send the archive to Please mention the following in the email:
|
|
I've sent at least 3 exports now hope it helps
…Sent from my iPhone
On 26 Mar 2021, at 09:51, Andrey Meshkov ***@***.***> wrote:
Next time this happens, could you please export AG logs and send the archive to ***@***.***?
Please mention the following in the email:
Link to this issue
Exact time when it happened
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@nileplumb I've got the logs, thank you! What's strange is that there's nothing blocked at the time when the problem occurs for you. Could you please do one more thing for us? Let's use local DNS filtering (i.e. tracking requests will be blocked locally right on your device) but a different DNS resolver. Here's how to do that:
If the issue is reproduced again, please send us the logs one more time. |
I've only had 1 instance of discord having connection issues since changing but a simple restart of the discord app fixed that, it seems more stable either way |
|
just reporting still much more stable using the filters file + no filter dns |
|
I'm having this issue a lot on AdGuard DNS over QUIC via VPN. Here are my discord debug logs for reference. The requests seem to be timing out after 2 seconds. Like others have mentioned, no DNS requests appeared to be blocked for me either.
|
This immediately fixed my issue. I restarted my device after changing the settings for good measure. I've been using Discord all morning without any problems after months of constant trouble. I'm using Cloudflare Secure DNS now. Thanks for the suggestion. |
|
Yeah definitely acceptable connection times still using file filter instead of basic dns. So how can you further debug the vpn dns stuff |
|
We've made some changes to AdGuard DNS recently (we had a problem with Google serving us Chinese IPs). I wonder could it be that Discord was affected by the same issue? Could you please try AG DNS again just to check if the issue is still there? |
|
has there been an app update or just cycle the settings in current one?
… On 13 Apr 2021, at 16:22, Andrey Meshkov ***@***.***> wrote:
We've made some changes to AdGuard DNS recently (we had a problem with Google serving us Chinese IPs). I wonder could it be that Discord was affected by the same issue?
Could you please try AG DNS again just to check if the issue is still there?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
This seems to be an AdGuard DNS issue so no update is required. |
|
nope issue returned
…Sent from my iPhone
On 13 Apr 2021, at 17:20, Andrey Meshkov ***@***.***> wrote:
has there been an app update or just cycle the settings in current one?
This seems to be an AdGuard DNS issue so no update is required.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I also had the issue return.
On April 13, 2021 at 11:38:29 AM, nileplumb ***@***.***)
wrote:
… nope issue returned
Sent from my iPhone
> On 13 Apr 2021, at 17:20, Andrey Meshkov ***@***.***> wrote:
>
>
> has there been an app update or just cycle the settings in current one?
>
> This seems to be an AdGuard DNS issue so no update is required.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1718 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMACXDSJVNDAN5RJLFH74LTISFSLANCNFSM4XLTHEPA>
.
|
|
So let me please summarize:
Am I right? |
|
seems so, though I've not tested adguard family mode dns.
I had no issues on
Dns implementation: Adguard local
dns server: Adguard non filtering or cloud flare secure
dns filtering: Adguard dns filter file (previously linked)
…Sent from my iPhone
On 14 Apr 2021, at 09:54, Andrey Meshkov ***@***.***> wrote:
So let me please summarize:
First, there's no issue when you're using AdGuard DNS Non-Filtering configuration (i.e. no blocking on the server-side).
The issue is there with any other AdGuard DNS configuration (Default or Family), but it does not appear right away, it takes some time to re-appear.
The issue goes away if you use AdGuard DNS filter locally and use your ISP of CloudFlare DNS.
Am I right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
the issue more often presents itself when reopening/switching back to the app eg after a notification you might tap that to return to the chat you were in and then the content will rarely/never load, even after quitting discord and reloading
…Sent from my iPhone
On 14 Apr 2021, at 09:54, Andrey Meshkov ***@***.***> wrote:
So let me please summarize:
First, there's no issue when you're using AdGuard DNS Non-Filtering configuration (i.e. no blocking on the server-side).
The issue is there with any other AdGuard DNS configuration (Default or Family), but it does not appear right away, it takes some time to re-appear.
The issue goes away if you use AdGuard DNS filter locally and use your ISP of CloudFlare DNS.
Am I right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@nileplumb could you please email me at If you don't mind, I could share a test DNS endpoint with pretty much the same configuration as the normal AdGuard DNS. This way I could see what requests are made and what happens to them. |
|
of course |
|
so far so good on the test endpoint you senf me (unfortunately for debugging???)
… On 14 Apr 2021, at 10:06, Andrey Meshkov ***@***.***> wrote:
@nileplumb could you please email me at ***@***.***?
If you don't mind, I could share a test DNS endpoint with pretty much the same configuration as the normal AdGuard DNS. This way I could see what requests are made and what happens to them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Yeah, this is indeed unfortunate. Tbh, I am out of ideas for now, that server had pretty much the same configuration as the public one.. |
|
I believe discord has some sort of IP protection, I know webhook IFTTT recipes will fail for no reason other than lots of other users badly configured triggers going off causing some sort of block. Perhaps reach out to the discord devs to see what's possibly going on (they don't have ads so probably wouldn't be offended you asking), mind you I guess it wouldn't explain why it's only bring reported from ios?
… On 15 Apr 2021, at 21:46, Andrey Meshkov ***@***.***> wrote:
Yeah, this is indeed unfortunate. Tbh, I am out of ideas for now, that server had pretty much the same configuration as the public one..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Just had a lot of connection issues perhaps related? Do you need my logs or can you grab?
19th April 08:58-09:02 UTC+1
|
|
@nileplumb probably just a glitch, I see nothing special in the logs. Note that this is a test endpoint, it sometimes gets restarted/updated randomly. |
|
happened again approximately 12:07 onwards still can't connect now
…Sent from my iPhone
On 19 Apr 2021, at 09:09, Andrey Meshkov ***@***.***> wrote:
@nileplumb probably just a glitch, I see nothing special in the logs. Note that this is a test endpoint, it sometimes gets restarted/updated randomly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@nileplumb 12:07 what time zone? In fact, I see one strange thing in the DNS log, it returns a suspicious HTTPS record for
|
|
@nileplumb we've been able to identify the problem and the fix has just been rolled out. Thank you so much for helping us, this was really valuable. |
|
Cool good to switch back to iOS QUIC app based dns without filter files now? |
|
@nileplumb yep, it should work just okay |
adguard-bot
added
Resolution: Fixed
Status: Resolved
Status: Closed
and removed
Version: AdGuard v4.2
Status: Resolved
labels
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
Adguard for IOS v 4.0.4 (588)
Iphone 11 Pro 14.5 beta (also broke with 14.4)
Discord
Expected Behavior
Actual Behavior
When you open discord it should work. Instead it hangs at connecting. If you disable adguard it works just fine.
Screenshots
Not needed it simply goes to connecting with discord open.
Additional Information
As soon as you disable the adguard vpn/protection discord works fine. I dont see any blocks in the DNS list.
The text was updated successfully, but these errors were encountered: