kex_exchange_identification: read: Connection reset by peer

[dirk]

I’m having issues connecting to my remote Pi using spacebridge. I was able to connect previously with a different hologram SIM card. Below is the output from terminal:

$ ssh -Y 127.0.0.1 -p5000 -vvvv
OpenSSH_8.0p1, OpenSSL 1.0.2s  28 May 2019
debug1: Reading configuration data /Users/Dirk/.ssh/config
debug1: /Users/Dirk/.ssh/config line 1: Applying options for *
debug1: /Users/Dirk/.ssh/config line 6: Applying options for 127.0.0.1
debug1: Reading configuration data /usr/local/etc/ssh/ssh_config
debug2: resolve_canonicalize: hostname 127.0.0.1 is address
debug2: ssh_connect_direct
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 5000.
debug1: Connection established.
debug1: identity file /Users/Dirk/.ssh/id_rsa type 0
debug1: identity file /Users/Dirk/.ssh/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.0
kex_exchange_identification: read: Connection reset by peer

I’m not sure what Connection reset by peer means.
Also, this is the output from the spacebridge app:

$ /Applications/spacebridge ; exit;
Secsh channel 0 open FAILED: open failed: Administratively prohibited
Incoming request to link511255:22 failed: ChannelException(1, 'Administratively prohibited')

[Reuben]

Have you enabled tunneling on the SIM?

[dirk]

Device tunneling is enabled on the dashboard

[Reuben]

Is it possible this SIM is under a different user account from the other one? The spacebridge client might be using the tunnel key from another account.

[dirk]

That is a possibility. The first SIM is under an org. account and the second is on a different user account. Is there a command line function to specify a new tunnel key?

[Reuben]

If you look inside the .hologram directory in your home directory you’ll see the keyfile. If you rename or delete it then the spacebridge client will generate a new one for whatever user is attached to the API key you specify.

[dirk]

Thanks! I shall try that the next time my remote device connects to the network.