Re: [Proftpd-user] PROFTPD - ERROR:> unexp. packet type 95 in respond to SSH_MSG_CHANNEL_REQUEST (error #77)

[Cosmin N. <cos...@az...>]

You were spot on TJ, that was actually the only difference between Test Server and Production server.
On the test server, I had the DisplayLogin directive, but was pointing to a non-existent file.
Once I created the login file, started to get the same error with the test instance as well.

Any idea if there's another way (maybe not too complicated) to circumvent this for a particular SFTP client type? Other than removing the DisplayLogin banner?
Kind of reluctant to disable the login banner in production, just for one sftp client - we have hundreds of clients.






Best regards,

Cosmin Neagu

Network Architect

Phone +40.744.625.033

________________________________
From: TJ Saunders <tj...@ca...>
Sent: Tuesday, June 24, 2025 8:34 PM
To: ProFTPD Users <pro...@li...>
Cc: Cosmin Neagu <cos...@az...>
Subject: Re: [Proftpd-user] PROFTPD - ERROR:> unexp. packet type 95 in respond to SSH_MSG_CHANNEL_REQUEST (error #77)


> I have proftpd version 1.3.8b installed on 2 production servers, and a
> client using TurboFTP client, complains about getting this error, after
> succesfull authentication:
> *unexp. packet type 95 in respond to SSH_MSG_CHANNEL_REQUEST (error
> #77)*

Packet type 95 means that that unexpected packet is SSH2_MSG_CHANNEL_EXTENDED_DATA.  It's not exactly common, which is why your particular SFTP client might be be handling it like other SFTP clients.

In this case, the mod_sftp module uses SSH2_MSG_CHANNEL_EXTENDED_DATA to convey the contents of your DisplayLogin file to the client.  You might try commenting out that DisplayLogin directive, restarting ProFTPD, and seeing if your SFTP client works without encountering that issue.

Hope this helps,
TJ