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 <ito...@tidyhosts.com> 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 > tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN > tcp 0 0 169.254.242.168:3922 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:8001 0.0.0.0:* LISTEN > tcp 0 0 192.168.0.203:36154 192.168.0.33:8250 > ESTABLISHED > > thanks > > Ian > > > > > -----Original Message----- > From: Wei ZHOU <ustcweiz...@gmail.com> > 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 <ito...@tidyhosts.com> 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 <ito...@tidyhosts.com> > > 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 <ustcweiz...@gmail.com> > > 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.htm > > l# > > accessing-system-vms > > > > -Wei > > > > On Wed, 7 Jun 2023 at 13:58, Ian Tobin <ito...@tidyhosts.com> 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 <ustcweiz...@gmail.com> > > > 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 <ito...@tidyhosts.com> 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 > > > > > > > > > >
