Ah, I see. I believe you'd need access to whatever IP the consoleproxy vm
is listening on. I don't actually use the console proxy vm for my purposes,
but I don't think you need to open the vnc console or libvirt ports to the
outside. If the console proxy works internally, you probably just don't
ha
Would this be on the Console VM, Or from the node? Need to know which local IP
I need to redirect it to.
I see in the log, it’s coming from 192.168.1.43 (which is console vm) so I
suspect there?
--
Mo
Sent with Airmail
On October 15, 2014 at 1:00:12 PM, Marcus (shadow...@gmail.com) wrote:
>From outside, (say from hotel, through home router, to mgmt server) you
need access to the web ui and for the web ui to have access to the api
server. That would just be 8080 (UI) and 8096(API), I believe. you wouldn't
need libvirt and the others unless you are stringing mgmt servers and hosts
acr
Hello,
I’ve setup Cloudstack on my home server. However, it works without issues
locally. When I attempt to pull up console outside, it times out. I have of
course enabled ports for SSH / UI, so I can setup instances, but I am not sure
what else I need to permit through my router to allow all t
If you have assigned a certificate then it will be 443, otherwise it is
going over port 80.
On 10/14/14, 5:54 PM, "Mo" wrote:
>Hello,
>
>Locally I can access the console of my instances without issue. Outside
>of my network, I have trouble; therefore, I need to open ports. The
>problem is,
Hello,
Locally I can access the console of my instances without issue. Outside of my
network, I have trouble; therefore, I need to open ports. The problem is, I
have no clue what ports to add; according to some things I read 443 for VNC?
Could someone please advise?
// Mo
