TunnlTo/desktop-app

question: can't connect via your app

UmkasArt opened this issue · 4 comments

UmkasArt commented

Hi!
I can't connect to the tunnel through your application. After clicking the Connect button, nothing happens at first, and then I get an error (in the screenshot)
image

brendanosborne commented

Hi, could you try issuing the following command in your command prompt:

"c:\program files\wiresock vpn client\bin\wiresock-client.exe" run -config %USERPROFILE%\AppData\Local\TunnlTo\tunnel.conf -log-level debug

If your Program Files directory is not on your C drive you'll need to update the command to suit.

Please screenshot the results of the command and reply with it here.

JustAnotherUsername1234 commented

I have the same problem.

PS C:\Program Files\WireSock VPN Client\bin> .\wiresock-client.exe run -config %USERPROFILE%\AppData\Local\TunnlTo\tunnel.conf -log-level debug
2023-02-03 23:21:58 WireSock WireGuard VPN Client Service 1.2.15
The service is starting using %USERPROFILE%\AppData\Local\TunnlTo\tunnel.conf WireGuard client configuration.

WireSock WireGuard VPN Client 1.2.15 is running as a regular process.
2023-02-03 23:21:58 WireSock Service has started.
2023-02-03 23:21:58 failed to open the configuration file!
2023-02-03 23:21:58 Interface section is not present!
2023-02-03 23:21:58 Failed to initialize Wireguard tunnel.

But the tunnel config was definitely there. So I have moved the file to C:\tmp\tunnel.conf and it worked:

PS C:\Program Files\WireSock VPN Client\bin> .\wiresock-client.exe run -config C:\tmp\tunnel.conf -log-level debug
2023-02-03 23:25:54 WireSock WireGuard VPN Client Service 1.2.15
The service is starting using C:\tmp\tunnel.conf WireGuard client configuration.

WireSock WireGuard VPN Client 1.2.15 is running as a regular process.
2023-02-03 23:25:54 WireSock Service has started.
2023-02-03 23:25:54 [MGR]: Using WireGuard server: 
2023-02-03 23:25:54 [TUN]: Detected default interface 
2023-02-03 23:25:54 [TUN]: Using local IPv4 = 
2023-02-03 23:25:54 [TUN]: Using local IPv6 = 
2023-02-03 23:25:54 [TUN]: Sent handshake packet to the WireGuard server at 

2023-02-03 23:25:54 [MGR]: Tunnel has started
2023-02-03 23:25:54 Wireguard tunnel has been started.
2023-02-03 23:25:54 [TUN]: Handshake response received from 
2023-02-03 23:26:19 [TUN]: keep_alive_thread: Sending Keepalive packet to WireGuard Server success

It looks like a wiresock-client.exe can't handle config path if it contains any non-latin symbol in it, as my %USERPROFILE% contains some non-latin unicode characters and they got changed in the debug output if I use a full path.

brendanosborne commented

Thanks, that's a good pickup on the non latin username. I had similar issues in another part of the app. Shouldn't be too hard to resolve.