Forum Discussion
[FIXED] Problem: Can't open unsafe ports on Edge insider
UPDATE: Fixed in Edge insider Version 79.0.280.0 (Official build) canary (64-bit) I need to open a custom port for WAC. I can do that with Google Chrome Canary 79 by adding this to the shortcu...
Eric_Lawrence
Microsoft
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)
- Eric_LawrenceFor clarity, the command line above doesn't work because you need to pass --explicitly-allowed-ports with two leading dashes.
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.
- Yes, I think the problem was solved in Edge insider 79. now I'm testing it on version
Version 79.0.280.0 (Official build) canary (64-bit)
and it's working fine.
