-
Notifications
You must be signed in to change notification settings - Fork 1.3k
VS Code Not Opening #7458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jeanp413 could you try to reproduce it? It seems to be related to VS Code Desktop. |
FYI: I just tried it on my personal laptop instead of my work laptop, and my personal GitPod account instead of my work GitPod account. That one worked. So that does support that there's something unique about my work laptop that isn't working with it anymore. |
Cannot reproduce on Linux. |
The personal laptop is also Windows, but Home instead of Professional and not managed by my organization. There's other variation in what apps are installed, but those are probably the two starting point differences. Here's the output:
And then a new one about the api endpoint not being ready every 1s until I cancel it. |
Quick update: I've spent more time trying to narrow down which variable is making the difference. It seems the most likely culprit is the VPN/work network (I'm currently at home but this problem started when I was in person). In a relatively small sample size, it works if I have not yet connected to the VPN since restarting the computer. It does not work if I am currently connected to the VPN, or sometimes not if I was connected to the VPN but since disconnected. Are you aware of any network requirements that I could take to our IT team? Or are you aware of anything that changed a couple months ago on the GitPod end that our network doesn't like? |
cc @akosyakov ☝️ |
VS Code Desktop right now relies on https://www.gitpod.io/blog/local-app. Could you try to install it and see whether you can SSH into workspace? Please also investigate log output of the local app bundled with VS Code Destkop, you can see a path to it in the output view, e.g. "log": "file:///c%3A/Users/RYROBI~1/AppData/Local/Temp/gitpod-local-companion-22904-33QFks7obsgc-.log" VS Code Desktop is still in beta, we are going to rework it next month to use direct SSH access. Maybe it will resolve your issue. |
I've installed the local app. I then tried to SSH to a workspace (while on the VPN). This is one of the workspaces which is in the gitpod_ssh_config file, successfully added yesterday. My command was:
The response after about a minute is:
I also tried the same thing with another workspace that is not yet in the gitpod_ssh_config. Same result. The gitpod-local-companion log file gives me a series of "failed to connect":
(There's more but with different ports and going up to 30 seconds between tries) |
@ryan-l-robinson Could you try from the scratch and share entire log of the local app with us by sending to [email protected]? Please mention that it is for Anton and Jean Pierre. You can also run the local app in debug mode with
It happens when the local app cannot access Gitpod Server for some reason. It could be temporary, but it never stops and you don't see that it is connected when it is bad. You can try to use other tools then to connect to the same host or ip address to see whether you have general issues with network. |
Done. Log is sent. |
From logs indeed it looks like the local companion cannot reach gitpod.io host. Can you ping it? |
Yes, I can ping gitpod.io even when I'm on the VPN.
I can also browse gitpod.io with no issues. |
I feel this is more like a clientside issue which is hard to reproduce and also debug 😬, more like this one at discord: https://discord.com/channels/816244985187008514/839379835662368768/932334019583017040 |
Understood. Our network is blocking something that this particular function needs. If you have any suggestions for what I could ask our IT department (e.g. a port to unblock), that would be great. If not, go ahead and close this ticket and we'll accept that if we stick with GitPod we'll have to do it in a browser. |
@ryan-l-robinson we will try to help until we run out of ideas, closing this issue is the last resort 😅 . Can you try connecting to some other server via SSH on your terminal? Does that work? |
Yes, I can SSH to other servers, including some within our network (staging servers) and some unrelated (my personal website). |
Okay thanks for testing that. Another thing that you can try is ssh'ing into the Gitpod generated config file with |
To generate the ssh config file, I have to go off the VPN. If I try to launch VS Code from GitPod while on the VPN, it will create the file but with nothing in it. So I went off the VPN, launched VS Code from GitPod, which generated the file. I then tried to SSH to the host name that was showing in that file, with verbose logging, and got this response:
A couple of those files that it says fail to open do not exist: the ones ending with -cert. |
Now those logs might be helpful for @akosyakov to debug. Let's wait for him 🙂 |
I'm not sure if this is helpful but sometimes antiviruses on windows can automatically delete files. I have not used windows for a long time now, so not sure how it's like today. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It happened to me too on mac 2013. After some tries, I opened the log and tried again: 1. open the workspace on the browser , from there click on on open with vscode and then look on the log file (which was a good decision to make). Then the log says trying to fetch url... |
Can reproduce on MBA 2019. |
Can reproduce on Windows 10 |
@soshimee @RafidMuhymin could you install the pre-release version of |
@jeanp413 yup! It's working now 🚀! I had to configure nothing! Thank you so much! |
Feel free to reopen it if the new feature #7458 (comment) not works for you |
For stable version you can configure |
Bug description
When I try to launch desktop VS Code for a workspace, it does not load. I get the prompt in Edge to approve opening VS Code. VS Code launches with whatever the last (local) workspace I had open. There is a notification saying that it is trying to open the workspace, but it will spin on "Connecting to GitPod workspace" for hours until I either cancel or close VS Code.
This used to work until about a month ago.
Knowing how central this is to the GitPod experience, I assume there's something unique to my setup and this isn't widespread for everybody. But I don't have any ideas for what might be causing a conflict.
Steps to reproduce
Start the GitPod workspace in the browser
Click the Open button to launch in VS Code when prompted, or choose the option to open in VS Code from the command palette.
When prompted by browser (Edge), allow this site to open VS Code links.
Look at the VS Code notification to open the GitPod workspace.
Environment:
Browser: Edge (although I don't think it's a browser issue since it can launch Code)
Desktop OS: Windows 10 Professional
VS Code version: 1.63.2 (system setup)
VS Code extensions installed locally:
Workspace affected
No response
Expected behavior
Launches GitPod workspace in VS Code (after a minute or two).
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: