Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPN's SOCKS5 Compatibility issue for 1.4.9 Beta #1334

Closed
Noir16 opened this issue Oct 3, 2023 · 4 comments
Closed

VPN's SOCKS5 Compatibility issue for 1.4.9 Beta #1334

Noir16 opened this issue Oct 3, 2023 · 4 comments
Labels
documentation pending ATTRIBUTE: some part of this issue still needs to be documented in the wiki or somewhere else in/compatibility TYPE: a report about in/compatibility stale ATTRIBUTE: this issue has not had recent activity

Comments

@Noir16
Copy link

Noir16 commented Oct 3, 2023

What worked?

The behavior of pass-through SOCKS5, a feature of VPNs. (ex. Mullvad VPN, IVPN)

What did not work?

Some VPNs come with SOCKS5 functionality, but if you update to 1.4.9, you'll get a DNS horizon violation error.

Additional information

How to fix it:

  1. In the search bar at the top of the settings, type in Enforce Global/Private Split-View.
  2. The issue was resolved by disabling the Enforce Global/Private Split-View [Developer].
@Noir16 Noir16 added the in/compatibility TYPE: a report about in/compatibility label Oct 3, 2023
@github-actions
Copy link

github-actions bot commented Oct 3, 2023

Hey @Noir16, thank you for reporting on a compatibility.

We keep a list of compatible software and user provided guides for improving compatibility in the wiki - please have a look there.
If you can't find your software in the list, then a good starting point is our guide on How do I make software compatible with Portmaster.

If you have managed to establish compatibility with an application, please share your findings here. This will greatly help other users encountering the same issues.

@Raphty
Copy link
Member

Raphty commented Oct 3, 2023

Thanks for letting us know!

@Raphty Raphty added the documentation pending ATTRIBUTE: some part of this issue still needs to be documented in the wiki or somewhere else label Oct 3, 2023
Copy link

github-actions bot commented Dec 6, 2023

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Dec 6, 2023
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation pending ATTRIBUTE: some part of this issue still needs to be documented in the wiki or somewhere else in/compatibility TYPE: a report about in/compatibility stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Development

No branches or pull requests

2 participants