Page 1 of 1

Odd Legacy Issue

Posted: 2022-08-17 12:53
by bclingan
I've been troubleshooting an odd issue. I have a legacy app... Python 2.5.4 on Windows Server 2008... it can connect to older versions of FileZilla Server but not latest one. It makes the initial connection, but then nothing after- no ability to send/receive files or list directories, etc... connections timeout.. I'm suspecting a port issue, but what would be different between older FileZilla Server and current one for this to happen?

Re: Odd Legacy Issue

Posted: 2022-08-17 14:57
by botg
What does it say in the log?

Re: Odd Legacy Issue

Posted: 2022-08-17 19:24
by CrimpOn
It might be a good idea to change the log level to get more detail in the FileZilla log:
LogLevel.JPG
LogLevel.JPG (29.85 KiB) Viewed 3465 times

Re: Odd Legacy Issue

Posted: 2022-08-18 18:36
by bclingan
So currently, I see the connection and then nothing after. On the client side, a timeout occurs.

2022-08-18T18:22:53.679Z << [FTP Session 160 XX.XXX.XX.XXX] 220-FileZilla Server 1.5.1
2022-08-18T18:22:53.679Z << [FTP Session 160 XX.XXX.XX.XXX] 220 Please visit https://filezilla-project.org/
2022-08-18T18:22:53.695Z >> [FTP Session 160 XX.XXX.XX.XXX] USER **REDACTED**
2022-08-18T18:22:53.695Z << [FTP Session 160 XX.XXX.XX.XXX] 331 Please, specify the password.
2022-08-18T18:22:53.727Z >> [FTP Session 160 XX.XXX.XX.XXX] PASS ****
2022-08-18T18:22:53.807Z << [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] 230 Login successful.
2022-08-18T18:22:53.823Z >> [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] CWD /
2022-08-18T18:22:53.823Z << [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] 250 CWD command successful
2022-08-18T18:22:53.855Z >> [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] TYPE I
2022-08-18T18:22:53.855Z << [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] 200 Type set to I
2022-08-18T18:22:53.876Z >> [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] PASV
2022-08-18T18:22:53.876Z << [FTP Session 160 XX.XXX.XX.XXX **REDACTED**] 227 Entering Passive Mode (XX,XXX,XX,X,XXX,XXX)

I will turn up logging level and see what I get.

Re: Odd Legacy Issue

Posted: 2022-08-18 19:01
by bclingan
Nothing illuminating after additional logging added.

2022-08-18T18:43:52.892Z II [FTP Session 166 XX.XXX.XX.XXX] Session 0x12e659aacf0 with ID 166 created.
2022-08-18T18:43:52.892Z << [FTP Session 166 XX.XXX.XX.XXX] 220-FileZilla Server 1.5.1
2022-08-18T18:43:52.892Z << [FTP Session 166 XX.XXX.XX.XXX] 220 Please visit https://filezilla-project.org/
2022-08-18T18:43:52.907Z >> [FTP Session 166 XX.XXX.XX.XXX] USER **REDACTED**
2022-08-18T18:43:52.907Z << [FTP Session 166 XX.XXX.XX.XXX] 331 Please, specify the password.
2022-08-18T18:43:52.923Z >> [FTP Session 166 XX.XXX.XX.XXX] PASS ****
2022-08-18T18:43:52.923Z DD [Throttled Authenticator] Authenticating user **REDACTED** from IP XX.XXX.XX.XXX.
2022-08-18T18:43:52.986Z DD [File-based Authenticator] authenticate: is_from_system: 0, impersonation_token: { username: "", home: "" }
2022-08-18T18:43:52.986Z << [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] 230 Login successful.
2022-08-18T18:43:53.001Z >> [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] CWD /
2022-08-18T18:43:53.001Z DD [FTP Session 166 XX.XXX.XX.XXX **REDACTED**/TVFS/local_filesys] info(F:\**REDACTED**): result: 0
2022-08-18T18:43:53.017Z << [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] 250 CWD command successful
2022-08-18T18:43:53.033Z >> [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] TYPE I
2022-08-18T18:43:53.033Z << [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] 200 Type set to I
2022-08-18T18:43:53.049Z >> [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] PASV
2022-08-18T18:43:53.049Z VV [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] Trying listen(1, 0) for data connection.
2022-08-18T18:43:53.049Z << [FTP Session 166 XX.XXX.XX.XXX **REDACTED**] 227 Entering Passive Mode (XX,XXX,XX,X,XXX,XX)
2022-08-18T18:44:14.286Z == [FTP Server] Session 166 ended gracefully.
2022-08-18T18:44:14.286Z II [FTP Session 166 XX.XXX.XX.XXX] Session 0x12e659aacf0 with ID 166 destroyed.

Re: Odd Legacy Issue

Posted: 2022-08-19 07:17
by botg
Unfortunately all diagnostic information has been removed from the log.