Wiresock Interface section is not present

Home Forums Discussions Support Portal Wiresock Interface section is not present

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #12335
    joq3
    Participant

      Hi,

      I just found WireSock, have been using WireGuard client on my Windows computer to connect to my NAS running Unraid with a WireGuard server.

      I exported the config-file from my NAS and I have no trouble connecting to it with the WireGuard client.

      I then installed WireSock and tried to run it like this:

      wiresock-client.exe run -config C:\Program Files\WireSock VPN Client\bin\config.conf -log-level all -lac

      When running with logs this is the output:

      2022-09-07 08:01:29 WireSock Service has started.
      2022-09-07 08:01:29 failed to open the configuration file!
      2022-09-07 08:01:29 Interface section is not present!
      2022-09-07 08:01:29 Failed to initialize Wireguard tunnel.

      What am I doing wrong?

      This is the config-file:

      [Interface]
      PrivateKey = redacted
      Address = 10.253.0.2/32
      DNS = 192.168.1.1

      [Peer]
      PublicKey = redacted
      Endpoint = vpn.redacted.com:51820
      AllowedApps = firefox
      AllowedIPs = 0.0.0.0/0

      My goal is to tunnel only the Firefox browser through the VPN, so this app is really what I need!

      #12336
      Vadim Smirnov
      Keymaster

        Hi,

        If this is the exact command line

        wiresock-client.exe run -config C:\Program Files\WireSock VPN Client\bin\config.conf -log-level all -lac,

        then you must either add quotes (path contains spaces) or remove the full path (wiresock checks the \bin folder for a config file):

        wiresock-client.exe run -config "C:\Program Files\WireSock VPN Client\bin\config.conf" -log-level all -lac

        OR

        wiresock-client.exe run -config config.conf -log-level all -lac

        Hope it helps!

         

      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.