On Thu, May 15, 2014 at 2:41 AM, Ian Young wrote:
> I decided to create my own internal realhostip.com. My DNS servers use
> PowerDNS, not BIND, so the $GENERATE directive was not an option and I
> didn't want to have to populate my DNS servers' databases with a record for
> every possible IP ad
Mobile network.
Original Message
From: Ian Young
Sent: Friday, May 16, 2014 2:47 PM
To: users@cloudstack.apache.org
Reply To: users@cloudstack.apache.org
Subject: Re: replacement for realhostip
The problem appears to be with the console proxy itself. Here are the
ports that are listening on the
yes, you can not use realhostip.com.
On 14/05/14 08:56 PM, Ian Young wrote:
Looks like it's still using HTTP, not HTTPS:
2014-05-14 17:52:35,812 DEBUG [c.c.a.t.Request] (catalina-exec-20:null) Seq
1-800529939: Sending { Cmd , MgmtId: 161342909744, via: 1(
virthost1.lax.ratespecial.com), Ver: v
I just realized I had to set the consoleproxy.url.domain field to "
realhostip.com" but now when I try to view the console, the browser says
"The server refused the connection." Does that indicate a problem with the
SSL certificate?
management-server.log:
2014-05-15 14:43:55,506 DEBUG [c.c.a.t.Re
I was able to confirm the certificate by going directly to
https://192-168-100-159.realhostip.com/ in the browser. I wish there was
an easier way to do this. I don't mind the extra step, and the rest of my
tech team will understand how it works but it's going to be a hassle
explaining this proced
4.3
consoleproxy.url.domain = realhostip.com
It's working now. I'm just responding to clarify those questions.
On Thu, May 15, 2014 at 10:43 AM, Amogh Vasekar wrote:
> Hi,
>
> Which version of CloudStack are you on?
> Also, what does the config "console proxy.url.domain" refer to?
>
> Thanks,
Ok, so the console proxy needed to be restarted in order for the
consoleproxy.url.domain
setting to take effect. However, I still can't see the console. In
Chrome, it just shows a frowning face with no error message (not very
useful). In Firefox, at least it tells me the certificate is not trust
The problem appears to be with the console proxy itself. Here are the
ports that are listening on the public interface, according to an nmap TCP
scan:
PORTSTATE SERVICE
80/tcp open http
443/tcp closed https
When I logged into the console proxy through the link local address, I
checked fo
Hi,
Which version of CloudStack are you on?
Also, what does the config "console proxy.url.domain" refer to?
Thanks,
Amogh
On 5/14/14 5:41 PM, "Ian Young" wrote:
>I decided to create my own internal realhostip.com. My DNS servers use
>PowerDNS, not BIND, so the $GENERATE directive was not an o
Looks like it's still using HTTP, not HTTPS:
2014-05-14 17:52:35,812 DEBUG [c.c.a.t.Request] (catalina-exec-20:null) Seq
1-800529939: Sending { Cmd , MgmtId: 161342909744, via: 1(
virthost1.lax.ratespecial.com), Ver: v1, Flags: 100011,
[{"com.cloud.agent.api.GetVncPortCommand":{"id":6,"name":"i-5
10 matches
Mail list logo
