Hi Wei,
I saw this in the log
2023-06-11 16:35:31,083 WARN [cloud.consoleproxy.ConsoleProxyNoVNCHandler]
(qtpp
1670543353-39:null) Failed to create viewer due to External authenticator
failedd
request for vm 90faddb0-b512-4aff-9738-084b3eecc3af with sid
HVaYsT4NZY2UTkt4V00
v2Jw
com.cloud.consoleproxy.AuthenticationException: External authenticator failed
ree
quest for vm 90faddb0-b512-4aff-9738-084b3eecc3af with sid
HVaYsT4NZY2UTkt4V0v2JJ
w
not sure if that is relevant or not?
Thanks
Ian
-----Original Message-----
From: Wei ZHOU <ustcweiz...@gmail.com>
Sent: 11 June 2023 17:13
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
All looks good.
Can you check /var/log/cloud.log in cpvm if there are some errors ?
On Sunday, 11 June 2023, Ian Tobin <ito...@tidyhosts.com> wrote:
> Hi Wei,
>
> This is the output from consoleproxy
>
> root@v-26-VM:/etc# telnet 192.168.0.34 5900 Trying 192.168.0.34...
> Connected to 192.168.0.34.
> Escape character is '^]'.
> RFB 003.008
>
>
> Connection closed by foreign host.
> root@v-26-VM:/etc# telnet 192.168.0.34 5901
> Trying 192.168.0.34...
> Connected to 192.168.0.34.
> Escape character is '^]'.
> RFB 003.008
>
> Thanks
>
> Ian
>
>
>
> -----Original Message-----
> From: Wei ZHOU <ustcweiz...@gmail.com>
> Sent: 10 June 2023 16:19
> To: users@cloudstack.apache.org
> Subject: 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 <ito...@tidyhosts.com> 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
> > tcp 0 0 127.0.0.53:53 0.0.0.0:*
> LISTEN
> > tcp 0 0 0.0.0.0:41757 0.0.0.0:*
> LISTEN
> > tcp 0 0 0.0.0.0:33523 0.0.0.0:*
> LISTEN
> > tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN
> > tcp 0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN
> > tcp 0 0 0.0.0.0:16514 0.0.0.0:*
> LISTEN
> > tcp 0 0 192.168.0.34:5900 0.0.0.0:*
> LISTEN
> > tcp 0 0 192.168.0.34:5901 0.0.0.0:*
> LISTEN
> > tcp 0 256 192.168.0.34:22 192.168.0.97:53409
> > ESTABLISHED
> > tcp 0 0 192.168.0.34:670 192.168.0.37:2049
> > ESTABLISHED
> > tcp 0 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 <ustcweiz...@gmail.com>
> > 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 <ito...@tidyhosts.com> 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 <ustcweiz...@gmail.com>
> > > 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 <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/system
> > > > > vm
> > > > > .h
> > > > > tm
> > > > > 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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
