kubevpn connect --ssh-addr error desc = not an ip:port
whomobile opened this issue · 15 comments
It looks like even if all ssh configuration correct, it failed with below error.
kubevpn connect --ssh-addr 192.168.1.100:22 --ssh-username root --ssh-keyfile ~/.ssh/ssh.pem --foreground=true
Error: rpc error: code = Unknown desc = not an ip:port
ahd kubevpn logs or debug=true does not generate any logs.
It looks like even if all ssh configuration correct, it failed with below error.
kubevpn connect --ssh-addr 192.168.1.100:22 --ssh-username root --ssh-keyfile ~/.ssh/ssh.pem --foreground=true Error: rpc error: code = Unknown desc = not an ip:portahd kubevpn logs or debug=true does not generate any logs.
you can use kubevpn logs -f to see more log
i will comfire this issue and fix it as soon as possible
It looks like even if all ssh configuration correct, it failed with below error.
kubevpn connect --ssh-addr 192.168.1.100:22 --ssh-username root --ssh-keyfile ~/.ssh/ssh.pem --foreground=true Error: rpc error: code = Unknown desc = not an ip:portahd kubevpn logs or debug=true does not generate any logs.
i tested it and it works well, you can upgrade it to latest version by command kubevpn upgrade and try it again?
maybe it is because you do not special remote cluster kubeconfig or special option --remote-kubeconfig, this option means kubevpn will use ssh server ~/.kube/config file to connect to cluster or you can copy this file to local , and special --kubeconfig or export env like k8s kubectl
❯ kubevpn upgrade
The latest version is: v2.1.0, commit: fa49431
Already up to date, don't needs to upgrade
Upgrade daemon...done
My environment is macos ventua 13.4, just in case.
normally it works fine.
by the way, I test ssh server with/without ~/.kube/config
based on timing, it looks not even try to connect remote.
can you exec command kubevpn version and show me output?
no needs to quit daemon by command kubevpn quit, daemon server will do nothing if client not send any command to server. the reason why i startup a daemon server is because can connect to mutiple cluster
maybe we can have a online meeting by feishu or tencent meeting? to diagnose issue ? if you have some time
sure, we can talk your time morning (my time evening), let me know time.
sure, we can talk your time morning (my time evening), let me know time.
ok, here is my wechat: fcw895703375
Sorry, my wechat account got logged out and can't recover it. Here is larksuite meeting we can use.
Meeting topic: kubevpn
Meeting time: Tomorrow, Nov 1, 8:00 - 8:30 PM (GMT-7)
Meeting ID: 954 040 901
Meeting link: https://vc.larksuite.com/j/954040901
Sorry, my wechat account got logged out and can't recover it. Here is larksuite meeting we can use.
Meeting topic: kubevpn Meeting time: Tomorrow, Nov 1, 8:00 - 8:30 PM (GMT-7) Meeting ID: 954 040 901 Meeting link: https://vc.larksuite.com/j/954040901
ok ,got it, meeting start timestamp should is 1698894000 . right? because i am in chain, GMT+8, in case of mistake the time
yes next 10minutes :-) . started the meeting. Thanks
yes next 10minutes :-) . started the meeting. Thanks
Maybe you can use comand kubectl config view --flatten --raw and save output , use this kubeconfig to connect via ssh. i noticed that when we try to connect to via ssh, we have see log like kubeconfig is invalid, and i checked code, this message only shows while kubeconfig is not configured correctly
