-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Error -16 (SSH response issue) with Godot 4.2.1 Stable #215
Comments
Which Git host are you trying to push to? Does your SSH key use ECDSA (elliptic curve) cryptography? See #193. |
This is going to Github.com It's been a while since I had created the key so I'm unsure, but it's possible that I created it with ECDSA. I know on MacOS it was giving me some issues because it was an OPENSSH generated key instead of RSA and I had to do some conversions to have the Mac even load the key. I've tried both versions of that with the plugin and both failed. I've switched to having a 2nd remote as an HTTP origin and PAT for now. If there is any kind of debugging I can run have it the plugin show more information, I'm happy to try that out. |
I am encountering the same issue, trying to push to Github with an RSA key. |
Same, using SSH doesn't seems to work. Tried with Ed25519 and RSA keys.
Luckily that works out for me too, thankyou, I just wish that I could have the option to save the PAT so I don't have to put it again every time I want to push something. |
same issue for me with SSH |
Just wanted to chime in that I experienced the same thing. SSH wasn't connecting with error -16, but an HTTPS url for the remote and a PAT for the password works. I'm new-ish to software and mostly self-taught, so this tripped me up for a bit since I was just following the plugin documentation, which makes no mention of this issue. |
I've modified the wiki setup page to warn about known issues in SSH authentication. |
I've had the same issue with the RSA key, after hours of searching for a fix I found out that the SSH key in PEM format works fine. |
Thank you so much @Buczkek |
I still get the error even if my RSA key is in PEM format |
thanks, finally i found a solution for this issue ... |
ok let me sort this out ... this could be added to the docs but for now we have it working the set up and exact process omits a lot of steps that break the process ... this is my first time setting up github repo and hear is how i got it working 1 - you need to get the software called "git" you can follow any guide on that you are all connected up to push ... to do so in godot on the commit tap you will find your latest changes .. move them to the staging tap ... type any comment and hit commit changes .... nothing will happen on github yet you need to create a branch from the 3 dots on the bottom left and then finally you can push to github using the push arrow right next to the 3 dots on the bottom left Good luck |
I believe this is working if your remote is setup as HTTPS and not GIT. I've had no issues using a remote with HTTPS and user/pass. It specifically is using a GIT over SSH upstream and only using keyexchange
I believe yours is working with all that setup if your git remote is setup as HTTPS and not SSH. I've had no issues using a remote with HTTPS and user/pat. It specifically is using a GIT over SSH upstream and only using key-exchange.
As long as I push to origin-http and I have user/pat setup, no issues. But if I try to push to origin with just keyexchange and ssh keys, the error happens. |
While being able to stage/unstage and commit files without issue, pushing to and pulling from Git over SSH appears to not work for me. If I open the repository in VSCode (or from cmd line) I am able to push and pull without issue.
I setup my respos to use SSH transport and in the VCS I have added my keys. Refreshing, pulling or pushing commits causes the Godot editor to freeze for ~2 minutes (assuming this is the SSH timeout). Screenshot of the error below.
Not sure if I'm doing something wrong or if there was something I missed.
The text was updated successfully, but these errors were encountered: