Thanks, I will try then
________________________________ From: Andrija Panic <andrija.pa...@gmail.com> Sent: Wednesday, April 20, 2022 4:29:22 AM To: users <users@cloudstack.apache.org> Subject: Re: Bad Gateway: Expose Cloudstack Console Proxy Ricardo, if you have not provided a proper SSL certificate to CloudStack, that might also be an issue. Can you please try to have things set up withOUT the load balancer first, to make sure you have the right ACS config in place? You have not provided enough information on what/how EXACTLY you have configured the rest of the ACS setting (did you upload SSL or not), and also how the SSL is set up on the LB, etc. Please start simple, set things without LB< then work your way up to using the LB. Regards, Andrija On Thu, 14 Apr 2022 at 15:31, Ricardo Pertuz <ricardo.per...@kuasar.co> wrote: > 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" <andrija.pa...@gmail.com> 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 <ricardo.per...@kuasar.co > > > 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ć > > -- Andrija Panić
