RE: When i update 4.2.1 to 4.3.0,console don't work

2014-04-02 Thread Martin Knott
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!


RE: When i update 4.2.1 to 4.3.0,console don't work

2014-04-02 Thread Martin Knott
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!