[GH-ISSUE #718] Breaks with encrypted DNS on Big Sur #713

Open
opened 2026-03-03 19:21:14 +03:00 by kerem · 6 comments
Owner

Originally created by @florianbuerger on GitHub (Dec 6, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/718

Proxyman version?

Version 2.14.1 (21410)

macOS Version?

11.0.1 (20B29)

Steps to reproduce

  1. Install configuration profile that configures the native encrypted DNS feature new to Big Sur (I am using NextDNS), other examples → https://github.com/paulmillr/encrypted-dns
  2. Launch Proxyman

Now all traffic is blocked. The only way to use Proxyman now is to disable the networks service that was installed by the profile in System Preferences → Network.

I don't know how the new encrypted DNS works internally or if it is even possible for Proxyman to work in such a setup. Happy to provide more info if needed 😊

Originally created by @florianbuerger on GitHub (Dec 6, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/718 ### Proxyman version? Version 2.14.1 (21410) ### macOS Version? 11.0.1 (20B29) ### Steps to reproduce 1. Install configuration profile that configures the native encrypted DNS feature new to Big Sur (I am using [NextDNS](https://apple.nextdns.io)), other examples → https://github.com/paulmillr/encrypted-dns 2. Launch Proxyman Now all traffic is blocked. The only way to use Proxyman now is to disable the networks service that was installed by the profile in `System Preferences → Network`. I don't know how the new encrypted DNS works internally or if it is even possible for Proxyman to work in such a setup. Happy to provide more info if needed 😊
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 7, 2020):

Thanks for the info. It looks like Proxyman doesn't handle DNS over HTTPS properly. I will check it today 👍

<!-- gh-comment-id:739616126 --> @NghiaTranUIT commented on GitHub (Dec 7, 2020): Thanks for the info. It looks like Proxyman doesn't handle DNS over HTTPS properly. I will check it today 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 8, 2020):

I'm not sure why Proxyman doesn't work with DNS over HTTPS, but the Charles app has the same issue.

With Charles, I can visit google.com, but couldn't open github.com or some of my websites.

Screen Shot 2020-12-08 at 09 27 18
<!-- gh-comment-id:740319492 --> @NghiaTranUIT commented on GitHub (Dec 8, 2020): I'm not sure why Proxyman doesn't work with DNS over HTTPS, but the Charles app has the same issue. With Charles, I can visit google.com, but couldn't open github.com or some of my websites. <img width="500" alt="Screen Shot 2020-12-08 at 09 27 18" src="https://user-images.githubusercontent.com/5878421/101430453-9aeadd80-3937-11eb-9356-cc31f529e0f4.png">
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 8, 2020):

@florianbuerger can you try again? At the first time, Proxyman didn't work, but after restarting Proxyman, It's working now

Video: https://www.dropbox.com/s/imzjz7i0do8z6me/DNS_Over_HTTPS_1.mov?dl=0

Technically, DNS over HTTPS is just an HTTPS request, so as soon as you don't enable SSL Proxying on this domain, it should work (Proxyman just forward bytes between the client <-> Server)

<!-- gh-comment-id:740323767 --> @NghiaTranUIT commented on GitHub (Dec 8, 2020): @florianbuerger can you try again? At the first time, Proxyman didn't work, but after restarting Proxyman, It's working now Video: https://www.dropbox.com/s/imzjz7i0do8z6me/DNS_Over_HTTPS_1.mov?dl=0 Technically, DNS over HTTPS is just an HTTPS request, so as soon as you don't enable SSL Proxying on this domain, it should work (Proxyman just forward bytes between the client <-> Server)
Author
Owner

@florianbuerger commented on GitHub (Dec 8, 2020):

At the first time, Proxyman didn't work, but after restarting Proxyman, It's working now

Interesting. You are right, when I quit Proxyman and restart, it works. Strange that I didn't try that before 😄 Any idea why that is?

Anyway, thanks for looking into it. Launching Proxyman twice isn't a big deal, way easier than going into System Preferences and toggle the network service.

<!-- gh-comment-id:740507634 --> @florianbuerger commented on GitHub (Dec 8, 2020): > At the first time, Proxyman didn't work, but after restarting Proxyman, It's working now Interesting. You are right, when I quit Proxyman and restart, it works. Strange that I didn't try that before 😄 Any idea why that is? Anyway, thanks for looking into it. Launching Proxyman twice isn't a big deal, way easier than going into System Preferences and toggle the network service.
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 8, 2020):

I'm not sure what wrong with it. I'm still able to reproduce the bug with a 50% chance. Sometimes it works, sometimes it doesn't.

I opened a ticket and seek help from the Swift-NIO team (https://github.com/apple/swift-nio-examples/issues/65). I will make sure fix it 100% 😄

<!-- gh-comment-id:740512968 --> @NghiaTranUIT commented on GitHub (Dec 8, 2020): I'm not sure what wrong with it. I'm still able to reproduce the bug with a 50% chance. Sometimes it works, sometimes it doesn't. I opened a ticket and seek help from the Swift-NIO team (https://github.com/apple/swift-nio-examples/issues/65). I will make sure fix it 100% 😄
Author
Owner

@Lukasa commented on GitHub (Dec 8, 2020):

Hey folks, while we're diagnosing things over here it would be extremely useful if you could provide sample projects and file reports using Feedback Assistant. This will give us more info to work with.

<!-- gh-comment-id:740791289 --> @Lukasa commented on GitHub (Dec 8, 2020): Hey folks, while we're diagnosing things over here it would be _extremely_ useful if you could provide sample projects and file reports using Feedback Assistant. This will give us more info to work with.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#713
No description provided.