TunnlTo Premium Beta Release 2

[brendanosborne]

Issues

Please create an issue

Feedback

Please email me directly for feedback that could not be described as a bug/issue. The address is in the app under Help > About.

---

Release Announcement

Hi Everyone,

I'm thrilled to announce a brand-new beta release! The app has been almost entirely rebuilt, making it virtually unrecognizable from previous versions. After a lot of careful planning, I’ve restructured how TunnlTo works to create a more intuitive and accessible way to manage tunnels.

Restructure

Tunnels have been restructured into three categories.

Tunnels

• Tunnels are used to configure WireGuard VPN and Wiresock settings.

Rules

• Rules allow you to include or exclude specific process names, file paths, IP addresses/ranges, and folders when connecting to a tunnel.

Rule Groups

• Rule Groups let you organize multiple rules together. For example, you can group work-related applications and folders separately from your gaming-related ones.

With this update, you no longer need to duplicate WireGuard configs for different use cases! Switching between tunnels is now effortless, and you can easily decide what traffic should or shouldn’t route through a tunnel.

I’ve also focused heavily on improving forms and validation to prevent incompatible configurations with WireGuard and Wiresock. The previous documentation has been replaced with intuitive tooltips and strict form validation, making Wiresock far more accessible—even for less tech-savvy users.

Release Notes

• There will be a paid version of the app. The details have not been decided yet. The beta is free.
• TunnlTo is no longer open source.
• Accounts & subscriptions from the previous beta (v2.0.0 and v2.0.2) have been deleted.
• You will need to register a new account, but the payment system is not being tested during this beta phase.
• The import feature is not available in this version.
• The system tray menu does not yet support Connect functionality.
• The "Payment Settings" button on the Accounts page is non-functional, as payments are not being tested.

Important Notice!

If you’ve used the original TunnlTo, you’re familiar with manually adding 0.0.0.0/0, ::/0 to a tunnel’s "Allowed" section. Now, TunnlTo automatically adds them to AllowedIPs in Wiresock configs unless you specify other IPs/ranges.

For more granular control, you can add 0.0.0.0/0 or ::/0 as a rule and manually include it as needed.

Thanks for testing this beta—I’m looking forward to your feedback! 🚀

---

Download

Visit the releases page

---

Troubleshooting

Logs

The log file location has been changed a couple of times while I'm sorting out some issues:

• v2.0.5 C:\Users\[YOUR USERNAME]\AppData\Local\com.tunnl.to\logs\app_logs.log
• v2.0.2 C:\Users\[YOUR USERNAME]\AppData\Roaming\com.tunnl.to\app_logs.log
• v2.0.1 C:\Users\[YOUR USERNAME]\AppData\Local\com.tunnl.to\logs\TunnlTo.log

Wiresock Config File

• The Wiresock config file that is generated when clicking "Enable" is located at C:\Users\[YOUR USERNAME]\AppData\Local\TunnlTo\tunnel.conf

Issues

Please create an issue

Feedback

Please email me directly for feedback that could not be described as a bug/issue. The address is in the app under Help > About.

---

Screenshots

Setup now guides you through the installation and setup of Wiresock.

Home screen in dark mode.

Home screen in light mode.

Configure rules to include or exclude process names, process paths, IP addresses/ranges, and folders. All input is validated to prevent incorrect formatting or incompatible configurations with Wiresock.
IP ranges can be entered in the format 192.168.1.1 - 192.168.1.254 and are automatically converted to the correct CIDR format in the background.

Rule Groups.

Tunnel setup has an advanced form schema to ensure correct values are entered. The latest Wiresock features are included for configuration.

Settings includes new helpful features as requested by the community.

[brendanosborne]

That may be a problem with the app not registering the deep links correctly. Can you run the app as administrator and let me know what happens?

[brendanosborne]

@ldengcc Can you try v2.0.5 please. I believe the issue you are experiencing is resolved.

[edwardch]

Hey @brendanosborne, thanks for the update!

I'm still getting the same issue when trying to connect

Failed to start WireSock tunnel: "Failed to run scheduled task: StartWiresock"

I will log a ticket with our IT support folks to check whether there is a policy blocking anything around this.

[ldengcc]

@ldengcc Can you try v2.0.5 please. I believe the issue you are experiencing is resolved.

Thanks for update ! now login page redirect successfully ❤️ and I got same issue like edwardch replied.

[brendanosborne]

@ldengcc I've created a dedicated issue thread for that error. Please post any more info relating to this issue in here: #252

[edwardch]

Congrats on the release, Brendan!

There were a couple of issues that I came accross, though I upgraded from (I think) the first beta version so this might be a just me thing...

Wiresock

I had to upgrade Wiresock to 1.4.7, so that was cool to see
In the Wiresock setup, I clicked "Configure Service", which gave an error (can't remember exactly what it was now)
So I went into ~\AppData\Local\Temp and ran setup_wiresock.bat as an administrator, which worked

Login

Then I reopened TunnlTo and it took me to the login screen (confirming my manual config above worked)
I tried using my saved credentials from before which said was unauthorised
I also tried logging in with GitHub, but in Firefox it got me into a TunnlTo sign in loop (maybe my browser settings, but not sure)

Then tried to sign up and got

Sign-up Error
Firebase: HTTP Cloud Function returned an error: {"error":{"message":"Unverified email","status":"INVALID_ARGUMENT"}} (auth/internal-error).

Maybe my email is already in your database, and I have the incorrect password saved.

---

Thanks again for the hard work on the new release, really looking forward to giving it a shot!

Cheers!

[brendanosborne]

Thank you! Reply here re: the login issue: #249 (reply in thread)

Would you mind checking the logs in C:\Users\[your username]\AppData\Local\com.tunnl.to\logs\TunnlTo.log to see if there are any error details for the error that occurred during the Configure Service step?

[edwardch]

Hmm, I don't see a logs directory in there (and I also checked the com.tunnl.to.old path.

There's only an EBWebView directory, but nothing that looks loggy to me 🤔

[iDarkEmpire]

Hmm, I don't see a logs directory in there (and I also checked the com.tunnl.to.old path.

There's only an EBWebView directory, but nothing that looks loggy to me 🤔

same

[johnsonjamees]

There doesn't seem to any function to import tunnel(s). Is this intentionally left out or are there plans for adding it in the future?

[brendanosborne]

The import feature is not available in this version.

It's a high priority. I just wanted to ensure the new tunnel structure and schema were all good before building out this feature.

[brendanosborne]

Quick update - I'll upload a new signed version tomorrow (super bowl Monday) with a few bug fixes.

I'd appreciate feedback about the new layout and if the rules/groups/tunnels restructure is intuitive. I'm not hearing any issues or complaints so assume it's working as intended?

[brendanosborne]

Version 2.0.5 is up! Visit the releases page for the download. Please update manually and once it is known to be stable I will push it to auto-update.

[coey0814]

Just like with version 2.0.2, I'm experiencing the same issue with version 2.0.5, making the program unusable.

The initial setup proceeds normally up to the 'Wiresock Setup' stage. I see the 'Configure Wiresock' message:
'Almost there! Wiresock needs to be configured as a service to work with TunnlTo.'

However, when I click the 'Configure Service' button, I briefly see a 'Setup Error' message:
'Failed to execute setup script'

This message disappears, and a cmd window (saying 'The service has not been started') flashes very briefly and then closes.

Could this problem be caused by my system environment not being in English?"

[edwardch]

The UI is looking great.

Hopefully I can provide some better feedback when I can get my tunnels to connect :)

BTW I also checked my log folder and there is now a log, "TunnlTo.log", which is 11.6 GB

[brendanosborne]

Just to clarify, when you click "Configure Service" you see this prompt?

I'm adding some further error handling in a new version which will hopefully point us in the right direction for a fix.

BTW I also checked my log folder and there is now a log, "TunnlTo.log", which is 11.6 GB

There is meant to be a 5mb log file size limit, so I'm a bit confused how that happened. I wonder if you guys are having similar issues to this users issue where they have a home PC with no policies/restrictions that they're aware of, but they're also not able to write to folders in the home directory?

Can you create a file manually in C:\Users\[YOUR USERNAME]\AppData\Local\Temp ?

[edwardch]

Just to clarify, when you click "Configure Service" you see this prompt?

I uninstalled, deleted all files inside AppData Roaming and Local,.

Then reinstalled, I didn't select run as administrator.
And I did get this prompt from your image when configuring the service, then I got the Failed to execute setup script error.

Running it as administrator worked (like it did before).

A note is that now I got the "magic link" login, but that didn't seem to log me in when "opening with TunnlTo" in my browser.
The GitHub login worked fine though.

Regarding logs, I looked in both the Roaming and Local paths and noticed both logs were about 11.6 gigs.

Then just to confirm, after the reinstall I'm still stuck on the scheduled tasks issue.

I tried the option to add "Everyone" to the security group of the EBWebView directory but that didn't change anything.
I don't see the task in the task scheduler, so maybe the part that sets up this task isn't working.

Definitely not looking for free support here, but I'm happy to try out a screen share session if you think that could help find the issue faster?
Let me know if you're up for that and I can email you for the next steps.

Cheers,
Edward

[brendanosborne]

Thanks for following up. I might take you up on that remote session offer after the next update which will includes a potential fix and more robust error handling to at least point us in the right direction if the fix doesn't work.

I've created a dedicated issue thread for this so please post any more info relating to this issue in here: #252

[gmancode]

Congratulations on the update! I've been using version 1 for over seven months, and I decided to check if the update was available. It is, and I'm happy to see it. I really liked the dark design because the white one from the previous version was stressful for me at night on my two monitors.
I also want to know what authorization is needed for.
I had a problem when I opened an email on my phone and clicked on a link. The authorization didn't pass in the application.I also want to know if I can refuse authorization. Many of my friends are afraid to authorize unfamiliar services, even though I have always told them to use your software.Now, about the updated version of the application, I have a Homeassistent that hangs on 192.168.0.90.
I allowed all IP addresses of the subnet to connect to 192.168.0.0/24, and everything works fine except for one thing: Homeassistent raises a kind of DNS and sets it to http://homeass istant.local:8123/ and although the address 192.168.0.92 opens, it is not always convenient. http://homeassistant.local:8123/ is not possible to open.
I would also like to add additional languages and automatic update with import of wg config.
and it would be great to add buttons on the mouse, for example, or specify yourself to connect and disconnect or even possibly comibination

[brendanosborne]

Thanks to those who have reported issues. Using a discussion thread wasn't a great idea for managing issues and some off-topic feedback based on personal opinions. I'm seeing the same issues in three different channels of communication, which it taking time to manage that I'd rather spend working on fixes and features.

Issues

Please create an issue

Feedback

Please email me directly for feedback that could not be described as a bug/issue. The address is in the app under Help > About.