Unable to connect to the existing tunnel and even refresh the tunnels list

[JavaStudentAlex]

There was already an issue #10554 with the other error code but the solutions was not found for me.
There is an issue connecting to the vscode tunnel services in the network with set up with the proxy and firewall. I have tried same actions with the same server with the microsoft and github accounts but it did not work out on the target machine. I have tried this functions on the other laptop with other network configurations and it worked perfectly, so probably the issue is exactly in the proxy or firewall I use. I just need your help to understand what exactly I need to enable to not to block the requests from the vscode.

• VSCode Version: 1.96.4
• Local OS Version: Windows: 10 Enterprise 22H2
• Remote OS Version: Amazon: 5.10.230-223.885.amzn2.x86_64 GNU/Linux
• Remote Extension/Connection Type: Dev Containers/WSL/Remote - Tunnels/VS Code Server: Remote Tunnels extension 1.5.2, remote vscode cli version is 1.96.4
• To prevent delays, please STOP and use the 'Remote - SSH Bug' issue template instead -->
• Logs:

2025-01-29 13:17:12.892 [error] AxiosError: Request failed with status code 400
	at je (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:951027)
	at IncomingMessage.<anonymous> (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:963117)
	at IncomingMessage.emit (node:events:530:35)
	at endReadableNT (node:internal/streams/readable:1698:12)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
	at At.request (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:971833)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async E.axiosRequest (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:75388)
	at async E.request (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:76034)
	at async E.sendRequest (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:69974)
	at async E.listTunnels (c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:64683)
	at async c:\Users\alex\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:1201977
	at async cw.h (file:///c:/Users/alex/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:115:32825)
	at async Promise.all (index 0)
	at async t.RemoteTreeDataProvider.refreshTunnels (c:\Users\alex\.vscode\extensions\ms-vscode.remote-explorer-0.4.3\dist\node\extension.js:1:7783)
	at async Promise.all (index 0) remote-explorer.refresh {"value":"ms-vscode.remote-explorer","_lower":"ms-vscode.remote-explorer"}

Steps to Reproduce:

1. On the server: run the code cli on the server with ./code tunnel with auth into microsoft account
2. On the client: open the VSCode, open remote extension, login into account.
3. From that time I got 2 different error message which probably caused by one source
   The first error message is about unable to refresh tunels list and actually the stacktrace is given for this error message:

Error running command remote-explorer.refresh: The tunnel request resulted in 400 status, but the request did not reach the tunnel service. This may indicate the domain 'global.rel.tunnels.api.visualstudio.com' is blocked by a firewall.. This is likely caused by the extension that contributes remote-explorer.refresh.

Another issue message also got together with the first one during the connection to the existing tunnel:

AxiosError: The tunnel request resulted in 400 status, but the request did not reach the tunnel service. This may indicate the domain 'global.rel.tunnels.api.visualstudio.com' is blocked by a firewall.. You may need to sign out and back in.

I did not find any stacktrace for it, but it looks like it has the same reason as the previous one.