You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Registered GitHub App successfully, but when I deploy, I get:
docker exec tgsssg08k48o0wcokk0kg4ow 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 https://x-access-token:<REDACTED>@github.com/<myname>/<myrepo>.git main'
2025-Jan-01 11:59:11.531003
fatal: unable to access 'https://github.com/<myname>/<myrepo>.git/': Recv failure: Connection reset by peer
2025-Jan-01 11:59:11.555584
Oops something is not okay, are you okay? 😢
Tried installing Coolify on VPS and my home server, same error on both. Not sure what to do, network connectivity seems ok (since Coolify installed fine, I can see the available images and GitHub App registered without issues)
Steps to Reproduce
Install Coolify
Add a server
Add a resource - GitHub private repo
Deploy
Example Repository URL
No response
Coolify Version
v4.0.0-beta.380
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
melang982
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Jan 1, 2025
Error Message and Logs
Registered GitHub App successfully, but when I deploy, I get:
Tried installing Coolify on VPS and my home server, same error on both. Not sure what to do, network connectivity seems ok (since Coolify installed fine, I can see the available images and GitHub App registered without issues)
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.380
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: