mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #1484] Internal Error (999) on all requests when using NextDNS Profile #1476
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1476
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ikurek on GitHub (Jan 2, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1484
Originally assigned to: @NghiaTranUIT on GitHub.
Description
I'm using NextDNS as a dedicated DNS service, and the configuration is done by installing a configuration profile generated by NextDNS on MacOD device. I've noticed, that when the profile is active, Proxyman can't process any request correctly. This may also be a case for other DNS providers that may use configuration profiles (f.e. AdGuard DNS)
Steps to Reproduce
Current Behavior
All requests return with error code 999 and
Internal Errormessage. When NextDNS profile is removed, everything works without issuesExpected Behavior
Requests are processed normally
Environment
@NghiaTranUIT commented on GitHub (Jan 2, 2023):
Hey @ikurek I've downloaded the NextDNS and it seems it isn't compatible with Proxyman. Tried Wireshark / Charles Proxy, and the same issue occurs.
The internal logs show that Proxyman could not resolve the DNS, so the request is a timeout -> 999 Error.
Unfortunately, Google doesn't show any suggestions on how to fix it.
@ikurek commented on GitHub (Jan 2, 2023):
@NghiaTranUIT Thanks for checking my case out so fast! That's a shame this probably can't be fixed. I think it may be a good idea to have a note about this in the docs then 🙂
@NghiaTranUIT commented on GitHub (Jan 2, 2023):
Sure, I will NextDNS into the Not Compatible List 👍
@twttr commented on GitHub (Apr 11, 2025):
To make Proxyman and NextDNS work simultaneously, you need to exclude the DNS domain in Proxyman settings.