Re: When i update 4.2.1 to 4.3.0,console don't work
Hi, Please change global config "console proxy.url.domain" to realhostip.com Thanks, Amogh On 4/1/14 6:59 PM, "ma y" wrote: >When i open vm console, i got this info from management server log ,like " >https://192-168-28-2.*.realhostip.com/...",and it don't work. >I think the problem is my computer can't resolve this domain name >"192-168-28-2.*.realhostip.com". >In CS 4.2.1 , that domain name like "192-168-28-2.realhostip.com" , and it >works well. >So, is this a bug for CS 4.3.0 ? How to fix this? >Thks!
Re: When i update 4.2.1 to 4.3.0,console don't work
Thk u ! It works. However , is this a bug for 4.3.0 ? 2014-04-02 10:02 GMT+08:00 Amogh Vasekar : > Hi, > > Please change global config "console proxy.url.domain" to realhostip.com > > Thanks, > Amogh > > On 4/1/14 6:59 PM, "ma y" wrote: > > >When i open vm console, i got this info from management server log ,like " > >https://192-168-28-2.*.realhostip.com/...",and it don't work. > >I think the problem is my computer can't resolve this domain name > >"192-168-28-2.*.realhostip.com". > >In CS 4.2.1 , that domain name like "192-168-28-2.realhostip.com" , and > it > >works well. > >So, is this a bug for CS 4.3.0 ? How to fix this? > >Thks! > >
Re: When i update 4.2.1 to 4.3.0,console don't work
I believe I saw an email saying that realhostip.com has been retired? Regardless, it's been terribly unreliable anyways and you should move away from it. Good luck though, I haven't managed to get the SSL Certificate change to work due to CS inability to handle certificate chains - despite many attempts with every trick found on google and this list. It's a very much incomplete part of CS. Mark > On 2 Apr 2014, at 1:04 pm, "ma y" wrote: > > When i open vm console, i got this info from management server log ,like " > https://192-168-28-2.*.realhostip.com/...",and it don't work. > I think the problem is my computer can't resolve this domain name > "192-168-28-2.*.realhostip.com". > In CS 4.2.1 , that domain name like "192-168-28-2.realhostip.com" , and it > works well. > So, is this a bug for CS 4.3.0 ? How to fix this? > Thks!
Re: When i update 4.2.1 to 4.3.0,console don't work
Hi, Can you please let us know the errors you observed for chains? If its broken, gotta be fixed :-) Thanks, Amogh On 4/1/14 7:38 PM, "Mark van der Meulen" wrote: >I believe I saw an email saying that realhostip.com has been retired? >Regardless, it's been terribly unreliable anyways and you should move >away from it. > >Good luck though, I haven't managed to get the SSL Certificate change to >work due to CS inability to handle certificate chains - despite many >attempts with every trick found on google and this list. It's a very much >incomplete part of CS. > >Mark > >> On 2 Apr 2014, at 1:04 pm, "ma y" wrote: >> >> When i open vm console, i got this info from management server log >>,like " >> https://192-168-28-2.*.realhostip.com/...",and it don't work. >> I think the problem is my computer can't resolve this domain name >> "192-168-28-2.*.realhostip.com". >> In CS 4.2.1 , that domain name like "192-168-28-2.realhostip.com" , and >>it >> works well. >> So, is this a bug for CS 4.3.0 ? How to fix this? >> Thks!
Re: When i update 4.2.1 to 4.3.0,console don't work
I updated my CS from 4.2.1 to 4.3.0. Once operation has been completed , the "console" feature in UI can't work yet, then i try your method to change global config "*.realhostip.com"(default) to "realhostip.com" and it works. Hope this can help u .
RE: When i update 4.2.1 to 4.3.0,console don't work
Hi I'm getting the same dns errors on the cloudstack Console Restarted VM Console And can ping and dns resolves fine from the consoles command prompt rolled back to 4.2.1 it's fine Please confirm if it's a bug Regards -Original Message- From: ma y [mailto:breeze7...@gmail.com] Sent: 02 April 2014 03:00 To: cloudstack-us...@incubator.apache.org Subject: When i update 4.2.1 to 4.3.0,console don't work When i open vm console, i got this info from management server log ,like " https://192-168-28-2.*.realhostip.com/...",and it don't work. I think the problem is my computer can't resolve this domain name "192-168-28-2.*.realhostip.com". In CS 4.2.1 , that domain name like "192-168-28-2.realhostip.com" , and it works well. So, is this a bug for CS 4.3.0 ? How to fix this? Thks!
RE: When i update 4.2.1 to 4.3.0,console don't work
Amough is on the money Fixed mine move from global settings consoleproxy.url.domain from *.realhostip.com to realhostip.com Regards Martin -Original Message- From: Martin Knott [mailto:mkn...@novemgroup.co.uk] Sent: 02 April 2014 10:15 To: users@cloudstack.apache.org Subject: RE: When i update 4.2.1 to 4.3.0,console don't work Hi I'm getting the same dns errors on the cloudstack Console Restarted VM Console And can ping and dns resolves fine from the consoles command prompt rolled back to 4.2.1 it's fine Please confirm if it's a bug Regards -Original Message- From: ma y [mailto:breeze7...@gmail.com] Sent: 02 April 2014 03:00 To: cloudstack-us...@incubator.apache.org Subject: When i update 4.2.1 to 4.3.0,console don't work When i open vm console, i got this info from management server log ,like " https://192-168-28-2.*.realhostip.com/...",and it don't work. I think the problem is my computer can't resolve this domain name "192-168-28-2.*.realhostip.com". In CS 4.2.1 , that domain name like "192-168-28-2.realhostip.com" , and it works well. So, is this a bug for CS 4.3.0 ? How to fix this? Thks!
