Filezilla-server Service Terminated Unexpectedly

[csteinhaus@questce.com]

Hello,

I see in our Event View that the Filezilla-server is Terninating unexpectedly every time a user attempts to connect using the Filezilla client. Here is the information received by the client(Server IP redacted):
Status: Connecting to 999.999.999.999:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful
Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from socket: ECONNABORTED - Connection aborted
Error: Disconnected from server

On the server side, the service stops. I have attached a file with the messages from the Administration interface.
I reinstalled the server using the latest version, 1.7.2, to attempt to fix the issue, but the problem remains.

What is causing the Filezilla service to terminate?

[boco]

Check for a recent crash log/dump in %LOCALAPPDATA%\Crashdumps - the crashdump information will be much more useful for service crashes.

[botg]

Note that the server service by default runs as SYSTEM, so you need to use the SYSTEM account's %LOCALAPPDATA%. On a standard Windows installation it should resolve to C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps

[csteinhaus@questce.com]

Hi All,

I have attached a screenshot of the Log On tab of the Filezilla-service and the crashdump folder. The Log On setting looks correct, but there aren't any dump files. I have the logging level set to 5 - Debug and have attached the log file. Please let me know if there is any more information you need.

Thank you,
Curt

[oibaf]

When the service stops, which status is it in?

When you find it has stopped, can you please issue the following command and paste the result here?

Code: Select all

sc queryex filezilla-server

[botg]

2023-06-12T19:04:18.313Z << [FTP Session 2 207.250.135.154 csteinhaus] 227 Entering Passive Mode (192,168,147,6,248,106)

While this has nothing to do with the server terminating, you may want to configure the server's passive mode settings such that it reports the correct IP address in the PASV reply to clients connecting from the Internet.

[csteinhaus@questce.com]

Hi oibaf,

I verified the service was running and waited for it to stop. When it had stopped, I refreshed the Sevices view and ran the sc queryex command you suggested. I attached the screenshot to this post. Please let me know the next steps.

[oibaf]

Did you install the program with the provided installer, or by other means?

Could you check that the registry keys and values under "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" look the same as the ones in the following picture?

Schermata del 2023-06-13 18-50-02.png (14.35 KiB) Viewed 3216 times

Can you also check if you have got the Disabled DWORD value under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\

If you have, can you make sure its value is set to 0 (which means Enabled)?

If it was set to 1, please set it to 0. Then, to make sure the new value is taken into account, reboot the system. Then wait for the service to stop again. At that point you should have the minidump at the aforementioned location. If you do, please send it to tim.kosse@filezilla-project.org

[csteinhaus@questce.com]

Hi oibaf,

The issue started with our previous version of Filezilla Server. Since there was a new version available, I made a copy of my config file, used the Filezilla uninstall program to remove the program. Use the latest Filezilla setup exe to install the version. Converted my previous config file to create a user.xml file and copied it to the Filezilla programdata folder. I then setup the current version base of the config of our previous version.

The Reg entries look correct to my, please see the screenshot.

[oibaf]

Please, make sure to read also the second part of my previous post. I've edited it, but probably you have not read the edited version before responding.

[csteinhaus@questce.com]

The Disabled DWORD value is not listed under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\

[oibaf]

Thanks for your patience. It looks like you have everything set up for minidumps to be generated, yet you say they are not and we're at a loss as of why.

There's one more thing we could do to investigate the matter, if you're willing to go through with it: install Visual Studio (the community edition is fine) and attach its debugger to the filezilla-server.exe process. Then, when it crashes, choose "Save Dump As..." from the "Debug" menu.

It'd be very much appreciated if you did that.