Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No FTP folders #76

Closed
Derweis opened this issue Mar 6, 2024 · 4 comments
Closed

No FTP folders #76

Derweis opened this issue Mar 6, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@Derweis
Copy link

Derweis commented Mar 6, 2024

NOTE:
all of the below are optional, consider them as inspiration, delete and rewrite at will, thx md

Describe the bug
FTP is uncommented, the port has not changed, it does not load folders when trying to log in to the server

Server details
if the issue is possibly on the server-side, then mention some of the following:

  • server OS / version: debian 12
  • python version: 3.11.2
  • copyparty arguments:
  • filesystem (lsblk -f on linux): ext4

Client details
if the issue is possibly on the client-side, then mention some of the following:

  • the device type and model:
  • OS version:
  • browser version: filezilla
@Derweis Derweis added the bug Something isn't working label Mar 6, 2024
@Derweis
Copy link
Author

Derweis commented Mar 6, 2024

image
image2

@Derweis
Copy link
Author

Derweis commented Mar 6, 2024

image3

@9001
Copy link
Owner

9001 commented Mar 6, 2024

Hello, and thanks for giving copyparty a try 👍

I think you're getting this issue because you're running copyparty in docker, which gets a bit tricky because FTP is a weird protocol... it uses the main socket (on port 3921) just for sending control messages back and forth, but it will open an additional connection for larger stuff (each directory listing, and each file transfer). And there's a difference between active and passive mode, which decides if the client will make another connection to the server, or if the client should start listening for a connection from the client... So this makes FTP a bit slow, and a pain in the ass to deal with 😁

You'll want to specify a port-range to allow copyparty to use for data transfers, for example 12000 through 12099, which will allow for 100 actions in parallel. And you will have to tell copyparty what the server's external IP is, which is the only IP that the clients will be able to connect to, since docker kinda destroys that information by routing the connections through its own network before it hits copyparty.

The following additions to the [general] config section should tell copyparty what it needs to know:

[global]
  ftp-nat: 127.0.0.1
  ftp-pr: 12000-12099

Replace 127.0.0.1 with the actual IP that the clients will be connecting to, or leave it as 127.0.0.1 if you'll only be using this yourself.

Then, finally, you need to run the docker container with all the ports from 12000 through 12099 forwarded to ports 12000 through 12099.

Let me know if it works out! And thanks for pointing this out, I'll see if I can mention it somewhere in the docker documentation 👍

@Derweis
Copy link
Author

Derweis commented Mar 6, 2024

Thank you very much, it helped

@9001 9001 closed this as completed Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants