Hi Andrija, Thanks for the reply, basically what is happening is that on normal operation the console vms is listening on ports 80 and 8080, however when I configure a domain on consoleproxy.url.domain or consoleproxy.sslEnabled , for example: console.kuasar.net, and I recreate the systemvm, I only get the ssh working, and the apache2
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 169.254.239.147:3922 0.0.0.0:* LISTEN 1152/sshd Not so sure what is going on, if I rollback the change, removing the domain, then I get the console working on IP So I started the apache2 manually on the systemvm /etc/init.d/apache2 start And try to access getting a 404 not found now On 14/04/22, 3:44 AM, "Andrija Panic" <[email protected]> wrote: How do you try to " expose to Internet the ConsoleProxy VM using LoadBalancer"? What is your Public IP vs SSVM vs LoadBalancer vs DNS setup? When you initiate a Console access to a VM, your browser will connect to the Public IP of the SSVM (if no SSL used) or to the DNS name based on the Public IP, e.g. 11-22-33-44.mydomain.com (if you have configured SSL) - this might resolve to the IP public IP of your loadbalancer - then it's LB work to correctly pass all traffic to whatever is the CURRENTLY USED public IP of the SSVM That error, is a typical load balancer error when the backend server is not reachable - check LB and the backend (public IP of the SSVM) configured. Your error is too generic to be able to help. On Mon, 11 Apr 2022 at 20:42, Ricardo Pertuz <[email protected]> wrote: > Hi, > > When I try to expose to Internet the ConsoleProxy VM using LoadBalancer > with a valid domain and cert, I’m getting a “502 Bad Gateway” when click on > the console icon. I have configured these params > > consoleproxy.sslEnabled > consoleproxy.url.domain > > am I missing something? > > CloudStack 4.15.2.0 > > Regards, > > > > -- Andrija Panić
