Re: Unable to start openshift in VM, AWS or google cloud

Looks like we're not displaying the public address after it starts. However, you should be able to access it at the server's public address: https://ec2-54-227-129-18.compute-1.amazonaws.com:8443/ On Nov 3, 2016, at 4:23 PM, Ravi Kapoor wrote: I tried this, it still starts at private IP address

Re: Unable to start openshift in VM, AWS or google cloud

> Have you installed a router? Does DNS or /etc/hosts for the route direct your browser to the host's IP? my browser is running within the same VM where openshift is starting. Also it is able to load the console. The issue is that when I do a deployment, I am not able to access the route. I am abl

Re: Unable to start openshift in VM, AWS or google cloud

I tried this, it still starts at private IP address. My logs are copied below notice that I want to start at 54.227.129.18 but server starts at https://172.31.32.131:8443 What am I doing wrong? -- [ec2-user@ip-172-31-32-131 openshift131]$ ./oc c

Re: Unable to start openshift in VM, AWS or google cloud

Hi Ravi, On AWS, the magic incantation is: oc cluster up --public-hostname=[public dns name] --routing-suffix=[ip address].xip.io Don't specify the numeric ip address in --public-hostname, rather the dns name. You can then access the web console at https://[public

Re: Unable to start openshift in VM, AWS or google cloud

On Wed, Nov 2, 2016 at 11:34 PM, Ravi wrote: > > I am not able to start openshift, I tried three different ways. > > 1. Windows 7 + Virtual Box + Ubuntu > oc cluster up works well. I went to console and launched nodejs-ex > example. Console shows it is up, however when I click on route, it says >

Unable to start openshift in VM, AWS or google cloud

I am not able to start openshift, I tried three different ways. 1. Windows 7 + Virtual Box + Ubuntu oc cluster up works well. I went to console and launched nodejs-ex example. Console shows it is up, however when I click on route, it says "unable to connect". I tried going directly to POD's IP