# Localhost:8989 unable to connect **URL:** \ **Category:** openXDA\ **Created:** [April 11, 2018, 1:44am UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309 "2018-04-11T01:44:37Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![TLawanson](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/tlawanson/32/249_2.png) [@TLawanson](http://discussions.gridprotectionalliance.org/u/TLawanson)\ **Post date:** [April 11, 2018, 1:44am UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/1 "2018-04-11T01:44:37Z")
Hello All, I just installed openHistorian, openXDA and PQDashboard, but I am unable to access the openXDA web manager through [http://localhost:8989](http://localhost:8989) - the browser (Firefox, Chrome and Internet Explorer) returns an “unable to connect” message. Also, I have tried to launch the openXDA console, but I keep getting the error message shown in the snapshot. ![Capture](http://discussions.gridprotectionalliance.org/uploads/default/original/1X/e60cf5e633eb70387709570a13787eeb0bb83f6f.PNG) I would appreciate your help with this error. Thanks, Tumi ---
**Author:** ![bernest](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/bernest/32/378_2.png) [@bernest](http://discussions.gridprotectionalliance.org/u/bernest)\ **Post date:** [April 11, 2018, 12:38pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/2 "2018-04-11T12:38:41Z")
Hi Tumi, Generally, this error means that the openXDA service is not running. Check in the Windows Services screen. If it fails to start from there, you may want to check the Event Viewer to see what kind of error you are receiving when trying to start the service. ---
**Author:** ![TLawanson](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/tlawanson/32/249_2.png) [@TLawanson](http://discussions.gridprotectionalliance.org/u/TLawanson)\ **Post date:** [April 11, 2018, 4:14pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/3 "2018-04-11T16:14:53Z")
Hi Bernest, Thanks for your help. I was able to start openXDA service in the Windows services screen just as you suggested. Now, I am able to connect to [http://localhost:8989/](http://localhost:8989/) but I am unable to get past the “Authentication Required” dialog box. I put in the same username and password I used for Open PQ dashboard and openHistorian, but the box just reappears each time. ![image](http://discussions.gridprotectionalliance.org/uploads/default/original/1X/2981559e966c78aaa819acb929156263208675b7.png) I have read through a previous discussion on the same error here: [Authorization Problem for localhost:8989 no working - #9 by fischerbast](http://discussions.gridprotectionalliance.org/t/authorization-problem-for-localhost-8989-no-working/270/9) but I could not find a solution. I would appreciate your help with resolving this. Thanks, Tumi ---
**Author:** ![bernest](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/bernest/32/378_2.png) [@bernest](http://discussions.gridprotectionalliance.org/u/bernest)\ **Post date:** [April 11, 2018, 6:18pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/4 "2018-04-11T18:18:58Z")
Tumi, Try using the Chrome browser, its pass-through authentication tends to work better. ---
**Author:** ![TLawanson](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/tlawanson/32/249_2.png) [@TLawanson](http://discussions.gridprotectionalliance.org/u/TLawanson)\ **Post date:** [April 11, 2018, 7:47pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/5 "2018-04-11T19:47:15Z")
Thanks again Bernest. I have tried using the Chrome browser, but I was still unable to login - the authentication box keeps popping up. ---
**Author:** ![bernest](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/bernest/32/378_2.png) [@bernest](http://discussions.gridprotectionalliance.org/u/bernest)\ **Post date:** [April 12, 2018, 12:17pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/6 "2018-04-12T12:17:14Z")
Tumi, Is the openXDA Console app connecting now? ---
**Author:** ![TLawanson](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/tlawanson/32/249_2.png) [@TLawanson](http://discussions.gridprotectionalliance.org/u/TLawanson)\ **Post date:** [April 12, 2018, 3:58pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/7 "2018-04-12T15:58:43Z")
Yes, the openXDA Console app is connecting. ![image](http://discussions.gridprotectionalliance.org/uploads/default/original/1X/5ace24175c55ba263a6227499b343d817fa2c18f.png) But I am still not able to login to [http://localhost:8989/](http://localhost:8989/) ---
**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\ **Post date:** [April 12, 2018, 5:04pm UTC](http://discussions.gridprotectionalliance.org/t/localhost-8989-unable-to-connect/309/8 "2018-04-12T17:04:12Z")
Hi Tumi, There seems to be a fairly widespread issue where NTLM authentication fails for unknown reasons on certain networks. When this error occurs, the web server within openXDA will continually respond with 401, causing the browser to repeatedly ask for the user’s credentials. We have not been able to reproduce this issue, and HttpListener doesn’t provide enough information about the authentication process for us to even begin to understand what might be failing. As there are no other supported authentication mechanisms in openXDA, there are also no workarounds at this time. Unless you can provide some more details to help us pin down the solution to this problem, like maybe inspecting the request and response headers, I don’t think there’s any way we can help you. Thanks, Stephen