NOTICE: We advise users to not update the Google Chrome Browser just yet if you use it for eLOQ Enterprise. Please do not go to Help>About as this will trigger the update.
UPDATE: 11/05/17 (current fix)
Please follow the below steps that need to be taken in Chrome and Opera browser if you see the below error and you know eLOQ Uplink is running.
Step1: Navigate to https://127.0.0.1:8080 or click this link. and you will see the image below:
Step2: Click the “Advanced button” and then select “Proceed to..” like below:
This will cause the eLOQ Uplink Icon to flash green and white alternatively, which means the browser can now communicate with eLOQ Uplink successfully:
Step3: Close eLOQ Uplink by right clicking on the icon and selecting “Exit” as shown in the image below. Then close the browser in which you navigated to 127.0.0.1 .
Step4: Re-launch the browser and eLOQ Uplink. Navigate to your unique login URL, the eLOQ Uplink error should not occur anymore and you will be able to use eLOQ Enterprise as usual.
Google Chrome developers have reacted to some security research that suggest there is exposed risk to users of the browser when connecting to local services.
Two articles about such attacks can be seen here:
However I would like to make clear this is NOT an issue with eLOQ Uplink but more to do with other devices e.g. old insecure routers that are on the localhost network.
Because the chrome developers cannot securely identify different use-cases over the localhost identifier they have for now blocked any networking to the local network i.e. 127.0.0.1, localhost etc.
A link to the bug tracker is here:
We have already identified a few possible solutions however we will hold out a little longer for some new news from the Chrome Dev team.
For the near future we advise not updating Chrome just yet.
However we understand this is not ideal so alternative browsers that can be used with eLOQ Uplink are below:
(List will keep being updated)
Microsoft Edge 40.15063.0.0 (Latest as of 21 April 2017)