Hi Amogh,

Thanks for the headsup...As told by you I tried ping from external network
and found that i cudnt...I checked on the net and found that by default
egress is allowed but ingress is blocked on virtual machine security
groups...So I proceeded to add the following rules in ingress

TCP startport = 0 end port = 65535 CIDR= 0.0.0.0/0
UDP startport = 0 end port = 65535 CIDR= 0.0.0.0/0
for ping i added the following rule
ICMP ICMP type = -1 ICMP Code = -1 CIDR=0.0.0.0/0

I think these all info along with the port issue being 80 and not 443 now
should be added to the cloudstack wiki so that users can easily append
these..

Regards :) :)


On Wed, Nov 19, 2014 at 7:39 AM, Amogh Vasekar <amogh.vase...@citrix.com>
wrote:

> By default console proxy will run in HTTP mode and listen on port 80.
> If you wish to run on HTTPS, you will need to set up your own DNS and SSL
> certificate.
> The wiki you mentioned needs to be updated with current info :-)
>
> For the second part of not being able to reach the web service - I'd start
> by checking if I can ping the web server machine, and review the security
> policies of the network attached to this VM (security groups if any,
> ingress/egress rules etc)
>
> HTH
> Amogh
>
> On 11/17/14 11:17 PM, "Tilak Raj Singh" <tila...@gmail.com> wrote:
>
> >Hi..
> >
> >I am using cloudstack 4.4.1 on a single machine
> >As I can see in global settings there is no value assigned to
> >consoleproxy.url.domain. The field is empty. Do I have to assign any value
> >in there?
> >
> >I reinstalled cloudstack from start again. Now I can access the machines
> >using the console button but still the output of
> >
> >netstat -na | grep 443 gives nothing
> >
> >Further information about my setup
> >
> >Management server ip 172.31.101.202
> >gateway 172.31.100.1
> >dns 172.31.100.6, 172.31.100.8
> >private ip pool 172.31.101.210-172.31.101.230
> >public ip pool 172.31.101.240-172.31.101.250
> >
> >v-1-vm :- public  ip 172.31.101.245
> >             private ip 172.31.101.222
> >             link local ip 169.254.0.117
> >
> >s-2-vm :-  public  ip 172.31.101.250
> >             private ip 172.31.101.210
> >             link local ip 169.254.3.141
> >
> >r-4-vm :- public ip 172.31.101.249
> >             link local ip 169.254.3.10
> >
> >the testmachine is running at ip 172.31.101.248
> >
> >the issue I am facing now is that i created an apache webservice on my
> >test
> >machine i.e. 172.31.101.248
> >this service can be accessed by the browser of the management server i.e.
> >172.31.101.202
> >but i cant access it from my room i.e. 172.31.84.72 (its a different
> >subnet)
> >the management server is located in the server room of my college with
> >default gateway of 172.31.100.1 mask 255.255.252.0
> >
> >route -n on the management server gives
> >
> >route -n
> >Kernel IP routing table
> >Destination     Gateway         Genmask         Flags Metric Ref    Use
> >Iface
> >172.31.100.0    0.0.0.0         255.255.252.0   U     0      0        0
> >cloudbr0
> >169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
> >cloud0
> >0.0.0.0         172.31.100.1    0.0.0.0         UG    0      0        0
> >cloudbr0
> >
> >here cloudbr0 is the network bridge i created on my management server
> >and sent all the requests from eth0 to cloudbr0
> >
> >and on the virtual machine hosting the service gives
> >
> >route -n
> >Kernel IP routing table
> >Destination     Gateway         Genmask         Flags Metric Ref    Use
> >Iface
> >172.31.100.0    0.0.0.0         255.255.252.0   U     0      0        0
> >eth0
> >169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0
> >eth0
> >0.0.0.0         172.31.100.1    0.0.0.0         UG    0      0        0
> >eth0
> >
> >So what do i need to do to make the webservice running on my virtual
> >machine to be accessible from the system in my room??
> >The virtual machine can access the webservices running on the machine in
> >my
> >room but vice versa is not possible
> >the virtual machine can also access the internet.
> >So do I need to make any changes in the router 172.31.100.1 or the fault
> >is
> >somewhere in my installation or there is some other issue??
> >
> >Please help
> >
> >On Mon, Nov 17, 2014 at 3:29 AM, Amogh Vasekar <amogh.vase...@citrix.com>
> >wrote:
> >
> >> Hi,
> >>
> >> Which version of CS are you on? Also, what is the value of
> >> consoleproxy.url.domain global parameter?
> >>
> >> Amogh
> >>
> >> On 11/15/14 2:57 AM, "Tilak Raj Singh" <tila...@gmail.com> wrote:
> >>
> >> >hello everyone.
> >> >I am new to cloudstack and I am having a issue with my cloudstack
> >> >installation.when i try to hit the console button of my vm the browser
> >> >says
> >> >request timed out. It was working earlier but now its not after I
> >>rebooted
> >> >my machine once.
> >> >
> >> >i tried to ssh into my console proxy and check all the commands listed
> >> >here
> >> >
> >>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/View+Console+and+C
> >>o
> >> >nsole+Proxy+Troubleshooting
> >> >
> >> >netstat -na | grep 443
> >> >
> >> >This command gives no output. As i can understand port 443 is not
> >>bound to
> >> >java. All the other commands are running.
> >> >I even restarted my console proxy and also tried running command
> >>"service
> >> >cloud restart" from the console proxy to looked at the
> >>/var/log/cloud.log
> >> >file. But nothing seems to be any problem there.
> >> >
> >> >Can anybody please help me with this issue.
> >> >
> >> >Regards,
> >> >Tilak Raj Singh
> >>
> >>
>
>

Reply via email to