Is anything already listening on port 80/443/1936 on your host? Did the router pod get created successfully (oc get pods -n default)?
On Jul 27, 2016, at 7:12 AM, Lionel Orellana <[email protected]> wrote: My iptables has these rules. Is this normal? Chain KUBE-SERVICES (1 references) target prot opt source destination REJECT tcp -- 0.0.0.0/0 172.30.52.230 /* default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with icmp-port-unreachable REJECT tcp -- 0.0.0.0/0 172.30.52.230 /* default/router:443-tcp has no endpoints */ tcp dpt:443 reject-with icmp-port-unreachable REJECT tcp -- 0.0.0.0/0 172.30.52.230 /* default/router:1936-tcp has no endpoints */ tcp dpt:1936 reject-with icmp-port-unreachable On 27 July 2016 at 16:08, Lionel Orellana <[email protected]> wrote: > Further info > > $ oc get endpoints --namespace=default --selector=router > > NAME ENDPOINTS AGE > router <none> 1h > > Router has no endpoints? > > > > On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana <[email protected]> > wrote: > >> Forgot to mention >> >> Openshift v1.3.0-alpha.2 >> Docker 1.11.2 >> Ubuntu 15.10 >> >> On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana <[email protected]> >> wrote: >> >>> Hi >>> >>> I'm trying the new cluster up command. It seems to run Ok and I can >>> deploy an app (Jenkins, from the template) that also seems to start fine. >>> But I can't hit it. When I go to the url shown in the route chrome says >>> "site can't be reached". >>> >>> If I login to the host I can curl the aplication on the internal ip/port. >>> >>> Seems like a dns issue but I thought xip.io was supposed to take care >>> of that. >>> >>> Do I need to do anything to make my service accessible from outside? >>> >>> Thanks >>> >>> >>> Lionel. >>> >>> _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
