Update Documentation for SSH Connection Issues During Installation #2639
Replies: 9 comments 4 replies
-
|
Just ran into this problem myself and was able to resolve it with the solution provided. |
Beta Was this translation helpful? Give feedback.
-
|
I had this problem now, and unfortunately the AllowGroups admin line did not exist. I solved the problem by installing Coolify one on top of the other (I ran the 'curl' command without uninstalling the existing installation) |
Beta Was this translation helpful? Give feedback.
-
|
Running in to this problem but unfortunately this does not fix the issue. Still searching for a solution |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Had a simular issue. Neither solution above worked. My solution was there are 2 different Adding a new line between the two ssh keys fixed the issue. |
Beta Was this translation helpful? Give feedback.
-
|
HI! Still having the same issue trying to validate the server: "Please validate your configuration and connection. I ran the coolify installation twice (Not manually) and the server still is not being validated. I can connect to my VPs via ssh successfully, and I can login to the coolify admin panel. Any possible solution? I tried all from this thread but nothing is working. |
Beta Was this translation helpful? Give feedback.
-
|
i had a similar issue all i had to do was uninstall and reinstall again |
Beta Was this translation helpful? Give feedback.
-
|
I also ran into this while self-hosting Coolify (on Unraid in my case), and for me the root cause wasn’t sshd_config but Coolify’s own private key / server registration state. A few things that finally solved it: Ensure the Coolify key actually exists in the DB
If you see Error loading private key or no rows at all, regenerate a key pair in the UI and make sure the public key gets added (on its own line) to ~/.ssh/authorized_keys on the target host. Sentinel must be running with a valid token Then update the server row inside Coolify with that token if the UI doesn’t expose a field yet. Set a proper FQDN in Instance Settings — Coolify won’t let you enable Sentinel with just an IP. After those three steps the “No query results for model [App\Models\PrivateKey] 0” error went away, and Sentinel synced properly. From there I could validate the server and deploy apps without further SSH issues. |
Beta Was this translation helpful? Give feedback.
-
|
Lol that's amazing. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hi Coolify Team,
I recently encountered an issue during the installation of Coolify where it was unable to connect to localhost due to SSH connection problems. The specific error message displayed was:
root@host.docker.internal: Permission denied (publickey,password).After spending several hours troubleshooting, I discovered that the problem was not with Coolify itself, but with the default SSH configuration on Ubuntu Server.
By default, the sshd_config file contains the following rule:
AllowGroups adminThis rule prevents the root user from connecting unless explicitly added to the AllowGroups.
To resolve this issue, I added the root group to the AllowGroups in the sshd_config file as follows:
AllowGroups admin rootI believe it would be beneficial for other users if this information were included in the Coolify installation documentation. This addition could save significant troubleshooting time and help ensure a smoother installation process.
Thank you for considering this request!
Beta Was this translation helpful? Give feedback.
All reactions