It seems the issue was in DNS cache. After 30 minutes passed from the moment when I added new DNS record for console-proxy, the pop-up window now successfully shows remote console for the given VM.
P.S. For those who read this, if you use self-signed SSL certificate, don't use passphrase on cert creation, and don't use password when you convert cert to PKCS#8 format. Issue closed. Thanks. On Wed, May 14, 2014 at 8:16 PM, Владислав Старков <[email protected]> wrote: > After I added domain name to Global setting key > "consoleproxy.url.domain", it seems the JavaScript program in pop-up > window now started sending request to HTTPS and proper domain name is > used. However there is a drawback, the console proxy not working > anymore. > > Is it possible, that something wrong with SSL certificate that I've > uploaded to CloudStack (I suspect that the issue can be in > certificate's passphrase)? > > Thanks > > On Wed, May 14, 2014 at 11:20 AM, Prashant Kumar Mishra > <[email protected]> wrote: >> Can you check Global setting "consoleproxy.url.domain" value , HTTP will be >> used if this field is blank . >> >> Thanks >> Prashant >> >> -----Original Message----- >> From: Владислав Старков [mailto:[email protected]] >> Sent: Wednesday, May 14, 2014 5:10 AM >> To: [email protected] >> Subject: Console Proxy still not using HTTPS >> >> Hi, >> >> I've install SSL certificate to enable HTTPS for Console Proxy VM, as >> described on >> http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/systemvm.html#console-proxy >> >> However my Console window still connecting to Console Proxy VM through >> unencrypted HTTP. >> >> The question is, how to force it to use HTTPS? >> >> Thanks. >> >> >> -- >> Vlad -- С уважением, Старков Владислав Мобильная почта: [email protected] Сотовый: +7 (495) 960-50-75
