Admin GUI fails after v1.8.2 update

[yatesf]

Today I upgraded from FileZilla server version 1.8.1 to 1.8.2

Everything was working fine beforehand and I did not change any OS or server config settings at all after my upgrade.

Now the admin GUI is not able to logon to localhost with the same password, default port (14148) and default localhost IP (127.0.0.1) that it had previously been using.

I am getting the following errors from my logs recurring every 1 second:

Code: Select all

2024-04-28T02:07:20.826Z !! [FTP Server] Couldn't bind on 192.168.X.XX:3**5. Reason: EACCES - Permission denied. Retrying in 1 seconds.
2024-04-28T02:07:21.826Z !! [FTP Server] Couldn't bind on 192.168.X.XX:3**5. Reason: EACCES - Permission denied. Retrying in 1 seconds.
2024-04-28T02:07:22.842Z !! [FTP Server] Couldn't bind on 192.168.X.XX:3**5. Reason: EACCES - Permission denied. Retrying in 1 seconds.

I have rebooted my Windows 11 machine multiple times. I have also disabled AV and firewall to no avail.

My "rights management" config in the server has always been to run as system user. I even toggled it after the problem to run as the user I logon as, and it did not change the results.

Of note, my server still works fine for external/incoming FTP connections, I am just unable to logon locally via the admin GUI in order to monitor the server.

This error never happened on v1.8.1 or prior.

[oibaf]

If you run the following command in a cmd/powershell window, what does it say?

Code: Select all

netsh interface ipv4 show excludedportrange protocol=tcp

Also, which user is the filezilla-server service running under? This would be the name after the "The server you are connecting to is running as ..." string in the Rights management configuration pane.

[yatesf]

Code: Select all

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
      2869        2869
      5357        5357
     10243       10243

* - Administered port exclusions.

running as SYSTEM.

[oibaf]

That's the server's machine or the one you're running the administration interface on?

The log you've pasted show errors from the FTP Server. The one related to the administration is the Administration Server. Can you please post the full log?

[yatesf]

I've always ran the Admin GUI on the same machine as the server and connected to the Admin GUI via localhost (127.0.0.1).

I fixed the problem. Previously, I've always had my machine's interface IP under the server listeners in the settings. Now since it seems to produce the constant error in the FTP server logs, I removed it from the server listeners and my FTP server still works fine, but more importantly, the Admin GUI does not produce the constant recurring errors that were showing up every 1 second as referenced from my previously cut and pasted log messages.

And my former description of the problem was technically inaccurate. I have still been able to log into the Admin GUI after the upgrade, it is just that the GUI screen would now produce the constant barrage of those "EACCES - Permission denied" errors and I mistook that to be a GUI logon problem, which it was not.

I have also attached a screenshot ("server-listeners.png") of my former server listener settings where I only removed the bottom line (where the red arrow is pointing) in order to resolve the new problem after the upgrade. In other words, the "EACCES - Permission denied" errors no longer happen after removing that last listener entry. If this is a bug and I am indeed supposed to have my interface IP with those other server listener settings (for future technical accuracy), please clarify so I can add it back in when the fix is published.

That last server listener line never caused an error in previous versions of the server.

[boco]

More so, as the 0.0.0.0 address already includes all IPv4 addresses that exist. And :: includes all IPv6 addresses. So, these two entries are sufficient.