Getting started, however I cannot push code to resin.io - 'git push resin master' fails


#1

Hi, I’m new and I’m going thru the getting started guide, and an stuck trying to get to get the example working, I’m using the ‘getting started’ guide for Node.js on Raspberry Pi 3

I’ve added the SSH key and I can see my Rasberry Pi 3 show up in the Resin control panel, but I’m unable to push the code to the device.

After going into the folder containing the ‘simple-server-node’ and setting up the remote, I do the ‘git push resin master’ command and get the following error:

$ git push resin master
packet_write_wait: Connection to 54.165.162.194: Broken pipe
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Now after a bit of googling I found people had similar issues with git, I tried a verbose SSH connection:

$ ssh -vT gh_deviouspenguin@git.resin.io
debug1: Host 'git.resin.io' is known and matches the ECDSA host key.
debug1: Found key in /Users/codec/.ssh/known_hosts:25
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/codec/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to git.resin.io ([54.165.162.194]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_GB.UTF-8
packet_write_wait: Connection to 54.165.162.194: Broken pipe

So it looks like my SSH key is working but I still can’t connact to Resin.

I’m now pretty much stuck, I’m using a Macbook running OS X 10.11.6 but I can try using another Raspberry Pi (2) which is running Raspbian in order to see if it gives the same error?

Thanks


#2

This looks to me like a temporary service outage, that hit during a (for resin) quiet time, so no broader confirmations.
I’m going to spin up a new application soon and try to deploy the getting started Node server, but I’d appreciate it if you could try again now that several hours have passed (most people are enjoying their weekend, so support shifts are more sparse).
Also, may I congratulate you on using Resin soon enough to bag a really cool nickname.
Andrew.


#3

Thanks, Futurama was a great show :smiley:

I’ve tried doing ‘git push’ again, and am getting the same issue. I’ve also tried a different example, I tried using the python example ‘simple-server-python’ and get the same error.

I have a feeling the problem is on my end however, I’ve tried doing a little more troubleshooting and I’m also unable to connect to github using my ssh key, I get almost the same error:

$ ssh -Tv git@github.com
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /Users/codec/.ssh/known_hosts:26
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/codec/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([192.30.253.113]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_GB.UTF-8
packet_write_wait: Connection to 192.30.253.113: Broken pipe

So it looks like it may be some sort of network issue? I’m pretty new to the whole git and github universe, so I’m going to go off and doing a ‘getting started with github’ and see if there’s something I’ve overlooked or screwed up somewhere.


#6

Thanks for the update. Triaging our other support services and check my more general communications took longer than expected so I’m only now sitting down with the dedicated time to isolate where these particular gremlins are.
Andrew.


#7

Okay, so I’ve just confirmed that I can push the sample code to a new application, within my existing account. With the troubles connecting to github (I get a welcome message then exit, which is expected behaviour) I am suspicious of your network. What is your network configuration like? No proxies (transparent especially), firewalls or stuff?


#8

That’s good to know everything is working with Resin ok, I checked the github status page and there are no issues right now, so yep I’m 99% sure it’s my network. I’ve tried creating a test repo on github and am unable a push a text file despite follow the instructions to the letter.

My network setup is pretty standard, no proxies or VPN.

My ISP is TalkTalk in the UK using VDSL2+, my router is a TP-Link VR2600, most of the settings on the router are default settings, the only non standard thing is I’m using OpenDNS DNS servers set in the router.

I’ve not tried different DNS settings yet, but I’ll try using my ISP’s DNS and Google’s DNS now in order to see if this is causing the issue.

I’ve tried both a Macbook running OSX and another Raspberry Pi running Raspbian as the machine to do ‘git push’, each with a different SSH key, Macbook on wifi and the Raspberry Pi on wired.

I did find someone else who had the same issue on SA: http://stackoverflow.com/questions/14123170/git-impossible-to-push-after-add - I did try reducing the MTU size on my laptop but it didn’t seem to have any effect.

EDIT: I’m using the Google DNS servers now instead of the OpenDNS servers, I get the exact same errors so I can rule out DNS servers causing the issue.

Also I will be at a different location tomorrow which will have a different ISP and router, so I’ll try ‘git push’ from that location and see if that does the trick. :slight_smile:


#9

Let us know how you get on, it is nice to have all issues documented for other visitors; even when we can be pretty certain it’s not the resin stuff that’s breaking.

Isolating your keys/pc from your isp/network is a very good next step. For me ssh direct to both IP’s gives welcome/bounce. The output of these commands might well be worth comparing across set ups.


#10

Ok, progress has been madeI have made the Unicorn appear :smiley: ‘git push’ now works, but only after connecting up to a public wifi hotspot which is just within range. I’m still connected to it right now so I can try nslookup from the public wifi:

$ nslookup github.com
Server:		192.168.22.22
Address:	192.168.22.22#53

Non-authoritative answer:
Name:	github.com
Address: 192.30.253.112
Name:	github.com
Address: 192.30.253.113

So it looks like my home network is the issue 100%, I’m going to check my router is running the latest firmware and seeing is anyone else has had any SSH issues.

FWIW here’s what I get when doing a verbose SSH connect to Resin with the public wifi:

$ ssh -vT gh_deviouspenguin@git.resin.io
Authenticated to git.resin.io ([54.165.162.194]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_GB.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
Invalid command: undefined
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3344, received 1704 bytes, in 1.5 seconds
Bytes per second: sent 2257.8, received 1150.5
debug1: Exit status 1

EDIT:

Connected back to my home network, nslookup gives the same result

Non-authoritative answer:
Name: github.com
Address: 192.30.253.112
Name: github.com
Address: 192.30.253.113


#11

Glad we got to the bottom (ish) of this, and that you saw the unicorm. If you’ve any other problems feel free to ALL GLORY TO THE HYPNOTOAD.


#12

:smiley: Thanks very much for your help

It looks like the router I’m using has some issues with SSH so I’m going to pester their support for a beta firmware: http://forum.tp-link.com/showthread.php?94412-vr2600-ssh-TOS-issues

Fingers crossed that will fix it