hiddify-next
hiddify-next copied to clipboard
Unable to use VPN mode on MacOS
Search first
- [X] I searched and no similar issues were found
What Happened?
After changing the Config Options to use VPN as service mode, when turning it on this error pops up:
Missing Privilege
VPN mode requires administrator privileges ....
I tried opening it using sudo or lunching with holding control but nothing worked.
Reproduce the Bug
** On Mac ** Go to Settings Go to Config Options select Service Mode select VPN Go to Home and turn it on
Expected Behavior
No response
Version
0.11.0
Platform/OS
macOS
Additional Context
No response
Relevant log output
No response
Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
روی اندروید هم با کلاینت جدید نمیشه وصل شد
在 2022 m1macbookair 上不起作用,
Same issue
Same I even tried to run it as sudo but still nothing! The tun mode won't start
I'm not sure this is a good thing or not but, for using vpn mode in mac os you can use this command :
sudo "/Applications/Hiddify Next.app/Contents/MacOS/Hiddify Next"
Execute this command at your own risk
@hiddify-com if this command is not allowed please let me know
Hiddify Next should consider altering the implementation of administrator privileges. Running an app with sudo in macOS seems unconventional; instead, utilizing a privileges helper is a more standard approach. Please refer to SMJobBless or SMAppService for guidance.
This issue is fixed. Pls update your app
This issue is fixed. Pls update your app
Dear, I'm using v0.14.20 and the issue still exists. The solution by mrjavadseydi is working for me:
I'm not sure this is a good thing or not but, for using vpn mode in mac os you can use this command :
sudo "/Applications/Hiddify Next.app/Contents/MacOS/Hiddify Next"Execute this command at your own risk @hiddify-com if this command is not allowed please let me know
The issue exists in versions v0.14.20 and v0.16.0.dev
v1.1.1 still has this problem. Permissions cannot be obtained in MacOS14.1.1
v1.1.1 still has this problem.
in the v1.1.1 still has this problem
I still have this problem with version 1.1.1
The same problem with version 2.0.5
Any updates on this?