Databases
StackOverflow2013
Postsdbo
POProblems setting up git with github
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProblems setting up git with github
    primarykey
    data
    text
    <p>I've googled the heck out of this one, and it is still failing me. </p> <blockquote> <p>ssh: Could not resolve hostname github: Name or service not known fatal: The remote end hung up unexpectedly</p> </blockquote> <p>Most of the problems with this seem to do with having the wrong keys being sent to the server, which isn't the problem. I can SSH into github as stated in github's help pages. I did have this working fine before, but I had wiped out the repository, wiped out my keys, and started fresh. Here is the output of <code>ssh -v git@github.com</code>:</p> <blockquote> <p>OpenSSH_5.5p1 Debian-4ubuntu5, OpenSSL 0.9.8o 01 Jun 2010<br> debug1: Reading configuration data /etc/ssh/ssh_config<br> debug1: Applying options for *<br> debug1: Connecting to github.com [207.97.227.239] port 22.<br> debug1: Connection established.<br> debug1: identity file /home/patrick/.ssh/id_rsa type 1<br> debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048<br> debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048<br> debug1: identity file /home/patrick/.ssh/id_rsa-cert type -1<br> debug1: identity file /home/patrick/.ssh/id_dsa type -1<br> debug1: identity file /home/patrick/.ssh/id_dsa-cert type -1<br> debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5github2<br> debug1: match: OpenSSH_5.1p1 Debian-5github2 pat OpenSSH*<br> debug1: Enabling compatibility mode for protocol 2.0<br> debug1: Local version string SSH-2.0-OpenSSH_5.5p1 Debian-4ubuntu5<br> debug1: SSH2_MSG_KEXINIT sent<br> debug1: SSH2_MSG_KEXINIT received<br> debug1: kex: server->client aes128-ctr hmac-md5 none<br> debug1: kex: client->server aes128-ctr hmac-md5 none<br> debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024&lt;1024&lt;8192) sent<br> debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP<br> debug1: SSH2_MSG_KEX_DH_GEX_INIT sent<br> debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY<br> debug1: Host 'github.com' is known and matches the RSA host key.<br> debug1: Found key in /home/patrick/.ssh/known_hosts:1<br> debug1: ssh_rsa_verify: signature correct<br> debug1: SSH2_MSG_NEWKEYS sent<br> debug1: expecting SSH2_MSG_NEWKEYS<br> debug1: SSH2_MSG_NEWKEYS received<br> debug1: Roaming not allowed by server<br> debug1: SSH2_MSG_SERVICE_REQUEST sent<br> debug1: SSH2_MSG_SERVICE_ACCEPT received<br> debug1: Authentications that can continue: publickey<br> debug1: Next authentication method: publickey<br> debug1: Offering public key: /home/patrick/.ssh/id_rsa<br> debug1: Remote: Forced command: gerve blueshift9<br> debug1: Remote: Port forwarding disabled.<br> debug1: Remote: X11 forwarding disabled.<br> debug1: Remote: Agent forwarding disabled.<br> debug1: Remote: Pty allocation disabled.<br> debug1: Server accepts key: pkalg ssh-rsa blen 279<br> debug1: Remote: Forced command: gerve blueshift9<br> debug1: Remote: Port forwarding disabled.<br> debug1: Remote: X11 forwarding disabled.<br> debug1: Remote: Agent forwarding disabled.<br> debug1: Remote: Pty allocation disabled.<br> debug1: Authentication succeeded (publickey).<br> debug1: channel 0: new [client-session]<br> debug1: Requesting no-more-sessions@openssh.com<br> debug1: Entering interactive session.<br> debug1: Sending environment.<br> debug1: Sending env LANG = en_US.utf8<br> PTY allocation request failed on channel 0<br> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0<br> debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0<br> Hi! You've successfully authenticated, but GitHub does not provide shell access.<br> debug1: channel 0: free: client-session, nchannels 1<br> Connection to github.com closed.<br> Transferred: sent 2648, received 2904 bytes, in 0.1 seconds<br> Bytes per second: sent 37663.4, received 41304.6<br> debug1: Exit status 1 </p> </blockquote> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USpatricksweeney
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COSee: http://stackoverflow.com/questions/3844393/what-to-do-about-pty-allocation-request-failed-on-channel-0
      singulars
      1. POProblems setting up git with github
      1. USghoppe
    2. COThanks ghoppe; I had actually tried that at some point, didn't work, tried again, worked! Thanks! If you add it as an answer, I can checkmark your answer.
      singulars
      1. POProblems setting up git with github
      1. USpatricksweeney
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload