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.html#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 > > >
