wsl-vpnkit icon indicating copy to clipboard operation
wsl-vpnkit copied to clipboard

cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory

Open koekto1968 opened this issue 1 year ago • 3 comments

Hi guys! Something strange happened. The service stopped running all of a sudden.

wsl.exe -d wsl-vpnkit --cd /app wsl-vpnkit

  • VPNKIT_GATEWAY_IP=192.168.127.1
  • VPNKIT_HOST_IP=192.168.127.254
  • VPNKIT_LOCAL_IP=192.168.127.2
  • TAP_MAC_ADDR=5a:94:ef:e4:0c:ee
  • VMEXEC_PATH=/app/wsl-vm
  • GVPROXY_PATH=/app/wsl-gvproxy.exe
  • TAP_NAME=wsltap
  • CHECK_HOST=example.com
  • CHECK_DNS=1.1.1.1
  • DEBUG=0
  • set +x
  • WSL2_TAP_NAME=eth0
  • WSL2_GATEWAY_IP=172.18.128.1
  • '[' 0 -eq 0 ]
  • set +x starting vm and gvproxy... ERRO[0000] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory started vm and gvproxy ERRO[0001] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory ERRO[0002] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory ERRO[0003] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory ERRO[0004] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory ERRO[0005] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory ERRO[0006] cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory

Installation was done according to the manual. Yesterday and before everything works fine. No updates have been installed. The change systemd=false in /etc/wsl.conf helps to start the kit in manual mode. But at the same time, it is not possible to start the service at the start of the WSL. Ubuntu 22.04 WSL 1.2.5.0

Please, help!!!

koekto1968 avatar Jun 23 '23 12:06 koekto1968

I had a similar problem, but instead it was "exec format error". This fixed it. Not sure if it's related to this.

kropptrevor avatar Aug 01 '23 20:08 kropptrevor

@kropptrevor, thanks a lot for the valid path! As a result, everything was solved by adding lines to wsl.conf [boot]
command=update-binfmts --disable cli

koekto1968 avatar Aug 02 '23 12:08 koekto1968

I had a similar problem, but instead it was "exec format error". This fixed it. Not sure if it's related to this.

Same here, but I used the approach described in the comment bellow the one you've used.

rudironsonijr avatar Aug 03 '23 14:08 rudironsonijr