[jbosstools-issues] [JBoss JIRA] (JBDS-3746) Unable to access OpenShift console with MS Edge

Misha Ali (JIRA) issues at jboss.org
Wed Apr 20 20:35:00 EDT 2016


    [ https://issues.jboss.org/browse/JBDS-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194853#comment-13194853 ] 

Misha Ali commented on JBDS-3746:
---------------------------------

Not assigned to me, but done for docs: https://access.redhat.com/articles/2255391#openshift-console-inaccessible-on-microsoft-edge-browser

Do we want to leave this open to track any other part of this task or close it off after assigning it to me?

> Unable to access OpenShift console with MS Edge 
> ------------------------------------------------
>
>                 Key: JBDS-3746
>                 URL: https://issues.jboss.org/browse/JBDS-3746
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Task
>          Components: documentation, installer
>         Environment: Windows 10 Pro
>            Reporter: Hardy Ferentschik
>              Labels: havoc
>             Fix For: 9.1.0.GA
>
>
> On Windows 10 (Pro) after installing and starting the CDK development environment, one is not able to access the OpenShift console (https://10.1.2.2:8443/console) using Microsoft Edge. The IP of the host only network IP does not matter. Using a 192.168 address won't work either. 
> Using any other browser - IE, Chrome, Firefox - the console can be reached. It seems to be an Edge specific issue and may report the same issue:
> * http://www.tenforums.com/installation-setup/8979-dont-forget-edge-can-access-localhost-type-ip-addresses-now.html
> * https://social.technet.microsoft.com/Forums/forefront/en-US/0face535-3c7a-4658-be34-6c376322ca34/microsoft-edge-cant-open-local-domains?forum=win10itpronetworking
> * https://www.google.se/search?q=edge+canot+acess+page&ie=utf-8&oe=utf-8&gws_rd=cr&ei=_CX9VtbrEIq4sQGA77DABg#q=edge+hmm+we+can%27t+reach+this+page
> I tried several work-arounds, but none worked so far. If there were a confirmed workaround one could image the installer applying it (if possible). In this case we might want to add a warning somewhere in the installer or at least somewhere in the documentation. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list