Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Error connecting Visual Studio Code with remote SSH to my GCP VM instance

Hello

I've been trying out the Visual Studio connection from my PC via Remote-SSH for a few days now. I've generated private keys, added to the GCP instance, which work without problems in Putty.
In VS Code it's different. It works at first, it connects, but after a while of browsing or opening a file on the server using VS Code navigation, the server seems to enter a Zombie state, sometimes it recovers by itself but most of the time I have to reset the VM, which prevents me from working with VS. The machine pings at all times, meaning there are no network problems in the meantime.
I'm attaching a photo of the connection in VS to the server and the messages it shows at the beginning of the connection.
The system logs a successful ssh connection, but it doesn't log anything about the error.
The logs that the MV instance registers while it is in zombie mode, trying to reconnect are these on one occasion:

Aug 18 20:17:53 laboratorio chrome-remote-desktop[1496]: [0818/201752.239553 ftl_message_reception_channel.cc(213)] Timed out waiting for PONG message from server.
Aug 18 20:18:12 laboratorio chrome-remote-desktop[1496]: [0818/201753.735329:ERROR:zombie_host_detector.cc(24)] Last signaling activity happened 124.672 s ago, exceeding max duration of 60 s
Aug 18 20:18:23 laboratorio chrome-remote-desktop[1496]: [0818/201754.000040:ERROR:zombie_host_detector.cc(106)] Host zombie state detected.
Aug 18 20:18:29 laboratorio chrome-remote-desktop[1496]: [0818/201755.998499:INFO:remoting_me2me_host.cc(1931)] SendHostOfflineReason: sending ZOMBIE_STATE_DETECTED.
Aug 18 20:18:39 laboratorio chrome-remote-desktop[1496]: [0818/201757.528570:INFO:heartbeat_sender.cc(172)] Sending outgoing heartbeat. host_offline_reason: ZOMBIE_STATE_DETECTED
Aug 18 20:18:47 laboratorio chrome-remote-desktop[1496]: [0818/201842.485267:INFO:remoting_me2me_host.cc(1948)] SendHostOfflineReason failed.
Aug 18 20:19:09 laboratorio chrome-remote-desktop[1496]: [0818/201851.729779:INFO:chromoting_host.cc(121)] Starting host
Aug 18 20:19:21 laboratorio chrome-remote-desktop[1496]: [0818/201853.517617:INFO:chromoting_host.cc(167)] ChromotingHostServices IPC server has been started.
Aug 18 20:19:28 laboratorio chrome-remote-desktop[1496]: [0818/201854.986315:INFO:remoting_me2me_host.cc(1260)] Policy sets host domains:
Aug 18 20:19:38 laboratorio chrome-remote-desktop[1496]: [0818/201855.737249:INFO:remoting_me2me_host.cc(1366)] Policy does not require host username match.
Aug 18 20:19:44 laboratorio chrome-remote-desktop[1496]: [0818/201856.481276:INFO:remoting_me2me_host.cc(1283)] Policy allows remote access connections: 1

another attempt

Aug 18 21:54:14 laboratorio chrome-remote-desktop[1458]: [0818/215413.117631 ftl_message_reception_channel.cc(213)] Timed out waiting for PONG message from server.
Aug 18 21:55:56 laboratorio chrome-remote-desktop[1458]: [0818/215556.032790:ERROR:ftl_signal_strategy.cc(430)] Received server error. Error code: 4, message: Stream connection failed: timeout, location: OnReceiveMessagesStreamClosed@remoting/signaling/ftl_signal_strategy.cc:321
Aug 18 21:55:56 laboratorio chrome-remote-desktop[1458]: [0818/215556.199120:INFO:ftl_signaling_connector.cc(98)] Signaling disconnected. error=NETWORK_ERROR
Aug 18 21:55:57 laboratorio chrome-remote-desktop[1458]: [0818/215557.357306:INFO:ftl_signaling_connector.cc(136)] Attempting to reconnect signaling.
Aug 18 21:55:57 laboratorio chrome-remote-desktop[1458]: [0818/215557.802710 spdy_session.cc(3198)] Received HEADERS for invalid stream 77
Aug 18 21:55:59 laboratorio chrome-remote-desktop[1458]: [0818/215559.223997:INFO:ftl_signaling_connector.cc(93)] Signaling connected. New JID: 87fe81695c894c60b7d81cdcff4d1ffe@chromoting.gserviceaccount.com/chromoting_ftl_7bc2a6c2-86c7-411a-9b4b-411acf3f146b
Aug 18 21:55:59 laboratorio chrome-remote-desktop[1458]: [0818/215559.225205:INFO:heartbeat_sender.cc(172)] Sending outgoing heartbeat.
Aug 18 21:56:31 laboratorio chrome-remote-desktop[1458]: [0818/215627.584654 ftl_message_reception_channel.cc(213)] Timed out waiting for PONG message from server.

I thank you in advance for your help, since I am worried, VS is the most comfortable way I know to work on remote servers, the idea of ​​filling out the scripts by console seems annoying to me. Anyway, if someone works in a comfortable way that I am not familiar with, let me know.

Sin título.png

 

1 2 619
2 REPLIES 2

I'm adding some information that I forgot to mention. At first I thought it was a lack of memory on the disk (which it was), but I added 10GB and it didn't work. It's been tested with 2 PCs; Windows 11 and Windows 10, with the same result.

Hi s_tobar_manzor,

Did you solve your problem? I see the same problem now. Can you help me?