After i restart an airbyte vm on gcp, i get the following errors when trying to login via an ssh tunnel. Before restart, it works fine. Any ideas?

channel 4: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused

This usually happens if you try to communicate with a port on the remote that either isn't mapped or isn't connected to anything.

Let me know if Callum's comment helps you figure this out, Eli.

@Nataly Merezhuk (Airbyte) - containers look to be running on the right ports, and my tunnel command looks to be working - if this is the case, the airbyte server isn't listening or is blocked from listening on port 8000 (not sure how to troubleshoot that, there is no firewall installed). This is a out of the box debian 11 vm in gcp. The tunnel worked no problem after the initial install, it was only after I restarted the vm that this problem started.

@Eli Rosenberg could you please tell me what Airbyte version you're using?

It's working - I was just restarting the web server container, but if I restart all containers after I restart the vm, it works

Great!