Skip to content
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

[Bug]: SSH often disconnects #4769

Open
stag-enterprises opened this issue Jan 8, 2025 · 2 comments
Open

[Bug]: SSH often disconnects #4769

stag-enterprises opened this issue Jan 8, 2025 · 2 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@stag-enterprises
Copy link

stag-enterprises commented Jan 8, 2025

I made this issue a while ago, and while a fix was supposedly released, either my issue is not the same or the fix does not work for me. I am on the latest release (380).

The issue is that Coolify will often connect to the SSH of the host machine, and then immediately disconnect. Attached are my SSH access logs. You can see Coolify disconnects after ~35 seconds (not the host kicking it, Coolify is closing the connection), and then will reconnect after about ~25 seconds.

This causes many problems in the dashboard, since the server is unreachable. For example, localhost server will appear as unvalidated most of the time, I am unable to access reverse proxy logs, most resources won't deploy most of the time, etc... On the dashboard side, it sometimes also throws an SSH error 22 to host.docker.internal with connection refused.

Image

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12

@stag-enterprises stag-enterprises added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 8, 2025
@stag-enterprises stag-enterprises changed the title [Bug]: [Bug]: SSH often disconnects Jan 8, 2025
@stag-enterprises
Copy link
Author

bump

@petalas
Copy link

petalas commented Jan 21, 2025

I hit the same after installing latest coolify on brand new Debian VM with zero changes to /etc/ssh/sshd_config

In my case, as soon as the coolify containers come up, I can no longer ssh into the VM.

❯ ssh -v [email protected]
OpenSSH_9.8p1, LibreSSL 3.3.6
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/100-macos.conf
debug1: /etc/ssh/ssh_config.d/100-macos.conf line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/crypto.conf
debug2: resolve_canonicalize: hostname 192.168.1.103 is address
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 192.168.1.103 [192.168.1.103] port 22.
debug1: connect to address 192.168.1.103 port 22: Connection refused
ssh: connect to host 192.168.1.103 port 22: Connection refused

If I look at sudo journalctl -u ssh the only activity I see is from the coolify container on the docker network (10.0.1.6) repeatedly connecting and disconnecting (?)

Image

External attempts to ssh in don't seem to even hit it the VM at all, feels like coolify takes over the port or something, not sure.

Additional info:

  • If I restart the VM and I can ssh into it in the first few seconds before the coolify containers come up.
  • If I uninstall coolify, the problem goes away and I can ssh into the VM just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants