Arch Linux User Repository

i used sudo torguard

but it's won't connect with stealth or stunnel or openconnect

give me this error: Could not connect to the VPN management socket. Please check your firewall settings!

and: Error while starting STunnel STunnel could not be started

btw i disable firewall but still got those errors

@dramm i did it with sudo, something is wrong.

Make sure you are running it with sudo.

i cant make app connect on ManjaroLinux i got errors about firewall and stunnel not start

i disabled firewall and still same issue, i talked to TG team and they said they arent support manjaro officialy

Torguard has an Arch installation package you can download directly from their website. Current version is 3.92.0. Upstream URL should be https://torguard.net

I had to use Exec=/usr/bin/pkexec /opt/torguard/bin/torguard or as you suggest: Exec=pkexec /opt/torguard/bin/torguard. pkexec would not work for me with the torguard link in /usr/bin.

If pkexec is in your PATH (and it should) you don't need /usr/bin/pkexec, just pkexec

My system has pkexec installed and I never really thought much about what was going on behind the scenes. Gparted does something similar with pkexec when I start it up as an ordinary user.

Perhaps some instructions would be useful for new users installing torguard from the AUR repository versus using the Arch Linux package directly from TorGuard.

Thanks for the suggestion. For my system, Exec=/usr/bin/pkexec /usr/bin/torguard will probably work. I'm not sure if gksudo and kdesudo are around anymore.

I removed the sudoers file that comes with the original package and since that wrapper never worked in my machines (I wrongly assumed that it also didn't work for everybody else) I also removed it. I won't have time to work on this until the next weekend. You can, however, simply edit the torguard.desktop file changing the Exec line to something like: Exec=gksudo /usr/bin/torguard

AFAICT all the wrapper was supposed to do was identify if you use gksudo, kdesudo or pkexec and call it, so by modifying the desktop file you should get the same behaviour. If you don't want to type your password every time you can then add a rule, probably in sudoers.d

So I see what you've changed: the vendor package puts a link in /usr/bin/torguard that points to torguard-wrapper which is a script which prompts for a sudo GUI prompt if one does not have root privileges. Your /usr/bin/torguard link points directly to the torguard executable.

This requires that as a simple user, I need to setup torguard to automatically run as root under my userid or perhaps all user userids. I will have to think about whether I want to do this.