[ https://issues.apache.org/jira/browse/CLOUDSTACK-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239342#comment-14239342 ]
Rohit Yadav commented on CLOUDSTACK-7572: ----------------------------------------- I checked https://issues.apache.org/jira/browse/CLOUDSTACK-6204 's fix, it worked fine on 4.3.0 but then a commit broke it for users who will migrate to 4.3.1. The fix (that I'll add in release docs for 4.3.1 is that they need to add *. to the domain if they are using wildcard certificates). In 4.3.2 we'll try to fix it. > Virtual Console Proxy url domain > -------------------------------- > > Key: CLOUDSTACK-7572 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7572 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy > Affects Versions: 4.3.1 > Environment: CentOS 6.5, CloudStack 4.3.1 from rhel packages. > Reporter: Martins Jakubovics > Assignee: Rohit Yadav > > After CS upgrade from 4.3.0 or fresh install of 4.3.1, value > "consoleproxy.url.domain" stopped to work. When launch console proxy, it > connect to ".realhostip.com" domain in a way to connect real domain. When I > clean this value, console proxy connects to IP. After entering any other > value it connects to ".realhostip.com" anyway. -- This message was sent by Atlassian JIRA (v6.3.4#6332)