Leaderboard

Dear Fellow Privacy Enthusiasts, We hope everyone’s year is off to a safe start. If you’re not quite as protected as you’d like to be, we have some great news. You can now renew TorGuard for two years at 50% off and get a free Gli Wireguard mini VPN router plus a free $20 TorGuard gift card. This tiny powerhouse router never ceases to impress us. Take your privacy with you wherever you go or add a second secure VPN WiFi network at your home or office. If you are working remotely like many are, this router is small enough to fit in your laptop bag, yet powerful enough to run TorGuard VPN c

Prob not the right way but it works for me. Exit torguard and delete current configs Create ~/.config/autostart/torguard.desktop If you do not want to authenticate every startup change this line Then make any other config changes you want.

@James8078 sorry for late reply and thanks for reporting. I am quite busy with life and work and could not find time to check this forum, hope you are well. If your issue is already resolved, then ignore following: as far as I can see, curl tries to resolve updates.torguard.biz and you get a reply that updates.torguard.biz can not be resolved as well as few uci not found commands. On my routers it still works and have no issues at, check if you changed something on your router which might have caused this. Would be good if you could create an issue on github as it makes it easie

More details will follow soon...... In this contest you will have the chance to win an Asus AC-5300, the NETGEAR Nighthawk X6 R8000 or a top end GLi Mini router....

I experienced a frozen TG client issue with this update. If anyone else experiences the same, you can do this to fix it: Edit the torguard client configuration file: ~/.config/VPNetworkLLC/TorGuard.conf Search for "dns-manager-preference", set it to "linux_system_d" and start the client again. I am using dnsmasq and dnscrypt services on my machine, so it is possible that the problem occurred because of my configuration. It was working fine before with /etc/resolv.conf option but not anymore for me. I have not faced any other issue after fixing the configuration.

We haven't forgot about this