2.1.6

Note for existing users of TunnlTo

If you haven't yet seen the 2.1.5 release notes please review them here.

🐞 Bug Fixes

🔧 Fixed an issue where Wiresock setup was not recognized as complete on some systems using non-English languages. Issues: #280 #252

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

Support

Email: support [AT] tunnl.to

Download

Windows 10/11 x64: TunnlTo_2.1.6_x64_en-US.msi
Windows 10/11 ARM64: TunnlTo_2.1.6_arm64-setup.exe

2.1.5

TunnlTo Update: Important Changes & New Features

First, a big thank you to everyone who provided feedback and bug reports! This release marks the end of the beta period.

Now that the beta is complete and base functionality has been thoroughly tested, I’ve restructured the app to ensure all features from the original open-source version of TunnlTo remain free without having to create an account. There is also now an option to upgrade to Premium which offers additional features and direct support, while Business Premium includes priority support. Now that the core functionality is stable, I’ll be focusing on expanding premium features.

Free: All features from the original open-source TunnlTo, now with an improved UI/UX. Includes Rules, Rule Groups, and advanced config validation to help ensure your tunnel works as expected—without the need to sift through pages of documentation.

Premium: Adds premium features and direct support with the developer.

Business Premium: Includes all premium features plus priority support.

🚨 Important Update Notice

If you’re using a version older than 2.1.5, please update before March 31, 2025. Older versions will no longer be supported, and some features may stop working. You can update manually or it will be available as an auto update in the coming days.

🆕 New Features & Improvements

✅ No More Login Requirement – Basic access is now fully sign-in-free.
✅ Exit Warning Dialog – Get a prompt when closing the app with an active tunnel.
✅ Auto Disable Tunnel – New setting to control tunnel behavior on app exit.

🐞 Bug Fixes

🔧 Enable/Disable Button Accuracy – Fixed text inconsistencies.
🔧 Wiresock Setup Issues – Improved support across different terminal configurations.
🔧 Log Fix – Improved handling of Wiresock service logs to stop excessive log file sizes.
🔧 Enable Button Visibility – Properly displayed across all window sizes.
🔧 "No Rules Selected" Dialog – No longer appears incorrectly when disabling.

🚀 Upcoming Features (for both Free & Premium users!)

🔜 System Tray Connect – Quickly manage tunnels from the system tray.
🔜 Auto-Connect on Startup – Seamlessly connect when launching the app.

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

Feedback, Issues and Support

Email: support [AT] tunnl.to

Download

Windows 10/11 x64: TunnlTo_2.1.5_x64_en-US.msi
Windows 10/11 ARM64: TunnlTo_2.1.5_arm64-setup.exe

1.0.7 - Old Open Source Version

This Version Is No Longer Supported

The latest release of TunnlTo includes all features from this version, except auto-connect and system tray connect (coming soon). The new version is actively maintained and uses updated Tauri and Wiresock versions.

🔗 New version details: https://github.com/TunnlTo/desktop-app

Known Issues

• Settings & tunnel configs may not save correctly: #213
• 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 unnecessary data 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.