Releases: TunnlTo/desktop-app
2.2.1
🚀 New Features & Improvements
- Fix: WireGuard Config Import
Fixed a bug introduced in 2.2.0 that caused incorrect key values when importing configs.
🌐 Official TunnlTo website
The official TunnlTo website has a fresh new look - with more updates on the way. Check it out!
💎 TunnlTo Premium
Unlock additional features and priority support with TunnlTo Premium.
View the full feature list and pricing on the TunnlTo website.
Download
Troubleshooting
App Log Files
C:\Users\[YOUR USERNAME]\AppData\Local\com.tunnl.to\logs\app_logs.log
Wiresock Config File
The Wiresock config file that is generated after clicking the "Enable" button is located at:
C:\Users\[YOUR USERNAME]\AppData\Local\TunnlTo\tunnel.conf
Contact
Basic support for the TunnlTo app is available to all users, covering installation issues and getting the app up and running.
For support with WireGuard connections, tunnel configuration, or advanced setup, please note that this is included with TunnlTo Premium.
Support: support@tunnl.to
Feedback: feedback@tunnl.to
Previous Release Notes:
2.2.1
-
Beta Release Channel for Auto Updates
You can now opt into the Beta release channel via the settings. This allows the auto-update system to fetch the latest beta builds of TunnlTo, giving you early access to new features and fixes. -
Fix: Folder and Process Path Rules
Resolved an issue where rules using "Folder Path" or "Process Path" types didn't display their values correctly when editing. -
Fix: WireGuard Config Import
Improved compatibility with WireGuard configuration files that use inconsistent casing (e.g., Privatekey vs PrivateKey). These are now imported correctly.
2.2.0
🚀 New Features & Improvements
-
Beta Release Channel for Auto Updates
You can now opt into the Beta release channel via the settings. This allows the auto-update system to fetch the latest beta builds of TunnlTo, giving you early access to new features and fixes. -
Fix: Folder and Process Path Rules
Resolved an issue where rules using "Folder Path" or "Process Path" types didn't display their values correctly when editing. -
Fix: WireGuard Config Import
Improved compatibility with WireGuard configuration files that use inconsistent casing (e.g., Privatekey vs PrivateKey). These are now imported correctly.
🌐 Official TunnlTo website
The official TunnlTo website has a fresh new look - with more updates on the way. Check it out!
💎 TunnlTo Premium
Unlock additional features and priority support with TunnlTo Premium.
View the full feature list and pricing on the TunnlTo website.
Download
Troubleshooting
App Log Files
C:\Users\[YOUR USERNAME]\AppData\Local\com.tunnl.to\logs\app_logs.log
Wiresock Config File
The Wiresock config file that is generated after clicking the "Enable" button is located at:
C:\Users\[YOUR USERNAME]\AppData\Local\TunnlTo\tunnel.conf
Contact
Basic support for the TunnlTo app is available to all users, covering installation issues and getting the app up and running.
For support with WireGuard connections, tunnel configuration, or advanced setup, please note that this is included with TunnlTo Premium.
Support: support@tunnl.to
Feedback: feedback@tunnl.to
1.0.7 - Old Open Source Version
This Release Is No Longer Supported
The latest release of TunnlTo includes all the features from this version, free of charge. Grab the latest release here: https://github.com/TunnlTo/desktop-app/releases
Licensing
- This version of TunnlTo (1.0.7) follows the same licensing terms as the Wiresock version it’s built around: it’s free for personal use, but not licensed for business or commercial use. These terms have been in place since the initial release of both TunnlTo/Wiresock and continue to apply here.
Known Issues
- Settings & tunnel configs may not save correctly
- Outdated dependencies: This version (last updated in 2023) may have security vulnerabilities. Use at your own risk.
FAQ
Why a "new" version?
To meet feature requests and provide better support, a new version was built with additional functionality and premium support options.
Why is it not open source?
If open-source software is a requirement for you, keep in mind that TunnlTo has always relied on Wiresock, a closed-source network driver. Using an open-source GUI for a proprietary driver offers little practical benefit in terms of transparency or security. The new version of TunnlTo is digitally signed with a Microsoft-issued code signing certificate, ensuring its integrity and authenticity.
Why was the old repo removed?
Keeping outdated source code for a now closed-source app would be misleading.
Can I modify this version?
This version is not licensed for redistribution.
Why is the UI different?
The previous UI was designed for advanced users managing one or two tunnels, but it wasn't approachable for those unfamiliar with WireGuard. The original TunnlTo documentation even stated that users needed a "good understanding of WireGuard," yet many still wanted to use the software. As a result, the majority of support requests were about tunnel configuration, often leading beginners to misconfigure their setups.
Goals of the Updated UI
- Make the interface more accessible to non-technical users.
- Reduce misconfigurations that could lead to unintended tunnel behavior.
- Eliminate tunnel config duplication.
- Allow seamless switching between VPN endpoints without reconfiguring each tunnel’s include/exclude settings.
- Improve functionality for users managing tens or even hundreds of tunnels.
- Remove the need for extensive documentation by integrating explanations and form validation directly into the UI.
Previously, the main repository homepage was a dense wall of text explaining the required syntax for each input field. Now, the UI itself provides this guidance, eliminating the need for separate documentation.
For users handling large numbers of tunnels (such as those importing from privacy-focused VPN services), the searchable dropdown significantly improves usability. Instead of scrolling through an overwhelming list, they can quickly find and select the tunnel they need. Additionally, rather than duplicating entries like "chrome, firefox" in every tunnel configuration, users now define them once and switch between tunnels effortlessly. This becomes even more valuable as more applications are added.
Ultimately, these updates aim to balance simplicity for beginners with the flexibility that advanced users need—while ensuring tunnel configurations remain correct to minimize security and privacy risks.