Sep 18 2019 04:36 AM - edited Sep 22 2019 02:50 AM
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 shortcut target: "--explicitly-allowed-ports=6666" and it loads the WAC console just fine.
but when I do the same for Edge insider Canary, it won't work and still gives me the unsafe port error.
Edge Insider Version 78.0.277.0 (Official build) canary (64-bit)
Windows 10 latest ver
WAC 1909
Sep 20 2019 04:33 PM
@HotCakeX 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.
Sep 22 2019 02:49 AM
Mar 02 2020 06:13 PM
@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)
Jun 14 2021 08:10 AM
@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!
Jun 14 2021 08:18 AM
Jun 14 2021 08:24 AM
@Eric79x Hi Eric, I would like to update Win10 to the latest version, but unfortunately it's managed by our not very up-to-date IT workplace team. I got my outdated 1909 last Friday
Jun 14 2021 11:04 AM
Jun 14 2021 11:06 AM
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.