Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: "Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0" #211

Open
isarrider opened this issue Jan 3, 2023 · 4 comments
Open

Comments

@isarrider
Copy link

Hi,

when using Dropbear together with this sftp server (and WinSCP),
I get after like transferring a few hundred Megabytes:
image

Can I help debug this somehow?
(Reference: ewxrjk/sftpserver#17)

@mkj
Copy link
Owner

mkj commented Jan 6, 2023

I haven't seen that before - does it happen at the end of a transfer or session? Is it reliable to reproduce? If winscp has a debug log option that might give some clues. I agree with Richard Kettlewell - it looks like a bug in Dropbear or WinSCP.

I'll see if I can reproduce it here when I have time - what are the versions of Dropbear, WinSCP, sftpserver?

@isarrider
Copy link
Author

isarrider commented Jan 6, 2023

it happens during the transfer session, with big files (~2GB usually more than 1x)...
For me it is really reliable to reproduce...
WinSCP does have a debug log - which level would you like?
(Cause the highest one really produces LARGE log files)
Version are the latest ones availible atm... (not the WinSCP beta, but the normal version...

@mkj
Copy link
Owner

mkj commented Jan 24, 2023

Sorry missed your question about logs - any size would be OK, whatever's the largest you can upload!

@isarrider
Copy link
Author

No worries...
Meanwhile there were some more tests:
MichaIng/DietPi#3296 (comment)
Ill take a look when I can do more tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants