Re: NoVNC failed to connect
Hi, Can you check in the console proxy vm if the vnc ports are reachable ? telnet 192.168.0.34 5900 telnet 192.168.0.34 5901 -Wei On Sat, 10 Jun 2023 at 12:33, Ian Tobin wrote: > Hi Wei, > > Sorry I thought you wanted me to run inside consoleproxy. > > So on the hypervisor I can see the standard VNC ports open > > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN > tcp0 0 0.0.0.0:41757 0.0.0.0:* LISTEN > tcp0 0 0.0.0.0:33523 0.0.0.0:* LISTEN > tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN > tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN > tcp0 0 0.0.0.0:16514 0.0.0.0:* LISTEN > tcp0 0 192.168.0.34:5900 0.0.0.0:* LISTEN > tcp0 0 192.168.0.34:5901 0.0.0.0:* LISTEN > tcp0256 192.168.0.34:22 192.168.0.97:53409 > ESTABLISHED > tcp0 0 192.168.0.34:670192.168.0.37:2049 > ESTABLISHED > tcp0 0 192.168.0.34:34234 185.125.190.36:80 > TIME_WAIT > tcp6 0 0 :::22 :::*LISTEN > tcp6 0 0 :::111 :::*LISTEN > tcp6 0 0 :::16514:::*LISTEN > tcp6 0 0 :::43853:::*LISTEN > tcp6 0 0 :::39889:::*LISTEN > tcp6 0 0 192.168.0.34:47868 192.168.0.33:8250 > ESTABLISHED > > > > thanks > > Ian > > > -Original Message- > From: Wei ZHOU > Sent: 10 June 2023 10:39 > To: users@cloudstack.apache.org > Subject: Re: NoVNC failed to connect > > Just noticed you run the commands in consoleproxy vm. > Can you please run same commands on ubuntu hosts ? > > -Wei > > On Saturday, 10 June 2023, Ian Tobin wrote: > > > Hi Wei, > > > > The Hypervisor is running Ubuntu 22.04.2 LTS > > > > The Console Proxy is running Debian 11.6, ive also just destroyed it > > and let it re create but the netstat shows there is no VNC ports running. > > > > Thanks > > > > Ian > > > > > > -Original Message- > > From: Wei ZHOU > > Sent: 10 June 2023 06:50 > > To: users@cloudstack.apache.org > > Subject: Re: NoVNC failed to connect > > > > Hi, > > > > What OS do you use? > > > > Normally you can find the ports listened on 5900/5901/... which are > > vnc ports of vms. > > > > -Wei > > > > On Fri, 9 Jun 2023 at 23:40, Ian Tobin wrote: > > > > > Hi Wei, > > > > > > Sorry for the delay in coming back. > > > > > > I have got on to the console of the consoleproxy VM, when I issue > > > virsh domdisplay it say > > > > > > root@v-21-VM:~# virsh domdisplay > > > -bash: virsh: command not found > > > > > > Netstat -nat > > > > > > Active Internet connections (servers and established) > > > Proto Recv-Q Send-Q Local Address Foreign Address > State > > > tcp0 0 0.0.0.0:80800.0.0.0:* > > LISTEN > > > tcp0 0 0.0.0.0:80 0.0.0.0:* > > LISTEN > > > tcp0 0 169.254.242.168:39220.0.0.0:* > > LISTEN > > > tcp0 0 0.0.0.0:80010.0.0.0:* > > LISTEN > > > tcp0 0 192.168.0.203:36154 192.168.0.33:8250 > > > ESTABLISHED > > > > > > thanks > > > > > > Ian > > > > > > > > > > > > > > > -Original Message- > > > From: Wei ZHOU > > > Sent: 07 June 2023 16:33 > > > To: users@cloudstack.apache.org > > > Subject: Re: NoVNC failed to connect > > > > > > The default password for root user is "password". > > > If you use ssh, password is not required. > > > > > > -Wei > > > > > > On Wednesday, 7 June 2023, Ian Tobin wrote: > > > > > > > Hey Wei, > > > > > > > > I can console on to the proxy VM from the KVM host, but I cannot > > > > locate the system.vm.password parameter to get the password in the > > > > UI, unless im missing something? > > > > > > > > Thanks > > > > > > > > Ian > > > > > > > > > > > > > > > > -Original Message- > > > > From: Ian Tobin > > > > Sent: 07 June 2023 13:06 > > > > To: users@cloudstack.apache.org > > > > Subject: RE: NoVNC failed to connect > > > > > > > > Hi Wei, > > > > > > > > Thanks for the info, ill connect and report back. > > > > > > > > Thanks > > > > > > > > Ian > > > > > > > > > > > > > > > > > > > > -Original Message- > > > > From: Wei ZHOU > > > > Sent: 07 June 2023 13:04 > > > > To: users@cloudstack.apache.org > > > > Subject: Re: NoVNC failed to connect > > > > > > > > Hi Ian, > > > > > > > > You can access the system vm via "virsh console" on the kvm host > > > > or follow > > > > https://docs.cloudstack.apache.org/en/4.18.0.0/adminguide/systemvm > > > > .h > > > > tm > > > > l# > > > > accessing-sy
RE: NoVNC failed to connect
Hi Wei, Sorry I thought you wanted me to run inside consoleproxy. So on the hypervisor I can see the standard VNC ports open Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:41757 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:33523 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:16514 0.0.0.0:* LISTEN tcp0 0 192.168.0.34:5900 0.0.0.0:* LISTEN tcp0 0 192.168.0.34:5901 0.0.0.0:* LISTEN tcp0256 192.168.0.34:22 192.168.0.97:53409 ESTABLISHED tcp0 0 192.168.0.34:670192.168.0.37:2049 ESTABLISHED tcp0 0 192.168.0.34:34234 185.125.190.36:80 TIME_WAIT tcp6 0 0 :::22 :::*LISTEN tcp6 0 0 :::111 :::*LISTEN tcp6 0 0 :::16514:::*LISTEN tcp6 0 0 :::43853:::*LISTEN tcp6 0 0 :::39889:::*LISTEN tcp6 0 0 192.168.0.34:47868 192.168.0.33:8250 ESTABLISHED thanks Ian -Original Message- From: Wei ZHOU Sent: 10 June 2023 10:39 To: users@cloudstack.apache.org Subject: Re: NoVNC failed to connect Just noticed you run the commands in consoleproxy vm. Can you please run same commands on ubuntu hosts ? -Wei On Saturday, 10 June 2023, Ian Tobin wrote: > Hi Wei, > > The Hypervisor is running Ubuntu 22.04.2 LTS > > The Console Proxy is running Debian 11.6, ive also just destroyed it > and let it re create but the netstat shows there is no VNC ports running. > > Thanks > > Ian > > > -Original Message- > From: Wei ZHOU > Sent: 10 June 2023 06:50 > To: users@cloudstack.apache.org > Subject: Re: NoVNC failed to connect > > Hi, > > What OS do you use? > > Normally you can find the ports listened on 5900/5901/... which are > vnc ports of vms. > > -Wei > > On Fri, 9 Jun 2023 at 23:40, Ian Tobin wrote: > > > Hi Wei, > > > > Sorry for the delay in coming back. > > > > I have got on to the console of the consoleproxy VM, when I issue > > virsh domdisplay it say > > > > root@v-21-VM:~# virsh domdisplay > > -bash: virsh: command not found > > > > Netstat -nat > > > > Active Internet connections (servers and established) > > Proto Recv-Q Send-Q Local Address Foreign Address State > > tcp0 0 0.0.0.0:80800.0.0.0:* > LISTEN > > tcp0 0 0.0.0.0:80 0.0.0.0:* > LISTEN > > tcp0 0 169.254.242.168:39220.0.0.0:* > LISTEN > > tcp0 0 0.0.0.0:80010.0.0.0:* > LISTEN > > tcp0 0 192.168.0.203:36154 192.168.0.33:8250 > > ESTABLISHED > > > > thanks > > > > Ian > > > > > > > > > > -Original Message- > > From: Wei ZHOU > > Sent: 07 June 2023 16:33 > > To: users@cloudstack.apache.org > > Subject: Re: NoVNC failed to connect > > > > The default password for root user is "password". > > If you use ssh, password is not required. > > > > -Wei > > > > On Wednesday, 7 June 2023, Ian Tobin wrote: > > > > > Hey Wei, > > > > > > I can console on to the proxy VM from the KVM host, but I cannot > > > locate the system.vm.password parameter to get the password in the > > > UI, unless im missing something? > > > > > > Thanks > > > > > > Ian > > > > > > > > > > > > -Original Message- > > > From: Ian Tobin > > > Sent: 07 June 2023 13:06 > > > To: users@cloudstack.apache.org > > > Subject: RE: NoVNC failed to connect > > > > > > Hi Wei, > > > > > > Thanks for the info, ill connect and report back. > > > > > > Thanks > > > > > > Ian > > > > > > > > > > > > > > > -Original Message- > > > From: Wei ZHOU > > > Sent: 07 June 2023 13:04 > > > To: users@cloudstack.apache.org > > > Subject: Re: NoVNC failed to connect > > > > > > Hi Ian, > > > > > > You can access the system vm via "virsh console" on the kvm host > > > or follow > > > https://docs.cloudstack.apache.org/en/4.18.0.0/adminguide/systemvm > > > .h > > > tm > > > l# > > > accessing-system-vms > > > > > > -Wei > > > > > > On Wed, 7 Jun 2023 at 13:58, Ian Tobin wrote: > > > > > > > Hey Wei, > > > > > > > > Thanks for the reply. > > > > > > > > I think I didn’t write correctly, we can ping the systemvm but > > > > also we cannot noVNC to the systemvms. > > > > > > > > Thanks > > > > > > > > Ian > > > > > > > > > > > > > > > > > > > > > > > > Tel: +44 (0)560 367 4610 > > > > Email: i...@tidyhosts.com > > > > Visit us: www.tidyhosts.com > > > > > >
Re: NoVNC failed to connect
Just noticed you run the commands in consoleproxy vm. Can you please run same commands on ubuntu hosts ? -Wei On Saturday, 10 June 2023, Ian Tobin wrote: > Hi Wei, > > The Hypervisor is running Ubuntu 22.04.2 LTS > > The Console Proxy is running Debian 11.6, ive also just destroyed it and > let it re create but the netstat shows there is no VNC ports running. > > Thanks > > Ian > > > -Original Message- > From: Wei ZHOU > Sent: 10 June 2023 06:50 > To: users@cloudstack.apache.org > Subject: Re: NoVNC failed to connect > > Hi, > > What OS do you use? > > Normally you can find the ports listened on 5900/5901/... which are vnc > ports of vms. > > -Wei > > On Fri, 9 Jun 2023 at 23:40, Ian Tobin wrote: > > > Hi Wei, > > > > Sorry for the delay in coming back. > > > > I have got on to the console of the consoleproxy VM, when I issue > > virsh domdisplay it say > > > > root@v-21-VM:~# virsh domdisplay > > -bash: virsh: command not found > > > > Netstat -nat > > > > Active Internet connections (servers and established) > > Proto Recv-Q Send-Q Local Address Foreign Address State > > tcp0 0 0.0.0.0:80800.0.0.0:* > LISTEN > > tcp0 0 0.0.0.0:80 0.0.0.0:* > LISTEN > > tcp0 0 169.254.242.168:39220.0.0.0:* > LISTEN > > tcp0 0 0.0.0.0:80010.0.0.0:* > LISTEN > > tcp0 0 192.168.0.203:36154 192.168.0.33:8250 > > ESTABLISHED > > > > thanks > > > > Ian > > > > > > > > > > -Original Message- > > From: Wei ZHOU > > Sent: 07 June 2023 16:33 > > To: users@cloudstack.apache.org > > Subject: Re: NoVNC failed to connect > > > > The default password for root user is "password". > > If you use ssh, password is not required. > > > > -Wei > > > > On Wednesday, 7 June 2023, Ian Tobin wrote: > > > > > Hey Wei, > > > > > > I can console on to the proxy VM from the KVM host, but I cannot > > > locate the system.vm.password parameter to get the password in the > > > UI, unless im missing something? > > > > > > Thanks > > > > > > Ian > > > > > > > > > > > > -Original Message- > > > From: Ian Tobin > > > Sent: 07 June 2023 13:06 > > > To: users@cloudstack.apache.org > > > Subject: RE: NoVNC failed to connect > > > > > > Hi Wei, > > > > > > Thanks for the info, ill connect and report back. > > > > > > Thanks > > > > > > Ian > > > > > > > > > > > > > > > -Original Message- > > > From: Wei ZHOU > > > Sent: 07 June 2023 13:04 > > > To: users@cloudstack.apache.org > > > Subject: Re: NoVNC failed to connect > > > > > > Hi Ian, > > > > > > You can access the system vm via "virsh console" on the kvm host or > > > follow > > > https://docs.cloudstack.apache.org/en/4.18.0.0/adminguide/systemvm.h > > > tm > > > l# > > > accessing-system-vms > > > > > > -Wei > > > > > > On Wed, 7 Jun 2023 at 13:58, Ian Tobin wrote: > > > > > > > Hey Wei, > > > > > > > > Thanks for the reply. > > > > > > > > I think I didn’t write correctly, we can ping the systemvm but > > > > also we cannot noVNC to the systemvms. > > > > > > > > Thanks > > > > > > > > Ian > > > > > > > > > > > > > > > > > > > > > > > > Tel: +44 (0)560 367 4610 > > > > Email: i...@tidyhosts.com > > > > Visit us: www.tidyhosts.com > > > > > > > > > > > > > > > > -Original Message- > > > > From: Wei ZHOU > > > > Sent: 07 June 2023 12:21 > > > > To: users@cloudstack.apache.org > > > > Subject: Re: NoVNC failed to connect > > > > > > > > Hi Ian, > > > > > > > > Can you log into the console proxy vm, and check if the vnc port > > > > of > > > > (any) vm is reachable ? > > > > You can get the vnc port by command "virsh domdisplay" or "virsh > > > > vncdisplay" on the kvm host. > > > > > > > > -Wei > > > > > > > > > > > > On Wed, 7 Jun 2023 at 10:19, Ian Tobin wrote: > > > > > > > > > Hi, > > > > > > > > > > We are currently testing CloudStack. We have setup with 3 nodes > > > > > (KVM) and the management server. > > > > > > > > > > We have deployed a new instance but we are unable to connect to > > > > > noVNC, the error just says failed to connect to server. > > > > > > > > > > We can connect to the systemvm proxy VM so unsure how to > > > > > troubleshoot the issue. > > > > > > > > > > At the moment there is no certificates installed so everything > > > > > is over http. > > > > > > > > > > Any ideas how we can troubleshoot this? > > > > > > > > > > Thanks > > > > > > > > > > Ian > > > > > > > > > > > > > > >
RE: NoVNC failed to connect
Hi Wei, The Hypervisor is running Ubuntu 22.04.2 LTS The Console Proxy is running Debian 11.6, ive also just destroyed it and let it re create but the netstat shows there is no VNC ports running. Thanks Ian -Original Message- From: Wei ZHOU Sent: 10 June 2023 06:50 To: users@cloudstack.apache.org Subject: Re: NoVNC failed to connect Hi, What OS do you use? Normally you can find the ports listened on 5900/5901/... which are vnc ports of vms. -Wei On Fri, 9 Jun 2023 at 23:40, Ian Tobin wrote: > Hi Wei, > > Sorry for the delay in coming back. > > I have got on to the console of the consoleproxy VM, when I issue > virsh domdisplay it say > > root@v-21-VM:~# virsh domdisplay > -bash: virsh: command not found > > Netstat -nat > > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN > tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN > tcp0 0 169.254.242.168:39220.0.0.0:* LISTEN > tcp0 0 0.0.0.0:80010.0.0.0:* LISTEN > tcp0 0 192.168.0.203:36154 192.168.0.33:8250 > ESTABLISHED > > thanks > > Ian > > > > > -Original Message- > From: Wei ZHOU > Sent: 07 June 2023 16:33 > To: users@cloudstack.apache.org > Subject: Re: NoVNC failed to connect > > The default password for root user is "password". > If you use ssh, password is not required. > > -Wei > > On Wednesday, 7 June 2023, Ian Tobin wrote: > > > Hey Wei, > > > > I can console on to the proxy VM from the KVM host, but I cannot > > locate the system.vm.password parameter to get the password in the > > UI, unless im missing something? > > > > Thanks > > > > Ian > > > > > > > > -Original Message- > > From: Ian Tobin > > Sent: 07 June 2023 13:06 > > To: users@cloudstack.apache.org > > Subject: RE: NoVNC failed to connect > > > > Hi Wei, > > > > Thanks for the info, ill connect and report back. > > > > Thanks > > > > Ian > > > > > > > > > > -Original Message- > > From: Wei ZHOU > > Sent: 07 June 2023 13:04 > > To: users@cloudstack.apache.org > > Subject: Re: NoVNC failed to connect > > > > Hi Ian, > > > > You can access the system vm via "virsh console" on the kvm host or > > follow > > https://docs.cloudstack.apache.org/en/4.18.0.0/adminguide/systemvm.h > > tm > > l# > > accessing-system-vms > > > > -Wei > > > > On Wed, 7 Jun 2023 at 13:58, Ian Tobin wrote: > > > > > Hey Wei, > > > > > > Thanks for the reply. > > > > > > I think I didn’t write correctly, we can ping the systemvm but > > > also we cannot noVNC to the systemvms. > > > > > > Thanks > > > > > > Ian > > > > > > > > > > > > > > > > > > Tel: +44 (0)560 367 4610 > > > Email: i...@tidyhosts.com > > > Visit us: www.tidyhosts.com > > > > > > > > > > > > -Original Message- > > > From: Wei ZHOU > > > Sent: 07 June 2023 12:21 > > > To: users@cloudstack.apache.org > > > Subject: Re: NoVNC failed to connect > > > > > > Hi Ian, > > > > > > Can you log into the console proxy vm, and check if the vnc port > > > of > > > (any) vm is reachable ? > > > You can get the vnc port by command "virsh domdisplay" or "virsh > > > vncdisplay" on the kvm host. > > > > > > -Wei > > > > > > > > > On Wed, 7 Jun 2023 at 10:19, Ian Tobin wrote: > > > > > > > Hi, > > > > > > > > We are currently testing CloudStack. We have setup with 3 nodes > > > > (KVM) and the management server. > > > > > > > > We have deployed a new instance but we are unable to connect to > > > > noVNC, the error just says failed to connect to server. > > > > > > > > We can connect to the systemvm proxy VM so unsure how to > > > > troubleshoot the issue. > > > > > > > > At the moment there is no certificates installed so everything > > > > is over http. > > > > > > > > Any ideas how we can troubleshoot this? > > > > > > > > Thanks > > > > > > > > Ian > > > > > > > > > >
