I had an issue similar to frank_hoffsummer's problem. and the ssh command still returns "Authentication succeeded" and error code 0. Then I changed the BitBucket section in my ~/.ssh/config to use a key that exists on my file system, but is not configured here Host The ssh command returns "Authentication succeeded" and error code 0. ![]() One with the actual key that I have configured in Host I tried two different ~/.ssh/config configurations to verify this. orgĭebug1: Authentication succeeded (publickey) fatal: the remote end hung up unexpectedly”įYI the ssh -T command mentioned here is misleading!Īs long as you have an ssh key configured on your Bitbucket account, the following command will report success, no matter the key that you're using to connect to BitBucket $ ssh -Tv bitbucket. However, attempts to push my code updates, even when my VPN is disconnected, produce the error message, “Connection to closed by remote host. Thus, I can conclude my SSH keys are now working properly. When I was not connected to my VPN, the command produced the expected output indicating I was logged in by my username. Ssh -T the error “Connection closed by port 22” whenever I was connected to my VPN (specifically, NordVPN). However, in troubleshooting, I did discover that the command Update: I did as Scott Dudley _Cenote_ suggested (below) and installed new SSH keys. It’s been several days now, and I still can’t write to my repository.Īs robertolo surmised, this is probably a server side error. A couple days after that, it stopped working again (no notice this time). The next day, my repository was working fine again. I got a notice from Atlassian that bitbucket was having problems. A little more than a week ago, it stopped working. I was working along just fine with my repository. I’m having the same problem right now, also for days. I do not know how to continue from this point. Transferred: sent 3468, received 1640 bytes, in 20.1 secondsīytes per second: sent 172.4, received 81.5 I have tried the following also: $ ssh -v Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n ĭebug1: Reading configuration data /home/roberto/.ssh/configĭebug1: /home/roberto/.ssh/config line 1: Applying options for ĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: /etc/ssh/ssh_config line 19: Applying options for *ĭebug1: Connecting to port 22.ĭebug1: identity file /home/roberto/.ssh/id_bitbucket type 0ĭebug1: key_load_public: No such file or directoryĭebug1: identity file /home/roberto/.ssh/id_bitbucket-cert type -1ĭebug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.1ĭebug1: Remote protocol version 2.0, remote software version conker_1.1.17-9953920 app-130ĭebug1: no match: conker_1.1.17-9953920 app-130ĭebug1: Authenticating to :22 as 'git'ĭebug1: kex: algorithm: kex: host key algorithm: ssh-rsaĭebug1: kex: server->client cipher: MAC: compression: noneĭebug1: kex: client->server cipher: MAC: compression: noneĭebug1: expecting SSH2_MSG_KEX_ECDH_REPLYĭebug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1Aĭebug1: Host '' is known and matches the RSA host key.ĭebug1: Found key in /home/roberto/.ssh/known_hosts:31ĭebug1: Authentications that can continue: publickeyĭebug1: Next authentication method: publickeyĭebug1: Offering public key: RSA SHA256:KwjrafCTA0P4mDiNqNztGEmmYkpdcGN633rHnL81AEM /home/roberto/.ssh/id_bitbucketĭebug1: Server accepts key: pkalg ssh-rsa blen 279ĭebug1: Authentication succeeded (publickey).Īuthenticated to (:22).ĭebug1: Sending env LC_MEASUREMENT = es_ES.UTF-8ĭebug1: Sending env LC_PAPER = es_ES.UTF-8ĭebug1: Sending env LC_MONETARY = es_ES.UTF-8ĭebug1: Sending env LC_NAME = es_ES.UTF-8ĭebug1: Sending env LC_ADDRESS = es_ES.UTF-8ĭebug1: Sending env LC_NUMERIC = es_ES.UTF-8ĭebug1: Sending env LC_TELEPHONE = es_ES.UTF-8ĭebug1: Sending env LC_IDENTIFICATION = es_ES.UTF-8ĭebug1: Sending env LC_TIME = es_ES.UTF-8ĭebug1: channel 0: free: client-session, nchannels 1 ![]() Please make sure you have the correct access rights Neither an internet connection problem on my side, as I can reproduce through two different networks (home connection and cell phone tethering).Įnter passphrase for key '/home/roberto/.ssh/id_bitbucket':Ĭonnection to closed by remote host.įatal: Could not read from remote repository. It does not seem a client issue as I can reproduce the same problem in my two machines. I am going today through connectivity problems to my bitbucket repositories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |