Applies to

StifleR Server

Google Chrome/Internet Explorer/Edge browsers


When attempting to access the StifleR Dashboard webpage locally on the StifleR IIS Server through http://localhost/StifleRDashboard a “Message from webpage” dialogue box is displayed showing “Failed to communicate with the server. Could not access: http://YourServerURL:9000/api/location

Also, when attempting to access the site both locally and remotely through the full URL path http://YourServerURL/StifleRDashboard a 401 Browser Security dialogue is displayed requesting credentials. This is as far as you will get without further configuration.


In StifleR 1.7 only members of the StifleR Global Admins Security group are allowed administrative level access to the Dashboards and, if configured, StifleR Global Read members are allowed Read access. This requires authentication and unless your internet security settings allow for automatic logon the errors listed above will be seen regardless of Group Membership.

This can also happen after a server upgrade - when cached browser settings can cause the issue.


The following is a checklist of troubleshooting steps if you encounter an issue with accessing the StifleR dashboards. This can happen while accessing the dashboards remotely - OR from the StifleR server itself.



Check lines 4/5 of the app.js file (by default in C:\Program Files\2Pint Software\StifleR\Dashboards\app)

They should contain the full FQDN of the stifleR server as shown below NOT 'Localhost' or any other variation.

app.value('backendServerUrl', 'http://SERVER.DOMAIN.COM:1414');

 app.constant('backendLocationServerUrl', 'http://SERVER.DOMAIN.COM:9000/api');

IIS Configuration:

Check that you have Windows Authentication enabled, and Anonymous Authentication disabled.

Further to that - check that the oly provider for WIndows Authentication is 'NTLM' (there should be no others present)

IE Security Zones

Check that the local server is added to the 'Local Intranet' zone


Check that you are using the correct URL to access the StifleR Dashboards

You should use the full FQDN i.e

Browser Cache

Finally - the browser cache may be caching old pages etc so clear that and reload the dashboard by pressing CTRL + F5