Troubleshooting
Last updated
Last updated
In some cases we have observed Microsoft Edge blocking connections to localhost, making it unable to communicate with the installed GCL instance.
Microsoft runs as a modern Windows app, which means it has network isolation enabled by default for security reasons. However, by default an exception is made for loopback/localhost addresses. This means that on most Edge browsers, communication with the GCL instance will not be a problem.
In specific cases though (exact reasons as yet unknown), it seems that this exception is ignored or not applied correctly, blocking communication with localhost.
If you find yourself in this situation, try the following options to resolve:
Open your browser and type about:flags in the address bar. This will open a hidden browser settings menu. Locate the Developer settings and make sure the option to Allow localhost loopback is checked.
The number of options under the Developer settings heading can vary between the different versions of Microsoft Edge, but the localhost loopback option should always be there.
Once the option is enabled, fully close down Microsoft Edge and restart the browser.
If this option was already enabled, try disabling it, restarting the browser and then re-enabling.
Check if this has resolved the issue. If not, proceed to option B.
B. Use the command prompt
Open a command prompt as administrator(!) and execute the following command:
Windows will respond with the message OK.
Restart Microsoft Edge and check if the issue is resolved.
https://blogs.msdn.microsoft.com/msgulfcommunity/2015/07/01/how-to-debug-localhost-on-microsoft-edge/https://www.ibm.com/support/knowledgecenter/en/SSPH29_9.0.3/com.ibm.help.common.infocenter.aps/r_LoopbackForEdge.html
