Forum Discussion
[FIXED] Problem: Can't open unsafe ports on Edge insider
MicrosoftHotCakeX This command line works properly for me in Edge Canary 79.0.278. Please confirm that you've closed all msedge.exe instances (using task manager to ensure there aren't any hidden processes lingering) before starting a new one using this command line argument.
Eric_Lawrence yesterday I made a batch file:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" -explicitly-allowed-ports=6666 http://<redacted>:6666/
It worked yesterday, today it gives unsafe port error.
Thoughts?
Version 80.0.361.62 (Official build) (64-bit)
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!
- Eric_Lawrence
The 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.
- I was never able to get it to work. I ended up having to use a different browser, but eventually ditched the app that required that port.
Also, you should be updating to at least version 2004, if not 20H2. Version 1909 is out of support.
- Eric_LawrenceFor clarity, the command line above doesn't work because you need to pass --explicitly-allowed-ports with two leading dashes.
