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

[HotCakeX]

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

[#2]

@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.

[#3]

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.

[#4]

@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)

[#5]

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

[#6]

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.

[#7]

@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 

[#8]

For clarity, the command line above doesn't work because you need to pass --explicitly-allowed-ports with two leading dashes.

[#9]

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.

[#10]

@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.

[#11]

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

[#12]

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!

[#13]

@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... 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.

[#14]

Indeed!

And you had already mentioned it, in your initial comment within parenthesis.
Somehow I missed that, and initially I tested it just by removing feature "Continue running background extensions and apps when Microsoft Edge is closed" which didn't help.
And then just removed everything 🙂

All good.