Forum Discussion
[FIXED] Problem: Can't open unsafe ports on Edge insider
eric79xxl After updating to Win10 Version 1909 / Edge Version 91.0.864.48 I cannot reach an https website on port 10080 anymore. Edge shows error ERR_UNSAFE_PORT. I tried to start Edge with parameter --explicitly-allowed-ports=10080 but no success. Thanks for your support!
MicrosoftThe command line
msedge.exe --explicitly-allowed-ports=10080 http://example.com:10080
...still works properly as of Edge 93. Keep in mind, however, that command lines only take effect when the browser is started from scratch. If there's an msedge.exe instance already running (even a hidden one created by the "Startup Boost" feature, the command line will be ignored.
You can visit edge://version/ to see the command-line currently in use by the active browser.
Eric_Lawrence
How this can be accepted as a solution?
Is it normal for a simple user, to check every time either task manager or command line, if there are open msedge instances running?
The target with the allowed port "msedge.exe --explicitly-allowed-ports=10080 http://example.com:10080" is supposed to have been set already by the administrator.
I can't image, that still there is no other workaround from Microsoft, to just open the browser and open properly the link with the desired port.
PS: This is not an issue in other browsers eg. chrome and firefox.Solution:
1) Disable all the features that exist within "Edge Settings > System and Performance" of Microsoft Edge (eg. Efficiency mode, Save resources with sleeping tabs, etc.) and then after closing the browser Microsoft Edge, no more edge instances will be running on the background.
That means that the described solution on this thread can work:
2) Microsoft edge app --> right click --> properties --> shortcut tab --> Target
And there add the desired port (you want to forward) like below:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --explicitly-allowed-ports=10080- Thank you for this!
Separate from the ports, I have long wondered why there's always so many processes of msedge.exe.
I will try those settings today!
