Cant Connect : mod_delay error

[bonnebulle]

Thanks for this Docker solution !

I cant FTP connect (using Filezilla, in LAN)
Maybe I better do a issue on a proftpd forum...
let me know

---

I have an error in my log ( I can ignore it ) :

mod_delay/0.7: no DelayOnEvent rules configured with "DelayTable none" in effect, disabling module

---

I also have an error saying username:username not exists.
But, I already check/create the user and group...

chown: invalid group: 'username:username'

---

Resultat :
On Filezilla I have an error too (but password looks great) :

Error:	Connection closed by server
Error:	Could not connect to server

And ftp ( looks $(passwd username) dont works like I do ) :

ftp ftp://@192.168.1.23
Connected to 192.168.1.23.
220 ProFTPD Server (Debian) [192.168.1.23]
331 Password required for ftp://
Password: 
530 Login incorrect.
ftp: Login failed.
Remote system type is UNIX.
Using binary mode to transfer files.

---

My config :

version: '3.7'
services:
  proftpd:
    image: kibatic/proftpd
    network_mode: "host"
    restart: unless-stopped
    environment:
      FTP_LIST: "username:password"
      USERADD_OPTIONS: "-o --gid 33 --uid 33"
      # optional : default to 50000 and 50100
      # My NAT is open...
      PASSIVE_MIN_PORT: 1024
      PASSIVE_MAX_PORT: 1035
      # optional : default to undefined
      MASQUERADE_ADDRESS: ftp.mydomaine.cow
    volumes:
      - "/media/HDD//:/home/username"

Thanks

[Avalancs]

Also experiencing this issue, using docker-compose.yml example from project and trying to connect on the same machine that docker is running

[Avalancs]

I could get my setup to work, what I found:

So the message

mod_delay/0.7: no DelayOnEvent rules configured with "DelayTable none" in effect, disabling module

Is related to proftpd/proftpd#1440 which does not cause an error, and has been fixed, but not yet released on Debian which is the base docker image.

The message

chown: invalid group: 'username:username'

Is probably the problem. If you look into the https://github.com/kibatic/docker-proftpd/blob/master/docker-entrypoint.sh file from the list it creates the user and then chowns the /home/username folder. In my case I used a gid that was on my Ubuntu 22.04 WSL2 system, but because of WSL it did not get mapped inside the container, so I also got a message of

useradd: group '999' does not exist

And I checked with docker diff <container name> and found that if the useradd command fails then the home directory doesn't get created either.

I removed the --gid flag from USERADD_OPTIONS and then the login worked, but the listing of '/' failed. Then I had to fix my MASQUERADE_ADDRESS and then everything worked. I was hasty and created an issue for allowing the container to start when the user creation failed: #5