After the update of the FTP add-on from 5.1.1 to 5.2.0 I get a login error. Restoring the old version and it works again. Something wrong with this update?
What does the addon log say?
I have exactly the same issue with addon update (5.2.0).
Mon Feb 17 15:55:00 2025 [pid 2] CONNECT: Client "192.168.1.154"
Mon Feb 17 15:55:00 2025 [pid 1] [admin] FAIL LOGIN: Client "192.168.1.154"
Same here! Updated to 5.2.0 today and getting the same error.
Couldn’t find anything strange in the log. Did also a restart of the ad on and then everything seems to be ok. I get the login error when I try a FTP connection using Filezilla.
The log:
Add-on: FTP
A secure and fast FTP server for Home Assistant
Add-on version: 5.2.0
You are running the latest version of this add-on.
System: Home Assistant OS 14.2 (amd64 / generic-x86-64)
Home Assistant Core: 2025.2.4
Home Assistant Supervisor: 2025.02.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-vsftpd: starting
s6-rc: info: service init-users: starting
s6-rc: info: service vsftpd-log: starting
s6-rc: info: service vsftpd-log successfully started
[12:42:14] INFO: Starting Log tailer…
s6-rc: info: service init-vsftpd successfully started
[12:42:15] INFO: Password is NOT in the Have I Been Pwned database! Nice!
s6-rc: info: service init-users successfully started
s6-rc: info: service vsftpd: starting
s6-rc: info: service vsftpd successfully started
s6-rc: info: service legacy-services: starting
[12:42:15] INFO: Starting FTP server…
s6-rc: info: service legacy-services successfully started
Mon Feb 17 12:43:23 2025 [pid 2] CONNECT: Client “192.168.178.244”
Mon Feb 17 12:43:23 2025 [pid 1] [home assistant OS] FAIL LOGIN: Client “192.168.178.244”
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service vsftpd: stopping
[12:44:00] INFO: Service vsftpd exited with code 256 (by signal 15)
s6-rc: info: service vsftpd successfully stopped
s6-rc: info: service init-vsftpd: stopping
s6-rc: info: service init-users: stopping
s6-rc: info: service vsftpd-log: stopping
s6-rc: info: service init-vsftpd successfully stopped
s6-rc: info: service init-users successfully stopped
s6-rc: info: service vsftpd-log successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
The messages from Filezilla:
Status: Connection to server disconnected
Status: Connecting to 192.168.178.211:21…
Status: Connected, waiting for welcome message…
Status: Insecure server, which does not support FTP over TLS.
Command: USER home assistant OS
Answer: 331 Please specify the password.
Request: PASS ************
Answer: 530 Login incorrect.
Error: Fatal error: Cannot connect to server
After the update the configuration (with username and password) isn’t changed, so strange that you get the message ‘Login incorrect’. So it seems that the addon doesn’t pass the credentials which are in the confguration file.
Try to up the log level in the FTP Addon configuration.
There is a new version available with a bugfix for the password file.
2 Likes
Did the upgrade again and now it works !
Thanks !
For me the 5.2.1 update works too. Many thanks.
Tue Feb 18 09:17:30 2025 [pid 2] CONNECT: Client "192.168.1.154"
Tue Feb 18 09:17:30 2025 [pid 1] [admin] OK LOGIN: Client "192.168.1.154"