Port '8400' is taken with error '[WinError 10013]

[bouncethebox]

Running into this error deploying:

Launching Azure sign-in... Checking for availability of Key Vault... Key Vault is available. Launching Azure AD sign-in...
Launching Azure CLI sign-in... Port '8400' is taken with error '[WinError 10013] An attempt was made to access a socket in a way forbidden by its acces s permissions'. Trying with the next one

Looks like it is calling: http://localhost:8400/?code=AQABAAIAAAAGV_bv21oQQ4ROqh0_1-tAZ5164xK_2W85RKUaKb6HJuaqJgJXUiZ18N85JBxo3675bqMDC7962v5Kwl9FqaHFIXC4qs5sICR0xEEX2nrMMz8JgqkqX7eIaHrM7rL25LCn5nfkNqt_usS1YV759SMq9odatPxm5W6kdUNqx5MfLNwX3IXAdmvKdaqEBMzZm3NNTUomPLmC6Gh-hKYXX8F8BfWWq7jIob-CyGAoqMPLKIws8Gk7CMb4SKYZ38nPNKS9PSOq3fGbD5bETOZL9pZXXUb2qcSDn7vip-U9kaOJNG-HNbC8PfmlAtruoBNaGWfZ96eeoVzfUPdOQXQiWgxbkOwMfHYodOA-R9b5If8zhCWQsyZH3K2TmAqSRvUJ35CLhqhPolZC5ZGC6ulhBYqBNmIP8qxbbSVxACfen01I_eajeKCqdBwbozT3wZwRqtTjmQ0jm3HOx5DCcpnaOr2t1DO3CC2fn4UR4JGyLcracn15h_wDMExQLNVs1nAj8OF82eb7B2CzLdBgOuZWV_WmQiIc7x2LL_xZmZHShicOleNrlleDnLyoEk1PBh9SMUS9oiWWyT-VqhVMcIE5OuHwIAA&state=bgt693xe8bi9dmgftb2a&session_state=a078fa6c-01ea-47ec-9d5c-1be5dd06ae47

Has anyone come across this error? Any information would be appreciated, thanks so much!

[alexc-MSFT]

@bouncethebox did you get past this? I have never seen this before? What version of PowerShell are you using out of interest?

[bouncethebox]

Yeah, still receiving the error. I'm running PS Version 5.1.18362.752

I'm deploying from a jump box over VPN from my local machine, the tenant is locked down. The second error, (Looks like its calling) pops up in a new window, right before the Azure CLI login.

[bouncethebox]

Update to the error:

Launching Azure CLI sign-in...
Port '8400' is taken with error '[WinError 10013] An attempt was made to access a socket in a way forbidden by its acces
s permissions'. Trying with the next one

Exception happened during processing of request from ('127.0.0.1', 63062)
Traceback (most recent call last):
File "socketserver.py", line 320, in _handle_request_noblock
File "socketserver.py", line 351, in process_request
File "socketserver.py", line 364, in finish_request
File "socketserver.py", line 724, in init
File "http\server.py", line 418, in handle
File "http\server.py", line 386, in handle_one_request
File "socket.py", line 586, in readinto
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

---

Exception happened during processing of request from ('127.0.0.1', 63063)
Traceback (most recent call last):
File "socketserver.py", line 320, in _handle_request_noblock
File "socketserver.py", line 351, in process_request
File "socketserver.py", line 364, in finish_request
File "socketserver.py", line 724, in init
File "http\server.py", line 418, in handle
File "http\server.py", line 386, in handle_one_request
File "socket.py", line 586, in readinto
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

[alexc-MSFT]

@bouncethebox see here - Azure/azure-cli#7227

Hopefully this will help you fix the above.

[bouncethebox]

Thanks for the info, I haven't been able to push through this error so I've tried another approach. I'm going to try deploying from Azure Cloud Shell to bypass this 8400 nonsense, lol.

[bouncethebox]

This error was caused by a McAfee Proxy NoAuth/Oauth rule and was resolved by adding the hostname and ip of the jumpbox to a whitelist for deployment purposes.