microsoft / microsoft/vscode-remote-release
If open Pulse Secure VPN first, then open vscode, then switch to Remote Explorer. The list is empty.
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing open issues and found none that apply.
- If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- I have read and performed the troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting - My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I asked @remote-ssh but it did not help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I COULD successfully SSH to the remote machine with the generated SSH command
Remote-SSH Log
Remote-SSH Log
[18:15:12.108] Log Level: 2
[18:15:12.278] VS Code version: 1.96.3
[18:15:12.278] Remote-SSH version: remote-ssh@0.116.1
[18:15:12.278] darwin arm64
Expected Behavior
After closing the Pulse VPN
Actual Behavior
After opening the Pulse VPN
Steps To Reproduce
- If open Pulse Secure VPN first, then open vscode, then switch to Remote Explorer. The list is empty.
- If open VScode first, then open Pulse Secure VPN, all is normal.
Anything else?
Pulse Secure VPN version:
Note:
After starting a VPN connection, the DNS Servers and Search Domains of current network will be changed. It could be a reason.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the sequence in the issue on macOS: launch Pulse Secure VPN before VS Code, then open Remote Explorer, and compare it with the reverse order. Read the Remote-SSH troubleshooting wiki and inspect the complete output from “Remote-SSH: Show Log”; done means Remote Explorer lists the expected connections in both launch orders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100