{"action":"opened","issue":{"url":"https://api.github.com/repos/openshift/openshift-docs/issues/1265","labels_url":"https://api.github.com/repos/openshift/openshift-docs/issues/1265/labels{/name}","comments_url":"https://api.github.com/repos/openshift/openshift-docs/issues/1265/comments","events_url":"https://api.github.com/repos/openshift/openshift-docs/issues/1265/events","html_url":"https://github.com/openshift/openshift-docs/issues/1265","id":118852406,"number":1265,"title":"Add a blurb on how to test in the Getting Started for Administrators guide","user":{"login":"tkramer-conversant","id":16018598,"avatar_url":"https://avatars.githubusercontent.com/u/16018598?v=3","gravatar_id":"","url":"https://api.github.com/users/tkramer-conversant","html_url":"https://github.com/tkramer-conversant","followers_url":"https://api.github.com/users/tkramer-conversant/followers","following_url":"https://api.github.com/users/tkramer-conversant/following{/other_user}","gists_url":"https://api.github.com/users/tkramer-conversant/gists{/gist_id}","starred_url":"https://api.github.com/users/tkramer-conversant/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tkramer-conversant/subscriptions","organizations_url":"https://api.github.com/users/tkramer-conversant/orgs","repos_url":"https://api.github.com/users/tkramer-conversant/repos","events_url":"https://api.github.com/users/tkramer-conversant/events{/privacy}","received_events_url":"https://api.github.com/users/tkramer-conversant/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-25T14:50:39Z","updated_at":"2015-11-25T14:50:39Z","closed_at":null,"body":"I have had two developers trying to do a quick install of OpenShift and they pointed out something that stuck them both.\r\n\r\nin:\r\nhttps://docs.openshift.org/latest/getting_started/administrators.html#running-in-a-docker-container\r\n\r\nUnder Method 1 it states:\r\n\r\n◦starts OpenShift listening on all interfaces (0.0.0.0:8443),\r\n\r\n\r\n◦starts the web console listening on all interfaces at /console (0.0.0.0:8443),\r\n\r\nI think a good third step would be to say to test the console connection.  When they did that they only tried http and it needs https.  I seen the blurb at the bottom but it would make it much clearer to have it in the same set of bullet points.  So a third line that says:\r\n\r\n- test the console   -   https://<server>:8443/console\r\n\r\nWould make it much clearer.\r\n"}}