Re: I can't read files deployed on a Diego App

Matthew Sykes <matthew.sykes@...>

For those that are interested, I want to make sure that you're aware that
the daemon supports sftp and scp as well as the interactive shell. I don't
think it would be hard for the cli team to pull in the sftp client at and implement most of what exists with the older DEA
`files` api.

Basically, the plumbing is there - it's the cli that's missing; when you
can't use the cli, you can use your existing ssh tools with the information
Eric pointed you to.

On Thu, Jan 7, 2016 at 2:08 PM, Gerhard Lazu <gerhard(a)> wrote:

When Diego was made the default runtime on PWS in October 2015, a number
of things changed in the cf cli behaviour which at that point in time was
bumped to 6.13.0. cf files stopped working & cf ssh became a cf cli
built-in, not a Diego plugin add-on.

To get cf ssh working with Diego apps deployed on PWS, cf login had to be
run with the --sso flag. I know this with absolute certainty because we
ended up changing some of the CF training material for the Berlin CF
Summit. This is the commit
that captured the initial training material changes and, after discussing
the Diego / cf ssh situation with PWS support, this commit
changed the "Not fully integrated into PWS yet" to "Not publicly announced
on PWS yet".

I have just re-run the steps with the CF training debug app against PWS
*without* the --sso flag

cf login -a -u gerhard(a)...
cd 06-debugging/debug-app
cf p
cf ssh debug-app

I can confirm that cf ssh works with the regular login, the --sso flag is
no longer required when logging in

Thanks, Gerhard.

On Thu, Jan 7, 2016 at 7:36 PM, Daniel Mikusa <dmikusa(a)> wrote:

On Thu, Jan 7, 2016 at 1:48 PM, Kris Hicks <khicks(a)> wrote:

It sounds like we should make some changes to remove some of the anguish
Juan Antonio has gone through:

* Update to
include the notice that the plugin is only for CLI v6.12.4 and older

* Update cf files help text to say it only works for DEAs

* Update cf files to only work when the targeted space has SSH enabled
+1, but I think you mean `cf ssh` not `cf files`, right?

* Update cf ssh help text to say it only works for Diego

* Update cf ssh's error message when login fails due to not having
logged in with a token, if possible
I don't agree with this one. @gerhard - can you expand on your comment.


I've copied the CLI PM, Dies Koper, to get these stories created.


On Fri, Jan 8, 2016 at 4:19 AM, Gerhard Lazu <gerhard(a)>

You need to cf login with a token - not the password - for cf ssh to
work. cf h login will tell you the exact flag to use for token login.


On Thursday, 7 January 2016, Juan Antonio BreƱa Moral <
bren(a)> wrote:

Yes, debugging CLI I think that the problem is in this REST call:

GET /login?code=4xCqgC HTTP/1.1
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip

RESPONSE: [2016-01-07T15:05:43+01:00]
HTTP/1.1 302 Found

Error: SSH session allocation failed: ssh: unexpected packet in
response to chan
nel open: <nil>
Error: SSH session allocation failed: ssh: unexpected packet in
response to chan
nel open: <nil>

Juan Antonio
Matthew Sykes

Join { to automatically receive all group messages.