hassio-addons/addon-ftp

FTP - Home Assistant Community Add-ons

Home Assistant Community Add-on: Log Viewer

Browser-based log utility for Home Assistant.

About

Easily monitor your Home Assistant logs in your web browser. Custom filtering is available to make it simple to differentiate different types of logs.

📚 Read the full add-on documentation

Support

Got questions?

You have several options to get them answered:

• The Home Assistant Community Add-ons Discord chat server for add-on support and feature requests.
• The Home Assistant Discord chat server for general Home Assistant discussions and questions.
• The Home Assistant Community Forum.
• Join the Reddit subreddit in /r/homeassistant

You could also open an issue here GitHub.

Contributing

This is an active open-source project. We are always open to people who want to use the code or contribute to it.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! 😍

Authors & contributors

The original setup of this repository is by Dale Higgs.

For a full list of all authors and contributors, check the contributor's page.

We have got some Home Assistant add-ons for you

Want some more functionality to your Home Assistant instance?

We have created multiple add-ons for Home Assistant. For a full list, check out our GitHub Repository.

License

MIT License

Copyright (c) 2018-2024 Dale Higgs <@dale3h>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

addon-ftp's Issues

error s6-rc-init:

Problem

s6-rc-init: fatal: unable to supervise service directories in /run/s6-rc/servicedirs: Exec format error

Version: 4.6.2

Home Assistant 2023.2.4
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest

Unable to mount /share

Utilization of option to provide access to share/ directory fails when specified in options

mount: mounting /share on /ftproot/users/eyespy/share failed: Permission denied

Expected behavior

Expected to have /share mounted

Actual behavior

Permission denied

Steps to reproduce

Change default configuration of addon to indicate "share": true (default is false)

Proposed changes

None

Possibility for a user's home folder to be directly mounted on the share

Motivation

I have a door bell that enables to upload snapshots to an FTP server (Dahua brand) but it does not provide the possibility to give a base folder inside the ftp server.
It would be nice if I could set an option for a specific user to chroot him to the share mount.
An option like chroot_to_share

Expected behavior

I would like to have the user homefolder be bound to the /share

Actual behavior

My door station can create the directory structure but it is inside the docker container instead of outside

Proposed changes

if bashio::config.true "users[${user}].chroot_to_share"; then
    mount --bind "/share" "/ftproot/users/${username}"
fi

FTP addon v4.2.0: TLS/SSL no longer working?

Got this message when logging in to FTP server:
500 OOPS: error:141FC0B5:SSL routines:tls_setup_handshake:no ciphers available.

This didn't happen in the previous version.

This is my current FTP addon and HA:
Add-on version: 4.2.0
You are running the latest version of this add-on.
System: Ubuntu 20.04.2 LTS (amd64 / qemux86-64)
Home Assistant Core: 2021.6.6
Home Assistant Supervisor: 2021.06.6

Setting SSL to 'false' in the configuration "solves" this issue, but of course this is not the solution.

Am I missing something?

Uploaded files lost on restart

Problem/Motivation

All uploaded data lost on restart of the container/addon

Expected behavior

Data is stored on a volume that is not wiped on restart

Actual behavior

Data is stored in /ftproot/ which is part of the image and gets wiped on restart

Steps to reproduce

Set all of addons, backup, config, share to false for [username]

1. Upload a file
2. Check if the file is stored in /ftproot/users/[username]
3. Restart the addon
4. Check that /ftproot/users/[username] is empty

Proposed changes

Mount a volume to /ftproot/ or at least document this behavior

possibility to show hidden files

i'd like to have an option to show hidden files (the ones that start with a .)
the motivation behind this is to be able to backup the .storage directory via ftp.

Revise/improve all log messages

Problem/Motivation

There are several reasons for this:

• Not all log messages are consistent across all add-ons.
• Some messages are unclear to the novice user.

Pull request to add some documentation

Problem/Motivation

To the untrained eye, it is not clear how to gain file system access to files that have been added to this ftp server. This can be solved via some documentation updates

Expected behaviour

A section in the README.md file outlining that files can be accessed by by enabling the share,config or backup folder options

Actual behaviour

The section does not exist

Steps to reproduce

Read the README.md file

Proposed changes

I will create a pull request to update the README.md file with changes that document this capability

FTP server does not work.

Problem/Motivation

I've installed the FTP server. Did standard set up and launched it. But cannot get FTP access. Any idea why?

(Why the issue was filed)
No FTP access while FTP server is running

Expected behavior

(What you expected to happen)
grant FTP access

Actual behavior

(What actually happened)
no ftp access

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

No serveradress / name

Problem/Motivation

no information about the name/address of the ftp server

Expected behavior

a documentation with the most obvious thing listed...

Actual behavior

absolutely no address or name is visible.

Steps to reproduce

install. and don't live in a ftp-nerd-bubble

Proposed changes

write how to access the ftp server in homeassistant
without a name this addon is useless

Where are the files?

Problem/Motivation

I uploaded a lot of files, but only shown up inside /var/lib/docker/overlay2/20c9ed508ebe51e105164f3b3834488bfa6b4fe856a0252fa0ce51632099fbb0/merged/ftproot/users/ftpuser/, there is no directory link between host and the docker?

Expected behavior

Should see the uploaded files inside a local host folder.

Actual behavior

Files cannot be touched, because only located inside the docker.

Steps to reproduce

Use the addon with any settings.

Proposed changes

add the -v /localdirectory/:/dockerdirectory/ to the docker container so we can reach our files.

Sorry if I misunderstood this but I try to fix it since days, and nobody on the forums was able to help with this.

Too many sessions - Connection refused

I tried multiple times with filezilla to connect to ftp but it refuses the connection constantly.
I can connect once and after five seconds i get a disconnect answer from 421.

It is possible to show the folders after the first connection. But i am not able to download the data i need because of this refused connection.

The protocol in FTP shows the following:

Can someone help with that?

addon indicates update is available, but running latest version.

from the addon log:

Add-on version: 3.3.1
There is an update available for this add-on!
Latest add-on version: null
Please consider upgrading as soon as possible.

FTP uploads are not visible locally and gone after addon restart

Files uploaded by my camera to FTP on HA are not accessible locally (cant find them in terminal) and they disappear after ftp addon restart. How can I set home directory for user so files will go where I want them and will be able to gram by telegram automation to be sent in a message?

Inflexible FTP-client only stores files in ftp-add-on root directory --> root directory of ftp add on not available in home assistant

Problem/Motivation

Inflexible FTP-client only stores files in ftp-add-on root directory --> root directory of ftp add on not available in home assistant

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...

Add-on: FTP
A secure and fast FTP server for Home Assistant

Add-on version: 4.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.13 (amd64 / qemux86-64)
Home Assistant Core: 2021.5.5
Home Assistant Supervisor: 2021.05.4

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] users.sh: executing...
[19:27:19] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[cont-init.d] users.sh: exited 0.
[cont-init.d] vsftpd.sh: executing...
[cont-init.d] vsftpd.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:27:21] INFO: Starting Log tailer...
[19:27:21] INFO: Starting FTP server...
Sat Jun 5 19:29:58 2021 [pid 2] CONNECT: Client "192.168.1.174"
Sat Jun 5 19:29:58 2021 [pid 1] [ftpuser] OK LOGIN: Client "192.168.1.174"
Sat Jun 5 19:29:58 2021 [pid 3] [ftpuser] FAIL DELETE: Client "192.168.1.174", "/20200213_181642_.jpg"
Sat Jun 5 19:30:17 2021 [pid 3] [ftpuser] FAIL RENAME: Client "192.168.1.174", "/20200213_181642_.jpg"
Sat Jun 5 19:45:26 2021 [pid 2] CONNECT: Client "192.168.1.174"
Sat Jun 5 19:45:27 2021 [pid 1] [ftpuser] OK LOGIN: Client "192.168.1.174"
Sat Jun 5 19:45:31 2021 [pid 2] CONNECT: Client "192.168.1.174"
Sat Jun 5 19:45:31 2021 [pid 1] [ftpuser] OK LOGIN: Client "192.168.1.174"
Sat Jun 5 19:45:31 2021 [pid 3] [ftpuser] OK UPLOAD: Client "192.168.1.174", "/20200213_181642_.jpg", 2946477 bytes, 7747.08Kbyte/sec

Unfortunately the root directory "/" is "not available" in homeassistant, therefore addressing "/20200213_181642_.jpg" is not possible.

Expected behavior

It would be great if you could set one home assistant folder, for example "share" as the ftp-add on root folder via configuration. That would be great.

Actual behavior

Files stored in the root folder can not be used.

see above

(How can someone else make/see it happen)

see above

Ohterwise it would be great to have a possiblity in the configuration, that all files/direcotries added in the root folder will be automatically moved to a folder (for example "share") set in the configuration.

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

No more than 11 PASV connections?

Problem/Motivation

It seems that there is only 11 PASV connection, regardless of the lowest - highest port range. MAC OS Finder tries to load preview of all videos in a directory, but hangs after 11 first ones.

Expected behavior

With the default config it is expected that only 11 PASV connections allowed, but when increasing the port range, more connections should be allowed. Initially it is 30000 - 30010, but changing it to 30000 - 30100 does not increase active PASV connections amount.

Actual behavior

MAC OS Finder tries to load preview of all videos in a directory, but hangs after 11 first ones. Then the only thing to do is disconnect, everything else is stucked.

Steps to reproduce

At least with MAC Finder (Big Sur) it happens every time. Not known, how about some FTP client app or Windows.

Proposed changes

Maybe configuration option for the maximum allowed PASV connections per host?

Change the time of the FTP Server

I am on the East coast of the US in the Easter Time Zone, my Raspberry Pi 3b+ is running the latest updated version of Hass.io (Home Assistant).

For some reason the FTP plug in is showing file creation times as if it was Hawaiian time instead of East Coast time. This is weird because Hassio and the Raspberry OS are showing the correct time.

Expected behavior

Show the file creation time as Eastern Time

Actual behavior

file creation time is the Hawaiian time zone

Steps to reproduce

I have no idea, I just added the plug-in, configured it, everything works fine except the time stamp

Proposed changes

maybe allow you to manually set your time zone like in Hassio in the configuration.yaml
homeassistant:
time_zone: America/New_York

I would like to thank you for creating this FTP add-on, it works great I must be missing something.

Modified timestamp through FTP server is off by timezone offset

Problem/Motivation

My timezone is UTC+1 (+2 in summer with DST). Files modified by Home Assistant or through Samba are displayed by the FTP server as modtime+1h. Files created through the FTP addon get a modtime of -1h.

Expected behavior

FTP should use UTC for modtime.

Actual behavior

FTP addon uses localtime.

Steps to reproduce

1. Modify a file through Samba or Home Assistant web interface and list the directory through the FTP addon. Modtime is 1 hour in the future.
2. Modify file through FTP and list it through Samba. Modtime is 1 hour in the past.

Proposed changes

Can the value use_localtime inside vsftpd.conf be changed from YES to NO? Or could this be made an configurable option though the addons YAML?

I think some users run their RTC in localtime so I guess they would need use_localtime to be set to yes? I run Home Assistant OS inside Hyper-V and have my Hyper-V clock set to UTC and found that my issues were resolved by changing the use_localtime value to no.

Option to show hidden files

As issue #11 mentions, this addon does not show hidden files or directories.

The reason is in vsftpd, which has this default behaviour, but it can be switched on with
force_dot_files=YES
option in /etc/vsftpd/vsftpd.conf

So it would be nice to have the same option in the config of this addon.

Change root directory

hi how can I change the default directory?

I solve it by modifying the file by adding:
/etc/vsftpd/users/$USER

"local_root=/ftp root/users/$USER/media"

but upon reboot addon HomeAssistant it is deleted,how can I solve it?

Connect to USB mounted Folder

Problem/Motivation

Attempts to access folders connected via USB via FTP

Expected behavior

Connectoion to USB via FTP

Actual behavior

Hello, I have SAMBA NAS running and can access my second hard disk and all USB sticks there cleanly

Unfortunately I cannot save via smb with a surveillance camera.

Now I have tried to access via the FTP addon. I can also access share and media, but not the mounted drives.

I would need help here on how to make the folders accessible via FTP

pasv_address will only resolve a numeric ip, not a hostname.

Problem/Motivation

When I access my FTP remotely I can only connect passively if I use a numeric ip, if I change to my duckdns hostname then it doesn't work

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

Connect remotely to the server and used the following config file

port: 21
data_port: 20
banner: Welcome to the Hass.io FTP service.
pasv: true
pasv_min_port: 30000
pasv_max_port: 30010
pasv_address: 1.1.1.80 real ip redacted
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
implicit_ssl: false
max_clients: 5
users:

• username: justcop
  password: redacted
  allow_chmod: true
  allow_download: true
  allow_upload: true
  allow_dirlist: true
  addons: false
  backup: false
  config: true
  media: true
  share: true
  ssl: false

this work

but when I change to:

port: 21
data_port: 20
banner: Welcome to the Hass.io FTP service.
pasv: true
pasv_min_port: 30000
pasv_max_port: 30010
pasv_address: ***.duckdns.org
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
implicit_ssl: false
max_clients: 5
users:

• username: justcop
  password: redacted
  allow_chmod: true
  allow_download: true
  allow_upload: true
  allow_dirlist: true
  addons: false
  backup: false
  config: true
  media: true
  share: true
  ssl: false

it does not work. I know that this hostname otherwise correctly resolves as I'm using this as the address of the FTP

Proposed changes

vsftp settings suggest a PASV_ADDR_RESOLVE option. Can this be enabled?

Fail login when deleting files

Problem/Motivation

When I try to delete a file it doesn't work, it gives a fail login error.

Expected behavior

The file should get removed

Actual behavior

It gives a FAIL LOGIN error, it's strange because when using the other commands it works fine (the fail login mesages are provoked by a delete command):

Steps to reproduce

I have this config:

- username: hassio
password: 59b466fd93164953e5
allow_chmod: true
allow_download: true
allow_upload: true
allow_dirlist: true
addons: false
backup: false
config: false
media: true
share: false
ssl: false

ftp upload to HA using ftp manager

Hey
how can i ftp upload to HA using ftp manager?

what is the path to the HA folder in Debian ( doker ) ?

Thnks!

Uploading files inside the share or media folder instead of root folder

Problem/Motivation

I want to upload Camera records automaticly with FTP, HomeAssistant can only see share media ssl or addon folder, but the FTP uploads to the root folder, what is unuseable to no files are uploaded.

Expected behavior

Should be able to select the default folder for FTP, so when I join to the FTP server I should be inside share folder for example instead of root. On any Camera there is no feature to select directory inside a Server.

Actual behavior

Downloading to / folder

Steps to reproduce

Upload anything

Proposed changes

DEFAULT_DIRECTORY selectable inside the config, you set it to the same folder where you give access to FTP user, for example
share folder. Hundreds of devices and softwares would work with FTP addon then, now a bit unusable for most of the stuffs.

Thank you very much,

i_like_to_be_pwned: true option doesn't work

Problem/Motivation

I want to use "123456" password for testing purposes.
Use this config:

port: 21
data_port: 20
banner: Welcome to the Hass.io FTP service.
pasv: true
pasv_min_port: 30000
pasv_max_port: 30010
pasv_address: ""
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
implicit_ssl: false
max_clients: 5
users:
  - username: admin
    password: 123456
    allow_chmod: false
    allow_download: true
    allow_upload: true
    allow_dirlist: true
    addons: false
    backup: false
    config: true
    media: true
    share: true
    ssl: false
i_like_to_be_pwned: true

Expected behavior

I can save configuration.
Server is running correctly.

Actual behavior

Trying to save config got error:

Can't start service:

[11:03:14] INFO: Starting Log tailer...
s6-rc: info: service init-vsftpd successfully started
[11:03:14] WARNING: Password is in the Have I Been Pwned database!
[11:03:14] WARNING: Password appeared 171031 times!
[11:03:14] FATAL: 
[11:03:14] FATAL: We are trying to help you to protect your system the
[11:03:14] FATAL: best we can. Therefore, this add-on checks your
[11:03:14] FATAL: configured password against the HaveIBeenPwned database.
[11:03:14] FATAL: 
[11:03:14] FATAL: Unfortunately, your configured password is considered
[11:03:14] FATAL: unsafe. We highly recommend you to pick a different one.
[11:03:14] FATAL: 
[11:03:14] FATAL: Please change the password in the 'users[0].password' option.
[11:03:14] FATAL: 
[11:03:14] FATAL: Check the add-on manual for more information.
[11:03:14] FATAL: 
s6-rc: warning: unable to start service init-users: command exited 1

Steps to reproduce

Set i_like_to_be_pwned option to true, use weak password for user (123456 for example)

Proposed changes

nope

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ⬆️ Update ghcr.io/hassio-addons/base Docker tag to v16.3.1

Detected dependencies

dockerfile

ftp/Dockerfile

• ghcr.io/hassio-addons/base 16.3.0

github-actions

.github/workflows/ci.yaml

.github/workflows/deploy.yaml

.github/workflows/labels.yaml

.github/workflows/lock.yaml

.github/workflows/pr-labels.yaml

.github/workflows/release-drafter.yaml

.github/workflows/stale.yaml

regex

ftp/Dockerfile

• ghcr.io/hassio-addons/base 16.3.0

ftp/build.yaml

• ghcr.io/hassio-addons/base 16.3.0
• ghcr.io/hassio-addons/base 16.3.0
• ghcr.io/hassio-addons/base 16.3.0

ftp/Dockerfile

• alpine_3_20/gcc 13.2.1_git20240309-r0
• alpine_3_20/linux-pam-dev 1.6.0-r0
• alpine_3_20/make 4.4.1-r2
• alpine_3_20/musl-dev 1.2.5-r0
• alpine_3_20/openssl 3.3.2-r0
• alpine_3_20/vsftpd 3.0.5-r2

---

• Check this box to trigger a request for Renovate to run again on this repository

Feature Request: Add HA action/event after a file got uploaded

My IPCAM uploads video files and this would allow me to convert them with ffmpeg to a format that the media browser in HA allows viewing. It would also allow users with IPCAMs that don't support ONVIF to get an event if something moved in the cam view, for other uses.

As a bonus it would be nice if the file extension which lead to an event/action can be configured.

FTP Cannot Connect

Problem/Motivation

Cannot connect to FTP via WIN SCP or Filezilla

Expected behavior

Expect to connect and see files

Actual behavior

It will connect, but then I get the following error:

WIN SCP
SSL3 alert write: fatal: protocol version wrong version number Disconnected from server Could not retrieve directory listing Error listing directory '/'.

FileZilla:
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: Disconnected from server: ECONNABORTED - Connection aborted
Error: Failed to retrieve directory listing

Steps to reproduce

The following is my config in the component:

{
  "log_level": "info",
  "port": 21,
  "data_port": 20,
  "banner": "Welcome to the Hass.io FTP service.",
  "pasv": true,
  "pasv_min_port": 30000,
  "pasv_max_port": 30010,
  "pasv_address": "REDACTED.duckdns.org",
  "ssl": true,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "implicit_ssl": false,
  "max_clients": 5,
  "users": [
    {
      "username": "REDATED",
      "password": "REDATED",
      "allow_chmod": false,
      "allow_download": true,
      "allow_upload": true,
      "allow_dirlist": true,
      "addons": true,
      "backup": true,
      "config": true,
      "share": true,
      "ssl": false
    }
  ]
}

I have SSL through the duckdns component with Lets Encrypt

Proposed changes

Possibly my config on RPI is wrong or client config wrong?

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

FROM THIS SITE: https://developer.ibm.com/answers/questions/213452/why-is-our-filezilla-ftp-client-receiving-gnutls-e/

In this situation it was found that the FTP server was configured (defaulted) to the draft level of the FTP/TLS RFCs. One effect of this is that the session is simply closed instead of first sending an SSL Close Alert message first.

If your TLSRFCLEVEL is configured as DRAFT, change it to TLSRFCLEVEL RFC4217. If it defaulted to DRAFT, add a TLSRFCLEVEL RFC4217 statement to the server's FTP.DATA input to change this behavior.

Specification of the TLSRFCLEVEL does not affect the initial SSL handshake or encryption of traffic; it changes the behavior when a session (or at least, SSL) ends. Specifically, configuring TLSRFCLEVEL RFC4217 will cause an SSL Close alert packet to be sent before actually closing the TCP connection (sending the FIN). Apparently the GnuTLS code used by FileZilla is strictly enforcing receipt of the alert, and errors out when a FIN arrives without the alert. So adding that configuration statement should resolve the problem with FileZilla not getting the LIST output.

Why is our Filezilla FTP client receiving GnuTLS error -110 when listing directory on z/OS FTP server?

We have FTPS configured on port 21 (security ALLOWED) and on port 990 (Security REQUIRED/Implicit). Filezilla connects successfully to the z/OS FTP server by using TLS to secure the control connection. But Filezilla cannot list the contents of a directory by using a TLS protected data connection. The screen shot shows these Filezilla client messages: Response: 125 List started OK Error: GnuTLS error -110 in gnu_tls_record_recv: The TLS Connection was non-properly terminated. Status: Server did not properly shut down TLS connection Error: Could not read from transfer socket: ECONNABORTED - Connection aborted Response: 250 List completed successfully. Error: Failed to retrieve directory listing

We verified that there is no firewall between the client and the mainframe. We also verified that the customer can connect to port 21 in the clear but receives an error on the same client if they try to use SSL/TLS (active FTP).

vsftpd fails to start with `unrecognised variable in config file: ssl_tlsv2`

I've just been trying to run the github head version of this addon, and it just loops with

[17:50:28] INFO: Starting FTP server...
[17:50:29] INFO: Starting FTP server...
[17:50:30] INFO: Starting FTP server...
[17:50:31] INFO: Starting FTP server...

I think the issue might be this change, as when I try running vsftpd from inside the container it complains like this...

root@local-ftp:/$ /run/s6/etc/services.d/vsftpd/run
[17:48:47] INFO: Starting FTP server...
500 OOPS: unrecognised variable in config file: ssl_tlsv2

If I edit /etc/vsftpd/vsftpd.conf in the running container, and remove the new ssl related lines, vsftpd starts up fine.

ftp send to telegram

is it possible to track the events of receiving files via ftp in order to send a file to telegram using automation?

ipcam ->(ftp)->home assistant->automation->telegram chat

interested in this possibility. It's real?

I understand that telegram does not apply to the functionality of this add-on.
I'm asking about being able to track a file transfer event.

!secret not working

Problem/Motivation

For security reasons I would like to save my passwords in the secrets.yaml file. As stated in the documentation that should be possible however i'm receiving a error when saving the settings of the FTP addon.

Expected behavior

To save my passwords in the secrets.yaml file and to use these in the FTP addon

Actual behavior

FTP addon throughs out a error when saving the settings when using !secret ftp_username and !secret ftp_password

Steps to reproduce

Use the following settings in the FTP addon,

{
      "username": "!secret ftp_username",
      "password": "!secret ftp_password",
      "allow_chmod": false,
      "allow_download": false,
      "allow_upload": true,
      "allow_dirlist": true,
      "addons": false,
      "backup": false,
      "config": true,
      "share": false,
      "ssl": false
    }

When using above settings i'm getting the following error,

not a valid value for dictionary value @ data['options']. Got {'log_level': 'info', 'port': 21, 'data_port': 20, 'banner': 'Dahua ip camera uploads', 'pasv': True, 'pasv_min_port': 30000, 'pasv_max_port': 30010, 'pasv_address': '', 'ssl': False, 'certfile': 'fullchain.pem', 'keyfile': 'privkey.pem', 'implicit_ssl': False, 'max_clients': 5, 'users': [{'username': '!secret ftp_username', 'password': '!secret ftp_username', 'allow_chmod': False, 'allow_download': False, 'allow_upload': True, 'allow_dirlist': True, 'addons': False, 'backup': False, 'config'...