Configure Docker for FTP

[Micsi]

Hi,

I would like to configure copyparty in a docker container as an ftp server.
I know what active and passive ftp is and I need to provide passive ftp. But I am unsure what the docs mean by

then finally update your docker config so that the port-range you specified (12000-12099) is exposed to the internet

Can someony please post a working docker compose example, please?

thanks, best regards
Jochen

[9001]

similar to how the http/https port is being forwarded,

    ports:
      - 3923:3923

i think you're supposed to add another Line with - 12000-12099:12000-12099

[Micsi]

Hi,

thanks for coming back to me so quickly!

This seems to work. Sort of. You also have to expose the ftp-port itself like:

from the compose.yaml:

ports: - 3923:3923 - 21:21 - 1200-1205:1200-1205

and from my copyparty.conf:

[global] e2dsa # enable file indexing and filesystem scanning e2ts # enable multimedia indexing ansi # enable colors in log messages (both in logfiles and stdout) ftp: 21 ftp-pr: 1200-1205

Basically, I can log in, but the passive connection does not get established…

17:29:52.217 root started FTPd 17:29:52.224 root workers OK ... 17:33:29.757 192.168.178.34:53620 [] FTP session opened (connect) 17:33:29.758 192.168.178.34:53620 [ed] USER 'ed' logged in. 17:33:59.789 192.168.178.34:53620 [ed] Passive data channel timed out. 17:34:30.758 192.168.178.34:53619 [ed] FTP session closed (disconnect).

I have copyparty run as root in the container, because I have no users on my dockerhost… this way I can red/write to the mounted volumes… at least the web-interface is working this way and I can upload to the container…

Any ideas?

[9001]

ah yes, good point that the ftp-port itself must be forwarded.

however I'm not getting the same issue you are when I try to connect; I instead get a complaint that I forgot to specify the ftp-nat option. By setting ftp-nat: 192.168.123.1 (which is one of the IPs on this machine) and then connecting to 192.168.123.1 from filezilla, I am able to connect.

do you have any firewalls (ufw, firewalld, or such)?

also, note that if you are willing to let the container use host network, then you can skip most of the complicating factors -- no need to forward the ports from the container, and no need to specify ftp-nat -- however it means isolation between copyparty and host is slightly reduced, although I cannot think of any reasons why this should be an issue

[Micsi]

Adding ftp-nat did the trick!

But I did not get any messages regarding that.

Thanks a lot! Best regards

Jochen

[Micsi]

the same happens with a port-ramge 12000-12005 and also if each port os defined separately:

`ports:
- 3923:3923
- 21:21

  - 12000:12000
  - 12001:12001
  - 12002:12002
  - 12003:12003
  - 12004:12004
  - 12005:12005

`

[Micsi]

sorry for the messy posts. Somehow, the editor is putting my code-entries into a single line…