WARP client blocks SSH connection without warning

What is the name of the domain?

/

What is the error number?

/

What is the error message?

/

What is the issue you’re encountering

Accidentally installed WARP client on a server accessed via SSH, causing SSH to immediately disconnect and become completely inaccessible.

What steps have you taken to resolve the issue?

  1. SSH to the server = No response.
  2. Try to recover the SSH access from my Google Cloud Platform Console. (very, very complicated).

What are the steps to reproduce the issue?

  1. SSH to the server (on port 2222).
  2. warp-cli registration new.
  3. warp-cli connect.
  4. SSH will disconnect without any warning.
  5. Can not connect to SSH anymore.

THERE SHOULD BE A WARNING!

++ There should have been a notification :frowning:

Isn’t SSH port anymore open at your machine to connect to directly? :thinking:

Did you tried rebooting your machine?

Is it installed and running as a service already?

Isn’t SSH port anymore open at your machine to connect to directly?

Before starting warp, it was accessible.
After starting wrap, ssh was immediately disconnected and could no longer be accessed through the same port.

Did you tried rebooting your machine?

Tried to restart the machine on the platform, which took a very long time (probably because the platform’s control request to the machine was also blocked), and then it should have been forced to restart.
After restart, ssh is still not accessible. Then I have to connect to the serial port and disable WRAP.

Is it installed and running as a service already?

Yes.