serversideup/proftpd repository overview

⁠ProFTPD Docker Image

This Docker image provides a customizable ProFTPD server with MySQL authentication support and TLS encryption.

Docker Image	Size
serversideup/proftpd⁠

⁠Base Image

The image is based on ubuntu:24.04, providing a stable and up-to-date environment for running ProFTPD.

⁠Features

• ProFTPD server with MySQL authentication
• TLS encryption support
• Customizable configuration via environment variables
• Self-signed SSL certificate generation
• IP address banning (bans IP addresses for 1 hour that fail authentication 5 times in 10 minutes)
• Native Docker health checks to ensure the server is running

⁠Environment Variables

The following environment variables can be used to customize the ProFTPD server:

⁠Build Defaults

The following build arguments are used during the image build process:

⁠Usage

If you want to use Let's Encrypt with ProFTPD + CloudFlare + MySQL authentication, you can also include our other image serversideup/certbot-dns-cloudflare⁠ to automatically generate the SSL certificates and share it with the ProFTPD container.

Here is an a full example configuration of how to use the ProFTPD image with Let's Encrypt. Just set your the environment variables to match your set up and you're good to go:

services:
  certbot:
    image: serversideup/certbot-dns-cloudflare:latest
    volumes:
      - certbot_data:/etc/letsencrypt
    environment:
      CLOUDFLARE_API_TOKEN: "${CERTBOT_CLOUDFLARE_API_TOKEN}"
      CERTBOT_EMAIL: "${CERTBOT_EMAIL}"
      CERTBOT_DOMAINS: "${FTP_SERVER}"
      CERTBOT_KEY_TYPE: "rsa"
      PUID: "999"
      PGID: "999"
  ftp:
    volumes:
      - ftp_data:/var/ftp/users
      - ftp_logs:/var/log/proftpd
      - certbot_data:/etc/letsencrypt
    environment:
      FTP_DEBUG_LEVEL: "0" # 0-10 (10 = most verbose)
      FTP_LOG_LEVEL: "info" # debug, info, warn, error
      FTP_MASQUERADE_ADDRESS: "${FTP_SERVER}"
      FTP_PASSIVE_PORT_RANGE_START: "60000"
      FTP_PASSIVE_PORT_RANGE_END: "60049"
      FTP_SQL_USERS_TABLE: "users"
      FTP_TLS_CERTIFICATE_FILE: "/etc/letsencrypt/live/${FTP_SERVER}/fullchain.pem"
      FTP_TLS_CERTIFICATE_KEY_FILE: "/etc/letsencrypt/live/${FTP_SERVER}/privkey.pem"
      FTP_TLS_REQUIRED: "on"
      FTP_TLS_WAIT_FOR_CERTIFICATE: "true"
      MYSQL_DATABASE: "${FTPUSER_DATABASE}"
      MYSQL_HOST: "${FTPUSER_HOST}"
      MYSQL_PASSWORD: "${FTPUSER_PASSWORD}"
      MYSQL_PORT: "${FTPUSER_PORT}"
      MYSQL_USER: "${FTPUSER_USERNAME}"
    depends_on:
      - certbot
    ports:
      - target: 21
        published: 21
        protocol: tcp
        mode: host
      - target: 990
        published: 990
        protocol: tcp
        mode: host
      - target: 60000
        published: 60000
        protocol: tcp
        mode: host
      - target: 60001
        published: 60001
        protocol: tcp
        mode: host
      - target: 60002
        published: 60002
        protocol: tcp
        mode: host
volumes:
  ftp_logs:
  ftp_data:
  certbot_data:

Make sure to replace the MySQL connection details with your own.

⁠Configuration

The ProFTPD configuration file (proftpd.conf) is included in the image. It sets up the following:

• FTP and FTPS (TLS) support
• MySQL authentication
• Passive port range: 60000-60100
• TLS Protocol: TLSv1.2 and TLSv1.3
• Logging configuration
• Home directory creation for users
• Anonymous access disabled
• IP address banning (bans IP addresses for 1 hour that fail authentication 5 times in 10 minutes) You can modify the proftpd.conf file to further customize the ProFTPD server according to your needs.

⁠Security Considerations

• The image generates a self-signed SSL certificate for FTPS. For production use, replace it with a valid SSL certificate.
• Ensure to use strong passwords for MySQL authentication.
• Review and adjust the proftpd.conf file to match your security requirements.
• Consider using Docker secrets or a secure method to pass sensitive information like database credentials.

⁠Ports

The following ports are exposed:

⁠Special Note on orchestrators

If you are using an orchestrator like Kubernetes, you will need to ensure that the ports are opened on the container and the host.

For example, for Docker Swarm you need to use the long format for the ports directive in your docker compose file:

services:
  ftp:
    image: serversideup/proftpd
    ports:
      - target: 21
        published: 21
        protocol: tcp
        mode: host
      - target: 990
        published: 990
        protocol: tcp
        mode: host
      - target: 60000
        published: 60000
        protocol: tcp
        mode: host
      - target: 60001
        published: 60001
        protocol: tcp
        mode: host
      - target: 60002
        published: 60002
        protocol: tcp
        mode: host

Unfortunately, Docker Swarm does not support specifying ranges for published ports with the long format, so you need to specify each port individually. Just be sure to open all ports within the range that you define within the FTP_PASSIVE_PORT_RANGE_START and FTP_PASSIVE_PORT_RANGE_END environment variables.

⁠MySQL Database

You can use either MySQL or MariaDB. Create a table in the database with the following SQL:

CREATE TABLE ftpusers (
    id INT AUTO_INCREMENT PRIMARY KEY,  -- Auto-incrementing primary key
    username VARCHAR(255) NOT NULL,     -- Username, max length 255 characters
    password VARCHAR(255) NOT NULL,     -- Password, max length 255 characters
    uid INT NOT NULL,                   -- User ID, integer type
    gid INT NOT NULL,                   -- Group ID, integer type
    homedir VARCHAR(255) NOT NULL,      -- Home directory path, max length 255 characters
    shell VARCHAR(255) NOT NULL         -- Shell, max length 255 characters
);

Then you can add users to the database with the following SQL:

INSERT INTO ftpusers (username, password, uid, gid, homedir, shell)
VALUES (
  'testuser',
  CONCAT('{sha256}', TO_BASE64(UNHEX(SHA2('mypassword', 256)))),
  2001,
  2001,
  '/var/ftp/users/testuser',
  '/bin/false'
);

⁠Resources

• Discord⁠ for friendly support from the community and the team.
• GitHub⁠ for source code, bug reports, and project management.
• Get Professional Help⁠ - Get video + screen-sharing help directly from the core contributors.

⁠Contributing

As an open-source project, we strive for transparency and collaboration in our development process. We greatly appreciate any contributions members of our community can provide. Whether you're fixing bugs, proposing features, improving documentation, or spreading awareness - your involvement strengthens the project.

• Bug Report: If you're experiencing an issue while using these images, please create an issue⁠.
• Security Report: Report critical security issues via our responsible disclosure policy⁠.

Need help getting started? Join our Discord community and we'll help you out!

⁠Our Sponsors

All of our software is free an open to the world. None of this can be brought to you without the financial backing of our sponsors.

⁠Black Level Sponsors

⁠Bronze Sponsors

⁠Individual Supporters

⁠About Us

We're Dan⁠ and Jay⁠ - a two person team with a passion for open source products. We created Server Side Up⁠ to help share what we learn.

Dan Pastori	Jay Rogers

⁠Find us at:

• 📖 Blog⁠ - Get the latest guides and free courses on all things web/mobile development.
• 🙋 Community⁠ - Get friendly help from our community members.
• 🤵‍♂️ Get Professional Help⁠ - Get video + screen-sharing support from the core contributors.
• 💻 GitHub⁠ - Check out our other open source projects.
• 📫 Newsletter⁠ - Skip the algorithms and get quality content right to your inbox.
• 🐥 Twitter⁠ - You can also follow Dan⁠ and Jay⁠.
• ❤️ Sponsor Us⁠ - Please consider sponsoring us so we can create more helpful resources.

⁠Our products

If you appreciate this project, be sure to check out our other projects.

⁠📚 Books

• The Ultimate Guide to Building APIs & SPAs⁠: Build web & mobile apps from the same codebase.
• Building Multi-Platform Browser Extensions⁠: Ship extensions to all browsers from the same codebase.

⁠🛠️ Software-as-a-Service

• Bugflow⁠: Get visual bug reports directly in GitHub, GitLab, and more.
• SelfHost Pro⁠: Connect Stripe or Lemonsqueezy to a private docker registry for self-hosted apps.

⁠🌍 Open Source

• AmplitudeJS⁠: Open-source HTML5 & JavaScript Web Audio Library.
• Spin⁠: Laravel Sail alternative for running Docker from development → production.
• Financial Freedom⁠: Open source alternative to Mint, YNAB, & Monarch Money.