Re: Upgrade to 4.3.1

2014-12-09 Thread Rohit Yadav
Hi, Regarding the console proxy url issue, this was a regression introduce in 4.3.1 release and will be faced by all users using the feature with 4.3.1 (freshly installed or upgraded to 4.3.1). JFYI, It has been fixed with 4.3.2: http://issues.apache.org/jira/browse/CLOUDSTACK-7572 On Tuesday 1

Re: Upgrade to 4.3.1

2014-09-26 Thread France
I am not the original poster, but I have upgraded from 4.1.1 to 4.3.1 and have working console. It did not work when HTTP was disabled and HTTPS was used for default GUI access, so we rolled out our own CA and certificates, updated via GUI ( https://issues.apache.org/jira/browse/CLOUDSTACK-7635

Re: Upgrade to 4.3.1

2014-09-26 Thread Sebastien Goasguen
Can we circulate back on this and determine whether there is an issue in 4.3.1 or not ? and if yes, which commit caused it. thanks, On Sep 18, 2014, at 7:29 PM, Amogh Vasekar wrote: > Hi, > > Please use "*.realhostip.com" (note the asterisk) as > consoleproxy.url.domain value in global confi

Re: Upgrade to 4.3.1

2014-09-18 Thread Amogh Vasekar
Hi, Please use "*.realhostip.com" (note the asterisk) as consoleproxy.url.domain value in global configs if you are using HTTPS for console proxy (I.e. Ever had a pre-4.3 version in your set-up) If you started with 4.3, you are likely running the console in HTTP mode and the value of the above glo

Re: Upgrade to 4.3.1

2014-09-18 Thread Rohit Yadav
Thanks for reporting, can you please open an issue. Looks like an easy issue, we should be able to fix it. On 18-Sep-2014, at 9:30 pm, Hollman Enciso R. wrote: > On Wed, Sep 17, 2014 at 1:05 AM, Mārtiņš Jakubovičs > wrote: > >> Hello Ilya, >> >> Thanks for response, I upgraded from 4.3.0 to 4.3

Re: Upgrade to 4.3.1

2014-09-18 Thread Aldis Gerhards
We reinstalled to 4.3.0 which was working. It seems there is a bug in console in 4.3.1. Sent from my iPhone > On 2014. gada 18. sept., at 22:30, Hollman Enciso R. > wrote: > > On Wed, Sep 17, 2014 at 1:05 AM, Mārtiņš Jakubovičs > wrote: > >> Hello Ilya, >> >> Thanks for response, I upgrade

Re: Upgrade to 4.3.1

2014-09-18 Thread Hollman Enciso R.
On Wed, Sep 17, 2014 at 1:05 AM, Mārtiņš Jakubovičs wrote: > Hello Ilya, > > Thanks for response, I upgraded from 4.3.0 to 4.3.1. > Hello Martins. I recently upgrade my test envioroment from 4.3.0 to 4.3.1 and i have the same problem. not load the console. i'm not usig any domain yat. how you

Re: Upgrade to 4.3.1

2014-09-16 Thread Mārtiņš Jakubovičs
Hello Ilya, Thanks for response, I upgraded from 4.3.0 to 4.3.1. On 2014.09.17. 03:34, ilya musayev wrote: Mārtiņš If you dont get a response here, please post on dev. I'll try this out shortly in my env, what version did you upgrade from? Regards ilya On 9/16/14, 6:07 AM, Mārtiņš Jakubovič

Re: Upgrade to 4.3.1

2014-09-16 Thread Aldis Gerhards
We upgraded from version 4.3 to 4.3.1 Sent from my iPhone > On 2014. gada 17. sept., at 03:34, ilya musayev > wrote: > > Mārtiņš > > If you dont get a response here, please post on dev. I'll try this out > shortly in my env, what version did you upgrade from? > > Regards > ilya >> On 9/16/

Re: Upgrade to 4.3.1

2014-09-16 Thread ilya musayev
Mārtiņš If you dont get a response here, please post on dev. I'll try this out shortly in my env, what version did you upgrade from? Regards ilya On 9/16/14, 6:07 AM, Mārtiņš Jakubovičs wrote: Hello, In CentOS 6.5 today I discovered that is available update for CS 4.3. I installed it but af

Upgrade to 4.3.1

2014-09-16 Thread Mārtiņš Jakubovičs
Hello, In CentOS 6.5 today I discovered that is available update for CS 4.3. I installed it but after management service restart " consoleproxy.url.domain" value stopped to work. When I launch console proxy, it connect to ".realhostip.com" domain in a way to connect my real domain. When I cle