[Bug]: ssh: connect to host 10.0.0.4 port 22: Operation timed out

[leonbeckert]

Error Message and Logs

sudo docker exec fgowso8wg84w8s4csgocwc8k bash -c 'GIT_SSH_COMMAND="ssh -o ConnectTimeout=30 -p 22 -o Port=22 -o LogLevel=ERROR -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" git ls-remote [email protected]:test/test.git main'
2024-Dec-21 21:41:08.921042
ssh: connect to host 10.0.0.4 port 22: Operation timed out
2024-Dec-21 21:41:08.925441
fatal: Could not read from remote repository.
2024-Dec-21 21:41:08.925441
2024-Dec-21 21:41:08.925441
Please make sure you have the correct access rights
2024-Dec-21 21:41:08.925441
and the repository exists.
2024-Dec-21 21:41:08.960131
Oops something is not okay, are you okay? 😢
2024-Dec-21 21:41:08.962644
ssh: connect to host 10.0.0.4 port 22: Operation timed out
2024-Dec-21 21:41:08.962644
fatal: Could not read from remote repository.
2024-Dec-21 21:41:08.962644
2024-Dec-21 21:41:08.962644
Please make sure you have the correct access rights
2024-Dec-21 21:41:08.962644
and the repository exists.
2024-Dec-21 21:41:08.964505
Deployment failed. Removing the new version of your application.

Steps to Reproduce

1. Set up a new Git repository on a GitLab instance (self-hosted, IP: 10.0.0.4).
2. Add a deploy key or deploy token for the repository.
3. Configure a Coolify app to use this repository.
4. Attempt to deploy the app via Coolify.
   Expected result: The repository is cloned, and the deployment succeeds.
   Actual result: The deployment fails with a timeout on port 22

Example Repository URL

No response

Coolify Version

v4.0.0-beta.379

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

I am encountering an issue with Coolify when trying to deploy applications connected to newly created Git repositories. Existing repositories on the same GitLab instance work without issues, but for any new repositories, Coolify consistently fails with the error mentioned above.

The issue persists even though:

1. The same deploy keys and tokens work manually when cloning the repository using git clone in the Coolify container and on the Coolify host machine.
2. I can SSH into the server (10.0.0.4) from both the Coolify host machine and the Coolify container without issues.
3. UFW is correctly configured to allow port 22 (it works for my other projects that deploy from the same GitLab instance).
4. Other previously configured repositories on the same GitLab server work without issue.

This appears to be a specific issue with newly created repositories and not a general configuration problem. The coolify docker logs do not show any additional information.

I also tried replacing git@ with an http URL, including deployment tokens, which did not solve the issue.

Any help would be greatly appreciated.