Re: [Proftpd-user] PROFTPD - ERROR:> unexp. packet type 95 in respond to SSH_MSG_CHANNEL_REQUEST (error #77)
Cosmin Neagu via Proftp-user <[email protected]> Wed, 2 Jul 2025 08:29:30 +0000
| Newsgroups | gmane.network.proftpd.user |
|---|---|
| Message-ID | <CWLP265MB6385CAB3F6C55760698F08A38F40A@CWLP265MB6385.GBRP265.PROD.OUTLOOK.COM> |
--===============4997447578465038819== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CWLP265MB6385CAB3F6C55760698F08A38F40ACWLP265MB6385GBRP_" --_000_CWLP265MB6385CAB3F6C55760698F08A38F40ACWLP265MB6385GBRP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You were spot on TJ, that was actually the only difference between Test Ser= ver 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 t= his 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 s= ftp client - we have hundreds of clients. Best regards, Cosmin Neagu Network Architect Phone +40.744.625.033 ________________________________ From: TJ Saunders <[email protected]> Sent: Tuesday, June 24, 2025 8:34 PM To: ProFTPD Users <[email protected]> Cc: Cosmin Neagu <[email protected]> Subject: Re: [Proftpd-user] PROFTPD - ERROR:> unexp. packet type 95 in resp= ond 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_EXTEND= ED_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 co= nvey the contents of your DisplayLogin file to the client. You might try c= ommenting out that DisplayLogin directive, restarting ProFTPD, and seeing i= f your SFTP client works without encountering that issue. Hope this helps, TJ --_000_CWLP265MB6385CAB3F6C55760698F08A38F40ACWLP265MB6385GBRP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> You were spot on TJ, that was actually the only difference between Test Ser= ver and Production server.</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> On the test server, I had the DisplayLogin directive, but was pointing to a= non-existent file.</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> Once I created the login file, started to get the same error with the test = instance as well.</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> Any idea if there's another way (maybe not too complicated) to circumvent t= his for a particular SFTP client type? Other than removing the DisplayLogin= banner?</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> Kind of reluctant to disable the login banner in production, just for one s= ftp client - we have hundreds of clients.</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div id=3D"Signature"> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <p style=3D"margin-top: 0px; margin-bottom: 0px;"><span style=3D"font-famil= y: Arial, sans-serif; font-size: 9.75pt; color: black;">Best regards,</span= ></p> <p style=3D"text-align: left; margin: 0in 0in 0.0001pt;"><span style=3D"fon= t-family: Arial, sans-serif; font-size: 9.75pt; color: black;"><b>Cosmin Ne= agu</b></span></p> <p style=3D"text-align: left; margin: 0in 0in 0.0001pt;"><span style=3D"fon= t-family: Arial, sans-serif; font-size: 10pt; color: black;">Network Archit= ect</span></p> <p style=3D"text-align: left; margin: 0in 0in 0.0001pt;"><span style=3D"fon= t-family: Arial, sans-serif; font-size: 10pt; color: black;">Phone +40.744.= 625.033</span></p> </div> <div id=3D"appendonsend"></div> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> TJ Saunders <tj@ca= staglia.org><br> <b>Sent:</b> Tuesday, June 24, 2025 8:34 PM<br> <b>To:</b> ProFTPD Users <[email protected]><br> <b>Cc:</b> Cosmin Neagu <[email protected]><br> <b>Subject:</b> Re: [Proftpd-user] PROFTPD - ERROR:> unexp. packet type = 95 in respond to SSH_MSG_CHANNEL_REQUEST (error #77)</font> <div> </div> </div> <div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;= "> <div class=3D"PlainText"><br> > I have proftpd version 1.3.8b installed on 2 production servers, and a= <br> > client using TurboFTP client, complains about getting this error, afte= r <br> > succesfull authentication:<br> > *unexp. packet type 95 in respond to SSH_MSG_CHANNEL_REQUEST (error <b= r> > #77)*<br> <br> Packet type 95 means that that unexpected packet is SSH2_MSG_CHANNEL_EXTEND= ED_DATA. It's not exactly common, which is why your particular SFTP c= lient might be be handling it like other SFTP clients.<br> <br> In this case, the mod_sftp module uses SSH2_MSG_CHANNEL_EXTENDED_DATA to co= nvey the contents of your DisplayLogin file to the client. You might = try commenting out that DisplayLogin directive, restarting ProFTPD, and see= ing if your SFTP client works without encountering that issue.<br> <br> Hope this helps,<br> TJ<br> </div> </span></font></div> </body> </html> --_000_CWLP265MB6385CAB3F6C55760698F08A38F40ACWLP265MB6385GBRP_-- --===============4997447578465038819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============4997447578465038819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ProFTPD Users List <[email protected]> Unsubscribe problems? http://www.proftpd.org/list-unsub.html --===============4997447578465038819==--