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 verWAC 1909

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.

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 --> TargetAnd 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!

wasilis92 The only thing you really should need to disable is Startup Boost -- that's the one that keeps a background Edge process around. Efficiency Mode and Sleeping tabs do NOT keep extra processes.See https://textslashplain.com/2022/01/05/edge-command-line-arguments/#:~:text=An%20argument%20I%20tried%20didn%E2%80%99t%20seem%20to%20do%20anything%3F%20Why%20not%3F for discussion. As for why Edge uses many processes-- Chromium-based browsers use many processes for security and reliability reasons. Each process can have its own sandbox, with restrictions locked down as tight as possible for that process' job. Similarly, if a utility process crashes, the browser does not crash and the utility can be restarted.

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.

[FIXED] Problem: Can't open unsafe ports on Edge insider

Eric_Lawrence
Microsoft
Sep 20, 2019
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.
- HotCakeX
  MVP
  Sep 22, 2019
  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.
- eric79xxl
  Copper Contributor
  Mar 03, 2020
  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)
  - dirum
    Copper Contributor
    Jun 14, 2021
    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!

Forum Discussion

[FIXED] Problem: Can't open unsafe ports on Edge insider

Share

Resources