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

%3CLINGO-SUB%20id%3D%22lingo-sub-868342%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%3A%20Can't%20open%20unsafe%20ports%20on%20Edge%20insider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-868342%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BThis%20command%20line%20works%20properly%20for%20me%20in%20Edge%20Canary%2079.0.278.%20Please%20confirm%20that%20you've%20closed%20all%20msedge.exe%20instances%20(using%20task%20manager%20to%20ensure%20there%20aren't%20any%20hidden%20processes%20lingering)%20before%20starting%20a%20new%20one%20using%20this%20command%20line%20argument.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-869126%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%3A%20Can't%20open%20unsafe%20ports%20on%20Edge%20insider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-869126%22%20slang%3D%22en-US%22%3EYes%2C%20I%20think%20the%20problem%20was%20solved%20in%20Edge%20insider%2079.%20now%20I'm%20testing%20it%20on%20version%3CBR%20%2F%3EVersion%2079.0.280.0%20(Official%20build)%20canary%20(64-bit)%3CBR%20%2F%3Eand%20it's%20working%20fine.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-860884%22%20slang%3D%22en-US%22%3E%5BFIXED%5D%20Problem%3A%20Can't%20open%20unsafe%20ports%20on%20Edge%20insider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-860884%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EUPDATE%3A%20Fixed%20in%20Edge%20insider%26nbsp%3BVersion%2079.0.280.0%20(Official%20build)%20canary%20(64-bit)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20to%20open%20a%20custom%20port%20for%20WAC.%20I%20can%20do%20that%20with%20Google%20Chrome%20Canary%2079%20by%20adding%20this%20to%20the%20shortcut%20target%3A%20%22--explicitly-allowed-ports%3D6666%22%20and%20it%20loads%20the%20WAC%20console%20just%20fine.%3C%2FP%3E%3CP%3Ebut%20when%20I%20do%20the%20same%20for%20Edge%20insider%20Canary%2C%20it%20won't%20work%20and%20still%20gives%20me%20the%20unsafe%20port%20error.%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20Insider%20Version%2078.0.277.0%20(Official%20build)%20canary%20(64-bit)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWindows%2010%20latest%20ver%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWAC%201909%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20987px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F132323iAA618E939441291E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Annotation%202019-09-18%20160508.png%22%20title%3D%22Annotation%202019-09-18%20160508.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-860884%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eproblem%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205589%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%3A%20Can't%20open%20unsafe%20ports%20on%20Edge%20insider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205589%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317619%22%20target%3D%22_blank%22%3E%40ericlaw%3C%2FA%3E%26nbsp%3Byesterday%20I%20made%20a%20batch%20file%3A%3C%2FP%3E%3CP%3E%22C%3A%5CProgram%20Files%20(x86)%5CMicrosoft%5CEdge%5CApplication%5Cmsedge.exe%22%20-explicitly-allowed-ports%3D6666%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2F%3CREDACTED%3E%3A6666%2F%3C%2FREDACTED%3E%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20worked%20yesterday%2C%20today%20it%20gives%20unsafe%20port%20error.%3C%2FP%3E%3CP%3EThoughts%3F%3C%2FP%3E%3CP%3E%3CSPAN%3EVersion%2080.0.361.62%20(Official%20build)%20(64-bit)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Honored Contributor

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

 

Annotation 2019-09-18 160508.png

 

3 Replies
Highlighted

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

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

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