"Error: ssh program unexpectedly exited" when trying to browse files on router

If you go to Places>Connect to server and attempt to connect, do you have the same behavior? Do you know what ssh server is on the router? I would guess dropbox, but knowing for sure might be helpful.

It does seem that SSH should not crash.

Yes, that is how I am connecting.

Tomato v1.25.1720

BusyBox v1.14.0 (2009-05-25 16:08:27 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Is "dropbear" the right answer?

dropbear[812]: password auth succeeded for 'root' from

I'm seeing the same error message when I try to connect to an OpenSSH 4.3 (protocol 1.99) server. I think this bug deserves another look.

Can you try to reproduce this issue in latest version of nautilus (2.28.1 ships in Karmic)? Thanks!

Yes, it still happens in Karmic in Virtualbox

    Cannot display location "sftp://root@router/"
    ssh program unexpectedly exited

The same issue from nautilus. Had issued command 'sftp 192.168.1.1 -vvv' in terminal (192.168.1.1 - is my router). The response is:
  Connecting to 192.168.1.1...
  admin@192.168.1.1's password:
  sh: /opt/libexec/sftp-server: not found
  Connection closed

SSH server on the router is actually dropbear. Seems that one should use some other sftp subsystem (according to sftp manual it would be 'sftp -s ... ', yet I just haven't figured out what to use)

Though, nevertheless scp is working ok (heh, why not):
$ > echo 'test' > test.out
$ > scp test.out admin@192.168.1.1:/tmp
admin@192.168.1.1's password:
test.out 100% 5 0.0KB/s 00:00

Yep, that is, googled a bit, the problem seems to be that dropbear installed on the router lacks sftp subsystem, so no sftp from nautilus too. It doesn't seem to be problem of nautilus, though it would be great to have some better error message, "Error: ssh program unexpectedly exited" doesn't seem to be enough informative.

Hi i'm having this same problem when trying to connect to one of my sftp locations, using Ubuntu 9.10 (up to date) and doing "Places->Connect to server"

The server which is giving me the problem is running Solaris 9 and the following version of SSH:
OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f

I regularly use the same method to connect to other sftp location without problems.

I tried connecting to the sftp location in question from the command line and recived the following error:
Connecting to <server>
subsystem request failed on channel 0
Couldn't read packet: Connection reset by peer

Connecting to the same server with FileZilla using sftp, works just fine.

Clearly a but in openssh and not nautilus

What is the status of this bug?
It's been more than half a year...

i get the same error when i try to connect to OpenSSH_5.1p1 from nautilus, works from command line(bash). Also it used to work in nautilus but then start giving me this error all of a sudden.

I know if I reboot and try to connect with nautilus again to the same server this error will not show until it shows again.

i have tried to do killall nautilus and try to reconnect again but still it gives me this error.

I am using karmic.

Maybe this is something with DBus? just guessing.

If there was more output I could debug more but I dont know where to look in this case.

I know this is possibly a bit off-topic, but I had this same error message and the problem turned out to be my server. OpenSSH was set up correctly, but /dev/null had the wrong permissions (700 instead of 666) which was stopping SFTP from functioning.

Just thought I'd leave this here in case anyone else is Googling a similar problem. :)

I think I know how to solve the problem:
(at least it works for me)

In my case it was related to some output when "running interactively".

Open a terminal and do:
ssh username@server /bin/true
(or maybe)
ssh username@server /usr/bin/true

If you get any output, then you probably need to write at the beginning of the server's ~/.bashrc:
# If not running interactively, don't do anything
[ -z "$PS1" ] && return

Try "ssh username@server /bin/true" again. If there is no output, try connecting through nautilus.

Good luck!

I'm having the same problem connecting to a remote sftp server.

By the way, I'm running Maverick.

 I have been unable to solve the problem :(

> -----Original Message-----
> Frá: Kip Warner <email address hidden>
> Til: <email address hidden>
> Dagsetning: 21/10/2010 06:30
> Viðfangsefni: [Bug 424648] Re: "Error: ssh program unexpectedly exited" when trying to browse files on router
>
> By the way, I'm running Maverick.
>
> --
> "Error: ssh program unexpectedly exited" when trying to browse files on router
> https://bugs.launchpad.net/bugs/424648
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “openssh” package in Ubuntu: New
>
> Bug description:
> If I try to browse the filesystem on my router through Nautilus, ssh crashes, even though I can access it through SSH on the command line.
>
> This is probably because the router lacks whatever lets you browse files (it's a minimal ssh server), but the error message could be more helpful.
>
> Could not display "sftp://root@router/".
> Error: ssh program unexpectedly exited
> Please select another viewer and try again.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/424648/+subscribe

Apparently this describes the underlying problem:
https://bugs.archlinux.org/task/20724

 I'm able to connect to openssh using nautilus, the problem is connecting to an ancient openssh server running on Solaris 8

> -----Original Message-----
> Frá: Kip Warner <email address hidden>
> Til: <email address hidden>
> Dagsetning: 22/10/2010 00:22
> Viðfangsefni: [Bug 424648] Re: "Error: ssh program unexpectedly exited" when trying to browse files on router
>
> Apparently this describes the underlying problem:
> https://bugs.archlinux.org/task/20724
>
> --
> "Error: ssh program unexpectedly exited" when trying to browse files on router
> https://bugs.launchpad.net/bugs/424648
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “openssh” package in Ubuntu: New
>
> Bug description:
> If I try to browse the filesystem on my router through Nautilus, ssh crashes, even though I can access it through SSH on the command line.
>
> This is probably because the router lacks whatever lets you browse files (it's a minimal ssh server), but the error message could be more helpful.
>
> Could not display "sftp://root@router/".
> Error: ssh program unexpectedly exited
> Please select another viewer and try again.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/424648/+subscribe

For me it doesn't seems to be the by Kip Warner mentioned bug in gvfs. I updated the gvfs-packages from the natty-repository (I'm currently working with maverick) where gvfs has version 1.7... (above the mentioned 1.6-1) but my problem persists. :-(

ssh-login via terminal and filezilla works perfectly, so seems to be no server-side problem.

dmesg shows nothing, has anyone any other debugging-ideas? (or even a solution :-))

thx for any suggestions!

Similar error, Natty Narwhal, but with Gigolo in Xubuntu.

This is PATHETIC, the bug has been here for 1,5 year and nobody gives a fuck. WHAT THE HELL IS IT WITH YOU LAZY DEVS?

Pétur, be respectful, and if you think it is easy to solve, you can code it and be the hero. Or pay the "lazy" devs...

Petur is RIGHT! We've been waiting fix over 1,5 years and still NO FIX!

WHAT IS THIS? IF THIS WOULD BE REAL JOB PEOPLE HAD BEEN FIRED LONG TIME AGO.

I call it as lazyness.

As you said Jaakko, but if the would be actual employees (most are not), they would be PAID to do the job, and you would be probably paying Canonical for the soft. And you don't. It is not lazyness to work for free in something, even if you don't meet the whole users's expectatives.

You don't like it, change distro, change to another free OS, or even better, pay M$ or Apple.

Sorry for spamming. The last until someone ask again. Lazyness is to not code at all and complain :)

ox:~ petur$ uname -a
Darwin box.local 10.5.0 Darwin Kernel Version 10.5.0: Fri Nov 5 23:20:39 PDT 2010; root:xnu-1504.9.17~1/RELEASE_I386 i386

and that stupid ssh bug does not bother me.

What's your point, then? That you use opendarwin? It is the same point here, you are complaining like a little girl, don't you? Telling everyone else that they should work more, when you are doing nothing to help.
Also, the 1.5 years old bug started to affect me just when I upgraded to Natty, I use Maverick in two other computers and works, and it worked for me in every other release. I have news for you, there might be: config mistakes; regressions; and you can compile a newer or older release to see if it works better. But then, the lazyones are the ones who actually MAKE the software.

Developers don't need to be paid. They will work for free because programming is fun. Haven't you read the GNU Manifesto?

"In the long run, making programs free is a step toward the postscarcity world, where nobody will have to work very hard just to make a living. People will be free to devote themselves to activities that are fun, such as programming, after spending the necessary ten hours a week on required tasks such as legislation, family counseling, robot repair and asteroid prospecting. There will be no need to be able to make a living from programming." http://www.gnu.org/gnu/manifesto.html

Also, you can use the same software recompiled for XNU, so your uname means nothing, as the bug, if in the GVFS, might actually affect you in XNU. FreeBSD (yes, the same it is sort of hybridized with a microkernel in XNU) claims source compatibility with linux.

And there are hard to catch bugs too. It is not always lazyness, there are random bugs, hardware dependant bugs, IF you are going to tell someone else they are lazy, maybe you can work to find the origin of the bug, you can commit patches too.

So? It is clairly stated the fact it is a possible future, not a today. Nowadays, most programmers needs to make a living from something, and they can be actually paid for doing what they like to do, or they can be just allowed to do it without some hipocritical people asking them to do what they want them to do. After all, they are not paying a product, what right have they to insult them or talk about them like "lazy devs". They probably have an 8 hours a day job like anyone else, and they are programming FOR FREE for someone who does not seems to appreciate it.

Don't get involved as a volunteer if you cannot act up to the expectation of what your doing.

And no, I don't appreciate broken software as it's USELESS to me.

But not everyone has the same expectations when involving. I mean, think of the GVFS (IIRC, someone said that's where the bug relies), maybe they just don't have someone who wants to code for the network uses of it, and as a volunteer you should work in your interest topics, basically because noone is going to pay you to work in something you don't like. I don't appreciate the broken software itself, I appreciate the people who actually try to fix it, and the people who make it in the first place. Also, as I said, it doesn't look like an ubicuous bug, since in my computers worked until today (I updated a few days ago, but until today I didn't tried to use SSH again).

Did you (users suffering this problem) checked that you are actually connected to the computer you try to use SSH with? In my case, I forgot to switch to the other wifi router to connect, and that's what is killing the program. Maybe that is the "bug".

My case is not bug (or at least, the action which triggers it is to not be connected to the same router with both computers, the other one is connected to another router and is the routers which are connected each other, anyway, the bug is triggered when using in a useless way XD). F*ck my memory.

Hey,

on the server side, try to specify the full path to the sftp-server binary explicitly in the sshd's config file. In Debian that would be:

Subsystem sftp /usr/lib/openssh/sftp-server

Worked for me at least.