[GitHub] [cloudstack] nxsbi commented on issue #4612: After Upgrade to 4.15, NoVNC Console not working - HTTP 403, legacy console works

[GitBox <gi...@apache.org>]

nxsbi commented on issue #4612:
URL: https://github.com/apache/cloudstack/issues/4612#issuecomment-910516377


   > nxsbi - I'm running into an issue where noVNC is using the hypervisor host IP to launch the console instead of FQDN. You said you are using SSL as well. Is your cert a wildcard cert for domain name and/or IP address?
   > 
   > I'm on ACS 4.15.1 and VMware 7.
   
   I use a wildcard certificate *.consoleproxy.yoursite.com
   You need to also make sure your Global Setting "consoleproxy.url.domain" parameter shows the exact same domain consoleproxysecure.yoursite.com - where the consoleproxy.yoursite.com is a publicly available domain. I had to add an A record on my domain to forward the console proxy external IP to resolve to that name. 
   
   Once you have added the certificate, as listed on http://docs.cloudstack.apache.org/en/latest/adminguide/systemvm.html#using-a-ssl-certificate-for-the-console-proxy
    you should destroy the console proxy VM so a new one gets created. Restarting did not work for me. 
   
   In my case I did not add the ROOT CA or Intermediate CA
   
   Hope this helps
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org