You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening Rancher Desktop the progress par shows that the application initializes.
However after waiting 5 minutes (showing 'waiting for services') the application throws an error.
Steps to Reproduce
Starting rancher desktop and waiting for the kubernetes services to connect
Result
Kubernetes Error
Error Starting Kubernetes
Error: tunneling socket could not be established, cause=write EPROTO 2283272:error:100000f7:SSL
routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:
@PretoPlasma Are you able to use our 1.9 release? We have implemented a networking solution that enables Rancher Desktop to function properly when running behind a VPN.
You can enable it using:
rdctl set --experimental.virtual-machine.networking-tunnel=true
I'm going to close this issue, feel free to re-open if the solution is not addressing your issue.
Actual Behavior
When opening Rancher Desktop the progress par shows that the application initializes.
However after waiting 5 minutes (showing 'waiting for services') the application throws an error.
Steps to Reproduce
Starting rancher desktop and waiting for the kubernetes services to connect
Result
Kubernetes Error
Error Starting Kubernetes
Error: tunneling socket could not be established, cause=write EPROTO 2283272:error:100000f7:SSL
routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:
Context:
Waiting for nodes
Some recent logfile lines:
}
2022-08-24T13:06:38.962Z: Running: wsl.exe --distribution rancher-desktop --exec docker images
2022-08-24T13:06:42.573Z: Running: wsl.exe --distribution rancher-desktop --exec /sbin/rc-update --update
2022-08-24T13:06:42.725Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service k3s start
2022-08-24T13:06:46.438Z: Capturing output: wsl.exe --distribution rancher-desktop --exec cat /proc/net/route
2022-08-24T13:06:46.587Z: Capturing output: wsl.exe --distribution rancher-desktop --exec cat /proc/net/fib_trie
2022-08-24T13:06:47.755Z: Capturing output: wsl.exe --distribution rancher-desktop --exec /bin/sh -c if test -r /etc/rancher/k3s/k3s.yaml; then echo yes; else echo no; fi
2022-08-24T13:06:47.918Z: Capturing output: wsl.exe --distribution rancher-desktop --exec wslpath -a -u C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\wsl-helper
2022-08-24T13:06:48.102Z: Capturing output: wsl.exe --distribution rancher-desktop --exec /mnt/c/Users/xxx/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/wsl-helper k3s kubeconfig
Expected Behavior
Kubernetes services are connected successfully and rancher desktop is ready to work with.
Additional Information
No response
Rancher Desktop Version
1.5.1
Rancher Desktop K8s Version
v1.23.6
Which container engine are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 10 Pro Version 1909
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
VPN Cisco AnyConnect
Company Proxy
Trend Micro Security Agent
The text was updated successfully, but these errors were encountered: